Changes to Jenkins config via Jenkins API are ignored by the plugin about scm-sync-configuration-plugin HOT 4 OPEN

Don't think it would be difficult to implement this.

Currently, you already have an endpoint allowing to say "hey, this path has been changed, register it in future commit" : look at there (FYI, doXXX methods are HTTP endpoints as well, so you might call this with an HTTP request)

I'm not completely sure about this, but I think by calling the API to create/update/delete job, you're already calling a Saveable.change() which should trigger the registerPath() call I exposed before.

As soon as you will have registered paths, all you will have to do is to commit the transaction, maybe by providing some comment to your commit before.

Hope this helps.

from scm-sync-configuration-plugin.

I too have run into this exact issue. Creating/updating a job via the API does not trigger an SCM save, we have to manually go to the Jenkins job page, click the 'save' button which then triggers the scm-sync-configuration plugin.

from scm-sync-configuration-plugin.

Any news on this? We use Jenkins-CLI and Jenkins REST-API for a complete automated job setup in case a new package was added to the VCS in the background. But all these auto-generated-jobs where missed on the configuration repo until someone "touches" them in some other way. Would be great if this could be fixed!

from scm-sync-configuration-plugin.

Would like to see this solved :)

from scm-sync-configuration-plugin.