Compare commits
No commits in common. "c9-beta" and "c9s" have entirely different histories.
|
@ -1 +0,0 @@
|
|||
9db9db71d7ce634d3d2d80c377c4e1a19da0db77 SOURCES/cloud-utils-0.33.tar.gz
|
|
@ -1 +1,5 @@
|
|||
SOURCES/cloud-utils-0.33.tar.gz
|
||||
/cloud-utils-0.27-bzr216.tar.gz
|
||||
/cloud-utils-0.27.tar.gz
|
||||
/cloud-utils-0.30.tar.gz
|
||||
/cloud-utils-0.31.tar.gz
|
||||
/cloud-utils-0.33.tar.gz
|
||||
|
|
|
@ -0,0 +1,18 @@
|
|||
===================
|
||||
cloud-utils development
|
||||
===================
|
||||
|
||||
cloud-utils is maintained in a `source tree`_ rather than directly in dist-git
|
||||
using packit service that provides way to develope using regular source code
|
||||
structure and provides way to generate SRPM and build using koji service.
|
||||
|
||||
Developers deliver all changes to source-git using merge request. Only maintainers
|
||||
will be pushing changes sent to source-git to dist-git.
|
||||
|
||||
Each release in dist-git is tagged in the source repository so you can easily
|
||||
check out the source tree for a build. The tags are in the format
|
||||
name-version-release, but note release doesn't contain the dist tag since the
|
||||
source can be built in different build roots (Fedora, CentOS, etc.)
|
||||
|
||||
.. _source tree: https://gitlab.com/redhat/centos-stream/src/cloud-utils
|
||||
|
|
@ -0,0 +1,6 @@
|
|||
--- !Policy
|
||||
product_versions:
|
||||
- rhel-9
|
||||
decision_context: osci_compose_gate
|
||||
rules:
|
||||
- !PassingTestCaseRule {test_case_name: 3rd-azure-ci.brew-build.tier1.functional}
|
Loading…
Reference in New Issue