From: "Nikolay Aleksandrovich Pavlov (ZyX)" <kp-pav@yandex.ru>
To: Julien Nicoulaud <julien.nicoulaud@gmail.com>,
Mailing-list zsh-users <zsh-users@zsh.org>
Subject: Re: Zsh docker images
Date: Tue, 15 Aug 2017 01:41:08 +0300 [thread overview]
Message-ID: <368651502750468@web46j.yandex.ru> (raw)
In-Reply-To: <CA+mcLN48bD4By2tjqPcu42hcF1JQg=boFuBCbGWvQqAgoZhSqw@mail.gmail.com>
15.08.2017, 01:12, "Julien Nicoulaud" <julien.nicoulaud@gmail.com>:
> Hi all,
>
> I just wanted to advertise a small project that could be useful to other
> zsh users: https://github.com/zsh-users/zsh-docker
>
> This builds images of many versions of zsh (including a daily build of
> zsh's master branch) and deploys them to Docker Hub (
> https://hub.docker.com/u/zshusers).
>
> So you can do, for instance:
>
> $ docker run -it zshusers/zsh-5.3.1
>
> -> will launch an interactive session of zsh 5.3.1
>
> We use it to automatically test zsh-syntax-highlighting on all supported
> versions of zsh.
What you could just as well do without docker which would make travis run faster due to not needed `sudo: required` and ability to setup travis cache. For testing something locally your docker images make more sense because they are easier to use then compiling that big amount of zsh versions.
Also why you have no builds for PRs and why you don’t merge those 24 jobs into something like 7 (4.3*, 5.0*, 5.1*, 5.2*, 5.3*, 5.4*, master)? Less then twenty seconds to run tests in a single job, lots of time to initialize VMs and there is nothing which may prevent you from consequently running two docker commands in one job, or using two zsh versions via other means.
>
> Cheers,
> Julien
next prev parent reply other threads:[~2017-08-14 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 22:09 Julien Nicoulaud
2017-08-14 22:41 ` Nikolay Aleksandrovich Pavlov (ZyX) [this message]
2017-08-14 23:16 ` Julien Nicoulaud
2017-08-15 8:53 ` Nikolay Aleksandrovich Pavlov (ZyX)
2017-08-15 10:53 ` Julien Nicoulaud
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=368651502750468@web46j.yandex.ru \
--to=kp-pav@yandex.ru \
--cc=julien.nicoulaud@gmail.com \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).