|
||||||||
|
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/d/optout.
Somehow this managed to work itself out. I tried several different things with no success. Ultimately the two things that were done last are most likely what cleared up the issue. One of them was a job being modified to "get a build working" and it appeared that Jenkins wasn't retaining changes I was making to the job definition until several attempts were done. The job would execute with the modified script, but then it would revert back somehow on it's own to the state before my changes. Then the next thing that was done was to clone a job with a build on github PR. I had gotten pulled away on a conference call and when I came back a little more than an hour later to "dig back in", I noticed that the site was working and others on the team were able to verify. Mental note to self... snapshot the VM before changing anything.