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

don't need sync -f @0 command in cleanup true

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Not A Defect
    • Icon: Major Major
    • p4-plugin
    • None

      Hello.

       

      I use this pipeline.

      pipeline {
        agent {
          kubernetes {
            label 'xx'
            yamlFile 'xx.yaml'
          }
        }
        options {
          skipDefaultCheckout()
          timestamps()
        }
        stages {
          stage('Run Test') {
            steps {
              container(name: 'xxx', shell: '/bin/bash') {
                checkout perforce(
                  browser: swarm('http://'),
                  credential: 'xxx',
                  populate: previewOnly(quiet: true),
                  workspace: templateSpec(charset: 'utf8', format: 'jenkins-${JOB_NAME}-${BUILD_ID}-${NODE_NAME}', pinHost: false, templateName: 'TEMPLATE__all')
                )
                timeout (10) {
                  sh '/sa.py'
                }
              }
            }
            post {
              always {
                cleanup true
              }
            }
          }
        }
      }
      

       

      In this case, 

      template workspace(TEMPLATE__all)'s view mapping is all depot like,

      //depot1/... //ws/depot1/...

      //depot2/... //ws/depot2/...

      ...

      and no sync command, just create workspace only.

       

      but at post, I want to delete workspace just,

      but "cleanup true" command runs

      p4 sync -f -q /home/jenkins/workspace/xxx/...@0 command

      and it does not run. 

      I don't know why but anyway I don't need sync -f -q @0 command.

       

      Please improve cleanup command.

       

      log is here.

      <snip>
      [Pipeline] // container
      Post stage
      [Pipeline] cleanup
      15:04:44  (p4):cmd:... p4 client -o TEMPLATE__SE_SWARM_AT_SA
      15:04:44  p4 client -o TEMPLATE__SE_SWARM_AT_SA
      15:04:44  
      15:04:44  (p4):stop:3
      15:04:44  (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb
      15:04:44  p4 client -o jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb
      15:04:44  
      15:04:45  (p4):stop:4
      15:04:45  (p4):cmd:... p4 client -i
      15:04:45  p4 client -i
      15:04:45  
      15:04:45  Client jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb not changed.
      15:04:45  
      15:04:45  (p4):stop:5
      15:04:45  (p4):cmd:... p4 client -f -s -t TEMPLATE__SE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-5892-se-swarm-at___
      15:04:45  p4 client -f -s -t TEMPLATE__SE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb
      15:04:45  
      15:04:45  Client jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb not changed.
      15:04:45  
      15:04:45  (p4):stop:6
      15:04:45  (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb
      15:04:45  p4 client -o jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb
      15:04:45  
      15:04:45  (p4):stop:7
      15:04:45  (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb
      15:04:45  p4 client -o jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb
      15:04:45  
      15:04:45  (p4):stop:8
      15:04:45  
      15:04:45  P4 Task: establishing connection.
      15:04:45  ... server: 10.251.245.74:1667
      15:04:45  ... node: se-swarm-at-sa-r0p3m-hxvxb
      15:04:45  P4 Task: cleanup client: jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb
      15:04:45  P4 Task: unsyncing client: jenkins-SE-SWARM_AT_SA-5892-se-swarm-at-sa-r0p3m-hxvxb
      15:04:45  P4 Task: syncing files at change: 0
      15:04:45  (p4):cmd:... p4 sync -f -q /home/jenkins/workspace/SE_SWARM_AT_SA/...@0
      15:04:45  p4 sync -f -q /home/jenkins/workspace/SE_SWARM_AT_SA/...@0
      15:04:45  
      [Pipeline] }
      [Pipeline] // stage
      [Pipeline] }
      [Pipeline] // timestamps
      [Pipeline] }
      [Pipeline] // node
      [Pipeline] }
      [Pipeline] // podTemplate
      [Pipeline] End of Pipeline
      ERROR: script returned exit code 1
      Finished: FAILURE
      

       

            p4paul Paul Allen
            luckyhorang Hokwang Lee
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: