Below are some important notes on upgrading to a new version of TeamCity Integration for JIRA Cloud. Below you can details of the improvements that are included into this release.Here you can also find details of maintenance jobs that you will have to perform.
Release Notes
The current release will feature the allocation of the single static IP address for sending requests to TeamCity. The administrators of TeamCity servers located behind firewall will be able to allow connections from the static IP address of the add-on. In such a way you can preserve the high security level of your infrastructure.
The new static IP address is XXX.XXX.XXX.XXX.
Upgrade Notes 2/6/2017
Thanks for choosing our development solution for JIRA Cloud. We are going to make some upgrades that should make our add-on TeamCity Integration for JIRA Cloud more reliable and ready for further growth.
The old version of the add-on is hosted in Heroku which does not provide a reliable way to get a static IP address for outbound requests. To secure the information of our customers, we decided to migrate all the existing add-on infrastructure to Amazon Web Services (AWS).
What are we doing?
We are migrating all the existing add-on infrastructure from Heroku to Amazon Web Services (AWS)
All the maintenance jobs are starting at 05:00 UTC on Monday, February 6, 2017. There will be a tentative one-hour downtime in the add-on operation during this migration.
The expected migration will take no longer than one hour.
Why are we doing this?
Our new IP address space, along with some underlying network improvements, should make response times noticeably faster for about a third of our users. Just as important, these changes make it easier for us to improve upstream network connectivity and load balancing, and to perform other infrastructure projects in the near future.
How will this affect you?
Most users will not have to do anything special for this migration. Your DNS servers should pick up the new IPs within a few minutes of the migration, and your systems should start using the new IPs right away. We’ll keep the old IPs running for a few weeks afterwards just in case, though.
Firewall considerations
If you control inbound or outbound access with a firewall, though, then you may need to update your configuration. Please whitelist these new IPs now; you should be able to remove the old IPs after the migration is complete.
New destination IP addresses for bitbucket.org will be:
- 104.192.143.1
- 104.192.143.2
- 104.192.143.3
- 104.192.143.65
- 104.192.143.66
- 104.192.143.67
New source IP addresses for hooks will be:
- 104.192.143.192/28
- 104.192.143.208/28
SSH considerations
Our server’s SSH key is not changing, so most SSH clients will continue to work without interruption. However, a small number of users may see a warning similar to this when they push or pull over SSH:
Warning: the RSA host key for ‘bitbucket.org’ differs from the key for the IP address ‘104.192.143.1’
The warning message will also tell you which lines in your ~/.ssh/known_hosts need to change. Open that file in your favorite editor, remove or comment out those lines, then retry your push or pull.
Stay updated
As we update records, we’ll post updates on our @BitbucketStatus Twitter account and our status site so you can follow along. We’ll also keep our knowledge base up-to-date with any future changes to the lists of IPs.
Thanks for your patience as we work to increase Bitbucket’s speed and reliability. Please contact us at support@bitbucket.org if you have any questions.
Можно разбить текст на разделы как в этом блог-посте bitbucket.org