[
https://issues.jenkins-ci.org/browse/JENKINS-10459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Seidel updated JENKINS-10459:
---------------------------------
Labels: bug builds plugins promoted (was: )
> Jenkins promoted builds plugin wrecks job configuration respectively fails on
> updating
> ---------------------------------------------------------------------------------------
>
> Key: JENKINS-10459
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10459
> Project: Jenkins
> Issue Type: Bug
> Components: promoted-builds
> Affects Versions: current
> Environment: WinXP SP3, Jenkins 1.423
> Reporter: Jan Seidel
> Labels: bug, builds, plugins, promoted
>
> I have noticed from beginning a weird behaviour with the promoted builds
> plugin.
> A job configuration can be made as long as there is no promoted builds plugin
> configured.
> Any changes made after the plugin is active/configured will result in a
> "Error - Failed to create".
> In newer Jenkins versions do the changes in the job config simply not take
> place. The config file is completely wrecked in case you use an older version
> of Jenkins.
> The config files for the promote plugin remain intact. Rebuilding the job
> configuration and activating the promote plugin will not lead to a reuse of
> the old promote config files. The inteface behaves like it is first time you
> use it. Saving will then overwrite the old configuration.
> Only ways to make changes later on are either to deactivate the promote
> plugin, make the changes and save and then rebuild the promote plugins
> configuration from scratch or by making the changes with an text editor and
> reload the jenkins configuration.
> I have made some research and noticed that the content of text fields in the
> job configuration are terminated with a 
> This terminator is removed entirely after the promote plugin is active. I
> have no proof but I think this is somehow related. The terminator is present
> until the passage comes that configures the promote plugin. Everything past
> the passage is not terminated.
> So in other words. Tasks have the terminator, build steps not
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
