|
||||||||
|
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.
Do you mean upgrading Jenkins itself?
I just upgraded Jenkins from 1.567 to 1.568. I changed some job configuration values afterwards; for some jobs those changes are recorded, for other jobs they are not. Note that this behavior stays the same for each job. Thus, the same jobs keep not working, the other ones keep working. In this sense, the behavior is consistent over time; at least since it stopped to work.