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

Clean Workpace doesn't work for local client setting in PTC Integrity Plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • integrity-plugin
    • None
    • Jenkins ver. 2.46.3
      Integrity-plugin 2.2

      I have just upgraded to Plugin 2.2, and we have had build fail, because they rely on the workspace being cleaned before checkout. This worked fine before, but now with the localClient setting = true, we are finding that the workspace is not being cleaned, files from previous builds are still in the workspace after checkout.

      I have reproduced this issue and it seems to be consistent. I created a simply Pipeline task, the script performs a checkout of a project just containing a few files and the checkout step is configured with the following settings:

      localClient:true, checkpointBeforeBuild: false,  cleanCopy: true, deleteNonMembers: false, fetchChangedWorkspaceFiles: false, restoreTimestamp: false, skipAuthorInfo: false

      I start by deleting the workspace on the master and configure the job to do a checkout as local client.

      I then manually added a folder and file to the workspace.

      I then rerun the task. I observe that despite the clean workspace option being set, the file I added is not deleted.

      The consoleText attached shows that the cleanWorkspace option is true.

       

            integrity_jenkins_plugin PTC ALM
            sharpep_trw Paul Sharpe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: