Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16378

All build logs added and committed when renaming job

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Using Git as back end, when renaming a job the commit added all files under /job/renamedJob/* to the commit, rather that just the ones supposed to be included by default.

      the commit message looks like:

      Job [oldJobName] hierarchy renamed from [jobs/oldJobName] to [jobs/newJobName] by user

      The commit added 114 new files:

      jobs/newJobName/builds/date/triggerlog.xml
      jobs/newJobName/builds/date/build.xml
      jobs/newJobName/builds/date/changelog.xml
      jobs/newJobName/builds/date/injectedEnvVars.txt

      repeating for each retaining build.

      The documentation says it should only be including the following by default:
      config.xml
      hudson*.xml
      scm-sync-configuration.xml
      jobs/*/config.xml

      but it incorrectly add jobs/newJobName/builds/*.[txt|xml]

        Attachments

          Issue Links

            Activity

            Hide
            fcamblor Frédéric Camblor added a comment -

            I think this is an issue which should benefit from the upcoming big refacto described in both JENKINS-18129 & JENKINS-18124

            Show
            fcamblor Frédéric Camblor added a comment - I think this is an issue which should benefit from the upcoming big refacto described in both JENKINS-18129 & JENKINS-18124
            Hide
            mrconnerton Matthew Connerton added a comment -

            ok I will follow. I am not a jenkins pluggin/java guy, but if you can point me to a good resource to get started, I would be happy to help test patches / dev versions.

            Show
            mrconnerton Matthew Connerton added a comment - ok I will follow. I am not a jenkins pluggin/java guy, but if you can point me to a good resource to get started, I would be happy to help test patches / dev versions.
            Hide
            fcamblor Frédéric Camblor added a comment -

            Thx, will keep the issues updated with my current work on them

            Show
            fcamblor Frédéric Camblor added a comment - Thx, will keep the issues updated with my current work on them
            Hide
            tpatja Teemu Patja added a comment -

            At my company we have been running Hudson/Jenkins for about 4 years and have jobs with a lot of builds. I took scm_sync_configuration to use with a git backend about 8 months ago and have been quite happy with it (able to track changes to job configs etc). Recently, a job with 200+ builds got renamed and that lead to a huge commit containing all the builds and workspace files, making the configs repo huge (du -sh scm-sync-configuration/checkoutConfiguration says 2.6 GB!). That lead to first configs no longer being updated to git (started 2 weeks ago) and today jenkins master no longer being able to start after a restart(git runs out of memory).

            Any tip on how to fix the situation (keeping our change history to job configs) would be appreciated. We need to get the config repo size back to a sane size (somehow undo the adds for the extra files).

            Also, after shrinking the repo, a workaround for avoiding this bug would be nice (just avoid rename for now?).

            FYI, we're using version 0.0.7.3.

            Thanks.

            Show
            tpatja Teemu Patja added a comment - At my company we have been running Hudson/Jenkins for about 4 years and have jobs with a lot of builds. I took scm_sync_configuration to use with a git backend about 8 months ago and have been quite happy with it (able to track changes to job configs etc). Recently, a job with 200+ builds got renamed and that lead to a huge commit containing all the builds and workspace files, making the configs repo huge (du -sh scm-sync-configuration/checkoutConfiguration says 2.6 GB!). That lead to first configs no longer being updated to git (started 2 weeks ago) and today jenkins master no longer being able to start after a restart(git runs out of memory). Any tip on how to fix the situation (keeping our change history to job configs) would be appreciated. We need to get the config repo size back to a sane size (somehow undo the adds for the extra files). Also, after shrinking the repo, a workaround for avoiding this bug would be nice (just avoid rename for now?). FYI, we're using version 0.0.7.3. Thanks.
            Hide
            rodrigc Craig Rodrigues added a comment -

            Fixed in 0.0.9

            Show
            rodrigc Craig Rodrigues added a comment - Fixed in 0.0.9

              People

              • Assignee:
                fcamblor Frédéric Camblor
                Reporter:
                trbaker Trevor Baker
              • Votes:
                1 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: