public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Kolen Cheung
	<christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Changing CI from Travis to CircleCI
Date: Sun, 27 Jan 2019 12:33:41 -0800	[thread overview]
Message-ID: <m28sz5rgbe.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <ece2aafd-fccf-4316-93a0-ff9735ac7322-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Partly because of
https://news.ycombinator.com/item?id=18978251
I worry more about the future of Travis.

Partly because, in my testing so far, CircleCI seems
more solid and reliable.

Partly because I like the configuration better for
CircleCI.

Actually it would be quite easy to add the building
of nightlies to pandoc's regular CircleCI script.

https://circleci.com/docs/2.0/workflows/#scheduling-a-workflow


Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> A bit of digression here: could you say why you've made the move? I've been tempted to migrate as well because I'm getting more and more problems from Travis especially in its macOS instances, and one of the pros of circleCI is its support of using docker images. But I'm yet to have time to learn about how to migrate. May be I'll start by pandoc's example and replicate pandoc-nightly using circldCI instead (pandoc-nightly is basically just a travis script.)
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ece2aafd-fccf-4316-93a0-ff9735ac7322%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m28sz5rgbe.fsf%40johnmacfarlane.net.
For more options, visit https://groups.google.com/d/optout.


      parent reply	other threads:[~2019-01-27 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 17:05 John MacFarlane
     [not found] ` <m2va2cy8fw.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-01-27 12:42   ` Kolen Cheung
     [not found]     ` <ece2aafd-fccf-4316-93a0-ff9735ac7322-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-01-27 20:33       ` John MacFarlane [this message]

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=m28sz5rgbe.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).