THIS IS AWESOME WORK! Kenneth
On Thu, Feb 27, 2014 at 5:44 PM, Raphael Kubo da Costa < raphael.kubo.da.co...@intel.com> wrote: > Hello, fellow pedestrians, > > At long last, our public trybots went live. The old trybot system has > been deactivated, and from now on you will hear from Mr. > crosswalk-trybot in your pull requests. > > You can see what the builders are up to by visiting > https://build.crosswalk-project.org/try. We have the same list of > builders as build.crosswalk-project.org, namely: > > * Content Shell Android x86 > * Content Shell Linux > * Crosswalk Android x86 > * Crosswalk Linux > * Crosswalk Tizen Mobile 3 > * Crosswalk Tizen IVI > * tizen-extensions-crosswalk (with IVI repositories) > > The slaves for these builders have pretty much the same configuration as > the build slaves in build.crosswalk-project.org, and should be > noticeably faster than the previous, private ones. > > Other user-visible changes include: > > * We now set the pull request's status: you can see a yellow dot on the > last commit and a "Merge with caution" message when the patch is > still being built, a failure message when all bots finish and at > least one of them failed or an OK if everything goes well. > > * The list of bots building a certain patch is changed as each builder > starts building a pull request. This means that initially no builders > will be listed, and they will be progressively added as they pick a > new patch. The message indicators described above are helpful to know > when all builders have finished and a patch is good for merging. > > * There is one comment per push. In other words, if you submit a pull > request there will be one comment with the status of that and if you > later change your commits and push to your branch again, there will > be a separate comment tracking that new push. This should clear the > previous confusion about which version of a patch was being built. > > * There is no "retrigger" checkbox to "kick the bots" anymore. If you > do not have anything to change in your branch but still need the bots > to process your patch again (maybe one builder failed with an > unrelated error, for example), just use "git commit --amend" to > change the SHA1 of your commit and push to your branch again. This > will cause the patch to be processed again as described in the > previous bullet point. > > * We have JIRA integration: if your pull request's message mentions > "XWALK-XXX" a comment will be added to the respective issue, and if > one line of the pull request message starts with "BUG=XWALK-XXXX" the > respective issue will be automatically closed when the pull request > is merged. > > The only downside in this transition is that existing pull requests have > not been migrated (ie. we did not manually create builds for the > existing pull requests). People with open pull requests: please > re-upload your patches (use the "git commit --amend" trick above if > there is nothing to change) for them to be processed by the new Trybots. > > If something goes wrong, please file tickets in JIRA with the issues you > are experiencing. > > Thanks to everyone who helped with this effort (as well as the folks who > maintained the private trybots while we made this long transition)! > _______________________________________________ > Crosswalk-dev mailing list > Crosswalk-dev@lists.crosswalk-project.org > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev > -- Kenneth Rohde Christiansen Web Platform Architect, Intel Corporation. Phone +45 4294 9458 ﹆﹆﹆
_______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
