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
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRxA3zbkBrZ1%3D6fOuWxWjyj7eHxV0WX_MnNbp6P1k7qhw%40mail.gmail.com.
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.