Closed Bug 1268958 Opened 8 years ago Closed 8 years ago

Add the autopush repository to Treeherder

Categories

(Tree Management :: Treeherder: API, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rshenthar, Assigned: emorley)

Details

Attachments

(1 file, 1 obsolete file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160425205003

Steps to reproduce:

@wlach: Please help me create a autopush repository on the stage server. https://github.com/mozilla-services/autopush
Whiteboard: Treeherder - Add autopush repo to Treeherder
As mentioned on irc, please create a pull request with the repository added to the repository's fixture. Here's an example:

https://github.com/mozilla/treeherder/pull/1440
(Adjusting summary since there's no way to just add a repository to stage and not also prod)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Add a autopush repository for treeherder staging → Add the autopush repository to Treeherder
Whiteboard: Treeherder - Add autopush repo to Treeherder
I'm happy to create the PR to add this, I just need to know what description should be used for the repo? (Examples: https://github.com/mozilla/treeherder/blob/master/treeherder/model/fixtures/repository.json#L940 )
Flags: needinfo?(rshenthar)
(In reply to Ed Morley [:emorley] from comment #3)
> I'm happy to create the PR to add this, I just need to know what description
> should be used for the repo? (Examples:
> https://github.com/mozilla/treeherder/blob/master/treeherder/model/fixtures/
> repository.json#L940 )

Hi Ed! Please use the following description: "Mozilla Push server and Push Endpoint"
Flags: needinfo?(rshenthar)
Attachment #8748746 - Attachment is obsolete: true
:wlach, is there docs on structured logging for treeherder? currently our log format is unrecognized by treeherder so it gives us a link to the raw logs, which is OK for now, but we'd like to change that in future.
Flags: needinfo?(wlachance)
(In reply to Richard Pappalardo [:rpapa][:rpappalardo] from comment #7)
> :wlach, is there docs on structured logging for treeherder? currently our
> log format is unrecognized by treeherder so it gives us a link to the raw
> logs, which is OK for now, but we'd like to change that in future.

Not really at the moment, aside from the source code to the log parser (https://github.com/mozilla/treeherder/blob/master/treeherder/log_parser/parsers.py). I think the strategy that many projects (e.g. taskcluster) use is to actually get treeherder to parse their logs: camd or emorley could tell you about that. I'm hoping to simplify this part of treeherder in the near future (bug 1258861) and will try to document this if/when I do. Unless you have immediate needs I would just wait for that.
Flags: needinfo?(wlachance)
Assignee: nobody → emorley
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

Created:
Updated:
Size: