Re: Clone Workspace SCM tar vs. zip

2013-01-01 Thread Vikram Toprani
As a stop-gap solution, I've created a generic job that executes a windows script to rename the 'workspace.tar.gz' to 'workspace.zip' Once the "Archive Workspace" post-build action is complete, this script job can then be triggered using "Parameterized Trigger Build" with the "current job name"

Re: Clone Workspace SCM tar vs. zip

2012-12-31 Thread Vikram Toprani
Hi, I'm running Jenkins LTS v1.480 on Windows Server 2003 SP2. I'm too getting the same issue wherein no matter if I select "Zip" archival mode, it always creates a "workspace.tar.gz" due to which the client build fails with an error: \..\..builds\2012-12-31_15-06-06\workspace.zip (The system c

Re: Clone Workspace SCM tar vs. zip

2012-10-25 Thread Frank Bølviken
Hi, Did you manage to resolve this? I'm currently having the same issues... Was using the tar zipping, but that was so slow, that I wanted to try Zipped. But workspace.zip won't be created. Frank On Monday, 6 February 2012 11:08:51 UTC+1, Dirk Kuypers wrote: > > Hi, > > I just upgraded the Clon

Clone Workspace SCM tar vs. zip

2012-02-06 Thread Dirk Kuypers
Hi, I just upgraded the Clone Workspace SCM plugin this morning and although I configured my main compile job to zip the workspace a .taz.gz file is created. The unit tests following are failing with the following error message: 10:16:42 Started by upstream project "ContestContinuous" build numb