Migrated the add-on infrastructure from Heroku to AWS and allocated a static address
Below are some important notes on upgrading to a new version of TeamCity Integration for JIRA Cloud. Below you can find details of the improvements that are included into this release. Here you can also view information about maintenance jobs that you will have to perform.
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 184.108.40.206.
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?
We have received several requests from our customers who are hosting TeamCity servers behind the firewall. Using the existing add-on infrastructure hosted in Heroku did not allow us to allocate a static IP address for processing TeamCity data. Heroku does not provide an easy and efficient way to allocate a static address. As it deals mainly with dynamic addresses so it becomes impossible to set up the proper firewall configuration for correct operation of TeamCity Integration for JIRA Cloud add-on.
What will be unavailable during the downtime?
The temporary one-hour add-on downtime will NOT anyhow impact JIRA Cloud functionality.
The existing index of build data retrieved from TeamCity server will be unavailable on the TeamCity tab in the issue and project views.
The regular indexation of build data will be temporarily suspended during the maintenance jobs.
How will this affect you?
Most users will not have to do anything special for this migration. Unfortunately, there is one issue that we cannot resolve without your help.
The migration procedure will include a step that will require change of the baseUrl of the add-on. Atlassian Connect does not provide a seamless method to change the add-on baseUrl. That's so migration of the baseUrl will require the re-installation of the add-on by the administrator of JIRA Cloud.
Below you can find the step-by-step instructions on how to do this:
- Navigate to JIRA Cloud UPM.
- On the list with installed add-ons, locate TeamCity Integration for JIRA Cloud.
- Click Unsubscribe.
- Click Uninstall.
- Install the add-on once the uninstallation is complete.
Please note that the re-installation of the add-on will not affect the existing build index and configured settings. Though NO additional setup will be required after re-installation of the add-on.
The add-on should be fully operable after this procedure and pick the new IP address for operation.
If you control inbound traffic, though you may need to update your configuration. Please whitelist this IP address for correct operation of the add-on:
You will receive three emails:
- email with a notification about the scheduled maintenance jobs
- email one hour prior to launch of infrastructure migration
- email after migration completion
We will keep you updated on the process of migration and will notify you immediately if some unexpected issues occur during it,
Thanks for your patience and understanding! We will do our best to increase the reliability and security of TeamCity Integration for JIRA Cloud.
Please contact us at firstname.lastname@example.org if you have any questions.