You are viewing a plain text version of this content. The canonical link for it is here.

Posted to builds@apache.org by Jarek Potiuk <Ja...@polidea.com> on 2020/05/26 21:58:53 UTC

GitHub Actions CI/CD approach (Apache Airflow)

Hello everyone,

TL;DR; At Apache Airflow we have recently moved to GiHub Actions from
Travis CI - and we are not looking back. We initially looked at GitLab CI
but it seems the OSS is also not the highest priority for them, but it
turns out that Microsoft with GitHub adds some really OSS-friendly
solutions,

I had a discussion with Gavin (
https://issues.apache.org/jira/browse/INFRA-20124?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel)
and he asked me to share the description of Architecture choices we made at
Apache Airflow on our migration.

Here it is - the general description of the CI approach we use now:
https://cwiki.apache.org/confluence/display/INFRA/Github+Actions+to+DockerHub

I hope you find it useful and it will inspire your future CI/CD decisions.

I am happy to help if you have any questions, comments etc.

J

-- 

Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer

M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>