--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180207212838.ndyahjf7psu5obk2%40blackberry.coupleofllamas.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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180206160253.dkz7whf7h74bda64%40blackberry.coupleofllamas.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 jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180207212838.ndyahjf7psu5obk2%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
Looks good to me.My only concern is mixing three VMs in the one container. Python, node and java... would be nicer if that could be reduced... but ack that it’s non-trivial to do so
On Wed 7 Feb 2018 at 21:28, R. Tyler Croy <ty...@monkeypox.org> wrote:
In the same vein as my previous email, I've written up a design document which
outlines the current approach for packaging I intend to use for Jenkins
Essentials:
https://github.com/jenkinsci/jep/tree/master/jep/301
I think it should be fairly straight-forward and understandable why I'm taking
the approach described, but if there any ambiguity do let me know.
Please take a look at the document and let me know what you think on this
thread :)
Cheers
- R. Tyler Croy
------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
--
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 jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180207212838.ndyahjf7psu5obk2%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
--Sent from my phone
--
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 jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxu9ZkdQJK%3D%2Bq8hj%3DFpHfn81j0eaaPh5dBWo8znuvtiBA%40mail.gmail.com.
2018-02-08 0:14 GMT+01:00 Stephen Connolly <stephen.al...@gmail.com>:Looks good to me.My only concern is mixing three VMs in the one container. Python, node and java... would be nicer if that could be reduced... but ack that it’s non-trivial to do soI agree with this Stephen's comment. I would try to reduce the technology stack to Java (totally needed) and Python.Regards,
On Wed 7 Feb 2018 at 21:28, R. Tyler Croy <ty...@monkeypox.org> wrote:
In the same vein as my previous email, I've written up a design document which
outlines the current approach for packaging I intend to use for Jenkins
Essentials:
https://github.com/jenkinsci/jep/tree/master/jep/301
I think it should be fairly straight-forward and understandable why I'm taking
the approach described, but if there any ambiguity do let me know.
Please take a look at the document and let me know what you think on this
thread :)
Cheers
- R. Tyler Croy
------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
xmpp: rty...@jabber.org
% gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180207212838.ndyahjf7psu5obk2%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
--Sent from my phone
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxu9ZkdQJK%3D%2Bq8hj%3DFpHfn81j0eaaPh5dBWo8znuvtiBA%40mail.gmail.com.
> 2. Scripting should be done via yaml files, not environment variables(
> init.d/groovy). All essential plugins should be made compatible with
> configuration-as-code.
I fully intend on using as much support as possible from the Configuration as
Code effort which Ewelina and Nicolas are working on. I do not intend to
undertake, as part of Jenkins Essentials, patching or updating plugins in order
to support it however.
My order of priority for scripting Jenkins is:
1. Configuration as Code
2. Groovy scripting (bleh)
3. Hopefully very little if any scary hacks.
So I think we're mostly on same page here :)
--
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 jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180214000422.hkio3rohqdgzn4pd%40blackberry.coupleofllamas.com.
--
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 jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180214200627.qqocqne3gynh6msx%40blackberry.coupleofllamas.com.
--
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 jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180207212838.ndyahjf7psu5obk2%40blackberry.coupleofllamas.com.
--
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 jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180206160253.dkz7whf7h74bda64%40blackberry.coupleofllamas.com.
+1, very exciting to make Jenkins operatable by newcomers in a matter of minutes. Having had very recently to drive a newbie to use Jenkins, even if he was very motivated, I think this is a great initiative. The flexibility of Jenkins is a great strength for advanced users, but a real difficulty for newcomers.Though I agree using a watchdog tool like supervisord is not the official and best way to provide a Docker image, at the same time I agree this is a powerful way to make the experience very easy OOTB. I did that in the past for SonarQube, and it worked quite well for our usage.About supervisord specifically though, mostly a NIT/request for clarification: I wonder if the JEP should specify it? I read the reasoning and I understand this can save time and so on to start that work, but for instance if we discover a better alternative now or later, should a part of that JEP which somehow looks like an implementation detail (we mainly need to express we require a watchdog/restart tool don't we). Also/or this is typically a component that could be replaced later if something better surfaces or so?Also, adding another language dependency (python) when you already plan to have the evergreen client in nodejs might make the image bigger than it could be. But well, back to my previous point, this is something that can anyway be improved/changed over time.
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180215174522.ewqpuvbmjxchuj3j%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.