Hi,
Achim Gratz 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 loa
Hello Achim,
On Mar 22 2013, Achim Gratz wrote:
> As for Travis CI: a website that shows absolutely nothing when JavaScript is
> turned off? No, thanks.
Agreed although travis-ci source is under FSF approved license.
About hudson/jenkins (any other CI), If we have resources on the server, I
Am 22.03.2013 08:36, schrieb Bastien:
Do you know any free (as-in-speech), easy-to-use alternative?
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. U
Achim Gratz writes:
> Am 21.03.2013 18:59, schrieb Bastien:
>> Please see my reply to Yagnesh.
>>
>> It clearly describes a situation where automatically running tests
>> with a pre-push hook would be a problem.
>
> You keep mentioning a pre-push-hook to be run on the developers
> machine.
That
Am 21.03.2013 18:59, schrieb Bastien:
Please see my reply to Yagnesh.
It clearly describes a situation where automatically running tests
with a pre-push hook would be a problem.
You keep mentioning a pre-push-hook to be run on the developers machine.
However, the test would run on the server
There is no need to be unpleasant and to describe my attitude as
"cavalier".
Please see my reply to Yagnesh.
It clearly describes a situation where automatically running tests
with a pre-push hook would be a problem.
--
Bastien
Am 21.03.2013 14:41, schrieb Bastien:
The test are not automatic, they are manually triggered, so we don't
have an "automated tests framework" -- or am I misunderstanding what
an automated test framework is?
What you probably have in mind is a continuous integration framework
that triggers the
Hello Yagnesh,
Yagnesh Raghava Yakkala writes:
> We can use travis-ci for automated tests, I just run tests for org-mode¹ on
> travis
> with emacs-snapshot. Magit has been setup recently to run tests for multiple
> emacs versions² (emacs23, emacs24 and snapshot). travis has a facility to send
>
Hello Bastien,
We can use travis-ci for automated tests, I just run tests for org-mode¹ on
travis
with emacs-snapshot. Magit has been setup recently to run tests for multiple
emacs versions² (emacs23, emacs24 and snapshot). travis has a facility to send
mails if a test fails.
I see you have or
Bastien writes:
> I often have only 10 minutes at hand, make a few trivial changes, and
> push. For me, a mandatory pre-push hook running the test suite would
> be a useless burden for 50% of my commits. This would irritate me.
orgmode.org could run a post-receive hook and report any failure to
Hi Achim,
Achim Gratz writes:
>> If anyone knows how to setup an automated tests framework for Org,
>> feel free to go ahead, we will use it and monitor broken tests to
>> see what's wrong in the code or in the tests or in the environment
>> running the tests.
>
> We already have one,
The test
Hi Bastien,
Bastien wrote:
> "Sebastien Vauban" writes:
>> Nick Dokos wrote:
>>> Can we please make it an invariable practice to run `make test' before
>>> every push?
>>
>> Isn't it possible to put such in some sort of Git pre-commit hook (or
>> pre-push hook), so that it gets automatically enfor
Am 20.03.2013 14:47, schrieb Bastien:
If anyone knows how to setup an automated tests framework for Org,
feel free to go ahead, we will use it and monitor broken tests to
see what's wrong in the code or in the tests or in the environment
running the tests.
We already have one, what Nick and Se
Hi Sébastien,
"Sebastien Vauban"
writes:
> Nick Dokos wrote:
>> Can we please make it an invariable practice to run `make test' before
>> every push?
>
> Isn't it possible to put such in some sort of Git pre-commit hook (or pre-push
> hook), so that it gets automatically enforced?
If anyone k
Hi Nick,
Nick Dokos wrote:
> Can we please make it an invariable practice to run `make test' before
> every push?
Isn't it possible to put such in some sort of Git pre-commit hook (or pre-push
hook), so that it gets automatically enforced?
Best regards,
Seb
--
Sebastien Vauban
Hi Nick,
Nick Dokos writes:
> Compiling it I get
This is fixed, thanks.
--
Bastien
16 matches
Mail list logo
