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

Manual triggered pipeline on self-hosted not starting

Eric Christensen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 13, 2023

Hi,

When running a manually triggered pipeline running on a self-hosted runner it get stopped because of build minutes.

The automatically triggered ones works but not manual.
Did some searching on the community forum and found a similar post from ~1 year ago with a closed bug report

https://jira.atlassian.com/browse/BCLOUD-21780

Am I missing how to get around the issue or is the bug introduced again?

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.
Oct 16, 2023

Hi Eric and welcome to the community!

I tried to reproduce this issue with a workspace on the free plan that is out of build minutes, but I haven't been able to. Both automatically triggered and manual pipelines run on a self-hosted runner.

If you are using one self-hosted runner, and a build is already running, then the build that is triggered next will start as soon as the build currently running is finished.

  • Does the pipeline you are triggering manually have the following in all of its steps?
    runs-on:
      - self.hosted
      - macos # this could be linux, linux.shell or windows, depending on the runner
  • Are you perhaps triggering the pipeline for an older commit or for a branch that does not have the above runs-on definition?

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