I’ve updated Gerrit from 2.11.5 to the latest release 2.12.2. These are the user-visible highlights: New Submit Whole Topic setting: All changes belonging to the same topic will be submitted at the same time. Currently disabled because it’s still experimental but I will enable this once it’s considered stable. Support for GPG Keys and signed pushes. You can add your GPG key in Gerrit and git push –signed to use this. This should work right now – but doesn’t for me at least. If you have more success, let me know. 🙂 New search operators, e. g. author:, committer:, commentby: and a few others. Your preferences for editing and diff presentation can now be configured in your user settings. Gerrit’s in-line editor has now support for Emacs and Vim key maps. There are several new API calls available for those using their own Gerrit clients (yes, I’m looking at you, Kylie McClain! 😉 ). You can find the complete release notes for the Gerrit versions here: Gerrit 2.11.6 Gerrit 2.11.7 Gerrit 2.12 Gerrit 2.12.1 Gerrit 2.12.2 As for Jenkins, I’ve updated it to 1.652 as well. Nothing spectacular there but some bug fixes in the backend mostly; including two security fixes….
This morning, I’ve updated Gerrit to the latest release 2.11.2. These are the user-visible highlights: Automatic suggestions in the search box work again. Several issues that could potentially cause data loss have been fixed. Newer jgit version You can find the complete release notes for Gerrit 2.11.2 here. As for Jenkins, I’ve updated it from 1.617 to 1.620 as well. Lots of bugfixes were implemented the most interesting of which concerned the console (log) output that could get truncated. The full changelog can be found here.
I’ve just finished updating Gerrit to the latest release 2.11.1. These are the highlights: You can now link accounts to each other (Settings / Identities / Link Another Identity). This means, if you want to be able to use both Github and Google, just use that button. Furthermore, if you accidentally create a new account (you’ll know it happened if you can’t +2 changes for your own repository anymore), you can now just link both yourself. If things still somehow go wrong, just let me know and I’ll link your accounts manually. Performance improvements for pushing changes to Gerrit and some other areas Newer jgit version Lots of bugfixes You can find the complete release notes for Gerrit 2.11 here.
I’ve just finished updating Gerrit to the latest release 2.11. This gives us some amazingly cool new features to play with: In-line editing of changes! Till now, we could only edit the commit message; now we can fix typos, etc. ourselves. Let’s rule the (changeset) world! The new(er) change screen is more gorgeous than ever! (And you better like it because the old one is gone.) The Return of The King or: The Empire strikes back! Authentication using Google’s Oauth2 is supported now. When logging in, you can choose between github (the preferred supplier) or Google. (This is going to change once more this year and then hopefully never again. User accounts have been preserved now, though, and will be preserved when I’m done with the authentication changes I’m preparing.) Gerrit is now back where it belongs – in Tomcat. That makes it faster and more reliable. There’s one caveat: You mere mortals can’t generate your http passwords yourselves anymore due to security considerations. If you need this functionality, you’ll have to poke zlin or me. You can find the complete release notes for Gerrit 2.11 here.
Just a short heads-up: I’m going to update our Gerrit installation tomorrow so please expect some downtime.
As you will have noticed, after a hard crash and failed efforts to restore the existing Gerrit, it had to be re-installed from scratch. With it, some changes had to be made: OpenID is no longer available for authentication as Google is deprecating it. GitHub is now used for authentication. So you must have an account there. cgit is integrated into Gerrit and can be used stand-alone as well. All repositories had to be re-imported. If you have a repository in Gerrit, please contact zlin (via IRC or email) or myself (via IRC or email) to get your permissions set up again. I’ve updated my post Gerrit Code Review for Exherbo as well. P. S.: Due to being ill, I might not be available.
Just a small update today: You can find my build bash scripts for Jenkins in git and Gerrit now. git clone https://galileo.mailstation.de/gerrit/jenkins-build cgit: https://galileo.mailstation.de/cgit/cgit.cgi/jenkins-build.git/ Please submit patches via Gerrit.
As some of you will have noticed, my server galileo.mailstation.de has had some performance issues lately. Testing patches with Jenkins could take a long time, building stages was taking up to 20 hours (!) instead of the normal two and Gerrit itself could be slow at times as well. This was due to aging hardware (that server was assembled in 2010), one horribly performing hard disk and constant over-heating of the machine. I’ve changed a few things over the last few days and performance is much better now but still not to my satisfaction. Today, I’ve finally had enough of squeezing performance out of rotting hardware and simply ordered a new server. Functionally, it will be identical to good old galileo but on beefier hardware, especially with much more RAM (48 GB instead of 12 GB) which is essential for my uses. While I’m writing this, I’m copying over the entire galileo to the new server which will hopefully be finished in a few hours from now. Once that’s done, I’m going to shut down all non-essential services on galileo (that includes Gerrit, Jenkins, the bots and lots of other stuff), re-sync the data to the new server, change the DNS records, fire up…
Over the last few weeks, I’ve made a few changes to Exherbo’s Gerrit and Jenkins installation: Build artifacts are stored in Jenkins: If a build is unsuccessful, the Paludis build log, config.log (if it exists) and the cave-resolve command used are stored. Since build artifacts are associated with a project (i. e. the repository) and not individual builds, the files have the build number prepended in their file name: 77_build.log 77_cave-resolve.txt 77_config.log If a build is successful, only the cave-resolve command and the detected dependencies are archived: 78_cave-resolve.txt 78_dependencies.txt This change is effective immediately for all exheres repositories in Jenkins. If you have further suggestions of files to archive, please let me know. Due to the recent OpenSSL Heartbleed bug issue, I’ve re-issued the SSL certificates on my machines on April, 11th 2014. If you have a password login on galileo, now is the time to change it. For galileo.mailstation.de, the host key fingerprints are as follows: 1024 a8:8c:7d:87:3d:a6:61:78:8d:59:f5:52:d7:b1:3c:34 (DSA) 256 f1:08:b0:12:66:1c:72:af:2d:d8:c7:15:ca:13:f6:f2 (ECDSA) 256 68:1c:27:e2:8e:b5:42:62:98:8a:f3:04:45:c1:60:f9 (ED25519) 2048 37:38:6e:81:4a:53:24:4d:b0:fb:c7:3e:f0:1d:63:8c (RSA1) 2048 06:57:ff:b7:e6:6f:c8:31:76:c8:9a:7c:37:d7:f5:47 (RSA) The web server’s certifacte has the following fingerprints: SHA-256 Fingerprint: 85 3D 47 8B A5 44 76 A0 09 96 9F 15 4A 9A F8 C5 1C…