![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
cli |
|
Created:
|
24/Jan/15 12:32 AM
|
|
Description:
|
Hi.
I am using the ssh api to update jobs with the 'update-job' command.
I have not investigated if this is equivalent 100% to a POST with the config.xml.
There is a difference between the behavior I see and changing the job through the UI. The "update-job" command does not update the config.xml with current plugins versions, whereas saving the job in the UI changes the current plugins versions in the config.xml file.
Scenario #1
- create a job that uses some plugins
- get the config.xml (config 1)
- update jenkins with newer plugins
- restart
- post the config.xml with update-job command
- get the config.xml (config 2)
- compare config 1 and 2
- observe that currently config 1 and 2 are the same
- observe that currently config 2 does not have the new plugins version
Scenario #2
- create a job that uses some plugins
- get the config.xml (config 1)
- update jenkins with newer plugins
- restart
- open the job with the "configure" menu
- perform no changes but hit "save"
- get the config.xml (config 2)
- compare config 1 and 2
- observe that currently config 1 and 2 are different (expected behavior)
- observe that currently config 2 DOES have actual plugins version (expected behavior)
Action items:
- either make "update-job" behave the same as UI "save" button,
- or provide an option to the "update-job" command (e.g. "--update-plugins") that will persist the job and update the relevant plugins version.
|
|
Environment:
|
1.580.1
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Damien Nozay
|
|
|
|
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/d/optout.
