Page MenuHomePhabricator

Deploy Scap version 3.17.1-1
Closed, ResolvedPublic

Description

As discussed in T277793: Increase reliability of scap release process, we in RelEng would like to change the release process. As a result, we haven't updated the release branch for this release. Instead, we have created the 3.17.1 tag for the release. Please build a Debian package from that. We recommend using the build-deb-in-docker script, included in that tag.

$ git checkout -b build-release 3.17.1
$ ./build-deb-in-docker ~/scap-3.17.1

This builds a Docker image with stretch, installs all the build dependencies, and builds the package. The built packages get copied into the ~/scap-3.17.1 directory, which gets created if it doesn't exist. By using the script, RelEng can test builds in the same way that SRE builds them.

If there are any problems, please tell us and we'll work with you to fix it, and make sure it doesn't happen again.

After that, upload the package as described in https://wikitech.wikimedia.org/wiki/Scap3#Uploading_to_apt_repos but the packages are in the ~/scap-3.17.1 directory, not /var/cache/pbuilder/result/stretch-amd64/ as the wiki page says.

Thank you.

Event Timeline

We had a problem on beta; {T279703: Scap "import scap.git" fails on beta in CI}. Until that's fixed, let's not not build or deploy the 3.17.0 release.

We're going to tag a new version with fixes, and open a new task for that.

Re-opening and editing, because I'm lazy.

LarsWirzenius renamed this task from Deploy Scap version 3.17.0-1 to Deploy Scap version 3.17.1-1.Mon, Apr 19, 4:36 PM
LarsWirzenius changed the task status from Open to Stalled.
LarsWirzenius updated the task description. (Show Details)
LarsWirzenius updated the task description. (Show Details)
LarsWirzenius updated the task description. (Show Details)
LarsWirzenius changed the task status from Stalled to Open.Mon, Apr 19, 4:54 PM

We've tagged the bug fix release 3.17.1 and tested it on the beta cluster. We'd like it be built as a .deb and deployed to production, when there's time. Thanks!

@LarsWirzenius as discussed in T265501, using docker to build scap, is not an option. In T277793#6957246 I wrote that "we will be happy with a step by step documented process of how to build the debian package on our build host". Please update the "Building" section in https://wikitech.wikimedia.org/wiki/Scap3#Production_Upgrade, and I will be happy to build and roll it out.

@LarsWirzenius as discussed in T265501, using docker to build scap, is not an option. In T277793#6957246 I wrote that "we will be happy with a step by step documented process of how to build the debian package on our build host". Please update the "Building" section in https://wikitech.wikimedia.org/wiki/Scap3#Production_Upgrade, and I will be happy to build and roll it out.

Or simply provide the dsc/debian.tar.*/orig.tar.* somewhere for import/building, that rules out any issues in the git workflows before that step.

@LarsWirzenius as discussed in T265501, using docker to build scap, is not an option. In T277793#6957246 I wrote that "we will be happy with a step by step documented process of how to build the debian package on our build host". Please update the "Building" section in https://wikitech.wikimedia.org/wiki/Scap3#Production_Upgrade, and I will be happy to build and roll it out.

Or simply provide the dsc/debian.tar.*/orig.tar.* somewhere for import/building, that rules out any issues in the git workflows before that step.

Before reverting to such practices, I'd like to go back to the problem we're trying to solve, and that is "be able to run a build locally the same way as in production".

Being naive, I thought the simplest way was to just configure pbuilder on your local linux installation, or (if we want to also support people using OSX) create a docker image with pbuilder and a configuration similar to our build host, to use locally.

I think exceptions to the pbuilder workflow make sense in specific cases and with good justification; I don't see one for scap, to be honest.

Please update the "Building" section in https://wikitech.wikimedia.org/wiki/Scap3#Production_Upgrade, and I will be happy to build and roll it out.

Hi @jijiki. I have updated the instructions at that URL. Please give it a try and let me know how it goes.

Mentioned in SAL (#wikimedia-operations) [2021-04-27T16:22:50Z] <effie> upgrading scap 3.17.1-1 on mediawiki canaries - T279695

@dancy thank you very much, everything worked well!
I have installed scap 3.17.1-1 on our api canaries, I will proceed with a full rollout this week.

jijiki claimed this task.

@dancy it appears that rolling out scap coincided with the greek easter this time , sorry!

Update complete.