Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7495

Make POM parser aware of alternate settings.xml

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Hudson ver. 1.376

      POM parser currently doesn't make use of alternate settings.xml provided to Maven build via -s parameter within "Build --> Goals and options". Please implement support for this. Without this feature and with JENKINS-4693 not fixed, it is not possible at the moment to provide Maven build in Hudson with build job/project specific alternate settings.xml file.

      See this Hudson users mailinglist topic for more info.

          [JENKINS-7495] Make POM parser aware of alternate settings.xml

          Andrew Bayer added a comment -

          I think the answer here is for me to finally get JENKINS-4693 fixed - given that we have a way to specify an alternate settings location, I'd rather not also have to parse it out of the goals string. Let me see what I can do with the underlying problem.

          Andrew Bayer added a comment - I think the answer here is for me to finally get JENKINS-4693 fixed - given that we have a way to specify an alternate settings location, I'd rather not also have to parse it out of the goals string. Let me see what I can do with the underlying problem.

          Stevo Slavić added a comment -

          I agree, once JENKINS-4693 is fixed, this one can be closed.

          Stevo Slavić added a comment - I agree, once JENKINS-4693 is fixed, this one can be closed.

          Yves DM added a comment -

          To use an alternate settings file, you should use this plugin : https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin
          Maybe jankins should reject the -s option to say it is not supported.

          Yves DM added a comment - To use an alternate settings file, you should use this plugin : https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin Maybe jankins should reject the -s option to say it is not supported.

          Stevo Slavić added a comment -

          @Yves
          That plugin states it supports "Ability to provide configuration files (e.g. settings.xml for maven, XML, groovy, custom files,...) loaded trough the UI which will be copy to the job workspace", and that it works in a way that "It will prevents you to copy various similar configuration files to all your nodes. And the capability to edit those files trough the Jenkins UI !"

          This is not a solution for case where alternate settings.xml is already provided in project sources, and each project has its own very project specific alternate settings.xml file.

          Stevo Slavić added a comment - @Yves That plugin states it supports "Ability to provide configuration files (e.g. settings.xml for maven, XML, groovy, custom files,...) loaded trough the UI which will be copy to the job workspace", and that it works in a way that "It will prevents you to copy various similar configuration files to all your nodes. And the capability to edit those files trough the Jenkins UI !" This is not a solution for case where alternate settings.xml is already provided in project sources, and each project has its own very project specific alternate settings.xml file.

            Unassigned Unassigned
            sslavic Stevo Slavić
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: