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

"WAR/EAR files" filepath gets truncated to filename after build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • wildfly-deployer-plugin
    • None

      My build configuration creates a war artifact in a subdirectory of the workspace root. As the description says (A single WAR or EAR file to deploy, packaged with the appropriate bindings (if applicable). Relative to the workspace root.), I enter a relative path (in my case: mcmod-server/build/libs/missioncontrol.war).

      When I run a build, everything is fine. When I run it again, it failes, because Jenkins says "missioncontrol.war cannot be found" and that's correct, since it's in a subdirectory.

      So I set the filepath again and successfully run the build. When I have a look at the configuration after the build, the filepath has been truncated to the filename. I can reproduce that after each build.

          [JENKINS-33065] "WAR/EAR files" filepath gets truncated to filename after build

          Todd Brady added a comment -

          We are also having this issue. Our ear/war files are in directory build/FILE.ear

          So we put 'build/filename1.ear' in the configuration.

          Occasionally the input field is then set to 'filename1.ear' and our next build fails.

          Todd Brady added a comment - We are also having this issue. Our ear/war files are in directory build/FILE.ear So we put 'build/filename1.ear' in the configuration. Occasionally the input field is then set to 'filename1.ear' and our next build fails.

          Philipp Renoth added a comment -

          One possible workaround is to start a bash command before to move the war/ear file to root and deploy it then without a path.

          Philipp Renoth added a comment - One possible workaround is to start a bash command before to move the war/ear file to root and deploy it then without a path.

          Todd Brady added a comment -

          I have submitted a pull request for review for this issue:
          https://github.com/jenkinsci/wildfly-deployer-plugin/pull/1

          Todd Brady added a comment - I have submitted a pull request for review for this issue: https://github.com/jenkinsci/wildfly-deployer-plugin/pull/1

            ddilling Dan Dillingham
            aitch Philipp Renoth
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: