Closed Bug 1561628 Opened 6 years ago Closed 6 years ago

switch to YYYY.MM.DD tagging scheme

Categories

(Socorro :: Infra, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

Details

Attachments

(2 files)

For Antenna (collector) and Socorro (everything else), we tag with a monotonically incrementing integer value. Currently, Antenna is at 32 and Socorro is at 384.

This team picked up Buildhub2 and Tecken which use a YYYY.MM.DD tagging scheme. That's more helpful since you can infer the date it went out (roughly) from the tag name.

After some discussion, we decided we want to switch to a YYYY.MM.DD scheme for Antenna and Socorro.

This involves updating infrastructure code and also changing our deploy_bug.py script.

I want to start this this week. It's one fewer difference between all the projects on our plate and makes the "when did we last deploy this project?" question a lot easier to answer.

Assignee: nobody → willkg
Status: NEW → ASSIGNED
Type: task → enhancement
Priority: -- → P2

If there are multiple tags in a single day, Buildhub2 and Tecken add an integer to the end. So then you'd end up with (for example):

  • 2019.06.26
  • 2019.06.26-2
  • 2019.06.26-3
  • etc

We should do the same for Socorro and Antenna.

Brian updated the deploy code and we just deployed antenna 2019.06.26 to prod.

We need to update socorro and then land the release script I'm now using.

I'm maintaining the release script in a separate repository to make it easier to use and share across a bunch of projects.

https://github.com/willkg/socorro-release

We had chance to test this out today with socorro and pushed out a 2019.07.03 followed by a 2019.07.03-2.

I think there are some ergonomics changes I'd want to do to release.py so it worked better across our projects, but we can track that in the socorro-release repo.

Marking as FIXED.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: