--Luca.
--
To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On 18 Aug 2017, at 12:19, Gustaf Lundh <gustaf...@axis.com> wrote:Cool stuff! Really looking forward to try it out!> - Stability: stream-events are based on SSH, which isn't scalable, reliable against downtime, etc.Please note: The Gerrit Trigger plugin does support consuming events from rabbit-mq and also from the Gerrit event-log plugin.
I think it is also worth nothing that Gerrit Trigger is push based and not pull based. Which makes quite a difference when you have a great amount of projects.
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
On 18 Aug 2017, at 14:10, Robert Sandell <rsan...@cloudbees.com> wrote:Cool,So is this intended as a Branch API implementation? Something a la GitHub Branch Source Plugin?
Which is what my mind goes to when reading things like "Out-of-the-box integration with Gerrit validation workflow in the pipeline".
From a quick reading I'm not sure that is what you are planning, it seems like something else?
The gerrit-branch-source-plugin is something that has been on my todo list for over two years and I haven't been able to free enough cycles to implement it yet. So getting that ghost off my chest would be nice ;)
/B
--
--
To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Robert SandellSoftware EngineerCloudBees Inc.
--
--
To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss+unsubscribe@googlegroups.com.
On 7 Sep 2017, at 14:48, Vacelet, Manuel <manuel....@enalean.com> wrote:Hi Luca (congrats to the new gerrit maintainer BTW),It does answer the question but raise a new one ;)Have you an ETA in mind for all this ?
Hi all,
the wait is finally over ... and the first Alpha release of the new Gerrit Code Review plugin for Jenkins is finally available!
I have submitted the request to get this hosted by the JenkinsCI organization and plugin central distribution ... however, in the meantime, you can download and install it from the GitHub repo at:
https://github.com/GerritForge/gerrit-plugin/releases/tag/v0.1.0
How to use it ... so, it is embarrassing simple!
1. Create a new multi-branch pipeline project
2. Select "Gerrit" as repository source
3. Add the Git/HTTP URL of your Gerrit repository (Git/SSH should work, but it won't allow submitting feedback to Gerrit yet)
... and there you go :-)
If you want to submit feedback to Gerrit in your pipeline, just add the following statement in your pipeline script:
gerrit.review("Verified", 1, "It works !")
(when it works)
OR
gerrit.review("Verified", -1, "Breaks the build ;-(")
(when it breaks)
*DISCLAIMER* this is an Alpha pre-release that is mainly focussed on getting early feedback on what are the most critical features to get implemented.
*Happy EARLY ADOPTION* to everyone, and thanks for your patience!
Luca.
-Matthias
Hi all,
the wait is finally over ... and the first Alpha release of the new Gerrit Code Review plugin for Jenkins is finally available!
I have submitted the request to get this hosted by the JenkinsCI organization and plugin central distribution ... however, in the meantime, you can download and install it from the GitHub repo at:
https://github.com/GerritForge/gerrit-plugin/releases/tag/v0.1.0
Aside from binary distribution, how do you intend to manage code reviews? Will you keep it on GitHub and use pull requests, or are you going to host it on gerrit-review.googlesource.com?This is actually a good idea, however we’ll have the problem of people expecting to raise PRs on the GitHub Jenkinsci organisation.GerritHub would then be a better choice, because it allows to accept PRs as well, and review them through Gerrit.
Hi all,
the wait is finally over ... and the first Alpha release of the new Gerrit Code Review plugin for Jenkins is finally available!
I have submitted the request to get this hosted by the JenkinsCI organization and plugin central distribution ... however, in the meantime, you can download and install it from the GitHub repo at:
https://github.com/GerritForge/gerrit-plugin/releases/tag/v0.1.0
<<snip>>
*DISCLAIMER* this is an Alpha pre-release that is mainly focussed on getting early feedback on what are the most critical features to get implemented.
Hi Matthew,the project has now been moved to the JenkinsCI organisation.As soon as CloudBees will approve my PR on their repository, it will be available through the Jenkins Plugin Manager as well :-)Luca.
Giving this a shot but all I see in my jenkins build log is:
Gerrit Review Verified cannot be executed on branch null
I'm starting my pipeline with:
sh "git init"
sh "git fetch http://$GERRIT_HOST/$GERRIT_PROJECT $GERRIT_REFSPEC && git checkout FETCH_HEAD"
which lands me on a detached head. I'm calling it with:
gerrit.review("Verified", 1, "Project compilation successful ;-)")
I see https://wiki.jenkins.io/display/JENKINS/Gerrit+Code+Review+Plugin mentions checking out with:
checkout scm
so maybe that's where I'm going wrong.
Any suggestions?
Mark
On 4 Apr 2018, at 10:33, lucamilanesio wrote:
The final repository name is the following:
https://github.com/jenkinsci/gerrit-code-review-plugin
The Plugin has been renamed 'gerrit-code-review' because it seems that a few years ago a plugin was named 'gerrit' and thus the same name could not be reused.
I am planning to make the first release in the forthcoming days, so the Jenkins Users will have the first "Gerrit Code Review" plugin, which leverages (finally !) the Jenkins 2.0 features :-)
"The ease with which a change can be implemented has no relevance at all to whether it is the right change for the (Java) Platform for all time." — Mark Reinhold.
Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt
On 13 Apr 2018, at 00:20, Mark Derricutt <ma...@talios.com> wrote:Giving this a shot but all I see in my jenkins build log is:
Gerrit Review Verified cannot be executed on branch null
I'm starting my pipeline with:
sh "git init" sh "git fetch http://$GERRIT_HOST/$GERRIT_PROJECT $GERRIT_REFSPEC && git checkout FETCH_HEAD"
which lands me on a detached head. I'm calling it with:
gerrit.review("Verified", 1, "Project compilation successful ;-)")
I see https://wiki.jenkins.io/display/JENKINS/Gerrit+Code+Review+Plugin mentions checking out with:
checkout scm
so maybe that's where I'm going wrong.
On 13 Apr 2018, at 00:20, Mark Derricutt <ma...@talios.com> wrote:Giving this a shot but all I see in my jenkins build log is:
Gerrit Review Verified cannot be executed on branch null
I'm starting my pipeline with:
sh "git init" sh "git fetch http://$GERRIT_HOST/$GERRIT_PROJECT $GERRIT_REFSPEC && git checkout FETCH_HEAD"
No need to do this: just to a simple 'checkout scm'.The plugin gets automatically the gerrit host, project and ref for you :-)which lands me on a detached head. I'm calling it with:
gerrit.review("Verified", 1, "Project compilation successful ;-)")
I see https://wiki.jenkins.io/display/JENKINS/Gerrit+Code+Review+Plugin mentions checking out with:
checkout scm
so maybe that's where I'm going wrong.
The plugin uses the Gerrit API to understand the exact ref to use.Doesn't use anymore the old-style Gerrit Trigger Plugin envs.Trust me ... it is all "working by magic" ... as it should be :-)
Any suggestions?
Mark
On 4 Apr 2018, at 10:33, lucamilanesio wrote:
The final repository name is the following:
https://github.com/jenkinsci/gerrit-code-review-plugin
The Plugin has been renamed 'gerrit-code-review' because it seems that a few years ago a plugin was named 'gerrit' and thus the same name could not be reused.
I am planning to make the first release in the forthcoming days, so the Jenkins Users will have the first "Gerrit Code Review" plugin, which leverages (finally !) the Jenkins 2.0 features :-)
"The ease with which a change can be implemented has no relevance at all to whether it is the right change for the (Java) Platform for all time." — Mark Reinhold.
Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt
--
On 13 Apr 2018, at 00:45, David Pursehouse <david.pu...@gmail.com> wrote:On Fri, Apr 13, 2018 at 8:23 AM Luca Milanesio <luca.mi...@gmail.com> wrote:On 13 Apr 2018, at 00:20, Mark Derricutt <ma...@talios.com> wrote:Giving this a shot but all I see in my jenkins build log is:
Gerrit Review Verified cannot be executed on branch null
I'm starting my pipeline with:
sh "git init" sh "git fetch http://$GERRIT_HOST/$GERRIT_PROJECT $GERRIT_REFSPEC && git checkout FETCH_HEAD"
No need to do this: just to a simple 'checkout scm'.The plugin gets automatically the gerrit host, project and ref for you :-)which lands me on a detached head. I'm calling it with:
gerrit.review("Verified", 1, "Project compilation successful ;-)")
I see https://wiki.jenkins.io/display/JENKINS/Gerrit+Code+Review+Plugin mentions checking out with:
checkout scm
so maybe that's where I'm going wrong.
The plugin uses the Gerrit API to understand the exact ref to use.Doesn't use anymore the old-style Gerrit Trigger Plugin envs.Trust me ... it is all "working by magic" ... as it should be :-)Are you planning to update the README of the project with a bit more detail on how it's supposed to be set up?I know the setup is intended to be as simple and "working by magic" as much as possible, but I think it would help to have a bit more guidance in the documentation.
On 13 Apr 2018, at 11:23, Luca Milanesio wrote:
No need to do this: just to a simple 'checkout scm'.
You say that... but that just failed to checkout any code and just broke 50 jobs :)
I'm using a generic GerritJenkinsJobFile was a separate git repo. checkout scp checked out the job file repo, not the project repo.
On 13 Apr 2018, at 11:23, Luca Milanesio wrote:
No need to do this: just to a simple 'checkout scm'.
You say that... but that just failed to checkout any code and just broke 50 jobs :)
I'm using a generic GerritJenkinsJobFile was a separate git repo. checkout scp checked out the job file repo, not the project repo.
On 13 Apr 2018, at 18:29, luca.mi...@gmail.com wrote:
So, your project is not a multi-branch Pipeline, isn’t it?
We have about 50 projects all reusing the same JenkinsFile, from a separate git repo.
99% of the projects only have one 'develop' branch for reviews, some have shortlived/rarely used support branches tho.
I guess I should read that first line about starting with a multi-branch Pipeline job
- I'll have to go create a new job like that and see what the XML job looks like, and craft a script to remake all our jobs. I'm not actually sure what kind of pipeline job I created initially, I've usually just been creating new jobs based off the a previous one and changing the gerrit project/ref in the scm section.