From: Moritz Ulrich <moritz@tarn-vedra.de>
To: "Sebastian Wiesner" <lunaryorn@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Continuous Integration for package.el Packages
Date: Thu, 11 Jul 2013 09:43:31 +0200 [thread overview]
Message-ID: <8738rlmti4.fsf@moritz-x230.lan> (raw)
In-Reply-To: <CALf2awQ1FqNnSCrr+SYui+doadGkpgmGhnZ9qUsEkhtxeiK93w@mail.gmail.com>
Sebastian Wiesner writes:
> 2013/7/7 Moritz Ulrich <moritz@tarn-vedra.de>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>>
>> Hello,
>>
>> During my efforts to integrate package.el packages into the Nix[1]
>> package manager, I started running automatic builds on all packages
>> available in GNU ELPA and Marmalade packages.
>
> Do you intend to test MELPA, too? It builds snapshot versions, which
> are more interesting to test.
I'll see if I find time to setup MELPA too. You're right - it's more
interesting.
>> The results are available on my Hydra instance[2]. Most build errors are
>> caused by missing 'Version' headers. Some others fail because they
>> depend on packages neither available in ELPA nor in Marmalade (visible
>> in the 'Evaluation Errors' tab).
>>
>> The code implementing all this is available on Github[3]. A cronjob
>> fetches new releases every four hours, Hydra starts building soon after.
>>
>> What do you think of this? Is it useful? Does your build fails, even if
>> it works on your local Emacs instance? Please tell me!
>
> To be honest, it is not useful for me.
>
> I already have a more powerful setup for automatically build and test
> my Flycheck package. It's based on Carton and Vagrant to create
> automated and repeatable VMs for local unit testing and Travis CI to
> build my package and run my ERT tests after every single push.
>
> As long as you do not run my ERT tests with all necessary dependencies
> (beyond just package.el deps), you don't tell me anything I didn't
> already know.
The code currently loads all .el files with 'test' in their name and
runs ert afterwards. This won't work with non-package.el dependencies
though. Nix blocks access on environment which isn't explicitly listed
in the buildInputs.
To add native dependencies, package.el would need a new dependency field
listing native dependencies. This won't be easy, but would make
installations way more reproducible.
--
Moritz Ulrich
next prev parent reply other threads:[~2013-07-11 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 11:34 Continuous Integration for package.el Packages Moritz Ulrich
2013-07-07 12:56 ` Dmitry Gutov
2013-07-07 15:51 ` Moritz Ulrich
2013-07-07 16:26 ` Sebastian Wiesner
2013-07-11 7:43 ` Moritz Ulrich [this message]
2013-07-07 20:53 ` Richard Stallman
2013-07-11 7:34 ` Moritz Ulrich
2013-07-11 8:14 ` Moritz Ulrich
2013-08-20 9:19 ` Bastien
2013-08-02 17:17 ` Glenn Morris
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=8738rlmti4.fsf@moritz-x230.lan \
--to=moritz@tarn-vedra.de \
--cc=emacs-devel@gnu.org \
--cc=lunaryorn@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.