Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attach BuildTimeTrend to the builders #202

Closed
jdm opened this issue Jan 25, 2016 · 3 comments
Closed

Attach BuildTimeTrend to the builders #202

jdm opened this issue Jan 25, 2016 · 3 comments

Comments

@jdm
Copy link
Member

@jdm jdm commented Jan 25, 2016

http://buildtimetrend.github.io/service/

We have this hooked up to our TravisCI builds right now, but that information is less clearly actionable/meaningful than the build time data for our actual builders. The documentation suggests there are a couple ways to go about this, either using Keen.io or storing XML data locally. Then we also need to run an instance of the client that fetches this data appropriately.

@edunham
Copy link
Contributor

@edunham edunham commented Jul 5, 2017

This can be done through Salt changes, requiring admin intervention only to roll those changes out. The buildtimetrend client should run as its own user so we can decide whether it's on its own or sharing a host.

@aneeshusa
Copy link
Member

@aneeshusa aneeshusa commented Jul 6, 2017

AIUI, they've discontinued the production instance at https://buildtimetrend.herokuapp.com/, so we'll likely also need to run our own server in addition to clients.

@aneeshusa
Copy link
Member

@aneeshusa aneeshusa commented Dec 13, 2017

We are currently using the Buildbot API to fetch and upload build time data, thanks to work by Alan in servo/servo#19344, servo/servo#19450, and servo/servo#19524. Data is available in S3 and I believe can be viewed in Google Data Studio.

@aneeshusa aneeshusa closed this Dec 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.