Mailing-List: contact dev-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAEqTbYkcHq6H7vC0Z4TkOKpfC4rKM02or0L_cY+d1V7fegbwVw@mail.gmail.com>
References: <CAEqTbYkcHq6H7vC0Z4TkOKpfC4rKM02or0L_cY+d1V7fegbwVw@mail.gmail.com>
From: Alek Storm <alek.storm@gmail.com>
Date: Tue, 14 Nov 2017 12:18:07 -0600
Message-ID: <CAMNEcwuOhrnyzez7Lk6XhFeMHBn2MxJZ4dsAUq=ysSKqaz-JhA@mail.gmail.com>
Subject: Re: Airflow Deployment tools
To: dev@airflow.incubator.apache.org
Content-Type: multipart/alternative; boundary="f403045d92cca93118055df568a5"
archived-at: Tue, 14 Nov 2017 18:18:12 -0000

--f403045d92cca93118055df568a5
Content-Type: text/plain; charset="UTF-8"

Our TeamCity server detects the master branch has changed, then packages up
the repo containing our DAGs as an artifact. We then use SaltStack to
trigger a bash script on the targeted servers that downloads the artifact,
moves the files to the right place, and restarts the scheduler (on the
master).

This allows us to easily revert changes by redeploying a particular
TeamCity artifact, without touching the git history.

Alek

On Nov 14, 2017 11:02 AM, "Andy Hadjigeorgiou" <andyxhadji@gmail.com> wrote:

> Hey,
>
> Was just wondering what tools & services everyone uses to deploy new
> versions of their data pipelines (understandably this would vary greatly
> based on tech stack) but I'd love to hear what the community has been
> using.
>
> - Andy
>

--f403045d92cca93118055df568a5--