add graphics project branch to treeherder

RESOLVED FIXED

Status

Tree Management
Treeherder
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: kmoir, Assigned: kats)

Tracking

(Blocks: 1 bug)

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
We will be enabling ci on it for the quantum graphics work.

See bug 1313389
Blocks: 1311790
Standard procedure would be to submit a pull request with the new repository metadata. See bug 1267716 for an example of this.
(In reply to William Lachance (:wlach) from comment #1)
> Standard procedure would be to submit a pull request with the new repository
> metadata. See bug 1267716 for an example of this.

Or bug 1298558 (stylo is likely a better example to work from)
Created attachment 8806377 [details] [review]
[treeherder] staktrace:patch-1 > mozilla:master

Comment 5

a year ago
Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/e9b9c2c281c8d38963886144c5f247eccd86eef1
Bug 1314079 - Reactivate the projects/graphics branch (#1966)

This branch will be used for the Quantum Render work, and we want it displayed on TreeHerder as there will be CI jobs running on it.
Since the repository was previously added, I'm not sure if datasource is smart enough to also add the project-specific db (which we unfortunately still need). So I'll need to take care to make sure that's added after this is deployed.
(In reply to William Lachance (:wlach) from comment #6)
> Since the repository was previously added, I'm not sure if datasource is
> smart enough to also add the project-specific db (which we unfortunately
> still need). So I'll need to take care to make sure that's added after this
> is deployed.

Actually it looks like the graphics database was already there (on both treeherder stage and production). So we're good, I think:

https://treeherder.allizom.org/#/jobs?repo=graphics
Hmm, what's the difference between a "development" repository and a "project" repository? I notice that stylo is listed as a "development" repo on TH.
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #8)
> Hmm, what's the difference between a "development" repository and a
> "project" repository? I notice that stylo is listed as a "development" repo
> on TH.

As far as I know, the only difference is where the repository will appear in the list dropdown in treeherder.
Heh, ok. That shouldn't matter for us then.
Is there more that needs to be done here? https://treeherder.mozilla.org/#/jobs?repo=graphics seems to exist now but it doesn't show anything. And the info message says "graphics is not supported in api.pub.build.mozilla.org/treestatus"
Flags: needinfo?(wlachance)
I also can't push to the branch because of the missing treestatus:

pushing to ssh://hg.mozilla.org/projects/graphics
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1629 changesets with 12839 changes to 7979 files
remote:
remote:
remote: ************************** ERROR ****************************
remote: Error accessing https://api.pub.build.mozilla.org/treestatus/trees/graphics :
remote: HTTP Error 404: NOT FOUND
remote: Unable to check if the tree is open - treating as if CLOSED.
remote: To push regardless, include "CLOSED TREE" in your push comment.
remote: *************************************************************
remote:
remote:
remote: transaction abort!
remote: rollback completed
remote: pretxnchangegroup.a_treeclosure hook failed
abort: push failed on remote
treestatus is a seperate system, redirecting to ryanvm
Flags: needinfo?(wlachance) → needinfo?(ryanvm)
I've added it to treestatus. Try now.
Flags: needinfo?(ryanvm) → needinfo?(bugmail)

Updated

a year ago
Assignee: nobody → bugmail
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
Works now, thanks! I'll follow up on bug 1313389 for the build/test jobs.
Flags: needinfo?(bugmail)
You need to log in before you can comment on or make changes to this bug.