Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-13370

For pipelines, as a user I want to be able to include/exclude files that trigger the build

XMLWordPrintable

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

      As of now all files trigger the build. It would be great to be able to trigger the build only when a specific file changes, or exclude files from triggering the build. For example, when project.json changes do not trigger a build. This can be useful when keeping npmjs up to date with the latest version and the project.json file needs its version saved within source control (which would then trigger another build).

            [BCLOUD-13370] For pipelines, as a user I want to be able to include/exclude files that trigger the build

            Hari Sekhon added a comment -

            +1

            Hari Sekhon added a comment - +1

            Aneita added a comment -

            This request is being tracked on https://jira.atlassian.com/browse/BCLOUD-16560.

            Aneita added a comment - This request is being tracked on  https://jira.atlassian.com/browse/BCLOUD-16560 .

            Joel Skrepnek added a comment -

            This is a crucial requirement for monorepository scenarios.

            Joel Skrepnek added a comment - This is a crucial requirement for monorepository scenarios.

            Thomas Turrell-Croft added a comment -

            Atlasssian have made it possible to ignore commits. I'm guessing that might help you.

            See Issue BCLOUD-13004

            Thomas Turrell-Croft added a comment - Atlasssian have made it possible to ignore commits. I'm guessing that might help you. See Issue BCLOUD-13004

            Matt Filion added a comment -

            Thomas, branching could very well solve it but comes with a lot of overhead that we cannot afford to take on. Having the ability to exclude or include files that trigger the pipeline will provide a very graceful solution with no overhead.

            Matt Filion added a comment - Thomas, branching could very well solve it but comes with a lot of overhead that we cannot afford to take on. Having the ability to exclude or include files that trigger the pipeline will provide a very graceful solution with no overhead.

            Tom Bradshaw (Inactive) added a comment -

            Hi Matt,

            It sounds like you're trying to avoid your build and deployment cycle getting stuck in an infinite loop. While there is not currently a way to specify individual file triggers branch triggers may be able to alleviate some of your problems. Depending on the way your release tool is configured it's also possible to implement a system where you have a release branch and a master branch. All branches should branch off master and be merged back into release. The release branch should then run the tests, deploy and push the newly versioned project.json to the master branch instead of the release branch.

            Tom Bradshaw (Inactive) added a comment - Hi Matt, It sounds like you're trying to avoid your build and deployment cycle getting stuck in an infinite loop. While there is not currently a way to specify individual file triggers branch triggers may be able to alleviate some of your problems. Depending on the way your release tool is configured it's also possible to implement a system where you have a release branch and a master branch. All branches should branch off master and be merged back into release. The release branch should then run the tests, deploy and push the newly versioned project.json to the master branch instead of the release branch.

              Unassigned Unassigned
              ae18f276f46e Matt Filion
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: