From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Luke Diamand <luke@diamand.org>,
lkp@intel.com, Greg KH <gregkh@linuxfoundation.org>,
Stefan Beller <sbeller@google.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: 0 bot for Git
Date: Mon, 25 Apr 2016 16:07:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1604251603590.2896@virtualbox> (raw)
In-Reply-To: <1C553D20-26D9-4BF2-B77E-DEAEDDE869E2@gmail.com>
Hi Lars,
On Sun, 24 Apr 2016, Lars Schneider wrote:
> [...] the current Git Travis CI OSX build always installs the latest
> versions of Git LFS and Perforce via brew [1] and the Linux build
> installs fixed versions [2]. Consequently new LFS/Perforce versions can
> brake the OS X build even if there is no change in Git.
>
> You could argue that this is bad CI practice because CI results should
> be reproducible. However, it has value to test the latest versions to
> detect integration errors as the one with Git LFS 1.2. We could add
> additional build jobs to test fixed versions and latest versions but
> this would just burn a lot of CPU cycles... that was the reason why I
> chose the way it is implemented right now. I will add a comment to the
> OSX build to make the current strategy more clear (Linux fixed versions,
> OS X latest versions).
>
> What do you think about that? Do you agree/disagree? Do you see a better
> way?
I agree with your reasoning.
Ciao,
Dscho
next prev parent reply other threads:[~2016-04-25 14:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGZ79kYWGFN1W0_y72-V6M3n4WLgtLPzs22bWgs1ObCCDt5BfQ@mail.gmail.com>
2016-04-12 4:29 ` 0 bot for Git Stefan Beller
2016-04-12 6:41 ` Greg KH
2016-04-12 7:23 ` Matthieu Moy
2016-04-12 14:52 ` Stefan Beller
2016-04-12 15:15 ` Philip Li
2016-04-12 20:29 ` Matthieu Moy
2016-04-12 20:49 ` Junio C Hamano
2016-04-13 5:43 ` Matthieu Moy
2016-04-13 12:16 ` Lars Schneider
2016-04-13 12:30 ` Matthieu Moy
2016-04-13 16:14 ` Lars Schneider
2016-04-13 16:15 ` Junio C Hamano
2016-04-13 6:11 ` Lars Schneider
2016-04-13 16:27 ` Junio C Hamano
2016-04-13 17:09 ` Lars Schneider
2016-04-13 17:29 ` Stefan Beller
2016-04-13 17:43 ` Greg KH
2016-04-16 15:51 ` Lars Schneider
2016-04-16 18:02 ` Junio C Hamano
2016-04-22 8:19 ` Lars Schneider
2016-04-22 17:30 ` Junio C Hamano
2016-04-24 7:15 ` Johannes Schindelin
2016-04-24 12:19 ` SZEDER Gábor
2016-04-24 13:05 ` Johannes Schindelin
[not found] ` <CAE5ih7-fyuEvSDzmHVfXta3hd_7ZRp1+_VtytDM+u0372Kyidg@mail.gmail.com>
[not found] ` <CAE5ih7_fabo7DyZyHoxdp1Y4ygby2qwKA8E1N6MuGzHa60Wf4w@mail.gmail.com>
[not found] ` <CAE5ih7-DzFe_3=kyan=E17zCo-iNdNdH7DE5ZwYVHmFvUBkDkA@mail.gmail.com>
[not found] ` <CAE5ih7-d9ow0dF6wfWCkmx+HAQOzVBONGCC_U4-2bkDUZGPecQ@mail.gmail.com>
[not found] ` <CAE5ih7_OEAWjYm9LwMAwBCtnvG+KgGo1aFuT9CyQjeN6nFmC5w@mail.gmail.com>
[not found] ` <CAE5ih7-z8K5Z7HuBa=pF53b6obU60ZCxrEkTLWbaSMsg0G1Ctg@mail.gmail.com>
[not found] ` <CAE5ih78arC2V76XR7yUoXk77c0d_z3Hzupw6MA1+saS3faXjTw@mail.gmail.com>
2016-04-24 13:05 ` Johannes Schindelin
[not found] ` <1C553D20-26D9-4BF2-B77E-DEAEDDE869E2@gmail.com>
2016-04-25 14:07 ` Johannes Schindelin [this message]
2016-04-13 17:47 ` Junio C Hamano
2016-04-13 13:44 ` Fengguang Wu
2016-04-12 9:42 ` Duy Nguyen
2016-04-12 14:59 ` Stefan Beller
2016-04-14 22:04 ` Christian Couder
2016-04-15 9:51 ` Parallel checkout (Was Re: 0 bot for Git) Duy Nguyen
2016-04-15 11:18 ` Christian Couder
2016-04-15 11:32 ` Duy Nguyen
2016-04-15 16:52 ` Jeff King
2016-04-15 17:31 ` Junio C Hamano
2016-04-15 17:38 ` Jeff King
2016-04-16 5:17 ` Michael Haggerty
2016-04-15 15:08 ` Stefan Beller
2016-04-16 0:16 ` Duy Nguyen
2016-04-26 11:35 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1604251603590.2896@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gregkh@linuxfoundation.org \
--cc=larsxschneider@gmail.com \
--cc=lkp@intel.com \
--cc=luke@diamand.org \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.