-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
9.12.7
-
9.12
-
1
-
Severity 3 - Minor
-
1
-
Issue Summary
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Adding the following parameters to disable the DVCS UI sync:
dvcs.connector.synchronization.disabled dvcs.connector.full-synchronization.disabled dvcs.connector.pr-synchronization.disabled
- Update the DVCS scheduler job time to zero to disable the hourly sync job:
- Set the JVM parameter below via setenv.sh:
-Ddvcs.connector.scheduler.interval=0
- Restart Jira.
- Run the SQL query below:
UPDATE clusteredjob SET interval_millis=0 WHERE job_runner_key='com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler';
- This com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler will trigger the sync once, and never again.
- Set the JVM parameter below via setenv.sh:
- Wait for 1 -2 hours later and generate a new support zip.
- Upload the support zip file into the perflog viewer and we can see some outbound requests from "Repository Request" in the DVCS stat:
Expected Results
DVCS shouldn't be sending any sync request to the Github, Gitlab or Bitbucket Cloud.
Actual Results
DVCS is sending some sync request to the Github, Gitlab or Bitbucket Cloud.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- links to