Closed Bug 1318112 Opened 8 years ago Closed 6 years ago

Document how changes to socorro-infra "deploys"

Categories

(Socorro :: Infra, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: peterbe, Assigned: miles)

Details

We have two repos: github.com/mozilla/socorro and github.com/mozilla/socorro-infra.
Changes to github.com/mozilla/socorro immediately trigger a stage deploy.

What about changes to socorro-infra? How does a change there go into stage or prod?
Miles, you can put the answer almost anywhere but please make sure to link to it from the Crash-stats Mana page. Or just write it in the Mana page if you want.
Assignee: nobody → miles
This used to be done via a Git hook from the socorro-infra repo to Leeroy, the job in Jenkins is "INFRA-SOCORRO-update-local-repo". I will be folding this step into the deploy process for stage, isolating the stage and prod deploy processes, and moving forward from there. The temporary solution is for me to manually run this job (or manually git pull on the instance), then run the stage build.

Updating socorro-infra as part of the stage deployment process will become automatic _soon_.
I'm updating this bug from the perspective of the new infrastructure because we have no plans to revise deployment procedures for the existing (old) socorro infrastructure.

On the cloudops side, the next deployment of a service will pick up merged changes. If we're regularly deploying from cloudops-deployment master, any infra changes that have been merged will be picked up into the next deploy, including automated stage build triggers.

This is roughly how it should be expected to work - new changes to the infra repository are implemented on the next deploy - whereas the old system was more counterintuitive (infra changes required a separate jenkins job to be run prior to the deploy to be picked up).
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.