Pipeline Build Step lightweight checkout?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Pipeline Build Step lightweight checkout?

Steven Foster
Hi there,

I'm using a pattern of split pipelines due to the number of parallel tasks needed and the grouping between them. I have an aggregating "parent" pipeline that kicks off indexing for all of the sub-builds (which are multibranch pipelines) then kicks off the sub-builds themselves.

The aggregate build usesĀ 
agent none
for the entire build.

If I manually trigger one of the sub-builds, it correctly retrieves just the Jenkinsfile and runs the build. The aggregate build (using the build and wait pipeline step) seems like it checks out the repo (once per sub build) onto the master somewhere in order to check the jenkinsfile.

Is it possible to use the same lightweight Jenkinsfile retrieval in a downstream build trigger in pipeline?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/59ed42c8-ef04-439f-8767-1d516e8a1154%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Pipeline Build Step lightweight checkout?

Steven Foster
Nevermind me, I'm a liar. When I added the aggregate build I also switched from a branch build to a PR-Merge build, which necessitates a full checkout to properly resolve the Jenkinsfile I suppose

On Friday, March 9, 2018 at 5:27:37 PM UTC, Steven Foster wrote:
Hi there,

I'm using a pattern of split pipelines due to the number of parallel tasks needed and the grouping between them. I have an aggregating "parent" pipeline that kicks off indexing for all of the sub-builds (which are multibranch pipelines) then kicks off the sub-builds themselves.

The aggregate build usesĀ 
agent none
for the entire build.

If I manually trigger one of the sub-builds, it correctly retrieves just the Jenkinsfile and runs the build. The aggregate build (using the build and wait pipeline step) seems like it checks out the repo (once per sub build) onto the master somewhere in order to check the jenkinsfile.

Is it possible to use the same lightweight Jenkinsfile retrieval in a downstream build trigger in pipeline?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5c01fc7b-2581-41f0-811f-f69f8ee73ca4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.