You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally created by @DouweM on 2021-04-01 21:48:07
I think we can add a meltano.yml to this project that comes with:
orchestrator airflow
a file bundle with pip_url: . (so that it always uses the most recent version from the current branch)
some schedules
Then we can add a .gitlab-ci.yml that runs meltano invoke airflow scheduler and validates the expected output, i.e. there should be no error about meltano.py, or the expected lines confirming that a DAG was created for each schedule.
Migrated from GitLab: https://gitlab.com/meltano/files-airflow/-/issues/6
Originally created by @DouweM on 2021-04-01 21:48:07
I think we can add a
meltano.yml
to this project that comes with:airflow
pip_url: .
(so that it always uses the most recent version from the current branch)Then we can add a
.gitlab-ci.yml
that runsmeltano invoke airflow scheduler
and validates the expected output, i.e. there should be no error aboutmeltano.py
, or the expected lines confirming that a DAG was created for each schedule.Similar to how https://gitlab.com/DouweM/tap-investing tests itself using https://gitlab.com/DouweM/tap-investing/-/blob/master/meltano.yml and https://gitlab.com/DouweM/tap-investing/-/blob/master/.gitlab-ci.yml#L18.
The text was updated successfully, but these errors were encountered: