Re: Pipelines, github fork models and the Jenkinfile

This plugin is letting me do everything I wanted. https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Integration+Plugin The plugin lets me trigger pipelines based on pull request triggers from github without imposing any conventions on files that needs to be present in the source trees. I then

Re: Pipelines, github fork models and the Jenkinfile

On Tuesday, August 16, 2016 at 12:17:44 AM UTC+5:30, Jesse Glick wrote: > > On Sunday, August 14, 2016 at 1:28:50 AM UTC-4, Arvind Jayaprakash wrote: >> >> A world wherein the following can happen is god enough >>> >> >>- "jenkins team" is able to offer pipelines with restricted set of >>

Re: Pipelines, github fork models and the Jenkinfile

On Sunday, August 14, 2016 at 1:28:50 AM UTC-4, Arvind Jayaprakash wrote: > > A world wherein the following can happen is god enough >> > >- "jenkins team" is able to offer pipelines with restricted set of >configuration points >- "development team" exercises these configs through a

Re: Pipelines, github fork models and the Jenkinfile

It appears that having the ghprb trigger be pipeline compatible might solve my problems. Most of the other triggers seem to have been ported to be pipeline compatible. On Saturday, August 13, 2016 at 9:02:07

Re: Pipelines, github fork models and the Jenkinfile

Comments inline On Sunday, August 14, 2016 at 7:05:57 AM UTC+5:30, Mark Waite wrote: > > I don't think what you want is available. > > You can construct a job which defines the pipeline script for execution in > that job. > This is straightforward as the existing job dsl plugin permits

Re: Pipelines, github fork models and the Jenkinfile

I don't think what you want is available. You can construct a job which defines the pipeline script for execution in that job. You can construct a job which automatically defines jobs for every branch where it finds a pipeline script and it will execute that script. You can construct a job

Pipelines, github fork models and the Jenkinfile

I seem to have developed a love/hate relationship with Jenkins 2.x pipelines and some of the concepts that it imposes. Hence, I'd like to hear how best operate in the new world. The one thing I'd like to make clear before I get into the details is that I am suggesting that this the only right