1210532 - Run final verification using TC workers

Status: RESOLVED FIXED

(Release Engineering :: Release Automation: Other, defect)

Description

[Rail Aliiev [:rail]]

... because it's the easiest job evah!

Comment 1

[Justin Wood (:Callek)]

I'm not yet sure how to link this up to pass the "things" but here is what I have so far:

https://tools.taskcluster.net/task-inspector/#COjeapHJSfCneXy6TzvqdA/

{
  "provisionerId": "aws-provisioner-v1",
  "workerType": "b2gtest",
  "schedulerId": "-",
  "taskGroupId": "JjYUAHGqRECrJj2abKiWxA",
  "routes": [],
  "priority": "normal",
  "retries": 1,
  "created": "2015-10-21T22:35:54.587Z",
  "deadline": "2015-10-21T23:35:54.587Z",
  "expires": "3015-10-15T16:04:01.204Z",
  "scopes": [],
  "payload": {
    "artifacts": {},
    "command": [
      "/bin/bash",
      "-c",
      "hg clone https://hg.mozilla.org/build/tools && cd tools && hg up -r $RELEASE_TAG && cd release/ && ./final-verification.sh $RELEASE_CONFIGS"
    ],
    "env": {
      "RELEASE_TAG": "FIREFOX_42_0b8_RELEASE_RUNTIME",
      "RELEASE_CONFIGS": "mozBeta-firefox-linux.cfg mozBeta-firefox-linux64.cfg mozBeta-firefox-mac64.cfg mozBeta-firefox-win32.cfg mozBeta-firefox-win64.cfg"
    },
    "maxRunTime": 7200,
    "image": "rail/python-test-runner",
    "cache": {}
  },
  "metadata": {
    "owner": "[e-mail]",
    "source": "https://hg.mozilla.org/build/tools",
    "name": "test final verification",
    "description": "test release final verification\n"
  },
  "tags": {},
  "extra": {}
}


That uses rail's image from https://github.com/rail/python-test-runner/ which will move in-tree at some point (and could likely use nearly any linux host, this happens to be ubuntu:vivid

I'm using b2gtest as the provisioner, since I'm told it rarely has backlog and is not really that beefy of a box, (we are not really CPU bound here) running on opt-linux64 (the same used for firefox builds) we didn't actually shave much time off.

I'm putting this comment here so that if I get dragged off on another piece of work that it is easily repeatable/findable for another go-around.

Comment 2

[Rail Aliiev [:rail]]

We use Jinja templates to pass things around. You can look at https://github.com/mozilla/releasetasks/blob/master/releasetasks/templates/source.yml.tmpl or something from that directory. You may need to add your own template variables and pass them from release-runner.py.

Also don't forget to add the task to the graph https://github.com/mozilla/releasetasks/blob/master/releasetasks/templates/release_graph.yml.tmpl

Comment 3

[Justin Wood (:Callek)]

Attachment: [tools] add verifyConfigs to task_graph creation

This will require us to s/mac64.cfg/macosx64.cfg/ later on, but I feels its too risky a change for right now (there could be any number of things that make assumptions on filename there)

Comment 4

[Rail Aliiev [:rail]]

Comment on attachment 8679033 [details] [diff] [review]
[tools] add verifyConfigs to task_graph creation

Review of attachment 8679033 [details] [diff] [review]:
-----------------------------------------------------------------

A conditional r+:

::: buildfarm/release/release-runner.py
@@ +286,5 @@
>                  "balrog_password": balrog_password,
>                  # TODO: stagin specific, make them configurable
>                  "signing_class": "dep-signing",
>              }
> +            verifyConfigTemplate = "moz{branch}-{product}-{plat}.cfg"

Let's use "{branch}-{product}-{plat}.cfg", no "moz" prefix, no capitalization. The prefix is redundant for release promotion. There is no TB in the new process and even if someone decides to add it, it'd be "comm-something".

And rename the cfg files accordingly.

Comment 5

[Justin Wood (:Callek)]

Comment on attachment 8679033 [details] [diff] [review]
[tools] add verifyConfigs to task_graph creation

https://hg.mozilla.org/build/tools/rev/a216e3eb38f2

Checked in with mentioned changes

Comment 6

[Justin Wood (:Callek)]

This is running now, though needs to be wired up to upstreams.... Which are not yet ready.