openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Santana <>
Subject Re: "nightly" releases of clis (was Graduation)
Date Fri, 07 Dec 2018 15:26:45 GMT
This are nightly builds for cicd integration.

We don’t link to them or document them from our website.

Your suggesting that when we do the next source release with a new version
of the CLI we always include a disclaimer clarifying that the nightly
binary “latest” is not the released version it should not be use, that
users to get the released need to go to the website download page and the
correct artifacts will be linked there

On Thu, Dec 6, 2018 at 11:40 AM Bertrand Delacretaz <>

> Hi Dave,
> On Thu, Dec 6, 2018 at 4:40 PM David P Grove <> wrote:
> >> ...I haven't checked all OpenWhisk repositories but there's also at
> least
> > >
> >
> > Here I think the problem is the 'latest' tag/release.  This is actually a
> > nightly build that we need to publish somewhere so that other parts of
> our
> > CI/CD pipeline can pick up pre-built CLIs...
> Ok, got it. Nightly builds are fine, and having them named "latest" is
> ok as far as I'm concerned but their purpose should be documented in
> the OpenWhisk release instructions so that the intention is clear.
> As per such
> builds "should not be hosted or linked on pages intended for end
> users" so I think having them in GitHub repositories is fine, that's
> clearly a place for developers.
> On the other hand, as you mention, the mix of such builds with Apache
> Releases and "other" releases like at
> needs
> to be addressed, and OpenWhisk release instructions probably need an
> update to clarify what goes where.
> Thanks for your prompt reply on this!
> -Bertrand
Carlos Santana

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message