Closed Bug 1270627 Opened 8 years ago Closed 8 years ago

fix missing builder names in treeherder for release promotion jobs

Categories

(Tree Management :: Treeherder: Data Ingestion, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kmoir, Assigned: h.franciskang)

References

Details

Attachments

(3 files)

For example, the jobs with ? means the job isn't mapped to anything in the treeherder code

https://treeherder.mozilla.org/#/jobs?repo=mozilla-release&revision=0b8492c110bec959b94e3d54d5bd5ca7f7f97f6c

The code for this is in https://github.com/mozilla/treeherder

in  treeherder/etl and  tests/etl
Assignee: nobody → fkang
Notes from talking to rail

you can see that some job names are fixed here.
https://treeherder.allizom.org/#/jobs?repo=mozilla-beta
(staging treeherder)

in release tasks, the treeherder jobs are defined as staging or production
in the templates.  For example, for the beetmover task
https://github.com/mozilla/releasetasks/blob/master/releasetasks/templates/firefox/beetmove_image.yml.tmpl
you can see 
treeherderEnv:
                - staging

and 
 routes:
            - tc-treeherder-stage.{{ branch }}.{{ revision_hash }}

We can make a pull request to change these to production as a first step.  Then we can deploy once a new treeherder is deployed to production.
Looks good here with our latest beta in release promotion (Firefox 47.0b5)

https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&revision=93a53170dedffdff45bf9eb8dac6e5ef7a13c4ba

I think the next step is to add the remaining jobs indicated with question marks in treeherder etc.
So you can see there are jobs with question marks here

https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&revision=7d1f3450acc47025876964c1eca854ae027934f3

release-mozilla-beta-fir opt 	
release-mozilla-beta_fir opt

They'll need to be added to treeherder so they appear properly. There are a variety of job types, not sure if it important to separate them into specific headings are just include them as a generic release promotion job.
Here is an example of a previous change that updates the tests too in treeherder 
https://bugzilla.mozilla.org/show_bug.cgi?id=1212177#c10
Should we update the task templates to include test platform information?
Flags: needinfo?(rail)
I just checked the task templates and it looks like we don't explicitly submit most of those (except uptake monitoring I think), they come via buildbot. https://github.com/mozilla/releasetasks/search?p=2&q=treeherder&utf8=%E2%9C%93

Sounds like treeherder tries to guess the platform and falls back to something (first N characters?).
Flags: needinfo?(rail)
Moving to Treeherder since the PR is for the Treeherder repo. Have left some comments on the PR - please re-request review on the PR-link attachment here once ready for re-review :-)
Component: Releases → Treeherder: Data Ingestion
Product: Release Engineering → Tree Management
QA Contact: rail
Version: unspecified → ---
Attachment #8757999 - Flags: review?(emorley)
Comment on attachment 8757999 [details] [review]
[treeherder] hfkang:bug1260627-pr > mozilla:master

Left some more comments in response to the platform change :-)
Attachment #8757999 - Flags: review?(emorley) → feedback+
Attachment #8757999 - Flags: feedback+ → review?(emorley)
Comment on attachment 8757999 [details] [review]
[treeherder] hfkang:bug1260627-pr > mozilla:master

Sorry for the delay. This looks good - if you could adjust the first line of the commit message of the deadcode removal commit to mention the deadcode removal (and rebase on master if possible), I'll merge this for you :-)
Attachment #8757999 - Flags: review?(emorley) → review+
I've rebased, and amended the commit :)
Commits pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/0d9ae7a6b2b2555f700c53ffd2aa39b376f1260e
Bug 1270627 - Support release promotion jobs

These jobs have been added under the new Release group in the "other" platform:
 - Version Bump
 - Checksums Builder
 - Uptake Monitor
 - Updates
 - Bouncer Aliases
 - Bouncer Submission
 - Update Verify (moved from Updates group)

Since the jobs do not contain platform info in buildname, nor are
associated with a specific os platform, the regex captures all
of the jobs individually to assign it the "other" os_platform.

https://github.com/mozilla/treeherder/commit/3b2d48d319380e500e43812f7fecbf28c861fb1a
Bug 1270627 - Remove unused job_type dictionary

Remove JOB_TYPE_BUILDERNAME and extract_job_type(), as neither are used
anywhere.
The relevant test components have also been removed from test_buildbot.py.
This should be deployed sometime this week :-)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: