Skip to content

Commit 30bd2a3

Browse files
committed
chore(build): add trend for travis time
We discussed last week that our build has been steadily getting longer. We should track the time so we can easily notice that it went up and find the culprit. This hooks us up to https://buildtimetrend.herokuapp.com/ which seems capable and very quick to setup. We can easily gather the data and then evaluate the dashboard. Note that we want to have two different webhooks, and only notify gitter on transitions, but we want to have timing for all builds, since a series of passing builds might have a big jump in build time in the middle. I don't see how to do this with travis.yml so I've overnotified gitter.
1 parent 7cbaf10 commit 30bd2a3

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

.travis.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,9 @@ notifications:
6565
webhooks:
6666
urls:
6767
- https://webhooks.gitter.im/e/1ef62e23078036f9cee4
68-
on_success: change # options: [always|never|change] default: always
68+
# trigger Buildtime Trend Service to parse Travis CI log
69+
- https://buildtimetrend.herokuapp.com/travis
70+
on_success: always # options: [always|never|change] default: always
6971
on_failure: always # options: [always|never|change] default: always
7072
on_start: false # default: false
7173
slack:

0 commit comments

Comments
 (0)