On Monday 03 May 2010 10:05:04 Andreas Jaeger wrote: > On Monday 03 May 2010 10:51:38 Jeremiah Foster wrote: > > [...] > > Good stuff. I look forward to pushing sources into OBS. I think it would > > be great if I could just set up a cron job to push a tag from my git repo > > into OBS. Is that sort of automated building possible on the OBS side? > > i.e. can a process push to the OBS or does it have to be a human? > > The command line client for obs called osc allows to do quite a lot of > scripting. And if that fails, you can access the public API directly (via > curl or osc). So, you need to setup the cron job on your site but should > be able to push to obs from it without problems,
While we are asking questions... Will I be able to run the build itself on my own system? I.e. replicate the MeeGo OBS environment (when it exists) on my own system so that I can do builds locally but be confident they will work when I submit them to the real OBS? My reasoning is that for Maemo today I automatically build about 120 packages every night. I don't suppose that the MeeGo OBS wants to support each developer doing so many builds every day. I also do not want all the results from those builds necessarily going straight into some repository that users might be using (we haven't worked out the repositories yet, but I wouldn't want every nightly build to end up in extras-devel for Maemo -- I wouldn't want to release until code is tested). So, I assume I will want to build locally. But I really want confidence that if my local build succeeds, the real OBS build will also succeed (no problems with build dependencies, for example) so I want to reproduce the OBS as closely as possible. Graham _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
