Lars fixed it, now.
On Wed, Dec 6, 2017 at 6:46 PM, Jim Apple wrote:
> It stopped being able to launch workers for a few hours. I'll be bringing
> it back up shortly.
>
It stopped being able to launch workers for a few hours. I'll be bringing
it back up shortly.
Hi folks,
I misspoke earlier: this was actually a plugin upgrade, not a Jenkins
upgrade.
I've restarted jenkins.impala.io. Three recalcitrant jobs weren't
finishing, so were aborted by the restart. If you're in the To line of this
e-mail, you have one job to restart. Here are the reviews those jo
It's now in "no new jobs" mode. In about 3 hours, the currently running
jobs will have finished, and I'll restart Jenkins.
On Wed, Dec 6, 2017 at 11:16 AM, Philip Zeyliger
wrote:
> I'll be upgrading Jenkins today in response to a security advisory. I'll
> be putting it in "no new jobs" mode shor
I'll be upgrading Jenkins today in response to a security advisory. I'll be
putting it in "no new jobs" mode shortly.
-- Philip
I wonder if the "Rebase always" merge strategy would help with this
scenario:
https://gerrit-review.googlesource.com/Documentation/project-configuration.html#submit_type
On Wed, Dec 6, 2017 at 9:04 AM, Daniel Hecht wrote:
> Sailesh, please keep that in mind with the ServicePool change -- you'll
Sailesh, please keep that in mind with the ServicePool change -- you'll
need to explicitly merge part 1 first.
On Wed, Dec 6, 2017 at 8:41 AM, Tim Armstrong
wrote:
> I think that's a consequence of the "cherry pick" merge strategy. It does
> seem like a flaw in our merge process. It would be nic
I think that's a consequence of the "cherry pick" merge strategy. It does
seem like a flaw in our merge process. It would be nice if we could
configure gerrit so that it didn't merge patches where the parent isn't a
commit on the master branch.
On Tue, Dec 5, 2017 at 9:31 PM, Sailesh Mukil wrote:
