You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwhisk.apache.org by David P Grove <gr...@us.ibm.com> on 2019/06/30 11:19:02 UTC
automated builds of all runtimes now publishing using `nightly`
The travis setup for all the runtime repos has been changed to use the
nightly tag to indicate the most recent build from the master branch.
I've submitted a PR to update runtimes.json for core repo's master branch
accordingly [1].
My plan is that 48 hours after [1] merges, I will go through all the
runtime images on dockerhub and change the latest tag to refer to the image
that was built from the last official release (1.13.0-incubating). In some
cases (due to image naming convention changes after the 1.13.0-incubating
release), there is no such tag. I believe in most (all?) cases I can
simply do some docker operations to publish the appropriate version of the
old-style name image under the new-style name with the 1.13.0-incubating
tag.
--dave
[1] https://github.com/apache/incubator-openwhisk/pull/4529
Re: Re: automated builds of all runtimes now publishing using `nightly`
Posted by Matt Rutkowski <mr...@us.ibm.com>.
Dave,
You're the best!
Kind regards,
Matt
From: Matt Sicker <bo...@gmail.com>
To: dev@openwhisk.apache.org
Date: 07/01/2019 04:40 PM
Subject: [EXTERNAL] Re: automated builds of all runtimes now
publishing using `nightly`
Fantastic, thanks for handling this!
On Sun, 30 Jun 2019 at 06:19, David P Grove <gr...@us.ibm.com> wrote:
>
>
>
> The travis setup for all the runtime repos has been changed to use the
> nightly tag to indicate the most recent build from the master branch.
>
> I've submitted a PR to update runtimes.json for core repo's master
branch
> accordingly [1].
>
> My plan is that 48 hours after [1] merges, I will go through all the
> runtime images on dockerhub and change the latest tag to refer to the
image
> that was built from the last official release (1.13.0-incubating). In
some
> cases (due to image naming convention changes after the
1.13.0-incubating
> release), there is no such tag. I believe in most (all?) cases I can
> simply do some docker operations to publish the appropriate version of
the
> old-style name image under the new-style name with the 1.13.0-incubating
> tag.
>
> --dave
>
> [1]
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk_pull_4529&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS478q2gZlAJj4Zw&m=TCGf8zwqExer_aEt3hJd5e7UakbpZJQQA9PtUUQUvJE&s=3tnNo1L-7l8N4K9bgs2_7UDDwblXOYJiEchLZMxO5uQ&e=
--
Matt Sicker <bo...@gmail.com>
Re: automated builds of all runtimes now publishing using `nightly`
Posted by Matt Sicker <bo...@gmail.com>.
Fantastic, thanks for handling this!
On Sun, 30 Jun 2019 at 06:19, David P Grove <gr...@us.ibm.com> wrote:
>
>
>
> The travis setup for all the runtime repos has been changed to use the
> nightly tag to indicate the most recent build from the master branch.
>
> I've submitted a PR to update runtimes.json for core repo's master branch
> accordingly [1].
>
> My plan is that 48 hours after [1] merges, I will go through all the
> runtime images on dockerhub and change the latest tag to refer to the image
> that was built from the last official release (1.13.0-incubating). In some
> cases (due to image naming convention changes after the 1.13.0-incubating
> release), there is no such tag. I believe in most (all?) cases I can
> simply do some docker operations to publish the appropriate version of the
> old-style name image under the new-style name with the 1.13.0-incubating
> tag.
>
> --dave
>
> [1] https://github.com/apache/incubator-openwhisk/pull/4529
--
Matt Sicker <bo...@gmail.com>