• Type: Bug
• Resolution: Unresolved
• Priority: Low (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 9.12.7
• Component/s: DVCS Connector
• Labels:

  • FY24RRC
  • ril

1. 

   Screenshot 2024-06-19 at 1.23.42 PM.png

   67 kB

   19/Jun/2024 11:26 AM

[JSWSERVER-25997] Disable all dvcs sync still sending some request to the providers according to DVCS stats

SET Analytics Bot made changes - 18/Mar/2025 2:28 AM

UIS

New: 1

Marc Dacanay made changes - 16/Oct/2024 4:17 AM

Labels

Original: FY24RRC

New: FY24RRC ril

Marc Dacanay made changes - 16/Oct/2024 4:17 AM

Remote Link

New: This issue links to "Internal ticket (Web Link)" [ 956810 ]

ScottC made changes - 21/Aug/2024 6:50 PM

Labels

Original: FY24RRC support-required

New: FY24RRC

John Chin made changes - 01/Aug/2024 2:17 PM

Description

Original: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Adding the following parameters to disable the DVCS UI sync: {code:java} dvcs.connector.synchronization.disabled dvcs.connector.full-synchronization.disabled dvcs.connector.pr-synchronization.disabled {code}  # Update the DVCS scheduler job time to zero to disable the hourly sync job:  ** Set the JVM parameter below via setenv.sh: {code:java} -Ddvcs.connector.scheduler.interval=0 {code}  *  ** Restart Jira.  ** Run the SQL query below: {code:java} UPDATE clusteredjob SET interval_millis=0 WHERE job_runner_key='com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler'; {code}  *  ** This *com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler* will trigger the sync once, and never again.  # 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: !Screenshot 2024-06-19 at 1.23.42 PM.png|width=929,height=300! h3. Expected Results DVCS shouldn't be sending any sync request to the Github, Gitlab or Bitbucket Cloud. h3. Actual Results DVCS is sending some sync request to the Github, Gitlab or Bitbucket Cloud. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Adding the following parameters to disable the DVCS UI sync: {code:java} dvcs.connector.synchronization.disabled dvcs.connector.full-synchronization.disabled dvcs.connector.pr-synchronization.disabled {code}  # Update the DVCS scheduler job time to zero to disable the hourly sync job:  ** Set the JVM parameter below via setenv.sh: {code:java} -Ddvcs.connector.scheduler.interval=0 {code}  ** Restart Jira.  ** Run the SQL query below: {code:java} UPDATE clusteredjob SET interval_millis=0 WHERE job_runner_key='com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler'; {code}  ** This *com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler* will trigger the sync once, and never again.  # 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: !Screenshot 2024-06-19 at 1.23.42 PM.png|width=929,height=300! h3. Expected Results DVCS shouldn't be sending any sync request to the Github, Gitlab or Bitbucket Cloud. h3. Actual Results DVCS is sending some sync request to the Github, Gitlab or Bitbucket Cloud. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available

John Chin made changes - 01/Aug/2024 2:16 PM

Description

Original: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Adding the following parameters to disable the DVCS UI sync: {code:java} dvcs.connector.synchronization.disabled dvcs.connector.full-synchronization.disabled dvcs.connector.pr-synchronization.disabled {code}  # Update the DVCS scheduler job time to zero to disable the hourly sync job:  ** Set the JVM parameter below via setenv.sh: {code:java} -Ddvcs.connector.scheduler.interval=0 {code}  ** Restart Jira.  ** Run the SQL query below: {code:java} UPDATE clusteredjob SET interval_millis=0 WHERE job_runner_key='com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler'; {code}  ** This *com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler* will trigger the sync once, and never again.  # Wait for 1 -2 hours later and generate a new support zip.  # Upload the zip file to perflog viewer and we can see some outbound requests from "{*}Repository Request{*}" in the DVCS stat: !Screenshot 2024-06-19 at 1.23.42 PM.png|width=929,height=300! h3. Expected Results DVCS shouldn't be sending any sync request to the Github, Gitlab or Bitbucket Cloud. h3. Actual Results DVCS is sending some sync request to the Github, Gitlab or Bitbucket Cloud. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Adding the following parameters to disable the DVCS UI sync: {code:java} dvcs.connector.synchronization.disabled dvcs.connector.full-synchronization.disabled dvcs.connector.pr-synchronization.disabled {code}  # Update the DVCS scheduler job time to zero to disable the hourly sync job:  ** Set the JVM parameter below via setenv.sh: {code:java} -Ddvcs.connector.scheduler.interval=0 {code}  *  ** Restart Jira.  ** Run the SQL query below: {code:java} UPDATE clusteredjob SET interval_millis=0 WHERE job_runner_key='com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler'; {code}  *  ** This *com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler* will trigger the sync once, and never again.  # 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: !Screenshot 2024-06-19 at 1.23.42 PM.png|width=929,height=300! h3. Expected Results DVCS shouldn't be sending any sync request to the Github, Gitlab or Bitbucket Cloud. h3. Actual Results DVCS is sending some sync request to the Github, Gitlab or Bitbucket Cloud. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available

John Chin made changes - 01/Aug/2024 2:16 PM

Description

Original: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Adding the following parameters to disable the DVCS UI sync: {code:java} dvcs.connector.synchronization.disabled dvcs.connector.full-synchronization.disabled dvcs.connector.pr-synchronization.disabled {code}  # Update the DVCS scheduler job time to zero to disable the hourly sync job:  #* Set the JVM parameter below via setenv.sh: {code:java} -Ddvcs.connector.scheduler.interval=0 {code} #* Restart Jira.  #* Run the SQL query below: {code:java} UPDATE clusteredjob SET interval_millis=0 WHERE job_runner_key='com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler'; {code} #* This *com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler* will trigger the sync once, and never again.  # Wait for 1 -2 hours later and we can see some outbound requests from "{*}Repository Request{*}" in the DVCS stat: !Screenshot 2024-06-19 at 1.23.42 PM.png|width=929,height=300! h3. Expected Results DVCS shouldn't be sending any sync request to the Github, Gitlab or Bitbucket Cloud. h3. Actual Results DVCS is sending some sync request to the Github, Gitlab or Bitbucket Cloud. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary This is reproducible on Data Center: (yes) h3. Steps to Reproduce  # Adding the following parameters to disable the DVCS UI sync: {code:java} dvcs.connector.synchronization.disabled dvcs.connector.full-synchronization.disabled dvcs.connector.pr-synchronization.disabled {code}  # Update the DVCS scheduler job time to zero to disable the hourly sync job:  ** Set the JVM parameter below via setenv.sh: {code:java} -Ddvcs.connector.scheduler.interval=0 {code}  ** Restart Jira.  ** Run the SQL query below: {code:java} UPDATE clusteredjob SET interval_millis=0 WHERE job_runner_key='com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler'; {code}  ** This *com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler* will trigger the sync once, and never again.  # Wait for 1 -2 hours later and generate a new support zip.  # Upload the zip file to perflog viewer and we can see some outbound requests from "{*}Repository Request{*}" in the DVCS stat: !Screenshot 2024-06-19 at 1.23.42 PM.png|width=929,height=300! h3. Expected Results DVCS shouldn't be sending any sync request to the Github, Gitlab or Bitbucket Cloud. h3. Actual Results DVCS is sending some sync request to the Github, Gitlab or Bitbucket Cloud. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available

John Chin made changes - 01/Aug/2024 2:00 PM

Summary

Original: Disable all dvcs sync still sending some request to the providers

New: Disable all dvcs sync still sending some request to the providers according to DVCS stats

Oleksandr Tkachenko made changes - 26/Jun/2024 8:23 AM

Labels

New: FY24RRC support-required

awojtasik made changes - 20/Jun/2024 7:08 AM

Status

Original: Needs Triage [ 10030 ]

New: Gathering Impact [ 12072 ]

Load more older events