Automatically test pull requests

[mzdaniel]

Testing pull request automatically will have a measurable impact on the code base quality.

[shykes]

... as well as on the maintainer's ability to get some sleep :)

On Fri, May 31, 2013 at 5:40 PM, Daniel Mizyrycki
notifications@github.comwrote:

Testing pull request automatically will have a measurable impact on the
code base quality.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/773
.

[vieux]

👍 would be awesome, specially to test against, go1.0.3, I mainly us go1.1 and it takes time to test on go1.0.3

[mzdaniel]

@vieux: we are trying to deprecate go1.0.3 soon :)

[shykes]

This is implemented.

[titanous]

@shykes I don't see commit statuses on pull requests, is there a CI instance somewhere that doesn't update GitHub?

[creack]

/cc @mzdaniel

[mzdaniel]

@titanous: We'd like to stabilize the testbed before sending the notifications. So far the results are encouraging
(http://docker-ci.dotcloud.com/waterfall) :)

It seems sensitive we properly address at least #1548, #1431, and #1572 first

[mzdaniel]

@shykes: Do we want to create a new issue for commit statuses and close this one now that PR #1603 is in place?

[shykes]

Yes please.

On Tue, Aug 20, 2013 at 5:30 PM, Daniel Mizyrycki
notifications@github.comwrote:

@shykes https://github.com/shykes: Do we want to create a new issue for
commit statuses and close this one now that PR #1603https://github.com/dotcloud/docker/issues/1603is in place?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/773#issuecomment-22988068
.