All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Ed Maste <emaste@freebsd.org>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	git mailing list <git@vger.kernel.org>
Subject: CI/PR builds on FreeBSD, was Re: [PATCH 1/3] t/lib-httpd: avoid using BSD's sed
Date: Sat, 29 Feb 2020 00:57:07 +0100 (CET)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2002290054540.11433@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2002272046060.46@tvgsbejvaqbjf.bet>

Hi Ed,

On Thu, 27 Feb 2020, Johannes Schindelin wrote:

> On Thu, 27 Feb 2020, Ed Maste wrote:
>
> > On Thu, 27 Feb 2020 at 10:40, Johannes Schindelin
> > <Johannes.Schindelin@gmx.de> wrote:
> >
> > > Related, I saw that Cirrus CI offers FreeBSD builds, maybe you'd be
> > > interested in supporting that out of the box in
> > > https://github.com/git/git?
> >
> > Indeed - there is a .cirrus.yml in git now which builds and runs tests
> > (on FreeBSD 12.1). I'll look into working with the GitHub organization
> > owners for git and gitgitgadget to see about allowing Cirrus to access
> > the repositories.
>
> Oy, I had forgotten that you worked on this. I enabled this in the git
> and in the gitgitgadget orgs. The next pushes/PRs should benefit from
> this.

This works now. When you click on the green checkmarks (and the one red X)
at https://github.com/git/git/branches/active, you will see the
`freebsd_12` build.

Ciao,
Dscho

  reply	other threads:[~2020-02-28 23:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 20:09 [PATCH 0/3] ci: upgrade to the latest Azure Pipelines agent pools Johannes Schindelin via GitGitGadget
2020-02-26 20:09 ` [PATCH 1/3] t/lib-httpd: avoid using BSD's sed Johannes Schindelin via GitGitGadget
2020-02-26 20:20   ` Ed Maste
2020-02-27 15:40     ` Johannes Schindelin
2020-02-27 17:39       ` Ed Maste
2020-02-27 19:46         ` Johannes Schindelin
2020-02-28 23:57           ` Johannes Schindelin [this message]
2020-02-26 20:26   ` Junio C Hamano
2020-02-26 22:22     ` Junio C Hamano
2020-02-27 15:42       ` Johannes Schindelin
2020-02-26 20:09 ` [PATCH 2/3] ci: prevent `perforce` from being quarantined Johannes Schindelin via GitGitGadget
2020-02-26 20:09 ` [PATCH 3/3] Azure Pipeline: switch to the latest agent pools Johannes Schindelin via GitGitGadget
2020-02-27 13:23 ` [PATCH v2 0/3] ci: upgrade to the latest Azure Pipelines " Johannes Schindelin via GitGitGadget
2020-02-27 13:23   ` [PATCH v2 1/3] t/lib-httpd: avoid using macOS' sed Johannes Schindelin via GitGitGadget
2020-02-27 13:23   ` [PATCH v2 2/3] ci: prevent `perforce` from being quarantined Johannes Schindelin via GitGitGadget
2020-02-27 13:23   ` [PATCH v2 3/3] Azure Pipeline: switch to the latest agent pools Johannes Schindelin via GitGitGadget

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=nycvar.QRO.7.76.6.2002290054540.11433@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=emaste@freebsd.org \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.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.