Leave pushed package on Workstation

Follow

Smalone

• April 04, 2013 15:26

Is it possible once a package is pushed to leave the package "cached" on the workstation after it copies?  Reason being so that if I have a machine fail, I don't have to copy the entire package back down to the workstation.

0

• 

  TonsOFun

  • April 04, 2013 16:26

  It copies it every time you deploy. 

  At least with my experience it does. 

  To get around this, here's my logic if you'd like to do this. 

  Create a deploy package with 3 steps. 

  Step 1. Use the XCOPY/COPY command to copy the installation files to a directory (TEMP/CACHED)

  Step 2. Run the installation. Make sure that "Stop deployment if this step fails" is checked. 

  Step 3. Delete the TEMP/CACHED directory

   

  Logic: If the workstation successfully gets the install, it will clear the directory. 

  If the workstation fails to get the install, Step 3 will be skipped, leaving the install in the temp directory for you. 

  Hope this helps. 

  0

  Comment actions Permalink
• 

  Shane Corellian

  • April 04, 2013 17:11

  Hi, as TonsOfFun eluded caching is not a native feature of Deploy. We do have this feature on our Roadmap.

  0

  Comment actions Permalink
• 

  Smalone

  • April 26, 2013 16:52

  Thank You guys for the guidance!  Much Appreciated!

  0

  Comment actions Permalink
• 

  Dana Lehman

  • January 17, 2020 18:06

  I know this is an old thread, but it has another vote.  Is it still on the road map?

  I've used robocopy to do similar in the past.  The two packages I'm looking at is Adobe CC and Autodesk.  My Adobe CC package is 7GB and keeps failing on one machine.  Half the deployment time is file copy.  

   

  Thanks,

  0

  Comment actions Permalink

Please sign in to leave a comment.