plugin binary repository

Max Spring

unread,

Mar 25, 2014, 12:45:13 PM3/25/14

to repo-d...@googlegroups.com

Is there a repository which carries the plugin jar files?
-Max

Shawn Pearce

unread,

Mar 25, 2014, 12:46:42 PM3/25/14

to Max Spring, David Ostrovsky, repo-discuss

On Tue, Mar 25, 2014 at 9:45 AM, Max Spring <maximili...@gmail.com> wrote:
> Is there a repository which carries the plugin jar files?

Not currently. David Ostrovsky and I were discussing creating one by
teaching Diffy (the Gerrit CI verifier) to also build the plugins and
deliver them to a public repository.

Max Spring

unread,

Mar 25, 2014, 12:57:38 PM3/25/14

to repo-d...@googlegroups.com, Max Spring, David Ostrovsky

Maybe continuing to build the plugins with Maven would help here?
;-)
-Max

Shawn Pearce

unread,

Mar 25, 2014, 1:00:49 PM3/25/14

to Max Spring, repo-discuss, David Ostrovsky

Maybe learning to use Buck would help here?
;-)

Luca Milanesio

unread,

Mar 25, 2014, 1:02:37 PM3/25/14

to Max Spring, repo-d...@googlegroups.com, David Ostrovsky

We already build Gerrit and the associated plugins on the GerritForge Jenkins instance (master and stable branches), we can make the URL public.

I was thinking about then extending the Gerrit init for accepting an external URL where to fetch the list of binary plugins available for download and install.

(similarly to the Eclipse install site mechanism)

Luca.

--
--
To unsubscribe, email repo-discuss...@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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Zaro

unread,

Mar 25, 2014, 1:06:13 PM3/25/14

to Shawn Pearce, Max Spring, David Ostrovsky, repo-discuss

Hey Shawn, I think deploying to a repo would be great. We do this already. We don't use maven to deploy we created a script to deploy to maven central and jenkins repos. It sets the artifacts to version info from git. Let me know if you want if i can help. -Khai

Zaro

unread,

Mar 25, 2014, 1:08:52 PM3/25/14

to Luca Milanesio, Max Spring, repo-d...@googlegroups.com, David Ostrovsky

Luca. do you build only current versions or older versions as well?

Luca Milanesio

unread,

Mar 25, 2014, 1:32:27 PM3/25/14

to Zaro, Max Spring, repo-d...@googlegroups.com, David Ostrovsky

*ALL* of them starting from Ver. 2.5.x

Of course some of them may not build on some plugin / Gerrit combination ... but knowing in advance that they *would never build* without changes, allows you to save time and then just concentrate on how to fix them :-)

We build them for our clients already today, as you get Gerrit binaries as part of your Customer Support Contract (see http://gerritforge.com/support)

However we decided to make part of our Jenkins visible to everyone, even without necessarily to have a support contract.

Older than 2.5 => no please ;-)

Luca.

Max Spring

unread,

Mar 26, 2014, 12:49:11 PM3/26/14

to repo-d...@googlegroups.com, Zaro, Max Spring, David Ostrovsky

Luca,
can you share details on how to get access to the Gerrit binaries on your Jenkins?
Thanks!
-Max

Luca Milanesio

unread,

Mar 26, 2014, 1:10:32 PM3/26/14

to Max Spring, repo-d...@googlegroups.com, Zaro, David Ostrovsky

It is not public yet, but I plan to make some progress today.

Luca.

Luca Milanesio

unread,

Mar 26, 2014, 5:33:31 PM3/26/14

to Max Spring, repo-d...@googlegroups.com, Zaro, David Ostrovsky

Hi Max,

the Gerrit master + associated plugins can be downloaded from:

http://ci.gerritforge.com/job/Gerrit-master/lastSuccessfulBuild/artifact/*zip*/archive.zip

The Jenkins build associated to Gerrit master is:

http://ci.gerritforge.com/job/Gerrit-master

One extra Jenkins job starts the full Gerrit acceptance tests:

http://ci.gerritforge.com/job/Gerrit-master-test/

More plugins and branches are coming over ...

Hope this help.

Luca.

On 26 Mar 2014, at 16:49, Max Spring <maximili...@gmail.com> wrote:

Luca Milanesio

unread,

Mar 26, 2014, 7:01:05 PM3/26/14

to Repo and Gerrit Discussion, Zaro, David Ostrovsky, Max Spring

