Project

General

Profile

Actions

action #55346

closed

packaging test as part of every PR

Added by okurz over 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2019-08-11
Due date:
% Done:

0%

Estimated time:


Related issues 2 (1 open1 closed)

Related to openQA Project (public) - action #43619: Improve workflow for dealing with openQA's dependenciesResolvedtinita2018-11-09

Actions
Related to openQA Project (public) - action #53546: Easier dependencies handling for packages, e.g. reduce duplication of build requirements in spec, documentation, DockerfileNew2019-06-27

Actions
Actions #1

Updated by coolo over 5 years ago

  • Assignee set to coolo
Actions #2

Updated by coolo about 5 years ago

  • Status changed from New to Feedback
  • Target version set to Current Sprint

I put this in place - let's see how fast we remove it again as it's taking too long :)

Actions #3

Updated by coolo about 5 years ago

  • Status changed from Feedback to Resolved

Seems to work fine

Actions #4

Updated by okurz about 5 years ago

Could you please share a bit of details what you have done so that we can learn from it for the potential application on other projects as well as know how to handle it in case of your unavailability?

Actions #5

Updated by okurz about 5 years ago

  • Related to action #43619: Improve workflow for dealing with openQA's dependencies added
Actions #6

Updated by okurz about 5 years ago

  • Related to action #53546: Easier dependencies handling for packages, e.g. reduce duplication of build requirements in spec, documentation, Dockerfile added
Actions #7

Updated by coolo about 5 years ago

Git clone https://github.com/coolo/pull_request_package/tree/for_openqa
docker build -t puller_for_openqa .
Create puller-config

Run /usr/bin/docker run --rm -v=/suse/coolo/prod/openQA/puller-config:/config -t puller_for_openqa:latest from systemd timer

Actions #8

Updated by okurz about 5 years ago

cool. Do you agree that we should do the same for os-autoinst? … and for every other package of openSUSE:Factory linked to spec file sources on github? Should we run it on botmaster or maybe a k8s cluster?

Actions #9

Updated by okurz over 4 years ago

This solution stopped working in 2020 after the account used was migrated to IDP. 2020-07-10: coolo moved it to a different account on botmaster.suse.de now. VM is maintained by autobuild.

Actions

Also available in: Atom PDF