You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Joan Touzet <wo...@apache.org> on 2020/08/31 18:36:07 UTC
Keeping our CI images live
(Apologies if this is a double-post.)
Some of you who work with Docker may have received an email from them
recently, indicating they will be removing container images that have
not been used within the past 6 months:
https://www.docker.com/pricing/resource-consumption-updates
This isn't an issue for our apache/couchdb and couchdb images, which are
widely in use and popular. (If people stop using 1.x, it might
disappear, but I very much doubt that.)
However, it might affect our CI workflow for older builds. These images
are only pulled when Jenkins needs them. And while we have the
Dockerfiles and build instructions for these older platforms, decay of
URLs and repositories means it may be increasingly difficult to stand up
old environments - on the off chance someone wants to patch something in
e.g. CouchDB 2.1.1, or try to build CouchDB 3.1.0 for Ubuntu 12.04 (good
luck!)
To solve this I've filed this PR which basically pulls every image in
our couchdbdev org. I'm going to run this on a cronjob once a month for
myself:
https://github.com/apache/couchdb-docker/pull/189
I'm also planning on filing a ticket with ASF Infra to ask if there is
an alternative, such as moving these images under the apache org
namespace at Docker Hub. (Previously they informed us we could have a
single image there only, apache/couchdb, with as many tags as we wanted.
Bah humbug.)
Another option is to run our own registry, but that seems like an awful
lot of work, and my goal has always been to reduce the amount of
infrastructure we have to maintain ourselves.
I'll let you know what comes of the ASF Infra ticket.
-Joan "improving our bus factor" Touzet
Re: Keeping our CI images live
Posted by Joan Touzet <wo...@apache.org>.
Thanks, that's interesting.
I also realized I can just put the new shell script into our Jenkins and
have that run it once a month. That's probably the lowest level of effort.
-Joan
On 01/09/2020 16:42, Alessio 'Blaster' Biancalana wrote:
> Hi Joan,
> Thanka for the effort in exploring these possibilities. Along with those,
> we could have another choice:
>
> https://github.blog/2020-09-01-introducing-github-container-registry/
>
> Alessio
>
> Il lun 31 ago 2020, 20:41 Joan Touzet <wo...@apache.org> ha scritto:
>
>> On 31/08/2020 14:36, Joan Touzet wrote:
>>> I'm also planning on filing a ticket with ASF Infra to ask if there is
>>> an alternative, such as moving these images under the apache org
>>> namespace at Docker Hub. (Previously they informed us we could have a
>>> single image there only, apache/couchdb, with as many tags as we wanted.
>>> Bah humbug.)
>>
>> That ticket is here: https://issues.apache.org/jira/browse/INFRA-20795
>>
>> -Joan
>>
>
Re: Keeping our CI images live
Posted by Alessio 'Blaster' Biancalana <do...@apache.org>.
Hi Joan,
Thanka for the effort in exploring these possibilities. Along with those,
we could have another choice:
https://github.blog/2020-09-01-introducing-github-container-registry/
Alessio
Il lun 31 ago 2020, 20:41 Joan Touzet <wo...@apache.org> ha scritto:
> On 31/08/2020 14:36, Joan Touzet wrote:
> > I'm also planning on filing a ticket with ASF Infra to ask if there is
> > an alternative, such as moving these images under the apache org
> > namespace at Docker Hub. (Previously they informed us we could have a
> > single image there only, apache/couchdb, with as many tags as we wanted.
> > Bah humbug.)
>
> That ticket is here: https://issues.apache.org/jira/browse/INFRA-20795
>
> -Joan
>
Re: Keeping our CI images live
Posted by Joan Touzet <wo...@apache.org>.
On 31/08/2020 14:36, Joan Touzet wrote:
> I'm also planning on filing a ticket with ASF Infra to ask if there is
> an alternative, such as moving these images under the apache org
> namespace at Docker Hub. (Previously they informed us we could have a
> single image there only, apache/couchdb, with as many tags as we wanted.
> Bah humbug.)
That ticket is here: https://issues.apache.org/jira/browse/INFRA-20795
-Joan