Re: fdio/release repository on packagecloud now contains 19900 with some odd artifacts
Dave Wallace (dwallace) <dwallace@...>
Thank you for the excellent write-up on our meeting!
@Ed Warnicke, can you please create the hicn repo on packagecloud.io (https://packagecloud/fdio/hicn)?
From: Luca Muscariello <muscariello@...>
Sent: Thursday, June 18, 2020 2:43 AM
To: Andrew 👽 Yourtchenko <ayourtch@...>; Vanessa Valderrama <vvalderrama@...>; Dave Wallace (dwallace) <dwallace@...>; tsc@...
Cc: hicn-dev@...; cicn-dev@...; ci-management-dev@...
Subject: Re: [tsc] fdio/release repository on packagecloud now contains 19900 with some odd artifacts
After meeting with Andrew, Dave and Vanessa, we have decided to
opt for option 4 described in this thread. Tradeoffs have been
explained in this thread.
This decision requires
- the creation of a new repo https://packagecloud/fdio/hicn;
- update to ci-management on hicn JJB to push artifacts there;
- therefore previous releases are pushed manually to
https://packagecloud/fdio/release via LF tickets.
- clean up the release repo to keep actual releases only (there is
a ci-management patch written by Mauro for this);
- lockdown releases from JJB push;
- https://packagecloud/fdio/attic is used by ci-management to cleanup
release/ but it may be used to cleanup fdio/hicn at stationary
regime in the long term.
- merge the ci-management cleanup job
- create new packagecloud repo
- update hicn ci-management
- lockdown release
On Fri, Jan 31, 2020 at 9:51 AM Luca Muscariello <muscariello@...> wrote: