|
||||||||
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-13536) File parameter causi... to...@hellberg.name (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... to...@hellberg.name (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... imoutsat...@msn.com (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... imoutsat...@msn.com (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... dogf...@java.net (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... m...@marc-seeger.de (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... m...@marc-seeger.de (JIRA)
- [JIRA] (JENKINS-13536) File parameter ... jgl...@cloudbees.com (JIRA)
Have noticed that the following 'hack' on the offending build.xml file will allow a 'Reload configuration from disk' operation to parse and load the missing build in the UI. Simply replace the offending <dfosFile> element with an empty <cachedContent> element.
So in the original example above:
replace
<dfosFile>/tmp/upload_6e074d3b_136c03af218__8000_00000013.tmp</dfosFile>
with
<cachedContent></cachedContent>