[opensuse-buildservice] setting up local build service
Hi list, I'm trying to set up my own build service, and I've followed the instructions in the README file that comes with obs-api, but I'm not having any luck. I sent a previous note to this list, but haven't had any responses so far. What channels do we have available to help with setup issues? Thanks, John --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 04 April 2008 17:41:33 wrote John Calcote:
Hi list,
I'm trying to set up my own build service, and I've followed the instructions in the README file that comes with obs-api, but I'm not having any luck. I sent a previous note to this list, but haven't had any responses so far. What channels do we have available to help with setup issues?
Please wait another week, I hope the version 0.9 will make this much more easy in future :) -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian, Adrian Schröter wrote:
On Friday 04 April 2008 17:41:33 wrote John Calcote:
Hi list,
I'm trying to set up my own build service, and I've followed the instructions in the README file that comes with obs-api, but I'm not having any luck. I sent a previous note to this list, but haven't had any responses so far. What channels do we have available to help with setup issues?
Please wait another week, I hope the version 0.9 will make this much more easy in future :) I got it to work now. To fix this problem, I did the following:
1. I uninstalled all osc-* and lighthttpd* packages, killed all running osc- and lighttpd-related processes, dropped all existing osc-related mysql databases, deleted the /srv/www/osc directory and the /etc/lighttpd directory. 2. I reinstalled the three osc packages - osc-server, osc-worker, and osc-api, along with all of their dependencies. 3. I meticulously followed the instructions in the file /usr/share/doc/package/osc-api/README.SUSE Works as advertised. I figured the problem was that I followed the wiki tutorial, which is out of date, then when it ddin't work, I tried to take another pass through the README.SUSE doc, but the installation was already hosed. Thanks, John --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Update... I've managed to mirror both the OpenSUSE:10.2 repository and the SLES 9 repository, but when I tried to mirror the SLE_10 (SDK) repository, the ruby import script just sits in an apparently endless loop printing this: ... --> trying to store previously unsaved projects, run [33679] SUSE:SLE-10:SDK => delayed --> trying to store previously unsaved projects, run [33680] SUSE:SLE-10:SDK => delayed --> trying to store previously unsaved projects, run [33681] SUSE:SLE-10:SDK => delayed --> trying to store previously unsaved projects, run [33682] SUSE:SLE-10:SDK => delayed --> trying to store previously unsaved projects, run [33683] SUSE:SLE-10:SDK => delayed --> trying to store previously unsaved projects, run [33684] SUSE:SLE-10:SDK => delayed --> trying to store previously unsaved projects, run [33685] SUSE:SLE-10:SDK => delayed --> trying to store previously unsaved projects, run [33686] SUSE:SLE-10:SDK => delayed --> trying to store previously unsaved projects, run [33687] SUSE:SLE-10:SDK => delayed ... As you can see, I've let this script run for around 50000 iterations. I don't know what it's doing, but I know what it's NOT doing - it's NOT importing the SLE_10:SDK that I mirrored. I've deleted the files and remirrored twice now, and both times, I've run into this barrier. I figured I've messed up the database somehow. Any ideas? Thanks, John John Calcote wrote:
Adrian,
Adrian Schröter wrote:
On Friday 04 April 2008 17:41:33 wrote John Calcote:
Hi list,
I'm trying to set up my own build service, and I've followed the instructions in the README file that comes with obs-api, but I'm not having any luck. I sent a previous note to this list, but haven't had any responses so far. What channels do we have available to help with setup issues?
Please wait another week, I hope the version 0.9 will make this much more easy in future :) I got it to work now. To fix this problem, I did the following:
1. I uninstalled all osc-* and lighthttpd* packages, killed all running osc- and lighttpd-related processes, dropped all existing osc-related mysql databases, deleted the /srv/www/osc directory and the /etc/lighttpd directory.
2. I reinstalled the three osc packages - osc-server, osc-worker, and osc-api, along with all of their dependencies.
3. I meticulously followed the instructions in the file /usr/share/doc/package/osc-api/README.SUSE
Works as advertised.
I figured the problem was that I followed the wiki tutorial, which is out of date, then when it ddin't work, I tried to take another pass through the README.SUSE doc, but the installation was already hosed.
Thanks, John
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
John Calcote
2. I reinstalled the three osc packages - osc-server, osc-worker, and osc-api, along with all of their dependencies.
3. I meticulously followed the instructions in the file /usr/share/doc/package/osc-api/README.SUSE
Works as advertised.
Phew :)
I figured the problem was that I followed the wiki tutorial, which is out of date, then when it didn't work, I tried to take another pass through the README.SUSE doc, but the installation was already hosed.
I really need to update the wiki install doc to just point to the
README.
John Calcote
Update...
I've managed to mirror both the OpenSUSE:10.2 repository and the SLES 9 repository, but when I tried to mirror the SLE_10 (SDK) repository, the ruby import script just sits in an apparently endless loop printing this: [...] Any ideas?
John, the updated obs server will have the repo mirroring built-in, so it would really be worth give at a few more days until the package is out. I'm traveling currently and don't have much chance to update the packages and the README for them this week but the test packages in openSUSE:Tools:Unstable are very close to what will be it, if you want to give them a try? You can check here on list how to set them up or wait for the update. S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Susanne, Thank you for the response. Adrian said I should wait till this week, but he didn't explain why. Now I see. I'll just wait. Regards, John Susanne Oberhauser wrote:
John,
the updated obs server will have the repo mirroring built-in, so it would really be worth give at a few more days until the package is out.
I'm traveling currently and don't have much chance to update the packages and the README for them this week but the test packages in openSUSE:Tools:Unstable are very close to what will be it, if you want to give them a try?
You can check here on list how to set them up or wait for the update.
S.
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi list,
I've been wondering something lately. Whenever someone points me to
the "Unstable" repository, and I try to use it, I get a slew of
dependencies that are not found in the repository set that I'm using
in my configured installation locations.
Well, I sort of expect this - these are updated packages, after all.
So I then try to add various repositories and try again, but I can
never quite get everything lined up.
What am I missing here? Is there a proper technique to using Unstable
or Factory repos?
Thanks in advance,
John
On Wed, Apr 9, 2008 at 3:03 PM, John Calcote
Susanne,
Thank you for the response. Adrian said I should wait till this week, but he didn't explain why. Now I see. I'll just wait.
Regards, John
Susanne Oberhauser wrote:
John,
the updated obs server will have the repo mirroring built-in, so it would really be worth give at a few more days until the package is out.
I'm traveling currently and don't have much chance to update the packages and the README for them this week but the test packages in openSUSE:Tools:Unstable are very close to what will be it, if you want to give them a try?
You can check here on list how to set them up or wait for the update.
S.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 11 April 2008 17:40:21 wrote John Calcote:
Hi list,
I've been wondering something lately. Whenever someone points me to the "Unstable" repository, and I try to use it, I get a slew of dependencies that are not found in the repository set that I'm using in my configured installation locations.
Well, I sort of expect this - these are updated packages, after all. So I then try to add various repositories and try again, but I can never quite get everything lined up.
What am I missing here? Is there a proper technique to using Unstable or Factory repos?
When you install packages from there via the "1-Click" button, you get possibly additionally needed repositories as well. There is unfortunatly no "additional repo" references in rpm-md meta data supported yet. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, as described in "openSUSE.org.xml", I have set up this project for use with <remoteurl>: <project name="openSUSE.org"> <title>openSUSE.org Project</title> <description>This project refers to projects hosted on the Build Service at the openSUSE.org project. This is important especially for the base projects which provides the distributions to build against by default. Your local Build Service instance will request, download and cache all needed sources or binary packages from the openSUSE.org project when you build against it. Use openSUSE.org:openSUSE:10.3 for example to build against the openSUSE:10.3 project as specified on the opensuse.org Build Service.</description> <remoteurl>https://<Mylogin>:<Mypasswd>@api.opensuse.org/</remoteurl> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> To check what happens, I have also added Build Repository in my OBS for openSUSE:Tools (a copy for of build.o.o/openSUSE:Tools for testing) like that: <repository name="RHEL_5"> <path repository="standard" project="openSUSE.org:RedHat:RHEL-5"/> <arch>i586</arch> <arch>x86_64</arch> </repository> Then the build for openSUSE:Tools/RHEL_5 should automagically start right now, correct? But I do not get a reaction in my "openSUSE:Tools", e.g. the build is stuck (does not start). What did I miss? Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Apr 11, 2008 at 06:20:27PM +0200, Martin Mohring wrote:
as described in "openSUSE.org.xml", I have set up this project for use with <remoteurl>:
<project name="openSUSE.org"> <title>openSUSE.org Project</title> <description>This project refers to projects hosted on the Build Service at the openSUSE.org project. This is important especially for the base projects which provides the distributions to build against by default. Your local Build Service instance will request, download and cache all needed sources or binary packages from the openSUSE.org project when you build against it.
Use openSUSE.org:openSUSE:10.3 for example to build against the openSUSE:10.3 project as specified on the opensuse.org Build Service.</description> <remoteurl>https://<Mylogin>:<Mypasswd>@api.opensuse.org/</remoteurl> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> </repository> </project>
Defining repositories in remoteurl projects doesn't make sense. But it shouldn't break things.
To check what happens, I have also added Build Repository in my OBS for openSUSE:Tools (a copy for of build.o.o/openSUSE:Tools for testing) like that:
<repository name="RHEL_5"> <path repository="standard" project="openSUSE.org:RedHat:RHEL-5"/> <arch>i586</arch> <arch>x86_64</arch> </repository>
Then the build for openSUSE:Tools/RHEL_5 should automagically start right now, correct?
Right.
But I do not get a reaction in my "openSUSE:Tools", e.g. the build is stuck (does not start). What did I miss?
Hard to tell without seeing any output from the scheduler. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, Michael Schroeder wrote:
On Fri, Apr 11, 2008 at 06:20:27PM +0200, Martin Mohring wrote:
as described in "openSUSE.org.xml", I have set up this project for use with <remoteurl>:
<project name="openSUSE.org"> <title>openSUSE.org Project</title> <description>This project refers to projects hosted on the Build Service at the openSUSE.org project. This is important especially for the base projects which provides the distributions to build against by default. Your local Build Service instance will request, download and cache all needed sources or binary packages from the openSUSE.org project when you build against it.
Use openSUSE.org:openSUSE:10.3 for example to build against the openSUSE:10.3 project as specified on the opensuse.org Build Service.</description> <remoteurl>https://<Mylogin>:<Mypasswd>@api.opensuse.org/</remoteurl> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> </repository> </project>
Defining repositories in remoteurl projects doesn't make sense. But it shouldn't break things.
That was just Adrians example (buildservice/docs/openSUSE.org.xml). If I leave away the <repository> stuff, I get an error when saving the project data.
To check what happens, I have also added Build Repository in my OBS for openSUSE:Tools (a copy for of build.o.o/openSUSE:Tools for testing) like that:
<repository name="RHEL_5"> <path repository="standard" project="openSUSE.org:RedHat:RHEL-5"/> <arch>i586</arch> <arch>x86_64</arch> </repository>
Then the build for openSUSE:Tools/RHEL_5 should automagically start right now, correct?
Right.
But I do not get a reaction in my "openSUSE:Tools", e.g. the build is stuck (does not start). What did I miss?
Hard to tell without seeing any output from the scheduler.
It need just a while to download the packages first before the build can start. So waiting 1 hour is not unusual, right? Looking 1 hour later I found the builds beeing started. Where are the packages beeing cached in the filesystem (which place)? Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Apr 11, 2008 at 08:17:16PM +0200, Martin Mohring wrote:
It need just a while to download the packages first before the build can start. So waiting 1 hour is not unusual, right? Looking 1 hour later I found the builds beeing started. Where are the packages beeing cached in the filesystem (which place)?
In "<bsdatadir>/remotecache/". I think it took so long because our AJAX server died (a bug somewhere in my code), thus your build service couldn't download the needed data. I'm just debugging this. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, Martin Mohring wrote:
Hi,
Michael Schroeder wrote:
On Fri, Apr 11, 2008 at 06:20:27PM +0200, Martin Mohring wrote:
But I do not get a reaction in my "openSUSE:Tools", e.g. the build is stuck (does not start). What did I miss?
Hard to tell without seeing any output from the scheduler.
It need just a while to download the packages first before the build can start. So waiting 1 hour is not unusual, right? Looking 1 hour later I found the builds beeing started. Where are the packages beeing cached in the filesystem (which place)? Yea, found it myself: /srv/obs/remotecache. What happens when it flooded my harddisk full? Can I just remove it?
Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Apr 11, 2008 at 08:23:05PM +0200, Martin Mohring wrote:
Yea, found it myself: /srv/obs/remotecache. What happens when it flooded my harddisk full? Can I just remove it?
Yes, you can just remove files. But there shouldn't be any need, the build service automatically deletes the files that were not used for a day. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, The new sample without <repository>: $ osc -A api.d-atasoft.com meta prj -F o.o.xml openSUSE.org Sending meta data... Cannot save meta data. Unknown error. HTTP Error 500: Internal Server Error Sorry, doesnt work. Martin <project name="openSUSE.org"> <title>openSUSE.org Project</title> <description>This project refers to projects hosted on the Build Service at the openSUSE.org project. This is important especially for the base projects which prov ides the distributions to build against by default. Your local Build Service instance will request, download and cache all needed sources or binary packages from the openSUSE.org project when you build against it. Use openSUSE.org:openSUSE:10.3 for example to build against the openSUSE:10.3 project as specified on the opensuse.org Build Service. </description> <!-- Keep in mind that this file is accessable via the api, before entering your password here ! <remoteurl>https://<account>:<password>@api.opensuse.org/</remoteurl> --> <remoteurl>https://api.opensuse.org/</remoteurl> </project> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 11 April 2008 20:43:21 wrote Martin Mohring:
Hi,
The new sample without <repository>:
$ osc -A api.d-atasoft.com meta prj -F o.o.xml openSUSE.org Sending meta data... Cannot save meta data. Unknown error. HTTP Error 500: Internal Server Error
maybe a validation error, can you run it with -H or with curl directly ? Also the frontend log file should show the problem in that case. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, I can confirm now that <remoteurl> is now working with public access, e.g. the project description from svn works (with svn trunc -r 3722): <project name="openSUSE.org"> <title>openSUSE.org Project</title> <description>This project refers to projects hosted on the Build Service at the openSUSE.org project. This is important especially for the base projects which provides the dist ributions to build against by default. Your local Build Service instance will request, download and cache all needed sources or binary packages from the openSUSE.org project when you build against it. Use openSUSE.org:openSUSE:10.3 for example to build against the openSUSE:10.3 project as specified on the opensuse.org Build Service. </description> <remoteurl>https://api.opensuse.org/public/</remoteurl> </project> You can now reference remote build targets e.g. via (in this case RHEL-5 target): <repository name="RHEL_5"> <path repository="standard" project="openSUSE.org:RedHat:RHEL-5"/> <arch>i586</arch> <arch>x86_64</arch> </repository> What seems not to work is debian targets, they result in dead jobs, e.g. <repository name="Debian_Etch"> <path repository="standard" project="openSUSE.org:Debian:Etch"/> <arch>i586</arch> <arch>x86_64</arch> </repository> even though I have put a working debian .dsc etc. in the package. For testing I used a working debian capable package (copy of openSUSE:Tools/osc). The logfile of the job shows: "No log available." Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (5)
-
Adrian Schröter -
John Calcote -
Martin Mohring -
Michael Schroeder -
Susanne Oberhauser