Ticket #102 (closed task: fixed)

Opened 5 years ago

Last modified 3 years ago

Move buildbot configuration files to SVN

Reported by: mloskot Owned by: mloskot
Priority: major Milestone:
Component: Systems Admin Keywords: buildbot
Cc:

Description

We've discussed with Hobu an idea of keeping Buildbot configuration files under control of SVN in order to:

  • keep things in order
  • have a simple backup system
  • track changes easily, especially if I won't be the only person editing these files

Recently, I've redesigned the Buildbot configuration and now every Buildbot instance is a configured by a number of files, so I'd like to ask/propose if it would be a good idea to move it to SVN and organize per project/instance.

Change History

Changed 4 years ago by neteler

Sounds like a good idea.

I would extend it to the cronjobs which I am implementing on download.osgeo.org right now for the GRASS project (creation of prog-man, source tarballs etc).

Changed 4 years ago by mloskot

Markus, good idea. I will keep Buildbot cronjobs there too.

Changed 4 years ago by mloskot

Dear SAC Fellows, I'd like to move forward with this task? What SVN URL should I use, where to put the buildbot module?

Changed 4 years ago by mloskot

  • owner changed from sac@… to mloskot
  • status changed from new to assigned

Changed 3 years ago by mloskot

Thanks Howard for preparing repository (r1496).

I've started implementing this proposal. A bunch of first changesets corresponding to BuildBot configuration import to the repository are from r1497 to r1509.

Work in progress

Changed 3 years ago by mloskot

  • status changed from assigned to closed
  • resolution set to fixed

Second part of new configuration import to the repository has been applied, from r1520 to r1529.

The transition has completed. Closing the ticket.

Changed 3 years ago by mloskot

Next, I'm going to updated the  BuildBot Configuration manual on the Wiki.

Changed 3 years ago by mloskot

I have updated the BuildBot Configuration on Wiki.

The task has been accomplished.

Note: See TracTickets for help on using tickets.