MR statuses not syncing in GitLab for Jira Connect application
Summary
Multiple users have reported that MR status does not transition in the Jira Development panel when using the GitLab for Jira connect application.
How to fix
Logs show that we sometimes run into timeouts and that we don't retry the jobs.
In order to be able to retry jobs, we need to make the JiraConnect::SyncMergeRequestWorker idempotent. Unfortunately this requeres a multi step deployment over 3 milestones.
-
Add the argument to the worker with a default value (13.6, !46535 (merged)) -
Add the new argument to all the invocations of the worker (13.7, !48234 (merged)) -
Remove the default value and make worker idempotent (13.8, !51006 (merged))
Steps to reproduce
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
(What actually happens)
What is the expected correct behavior?
(What you should see instead)
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
/cc @leipert