Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Prevent retesting the same commit (based on hash)

Aaron Hong June 2, 2020

I have tests running on the `default` pipeline, so it runs both on pull request branches and our `master` branch. It's fine most of the time. However, when I fast-forward merge a pull request, the exact same code gets tested twice, once from the pull request and again on `master`. Same thing happens when I create a branch from `master`. I don't want to waste my pipeline minutes. Is there a way to prevent that?

Fast-forward merge scenario

  • #91 My commit message (h4sh) <-- master branch
  • #90 My commit message (h4sh) <-- feature branch

New feature branch scenario

  • #98 My commit message (h4sh) <-- new feature branch
  • #97 My commit message (h4sh) <-- master branch

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, forge, forge learning path, atlassian learning, cloud app development, forge app development, build forge apps, atlassian certification, developer training, jira app development, confluence app development, automation, ui frameworks

Turn Ideas into Atlassian Apps 📱

From setup to deployment—this learning path shows you how to build your first app using Forge. Learn the essentials, streamline workflows, and bring custom solutions to life across Jira, Confluence, and more.

Start Learning
AUG Leaders

Atlassian Community Events