Closed Bug 1294543 Opened 9 years ago Closed 9 years ago

Use jenkins and github to update product-details

Categories

(www.mozilla.org :: Bedrock, defect)

Product:
www.mozilla.org
Component:
Bedrock
Version:
Production
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1296646

People

(Reporter: pmac, Unassigned)

Details

(Whiteboard: [PBL])

We'd like to have better testing whenever product-details updates so that errors created by JSON schema changes are caught before going to prod. To do that we propose the following: - Create a Jenkins job that will use the django-mozilla-product-details lib to download and update a copy of the product-details files. - Have this job monitor for changes, when it sees some it will check those changes into a git repo and push that commit to a repo on github. - The github repo will be configured to send a web-hook to Jenkins. - Jenkins will fire a job to build a new docker image with the latest deployed code and l10n images, layer on the updated product-details files, and deploy to stage. - Jenkins will then run full integration tests to be sure the update hasn't broken anything - On success, Jenkins will trigger a production deploy. On failure not thing more will happen and the failure will be reported Bedrock will also need to be configured to read the product-details data from files instead of the DB.
Whiteboard: [PBL]
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.