In preparation for migrating a production Bamboo system from Windows Server 2008 to Linux (Ubuntu) we have set up a test Bamboo system on Linux and imported the backup zip file from the existing Bamboo production system.
We have installed a remote agent on a new Windows Server 2012 machine which appears to successfully register itself with the test Bamboo system on Linux.
I am however uncertain about what steps to take next. All of the current production build plans and history have imported into the test system correctly, but of course all of the jobs that were configured to build .Net applications now fail because they cannot find an agent to run MSBuild etc.
My question therefore is:
Do I need to delete all of the .Net builds on the new test system and re-create them from scratch using the remote agent running on Windows Server 2012 - or - is there a way to 'switch' them from the previous default agent (which no longer has MSBuild capabilities as it is running on Linux) to the remote agent which does have MSBuild capabilities?
You will be required to add the Microsoft capability in Bamboo to the remote agent on Windows Server 2012 machine. Once you do, you need to make sure the Microsoft tasks within the Jobs are referring to this new capability, otherwise, they will still be making reference to the capability from your previous Bamboo instance on Windows Server 2008.
Thank you for your quick response. Your answer put me on the right path. Though I did have to remove all of the capabilities from the default local agent (now Linux) first.
The remote agent appears to have an ability to 'auto detect' capabilities which now display correctly (i.e. I didn't need to add them).
Once the above was complete, jobs then declared
no agent can run this job. I needed to go through each of them to select the respective MSBuild executable from the drop-down list in all MSBuild task(s).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs