Use stackbrew to generate version list

[ndeloof]

No description provided.

[ndeloof]

I can't see what's wrong in travis log (no error is reported on log)

[md5]

It doesn't look right that many of the shas are 40c3e3f46939b9f9dcf8d46e62fa7daa80485588 instead of being distinct by version.

[md5]

The other ones are all 91a58f1b7341ab8a253de7f4dec752d9daebd27b.

[ndeloof]

@md5 I'm using an update script to generate Dockerfile for all versions from a template, so they are all committed as same commit.

[tianon]

The CI failure is unrelated -- it's hitting something in CentOS (so hopefully that means a CentOS update is on the horizon).

My question is why we're listing so many different versions here? Are you actively supporting this many versions? I'm a little confused on what the value add of having them all here is besides management overhead, especially since it's going to give users the idea that they're actively supported releases and that upstream will release fixes to any one of these if there turns out to be an issue in Jenkins itself.

[tianon]

Also, do you have some reference somewhere that I can read about "Jenkins Enterprise by cloudbees" and what makes it different from upstream?

[ndeloof]

Yes, all of them will be supported and updated as the base template evolve to offer fixes / better flexibility. Cloudbees is offering 1 year support so you can expect such amount of versions (jenkins is released every week). Jenkins enterprise is same as LTS (1.xxx.y) with some extra high-availability feature and includes additional plugins with independent upgrade cycles. See www.cloudbees.com

[ndeloof]

Yes, all of them will be supported and updated as the base template evolve
to offer fixes / better flexibility. Cloudbees is offering 1 year support
so you can expect such amount of versions (jenkins is released every week).
Jenkins enterprise is same as LTS (1.xxx.y) and includes additional plugins
with independent upgrade cycles.

Le mar. 2 déc. 2014 18:14, Tianon Gravi notifications@github.com a écrit :

Also, do you have some reference somewhere that I can read about "Jenkins
Enterprise by cloudbees" and what makes it different from upstream?

—
Reply to this email directly or view it on GitHub
#333 (comment)
.

[tianon]

The year of support is really nice, but I'm definitely concerned that this is a divergence from "Jenkins" upstream, and the associated user confusion that's bound to come when users docker run jenkins and they really get "Jenkins Enterprise by cloudbees" which is Jenkins plus some extra stuff.

(Which, if that extra stuff is really great for the general user of Jenkins, why is it not included in Jenkins upstream by default?)

[ndeloof]

Right. That makes sense. I'll remove this and create a new pull-request for jenkins releases and publish cloudbees version under cloudbees github org.

[tianon]

Awesome, thanks @ndeloof! ❤️