I've assigned Tyler as the BDFL delegate of this JEP-301, given that I
consider him the leader of this effort.
On Thu, Feb 15, 2018 at 9:45 AM R. Tyler Croy wrote:
> (replies inline)
>
> On Thu, 15 Feb 2018, Carlos Sanchez wrote:
>
> > yay! +1
> >
> > I agree with previous comments that it is no
(replies inline)
On Thu, 15 Feb 2018, Carlos Sanchez wrote:
> yay! +1
>
> I agree with previous comments that it is not ideal to run multiple
> processes and that in a kubernetes world this would possibly be a Pod with
> two containers, but I think it's important to get something out and
> itera
yay! +1
I agree with previous comments that it is not ideal to run multiple
processes and that in a kubernetes world this would possibly be a Pod with
two containers, but I think it's important to get something out and
iteratively improve.
A decent user experience today means just one container an
(replies inline)
On Wed, 14 Feb 2018, Jesse Glick wrote:
> On Tue, Feb 13, 2018 at 7:03 PM, R. Tyler Croy wrote:
> > I have been thus far deriving jenkins/evergreen from
> > jenkins/jenkins simply to inherit some scripts, permissions, and other bits.
>
> Yeah, that makes sense as a way to get t
On Tue, Feb 13, 2018 at 7:03 PM, R. Tyler Croy wrote:
> I have been thus far deriving jenkins/evergreen from
> jenkins/jenkins simply to inherit some scripts, permissions, and other bits.
Yeah, that makes sense as a way to get things up and running quickly.
Once we have an accepted process for ta
The proposal looks good to me.
Also +1 for the JEP-300 writeup. My suggestion would be to also create an
Evergreen subproject page once it is approved.
BR, Oleg
среда, 14 февраля 2018 г., 8:39:26 UTC+1 пользователь Manuel Recena Soto
написал:
>
>
>
> 2018-02-08 0:14 GMT+01:00 Stephen Connolly
2018-02-08 0:14 GMT+01:00 Stephen Connolly
:
> 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
>
I agree with this Stephen's comment. I would try to redu
Hello Tyler,
A great document.
Regards,
2018-02-07 22:28 GMT+01:00 R. Tyler Croy :
> 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/
(replies inline)
On Thu, 08 Feb 2018, Jesse Glick wrote:
> https://github.com/jenkinsci/jep/blob/master/jep/301/README.adoc#plugins
>
> does not make sense to me. A critical benefit of this system as I
> understood it was that we could deliver a complete software
> package???including Jenkins co
BTW
On Thu, Feb 8, 2018 at 5:16 PM, Jesse Glick wrote:
> why are you treating core and plugins as distinct things?
was meant as a fairly technical comment about the packaging design.
The goal here makes a lot of sense.
On this topic, is there any information on how you would propose new
snapsh
https://github.com/jenkinsci/jep/blob/master/jep/301/README.adoc#plugins
does not make sense to me. A critical benefit of this system as I
understood it was that we could deliver a complete software
package—including Jenkins core and plugins—as a unit. So why are you
treating core and plugins as d
(replies inline)
On Wed, 07 Feb 2018, Stephen Connolly wrote:
> 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
I understand the desire to reduce dep
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 wrote:
> In the same vein as my previous email, I've written up a desi
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 takin
14 matches
Mail list logo
