Le 11/11/13 16:10, addshorewiki a écrit :
> For the benefit of the list!
>
> https://github.com/huggle/huggle3-qt-lx/commit/560508031c860e942a1df36cb85f140043d1
>
> https://travis-ci.org/huggle/huggle3-qt-lx/builds
Awesome :-]
--
Antoine "hashar" Musso
__
Cool thing :o
good job
On Mon, Nov 11, 2013 at 4:10 PM, addshorewiki wrote:
> For the benefit of the list!
>
> https://github.com/huggle/huggle3-qt-lx/commit/560508031c860e942a1df36cb85f140043d1
>
> https://travis-ci.org/huggle/huggle3-qt-lx/builds
>
> Addshore
>
>
> On 9 November 2013 00:33
For the benefit of the list!
https://github.com/huggle/huggle3-qt-lx/commit/560508031c860e942a1df36cb85f140043d1
https://travis-ci.org/huggle/huggle3-qt-lx/builds
Addshore
On 9 November 2013 00:33, addshorewiki wrote:
> Petr
>
> I'll try to setup Travis tests to run on every github commi
Petr
I'll try to setup Travis tests to run on every github commit on Monday. :)
That seems like the best solution as the repo is on github!
Also this way you'll be able to see the status of the tests for all
branches and pull requests etc :-)
Addshore
On 8 Nov 2013 17:22, "Petr Bena" wrote:
>
On Fri, 8 Nov 2013, at 20:51, Petr Bena wrote:
> Hi,
>
> would anyone experienced (like hashar) be interested in setup of
> jekins on wikimedia labs so that we can get a unit test environment
> available to all devs for any projects, written in languages like:
>
> * C
> * C++
> * Python
> * PHP
to explain how QT unit testing works a bit more, it's basically
another QT project that includes the source code from master branch
and produces a binary file (called tst_testmain) which can be executed
with various parameters and executes the unit tests defined in its
source code, for example:
pe
Yes, I made a simple unit test suite for huggle, which uses internal
QT unit test system, basically what I need to do is
* periodically pull the latest version of source code from master branch
* build the test suite (if build is failed submit this information)
* execute test suite (qt unit test s
Le 08/11/13 11:21, Petr Bena a écrit :
> would anyone experienced (like hashar) be interested in setup of
> jekins on wikimedia labs so that we can get a unit test environment
> available to all devs for any projects, written in languages like:
>
> * C
> * C++
> * Python
> * PHP
If the project is
Le 08/11/13 11:24, Petr Bena a écrit :
> I noticed there is "integration" project, but what its status is, I don't know
That is a play ground area. Merely intended to test out new features
for later inclusion in production.
--
Antoine "hashar" Musso
__
TBH I have no idea which sw for this is best, whatever that is working
I am fine with... I thought people are using jenkins for MW, so there
are likely more people who have experience witht hat
On Fri, Nov 8, 2013 at 1:14 PM, Jeroen De Dauw wrote:
> Hey,
>
> What about using TravisCI or any of th
Hey,
What about using TravisCI or any of the many alternatives? I'm not sure
what the benefit would be of setting up and maintaining something like that
yourself.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil. ~=[,,_,,]:3
--
I noticed there is "integration" project, but what its status is, I don't know
On Fri, Nov 8, 2013 at 11:21 AM, Petr Bena wrote:
> Hi,
>
> would anyone experienced (like hashar) be interested in setup of
> jekins on wikimedia labs so that we can get a unit test environment
> available to all devs
Hi,
would anyone experienced (like hashar) be interested in setup of
jekins on wikimedia labs so that we can get a unit test environment
available to all devs for any projects, written in languages like:
* C
* C++
* Python
* PHP
+ other frequently used languages
I think it would be useful for s
13 matches
Mail list logo
