<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Ah, sorry, mixed up two rwagner's ;)<br>
Rick you should start creating PRs too! <br>
<br>
<div class="moz-cite-prefix">On 06/28/2016 04:13 PM, Rick Wagner
wrote:<br>
</div>
<blockquote
cite="mid:CAGnpKD-dKdZB1nw_nMRUFqfAEt=YhR5n5arWbTEpBHP8ueTZPA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hi All,<br>
<br>
</div>
<div>I'm sorry, but I can't take credit for that Pull Request.
(It's most likely Radislav Wagner, I think from QE).<br>
<br>
</div>
<div>Thanks,<br>
</div>
<div><br>
</div>
<div>Rick</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jun 28, 2016 at 3:04 PM, Alexey
Kazakov <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:alkazako@redhat.com" target="_blank">alkazako@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hi Mickael,<br>
<br>
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.<br>
The job was started [2] but it looks like the user used in
the job doesn't have write access to jst.<br>
<br>
[1] <a moz-do-not-send="true"
href="https://github.com/jbosstools/jbosstools-jst/pull/566"
target="_blank">https://github.com/jbosstools/jbosstools-jst/pull/566</a><br>
<a moz-do-not-send="true"
href="https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStudio-Pull-Requests/job/jbosstools-jst-Pull-Request/6/console"
target="_blank">https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStudio-Pull-Requests/job/jbosstools-jst-Pull-Request/6/console</a><br>
<br>
<div>On 06/22/2016 06:34 AM, Mickael Istria wrote:<br>
</div>
<blockquote type="cite">
<div>On 06/22/2016 12:28 PM, Jean-Francois Maury wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Did it get relaunched when the PR is
updated ?</div>
</blockquote>
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.<br>
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.<br>
<br>
HTH<span class="HOEnZb"><font color="#888888"><br>
<div>-- <br>
Mickael Istria<br>
Eclipse developer at <a moz-do-not-send="true"
href="http://www.jboss.org/tools"
target="_blank">JBoss, by Red Hat</a><br>
<a moz-do-not-send="true"
href="http://mickaelistria.wordpress.com"
target="_blank">My blog</a> - <a
moz-do-not-send="true"
href="http://twitter.com/mickaelistria"
target="_blank">My Tweets</a></div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
jbosstools-dev mailing list
<a moz-do-not-send="true" href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">jbosstools-dev@lists.jboss.org</a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</font></span></blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>