1291010 - Add "branch" field to Repository model/table

Status: RESOLVED FIXED

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

Description

[Cameron Dawson [:camd]]

Some github repos (gaia, bmo) have the same repo url for several Treeherder projects.  In order to differentiate them, we need to store the branch name in that table to find the right project based on the pulse message we get from taskcluster-github

Comment 1

[GitHub Autolander Bot]

Attachment: [treeherder] mozilla:branch-field-repo-table > mozilla:master

Comment 2

[Cameron Dawson [:camd]]

Comment on attachment 8776753 [details] [review]
[treeherder] mozilla:branch-field-repo-table > mozilla:master

Need this for Github resultset ingestion from Pulse.

Comment 3

[Cameron Dawson [:camd]]

This will also be pulse jobs after bug 1291012

Comment 4

[Cameron Dawson [:camd]]

Comment on attachment 8776753 [details] [review]
[treeherder] mozilla:branch-field-repo-table > mozilla:master

Good call on that.  Fixed.

Comment 5

[Treeherder GitHub Bugbot]

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

https://github.com/mozilla/treeherder/commit/2039eb7545e99daf8557469dd1123d2abd07c35c
Bug 1291010 - Add branch field to Repository model/table (#1755)

We need a 'branch' field on the repository so that we can determine
which repo to use for incoming resultsets from pulse exchanges. In
the past, projects like gaia-taskcluster have had their own maps of
github repositories/names/branches to Treeherder projects.  But
Treeherder should be the one owning that mapping.  The only thing on
this table was the branch that's used.  So here it is.

The "branch" field will default to "master" which is appropriate for
several of the repos.  But a few will need more custom values set.
These are laid out in the fixtures/repository.json file.  But they
will need to be manually entered into the databases on Prod/Stage
and Heroku.