[Pulp-dev] CI/CD meeting minutes
mdellweg at redhat.com
Wed Mar 31 14:50:10 UTC 2021
On Wed, Mar 31, 2021 at 4:42 PM Brian Bouterse <bmbouter at redhat.com> wrote:
> On Wed, Mar 31, 2021 at 10:34 AM Fabricio Aguiar <faguiard at redhat.com>
>> ## March 31, 2021
>> * Github Actions
>> * good overall
>> * faster and more reliable so far than Travis
>> * easier to debug with tmate action
>> * downsides
>> * virtualization
>> * not possible to re-run individual jobs
>> * https://github.com/actions/runner/issues/432
>> * people need write permission to re-run CI
>> * https://github.com/actions/runner/issues/841
>> * workaround: `git commit --amend`, no changes, force push
>> * Release automation https://pulp.plan.io/issues/8093
>> * Availability
>> * Mike after operator?
>> * David has ~1 FTE
>> * Fabricio? Not sure. Maybe 0.5 FTE.
>> * Dkliban?
>> * First goal? https://pulp.plan.io/issues/7868
>> * [david] to write up design
>> * Regular CI/CD meeting?
>> * Every other Wednesday 9:30-9:55am (15:30 EST)
>> * [david] to schedule
>> * Convert CI/CD code to ansible playbook?
>> * Benefits: idempotence, easier to run locally
>> * *Big* rewrite
> I'm a little worried about this even besides its effort. One of my worries
> if we switch to Ansible is that not everyone knows it. If folks have to
> learn a new technology that's another barrier to usage. I've seen this
> happen with the installer already to some extent.
Def valid concern. OTOH this was (and it is missing from the benefits) also
driven by the idea that our current CI is understood only by a handful of
people. And that would vastly improve if you could run that locally and see
where it breaks.
>> Best regards,
>> Fabricio Aguiar
>> Software Engineer, Pulp Project
>> Red Hat Brazil - Latam <https://www.redhat.com/>
>> +55 22 999000595
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev