Markus Neteler writes:
> On Thu, Jun 9, 2016 at 11:14 AM, Rainer M Krug wrote:
> ...
>> Just realized the on-failure notification=s are still disabled - please
>> see my pull request where I enabled them again.
>>
>> https://github.com/GRASS-GIS/grass-ci/pull/2
>
> Done in r68656.
Thanks
Raine
On Thu, Jun 9, 2016 at 11:14 AM, Rainer M Krug wrote:
...
> Just realized the on-failure notification=s are still disabled - please
> see my pull request where I enabled them again.
>
> https://github.com/GRASS-GIS/grass-ci/pull/2
Done in r68656.
Markus
__
Rainer M Krug writes:
> Markus Neteler writes:
>
>> On Fri, Jun 3, 2016 at 1:43 PM, Rainer M Krug wrote:
>>> Markus Neteler writes:
>>>
On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote:
> Markus Neteler writes:
...
>> Anything to be done there? Was it integrated? Or stuc
Markus Neteler writes:
> On Fri, Jun 3, 2016 at 1:43 PM, Rainer M Krug wrote:
>> Markus Neteler writes:
>>
>>> On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote:
Markus Neteler writes:
>>> ...
> Anything to be done there? Was it integrated? Or stuck at
>
> https://trac.osge
On Fri, Jun 3, 2016 at 1:43 PM, Rainer M Krug wrote:
> Markus Neteler writes:
>
>> On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote:
>>> Markus Neteler writes:
>> ...
Anything to be done there? Was it integrated? Or stuck at
https://trac.osgeo.org/grass/ticket/2733
>>>
>>> I t
Just to make sure that this doesn't get lost again.
Rainer
Rainer M Krug writes:
> Markus Neteler writes:
>
>> On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote:
>>> Markus Neteler writes:
>> ...
Anything to be done there? Was it integrated? Or stuck at
https://trac.osgeo.or
Markus Neteler writes:
> On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote:
>> Markus Neteler writes:
> ...
>>> Anything to be done there? Was it integrated? Or stuck at
>>>
>>> https://trac.osgeo.org/grass/ticket/2733
>>
>> I think it was stuck - but I haven't looked at it since and I have n
On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote:
> Markus Neteler writes:
...
>> Anything to be done there? Was it integrated? Or stuck at
>>
>> https://trac.osgeo.org/grass/ticket/2733
>
> I think it was stuck - but I haven't looked at it since and I have no
> idea if it still works. I think
Markus Neteler writes:
> Hi,
>
> back to this topic:
>
> On Thu, Sep 3, 2015 at 5:24 PM, Rainer M Krug wrote:
>> Hi
>>
>> is anything happening in regards to the travis-ci integration? I did not
>> get any feedback or how I can submit it to the svn.
>>
>> In regards to testing: I know about the
Hi,
back to this topic:
On Thu, Sep 3, 2015 at 5:24 PM, Rainer M Krug wrote:
> Hi
>
> is anything happening in regards to the travis-ci integration? I did not
> get any feedback or how I can submit it to the svn.
>
> In regards to testing: I know about the python gunit tests [1]. Are
> there any
On Tue, Dec 15, 2015 at 1:56 AM, Vaclav Petras wrote:
>
> On Mon, Dec 14, 2015 at 5:50 PM, Martin Landa
> wrote:
>>
>> 2015-12-14 23:46 GMT+01:00 Martin Landa :
>> > Will update. I suggest to move file to trac (avoid duplication in
>> > different branches). What do you think? Martin
>>
>> we coul
wow
On Tue, Jul 21, 2015, 11:53 Ivan Minčík wrote:
> Hi all,
> we have just integrated Travis Continuous Integration system [1] to the
> GRASS source code. Every commit is now build in Travis [2] using gcc and
> clang. In case the build fails, error message should go to GRASS-dev list.
>
>
> 1 -
On Mon, Dec 14, 2015 at 5:50 PM, Martin Landa
wrote:
> 2015-12-14 23:46 GMT+01:00 Martin Landa :
> > Will update. I suggest to move file to trac (avoid duplication in
> > different branches). What do you think? Martin
>
> we could move to trac most (all) of text files from doc svn directory...
2015-12-14 23:46 GMT+01:00 Martin Landa :
> Will update. I suggest to move file to trac (avoid duplication in
> different branches). What do you think? Martin
we could move to trac most (all) of text files from doc svn directory...
Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gi
Hi Markus,
2015-12-14 23:34 GMT+01:00 Markus Neteler :
> Who has access to our Travis-CI in order to connect it to Coverity scan?
I have the access.
> (please add that info to doc/infrastructure.txt in SVN)
Will update. I suggest to move file to trac (avoid duplication in
different branches). W
On Sep 9, 2015 6:47 PM, "Markus Neteler" wrote:
>
> Hi,
>
> I just saw (again) this page:
> https://scan.coverity.com/travis_ci
>
> Could we now feed coverity scan through Travis?
Who has access to our Travis-CI in order to connect it to Coverity scan?
(please add that info to doc/infrastructure
Hi,
I just saw (again) this page:
https://scan.coverity.com/travis_ci
Could we now feed coverity scan through Travis?
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Vaclav Petras writes:
> Hi Rainer,
>
> On Thu, Sep 3, 2015 at 11:24 AM, Rainer M Krug wrote:
>>
>> Hi
>>
>> is anything happening in regards to the travis-ci integration? I did not
>> get any feedback or how I can submit it to the svn.
>
> Ideally open a ticket a submit a diff. That's what I do
Hi Rainer,
On Thu, Sep 3, 2015 at 11:24 AM, Rainer M Krug wrote:
>
> Hi
>
> is anything happening in regards to the travis-ci integration? I did not
> get any feedback or how I can submit it to the svn.
Ideally open a ticket a submit a diff. That's what I do (although I can
actually commit) for
Hi
is anything happening in regards to the travis-ci integration? I did not
get any feedback or how I can submit it to the svn.
In regards to testing: I know about the python gunit tests [1]. Are
there any other tests which should be included in the scripts? Should
detailed results generated by t
Quick update: the tests are running, the forked github repo is
https://github.com/rkrug/grass-ci
and the travis-ci is here (the actually running one)
https://travis-ci.org/rkrug/grass-ci/builds/77509876
It looks good now.
Cheers,
Rainer
Rainer M Krug writes:
> Hi Ivan, Hi Markus,
>
> I h
Hi Ivan, Hi Markus,
I have looked at the .travis.yml at
[https://trac.osgeo.org/grass/browser/grass/trunk/.travis.ym]l
and merged it with mine by
1) moving the sections of the .travis.yml fiole into scripts:
- before_install :: .travis.$TRAVIS_OS_NAME.before_install.sh
- install::
On Tue, Jul 21, 2015 at 11:52 AM, Ivan Minčík wrote:
> Hi all,
> we have just integrated Travis Continuous Integration system [1] to the
> GRASS source code. Every commit is now build in Travis [2] using gcc and
> clang. In case the build fails, error message should go to GRASS-dev list.
>
>
> 1 -
On Tue, Jul 28, 2015 at 3:39 PM, Rainer M Krug wrote:
...
>> If you tell me where (on which page in the wiki or on a new page?), I could
>> probably add it this evening - Oh -
>> do I need write access to the wiki?
Yes. "Thanks" to the spammers we cannot avoid that.
There is a related registrati
Markus Neteler writes:
> On Tue, Jul 28, 2015 at 3:39 PM, Rainer M Krug wrote:
> ...
>>> If you tell me where (on which page in the wiki or on a new page?), I could
>>> probably add it this evening - Oh -
>>> do I need write access to the wiki?
>
> Yes. "Thanks" to the spammers we cannot avoid
Rainer M Krug writes:
> Markus Neteler writes:
>
>> Hi Rainer,
>>
>> On Jul 28, 2015 10:11 AM, "Rainer M Krug" wrote:
>>>
>>> Ivan Mincik writes:
>> ...
>>
>>> I am using homebrew, a package manager for OSX. This simplifies the
>>> compilation significantly as it takes care of all dependencies
Markus Neteler writes:
> Hi Rainer,
>
> On Jul 28, 2015 10:11 AM, "Rainer M Krug" wrote:
>>
>> Ivan Mincik writes:
> ...
>
>> I am using homebrew, a package manager for OSX. This simplifies the
>> compilation significantly as it takes care of all dependencies. So the
>> installation script (cal
Hi Rainer,
On Jul 28, 2015 10:11 AM, "Rainer M Krug" wrote:
>
> Ivan Mincik writes:
...
> I am using homebrew, a package manager for OSX. This simplifies the
> compilation significantly as it takes care of all dependencies. So the
> installation script (called recipe) is at [1] and adapted from
Ivan Mincik writes:
> On 23.07.2015 10:42, Rainer M Krug wrote:
>> Ivan Minčík writes:
>>
>>> Hi all, we have just integrated Travis Continuous Integration
>>> system [1] to the GRASS source code. Every commit is now build in
>>> Travis [2] using gcc and clang. In case the build fails, error
>>>
On Mon, Jul 27, 2015 at 11:11 AM, Ivan Mincik wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Pietro, I have missed your email. Sorry for late answer.
>
> On 23.07.2015 09:22, Pietro wrote:
> > Dear Ivan,
> >
> > On Tue, Jul 21, 2015 at 11:52 AM, Ivan Minčík
> > wrote:
> >> Hi a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.07.2015 10:42, Rainer M Krug wrote:
> Ivan Minčík writes:
>
>> Hi all, we have just integrated Travis Continuous Integration
>> system [1] to the GRASS source code. Every commit is now build in
>> Travis [2] using gcc and clang. In case the bui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Pietro, I have missed your email. Sorry for late answer.
On 23.07.2015 09:22, Pietro wrote:
> Dear Ivan,
>
> On Tue, Jul 21, 2015 at 11:52 AM, Ivan Minčík
> wrote:
>> Hi all, we have just integrated Travis Continuous Integration
>> system [1] to
Ivan Minčík writes:
> Hi all,
> we have just integrated Travis Continuous Integration system [1] to the
> GRASS source code. Every commit is now build in Travis [2] using gcc and
> clang. In case the build fails, error message should go to GRASS-dev list.
>
This looks very nice - great. But I se
Dear Ivan,
On Tue, Jul 21, 2015 at 11:52 AM, Ivan Minčík wrote:
> Hi all,
> we have just integrated Travis Continuous Integration system [1] to the
> GRASS source code. Every commit is now build in Travis [2] using gcc and
> clang. In case the build fails, error message should go to GRASS-dev lis
Dear Ivan,
2015-07-21 11:52 GMT+02:00 Ivan Minčík :
> we have just integrated Travis Continuous Integration system [1] to the
> GRASS source code. Every commit is now build in Travis [2] using gcc and
> clang. In case the build fails, error message should go to GRASS-dev list.
thanks for your gr
Hi all,
we have just integrated Travis Continuous Integration system [1] to the
GRASS source code. Every commit is now build in Travis [2] using gcc and
clang. In case the build fails, error message should go to GRASS-dev list.
1 - https://trac.osgeo.org/grass/browser/grass/trunk/.travis.yml
2 -
36 matches
Mail list logo
