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,456,900
Community Members
 
Community Events
176
Community Groups

Remote Agent gitv2 not available

While Remote Windows Agents is started, it logs lots of plugin errors. Then remote agent is registered to the server without enabling some plugins. At this point I trigger a manual plan and it gets following error even Git is configured on the remote machine: 

 

The build has failed to check out the source code: Plugin
com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-git:gitv2 not available

 

Do you have any about what is wrong with my configuration?

1 answer

1 accepted

0 votes
Answer accepted

 Hi Melih,

  • Are you sure the JAVA_HOME environment variable is pointing to a valid JDK 1.8 installation?
  • Are you sure the user you're using to start the agent have read/write permissions on the bamboo-agent-home folder?
  • Have tried to remove the bamboo-agent-home folder and reinstall the agent from scratch?
  • Is there any other error messages in the bamboo-agent-home/logs/atlassian-bamboo-agent.log file?

thanks

Hi Gabriel, 

Thank you for your answer.

I just deleted all the plugin and cache folders and the problem somehow resolved. 

It does no make sense but anyway it is working properly now. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events