Draft JEP: Configuration as Code

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

Draft JEP: Configuration as Code

nicolas de loof-2
Hi,

Some of you who joined Contributor Summit at Jenkins World'17 already know about the resurrecting effort to provide configuration-as-code for Jenkins management (JENKINS-31094)

Both Praqma and CloudBees have been investigating on this topic last months, and have wrote prototypes to cover this need. As we learned about each other effort we decided to join forces, and make this public as a JEP proposal.

We also wrote a document to explain our goals and design decisions. We used JEP template so we can now propose this for JEP acceptance (I guess this is the right place to do so)

We'll be happy to hear from you about this.

--
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/CANMVJzkqaQPkb_cyg5RAJw9dvpwoAthY%3DbxhdvTSQNHWE4N_ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Draft JEP: Configuration as Code

Oleg Nenashev
Hello,

Would it be possible to stage the plugin in the experimental update center?
I would like to evaluate it for my use-cases, but I need it in the experimental update center to bundle it into my Docker images.

Thanks in advance,
Oleg

вторник, 7 ноября 2017 г., 10:49:59 UTC+1 пользователь nicolas de loof написал:
Hi,

Some of you who joined Contributor Summit at Jenkins World'17 already know about the resurrecting effort to provide configuration-as-code for Jenkins management (JENKINS-31094)

Both Praqma and CloudBees have been investigating on this topic last months, and have wrote prototypes to cover this need. As we learned about each other effort we decided to join forces, and make this public as a JEP proposal.

Our joined prototype is here : <a href="https://github.com/jenkinsci/configuration-as-code-plugin" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fconfiguration-as-code-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEBFSLRRiRNYGWqAZr6GdCRCYi73w&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fconfiguration-as-code-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEBFSLRRiRNYGWqAZr6GdCRCYi73w&#39;;return true;">https://github.com/jenkinsci/configuration-as-code-plugin
We also wrote a document to explain our goals and design decisions. We used <a href="https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/JEP.adoc" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fconfiguration-as-code-plugin%2Fblob%2Fmaster%2FJEP.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG3axVQedY9T6hZtzXM6Sobjkzfwg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fconfiguration-as-code-plugin%2Fblob%2Fmaster%2FJEP.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG3axVQedY9T6hZtzXM6Sobjkzfwg&#39;;return true;">JEP template so we can now propose this for JEP acceptance (I guess this is the right place to do so)

We'll be happy to hear from you about this.

--
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/2dd75307-3df0-4d97-8b2f-2cf159b605ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Draft JEP: Configuration as Code

Jesse Glick-4
On Mon, Nov 20, 2017 at 2:52 AM, Oleg Nenashev <[hidden email]> wrote:
> I would like to evaluate it for my use-cases, but I need it in the
> experimental update center to bundle it into my Docker images.

Maybe you should just change your demo build style to not depend on
the update center. See `workflow-aggregator-plugin/demo/` for an
example.

--
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/CANfRfr2BpTRM40fMWHG_7RhQfWdNocomzmkR7%3DdR0xO8SqkUYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.