Change jenkins root configuration config.xml location












0















I am setting up a customized Jenkins. My jenkins home is



echo $JENKINS_HOME
/srv/jenkins


This means that the location of my config.xml file is



$JENKINS_HOME/config.xml
/srv/jenkins/config.xml


But I want Jenkins to read the config.xml file from under



$$JENKINS_HOME/config/config.xml
/srv/jenkins/config/config.xml


You might ask why ? Because since this is a customized Jenkins, Im am deploying the config.xml file on runtime in a Helm chart on Kubernetes and this file will change based on the customization by different teams. And I want this file to persist after Ive done the modification during the InitContainer phase of my pod startup.



One thing I tried was to create a softlink



jenkins@25bea2ece6a9:~$ cd /srv/jenkins/
jenkins@25bea2ece6a9:~$ ls -ltrh | grep config.xml
lrwxrwxrwx 1 jenkins root 30 Nov 23 16:01 config.xml -> /srv/jenkins/config/config.xml


When I startup the Pod, this link is present but within 10 seconds, Jenkins overwrites this link with an actual file and all my configurations are overwirtten.



So can I tell jenkins to read the config.xml file from somewhere else ?










share|improve this question


















  • 1





    You can use the configuration as code plugin to inject your configuration at run time instead

    – towel
    Nov 26 '18 at 8:38
















0















I am setting up a customized Jenkins. My jenkins home is



echo $JENKINS_HOME
/srv/jenkins


This means that the location of my config.xml file is



$JENKINS_HOME/config.xml
/srv/jenkins/config.xml


But I want Jenkins to read the config.xml file from under



$$JENKINS_HOME/config/config.xml
/srv/jenkins/config/config.xml


You might ask why ? Because since this is a customized Jenkins, Im am deploying the config.xml file on runtime in a Helm chart on Kubernetes and this file will change based on the customization by different teams. And I want this file to persist after Ive done the modification during the InitContainer phase of my pod startup.



One thing I tried was to create a softlink



jenkins@25bea2ece6a9:~$ cd /srv/jenkins/
jenkins@25bea2ece6a9:~$ ls -ltrh | grep config.xml
lrwxrwxrwx 1 jenkins root 30 Nov 23 16:01 config.xml -> /srv/jenkins/config/config.xml


When I startup the Pod, this link is present but within 10 seconds, Jenkins overwrites this link with an actual file and all my configurations are overwirtten.



So can I tell jenkins to read the config.xml file from somewhere else ?










share|improve this question


















  • 1





    You can use the configuration as code plugin to inject your configuration at run time instead

    – towel
    Nov 26 '18 at 8:38














0












0








0








I am setting up a customized Jenkins. My jenkins home is



echo $JENKINS_HOME
/srv/jenkins


This means that the location of my config.xml file is



$JENKINS_HOME/config.xml
/srv/jenkins/config.xml


But I want Jenkins to read the config.xml file from under



$$JENKINS_HOME/config/config.xml
/srv/jenkins/config/config.xml


You might ask why ? Because since this is a customized Jenkins, Im am deploying the config.xml file on runtime in a Helm chart on Kubernetes and this file will change based on the customization by different teams. And I want this file to persist after Ive done the modification during the InitContainer phase of my pod startup.



One thing I tried was to create a softlink



jenkins@25bea2ece6a9:~$ cd /srv/jenkins/
jenkins@25bea2ece6a9:~$ ls -ltrh | grep config.xml
lrwxrwxrwx 1 jenkins root 30 Nov 23 16:01 config.xml -> /srv/jenkins/config/config.xml


When I startup the Pod, this link is present but within 10 seconds, Jenkins overwrites this link with an actual file and all my configurations are overwirtten.



So can I tell jenkins to read the config.xml file from somewhere else ?










share|improve this question














I am setting up a customized Jenkins. My jenkins home is



echo $JENKINS_HOME
/srv/jenkins


This means that the location of my config.xml file is



$JENKINS_HOME/config.xml
/srv/jenkins/config.xml


But I want Jenkins to read the config.xml file from under



$$JENKINS_HOME/config/config.xml
/srv/jenkins/config/config.xml


You might ask why ? Because since this is a customized Jenkins, Im am deploying the config.xml file on runtime in a Helm chart on Kubernetes and this file will change based on the customization by different teams. And I want this file to persist after Ive done the modification during the InitContainer phase of my pod startup.



One thing I tried was to create a softlink



jenkins@25bea2ece6a9:~$ cd /srv/jenkins/
jenkins@25bea2ece6a9:~$ ls -ltrh | grep config.xml
lrwxrwxrwx 1 jenkins root 30 Nov 23 16:01 config.xml -> /srv/jenkins/config/config.xml


When I startup the Pod, this link is present but within 10 seconds, Jenkins overwrites this link with an actual file and all my configurations are overwirtten.



So can I tell jenkins to read the config.xml file from somewhere else ?







