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

p4unshelve task uses the wrong Perforce workspace

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: p4-plugin
    • Labels:
      None
    • Environment:
      1.3.8-SNAPSHOT (private-3c567c28-jenkins)
    • Similar Issues:

      Description

      I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

      My pipeline script looks something like this:

      node(linux) {
      p4sync stream: '//buildtools/jenkins_review_workflow'
      pipeline = load 'workflows/linux-p4-review-build.groovy'
      pipeline.run_workflow()
      }

      Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.

        Attachments

          Issue Links

            Activity

            mrose Michael Rose created issue -
            mrose Michael Rose made changes -
            Field Original Value New Value
            Description I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {{node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }}}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            mrose Michael Rose made changes -
            Description I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {{node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }}}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {{node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            mrose Michael Rose made changes -
            Description I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {{node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {{node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }
            }}
            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            mrose Michael Rose made changes -
            Description I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {{node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }
            }}
            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {quote}node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }{quote}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            mrose Michael Rose made changes -
            Description I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {quote}node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }{quote}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {quote}
            node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }
            {quote}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            mrose Michael Rose made changes -
            Description I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {quote}
            node(linux) {
               p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }
            {quote}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {quote}
            node(linux) {{
                p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }}
            {quote}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            mrose Michael Rose made changes -
            Description I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {quote}
            node(linux) {{
                p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            }}
            {quote}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            I have a pipeline project configured that is tied in to Swarm. Earlier today my review build succeeded, but after I submitted my changelist the committed build failed. When I looked at the console output I found that the p4unshelve task was attempting to unshelve the review into the wrong workspace.

            My pipeline script looks something like this:

            {quote}
            node(linux) \{
                p4sync stream: '//buildtools/jenkins_review_workflow'
                pipeline = load 'workflows/linux-p4-review-build.groovy'
                pipeline.run_workflow()
            \}
            {quote}

            Within pipeline.run_workflow, there is another checkout call and an unshelve that occurs. The 2nd sync is where the actually source code is downloaded and that should be the workspace where the unshelve is performed as well, however the unshelve is actually being perforrmed against the workspace where the original p4sync was called.
            mrose Michael Rose made changes -
            Assignee Paul Allen [ p4paul ]
            Hide
            mrose Michael Rose added a comment - - edited

            Paul Allen: This is just an FYI in you want to look into it. I already have a workaround.

            sh "p4 unshelve ..."
            
            Show
            mrose Michael Rose added a comment - - edited Paul Allen : This is just an FYI in you want to look into it. I already have a workaround. sh "p4 unshelve ..."
            mrose Michael Rose made changes -
            Priority Major [ 3 ] Minor [ 4 ]
            p4paul Paul Allen made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 170031 ] JNJira + In-Review [ 185711 ]
            Hide
            p4paul Paul Allen added a comment -

            Ready for release

            Show
            p4paul Paul Allen added a comment - Ready for release
            p4paul Paul Allen made changes -
            Status In Progress [ 3 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            Hide
            p4paul Paul Allen added a comment -

            Released 1.4.4

            Show
            p4paul Paul Allen added a comment - Released 1.4.4
            p4paul Paul Allen made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            Hide
            p4paul Paul Allen added a comment -

            Incorrectly assigned to 1.4.4 release

            Show
            p4paul Paul Allen added a comment - Incorrectly assigned to 1.4.4 release
            p4paul Paul Allen made changes -
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            mrose Michael Rose made changes -
            Link This issue relates to JENKINS-42510 [ JENKINS-42510 ]

              People

              • Assignee:
                p4paul Paul Allen
                Reporter:
                mrose Michael Rose
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: