|
||||||||||||||||||||
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-14144) Build config his... dbai...@hp.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... jorge...@gmail.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... dbai...@hp.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... dbai...@hp.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... h...@koblmueller.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... h...@koblmueller.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... dbai...@hp.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... h...@koblmueller.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... gregory.boissi...@gmail.com (JIRA)
created a simple job that uses sleep. Seems you need to give the config history plugin long enough to both spot the change to the build.xml and be able to create a back of the change before the build job completes.
Added xml from http://localhost:8080/pluginManager/api/xml?depth=1 as well as xml files for envinject, jobConfigHistory and system configuration.
Versions
Jenkins: 1.472
EnvInject: 1.56
JobConfigHistory: 1.13