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

Promoted builds now clean workspace before running.

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • promoted-builds-plugin
    • None
    • Jenkins 1.639
      Promoted Builds Plugin 2.24

      In 2.23.1, and as far back as I can think, the workspace was never cleaned during a promotion. Starting with 2.24, when a promotion is run, it looks like it does the subversion clean before running the promotion scripts.

          [JENKINS-31901] Promoted builds now clean workspace before running.

          Jay Beeckman created issue -

          I have the same problem, I keep getting the following errors in my promotions because the Artifacts folder I create gets deleted when the promotion is launched.

          Promoting Some-Job-Name #319
          [parameterized-trigger] Properties file Artifacts\job-properties.properties did not exist.
          Not triggering due to missing file - did you archive it as a build artifact ?
          

          Dominic St-Jacques added a comment - I have the same problem, I keep getting the following errors in my promotions because the Artifacts folder I create gets deleted when the promotion is launched. Promoting Some-Job-Name #319 [parameterized-trigger] Properties file Artifacts\job-properties.properties did not exist. Not triggering due to missing file - did you archive it as a build artifact ?

          Will Saxon added a comment -

          Does the parent job define a clean step?

          https://github.com/jenkinsci/promoted-builds-plugin/pull/73 makes the parent job's SCM environment available to the promotion process. This has had some unplanned side effects, e.g. JENKINS-32006.

          Will Saxon added a comment - Does the parent job define a clean step? https://github.com/jenkinsci/promoted-builds-plugin/pull/73 makes the parent job's SCM environment available to the promotion process. This has had some unplanned side effects, e.g. JENKINS-32006 .

          Sorry for the delay in my response.. Yes, the parent (I assume you mean the step that declares the promotion trigger) does a git checkout with the "Clean before checkout" option (and the shallow clone option as well)...

          Dominic St-Jacques added a comment - Sorry for the delay in my response.. Yes, the parent (I assume you mean the step that declares the promotion trigger) does a git checkout with the "Clean before checkout" option (and the shallow clone option as well)...
          Oleg Nenashev made changes -
          Link New: This issue duplicates JENKINS-32006 [ JENKINS-32006 ]

          Oleg Nenashev added a comment -

          Should be fixed in 2.24.1

          Oleg Nenashev added a comment - Should be fixed in 2.24.1
          Oleg Nenashev made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 167369 ] New: JNJira + In-Review [ 198172 ]

            oleg_nenashev Oleg Nenashev
            gsxjay Jay Beeckman
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: