Minor When the plugin is polling the scm for change it creates a workspace (typically jenkins-master-JOBNAME)
The build itself create another workspace with the corresponding node name (typically jenkins-builder04-JOBNAME) that is correctly deleted at the end of the build if enabled in post build step
Is it really necessary to have a workspace created to poll the scm for change?
[JENKINS-48902] SCM Polling for change create workspace
David Levy
created issue -
David Levy
made changes -
| Description |
Original:
When the plugin is polling the scm for change it creates a workspace (typically jenkins-master-JOBNAME) The build itself create another workspace with the corresponding node name. Is it really necessary to have a workspace created to poll the scm for change? |
New:
When the plugin is polling the scm for change it creates a workspace (typically jenkins-master-JOBNAME) The build itself create another workspace with the corresponding node name. (typically jenkins-builder04-JOBNAME) Is it really necessary to have a workspace created to poll the scm for change? |
David Levy
made changes -
| Description |
Original:
When the plugin is polling the scm for change it creates a workspace (typically jenkins-master-JOBNAME) The build itself create another workspace with the corresponding node name. (typically jenkins-builder04-JOBNAME) Is it really necessary to have a workspace created to poll the scm for change? |
New:
When the plugin is polling the scm for change it creates a workspace (typically jenkins-master-JOBNAME) The build itself create another workspace with the corresponding node name (typically jenkins-builder04-JOBNAME) that is correctly deleted at the end of the build if enabled in post build step Is it really necessary to have a workspace created to poll the scm for change? |