Background migration for setting Jira tracker data deployment type
What does this MR do?
Now that !37003 (merged) and !36992 (merged) are merged, we should go through each Jira service and update the deployment type if possible.
This involves making an API call to each defined Jira url (a public call, authentication not needed) to determine what type of server it is. For this reason, I scheduled each record into it's own job, rather than batching them together. This keeps the background migration idempotent.
If the call out to the Jira Server fails for some reason (bad url, etc), then we simply leave the deployment_type set to 0.
Based on https://community.developer.atlassian.com/t/get-rest-api-3-filter-search/29459/2, it's enough at the moment to simply notice if the url is from atlassian.net, rather than making an API call for each server.
There are currently only 76,313 jira_tracker_data entries that need updating, 78,627 total records.
Related to #243607 (closed)
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #229223 (closed)