You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I want to test the import of a primary bamboo server instance's data.
However, I do NOT want all the plans to start checking and building on restart of the test instance.
Is there a config file setting that I can set to affect a PAUSE as it were before starting up the BAMBOO windows service after a successful IMPORT?
I could do a BULK PLAN disable before exporting, but in cases where some plans are already disabled, this is not a good methology, as it requires saving the state of all plans so one can accurately set them all back correctly after the IMPORT.
I could try to PAUSE the test server via REST API immediately after starting up the test instance but I'm not sure this guarantees that no plans would get started during that window of time during startup.
You can achieve this via the BUILDING_DISABLED system property (usually by passing -Datlassian.bamboo.build.disable=true at startup):
Disable triggering plans globally in Bamboo. Plan can be started manually only.
Please note that this only works as expected for Bamboo >= 6.3.1, see the following issue for details:
It's looking like for a windows' service it could only be the bamboo\bin\service.bat file.
One would modify the --JvmOptions string as appropriate and de-install/re-install the service. Kinda belabored for just that one change...
So I guess the the "properties" interface way IS actually simpler (with a service stop/start) thrown in too ...( :-)
Agreed - it's kinda weird that the only alternative option seems to be the service startup wrapper itself (also on Linux), but that's were we stand apparently.