|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
This appears to be related to our using multiple S3 Profiles. We have ~18 projects on the problematic Jenkins server, most using the S3 uploader. We have 3 profiles setup in the general config area for S3. 2 are identical with the second being setup when the first set appeared to fail (adding credentials seems to temporarily get it working again as well). The other set was added for a different S3 bucket on a different project. We have noticed that when most builds go "unstable" due to S3 uploads failing, this other project still works. After restarting Jenkins to get the other projects working again, this project fails. It looks like Jenkins is switching credential sets between projects.