Growing config.xml with GitLab plugin

[Qiang]

Recently I upgraded to Jenkins 2.46.3 (based on the docker image release). There is a "new weird" problem. I noticed job's config.xml grow really big. When open it , it has tons of repeated following code

    <hudson.plugins.buildblocker.BuildBlockerProperty reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
    <jenkins.model.BuildDiscarderProperty reference="../jenkins.model.BuildDiscarderProperty"/>
    <com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
    <hudson.plugins.buildblocker.BuildBlockerProperty reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
    <jenkins.model.BuildDiscarderProperty reference="../jenkins.model.BuildDiscarderProperty"/>
    <com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
    <hudson.plugins.buildblocker.BuildBlockerProperty reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
    <jenkins.model.BuildDiscarderProperty reference="../jenkins.model.BuildDiscarderProperty"/>
    <com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
    <hudson.plugins.buildblocker.BuildBlockerProperty reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
    <jenkins.model.BuildDiscarderProperty reference="../jenkins.model.BuildDiscarderProperty"/>

This was not observed before the upgrade (Jenkins ver. 2.46.2)
Even though I upgraded plugin versions, the GitLab plugin stays the same (1.4.5)


Wonder if any one else have seen this, and do you have any workaround or fix? 

Thanks!
Qiang

[Dan Tran]

we encounter similar issue  with declarative pipeline upgrade   https://groups.google.com/forum/#!topic/jenkinsci-users/lAyx4kof0wU

For you case, you may need drop and recreate the job

-Dan

[Andrew Bayer]

Yup, that was entirely my bad, but is now fixed. Sorry about that!

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-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/051604eb-0fec-46ce-98eb-272a3a36c8e2%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Andrew Bayer]

Oh, and you don't need to nuke the job - the configs will get fixed automatically on next run of the job, and if you're unable to kick a build off (due to https://issues.jenkins-ci.org/browse/JENKINS-44809), you can run the script at https://issues.jenkins-ci.org/browse/JENKINS-44809?focusedCommentId=302837&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-302837 in the Jenkins Script Console to manually clean up the bogus properties.

A.

[Qiang]

Hi, Dan , Thanks for the hint, and I did find the job recreatd by job DSL didn't have the problem

Hi, Andrew, thanks for the good news!  Do we just upgrade all the plugins to get the fix?

Qiang

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

[Andrew Bayer]

You only specifically need to upgrade Pipeline: Model Definition.

A.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/839e7ca5-1592-4003-a078-e273939c5180%40googlegroups.com.

[Qiang]

Thanks! I updated the plugin(s), now it is working!