So, we have a "latest-jdk8" tag in
https://hub.docker.com/r/jenkins/jenkins-experimental/tags/ now.
I will create a PR to jenkins.io later to reference this experimental image
source
On Thu, Oct 4, 2018 at 9:20 AM Oleg Nenashev wrote:
> https://github.com/jenkinsci/jenkins/pull/3670
>
> On
https://github.com/jenkinsci/jenkins/pull/3670
On Tuesday, October 2, 2018 at 12:46:25 PM UTC+2, Oleg Nenashev wrote:
>
> > > and stable-* branches
>
> > I see no need for that. This is “experimental” after all. If you want
> to experiment, you are not an LTS user.
>
> No need for LTS for
> > and stable-* branches
> I see no need for that. This is “experimental” after all. If you want
to experiment, you are not an LTS user.
No need for LTS for sure. But it could be a good addition for RC testing.
Currently we ship only WAR files for RC, Docker images could help us to get
more
On Sat, Sep 29, 2018 at 1:02 PM Oleg Nenashev wrote:
> Build happens before ci.jenkins.io completes the build/test cycle
Does not seem like a serious issue. It is marked experimental after
all, and we assume that commits in `master` are nothing more than
merges of PRs which were already tested.
Hi all,
As a part of Jenkins & Java 10+ work, I have created a simple CD flow for
Docker images so that we were able to quickly deliver patches in
java10-support and java11-support branches. I have just added multi-stage
Dockerfile