... and ... the first non-core non-Maven plugin available for Gerrit master:

http://ci.gerritforge.com/job/Plugin_codenvy-master/lastSuccessfulBuild/artifact/codenvy.jar

Luca.

On 26 Mar 2014, at 22:35, Luca Milanesio <luca.mi...@gmail.com> wrote:

... and ... the first non-core plugin available from Gerrit master:
http://ci.gerritforge.com/job/Plugin_avatars-external-master/lastSuccessfulBuild/artifact/target/external-url-avatar-provider-1.0-SNAPSHOT.jar

Others are coming ... guess lots of people are looking forward to see the GitBlit plugin pre-built and available for install :-)

Luca.

Zaro

unread,

Mar 26, 2014, 7:30:27 PM3/26/14

to Luca Milanesio, Repo and Gerrit Discussion, David Ostrovsky, Max Spring

Thanks Luca, but no versioning on the artifact?

Luca Milanesio

unread,

Mar 26, 2014, 8:04:35 PM3/26/14

to Zaro, Repo and Gerrit Discussion, David Ostrovsky, Max Spring

Hi Max,

the ones published so far are from master, not a release.

As master changes every day, the SHA1 is the only versioning you could have on them.

The stable branches will come later ...

Luca

Sent from my iPhone

David Pursehouse

unread,

Mar 26, 2014, 8:55:53 PM3/26/14

to Shawn Pearce, Max Spring, David Ostrovsky, repo-discuss

On Tue, Mar 25, 2014 at 9:46 AM, Shawn Pearce <s...@google.com> wrote:

Plugin jar files are now available to download from a google storage bucket [1]. This is also now linked from the sidebar and footer on the Gerrit project home page [2].

[1] http://gerritcodereview-plugins.storage.googleapis.com/index.html

[2] https://code.google.com/p/gerrit/

Luca Milanesio

unread,

Mar 26, 2014, 9:09:25 PM3/26/14

to David Pursehouse, Shawn Pearce, Max Spring, David Ostrovsky, repo-discuss

Cool :-)

Are the builds coming from the Gerrit (and plugins) master branch ?

Luca.

Luca Milanesio

unread,

Mar 26, 2014, 9:10:53 PM3/26/14

to David Pursehouse, Shawn Pearce, Max Spring, David Ostrovsky, repo-discuss

Stupid question as the 'master' is in the link name ;-)

Will concentrate then on the old stable-branches till ver. 2.5 for ci.gerritforge.com.

Luca.

Luca Milanesio

unread,

Mar 26, 2014, 11:11:01 PM3/26/14

to David Pursehouse, Shawn Pearce, Max Spring, David Ostrovsky, repo-discuss

All plugins (BUCK + Maven) for master are available ... working on the stable-2.9 now

http://ci.gerritforge.com

Luca.

lucamilanesio

unread,

Mar 27, 2014, 8:19:10 PM3/27/14

to repo-d...@googlegroups.com, David Pursehouse, Shawn Pearce, Max Spring, David Ostrovsky

GerritForge is glad to announce that the CI export is almost complete.

The Jenkins instance that powers the CI exposed is organised in the following views:

Gerrit view

=========

http://ci.gerritforge.com/view/Gerrit/

Contains all the SNAPSHOT builds of all branches (including master) back to stable-2.5.

If you are still running a Gerrit 2.4 or even older, you must consider upgrading ASAP.

NOTE: The Gerrit E2E test jobs are currently disabled because they take too much time and some of them are actually broken [not the test, but the functionality that they are testing]. We will dedicate a separate slave for tests in order to avoid blocking the main builds.

Under each Gerrit job, the associated BUCK plugins linked as Gerrit submodules are also built and published:

commit-message-length-validator.jar

cookbook-plugin.jar

download-commands.jar

replication.jar

reviewnotes.jar

singleusergroup.jar

Plugins views

===========

http://ci.gerritforge.com/view/Plugins-master/

http://ci.gerritforge.com/view/Plugins-stable-2.7/

http://ci.gerritforge.com/view/Plugins-stable-2.8/

Contains all the SNAPSHOT builds of the Gerrit plugins (the ones with at least one change merged). Most of the plugins have ONLY a master branch as they have not been modified since their initial version. This does not mean that they necessarily work on the current Gerrit master version though.

--- * ---

DISCLAIMER

===========

The GerritForge CI *IS NOT* the official Gerrit distribution and does not provide the officially tagged build binaries. For each version of Gerrit there is a release manager who is responsible for tagging, building, verifying the distributed packages.

