- Open Build Service Development

Porting OpenWRT to the Open Build Service
by Andrei-Stefan Enache 05 May '23

05 May '23

Hi, I've been recently accepted into GSoC to port OpenWRT to the Open Build Service (https://projects.freifunk.net/#/projects?project=openwrt_ppa_part_2). I am currently researching the requirements and reading through code. The current plan is to port the scripts from https://github.com/zoobab/openwrtsdkbuild and set up an SDK environment inside the build system. One issue that I am currently looking to resolve is dealing with binary dependencies (for example, binary gcc toolchain https://github.com/zoobab/openwrtsdk/blob/master/Dockerfile#L27) so that it can satisfy the security requirements described in HOWTO.add_another_format. Are binary packages provided by openwrt.org considered suitable, or do the binaries need to be run exclusively in, for example, Docker/Podman or KVM? Thank you very much, Andrei Enache

1 0

Operation x
by Michael Walker 21 Jul '22

21 Jul '22

7005 south main street apt10

1 0

[obs-devel] Change of default branch for obs-landing
by Dany Marcoux 02 Aug '18

02 Aug '18

Hi, The default branch of the repository obs-landing (https://github.com/openSUSE/obs-landing) was changed today from gh-pages to master. Since 2018-03-27, we use Netlify instead of GitHub Pages. This email is mostly a heads-up to anyone contributing and having a fork of the project, please update your default branch in your fork's settings on GitHub (Settings > Branches). Cheers -- Dany Marcoux <dmarcoux(a)suse.de> Full Stack Web Developer - Open Build Service SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: obs-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: obs-devel+owner(a)opensuse.org

1 0

[obs-devel] Test coverage with code climate
by Henne Vogelsang 25 Jun '18

25 Jun '18

Hey, we recently switched code coverage from codecov to code climate as we had serious problems with measurements of code based on push-to-master backend commits. This changes the workflow a bit. I spare you the CI setup details and concentrate on what you see: 1. Measurement on pull requests Code climate sets the status of pull-requests according to: - You are not allowed to decrease overall coverage (the codeclimate/total-coverage check) 2. Viewing code coverage To view the code coverage you have to install the code climate browser extension and navigate to the code in github. See https://docs.codeclimate.com/docs/browser-extension for details. There is no way to distinguish between the merged coverage reports (API vs. webui)... 3. Viewing code coverage trends for files Code climate has a "log" on how files improved/degraded in code coverage. See it here: https://codeclimate.com/github/openSUSE/open-build-service/progress/coverage Hope that helps to understand what has changed. Happy hacking, Henne -- Hendrik Vogelsang, Open Build Service Team SUSE LINUX GmbH, GF: Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: obs-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: obs-devel+owner(a)opensuse.org

1 0

[obs-devel] Site deploy ready: openbuildservice
by Netlify 04 May '18

04 May '18

= Site deploy ready: openbuildservice = You can see it live in https://openbuildservice.org Total build time was *1 minute* Unique deploy url: https://gh-pages--openbuildservice.netlify.com.

1 0

[obs-devel] Deploy preview ready: openbuildservice #151
by Netlify 04 May '18

04 May '18