I've started to worry about sfety of Buildbot configuration.
I have my own copies, but there is also need to track changes
as the fileset is quite big.
There are config files for every instance (min. 3 max unlimited number
of files), there are our own customizations and fixes to Buildbot core,
Buildbot status website HTML pages and styles, etc.
Yesterday, I upgraded form 0.7.4 yo 0.7.6 and I had to touch every file.
I'd feel better if I have easy way to backup files and track changes in
future for that cases. Also, if new maintainer will came, she can easily
find configuration history, etc.
I would propose that we host this configuration info (no logs! ) in the osgeoconfig repository. Currently, only three people have the ability to view or commit to this repository (Frank, myself, and Shawn), and we use it to store our apache configuration and cron scripts.
I motion to add Mateusz to the commit list for this repository to manage buildbot configuration.
/me starts with an obvious +1
Howard
On Nov 21, 2007, at 6:30 PM, Mateusz Loskot wrote:
I've started to worry about sfety of Buildbot configuration.
I have my own copies, but there is also need to track changes
as the fileset is quite big.
There are config files for every instance (min. 3 max unlimited number
of files), there are our own customizations and fixes to Buildbot core,
Buildbot status website HTML pages and styles, etc.
Yesterday, I upgraded form 0.7.4 yo 0.7.6 and I had to touch every file.
I'd feel better if I have easy way to backup files and track changes in
future for that cases. Also, if new maintainer will came, she can easily
find configuration history, etc.
I would propose that we host this configuration info (no logs! ) in
the osgeoconfig repository.
Hobu,
Certainly, no logs allowed
Currently, only three people have the
ability to view or commit to this repository (Frank, myself, and Shawn),
and we use it to store our apache configuration and cron scripts.
This place looks like a good candidate.
The Buildbot config scripts include slavenames/passwords for external
machines and I'd prefer to keep it a little confident, at least not
widely spread over the Internet
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 | President OSGeo, http://osgeo.org
I think one issue is that the buildbot config has sensitive info like passwords and such. We have been using http://svn.osgeo.org/osgeoconfig for stuff like that, but only sbarnes, hobu, and warmerdam have commit and read access to it currently.
I think one issue is that the buildbot config has sensitive info like
passwords and such. We have been using http://svn.osgeo.org/osgeoconfig
for stuff like that, but only sbarnes, hobu, and warmerdam have commit
and read access to it currently.
Frank, Hobu,
Yes, this is the case. I'd prefer to not to keep buildbot config files
in widely accessible repo.
So, if I could create 'buildbot' module in private repo, that is what I
need. Would it be possible?
I think one issue is that the buildbot config has sensitive info like
passwords and such. We have been using http://svn.osgeo.org/osgeoconfig
for stuff like that, but only sbarnes, hobu, and warmerdam have commit
and read access to it currently.
Frank, Hobu,
Yes, this is the case. I'd prefer to not to keep buildbot config files
in widely accessible repo.
So, if I could create 'buildbot' module in private repo, that is what I
need. Would it be possible?
Mateusz / Howard,
I'm somewhat nervous about having the osgeoconfig repository accessable
off osgeo1 and osgeo2. It contains a lot of very sensitive information.
Am I being silly?
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 | President OSGeo, http://osgeo.org
I think one issue is that the buildbot config has sensitive info like
passwords and such. We have been using http://svn.osgeo.org/osgeoconfig
for stuff like that, but only sbarnes, hobu, and warmerdam have commit
and read access to it currently.
Frank, Hobu,
Yes, this is the case. I'd prefer to not to keep buildbot config files
in widely accessible repo.
So, if I could create 'buildbot' module in private repo, that is what I
need. Would it be possible?
Mateusz / Howard,
I'm somewhat nervous about having the osgeoconfig repository accessable
off osgeo1 and osgeo2. It contains a lot of very sensitive information.
Am I being silly?
Frank,
I perfectly understand it.
What about having yet another hidden repository?
) in the osgeoconfig repository. Currently, only three people have the ability to view or commit to this repository (Frank, myself, and Shawn), and we use it to store our apache configuration and cron scripts.
) in