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

Artifactory plugin is configured to run post-build, but actually runs pre-"Post-Steps"

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • Jenkins 1.545, Artifactory plugin 2.2.1, Maven integration plugin 2.1

      Even though Artifactory plugin is in post-build, artifact deployment happens before post-steps (and it visually appears to actually be running as part of the main build step). So deployment happens regardless of whether a post-step fails or not, which appears to be broken behavior.

      the Artifactory plugin should respect the order of go, and not run out of sequence.

          [JENKINS-21235] Artifactory plugin is configured to run post-build, but actually runs pre-"Post-Steps"

          Same here: Jenkins LTS 1.532.3, Artifactory Plugin 2.2.1, Debian GNU/Linux 7, JRE1.7.0_55

          Tim-Christian Bloss added a comment - Same here: Jenkins LTS 1.532.3, Artifactory Plugin 2.2.1, Debian GNU/Linux 7, JRE1.7.0_55

          jlpinardon added a comment -

          This is still the case with 1.554.2.2 jenkins version with maven_integration 2.3 and artifactory 2.2.3.
          Really annoying because we would like to also store within artifactory interesting files generated outside maven during the post step.

          jlpinardon added a comment - This is still the case with 1.554.2.2 jenkins version with maven_integration 2.3 and artifactory 2.2.3. Really annoying because we would like to also store within artifactory interesting files generated outside maven during the post step.

          Same behavior for me. the artifactory deploy is done before the post build actions, while it should be executed after the post build actions.

          Jenkins 1.627 - Artifactory plugin 2.3.2-SNAPSHOT - Red hat 6 - JRE1.7.0_40.

          Will this issue be solved by the Jenkins team or by the jfrog team ?
          I mean : if i want this problem to be resolved, do I have to wait for this issue to be fixed, or do I have to create a new issue on the Jira from JFrog ?

          Thx

          Olivier Lambert added a comment - Same behavior for me. the artifactory deploy is done before the post build actions, while it should be executed after the post build actions. Jenkins 1.627 - Artifactory plugin 2.3.2-SNAPSHOT - Red hat 6 - JRE1.7.0_40. Will this issue be solved by the Jenkins team or by the jfrog team ? I mean : if i want this problem to be resolved, do I have to wait for this issue to be fixed, or do I have to create a new issue on the Jira from JFrog ? Thx

            eyalbe Eyal Ben Moshe
            rvanoo Rob van Oostrum
            Votes:
            6 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: