Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: svn-tag-plugin
    • Labels:
      None
    • Environment:
      Jenkins LTS 1.532.1
      Jenkins Subversion Tagging Plugin 1.16
    • Similar Issues:

      Description

      When tagging a matrix project with two slaves on an axis, each build tags the source code. This is very anoying, because the source code is tagged multiple times. Subsequent jobs have to delete the existing tag and create it again.

      Improvement: Support matrix build in that way, that in the job configuration one can choose whether the matrix parent job or the matrix child jobs will do the tagging.

      This could be implemented similar to the email-ext plugin.

        Attachments

          Issue Links

            Activity

            wh WH created issue -
            wh WH made changes -
            Field Original Value New Value
            Description When tagging a matrix project with two slaves on an axis, each build tries to tag the source code.
            The first build successfully deletes the existing tag and creates a new tag.
            The second build fails to delete the existing tag and creates a trunk folder inside the existing tag.

            Console output of the first build:

            Started by upstream project "test" build number 6
            Building remotely on slave1
            Checking out a fresh workspace because there's no workspace at /tmp/jenkins_slave1/workspace/test/label/slave1
            Cleaning workspace /tmp/jenkins_slave1/workspace/test/label/slave1
            Checking out svn+ssh://user@server/repo/test/trunk
            AU abc.txt
            At revision 238
            no change for svn+ssh://user@server/repo/test/trunk since the previous build
            moduleLocation: Remote ->svn+ssh://user@server/repo/test/trunk
            Tag Base URL: 'svn+ssh://user@server/repo/test/tags/myTag'.
            Delete old tag svn+ssh://user@server/repo/test/tags/myTag.
            Tagged as Revision 240
            Notifying upstream projects of job completion
            Finished: SUCCESS

            Console output of the second build:

            Started by upstream project "test" build number 6
            Building remotely on slave2
            Checking out a fresh workspace because there's no workspace at /tmp/jenkins_slave2/workspace/test/label/slave2
            Cleaning workspace /tmp/jenkins_slave2/workspace/test/label/slave2
            Checking out svn+ssh://user@server/repo/test/trunk
            AU abc.txt
            At revision 238
            no change for svn+ssh://user@server/repo/test/trunk since the previous build
            moduleLocation: Remote ->svn+ssh://user@server/repo/test/trunk
            Tag Base URL: 'svn+ssh://user@server/repo/test/tags/myTag'.
            There was no old tag at svn+ssh://user@server/repo/test/tags/myTag.
            Tagged as Revision 241
            Notifying upstream projects of job completion
            Finished: SUCCESS

            Subversion log says:

            239 Deleted /test/tags/myTag "Old tag deleted by Jenkins build: jenkins-label=slave1
            240 Added /test/tags/myTag (Copy from path /test/trunk) "Tagged by Jenkins build: jenkins-label=slave1
            241 Added /test/tags/myTag/trunk (Copy from path /test/trunk) "Tagged by Jenkins build: jenkins-labe-=slave2
            When tagging a matrix project with two slaves on an axis, each build tries to tag the source code.
            The first build successfully deletes the existing tag and creates a new tag.
            The second build fails to delete the existing tag and creates a trunk folder inside the existing tag.

            Console output of the first build:

            Started by upstream project "test" build number 6
            Building remotely on slave1
            Checking out a fresh workspace because there's no workspace at /tmp/jenkins_slave1/workspace/test/label/slave1
            Cleaning workspace /tmp/jenkins_slave1/workspace/test/label/slave1
            Checking out svn+ssh://user@server/repo/test/trunk
            AU abc.txt
            At revision 238
            no change for svn+ssh://user@server/repo/test/trunk since the previous build
            moduleLocation: Remote ->svn+ssh://user@server/repo/test/trunk
            Tag Base URL: 'svn+ssh://user@server/repo/test/tags/myTag'.
            Delete old tag svn+ssh://user@server/repo/test/tags/myTag.
            Tagged as Revision 240
            Notifying upstream projects of job completion
            Finished: SUCCESS

            Console output of the second build:

            Started by upstream project "test" build number 6
            Building remotely on slave2
            Checking out a fresh workspace because there's no workspace at /tmp/jenkins_slave2/workspace/test/label/slave2
            Cleaning workspace /tmp/jenkins_slave2/workspace/test/label/slave2
            Checking out svn+ssh://user@server/repo/test/trunk
            AU abc.txt
            At revision 238
            no change for svn+ssh://user@server/repo/test/trunk since the previous build
            moduleLocation: Remote ->svn+ssh://user@server/repo/test/trunk
            Tag Base URL: 'svn+ssh://user@server/repo/test/tags/myTag'.
            There was no old tag at svn+ssh://user@server/repo/test/tags/myTag.
            Tagged as Revision 241
            Notifying upstream projects of job completion
            Finished: SUCCESS

            Subversion log says:

            239 Deleted /test/tags/myTag "Old tag deleted by Jenkins build: jenkins-label=slave1"
            240 Added /test/tags/myTag (Copy from path /test/trunk) "Tagged by Jenkins build: jenkins-label=slave1"
            241 Added /test/tags/myTag/trunk (Copy from path /test/trunk) "Tagged by Jenkins build: jenkins-labe-=slave2"
            ohtake_tomohiro OHTAKE Tomohiro made changes -
            Link This issue is duplicated by JENKINS-9682 [ JENKINS-9682 ]
            wh WH made changes -
            Summary Tagging a matrix project Support matrix projects
            Issue Type Bug [ 1 ] Improvement [ 4 ]
            Assignee k2nakamura [ k2nakamura ] Renjith V [ vrenjith ]
            Environment Jenkins 1.411, Subversion Tagging Plugin 1.14 Jenkins LTS 1.532.1
            Jenkins Subversion Tagging Plugin 1.16
            Description When tagging a matrix project with two slaves on an axis, each build tries to tag the source code.
            The first build successfully deletes the existing tag and creates a new tag.
            The second build fails to delete the existing tag and creates a trunk folder inside the existing tag.

            Console output of the first build:

            Started by upstream project "test" build number 6
            Building remotely on slave1
            Checking out a fresh workspace because there's no workspace at /tmp/jenkins_slave1/workspace/test/label/slave1
            Cleaning workspace /tmp/jenkins_slave1/workspace/test/label/slave1
            Checking out svn+ssh://user@server/repo/test/trunk
            AU abc.txt
            At revision 238
            no change for svn+ssh://user@server/repo/test/trunk since the previous build
            moduleLocation: Remote ->svn+ssh://user@server/repo/test/trunk
            Tag Base URL: 'svn+ssh://user@server/repo/test/tags/myTag'.
            Delete old tag svn+ssh://user@server/repo/test/tags/myTag.
            Tagged as Revision 240
            Notifying upstream projects of job completion
            Finished: SUCCESS

            Console output of the second build:

            Started by upstream project "test" build number 6
            Building remotely on slave2
            Checking out a fresh workspace because there's no workspace at /tmp/jenkins_slave2/workspace/test/label/slave2
            Cleaning workspace /tmp/jenkins_slave2/workspace/test/label/slave2
            Checking out svn+ssh://user@server/repo/test/trunk
            AU abc.txt
            At revision 238
            no change for svn+ssh://user@server/repo/test/trunk since the previous build
            moduleLocation: Remote ->svn+ssh://user@server/repo/test/trunk
            Tag Base URL: 'svn+ssh://user@server/repo/test/tags/myTag'.
            There was no old tag at svn+ssh://user@server/repo/test/tags/myTag.
            Tagged as Revision 241
            Notifying upstream projects of job completion
            Finished: SUCCESS

            Subversion log says:

            239 Deleted /test/tags/myTag "Old tag deleted by Jenkins build: jenkins-label=slave1"
            240 Added /test/tags/myTag (Copy from path /test/trunk) "Tagged by Jenkins build: jenkins-label=slave1"
            241 Added /test/tags/myTag/trunk (Copy from path /test/trunk) "Tagged by Jenkins build: jenkins-labe-=slave2"
            When tagging a matrix project with two slaves on an axis, each build tags the source code. This is very anoying, because the source code is tagged multiple times. Subsequent jobs have to delete the existing tag and create it again.

            Improvement: Support matrix build in that way, that in the job configuration one can choose whether the matrix parent job or the matrix child jobs will do the tagging.

            This could be implemented similar to the email-ext plugin.
            ikedam ikedam made changes -
            Link This issue is related to JENKINS-21345 [ JENKINS-21345 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 139857 ] JNJira + In-Review [ 175168 ]

              People

              • Assignee:
                vrenjith Renjith Pillai
                Reporter:
                wh WH
              • Votes:
                2 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: