Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-15075

Clean build folder before artifact dependency is prepared (ie, job start)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Handled by Support
    • None
    • None
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      I have a manual stage in a build plan that uses artifacts from a previous stage.

      The artifacts are defined using wildcards because the plan would not know the actual filenames without previous computation (or being able to set build variables, and passing them through the stages). (Also it's possible for the build to produce one or more files)

      When the stage runs there is leftover files from previous builds and this is screwing with the build.

      I don't want to clean the working directory after the build in case a problem occurs and I need to fix things manually.

      A script task that cleans the working directory runs after the artifacts have been prepared. So does any commands using the prepost-build-command plugin.

      I can perform an unwarranted checkout of the build repository and use it to force a clean build, however I'm not certain how it would work in the case where there is a conflict between repository and artifact files. Nor do I want to maintain an empty repository just to get a "clean" build working.

      Is it possible to get a companion "Clean working directory" BEFORE build miscellaneous job option?

              Unassigned Unassigned
              982a92dd04b2 Gary Kennedy
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: