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/DevStudio-Pull-Requests/job/jbosstools-jst-Pull-Request/6/console

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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev