June 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] OBS junit tests support
by Antonio Cavallo 20 Jun '11

20 Jun '11

Hi, I was wondering if there's any support junit style test support during a package build. My scenario case is: * a build is performed * as part of the build xml files are emitted (junit style) * there'll be a report page for such results This is a widely used scenario on several companies. Thanks Antonio -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Importing rubygem-json to my project
by Robert Riemann 20 Jun '11

20 Jun '11

Hi all, my project (kubeplayer) needs th ruby json gem installed, which is available as rubygem-json in a foreign home repo, but not in the official repos of opensuse. How can I import this package to my repo to fullfil its dependency? Json belongs to the std libs from ruby 1.9.x on. I was really suprised, that a modern distro like opensuse still delivers ruby 1.8.x! Kind regards, Robert -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] [gsoc] osc code cleanup - summary of week 4
by Marcus Hüwe 19 Jun '11

19 Jun '11

Hi, here's a small summary of the 4th (coding) week. I spent most of the time with writing the RemoteFile classes and the BuildResult class (+ testcases of course:) ). TODO for this week: * improve RemoteFile classes * add APIInfo class: - resolve url-like parameters (api://foo/bar repo/arch) - raise an exception if required parameters are missing - initialize optional parameters with the config default - encapsulate "context-sensitivity" logic (sometimes parameters should be read from the working copy (like apiurl, project or package)) Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Solution for Tagging a version of a project and copying from an OBS with Anonymous login only
by Dominig ar Foll (Intel OTC) 18 Jun '11

18 Jun '11

Hi, I had to solve the problem of delivering software from an OBS instance to an other OBS instance in a controlled fashion. In particular I needed to provid a coherent set of the packages without being affected by possible changes which could take place between the snapshot validation and the actual time when the customer will actually do the copy. I also needed a solution which would manage time out an error with out having to restart the copy all the project at every network error. My proposed solution consists in creating a Tag for the project that I want to deliver. The Tag contains the list of all the packages as well as their revision number at the time of creation. The Tag file is created with a script called "obstag" and the tag file can be delivered to the customer by mail. With that Tag file the customer can at it's leisure (at least as long as the project is not deleted from your source OBS) collect the packages version that you wanted him to receive directly from your OBS (you need to have the public API open or give a login to the customer). To copy from a remote OBS with the obs2obscopy script, the customer will have to create of a local project which is a link to the remote OBS public API. I have tested the solution with the https://api.meego.com/public public API and it works. Limit: The public API of an OBS does not let extract the log for a packages and so obstag will create a tag file which only contains the package name when activated on a remote project via a link using a remote public API. Bug Surely but not seen yet :-) The code is available here. http://wiki.meego.com/images/ObsTagCopy.tgz -- Dominig ar Foll MeeGo TV Open Source Technology Centre Intel SSG -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] OBS 2.3 Beta 2
by Adrian Schröter 17 Jun '11

17 Jun '11

OBS 2.3 Beta 2 is out! ====================== This OBS 2.3 release is now feature complete. We changed a bit more then expected: * New source service mode handling is default now. Server side services get applied when listing in expand mode, like with source links. * Configuration UI to setup OBS instance name and description. * MeeGo.com is pre-configured now. * backend daemons have integrated runtime management * A large number of bugfixes Current State ============= Open tasks for next weeks are: * Get documentation in a better shape so that we can switch openSUSE maintenance using the new mechanisms. * There are absolute zero known regressions known atm. So really everything should be at least as good as in OBS 2.1.x :) Feel free to run it on your production system, we do it also on build.opensuse.org :) The call for help ================= There are still a number of areas where some clean up is needed. For example we have * 20 FIXME2.2 lines in the code (means that read access handling code needs checking) * 10 FIXME2.3 lines in the code (maintenance code needs a revisit here) * Unknown state of Cross architecture builds. It would be nice if someone can help so that the OBS Appliance can build for arm architectures out of the box. You can stop here when you read already Beta 1 announcement ,) OBS 2.3 main features ===================== The main features of this release are * Full distribution maintenance support. This includes support for the workflow in OBS and also the patch channel generation. This functionality can be used at full glance with coordination and review teams or just in parts. * Read access protection for projects (as planned for OBS 2.2) Apart from that we have many smaller improvements, esp. in the area of request handling and the webui integration. Download it =========== As usual, you find current packages or an appliance in openSUSE:Tools:Unstable project. OBS 2.3 Beta 2 is tagged as version 2.2.84. Please read here for usage details for the appliance: http://en.opensuse.org/openSUSE:Build_Service_Appliance Please find the full Release Notes below: ========================================= # # Open Build Service 2.3 # Please read the README.SETUP file for initial installation instructions or use the OBS Appliance from http://en.opensuse.org/Build_Service/OBS-Appliance There is also an install medium with installs OBS on hard disc now. README.UPDATERS file has informations for updaters. OBS Appliance users who have setup their LVM can just replace their appliance image without data loss. The migration will happen automatically. Main Features ============= The main topic of OBS 2.3 is to deliver a number of features to allow product maintenance handling with OBS. No external build or tracking tool is needed to do the typical maintenance workflow of a distribution team. The usage of these features are documented in the OBS book: http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/ OBS 2.3 comes also with a feature which was planned for the not released OBS 2.2 version. New created projects can set to hidden. That means no source or binary read access is possible. Please read the following for details: To be considered regarding read access checks ============================================= * "access" flag is hiding and protecting entire project. This includes binaries and sources. It can only be used at project creation time and can just be globally enabled (aka make it public again) afterwards. This flag can only be used on projects. * "sourceaccess" flag is hiding the sources to non maintainers, this includes also debug packages in case the distribution is supporting this correctly. This flag can also only be used at package creation time. There is no code yet which is checking for possible references to this package. This flag can be used on projects or packages. * "downloadbinary" permission still exists like before. However, unlike "access" and "sourceaccess" this is not a security feature. It is just a convinience feature, which makes it impossible to get the binaries via the API directly. But it still possible to get the binaries via build time in any case. Security aspects ================ Former OBS releases lack protection against XSS attacks. Esp. public instances should update to OBS 2.3, which is using rails plugins to protect against XSS attempts. This fixes (CVE-2011-0462). Building in "chroot" environments is known to be unsecure. XEN and KVM is considered to be a secure environment. However KVM is known to be unstable, it leads to build failures. Apache & mod_rails switch ========================= Former OBS versions used lighttpd as default web server. We have switched to apache with mod_rails (known as passenger) as default web server. We have also added an mod_xforward apache module to allow unloading the rails stack with long running requests to the backend. Please note that current apache2 versions have a known bug which cuts the http headers regardless to it's configuration. Please use apache2 from openSUSE:Tools project to get this fixed for now. Also the patched version of rubygem-passenger from openSUSE:Tools project is recommended. Known Regressions to 2.1: ========================= * none yet Features: ========= * web interface improvements: - package filtering - Generic authentification proxy support - delete request dialogs - request and review handling improvements - social features, i.e. show other user's projects and requests * api - review of requests by project or package maintainers is possible now (FATE #310806) - better Cross-Site Scripting (XSS) protection - larger number of request handling improvements * backend: Changes: ======== * web interface - bug reporting for projects/packages is only possible if a bugowner is set - XSS protection plugins are used now (CVE-2011-0462) * api - It was not possible so far to create submit requests from packages where no write access exists. This is possible now, but the source package maintainer will get asked for review the request. - the route /group/$GROUP is showing correct xml description and no directory anymore * new source service handling - Source services do not generate an extra commit for the result. Instead they work like source links, this means the generated files become visible with expand=1 parameter. - The state of the service is visible via serviceinfo element in package file list. * The backend is only accepting write access from the localhost by default. Build results can be still delivered from any host. This can be changed in BSConfig.pm Deprecated: =========== The following calls have been marked as deprecated, they will get removed in OBS 3.0 * api - /person/$LOGIN/group -> use /group?login=$LOGIN instead Requirements: ============= * The OBS server should not run on a system with less than 2GB memory. 4GB is recommended, esp. when the same system is also building packages. * Use osc 0.132 or later to get access to the new features. * Usage of Ruby on Rails version 2.3.11 is recommended. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] OBS scheduler downtime
by Michael Schroeder 17 Jun '11

