NOTE: If you don't see all the colored blocks on the page, you need to clean you browser cache to reload the css file!
Goals of the new waterfall "developer view"
(in contrast to the stock waterfall
- Make it easy to know the status of the buildbot for a given revision.
- Be able to easily track the status of your changes, or the changes of other people in your team.
- Be simple
- Fit in one page. No scrolling!
How to access the new view
How does it work?
For each revision, you can see the status of the change on all builders (represented by a colored square), on their first build containing this revision.
What does the colors mean
- Green : All the tests passed, congratulation!
- Red: There is a new failure. You need to take a look NOW!
- Orange: The build was red on its previous build, and it's still currently red. You should still take a quick look to make sure you did not introduce any regressions.
- Yellow: The builder is currently testing your change
- White: The builder has not started testing your change yet.
Here is a random example that shows the UI of this new view. (sorry Ben!)
(1): Enter your email, the one you use for svn, to see your personalized view with only your changes. Repeat this step for every team member you want to see in your view.
(2): Change 11699 did not compile on Windows. 4 squares turned red.
(3): Change 11700 was submitted to fix the compile failure. Unfortunately it did not work, the build was still broken. The failure is not attributed to this changelist though, since it was broken before. It's why it's orange
(4): If you hover your mouse over the box, you see a description of the error. You can also click on it for more details.
(5): Change 11701 fixed the build! Everything is green now!
- The second square is always "No Data" because we don't have revision information for the reliability test. It will be fixed later.
- If a build tests more than 1 changelist, and it turns red, all changelists in this build will be attributed the failure.
- If the build fails BEFORE the "gclient update" step, it will appear as "No Data" because we don't have a way to know which revisions were in this build.
- By default we show the last 50 changes.
- If it's a personalized view, we search for the changes in the last 100 changes.
- If the master has been restarted recently, it is possible that the revision history is truncated, and we will not display as many.