Simple pull request job plugin (GSOC 2018 project)

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Simple pull request job plugin (GSOC 2018 project)

Abhishek Gautam
Previous discussion,

By Oleg Nenashev,

Hi all,

I suggest to think a bit about the repo name. IMHO the proposed design needs some discussion.

Over last weeks I did some surveys about existing Jenkins & YAML projects. Here are some ones I discovered:

These things maybe interesting for you to research while designing the project. Although there are such "competing" projects, IMHO it even makes this GSoC project much more relevant and impactful if the project is integrated with Pipeline ecosystem. Offering such YAML support OOTB in Pipeline ecosystem may be a blockbuster actually.

One of the ways I see it:

    • Implement one of existing YAML => Pipeline engines, as FlowDefinition and ScmFlowDefinition for Pipeline
      • It would give integration with the Pipeline ecosystem and give your project tremendous amount of features OOTB
    • Work on YAML in order to offer more integrations and syntax sugar
    • Another interesting option could be YAML => Declarative Pipeline, which could use the same approaches as above

WDYT? i have also added Nicolas De Loof (CodeShip plugin creator) to CC. He may have some inputs.

Best regards,
Oleg

By Nicolas de loof

For the record, I created codeship plugin as a proof of concept to bring a simpler, yaml based model to Jenkins. It consumes yaml as a FlowDefinition to produce equivalent CPS script, as this was the shortest path. For a longer terms implementation I'd like it just implement those steps by itself without any CPS stuff running in the background, just running containers and waiting for them to complete.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/4c9250cf-7fb8-4d9d-97af-0852c855b719%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Simple pull request job plugin (GSOC 2018 project)

j.knurek
For those new to the thread, here's a link to the GSoC project https://jenkins.io/projects/gsoc/2018/simple-pull-request-job-plugin/ 
which has a further link to the details of the proposal. 

------------ 

Those are definitely good topics as starting points, thanks Oleg.

There was some other discussion in the Kubernetes Plugin recently regarding adding yaml usage in pipeline configuration.
First there was this PR to allow for k8s yaml configuration to define the pod setup using this plugin: https://github.com/jenkinsci/kubernetes-plugin/pull/275

But in a PR about two weeks ago, there was a comment that Andrew Bayer was questioning the usage of yaml:
https://github.com/jenkinsci/kubernetes-plugin/pull/306#issuecomment-380253762
(these PRs are not as related as the links from Oleg, but they should still be considered with this project)

---------------

My understanding is that we have just a week before work needs to be started on the project, so maybe a long deep discussion of the repo name shouldn't block the starting of work. But instead we create a repo with the original GSoC project name, with the potential that it needs to be renamed before the project completes. Is that an option?

/Jeff 


On Thursday, 26 April 2018 21:57:29 UTC+2, Abhishek Gautam wrote:
Previous discussion,

By Oleg Nenashev,

Hi all,

I suggest to think a bit about the repo name. IMHO the proposed design needs some discussion.

Over last weeks I did some surveys about existing Jenkins & YAML projects. Here are some ones I discovered:
    • <a href="https://github.com/constantcontact/jenkins_pipeline_builder" style="color:rgb(17,85,204)" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fconstantcontact%2Fjenkins_pipeline_builder\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGXY8bcZUD-yTNbO6v0ExdOTQQojg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fconstantcontact%2Fjenkins_pipeline_builder\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGXY8bcZUD-yTNbO6v0ExdOTQQojg&#39;;return true;">https://github.com/constantcontact/jenkins_pipeline_builder 
    • <a href="https://jenkins.io/blog/2018/04/25/configuring-jenkins-pipeline-with-yaml-file/" style="color:rgb(17,85,204)" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2018%2F04%2F25%2Fconfiguring-jenkins-pipeline-with-yaml-file%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFUEsn5Vs2NBR71DwI-wHrCdl2SHw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2018%2F04%2F25%2Fconfiguring-jenkins-pipeline-with-yaml-file%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFUEsn5Vs2NBR71DwI-wHrCdl2SHw&#39;;return true;">https://jenkins.io/blog/2018/04/25/configuring-jenkins-pipeline-with-yaml-file/
    • <a href="https://github.com/ndeloof/codeship-plugin" style="color:rgb(17,85,204)" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fndeloof%2Fcodeship-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHyhK0FMbBcWrHQSaYIj68BrmpkOw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fndeloof%2Fcodeship-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHyhK0FMbBcWrHQSaYIj68BrmpkOw&#39;;return true;">https://github.com/ndeloof/codeship-plugin (executing CodeShip YAML in Pipeline)

These things maybe interesting for you to research while designing the project. Although there are such "competing" projects, IMHO it even makes this GSoC project much more relevant and impactful if the project is integrated with Pipeline ecosystem. Offering such YAML support OOTB in Pipeline ecosystem may be a blockbuster actually.

One of the ways I see it:

    • Implement one of existing YAML => Pipeline engines, as FlowDefinition and ScmFlowDefinition for Pipeline
      • It would give integration with the Pipeline ecosystem and give your project tremendous amount of features OOTB
    • Work on YAML in order to offer more integrations and syntax sugar
    • Another interesting option could be YAML => Declarative Pipeline, which could use the same approaches as above

WDYT? i have also added Nicolas De Loof (CodeShip plugin creator) to CC. He may have some inputs.

Best regards,
Oleg

By Nicolas de loof

For the record, I created codeship plugin as a proof of concept to bring a simpler, yaml based model to Jenkins. It consumes yaml as a FlowDefinition to produce equivalent CPS script, as this was the shortest path. For a longer terms implementation I'd like it just implement those steps by itself without any CPS stuff running in the background, just running containers and waiting for them to complete.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/6a129755-ef7b-42a0-98d0-738a1144e7e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Simple pull request job plugin (GSOC 2018 project)

Martin d'Anjou
Hi Abhishek, Kristin, Jeff and Oleg,

We held the first community bonding meeting today on Simple Pull-Request Plugin (SPRP), and I captured some notes.
Anyone with the link can comment, if I have missing something let me know via a comment. If capturing notes like this becomes too much of a burden, we'll revise this decision.

Best,
Martin

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/bc1fb66c-d702-41f0-a537-fe91345fdabb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.