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,556,582
Community Members
 
Community Events
184
Community Groups

How do I add git capability to agent for Per Build Container builds?

We are working to get our Bamboo builds running in a K8s cluster.  We have the PBC plugins installed and configured, sidekick image created and our test plan seemS to be running OK (within OpenShift) but when the Source Code Checkout task executes, getting our source code from Bitbucket, I see the message "Submodules handling requested but no native Git capability defined for agent. Please define native Git capability for agent to use submodules." in the log file.

I've created a new sidekick image adding:

/buildeng/bamboo-update-capability "system.builder.command.Git" "/usr/bin/git"

to the file setup.sh and added:

Add setup.sh /buildeng-custom/

to the Dockerfile

I then ran the container locally via docker run and verified that the file and contents were there and in the correct location.

docker run --rm -it bamboo-agent-sidekick
# cat buildeng-custom/setup.sh
# GIT capability
/buildeng/bamboo-update-capability "system.builder.command.Git" "/usr/bin/git"

When I re-run the job I'm still getting the same error.

Can someone tell me how configure the system this so that I can do submodule updates?

Thanks






 

2 answers

1 accepted

2 votes
Answer accepted
Duke
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 02, 2020

I am not sure about "system.builder.command.Git". Have you tried "system.git.executable"?

/buildeng/bamboo-update-capability "system.git.executable" "/usr/bin/git"

See Submodules handling requested but no native Git capability defined for agent. Please define native Git capability for agent to use submodules for more details.

Thanks.  That seemed to get one step further.  Now getting "Permission denied (publickey)".  We are using linked libraries and I have tried saving the repository configuration to refresh the authentication details multiple times as well as putting the access key into Bitbucket manually without avail.

Any thoughts?

Duke
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 02, 2020

It's great that "system.git.executable" got you one step further. Now it looks like you hit the issue discussed in BAM-11369. I suggest trying the workaround in Permission denied (publickey) submodule after upgrade.

Can you please share your Helm chart? We may suggest for you some cloud-native recommendations (using initContainers, configmap,... instead of building image on top of the official image, ... so on) ?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events