Double changes in Declarative Pipeline job

[Andreas Magnusson]

We happily using Declarative Pipeline here, however I've noticed from the very beginning that we get double build "recordings" in the Changes log. It seems that we get one log from the checkout/update of the workspace for the Jenkinsfile, and then one from the automatic checkout/update from the automatic checkout by Declarative.
Is this a bug or a feature, or do anyone have a simple workaround? One would probably be to disable the auto checkout in Declarative, but it seems that it would go against the flow of the Declarative plugin. Also, I really like a solution where I don't have to duplicate the checkout url (which I don't have to do with a simple "checkout scm" entry)
Another would be to get the first checkout not to be part of the change log, but that option doesn't seem to be available on a standard Pipeline job.

Note that we're using Subversion (in case it differs from Git), and a standard Pipeline job (NOT multibranch).

Cheers,
Andreas

[Andrew Bayer]

This isn't Declarative specific, fwiw. I'll try to take another look at the change log logic this week.

A.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9edd36ed-09f7-4def-aa96-8bef1190e54e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.