17 Jun '11

Hey OBS users, Adrian managed to kill the schedulers, so there'll be a downtime of about two hours until we're building packages again. Sorry, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 13

[opensuse-buildservice] Re: [PATCH] [webui] minor design improvement
by Sascha Peilicke 17 Jun '11

17 Jun '11

On Friday 17 June 2011 13:57:38 you wrote: > From: Adrian Schröter <adrian(a)suse.de> > > --- > src/webui/app/views/package/_services.html.erb | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/src/webui/app/views/package/_services.html.erb > b/src/webui/app/views/package/_services.html.erb index 1aad51f..6274011 > 100644 > --- a/src/webui/app/views/package/_services.html.erb > +++ b/src/webui/app/views/package/_services.html.erb > @@ -34,7 +34,7 @@ >  > <% if @serviceerror %> > <div id="error" class="error"> > - <h4> > + <br/><h4> > Source processing is currently broken: > </h4> > <pre id="code" class="text"> This looks like the <div> could've become a <p> to achieve the same? We really need to re-freshen our Bento theme... -- Mit freundlichen Grüßen, Sascha Peilicke SUSE Linux Products GmbH

1 0

[opensuse-buildservice] Search bar annoyance
by Cristian Rodríguez 17 Jun '11

17 Jun '11

Hi: In the webUI, there is a search bar next to the "watchlist", it would be great if it strips leading and trailing whitespaces " home:iexists" , "home:iexists " return no results even if those repos exist. Cheers. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] [PATCH] Add config entry to allow permanent usage of ccache
by Cristian Rodríguez 17 Jun '11

17 Jun '11

Signed-off-by: Cristian Rodríguez <crrodriguez(a)opensuse.org> --- osc/build.py | 2 +- osc/conf.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/osc/build.py b/osc/build.py index c85be15..54dc6d2 100644 --- a/osc/build.py +++ b/osc/build.py @@ -399,7 +399,7 @@ def main(apiurl, opts, argv): buildargs.append('--icecream=%s' % num) xp.append('icecream') xp.append('gcc-c++') - if opts.ccache: + if opts.ccache or config['ccache'] != '0': buildargs.append('--ccache') xp.append('ccache') if opts.linksources: diff --git a/osc/conf.py b/osc/conf.py index 9494906..8c359a7 100644 --- a/osc/conf.py +++ b/osc/conf.py @@ -91,7 +91,7 @@ DEFAULTS = { 'apiurl': 'https://api.opensuse.org', 'build-jobs': _get_processors(), 'builtin_signature_check': '1', # by default use builtin check for verify pkgs 'icecream': '0', - + 'ccache': '0', 'debug': '0', 'http_debug': '0', 'http_full_debug': '0', -- 1.7.4.1 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Accepteted request results in empty package
by Johannes Weberhofer 16 Jun '11

16 Jun '11

Dear all, the request https://build.opensuse.org/request/show/73634 has been accepted but the resulting package is empty. How can the problem be solved? Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5