Joining late so apologies if this was already said.
PR jobs could be configured to set up whitelists of people for which a
"testPR" keyword is not needed. In fact, it would be awesome if all
PRs from people in the jbosstools organization would be build
automatically w/o the need to approve the PR prior to it being built.
$0.02,
Nick
On Wed, Jun 22, 2016 at 11:45 AM, Alexey Kazakov <alkazako(a)redhat.com> wrote:
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> 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
> My blog - My Tweets
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com