Compare commits

..

No commits in common. "50c55f28f77174051afeb914a594851b8daeff0c" and "c9-beta" have entirely different histories.

6 changed files with 2 additions and 30 deletions

1
.cloud-utils.metadata Normal file
View File

@ -0,0 +1 @@
9db9db71d7ce634d3d2d80c377c4e1a19da0db77 SOURCES/cloud-utils-0.33.tar.gz

6
.gitignore vendored
View File

@ -1,5 +1 @@
/cloud-utils-0.27-bzr216.tar.gz SOURCES/cloud-utils-0.33.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

View File

@ -1,18 +0,0 @@
===================
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

View File

@ -1,6 +0,0 @@
--- !Policy
product_versions:
- rhel-9
decision_context: osci_compose_gate
rules:
- !PassingTestCaseRule {test_case_name: 3rd-azure-ci.brew-build.tier1.functional}

View File

@ -1 +0,0 @@
SHA512 (cloud-utils-0.33.tar.gz) = 1e58e085bde295d4adf8ff219a7f22382fadff798f5398f3e2a62cb0926c740babba76ea6326f6042b46dbdeb12c15d1e080fb9890b10482e31c3acb64014c95