I recently noticed that Bamboo now has deployment plans for deploying build artefacts. I had already implemented deployment as another stage in my build plan, so I thought I would try my hand at making a deployment plan.
My deployment plan is a very simple windows script that remotely installs an msi on a target machine.
But guess what?
Deployment plans (unlike build plans) have no means to specify any necessary requirements of the bamboo agents that will run the plan. In this case, it is a windows script and NEEDS TO RUN ON A WINDOWS BAMBOO AGENT!
So my deployment plan runs on any available agent, including linux agents, where it fails completely.
Deployment plans are useless if you have both windows and linux build agents. You can dedicate an agent to deployment, but then you can't use it to build anymore.
Massive fail, Atlassian!
I found a workaround: include a MSBUILD job in your deployment plan, which will force it to run only on windows machines. For the solution file, choose any random name and pass /help as argument to msbuild, which prevents it from trying to open the bogus solution file.
No comments:
Post a Comment