Change Details

As a **developer**, **I want** to be sure that my configuration always matches my code, **so that** I can deploy any time Acceptance Criteria: * The FR-Team gets an email notification when the current production configuration for the fundraising frontend does not validate against the schema in the current master, Background: Until we have a souped-up Jenkins solution, an easy quick-fix would be a cron job that regularly pulls the current master and runs the schema check script against the production configuration. If the check fails, an email gets sent to fundraising-tech@wikimedia.de

As a **developer**, **I want** to be sure that my configuration always matches my code, **so that** I can deploy any time Acceptance Criteria: * The FR-Team gets an email notification when the current production configuration for the fundraising frontend does not validate against the schema in the current master, Background: ~~Until we have a souped-up Jenkins solution, an easy quick-fix would be a cron job that regularly pulls the current master and runs the schema check script against the production configuration. If the check fails, an email gets sent to fundraising-tech@wikimedia.de~~

As a **developer**, **I want** to be sure that my configuration always matches my code, **so that** I can deploy any time Acceptance Criteria: * The FR-Team gets an email notification when the current production configuration for the fundraising frontend does not validate against the schema in the current master, Background: ~~Until we have a souped-up Jenkins solution, an easy quick-fix would be a cron job that regularly pulls the current master and runs the schema check script against the production configuration. If the check fails, an email gets sent to fundraising-tech@wikimedia.de~~