[JIRA] [core] (JENKINS-17813) Jobs should have built in option to never clean workspace

Tue, 20 May 2014 06:22:49 -0700

For future reference, we ended up working around our original use case using symbolic links, something like this:

  1. Setup Jenkins job to monitor source files in SVN
  2. Run the job once on the agent of choice
  3. Log into remote machine and make symbolic links to the appropriate files / folders in the appropriate locations (e.g.: mklink "%userprofile%\project.settings" "c:\jenkins\workspaces\job_folder\project.settings" )

Then the files and folders exist within the Jenkins workspace realm, their sources can be monitored directly in the SCM and kept up to date automatically, without requiring further human intervention. Also deleting and restoring the files leaves the symbolic links largely unaffected - so long as you take care not to run tasks in parallel that may require access to those artifacts.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to