|
||||||||||||||
|
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 |
||||||||||||||
- [JIRA] (JENKINS-15443) Duplicate jira com... [email protected] (JIRA)
- [JIRA] (JENKINS-15443) Duplicate jir... [email protected] (JIRA)
- [JIRA] (JENKINS-15443) Duplicate jir... [email protected] (JIRA)
- [JIRA] (JENKINS-15443) Duplicate jir... [email protected] (JIRA)

Turns out the ops team had cloned our ci environment and changed DNS entries to point at new machine, but left the old one running. Thus had 2 jenkins instances running with duplicate jobs, which is why we were getting the double posts - (kicking off builds about same time, the 'incorrect' build number was actually correct build number on the old jenkins box.