From dev-return-1309-archive-asf-public=cust-asf.ponee.io@yetus.apache.org Tue Nov 13 13:17:57 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B66DD18062B for ; Tue, 13 Nov 2018 13:17:56 +0100 (CET) Received: (qmail 59712 invoked by uid 500); 13 Nov 2018 12:17:55 -0000 Mailing-List: contact dev-help@yetus.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@yetus.apache.org Delivered-To: mailing list dev@yetus.apache.org Received: (qmail 59701 invoked by uid 99); 13 Nov 2018 12:17:55 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Nov 2018 12:17:55 +0000 Received: from mail-qk1-f182.google.com (mail-qk1-f182.google.com [209.85.222.182]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id B07752125 for ; Tue, 13 Nov 2018 12:17:54 +0000 (UTC) Received: by mail-qk1-f182.google.com with SMTP id q1so18888052qkf.13 for ; Tue, 13 Nov 2018 04:17:54 -0800 (PST) X-Gm-Message-State: AGRZ1gLNizvxz2PBFloqhf/5dFXWm0tRaAfuEsxLsJligKprWPZA2Ciw +dCV2cysk2N0V3WSfRZrwAQA4OIW4KELSJ7N7QE= X-Google-Smtp-Source: AJdET5ceSPhzOs+XHV8YmpyaYuvYz+YwyDPcsX/LUmi5B0FURzEmTt2gjyiCOK47xdT0OmJE59o+0fxP1BN6Y6COHjQ= X-Received: by 2002:aed:3ae4:: with SMTP id o91mr4707833qte.251.1542111474247; Tue, 13 Nov 2018 04:17:54 -0800 (PST) MIME-Version: 1.0 References: <1FC06CB1-D2B6-4794-8E69-CA230B45CCAE@effectivemachines.com> In-Reply-To: <1FC06CB1-D2B6-4794-8E69-CA230B45CCAE@effectivemachines.com> From: Sean Busbey Date: Tue, 13 Nov 2018 06:17:41 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSS] YETUS-683 To: dev@yetus.apache.org Content-Type: multipart/alternative; boundary="000000000000a07d80057a8acee9" --000000000000a07d80057a8acee9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable How do we delineate between images meant for downstream (i.e. releases) vs those only for use when working on yetus (branches)? On Mon, Nov 12, 2018, 00:53 Allen Wittenauer > > YETUS-683 proposes to start publishing convenience binaries as > images at hub.docker.com. Included with that JIRA is a patch that > provides some (admittedly sparse) documentation on how to take advantage = of > those images. > > My current design is to provide two images: > > apache/yetus-base:(latest|branch|release tag) - Apache > Yetus=E2=80=99 requirements in it > apache/yetus:(latest|branch|release tag) - base+ Apache > Yetus pre-installed in /usr > > We=E2=80=99d take advantage of docker hub=E2=80=99s capabilities = to auto-build for > us so it shouldn=E2=80=99t require much work other than telling infra to = turn it > on. The necessary magic for hub.docker.com to build things sanely (e.g., > apache/yetus:0.9.0 will use apache/yetus-base:0.9.0 and not latest) was > already committed as part of YETUS-15. > > IMHO, I view making these images available as an absolutely > critical part of making Apache Yetus easier to use. In particular, it > should be noted that in order to make Circle CI and Gitlab CI first class > citizens (see YETUS-681), Docker images are pretty much required. > > Any questions/comments/concerns? > > Thanks! > > > --000000000000a07d80057a8acee9--