jenkins






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 23 '18 at 16:33









Jason StanleyJason Stanley

881931




881931








  • 1





    You can use the configuration as code plugin to inject your configuration at run time instead

    – towel
    Nov 26 '18 at 8:38














  • 1





    You can use the configuration as code plugin to inject your configuration at run time instead

    – towel
    Nov 26 '18 at 8:38








1




1





You can use the configuration as code plugin to inject your configuration at run time instead

– towel
Nov 26 '18 at 8:38





You can use the configuration as code plugin to inject your configuration at run time instead

– towel
Nov 26 '18 at 8:38












1 Answer
1






active

oldest

votes


















1














No, config.xml is hardcoded in source and until you want to recompile Jenkins by yourself this cannot be done. config.xml is written and by jenkins when loaded.



Great people working on Configuration as Code plugin want to bring this philosophy to jenkins but until it's stable (and it's not currently) you have to use init.groovy scripts for automation.



Jenkins currently provides access to it's initialization through groovy hooks (https://wiki.jenkins.io/display/JENKINS/Groovy+Hook+Script)



And what you can do is write init.groovy script which can issue reload on copied config.



You can do that using initialization state:



import hudson.init.InitMilestone

if(Jenkins.instance.getInitLevel() == InitMilestone.COMPLETED){
// copy config.xml
Jenkins.instance.reload()
} else {
// sleep for a while, do some other stuff
}





share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450203%2fchange-jenkins-root-configuration-config-xml-location%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    No, config.xml is hardcoded in source and until you want to recompile Jenkins by yourself this cannot be done. config.xml is written and by jenkins when loaded.



    Great people working on Configuration as Code plugin want to bring this philosophy to jenkins but until it's stable (and it's not currently) you have to use init.groovy scripts for automation.



    Jenkins currently provides access to it's initialization through groovy hooks (https://wiki.jenkins.io/display/JENKINS/Groovy+Hook+Script)



    And what you can do is write init.groovy script which can issue reload on copied config.



    You can do that using initialization state:



    import hudson.init.InitMilestone

    if(Jenkins.instance.getInitLevel() == InitMilestone.COMPLETED){
    // copy config.xml
    Jenkins.instance.reload()
    } else {
    // sleep for a while, do some other stuff
    }





    share|improve this answer




























      1














      No, config.xml is hardcoded in source and until you want to recompile Jenkins by yourself this cannot be done. config.xml is written and by jenkins when loaded.



      Great people working on Configuration as Code plugin want to bring this philosophy to jenkins but until it's stable (and it's not currently) you have to use init.groovy scripts for automation.



      Jenkins currently provides access to it's initialization through groovy hooks (https://wiki.jenkins.io/display/JENKINS/Groovy+Hook+Script)



      And what you can do is write init.groovy script which can issue reload on copied config.



      You can do that using initialization state:



      import hudson.init.InitMilestone

      if(Jenkins.instance.getInitLevel() == InitMilestone.COMPLETED){
      // copy config.xml
      Jenkins.instance.reload()
      } else {
      // sleep for a while, do some other stuff
      }





      share|improve this answer


























        1












        1








        1







        No, config.xml is hardcoded in source and until you want to recompile Jenkins by yourself this cannot be done. config.xml is written and by jenkins when loaded.



        Great people working on Configuration as Code plugin want to bring this philosophy to jenkins but until it's stable (and it's not currently) you have to use init.groovy scripts for automation.



        Jenkins currently provides access to it's initialization through groovy hooks (https://wiki.jenkins.io/display/JENKINS/Groovy+Hook+Script)



        And what you can do is write init.groovy script which can issue reload on copied config.



        You can do that using initialization state:



        import hudson.init.InitMilestone

        if(Jenkins.instance.getInitLevel() == InitMilestone.COMPLETED){
        // copy config.xml
        Jenkins.instance.reload()
        } else {
        // sleep for a while, do some other stuff
        }





        share|improve this answer













        No, config.xml is hardcoded in source and until you want to recompile Jenkins by yourself this cannot be done. config.xml is written and by jenkins when loaded.



        Great people working on Configuration as Code plugin want to bring this philosophy to jenkins but until it's stable (and it's not currently) you have to use init.groovy scripts for automation.



        Jenkins currently provides access to it's initialization through groovy hooks (https://wiki.jenkins.io/display/JENKINS/Groovy+Hook+Script)



        And what you can do is write init.groovy script which can issue reload on copied config.



        You can do that using initialization state:



        import hudson.init.InitMilestone

        if(Jenkins.instance.getInitLevel() == InitMilestone.COMPLETED){
        // copy config.xml
        Jenkins.instance.reload()
        } else {
        // sleep for a while, do some other stuff
        }






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 26 '18 at 11:39









        Dawid GosławskiDawid Gosławski

        1,098822




        1,098822
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450203%2fchange-jenkins-root-configuration-config-xml-location%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Wiesbaden

            Marschland

            Dieringhausen