Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How is the remote agent "sidekick" container specified when using the Per Build Container plugin? Edited

I recently had the PBC plugin installed by our IT department.  The sidekick image has been created via the script and stored in our registry but not sure where it is used/referenced within Bamboo.  

As an end user, I only have access to edit my plans.  I see the addition of the PBC plugin in the isolate build area under the Docker tab and when I select it I see a field to enter a Docker image.  The text above the field states "The build is picked up by an agent specially created for the current run and discarded afterwards. The agent will be based on a Docker Image provided."  This seems to suggest that the sidekick image should go here but the text below the field says "Docker image to use by the build's tasks. It has to provide all capabilities required by tasks." which seems to indicate the custom image I created that contains my build environment.  The Agent Size field also seems to indicate that this field is for the sidekick image.

That being said, I was told that all the builds would "potentially" use the same sidekick image and if that is the case I wouldn't expect to have to configure it for every single job therefore I'm confused as to where the two images are specified and what goes into this Docker image field.  As I understand it there are two containers in the pod with the first one being the sidekick image and the other my build environment image therefore I would expect that if the sidekick image does have to be specified per job (not good as we have lots of jobs) there were be two field for image configuration and not just one.  

Now there is a section for Additional containers to run but my understanding is that would be for a third container in the pod.

It seems to me that there should be a configuration option somewhere (maybe on the server side so I cannot see it) to indicate the location of the sidekick image so that the plan only has to enter the location for the image actually performing the tasks.  Can someone please shed some light at to where the sidekick and my build environment images are referenced?

1 answer

Was able to confirm with those who have access that the PBC sidekick image is specified with the configuration of this plugin.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

179 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you