6 p.m.
Hi all,
A couple of weeks ago, we created some jobs on so-called "Central CI" to
validate incoming pull requests:
https://issues.jboss.org/browse/JBIDE-21657?focusedCommentId=13247039&...
Those are now on for all components, but it may not be reporting on the
PR for some components because of permissions. If you're using PR, and
do not see report from CI jobs such as the one at the bottom of
https://github.com/jbosstools/jbosstools-openshift/pull/1175 .
If your component is missing those, please add a comment to JBIDE-21657
and we'll figure out what's missing and hopefully fix it.
Cheers,
--
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>
7:18 a.m.
Hi Mickael,
we currently run the PR tests on the old jenkins. I am wondering if we
are supposed to move to Central CI too. If yes, could you setup a job
for me or grant me the appropriate rights to do it myself?
Lars
##SELECTION_END##
-------- Weitergeleitete Nachricht --------
Von: Mickael Istria <mistria(a)redhat.com>
An: jbosstools-dev jbosstools-dev <jbosstools-dev(a)lists.jboss.org>
Betreff: [jbosstools-dev] CI jobs building PR
Datum: Tue, 21 Jun 2016 18:00:28 +0200
Mailer: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
Thunderbird/38.7.1
Hi all,
A couple of weeks ago, we created some jobs on so-called "Central CI"
to validate incoming pull requests: https://issues.jboss.org/browse/JBI
DE-
21657?focusedCommentId=13247039&page=com.atlassian.jira.plugin.system.i
ssuetabpanels:comment-tabpanel#comment-13247039
Those are now on for all components, but it may not be reporting on the
PR for some components because of permissions. If you're using PR, and
do not see report from CI jobs such as the one at the bottom of https:/
/github.com/jbosstools/jbosstools-openshift/pull/1175 .
If your component is missing those, please add a comment to JBIDE-21657
and we'll figure out what's missing and hopefully fix it.
Cheers,
--
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
7:31 a.m.
On 06/22/2016 07:18 AM, Lars Heinemann wrote:
Hi Mickael,
Hi,
we currently run the PR tests on the old jenkins. I am wondering if
we
are supposed to move to Central CI too. If yes, could you setup a job
for me or grant me the appropriate rights to do it myself?
It seems to me that this instance if for project inside the rhdevelopers
program. For integration, you should get in touch with eng-ops and
request a dedicated machine.
Cheers,
--
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>
9:48 a.m.
When does the job get launched ? Because I see lots of PR not being
validated (late ones) in jboss-openshift (ex
https://github.com/jbosstools/jbosstools-openshift/pull/1234). If the PR
got updated, will the job launched again ?
Thanks
Jeff
On Wed, Jun 22, 2016 at 7:31 AM, Mickael Istria <mistria(a)redhat.com> wrote:
On 06/22/2016 07:18 AM, Lars Heinemann wrote:
Hi Mickael,
Hi,
we currently run the PR tests on the old jenkins. I am wondering if we are
supposed to move to Central CI too. If yes, could you setup a job for me or
grant me the appropriate rights to do it myself?
It seems to me that this instance if for project inside the rhdevelopers
program. For integration, you should get in touch with eng-ops and request
a dedicated machine.
Cheers,
--
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
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
11:15 a.m.
On 06/22/2016 09:48 AM, Jean-Francois Maury wrote:
When does the job get launched ? Because I see lots of PR not being
validated (late ones) in jboss-openshift (ex
https://github.com/jbosstools/jbosstools-openshift/pull/1234). If the
PR got updated, will the job launched again ?
The job get launched automatically if
the submitter is part of the
"JBoss Tools" GitHub organization.
In case the submitter isn't part of this organization, someone from this
organization has to comment saying "testPR" to trigger the build.
--
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>
12:28 p.m.
Did it get relaunched when the PR is updated ?
Jeff
On Wed, Jun 22, 2016 at 11:15 AM, Mickael Istria <mistria(a)redhat.com> wrote:
On 06/22/2016 09:48 AM, Jean-Francois Maury wrote:
When does the job get launched ? Because I see lots of PR not being
validated (late ones) in jboss-openshift (ex
<https://github.com/jbosstools/jbosstools-openshift/pull/1234>
https://github.com/jbosstools/jbosstools-openshift/pull/1234). If the PR
got updated, will the job launched again ?
The job get launched automatically if the submitter is part of the "JBoss
Tools" GitHub organization.
In case the submitter isn't part of this organization, someone from this
organization has to comment saying "testPR" to trigger the build.
--
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>
12:34 p.m.
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>
3 p.m.
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
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
5:20 p.m.
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 <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing
listjbosstools-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev
5:45 p.m.
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
6:20 p.m.
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
6:32 p.m.
On 06/22/2016 06:20 PM, Nick Boldt wrote:
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.
It's
actually how they are currently configured. If this doesn't work,
please open a Jira and investigate.
--
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>
6:34 p.m.
On 06/22/2016 05:20 PM, 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 ?
AFAIK, there is no easy way on GitHub to automatically prevent a commit
from being merged via GitHub UI. So at the moment, taking build results
into account is the duty of the individual who wants to merge the patch.
Once again, Gerrit does it better :P
--
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>
6:44 p.m.
Well we could remove all push rights to master repos and let the ci bot do
the merge.
Then it's as prevented as gerrit.
I believe that's what openshift does. But they have actual integration
tests too :)
But yes gerrit has nicer flow overall.
/max
On Wednesday, 22 June 2016, Mickael Istria <mistria(a)redhat.com> wrote:
On 06/22/2016 05:20 PM, 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 ?
AFAIK, there is no easy way on GitHub to automatically prevent a commit
from being merged via GitHub UI. So at the moment, taking build results
into account is the duty of the individual who wants to merge the patch.
Once again, Gerrit does it better :P
--
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>
--
/max
https://about.me/maxandersen
6:49 p.m.
On 06/22/2016 06:44 PM, Max Andersen wrote:
Well we could remove all push rights to master repos and let the ci
bot do the merge.
You mean a CI bot that would merge on developer request? If so I
don't
get how it's better than leaving the developer push directly.
Then it's as prevented as gerrit.
Usually, Gerrit UI simply
hides the "Submit" button on a contribution if
it doesn't conform to project requirements (fast-forward, Verified+1,
Code-Review+2, no -1). AFAIK, there is no way to add such logic on
GitHub UI and the Merge button is always there, even when no-one likes it.
Note that usually with Gerrit, it's still possible for committers to
push directly to master.
But indeed, some projects do lock master and only allow submission via
Gerrit UI. Would GitHub allow that? Would it be good to use it given the
limitation explained above (no way to control the availability of the
merge operation in UI) ?
--
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>
11:30 a.m.
OK this is running ok if I update the PR. But the PR page says 1 successful
check although 2 have run (see
https://github.com/jbosstools/jbosstools-openshift/pull/1235). it is a
Github pb ?
Jeff
On Wed, Jun 22, 2016 at 6:49 PM, Mickael Istria <mistria(a)redhat.com> wrote:
On 06/22/2016 06:44 PM, Max Andersen wrote:
Well we could remove all push rights to master repos and let the ci bot do
the merge.
You mean a CI bot that would merge on developer request? If so I don't get
how it's better than leaving the developer push directly.
Then it's as prevented as gerrit.
Usually, Gerrit UI simply hides the "Submit" button on a contribution if
it doesn't conform to project requirements (fast-forward, Verified+1,
Code-Review+2, no -1). AFAIK, there is no way to add such logic on GitHub
UI and the Merge button is always there, even when no-one likes it.
Note that usually with Gerrit, it's still possible for committers to push
directly to master.
But indeed, some projects do lock master and only allow submission via
Gerrit UI. Would GitHub allow that? Would it be good to use it given the
limitation explained above (no way to control the availability of the merge
operation in UI) ?
--
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>
1:46 p.m.
On 06/23/2016 11:30 AM, Jean-Francois Maury wrote:
OK this is running ok if I update the PR. But the PR page says 1
successful check although 2 have run (see
https://github.com/jbosstools/jbosstools-openshift/pull/1235). it is a
Github pb ?
As far as I understand, the status of the GitHub PR is the status of
the
last commit. If you append a commit, then the status is wiped out, build
starts up and then status for the new commit is show.
So even if there were 2 successive build, it only shows the "1
successful build" for the latest one, and previous is ignored. If we set
up different jobs to review PRs (for example of distinct code quality
job), then you'll see the result of these 2 jobs on each commit.
If you want to track previous builds for individual commits, there's a
green tick or a red cross attached to each commit that was tested. Those
are visible at
https://github.com/jbosstools/jbosstools-openshift/pull/1235/commits .
Clicking on the green tick or red cross directs you to the Jenkins build.
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>
10:04 p.m.
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
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
10:13 p.m.
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> 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
listjbosstools-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev
10:16 p.m.
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
10:15 p.m.
On 06/28/2016 10:04 PM, Alexey Kazakov wrote:
Hi Mickael,
Hi,
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...
The GitHub user "rhdevelopers-ci" (https://github.com/rhdevelopers-ci)
needs to be added to the members of the jbosstools-jst project. See
configuration of jbosstools-openshift members for example
https://github.com/jbosstools/jbosstools-openshift/settings/collaboration .
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>
10:20 p.m.
On 06/28/2016 04:15 PM, Mickael Istria wrote:
On 06/28/2016 10:04 PM, Alexey Kazakov wrote:
> Hi Mickael,
Hi,
> 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...
The GitHub user "rhdevelopers-ci" (https://github.com/rhdevelopers-ci)
needs to be added to the members of the jbosstools-jst project. See
configuration of jbosstools-openshift members for example
https://github.com/jbosstools/jbosstools-openshift/settings/collaboration
.
It was already a member of JST (via "bot" team) but the "bot" team
didn't have write access. I fixed that.
Thanks!
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
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
10:24 p.m.
Actually half of our repos didn't have this set up properly.
Fixed now.
On 06/28/2016 04:20 PM, Alexey Kazakov wrote:
On 06/28/2016 04:15 PM, Mickael Istria wrote:
> On 06/28/2016 10:04 PM, Alexey Kazakov wrote:
>> Hi Mickael,
> Hi,
>> 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...
> The GitHub user "rhdevelopers-ci"
> (https://github.com/rhdevelopers-ci) needs to be added to the members
> of the jbosstools-jst project. See configuration of
> jbosstools-openshift members for example
> https://github.com/jbosstools/jbosstools-openshift/settings/collaboration
> .
It was already a member of JST (via "bot" team) but the "bot" team
didn't have write access. I fixed that.
Thanks!
> 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
> 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
2859
days inactive
2866
days old
jbosstools-dev@lists.jboss.org
22 comments
7 participants
participants (7)
-
Alexey Kazakov -
Jean-Francois Maury -
Lars Heinemann -
Max Andersen -
Mickael Istria -
Nick Boldt -
Rick Wagner