X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-ed1-f68.google.com (mail-ed1-f68.google.com [209.85.208.68]) by lists.alpinelinux.org (Postfix) with ESMTP id E8724F81497 for ; Tue, 19 Feb 2019 01:39:31 +0000 (UTC) Received: by mail-ed1-f68.google.com with SMTP id 10so15356389eds.7 for ; Mon, 18 Feb 2019 17:39:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UlembEjdGj6XS07YuHGiMy1a9SqfTP7XC4wLXFkH9LM=; b=oaYAT2ewGxGh2aiQvo5+qy7VvvMIz/9AUFNuPIaygrUY8ikOA6lBnXG32m4rsQp6NJ PCnNcBUarra+cMFiRhb76twOKGFXaXURjvMU/3x8Ozua0fCG1mIY+Z4hMQ7F2U2elsrC euvzRSMzuLxkerjR4cEqGM3EtZFXpPHkYMq3Zw8QBwCRqAvkL9rLM9oMICXbPxhrRq0p SPtqAE3Y7QJN7/elUrlg0JXziwRiGP1vUNZy/mqrz2RfREXTaWRdFMx4AeXXJCEyXg2S RhLlAPF4oJ8ubcyNdxAE07AoAZrYE1CL4HB6q0ZFdpkMKLgjz5Rcd0pPDk1+ykFJtn1p Cc0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UlembEjdGj6XS07YuHGiMy1a9SqfTP7XC4wLXFkH9LM=; b=lXHtHcxYmDr8Og7LAaioKomnlD+/HO159+T3eI2P0NLlBVPbNV82Q8b6W2CJCgcYIX UgIb/ktbIHtzcs1rDeoRn/Q9MaWFhTz71pA9I3ODFsShcrPq3c7XzVMA0/dsT8UVgKtI kNh8BDkbjAPFxpDJQIVKgC0qJ9d471GUVW2kSiePWvCW2RfgtDcNztiA80w3LWUEteGy tm9TZYIk0wotX4AY8qtf07upTyRrKmTwZp1c5gva0Xjmt+4QpiPXZGY8O3WVzG+0KBIZ p/X6eBYhxDn1iCKNBHBgD/yZCtHaap6Rb+nLhUKZJ1bQHKA0Zg6ha/nPKEZxEx52QcX6 a9zQ== X-Gm-Message-State: AHQUAuaQvy3pPcJDdyzTFyBDjY1UIt/pt7iGNhtnMkhWibfkjtGXxAxD PUzUD/cB8hmGegUVrfOzbHYr9leUv3I+58fTO2U= X-Google-Smtp-Source: AHgI3IaFZHS+EXTW1LGOtS3x+DY1MPBkpKvpm7DATtFUmxFAYqZ7LoQn+IfpRC2EOCQvkqzC6qobLo7CQfR5HkuU+0Y= X-Received: by 2002:a50:97fc:: with SMTP id f57mr20274878edb.29.1550540370989; Mon, 18 Feb 2019 17:39:30 -0800 (PST) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 References: <20190218102658.GA14592@stiletto> In-Reply-To: <20190218102658.GA14592@stiletto> From: Robert Hencke Date: Mon, 18 Feb 2019 20:39:18 -0500 Message-ID: Subject: Re: [alpine-devel] seeking advice of build automation and keeping git synced To: scrumpyjack@st.ilet.to Cc: alpine-devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="00000000000005d97a058235508e" --00000000000005d97a058235508e Content-Type: text/plain; charset="UTF-8" Hey scrumpyjack, If I understand correctly, what you want is a process that takes the latest work from your repository, combines it with the latest work on xeyes in sports, and builds the result? Thanks, Rob On Mon, Feb 18, 2019, 5:27 AM wrote: > hi folks. > > I'm attempting to automate my builds of packages, using gitea+drone > > Here is a sample build for xeyes > > https://gogs.bigyellowfish.com/scrumpyjack/xeyes > > The pipeline goes as follows. > When stuff gets pushedi to the above repo, a githook triggers the drone > build. > Drone uses docker images as a starting point, alpine:edge in this case, > and you can see the build steps in .drone.yml. > The last bit formats a patch, which cna be sent to the aports mailing > list. > > What I'm struggling with is how to keep that xeyes repo in sync with > https://git.alpinelinux.org/aports/tree/community/xeyes > so that changes anyone else makes get applied to my local xeyes repo. > > Anyone with better git skills than me have any advice? > > Perhaps there is a better way of doing this (i'd like to stick with > drone though)? > > -- > Not sent from a tablet or smartphone. > > > --- > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > Help: alpine-devel+help@lists.alpinelinux.org > --- > > --00000000000005d97a058235508e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey scrumpyjack,

If I understand correctly, what you wan= t is a process that takes the latest work from your repository, combines it= with the latest work on xeyes in sports, and builds the result?
=
Thanks,
Rob

On Mon, Feb 18, 2019, 5:27 AM <scrumpyjack@st.ilet.to> wrote:
hi folks.

I'm attempting to automate my builds of packages, using gitea+drone

Here is a sample build for xeyes

https://gogs.bigyellowfish.com/scrumpyjack/xeyes=

The pipeline goes as follows.
When stuff gets pushedi to the above repo, a githook triggers the drone build.
Drone uses docker images as a starting point, alpine:edge in this case, and you can see the build steps in .drone.yml.
The last bit formats a patch, which cna be sent to the aports mailing
list.

What I'm struggling with is how to keep that xeyes repo in sync with https://git.alpinelinux.org/aports/tree/commu= nity/xeyes
so that changes anyone else makes get applied to my local xeyes repo.

Anyone with better git skills than me have any advice?

Perhaps there is a better way of doing this (i'd like to stick with drone though)?

--
Not sent from a tablet or smartphone.


---
Unsubscribe:=C2=A0 alpine-devel+unsubscribe@lists.alpinelinux.or= g
Help:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0alpine-devel+help@lists.alpineli= nux.org
---

--00000000000005d97a058235508e-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---