![]() |
|
|
|
|
Change By:
|
Nihar Amin
(17/Jan/13 7:30 PM)
|
|
Description:
|
Jenkins Version - 1.4.80
Uploading: http://maven.platform.tm.tmcs:8081/nexus/service/local/staging/deploy/maven2/com/ticketmaster/wallet/wallet-parent/5.0.0-SNAPSHOT/
wallet-parent-5.0.0-20130111.191842-1.pom
ERROR: Failed to deploy artifacts: Could not transfer artifact com.ticketmaster.wallet:wallet-parent:pom:5.0.0-20130111.
191842
1910042
-1 from/to staging (http://maven.platform.tm.tmcs:8081/nexus/service/local/staging/deploy/maven2/): Failed to transfer file: http://maven.platform.tm.tmcs:8081/nexus/service/local/staging/deploy/maven2/com/ticketmaster/wallet/wallet-parent/5.0.0-SNAPSHOT/wallet-parent-5.0.0-20130111.
191842
10082042
-1.pom. Return code is: 400, ReasonPhrase:Bad Request
Lately we have been seeing some issues with 3 of our projects which leads to build failure and they are related to configuration bug. After doing some investigation, we found in all cases that the Repository URL, and Repository ID fields of the Post-Build Actions settings mysteriously had been set blank in the jenkins job. In none of these cases do members of our team recall making any changes to the job, and certainly did not modify these fields, in this last case we do know that a team member had viewed the job page, but also that *no* changes were made, let alone applied or saved. The failure is always in these two fields and its always the same - the fields go blank.
After build failure, if we reset these two fields with correct values it works fine but a few days later it goes blank again. The fact that this blanking behavior affects the same two fields every time is a sign of configuration bug.
Can you please provide some feedback?
Also it'd be great if Jenkins job configurations could be saved as text and examined.
Thanks
|
|
|
|
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
|
