There is currently no ability to restrict jobs which are able to run on the same agent from potentially interacting with each other. There are a bunch of feature requests asking for this sort of granularity, but if I understand your question correctly the most fitting request would be this one BAM-2504 Jira Ticket
It's a huge gap in the product line, the ...
IMHO if your successful build doesn't push to an artifact repository, there's a problem in your pipeline.
Jenkins or Bamboo do not aim at keeping built artifacts forever and they don't give you any versioning delivery, as such that's a point of failure in your delivery system.
I'd advise to review your method to use an artifact repository and that will ...
I've created the jenkins-remote-builder script which will follow your remote build to completion.
Some more details about it (from its README.md):
It is convenient to use Environment Variables to provide runtime configuration for such scripts. Especially when it contains secrets that you don't want to hold in any persistent storage or in version control.
When you do actually have secrets, it is even better to use some kind of secret management system that will provide these secrets on request. One ...
I think you have fundamentally misunderstood the relationship between plans, stages and jobs in bamboo.
A good rule of thumb is to have a single repository of code, which is linked to a single build plan, which produces a single independent module.
You may initially start out creating a single stage with a single job inside each single plan where you just ...
Using task schedulers like Bamboo or Airflow have a lot of advantages over cron, particularly in their ability to recognize errors and process dependent tasks accordingly. By far the most common reason not to use them is that you simply haven't set up the infrastructure yet: some form of cron is installed on every Linux machine, and it's easy to add a new ...
Atlassian Labs have now provided this functionality as an add-on: https://marketplace.atlassian.com/apps/1219706/conditional-tasks-for-bamboo?hosting=server&tab=overview
Only available for versions 6.7.1+
I don't know if there is some GUI way to do this
I am triggering the same plan in different ways from a REST request by using a variable
To do this
define a variable in the plan configuration variables ie myvariable
in the REST request set bamboo.variable.myvariable to the value required ie "1" or "2"
in the plan stage add a task of script and use the ...
I don't think Bamboo has that natively but there are plugins such as this one: (https://marketplace.atlassian.com/plugins/com.cobalt.cdpipeline.cdpipeline/server/overview).
Atlassian also has a different product called Bitbucket pipeline (https://bitbucket.org/product/features/pipelines) that may be more similar to what you want but it's more of a ...
Stages group jobs inside plans. So technically they are cloned when the respective plans are cloned.
Which means that missing the ability to clone a specific stage should be just a UX/usability/functionality issue, not a conceptual one.
There might be a non-trivial implementation details when cloning stages - they may carry inside stage sequencing ...
There is an improvement issue open for, I think, exactly what you're looking for: Bamboo should be able to group projects:
I'm mulling over redoing our project heirarchy and grouping things a
little more logically, and realize that being able to group projects
in Bamboo would be brilliant. It's already stellar that each project
Yes, you are correct. Bamboo will spawn the build containers on the agent that the build is running on (either Local, Remote, or, Elastic - depending on your configuration).
In order for this to work the agent will require Docker to be installed and running.
Bamboo doesn't have a color status like Jenkins per say, but it does have a very similar build status indicated by a circle with a symbol within it. This status is available for both the entire build plan and for an individual build.
For your GET request, you will want to use the same api calls that you are using to get the buildstate value to get a ...
In your deployment project configuration for each environment you could add a task prior to the actual deployment which would take care of setting up the right configuration file.
It could be a script simply copying/replacing the configuration file just as you currently do manually. The script could be invoked with some pre-configured argument to identify ...
Possible reasons for using cron over jenkins
I am assuming you mean cron on a Linux system and not a Kubernetes CronJob Controller (https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/)
1) User permissions. Although you can work around this with Jenkins, it is possibly easier to run commands as arbitary users in cron
2) Provisioning of ...
In case someone else finds this question, I thought I'd mention Favorites. You can mark certain jobs as favorites, and then have those jobs appear on your "My Bamboo"-page.
That's obviously just one group, but still it might help.
I don't know the inner of bamboo, but I assume it works like a bash script.
What happens is that variables are replaced before execution, in bash that would be echo "echo $VAR" > test.sh and test.sh will only contain "echo" because VAR is replaced by it's value before the command is executed.
If you want test.sh to contain echo $VAR you have to tell bash ...
If you need to trigger a job from CLI and wait for its completion you can use "Jenkins CLI" (see here).
However jenkins CLI does not support promotions so for them I came up with the following script:
# Trigger a promotion and wait for its completion
# For triggering jobs jenkins cli is sufficient: https://support.cloudbees.com/hc/en-us/...