[SAC] Please disable GDAL "Continuous Builds" on buildbot

Committees SAC mailing list
1

Mateusz,

Could you please disable the rebuild-on-commit logic for telascience-quick?
I believe this is resulting in too much activity on the server.

Thanks,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent

2

On Nov 12, 2008, at 10:06 AM, Frank Warmerdam wrote:

Mateusz,

Could you please disable the rebuild-on-commit logic for telascience-quick?
I believe this is resulting in too much activity on the server.

I have disabled the build-on-commit notifications for both GDAL and MapServer. To re-enable, the line in each repository's post-commit script must be uncommented.

Howard

3

Frank Warmerdam kirjoitti:

Mateusz,

Could you please disable the rebuild-on-commit logic for telascience-quick?
I believe this is resulting in too much activity on the server.

I took out the telascience-quick by commenting out the addBuilder command in a_telascience.py. There is also a common configuration object in _common.py, which now (since Nov 3?) has config['quick'] = False. These are both in /osgeo/buildbot/gdal/buildmaster/config

I already sorted out once how the scheduling is done, but forgot it :wink: The configuration is a bit hairy since the pieces are spread into several files. I'd like to have my gdal-msys build happen only in our night but it's not easy since the scehduler is shared between slaves.

I'm not sure if the current schedulers are just twice a day or is the scheduler, which starts a build after a certain time after commits, is in effect.

Ari

Thanks,

--
Prof. Ari Jolma
Environmental Management Information Technology
Teknillinen Korkeakoulu / Helsinki University of Technology
tel: +358 9 4511 address: POBox 5300, 02015 TKK, Finland
Email: ari.jolma at tkk.fi URL: http://geoinformatics.tkk.fi

4

Frank Warmerdam pisze:

Mateusz,

Could you please disable the rebuild-on-commit logic for telascience-quick?
I believe this is resulting in too much activity on the server.

Frank,

For all buildbot instances or for GDAL only?

I see Hobu has already fixed it, am I correct?

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org

5

Mateusz Loskot wrote:

Frank Warmerdam pisze:

Mateusz,

Could you please disable the rebuild-on-commit logic for telascience-quick?
I believe this is resulting in too much activity on the server.

Frank,

For all buildbot instances or for GDAL only?

I see Hobu has already fixed it, am I correct?

Mateusz,

I only meant for GDAL though I'm not clear what other instances might being
doing it too. I believe it is now taken care of. I'm trying to diagnose
why xblade14 still seems saturated much of the time.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent

6

Ari Jolma pisze:

Frank Warmerdam kirjoitti:

Mateusz,

Could you please disable the rebuild-on-commit logic for telascience-quick?
I believe this is resulting in too much activity on the server.

I took out the telascience-quick by commenting out the addBuilder command in a_telascience.py. There is also a common configuration object in _common.py, which now (since Nov 3?) has config['quick'] = False. These are both in /osgeo/buildbot/gdal/buildmaster/config

Ari,

To disable build on commit we only need to comment these lines
in master.cfg file of a buildbot instance:

from buildbot.changes.pb import PBChangeSource

and

c['change_source'] = PBChangeSource(prefix='trunk/')

I've fixed it for GDAL

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org

7

Mateusz Loskot kirjoitti:

Ari,

To disable build on commit we only need to comment these lines
in master.cfg file of a buildbot instance:

Thanks, I was looking for master.cfg but did not find it since it does not have .py extension although it is python. Too much work and no play I guess.

from buildbot.changes.pb import PBChangeSource

and

c['change_source'] = PBChangeSource(prefix='trunk/')

I've fixed it for GDAL

ok, what does the "config['quick'] = False" do?

Regards,

Ari

Best regards,

--
Prof. Ari Jolma
Environmental Management Information Technology
Teknillinen Korkeakoulu / Helsinki University of Technology
tel: +358 9 4511 address: POBox 5300, 02015 TKK, Finland
Email: ari.jolma at tkk.fi URL: http://geoinformatics.tkk.fi

8

Ari Jolma pisze:

Mateusz Loskot kirjoitti:

Ari,

To disable build on commit we only need to comment these lines
in master.cfg file of a buildbot instance:

Thanks, I was looking for master.cfg but did not find it since it does not have .py extension although it is python. Too much work and no play I guess.

from buildbot.changes.pb import PBChangeSource

and

c['change_source'] = PBChangeSource(prefix='trunk/')

I've fixed it for GDAL

ok, what does the "config['quick'] = False" do?

I guess it disables quick builders completely.
Sorry, I have too weak net link to search through buildbot documentation and mailing lists about this option.

Anyway, what I'm sure is that disabling change source does the job.

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org