From: Bastien <bzg@altern.org>
To: Achim Gratz <Stromeko@Nexgo.DE>
Cc: Jason Dunsmore <jason@dunsmor.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] ob-sql.el: probably an extra paren
Date: Sat, 06 Apr 2013 02:46:20 +0200 [thread overview]
Message-ID: <87txnkxz1r.fsf@bzg.ath.cx> (raw)
In-Reply-To: <kih30r$as3$1@ger.gmane.org> (Achim Gratz's message of "Fri, 22 Mar 2013 08:59:38 +0100")
Hi,
Achim Gratz <Stromeko@Nexgo.DE> writes:
> Hudson. However, I don't think that a CI framework is what we need or
> want. As I said, simply running the tests (preferrably with two different
> versions of Emacs) should be enough for now. Unless we hear from Jason if
> he thinks the server can take the extra load its a moot point to discuss
> details, but I think this can be done in one of the Git hooks (much like
> Worg triggers publishing).
Yagnesh Raghava Yakkala <hi@yagnesh.org> writes:
> About hudson/jenkins (any other CI), If we have resources on the server, I
> would say we should go for it. That will remove Bastien's concern of slowing
> down development because of running tests by hand.
I'm copying Jason -- the idea is to run tests on the servers via a Git
hook, the same way that a Git hook publishes Worg. If the tests fail,
the committer would get a warning and the commit would be discarded.
Jason, do you think it's feasible? Enough? I guess hudson/travis
is really too much for our needs.
Thanks,
--
Bastien
next prev parent reply other threads:[~2013-04-06 0:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 2:54 [BUG] ob-sql.el: probably an extra paren Nick Dokos
2013-03-20 6:47 ` Bastien
2013-03-20 12:39 ` Sebastien Vauban
2013-03-20 13:47 ` Bastien
2013-03-21 8:28 ` Achim Gratz
2013-03-21 13:41 ` Bastien
2013-03-21 14:03 ` Nicolas Richard
2013-03-21 16:58 ` Yagnesh Raghava Yakkala
2013-03-21 17:31 ` Bastien
2013-03-21 18:40 ` tests with travis-ci (was: [BUG] ob-sql.el: probably an extra paren) Yagnesh Raghava Yakkala
2013-03-21 20:41 ` tests with travis-ci Bastien
2013-03-21 22:20 ` Yagnesh Raghava Yakkala
2013-03-22 7:56 ` Yann Hodique
2013-03-22 10:40 ` Yagnesh Raghava Yakkala
2013-03-31 19:07 ` Yann Hodique
2013-03-22 6:40 ` Andreas Röhler
2013-03-22 12:55 ` Nick Dokos
2013-03-22 13:07 ` Andreas Röhler
2013-03-21 17:38 ` [BUG] ob-sql.el: probably an extra paren Achim Gratz
2013-03-21 17:59 ` Bastien
2013-03-22 7:01 ` Achim Gratz
2013-03-22 7:36 ` Bastien
2013-03-22 7:59 ` Achim Gratz
2013-04-06 0:46 ` Bastien [this message]
2013-03-22 10:44 ` Yagnesh Raghava Yakkala
2013-03-21 8:37 ` Sebastien Vauban
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txnkxz1r.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=Stromeko@Nexgo.DE \
--cc=emacs-orgmode@gnu.org \
--cc=jason@dunsmor.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).