On 11/20/2015 02:58 PM, Ashod Nakashian wrote:
On Fri, Nov 20, 2015 at 5:43 AM, David Tardon mailto:dtar...@redhat.com>> wrote:
Hi,
On Thu, Nov 19, 2015 at 05:55:01PM -0500, Ashod Nakashian wrote:
> On Thu, Nov 19, 2015 at 5:13 PM, Norbert Thiebaud mailto:nthieb...@gmail.com>>
>
On Thu, Nov 19, 2015 at 1:23 AM, David Ostrovsky wrote:
> Unfortunately, it cannot be done, because our infra team doesn't have
> free resources to set up new VM and install Gerrit and Jenkins on them.
> Last time i asked why they don't have resources and the answer was: this
> project is not Open
On Fri, Nov 20, 2015 at 5:43 AM, David Tardon wrote:
> Hi,
>
> On Thu, Nov 19, 2015 at 05:55:01PM -0500, Ashod Nakashian wrote:
> > On Thu, Nov 19, 2015 at 5:13 PM, Norbert Thiebaud
> > wrote:
> >
> > > On Thu, Nov 19, 2015 at 10:39 AM, Stephan Bergmann <
> sberg...@redhat.com>
> > > wrote:
> >
Hi,
On Thu, Nov 19, 2015 at 05:55:01PM -0500, Ashod Nakashian wrote:
> On Thu, Nov 19, 2015 at 5:13 PM, Norbert Thiebaud
> wrote:
>
> > On Thu, Nov 19, 2015 at 10:39 AM, Stephan Bergmann
> > wrote:
> > > By the way, one situation where it is debatable whether all the triggered
> > > builds are
>
> Norbert, there is clearly a terminology issue in our communication.
:-) quite possible indeed.
>
> I'm suggesting that for a given Change-Id we stop/cancel any ongoing or
> queued builds for that Change-Id before starting a new build.
cancelling build is a tricky/fragile business, especially
On Thu, Nov 19, 2015 at 5:13 PM, Norbert Thiebaud
wrote:
> On Thu, Nov 19, 2015 at 10:39 AM, Stephan Bergmann
> wrote:
> > By the way, one situation where it is debatable whether all the triggered
> > builds are useful is if you push a series of changes to gerrit, and
> Jenkins
> > does builds f
On Thu, Nov 19, 2015 at 5:09 PM, Norbert Thiebaud
wrote:
> On Thu, Nov 19, 2015 at 3:20 AM, Ashod Nakashian
> wrote:
> >
> > Sorry, I didn't explain well.
> >
> > The patches are related. They are updates based on feedback, partial
> failure
> > or improvement.
> >
> > They aren't bulk pushes (w
On Thu, Nov 19, 2015 at 10:39 AM, Stephan Bergmann wrote:
> By the way, one situation where it is debatable whether all the triggered
> builds are useful is if you push a series of changes to gerrit, and Jenkins
> does builds for each of the changes in the series. For me at least, in such
> a situ
On Thu, Nov 19, 2015 at 9:39 AM, Stephan Bergmann wrote:
> On 11/18/2015 03:28 PM, Ashod Nakashian wrote:
>>
>> As an aside, the recent drop in average build times (visible from the
>> Jenkins build times list/graph) is something I like to believe is my
>> fault :) The relevant commits were pushed
On Thu, Nov 19, 2015 at 3:20 AM, Ashod Nakashian wrote:
>
> Sorry, I didn't explain well.
>
> The patches are related. They are updates based on feedback, partial failure
> or improvement.
>
> They aren't bulk pushes (whatever that means). They are updates on a single
> changeset.
>
> Why do peopl
Hi Ashod,
On Wed, Nov 18, 2015 at 09:28:50AM -0500, Ashod Nakashian wrote:
> How much effort is necessary to stop builds for a given Gerrit push before
> starting new ones? (I'm assuming the Gerrit ID will be used and a command
> to kill all build configurations.)
So, that is more or less working
On 11/19/2015 02:03 PM, Ashod Nakashian wrote:
On Thu, Nov 19, 2015 at 5:39 AM, Stephan Bergmann mailto:sberg...@redhat.com>> wrote:
By the way, one situation where it is debatable whether all the
triggered builds are useful is if you push a series of changes to
gerrit, and Jenkins d
On Thu, Nov 19, 2015 at 2:23 AM, David Ostrovsky wrote:
> On Wed, Nov 18, 2015 at 19:20:03 PST, Ashod Nakashian gmail.com> wrote:
>
> >Sorry, I didn't explain well.
> >
> >The patches are related. They are updates based on feedback, partial
> >failure or improvement.
>
> [...]
>
> >Why do people
On Thu, Nov 19, 2015 at 5:39 AM, Stephan Bergmann
wrote:
> By the way, one situation where it is debatable whether all the triggered
> builds are useful is if you push a series of changes to gerrit, and Jenkins
> does builds for each of the changes in the series. For me at least, in such
> a situ
On Thu, Nov 19, 2015 at 5:53 AM, Samuel Mehrbrodt
wrote:
> Maybe this plugin would help, also for the problems Ashod mentioned:
> https://github.com/banyan/jenkins-ci-skip-plugin
>
> It allows to skip Jenkins build by adding [ci skip] to the commit message.
>
>
This is useful in general, but not
: Donnerstag, 19. November 2015 11:39
An: libreoffice@lists.freedesktop.org
Betreff: Re: Killing obsolete Jenkins builds
By the way, one situation where it is debatable whether all the
triggered builds are useful is if you push a series of changes to
gerrit, and Jenkins does builds for each of the
By the way, one situation where it is debatable whether all the
triggered builds are useful is if you push a series of changes to
gerrit, and Jenkins does builds for each of the changes in the series.
For me at least, in such a situation it would suffice if Jenkins just
only did a build for the
On 11/18/2015 03:28 PM, Ashod Nakashian wrote:
As an aside, the recent drop in average build times (visible from the
Jenkins build times list/graph) is something I like to believe is my
fault :) The relevant commits were pushed on Sunday last and now there
are far more sub 1h builds and the peaks
On Wed, Nov 18, 2015 at 19:20:03 PST, Ashod Nakashian wrote:
>Sorry, I didn't explain well.
>
>The patches are related. They are updates based on feedback, partial
>failure or improvement.
[...]
>Why do people send multiple patches per push? That's the right question
>to ask.
>
>And the answer
Just in case,
Do you know
git commit --amend to update last commit before pushing it to gerrit
And
git rebase -i HEAD~5 to rewrite your local commit history including for exemple
modify the third commit, merge commits 1 3 and 4 into a single one?
Philippe
Le 19 novembre 2015 04:20:03 CET, Ashod
On Wed, Nov 18, 2015 at 8:27 PM, Norbert Thiebaud
wrote:
> On Wed, Nov 18, 2015 at 2:28 PM, Ashod Nakashian
> wrote:
> > (Sorry if this has already been discussed/considered.)
> >
> > Once a patch is pushed to Gerrit a Jenkins build automatically starts.
> And
> > once subsequent patches are pus
On Wed, Nov 18, 2015 at 2:28 PM, Ashod Nakashian wrote:
> (Sorry if this has already been discussed/considered.)
>
> Once a patch is pushed to Gerrit a Jenkins build automatically starts. And
> once subsequent patches are pushed the cycle repeats.
>
> Is there a reason to keep running the builds o
(Sorry if this has already been discussed/considered.)
Once a patch is pushed to Gerrit a Jenkins build automatically starts. And
once subsequent patches are pushed the cycle repeats.
Is there a reason to keep running the builds of (old) patches that will not
get cherry picked?
How much effort i
23 matches
Mail list logo
