Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,466
Community Members
 
Community Events
175
Community Groups

Condition: Check for other repo if there is changes/no-changes in that repo pipeline skip/no-skip?

Use Case:
If there is a change in Repository A (Which is outside the workspace) 

atlassian/trigger-pipeline:5.0.0 will trigger pipeline in the Repository B

  • We have a project outside our workspace in that project's bitbucket-pipelines.yml file there is a step that triggers the pipeline in Repository B. (Working Perfectly Fine)

  • There is a condition in Repository B that if there is no change in these paths below:

    condition:

                changesets:

                    includePaths:

                        # Any changes in Cypress Directories

                        - cypress/fixtures/**

                        - cypress/integration/**

                        - cypress/plugins/**

                        - cypress/support/**

    pipeline gets stopped automatically. (Working Perfectly Fine)

     

The main Question starts here:

We want to bring a functionality in the condition that if there is no-change in Repository A's specified paths. As the condition is in Repository B's pipeline, Repository B's pipeline gets stopped
So basically our condition will be checking for two kinds of conditions either Repository A and B both has changes in specified path or not. If one of the two conditions get true pipeline should complete its steps, if it gets false pipeline should stop.

 

1 answer

0 votes

Hi @Abdul Rehman,

I'm afraid that the following is not possible by using condition and changesets in the bitbucket-pipelines.yml file:

If one of the two conditions get true pipeline should complete its steps

 

If you include a condition in Repository A and that condition is false, then the step in repo A will not run at all, and therefore the pipeline in Repository B is not going to get triggered in order to check if the condition in repo B is true.

 

If you want to check whether one of the conditions is true in order to trigger the pipeline in repo B, you could do this with some scripting and without using the condition and changesets in your yml file:

  • Create a script that checks if there are changes in certain files and/or paths in the HEAD of a repo
  • In the pipeline of repo A:
    • run this script for the HEAD of repo A (check 1)
    • clone repo B and run the script for repo B (check 2)
  • If both check 1 and check 2 are false, you can fail the build in repo A
  • Otherwise, trigger the pipeline in repo B

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events