We have chosen to expose our CI for allowing the Gerrit community to access to a wide variety of plugins in their binary form and to Gerrit SNAPSHOT releases without having to compile everything from source code.

Building Gerrit and its plugins is a useful but time-consuming activity that may be difficult for those who want just to use Gerrit without being involved with its development.

--- * ---

Q&A

====

Q: What is the relationship between the CI builds and the ones available at http://gerritcodereview-plugins.storage.googleapis.com/index.html ?

A: GerritForge CI is the build of the HEAD of Gerrit and their plugins branches, without any purpose of archiving or large-scale distribution. The Plugins published at Google storage are the ones built using BUCK and the official Google Diffy verifier and they are inteded to be used for distribution to the community.

Q: Can I use the CI builds for my production environment ?

A: Yes, but bear in mind that they are SNAPSHOT, they are not supported and thus not associated to any specific release. In case of problems you may need to contact someone in the Community, a contractor or request customer support.

Q: How can I find to what version the SNAPSHOT build is associated ?

A: SNAPSHOT is not associated to any version in particular, however if you need to know to which GIT SHA1 corresponds, just add "git/?" to the end of the build URL. Example http://ci.gerritforge.com/view/Gerrit/job/Gerrit-master/lastSuccessfulBuild/git/?

Q: Why the artifact name does not contain any SHA1, time-stamp or Build ID ?

A: This is the way that Gerrit build works: produces always the same artifact name, regardless of the SHA1 built. The SHA1 of the build is visible at the bottom of each Gerrit screen after the 'g' char: (e.g. 2.9-rc1-144-g0993c83 => SHA1 of the HEAD commit is 0993c83)

--- * ---

We believe that having a Gerrit Continuous Integration visible would allow:

> Gerrit contributors: having a direct feedback on the health status of the active branches

> Gerrit users: saving time in building SNAPSHOTs and Plugins

One extra value is the ability to access the plugin and extension APIs when they are in SNAPSHOT state, as they are not published to the Google Storage Maven repo.

Hope the community would benefit from our CI :-)

Luca.

On Thursday, March 27, 2014 3:11:01 AM UTC, lucamilanesio wrote:

All plugins (BUCK + Maven) for master are available ... working on the stable-2.9 now
http://ci.gerritforge.com

Luca.

On 27 Mar 2014, at 00:55, David Pursehouse <david.pursehouse@sonymobile.com> wrote:

On Tue, Mar 25, 2014 at 9:46 AM, Shawn Pearce <s...@google.com> wrote:

On Tue, Mar 25, 2014 at 9:45 AM, Max Spring <maximili...@gmail.com> wrote:
> Is there a repository which carries the plugin jar files?

Not currently. David Ostrovsky and I were discussing creating one by
teaching Diffy (the Gerrit CI verifier) to also build the plugins and
deliver them to a public repository.

Plugin jar files are now available to download from a google storage bucket [1]. This is also now linked from the sidebar and footer on the Gerrit project home page [2].

[1] http://gerritcodereview-plugins.storage.googleapis.com/index.html
[2] https://code.google.com/p/gerrit/

--
--

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.

Matthias Sohn

unread,

Mar 27, 2014, 8:40:23 PM3/27/14

to lucamilanesio, Repo and Gerrit Discussion, David Pursehouse, Shawn Pearce, Max Spring, David Ostrovsky

thanks for settings this up :-)

do you plan to also setup plugin builds for stable-2.9 ?

--

Matthias

Luca Milanesio

unread,

Mar 27, 2014, 8:47:24 PM3/27/14

to Matthias Sohn, Repo and Gerrit Discussion, David Pursehouse, Shawn Pearce, Max Spring, David Ostrovsky

It seems that no plugin at the moment has a "stable-2.9" branch.

As 2.9 and MASTER are really close, the Plugins-master should work on top of 2.9 as well.

I will start working (with who wants to join the effort) on a Gerrit change to automatically list and download plugins during the init phase.

My idea is to have a "--plugins-url" option on Gerrit init to download the URL where plugins are published.

The document published at that URL could be a simple HTML file like the one published on the Gerrit Web-Site:

http://gerritcodereview-plugins.storage.googleapis.com/index.html

That would allow to discover the list of plugins available and install them during init.

P.S. The "plugin compatibility with Gerrit" is a completely different (and more complex) problem :-) ... possibly worth another extra Change uploaded.