Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

Execute hourly job only when there are commits

Hi,

I have an hourly pipeline job. Currently it runs every hour even when no checkin has been made. Is it possible for the hourly job to be executed only when a change has been checked in ? I tried the condition -> changesets -> includePaths & it didn't help.

Here's the snippet of my bitbucket-pipelines.yml.

  • The hourly job uses the custom:scheduled
  • The custom:default is for on-demand builds.

 

definitions:
steps:
- step: &build
max-time: 30 # set a 30 minute timeout
name: Build & Test
size: 2x
caches:
- gradle

script:
- utils/build-scripts/setup-image.sh
- BASH_ENV=utils/build-scripts/bashrc bash ./gradlew -no-daemon dist
- utils/build-scripts/upload-distribution.sh


pipelines:
custom:
default: # runs even with no change
- step: *build

scheduled: # runs this only on a schedule & only if there are changes
- step: *build
condition:
changesets:
includePaths:
# run only when any changes found
- "**"

 

Thanks! 

1 answer

1 accepted

0 votes
Answer accepted
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 22, 2023

Hi Sathya!

I'm afraid that this is not possible at the moment. The condition -> changesets -> includePaths is not going to work, because what it does is check if the commit that the build is running for has changes in the files you specified. It won't check for changes since the last build.

We have an open feature request for what you are asking:

Please make sure to add your vote (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features.

You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates. Implementation of new features is done as per our policy here and any updates will be posted in the feature request.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events