Jenkins › Jenkins issues

[JIRA] (JENKINS-12441) Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied

classic Classic list List threaded Threaded
♦
♦
 4 messages Options
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-12441) Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied

JIRA noreply@jenkins-ci.org
Raul Arabaolaza created JENKINS-12441:
-----------------------------------------

             Summary: Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied
                 Key: JENKINS-12441
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12441
             Project: Jenkins
          Issue Type: Bug
          Components: config-autorefresh
            Reporter: Raul Arabaolaza
            Assignee: jieryn


We´re using the Remote API to update a job´s config making a POST
request with the new config.xml file to the jenkins_url/job/jobName/
config.xml URL, some of the things changed are the child jobs of the
build.
It seems to work fine, the config.xml file is changed and in the web´s
UI job´s config page the new values are reflected, the same for the
physical config.xml file in the Jenkins server. However in the job
details page the child projects are not updated and when I execute the
job the old child projects are executed.
If i restart the server the new child projects are executed so it
seems something related to config caches or similar.

I think that updating the config.xml file should automatically reload the job configuration if it has to be usefull.

Regards, Raul

--
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-12441) Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158120#comment-158120 ]

Nelma Tuñacao commented on JENKINS-12441:
-----------------------------------------

What's the current status on this issue? We are looking forward for this to get fixed.
               

> Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied
> ----------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-12441
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12441
>             Project: Jenkins
>          Issue Type: Bug
>          Components: config-autorefresh
>            Reporter: Raul Arabaolaza
>            Assignee: jieryn
>
> We´re using the Remote API to update a job´s config making a POST
> request with the new config.xml file to the jenkins_url/job/jobName/
> config.xml URL, some of the things changed are the child jobs of the
> build.
> It seems to work fine, the config.xml file is changed and in the web´s
> UI job´s config page the new values are reflected, the same for the
> physical config.xml file in the Jenkins server. However in the job
> details page the child projects are not updated and when I execute the
> job the old child projects are executed.
> If i restart the server the new child projects are executed so it
> seems something related to config caches or similar.
> I think that updating the config.xml file should automatically reload the job configuration if it has to be usefull.
> Regards, Raul

--
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-12441) Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159413#comment-159413 ]

jieryn commented on JENKINS-12441:
----------------------------------

This issue was in the wrong component.
               

> Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied
> ----------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-12441
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12441
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>            Reporter: Raul Arabaolaza
>
> We´re using the Remote API to update a job´s config making a POST
> request with the new config.xml file to the jenkins_url/job/jobName/
> config.xml URL, some of the things changed are the child jobs of the
> build.
> It seems to work fine, the config.xml file is changed and in the web´s
> UI job´s config page the new values are reflected, the same for the
> physical config.xml file in the Jenkins server. However in the job
> details page the child projects are not updated and when I execute the
> job the old child projects are executed.
> If i restart the server the new child projects are executed so it
> seems something related to config caches or similar.
> I think that updating the config.xml file should automatically reload the job configuration if it has to be usefull.
> Regards, Raul

--
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-12441) Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jieryn updated JENKINS-12441:
-----------------------------

       Assignee:     (was: jieryn)
    Component/s: core
                     (was: config-autorefresh)
   

> Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied
> ----------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-12441
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12441
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>            Reporter: Raul Arabaolaza
>
> We´re using the Remote API to update a job´s config making a POST
> request with the new config.xml file to the jenkins_url/job/jobName/
> config.xml URL, some of the things changed are the child jobs of the
> build.
> It seems to work fine, the config.xml file is changed and in the web´s
> UI job´s config page the new values are reflected, the same for the
> physical config.xml file in the Jenkins server. However in the job
> details page the child projects are not updated and when I execute the
> job the old child projects are executed.
> If i restart the server the new child projects are executed so it
> seems something related to config caches or similar.
> I think that updating the config.xml file should automatically reload the job configuration if it has to be usefull.
> Regards, Raul

--
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
Loading...
Powered by Nabble See how NAML generates this page