[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Dockerised CI and testing environment

Hello folks,

I just submitted a PR for using Docker as part of Airflow's build pipeline:

Currently, running unit tests is a difficult process. Airflow tests depend
on many external services and other custom setup, which makes it hard for
contributors to work on this codebase. CI builds have also been unreliable,
and it is hard to reproduce the causes. Having contributors trying to
emulate the build environment every time makes it easier to get to an "it
works on my machine" sort of situation. The proposed docker setup aims to
simplify this.

You can check the PR description, which goes into more details. Now, I
bring this to the list because I have a few requests:

- Could you try the branch out on your local machines? The instructions are
provided in the PR (pending: actual docs). I would love to get feedback
about it.
- Is anyone familiar with the impersonation tests? There have proven to be
hard to fix with my limited knowledge of the codebase

It's WIP, but I wanted to submit what I've got so far and check if you guys
think I'm going in the right direction.


Gerardo Curiel //

( ! ) Warning: include(msgfooter.php): failed to open stream: No such file or directory in /var/www/git/apache-airflow-development/msg03406.html on line 97
Call Stack
10.0007363640{main}( ).../msg03406.html:0

( ! ) Warning: include(): Failed opening 'msgfooter.php' for inclusion (include_path='.:/var/www/git') in /var/www/git/apache-airflow-development/msg03406.html on line 97
Call Stack
10.0007363640{main}( ).../msg03406.html:0