Closed Bug 1635455 Opened 5 years ago Closed 4 years ago

staging releases should actually make a github release somewhere

Categories

(Taskcluster :: Services, enhancement)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

Details

(somewhere on a test repo!) This will probably also entail deleting the 99.9.9 release at the start.

This will allow us to test the release process including uploading artifacts, which has been somewhat problematic in the past.

I've created https://github.com/taskcluster/staging-releases and will set things up to do staging pushes there, instead of to branches on the main repo.

https://github.com/mozilla/community-tc-config/pull/291

https://community-tc.services.mozilla.com/tasks/XzgC5iFGRc-nU5ldoLOFGA/runs/0/logs/live/https%3A%2F%2Fcommunity-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FXzgC5iFGRc-nU5ldoLOFGA%2Fruns%2F0%2Fartifacts%2Fpublic%2Flogs%2Flive.log#L1941

woo :)

Next up:

  • supply it with GitHub credentials that can only access this new repo
  • create the release even for staging releases (but still --no-push, so no packages or docker images are pushed)
  • write a yarn staging-release that will push a staging release to the new repo, perhaps searching for a release version that doesn't already exist, or just inventing one from the current timestamp.

With this, the only things special-cased for staging releases are the version determination and getting the changelog text.

Worth doing a nightly staging release off the tip of master to catch when we break things?

Nightly seems like a lot. Let's do it on-demand, like when we're thinking "let's do a release this afternoon" we can do a staging release in the morning :)

I created a new taskcluster-staging-bot github account, created a PAT, and put it in passwordstore. Next step would be to add it as a collaborator (or whatever) on the staging-releases repo, but it's been flagged by GitHub so I can't do that just yet. I sent a support request.

Flagging is cleared, and I added a secret containing the PAT.

I started to modify this so that it would use tags on the staging-releases repo instead of branches, but then remembered: tags tend to get pushed everywhere. So if I made a 99.8.7 tag to test a staging release, it'd be easy to accidentally push that tag to the real repo. Just noting that here in case I get confused again :)

Woah -- https://github.com/taskcluster/staging-releases/releases/tag/untagged-343e2e4008313d9b0697

It's a draft release, hence the weird name. But as a bonus, draft releases can have the same number, so it doesn't really matter what version number we pick.

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