- May 29, 2021
-
-
Lukas Krause authored
We were using the head (source) repository instead of the base (target) repository to report back the build state of a workflow. This is wrong since the state is reported using the scm token of the target repo owner/maintainer, which leads to permission problems (since it doesn't associate the reported state to the PR, but directly to the commit on the source repository). We also changed the download url, we should only take the "workflow.yml" file from the target repository. Co-authored-by:
Saray Cabrera Padrón <scabrerapadron@suse.de>
-
- May 28, 2021
-
-
Dani Donisa authored
Create job to report build status to SCM via SCMStatusReporter
-
Lukas Krause authored
Ignore signer related backend exceptions
-
Henne Vogelsang authored
[api] fix releaseing multibuild container
-
Victor Pereira authored
-
- May 27, 2021
-
-
Henne Vogelsang authored
-
Henne Vogelsang authored
-
Henne Vogelsang authored
Co-authored-by:
Dani Donisa <dani.doni@gmail.com>
-
Adrian Schröter authored
set_multibuild_flavor is now setting only the multibuild container as the method name implies. Doing so no matter if the package comes via a link or not, since it does not matter for container name. do not abort due to wrong guessed flavors because the wrong source state might be read. options[:package] can not be a string for releasing as it would crash when trying to lookup the release name, so having a seperate string for container name. (and to avoid the logic that it is a multibuild, if it is not a package object) simplify authorization object code
-
Lukas Krause authored
Token.:Workflow model specs
-
Michael Schroeder authored
[backend] support a block=0 option in /lastevents
-
Saray Cabrera Padrón authored
Co-authored-by:
Lukas Krause <lkrause@suse.de>
-
Saray Cabrera Padrón authored
-
Saray Cabrera Padrón authored
-
Saray Cabrera Padrón authored
Also add scm_token to the token workflow factory.
-
Saray Cabrera Padrón authored
-
Lukas Krause authored
Create Workflow::Step::BranchPackageStep model
-
Michael Schroeder authored
-
Michael Schroeder authored
[backend] support DoD container registries
-
Michael Schroeder authored
Those DoD resources are different to repositories because there is no way to request the complete state from the server. Thus we collect the needed DoD resources in the scheduler and put them into a "doddata.needed" file. The bs_dodup server then uses this information to request data for each resource.
-
Michael Schroeder authored
-
Michael Schroeder authored
- check the blobstore before downloading a blob - put downloaded blobs in the blobstore - try to get the container mtime from the config so that we always reconstruct bitwise identical containers - add correct provides to the obsbinlnk file
-
Lukas Krause authored
Remove package id from event table
-
Lukas Krause authored
The error messages are not used anywhere, therefore no need to add them for now.
-
Lukas Krause authored
Co-authored-by:
Daniel Donisa <daniel.donisa@suse.com> Co-authored-by:
Saray Cabrera Padrón <scabrerapadron@suse.de>
-
Lukas Krause authored
Co-authored-by:
Daniel Donisa <daniel.donisa@suse.com> Co-authored-by:
Eduardo Navarro <enavarro@suse.com> Co-authored-by:
Saray Cabrera Padrón <scabrerapadron@suse.de>
-
- May 26, 2021
-
-
Lukas Krause authored
After changing the from the attempt of building an association between an event and a package, to fetching the package using the passed payload in the `ReportToScmJob` in https://github.com/openSUSE/open-build-service/pull/11124 the package_id is not longer needed.
-
Lukas Krause authored
Preperation for the db migration in order to remove the package_id column from the events table. See https://github.com/ankane/strong_migrations#removing-a-column
-
- May 25, 2021
-
-
Lukas Krause authored
Hide scm channel from subscription configuration page
-
Henne Vogelsang authored
Those are content problems, developers can't do anything about them.
-
Lukas Krause authored
The test needs to take into account the hidden channels
-
Lukas Krause authored
The scm channel in the event system is not meant to be set by hand, its only used internally to report the state of a workflow (at least for now). Therefore we should not allow to set it by hand (since it doesnt bring any value).
-
Dany Marcoux authored
Create TriggerWorkflowController
-
depfu[bot] authored
-
Dany Marcoux authored
Refine validations related to SCM webhooks in trigger controller
-
Dany Marcoux authored
Add systemd service for scm delayed job queue
-
depfu[bot] authored
-
Dany Marcoux authored
[src/api] Update puma: 5.3.1 → 5.3.2 (patch)
-
Dany Marcoux authored
[src/api] Update ffi: 1.15.0 → 1.15.1 (patch)
-
- May 24, 2021
-
-
Lukas Krause authored
Skip validation of params only if request comes from and supported SCM Co-authored-by:
Daniel Donisa <daniel.donisa@suse.com> Co-authored-by:
Dany Marcoux <dmarcoux@suse.com> Co-authored-by:
Eduardo Navarro <enavarro@suse.com> Co-authored-by:
Saray Cabrera Padrón <scabrerapadron@suse.de>
-