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

Bamboo Specs - YAML - Capability to skip/disable checkout for a job

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Bamboo Specs
    • None
    • 2

    • 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.

      Raised from YAML - How to define a JOB that does not pull down source code?

      Currently there is no way to stop a job from checking out source code.
      This is a problem when trying to define multi stage plans. Multi stage plans typically checkout in stage one and for subsequent stages depend on output/artefacts thus do not need to checkout source again.

      eg.

          Form Name

            [BAM-20709] Bamboo Specs - YAML - Capability to skip/disable checkout for a job

            m added a comment - - edited

            It does not make sense to implicitly add source code checkout at each stage.

            It should be classified as a bug rather than suggestion.

            m added a comment - - edited It does not make sense to implicitly add source code checkout at each stage. It should be classified as a bug rather than suggestion.

            Cyril Labbe added a comment -

            Another workaround:

            1. host an empty git repository,
            2. set it as a "linked repository" in bamboo
            3. in your yaml bamboo specs, add a checkout task that explicitly fetches the empty linked repository

            it will save you the bandwidth & time, but it's still checking out something

            Cyril Labbe added a comment - Another workaround: host an empty git repository, set it as a "linked repository" in bamboo in your yaml bamboo specs, add a checkout task that explicitly fetches the empty linked repository it will save you the bandwidth & time, but it's still checking out something

            Aron Weiler added a comment -

            Just as a workaround, you can put this into your bamboo yaml script, if you're using bamboo-specs.  There's probably a way to do this from the UI, as well.

             

              ## Prevent the job from checking out source code, since bamboo implicitly adds a checkout (rolleyes)     
  - checkout:       
      conditions:
      - variable:
          exists: fake.var

             

            Aron Weiler added a comment - Just as a workaround, you can put this into your bamboo yaml script, if you're using bamboo-specs.  There's probably a way to do this from the UI, as well.   ## Prevent the job from checking out source code, since bamboo implicitly adds a checkout (rolleyes)        - checkout:              conditions:       - variable:           exists: fake. var  

            Simon Hooper added a comment -

            eg:

            I have a multi stage pipeline set up in YAML as follows working well.

            • Stage 1
              • checkout source and build
            • Stage 2
              • Run tests for proj A
              • Run tests for proj B
              • Run test for proj n ...

            Simon Hooper added a comment - eg: I have a multi stage pipeline set up in YAML as follows working well. Stage 1 checkout source and build Stage 2 Run tests for proj A Run tests for proj B Run test for proj n ...

              Unassigned Unassigned
              f1fe56b83fed Simon Hooper
              Votes:
              25 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: