Project

General

Profile

Actions

action #93838

closed

Use new OBS SCM integration to trigger OBS checks on pull/merge requests for our projects

Added by okurz almost 3 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2021-06-10
Due date:
% Done:

0%

Estimated time:

Description

Observation

https://openbuildservice.org/2021/05/31/scm-integration/ presents a new feature in OBS that OBS can trigger builds and feed back the result into pull/merge requests of github/gitlab. We already use a solution in os-autoinst in openQA that is rather "custom", relies on components on personal machines and are hard or impossible for us to debug if something goes wrong hence we should try out and use that new approach in one/most/all of our projects that have corresponding packages on OBS

Acceptance criteria

  • AC1: All projects that we care about that live in github/gitlab and have corresponding packages built on OBS use the OBS scm integration or clear explanation is given for each project why that is not applicable

Suggestions

  • Try with one project, maybe github.com/os-autoinst/openqa_review ?
  • Extend to os-autoinst and openQA
  • Look for more projects where we might want that

Related issues 1 (0 open1 closed)

Related to openQA Project - action #95164: OBS Package build in github fails to provide updates, "OBS Package Build Expected — Waiting for status to be reported" size:MResolvedokurz2021-07-072021-07-14

Actions
Actions #1

Updated by okurz almost 3 years ago

  • Related to action #95164: OBS Package build in github fails to provide updates, "OBS Package Build Expected — Waiting for status to be reported" size:M added
Actions #2

Updated by tinita almost 3 years ago

I think this ticket is too big and should be split into a Proof of Concept, where we try out the OBS feature for one of our projects (like mentioned in the suggestions), learn how it works, see if it works (fits our needs).

Actions #3

Updated by okurz over 1 year ago

  • Status changed from Workable to Resolved
  • Assignee set to okurz
  • Target version changed from future to Ready

Considering https://github.com/os-autoinst/os-autoinst/blob/master/.obs/workflows.yml and the corresponding definitions for openQA I think we are good. Maybe we have some minor stuff missing but adjusting on the fly whenever an old way does not work anymore should be feasible.

Actions

Also available in: Atom PDF