JIRA integration may captcha the JIRA account
In case the JIRA account used for the JIRA integration fails to authenticate enough times in a row, it may be prompted to resolve a captcha (depending on JIRA configuration). It requires an admin to go resolve the captcha and defeats the purpose of the integration.
Ultimately this is an issue with JIRA transient authentication failures, but it would be nice to mitigate it in GitLab.
Steps to reproduce
Hard to reproduce. Setup JIRA integration on a busy enough GitLab server and a flaky enough JIRA server.
What is the current bug behavior?
Current behaviour: authentication failure in JIRA has not impact on the JIRA API calls schedule.
What is the expected correct behavior?
Suggested behaviour: authentication failure in JIRA suspends JIRA API calls for a while and retry later.
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 16.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.6.3p62 Gem Version: 2.7.9 Bundler Version:1.17.3 Rake Version: 12.3.2 Redis Version: 3.2.12 Git Version: 2.22.0 Sidekiq Version:5.2.7 Go Version: unknown
GitLab information Version: 12.2.8-ee Revision: 60f41838709 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 10.7 URL: https://gitlab.myteksi.net HTTP Clone URL: https://gitlab.myteksi.net/some-group/some-project.git SSH Clone URL: firstname.lastname@example.org:some-group/some-project.git Elasticsearch: yes Geo: no Using LDAP: yes Using Omniauth: yes Omniauth Providers:
GitLab Shell Version: 9.3.0 Repository storage paths:
- default: /media/nfs/git_0/repositories
- shard_1: /media/nfs/git_1/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git