Another workaround is to avoid renaming jobs, and prefer create new job by copying the old one, then remove the old job.

Drawbacks for this solution :

  • Build history is lost
  • I totally agree this is not ideal, especially on large user codebase where we cannot keep an eye on everyone's job config

But this is the only I can provide now.
Fixing this issue would imply a big refactor on the way the plugin uses the scm abstractions (see my previous comments), and this is not something I have time to do nowadays.

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/groups/opt_out.

Reply via email to