SCM sync configuration plugin stopped working for new version of Jenkins 2.332.1

[preddymm]

Jenkins and plugins versions report

Environment

Paste the output here

What Operating System are you using (both controller, and any agents involved in the problem)?

SCM sync plugin stopped working after upgrading to the new LTS version of Jenkins.
Please fix it ASAP.

Reproduction steps

It should get updated in the git repository.

Expected Results

It should get updated in the git repository.

Actual Results

It should get updated in the git repository.

Anything else?

No response

[preddymm]

@rodrigc Could you please update and release the new plugin? It will be really helpful for all.

[preddymm]

@fcamblor @tomaswolf @ndeloof @johnou @jcarsique @stephenc @mhelff @mnencia @alanharder @olamy ? Please help us. We are using this plugin from last 6 years and after the recent Jenkins LTS upgrade it stopped working.

[johnou]

@preddymm is there a JIRA ticket with a stacktrace?

[preddymm]

@johnou https://plugins.jenkins.io/scm-sync-configuration/#issues
#76 is the one created by me.
I created an issue in the above link. Not sure, where to create the Jira one.

[johnou]

#74 may help. JEP still draft.

[basil]

@johnou @preddymm If the changes from #74 work, you can consider adopting the plugin to merge and release the PR. The "Contributing to Open Source" workshop from DevOps World 2021 is a useful starting point for new maintainers. That document includes links to a five part video series that illustrates many of the steps. If the plugin is crucial to your work, you may want to ask your employer to support your work efforts by allowing you to adopt the plugin.

[johnou]

@preddymm do you see an error or stacktrace in the Jenkins logs related to the plugin which explains why it stopped working?

[preddymm]

@johnou Unfortunately, it is not giving any errors in the Jenkins logs, The only issue with this plugin is it not updating in the Git repository. It was able to calculate the change in Jenkins configuration. Something was happening that it was not able to notify and update the Git repository.

The Jenkins version I am using is 2.332.1

[preddymm]

@fcamblor @tomaswolf @ndeloof @johnou @jcarsique @stephenc @mhelff @mnencia @alanharder @olamy ? Please help us. We are using this plugin from last 6 years and after the recent Jenkins LTS upgrade it stopped working.

Any update?

[basil]

@preddymm If the changes from #74 work, you can consider adopting the plugin to merge and release the PR. The "Contributing to Open Source" workshop from DevOps World 2021 is a useful starting point for new maintainers. That document includes links to a five part video series that illustrates many of the steps. If the plugin is crucial to your work, you may want to ask your employer to support your work efforts by allowing you to adopt the plugin.

[mdorotich-swi]

@basil Can you reconsider fixing https://issues.jenkins.io/browse/JENKINS-66326? For non-pipeline jobs, this is our Jenkins backup mechanism.

[basil]

@mdorotich-swi If the changes from #74 work, you can consider adopting the plugin to merge and release the PR. The "Contributing to Open Source" workshop from DevOps World 2021 is a useful starting point for new maintainers. That document includes links to a five part video series that illustrates many of the steps. If the plugin is crucial to your work, you may want to ask your employer to support your work efforts by allowing you to adopt the plugin.

[sunnyqeen]

I merged @basil #74 and fixed 2 jelly files
My build works OK with new jenkins 2.361.1
@preddymm you can try my build at
https://github.com/sunnyqeen/scm-sync-configuration-plugin/actions/runs/3111646714
Or build yourself

[preddymm]

@sunnyqeen That's awesome.
Thank you so much!!!

[preddymm]

@sunnyqeen It's working for me on the newer Jenkins. Thanks for your fix,

[mdorotich-swi]

@sunnyqeen thank you!