After some analysis of my previous script I realized it contained a lot of false positives possibly due to years of accumulated history of broken builds, java crashes, wrong copying of jobs between servers, etc, that lead to the following most common cases:

  • numbered links pointing to removed build directories (solution: remove links)
  • build directories without build.xml file (solution: remove directories)
  • build directories without numbered links (solution: create links)
  • build directories not in date format (solution: delete directories)

Since this is a common cause many I created a simple script to detect those common problems with optional cleanup (passing argument '-c') - Unable to embed resource: check_invalid_builds.sh of type application/x-sh

Also the same script for checking the missing builds as given as excerpt above - Unable to embed resource: check_missing_builds.sh of type application/x-sh

Tested in RHEL6 and Solaris 10 (with gnu utils)

Change By: Jose Sa (01/Apr/13 4:24 AM)
Attachment: check_invalid_builds.sh
Attachment: check_missing_builds.sh
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to