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

Hudson deploy artifact does not use alternate settings.xml

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • maven-plugin
    • None
    • Platform: PC, OS: Linux

    Description

      The Hudson 'Deploy artifacts to Maven repository' does not take the settings.xml
      into account (also see bug #). This means that the local-repository in ~/.m2
      will be used which was not used during the build.

      Attachments

        Issue Links

          Activity

            pleursoft pleursoft created issue -
            pleursoft pleursoft made changes -
            Field Original Value New Value
            Link This issue depends on JENKINS-4938 [ JENKINS-4938 ]
            mdonohue mdonohue made changes -
            Link This issue depends on JENKINS-4693 [ JENKINS-4693 ]
            mdonohue mdonohue made changes -
            Link This issue depends on JENKINS-4938 [ JENKINS-4938 ]
            abayer Andrew Bayer made changes -
            Link This issue is duplicated by JENKINS-5628 [ JENKINS-5628 ]
            scm_issue_link SCM/JIRA link daemon made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            abayer Andrew Bayer made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            ircbot Jenkins IRC Bot made changes -
            Component/s maven-plugin [ 16033 ]
            Component/s maven2 [ 15487 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 135012 ] JNJira + In-Review [ 203207 ]

            People

              Unassigned Unassigned
              pleursoft pleursoft
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: