• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • packaging
    • None

      The shasum file for the war artifact is always called jenkins.war.sha256 no matter what the name of the actual artifact is. Given that ARTIFACTNAME environment variable is overridable, it can happen that the generated war has a different name so this needs to be taken into account.

          [JENKINS-39819] WAR shasum file name is not correct always

          Code changed in jenkins
          User: Armando Fernandez
          Path:
          Makefile
          setup.mk
          http://jenkins-ci.org/commit/packaging/82e215ee48894b84585abf17017a5b83276baba1
          Log:
          JENKINS-39819 shasum filename was not correct under all circumstances

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Armando Fernandez Path: Makefile setup.mk http://jenkins-ci.org/commit/packaging/82e215ee48894b84585abf17017a5b83276baba1 Log: JENKINS-39819 shasum filename was not correct under all circumstances

          Code changed in jenkins
          User: R. Tyler Croy
          Path:
          Makefile
          setup.mk
          http://jenkins-ci.org/commit/packaging/b9f207f9a6c00b9f4aca2ac8141d52040e0e9e38
          Log:
          Merge pull request #84 from armfergom/JENKINS-39819

          JENKINS-39819 shasum filename was not correct under all circumstances

          Compare: https://github.com/jenkinsci/packaging/compare/26586fc6ef91...b9f207f9a6c0

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: R. Tyler Croy Path: Makefile setup.mk http://jenkins-ci.org/commit/packaging/b9f207f9a6c00b9f4aca2ac8141d52040e0e9e38 Log: Merge pull request #84 from armfergom/ JENKINS-39819 JENKINS-39819 shasum filename was not correct under all circumstances Compare: https://github.com/jenkinsci/packaging/compare/26586fc6ef91...b9f207f9a6c0

          Reopened as I missed the file extension when generating the war shasum file. This PR should fix it.

          Armando Fernandez added a comment - Reopened as I missed the file extension when generating the war shasum file. This PR should fix it.

          Code changed in jenkins
          User: Armando Fernandez
          Path:
          Makefile
          setup.mk
          http://jenkins-ci.org/commit/packaging/03c4cd2fe531b810cbf6c220e99653d79248596d
          Log:
          JENKINS-39819 Missed extension for WAR shasum file

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Armando Fernandez Path: Makefile setup.mk http://jenkins-ci.org/commit/packaging/03c4cd2fe531b810cbf6c220e99653d79248596d Log: JENKINS-39819 Missed extension for WAR shasum file

          Code changed in jenkins
          User: R. Tyler Croy
          Path:
          Makefile
          setup.mk
          http://jenkins-ci.org/commit/packaging/f25a3f6ff7528c6b81d98ff29884eaf4d70fee12
          Log:
          Merge pull request #85 from armfergom/JENKINS-39819-fix

          JENKINS-39819 Missed extension for WAR shasum file

          Compare: https://github.com/jenkinsci/packaging/compare/b9f207f9a6c0...f25a3f6ff752

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: R. Tyler Croy Path: Makefile setup.mk http://jenkins-ci.org/commit/packaging/f25a3f6ff7528c6b81d98ff29884eaf4d70fee12 Log: Merge pull request #85 from armfergom/ JENKINS-39819 -fix JENKINS-39819 Missed extension for WAR shasum file Compare: https://github.com/jenkinsci/packaging/compare/b9f207f9a6c0...f25a3f6ff752

            armfergom Armando Fernandez
            armfergom Armando Fernandez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: