Thanks, I’ll keep an eye on JENKINS-33273.
Perhaps looking for @script is a short term fix after all. Then I can limit
the checkout to just the Jenkinsfile.
> On 1 Jun 2016, at 17:52, Jesse Glick wrote:
>
> On Wed, Jun 1, 2016 at 12:46 PM, Paul Allen wrote:
>> The root directory of ‘src’ co
On Wed, Jun 1, 2016 at 12:46 PM, Paul Allen wrote:
> The root directory of ‘src’ contains the ‘Jenkinsfile' and say for arguments
> sake a game engine of 100K files (500 GB of space).
>
> Currently I end up syncing 500GB twice once in 'projA@script/' and again in
> ‘projA/‘, that is rather expen
In the SCM configuration I specify what path(s) to fetch from the SCM e.g.
//depot/projA/src/...
The root directory of ‘src’ contains the ‘Jenkinsfile' and say for arguments
sake a game engine of 100K files (500 GB of space).
Currently I end up syncing 500GB twice once in 'projA@script/' and ag
On Wed, Jun 1, 2016 at 8:15 AM, pallen wrote:
> how does the 'p4' plugin know how to checkout? It gets called with the same
> configuration used in the first stage, so all you end up with is a workspace
> directory 'jobName/' and just the Jenkinsfile?
Well presumably there is something in the rep
Hi Guys,
I'm updating the pipeline support for the 'p4' plugin and trying to workout
how the plugin should react to the two stages of checkout.
For example: creating a pipeline Job, then configuring 'Pipeline Script
from SCM' and providing the details of where to get the Jenkinsfile.
The first
