Hi Oleg, I went through the demo showing Continuous Delivery pipeline implementation: https://github.com/jenkinsci/workflow-aggregator-plugin/tree/master/demo
And also I tried to look at some scenarios, I felt it is some what different from previous what Jenkins giving in before versions. To have a better understanding of this I asked for use cases which were considered while implementing. I am preparing my observations regarding this. Thanks, Suresh On Saturday, April 30, 2016 at 6:35:50 PM UTC+5:30, Oleg Nenashev wrote: > > Here are several links: > > - Everything as code concept: > https://speakerdeck.com/garethr/everything-as-code > - Delivery Pipeline: > http://www.informit.com/articles/article.aspx?p=1621865&seqNum=2 > - Pipeline in Jenkins: https://jenkins.io/solutions/pipeline/ > > If you google for "Everything as Code" and "Configuration as Code", you > will find many articles explaining the concept. Pipeline as code is "just" > a way to describe automation flows in Jenkins in such way. > > вторник, 26 апреля 2016 г., 17:26:53 UTC+2 пользователь suresh kumar > написал: >> >> Thanks Antonio, >> For the information. Actually I am looking at real time use cases and >> scenarios of complex flows. There might be some specs against to the >> Pipeline as code, if there I want to go through those specs. >> >> Thanks, >> Suresh >> On 26 Apr 2016 6:37 pm, "Antonio Muñiz" <[email protected]> wrote: >> >>> Hello, >>> >>> You can find some examples in this repository: >>> https://github.com/jenkinsci/pipeline-examples >>> And there is a demo showing Continuous Delivery pipeline >>> implementation: >>> https://github.com/jenkinsci/workflow-aggregator-plugin/tree/master/demo >>> >>> On Mon, Apr 25, 2016 at 6:02 PM, suresh kumar <[email protected]> >>> wrote: >>> > Hi Team, >>> > If any use cases and scenarios driven to arrive at Pipeline as a code, >>> > please share I would like to understand and analyze the concepts. >>> > >>> > Please add thoughts and scenarios here. >>> > >>> > Thanks in advance. >>> > Suresh >>> > >>> > -- >>> > 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/aee10e1e-e010-4366-93da-57e7e3f8a1b9%40googlegroups.com >>> . >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> Antonio Muñiz >>> Software Engineer >>> CloudBees, Inc. >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Jenkins Developers" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-dev/6Iw0lmnIRwc/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRxA3zbkBrZ1%3D6fOuWxWjyj7eHxV0WX_MnNbp6P1k7qhw%40mail.gmail.com >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- 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/ee127523-3fed-4740-982c-01ffe50528e3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
