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:


   - https://github.com/constantcontact/jenkins_pipeline_builder 
      - 
      
https://jenkins.io/blog/2018/04/25/configuring-jenkins-pipeline-with-yaml-file/
      - 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 [email protected].
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 via email to