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,467,272
Community Members
 
Community Events
177
Community Groups

bitbucket pipeline runners

I am trying to setup runners for out bitbucket pipelines for our pipelines and happen to read documentation which lead me to these 2 questions

  • Could not understand the difference between

https://support.atlassian.com/bitbucket-cloud/docs/adding-a-new-runner-in-bitbucket/ 

and 

https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-runners-for-linux/

 

 

 

1 answer

0 votes
Mark C Atlassian Team Mar 31, 2022

Hi @Srikanth Mamidala

Thank you for reaching out to the community.
Unfortunately, it is not highlighted in our documentation that you can run runners in the background through the Docker command.
However, it is possible to run runners in the background.

For the runners Docker command, you can add the -d flag and that will run the Docker container in a detached mode.
Sample runners Docker command:

docker container run -it -d -v /tmp:/tmp ........

After that, you should be able to run other commands on your server.

Now, if you'd like to monitor the runners container logs, you can use the below command:

docker logs <Runners container ID here> -f

To get the runners container ID, you can run docker container ls

I'll make sure to raise this to our documentation team and add it as an FAQ.

Meanwhile, do let me know how it goes.

Regards,
Mark C

Mark C Atlassian Team Apr 03, 2022

Hi @Srikanth Mamidala

For the documentation here - Adding a new runner in Bitbucket

It is a guide on how you can set up Runners either in your specific repository or in a workspace level setting. When you add Runners in a workspace level, it can be used across your repositories whereas adding Runners in a specific repository will only make the runner available in that specific repository.

For the documentation here - Set up runners for Linux

It is a guide on how you can specifically set up Runners for the Linux environment and it also includes some optional best practices that you can implement in your self-hosted machine.

Let me know if you have further questions that I can help with.

Regards,
Mark C

Hi Mark thanks for explaining. I’m sorry I may not have communicated my question well. So first documentation has a Linux runner setup as well which is different from 2nd document. I am confused over which runner setup is correct for Linux machines. 

Mark C Atlassian Team Apr 04, 2022

Hi @Srikanth Mamidala

The first documentation is actually intended to be done on Bitbucket UI where you'll need to specify from which environment you'd like to run a Runner (e.g. Linux or Windows). This will also generate a Docker command where you'll need to copy and paste it into your chosen environment later on.

An example Docker command would be:

docker container run -it -d -v /tmp:/tmp ........

Whereas for second documentation, it is a guide for setting up your actual Linux environment (server) where you will run the Docker command above. 

In summary:

Hope it helps and let me know if you have further questions.

Regards,
Mark C

So both documentation have to be done for security for the Linux runner setup ? 

Mark C Atlassian Team Apr 04, 2022

Hi @Srikanth Mamidala

The first documentation is required while the second documentation is optional.

Regards,
Mark C

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events