Re: [GRASS-dev] [GRASS GIS] #761: Setup to use the OSGeo BuildBot

[GRASS GIS]

#761: Setup to use the OSGeo BuildBot
--+-
  Reporter:  hamish   |  Owner:  grass-dev@…
  Type:  task | Status:  closed
  Priority:  normal   |  Milestone:
 Component:  Compiling|Version:  svn-trunk
Resolution:  wontfix  |   Keywords:  buildbot
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by martinl):

 * status:  new => closed
 * resolution:   => wontfix
 * milestone:  7.2.4 =>


-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #761: Setup to use the OSGeo BuildBot

[GRASS GIS]

#761: Setup to use the OSGeo BuildBot
-+--
 Reporter:  hamish   |   Owner:  grass-dev@…  
 Type:  task |  Status:  new  
 Priority:  normal   |   Milestone:  7.1.0
Component:  Compiling| Version:  svn-trunk
 Keywords:  buildbot |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--
Changes (by neteler):

  * milestone:  7.0.0 = 7.1.0


Comment:

 See also

 http://wiki.osgeo.org/wiki/Infrastructure_Transition_Plan_2014#Future_Needs

 Perhaps there will be option to use

 https://osuosl.org/services/supercell

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/761#comment:1
GRASS GIS http://grass.osgeo.org

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #761: Setup to use the OSGeo BuildBot

[GRASS GIS]

#761: Setup to use the OSGeo BuildBot
-+--
 Reporter:  hamish   |   Owner:  grass-dev@lists.osgeo.org
 Type:  task |  Status:  new  
 Priority:  normal   |   Milestone:  7.0.0
Component:  Compiling| Version:  svn-trunk
 Keywords:  buildbot |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--
 Hi,

 I would be nice to use the OSGeo BuildBot to do nightly builds (tests) of
 the 3 main SVN branches.

 see
  * http://wiki.osgeo.org/wiki/BuildBot_Configuration
  * https://svn.osgeo.org/osgeo/buildbot/
  * http://buildbot.osgeo.org/


 I suppose the course of action would be to clone the gdal config/ in osgeo
 SVN, modify it for grass, then contact the SAC  send them the files.
 Probably some -dev packages would need to be installed on the blade server
 as well, and always-on remote MacOSX + MS-Win slaves be recruited.

 Once working some module-of-the-day style javascript magic could convert
 the latest branch result into a green/red/orange colored font
 color=#rrggbb size=+2bull;/font next to the name of each SVN
 branch on the web page, or some other passive reporting mechanism.


 Hamish

-- 
Ticket URL: https://trac.osgeo.org/grass/ticket/761
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev