Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This page describes known issues as well as changes you should be aware of before deciding whether or not to upgrade to Identity Federation for AWS 2.12.

Consider testing of app upgrades before rollout into critical production environments

As always, best practices suggest to test each app upgrade in a staging environment before rolling it out to critical production environments.

On this page:

Related pages:

Bamboo

Potential upgrade issue on remote agents

Bamboo might be unable to upgrade apps on running remote/elastic agents:

(warning) This long standing upstream issue had been resolved as of Bamboo 5.3. However, there seems to be a regression in Bamboo versions 5.6+, which expose a similar defect.

(info) In case you are affected, this can usually be remedied by restarting the Bamboo server or disabling/reenabling the remote agent.

Please refer to our KB article Unable to execute task due to plugin not being installed for details.

Bitbucket

There are no known issues or changes requiring awareness for this upgrade.

Confluence

There are no known issues or changes requiring awareness for this upgrade.

Jira

There are no known issues or changes requiring awareness for this upgrade.

  • No labels
Atlassian®, Atlassian Bamboo®, Bitbucket®, Atlassian Crowd®, Confluence®, Jira®, Jira Service Management™, Opsgenie®, and Statuspage™ are registered trademarks of Atlassian.
Amazon Web Services™, AWS™ and the “Powered by Amazon Web Services” logo are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.

Utoolity® is a registered trademark of Utoolity GmbH.
© 2024 Utoolity GmbH. All rights reserved.