all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Moritz Ulrich <moritz@tarn-vedra.de>
To: "Emacs developers" <emacs-devel@gnu.org>
Subject: Continuous Integration for package.el Packages
Date: Sun, 07 Jul 2013 13:34:23 +0200	[thread overview]
Message-ID: <8738rqk3i8.fsf@moritz-x230.lan> (raw)

-----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.

Nix is a pretty good fit for this kind of tests because it limits access
to all resources. This prevents leaking of the host environment into the
build, preventing implicit dependencies.

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!


Cheers,
Moritz Ulrich


[1]: http://nixos.org/
[2]: http://hydra.tarn-vedra.de/jobset/package-el-packages/next#tabs-status
[3]: https://github.com/NixOS/nixpkgs/pull/664

- -- 
Moritz Ulrich
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBCAAGBQJR2VJCAAoJEKnhzHnsv6QyyRkQAKTWZLRLialJeWKBgOu4TTft
A0xN772SNDgfe775O+RFNVpI850npM72JgTAVUtphJtE9amd7ovl7uBOZ3bo6TPF
XdsQzDRZtV5pMNur6C8JQijyNtVwcMYivOboZeTe/z1qsuGGVsxaAnUI2wYeYVRr
babNWMkgaMN82U7xPdLdBvk9hqelpPRhuOiqF4A9DMxj55OJolRuFGssBSlBMFpn
ql3UsumfhgoZ1ZFbLl8qr0X/g92Rivr6FHLZvcetnpL0p6eckxQMRH/fopKbrEJU
5Ou6luTTVHpi8E7obUpChEerXC+RJ/4OJuXe4zXPGoBHbWYBCfyKj2kK8w+8KwWA
Ub3cF1A5jTpPPx4HrCU9TwVonSmJ8H2STTDc/9Qy5Ry5ElyHexPTKzuZoETe6uKV
t+GCOUAfH4KjCviDHyw70PAt3ccmqq8b5kzfNmRTSnnHaGuK1+jUdJYfrYrYUs9y
cJikZm+QmpAvj4fUkAmoCBf0wVtMHIwuNaxtJFQ3bLGOJ/YTCxQgw2SvE3YqSFmD
oPUo9vIWs2cnom91YTF+YEUtnwqbROF4IEu0EsvQMbHl0rtp6Ww3k9oUxUbVEm2c
yV6l8QLz58PQnn4vaOs9rVPr7qJOzDb/Z1W6b5Lr55r663n78ofy5SL3Jmz+TPtZ
5Zkr0ZsNi2QOcyd6+dUp
=a7Ad
-----END PGP SIGNATURE-----



             reply	other threads:[~2013-07-07 11:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-07 11:34 Moritz Ulrich [this message]
2013-07-07 12:56 ` Continuous Integration for package.el Packages Dmitry Gutov
2013-07-07 15:51   ` Moritz Ulrich
2013-07-07 16:26 ` Sebastian Wiesner
2013-07-11  7:43   ` Moritz Ulrich
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=8738rqk3i8.fsf@moritz-x230.lan \
    --to=moritz@tarn-vedra.de \
    --cc=emacs-devel@gnu.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 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.