Yes, we should work on that workflow.
On 06/22/2016 11:20 AM, Jean-Francois Maury wrote:
Will it be part of our merge workflow ie merging the PR won't be
allowed if the status is not green or has it to be manually by the
merger ?
jeff
On Wed, Jun 22, 2016 at 3:00 PM, Alexey Kazakov <alkazako(a)redhat.com
<mailto:alkazako@redhat.com>> wrote:
Jeff, is a member of JBoss Tools organization.
On 06/22/2016 06:34 AM, Mickael Istria wrote:
> On 06/22/2016 12:28 PM, Jean-Francois Maury wrote:
>> Did it get relaunched when the PR is updated ?
> If it's updated by someone who's whitelisted (member of JBoss
> Tools organization on GitHub), then yes, it should be relaunched
> automatically. If it's from someone external, I believe someone
> has to say "testPR" to relaunch.
> On the GitHub PR, you can click on the "Show details" link for
> the build. It will drive you to Jenkins and on Jenkins you get
> access to more metadata such as the commitId that was built.
>
> HTH
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
> My blog <
http://mickaelistria.wordpress.com> - My Tweets
> <
http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> <mailto:jbosstools-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev