Perpetually red build status

[peter....@gmail.com]

How does the Polymer team use the build status?

I'm not sure if I've ever seen an all green status, and yet new releases keep coming...

As a developer wanting to use and advocate Polymer, this is hard to swallow and even harder to sell to fellow coworkers or management.

"You want to use what? They don't even have a grasp of their own tests! With constantly red builds, who knows what regressions are going to bubble up into our app if we use it!?"

Thanks.

[Matthew McNulty]

Hey Peter,

We're working on fixing this and will have a better answer soon, but I didn't want to continue to leave you hanging. 

The build status you see on the site is pointing at the tip of tree, which is a lot less stable than what we release. Occasionally there are testing infrastructure bugs or chrome bugs that keep some of the tests red, but we know about them and ignore those false negatives when we release, even though the matrix will show red. Any single test, including one false negative, is currently reflected as red for an entire portion of the matrix. 

This makes that particular build status useful for us internally (sort-of), but not for your purposes. We're working to change that so it more accurately reflects the release status and stability, but it will take a bit to accomplish. 

-Matt

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/193b8ef4-f895-4b1e-b812-f5ea50d1f422%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[peter....@gmail.com]

Thank you for the response and candor about the build status pages.

I look forward to a build status for the current release, this is great news.