| Section | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
General FAQ
How do I set up Tasks for AWS?
Please refer to the Installation and Upgrade Guide.
Which Bamboo versions are currently supported by Tasks for AWS?
Please refer to the Compatibility Notes for details.
Support FAQ
What is the relation to the Bamboo AWS Plugin?
Tasks for AWS 2.0 is the commercially supported successor of the deprecated Bamboo AWS Plugin 1.x (which will remain available in maintenance mode only, see below) - this transition enables us to sustain our established support level and add new features and improvements more frequently going forward (we have scheduled several new tasks for the upcoming months, e.g. support for Amazon S3 is already available as of Tasks for AWS 2.1).
Will the Bamboo AWS Plugin remain available?
While deprecated, the Bamboo AWS Plugin is an Open-source software (OSS) offering and will remain available as such. However, we are switching it to maintenance mode, which means we are going to fix critical issues, but are not going to add significant features and improvements and focus on Tasks for AWS instead - please get in touch if you have any questions or suggestions about this transition.
How can I migrate from the Bamboo AWS Plugin to Tasks for AWS?
Given the most common use cases for both add-ons are deployment scenarios, we've added support for the new Bamboo 5 Deployment Projects in Tasks for AWS. In order to use this, tasks would need to be recreated in a Deployment Project anyway, so we've decided to prioritize improving the add-on rather than providing a migration option right away. However, so you can use both add-ons side by side and mix and match tasks from each within a job as long as both remain compatible with the Bamboo version in use (we've added support for regular Bamboo 5.x build projects to the Bamboo AWS Plugin for this reason, but will likely not update it indefinitely for future Bamboo versions).
- Providing a migration option is not out of the question, but a disproportionate amount of work for us right now - please get in touch, if your use case requires a migration option regardless, we are willing to discuss this on a case by case basis.
Licensing & Purchasing
Do my Bamboo and Tasks for AWS licenses have to match?
Yes, this is a limitation imposed by the Atlassian Marketplace, see the Marketplace Licensing and Pricing FAQ:
Which license do I choose when purchasing an add-on?:
The Atlassian host application (for example, JIRA, Confluence, etc.) license tier determines the license type you need for an add-on that is paid-via-Atlassian. For example, if you are installing an add-on into a JIRA with 25-user license, you must purchase a 25-user license for the add-on, even if fewer users will actually use it.
IMPORTANT: If you do not purchase a license that matches your Atlassian application license, your add-on will not work.
| Info |
|---|
| Obviously there are many valid use cases where this limitation doesn't make sense. Accordingly, many customers and vendors have requested the ability to decouple the add-on user tier from the host application - please contact Atlassian directly for any questions in this regard, maybe they will reconsider this over time. |
...
|
Support
| Questionslist macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Compatibility
| Questionslist macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Security
| Questionslist macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Licensing & Purchasing
| Questionslist macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|