Ah, sorry, mixed up two rwagner's ;)
Rick you should start creating PRs too!
On 06/28/2016 04:13 PM, Rick Wagner wrote:
Hi All,
I'm sorry, but I can't take credit for that Pull Request. (It's most
likely Radislav Wagner, I think from QE).
Thanks,
Rick
On Tue, Jun 28, 2016 at 3:04 PM, Alexey Kazakov <alkazako(a)redhat.com
<mailto:alkazako@redhat.com>> wrote:
Hi Mickael,
There was a PR [1] in jst repo. Rick Wagner, the author of the PR
is not a member of JBoss Tools organization (I sent him an
invitation). So I used "testPR" to trigger the test build.
The job was started [2] but it looks like the user used in the job
doesn't have write access to jst.
[1]
https://github.com/jbosstools/jbosstools-jst/pull/566
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud...
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