[wildfly-dev] WildFly PR testing notification changes

[Tomaž Cerar]

there was recent post on this mailing list on exact this topic.

this was outcome:
https://developer.jboss.org/wiki/WildFlyPullRequestStandardsAndGuidelines


--
tomaz

On Thu, Sep 3, 2015 at 8:48 PM, Aleksandar Kostadinov <akostadi at redhat.com>
wrote:

> Is there any document describing wildfly PR review process? Blog, diagram,
> etc.
>
>
> Tomaž Cerar wrote on 09/03/2015 07:25 PM:
>
>> Hey guys,
>>
>> this mail is just heads up about recent changes to our CI <-->  GitHub
>> PR integration.
>>
>> As we started adding more and more different jobs to test each PR number
>> of comments
>> on each PR became almost like spam as each job added one comment when it
>> started
>> and second one with report of the build.
>>
>> With changes we did in past few weeks, we now have:
>>
>> - all build statuses only as part of github PR status check [1]
>> - comments get added only when there is build failure
>> - usual, retest this please & friends still work as they use to
>> - *in testing* auto lableling / unlabling of rebase-this/fixme lables.
>>
>> So to see the actual status of the builds and if all checks passed,
>> you will need to look at the pull request itself and not only mail
>> notifications like till now.
>>
>> --
>> tomaz
>>
>>
>> [1]
>>
>> https://github.com/blog/1935-see-results-from-all-pull-request-status-checks
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20150903/8e2b805e/attachment.html