![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
SCM/JIRA link daemon
|
|
Components:
|
cli |
|
Created:
|
16/Jul/13 9:57 AM
|
|
Description:
|
Demo step by step:
Step1: creat a job as maven2/3 project
Step2: make a copy of the job's config.xml as config-old.xml
Step3: update "Root POM" of the job from UI to "pom-new.xml"
Step4: update the job using "update-job" CLI Command with config-old.xml
Step5: Checking....
(1) from the backend, the config.xml is the same as config-old.xml!
(2) from the UI side, it's "pom-new.xml"!
Step6: reload configuration of Jenkins, back to normal!
So, we got it!
"update-job" CLI command has a bug when update "Root POM", just like change the config.xml directly.
|
|
Project:
|
Jenkins
|
|
Labels:
|
cli
update-job
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
bruce zhang
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
