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

Cleanup plugin doesn't work with artifact deployer - the clean up order is wrong

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • None
    • Jenkins v1.518

      Hi there,

      The workspace cleanup plugin does not work with with Artifact Deployer plugin.

      Here's my situation:

      Each element of my matrix project runs and I archive artifacts such as "Engine/Lib/*/.lib". My Artifact deployer settings tell the system to copy "Engine/Lib/*/.lib" to "C:\Engine".
      When each element of the matrix finishes I see:

      12:28:52 Archiving artifacts
      12:28:52
      12:28:52 Deleting project workspace...
      12:28:53 done

      in the console log. In the console log for the parent job I see:

      12:28:53 [ArtifactDeployer] - Starting deployment from the post-action ...
      12:28:53 [ArtifactDeployer] - 0 file(s) have been copied from the 'C:\JCI\jobs\Expat-Live\workspace\CONFIG\Release\TARGET\x64\VS\10.0' to 'C:\tom'.
      12:28:53 [ArtifactDeployer] - [ERROR] - Failed to deploy. Can't find any artifacts to deploy with the following configuration :[includes:Engine/Lib/**/*.lib,excludes:,basedir:C:\JCI\jobs\Expat-Live\workspace\CONFIG\Release\TARGET\x64\VS\10.0,outPath:C:\Engine]
      12:28:53 null
      12:28:53 Interrupting #55
      12:28:53 Interrupting #55
      12:28:53
      12:28:53 Deleting matrix project workspace...
      12:28:53 done

      The clean up plugin has removed the files the artifact deployer is trying to get. Can the cleanup of the matrix elements happen after the artifact deployer plugin has run? The workspace cleanup should be last thing that's run as a post build step, first for the matrix elements, then the parent.

      Can you please fix this as it's a major blocker for us?

      Regards,
      Tom

          [JENKINS-18333] Cleanup plugin doesn't work with artifact deployer - the clean up order is wrong

          Thomas Fields added a comment -

          Can anyone even acknowledge this is a bug?

          Cheers,
          Tom

          Thomas Fields added a comment - Can anyone even acknowledge this is a bug? Cheers, Tom

          vjuranek added a comment -

          Hi,
          ws cleanup run after artifact deployer. The problem is, if I get it right, that ws clenaup is called for each matrix combination while artifact deployer is called only for matrix parent. As matrix aggregators are called after all sub-jobs are finished, workspace of sub-jobs are already removed so there's nothing to deploy. I can implement an option to skip cleanup on matrix sub-jobs but IMHO make more sense to run artifact deployer on each matrix sub-job.

          vjuranek added a comment - Hi, ws cleanup run after artifact deployer. The problem is, if I get it right, that ws clenaup is called for each matrix combination while artifact deployer is called only for matrix parent. As matrix aggregators are called after all sub-jobs are finished, workspace of sub-jobs are already removed so there's nothing to deploy. I can implement an option to skip cleanup on matrix sub-jobs but IMHO make more sense to run artifact deployer on each matrix sub-job.

          Thomas Fields added a comment -

          Makes sense. I'll attempt to reassign this to the artifact deployer project.

          Thomas Fields added a comment - Makes sense. I'll attempt to reassign this to the artifact deployer project.

          Thomas Fields added a comment -

          Hi Gregory,

          Are we talking sense in this issue or do you disagree with the suggested fix?

          Thanks,
          Tom

          Thomas Fields added a comment - Hi Gregory, Are we talking sense in this issue or do you disagree with the suggested fix? Thanks, Tom

          Daniel Tehranian added a comment - - edited

          I got bit by this today. Any suggested work-around?

          Daniel Tehranian added a comment - - edited I got bit by this today. Any suggested work-around?

          Gigi Lentini added a comment -

          Hi,
          any news about that?
          I have seen trough the comments in the main page a workaround could be to use the 'deploy artifacts' build step, but I don't have it in the list (using Jenkins 1.565.1 and latest plugin version).

          Cheers!

          Gigi Lentini added a comment - Hi, any news about that? I have seen trough the comments in the main page a workaround could be to use the 'deploy artifacts' build step, but I don't have it in the list (using Jenkins 1.565.1 and latest plugin version). Cheers!

            gbois Gregory Boissinot
            tfields Thomas Fields
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: