NAC Build Automation

ACT-2 31

Keyboard shortcuts  
Summarize the review outcomes (optional)
 
#permalink

Details

Warning: no files are visible, they have all been filtered.
Participant Role Time Spent Comments Latest Comment
Author 1h 17m 15 Done
Amanda Bentley (deleted user)
Moderator      
Reviewer - Complete 1h 9m 16 This section of code is not really failing the Jenkins jo...
Total   2h 25m 31  

Branches in review

#permalink

Issues Raised From Comments

Key Summary State Assignee
#permalink

General Comments

Joe McCord

Amanda has established a new standard with the job parameters for the SVN log...

Amanda has established a new standard with the job parameters for the SVN login credentials. The SVNUSER and SVNPASS parameter names need to now be LDAP_USER_ID and LDAP_USER_PASSWD.

You need to incorporate error handling into the job:

  • validate job parameters are set correctly
  • validate code exists at the set path (look for solution file) before building
  • validate all necessary files were deleted as desired
  • before moving any files, validate the files exists at the expected location
  • after moving files, validate the files got moved to the new location
  • validate a tag was created if the option was selected
  • validate the build commit was successful


Make sure that each error handling check is logged

Send an email on success of job. One possible way is to add a post-build action titled 'Editable Email Notification' and add a trigger to that for 'Success'. This is purely a suggestion of a possible way. I have not tested this option myself.

/NAC_Build_Automation_configOutput.txt Added 2
Open in IDE #permalink
/NACconfigOutput.txt Added 28
Open in IDE #permalink
/configOutput_10292014.txt Added
Open in IDE #permalink

Review updated: Reload | Ignore | Collapse

You cannot reload the review while writing a comment.

Create issue

X
Assign To Me

Log time against