upload-rpms-action's Introduction

GitHub Action: Upload RPMs the oVirt way

This simple action takes a directory, creates an RPM repository and uploads the resulting RPM repository as a build artifact in a standardized way.

This is intended for oVirt projects to use as a standard way to archive built RPMs.

Usage:

name: Self-test
on:
  push:
  pull_request:
jobs:
  selftest:
    name: Self-test
    runs-on: ubuntu-latest
    container: quay.io/ovirt/buildcontainer:el8stream
    steps:
    - name: Upload artifacts
      uses: ovirt/upload-rpms-action@main
      with:
        directory: test-artifacts

upload-rpms-action's People

Contributors

Stargazers

Watchers

upload-rpms-action's Issues

mixed el8 and el9 repo

Using the action on both el8 and el9 builds ends up generating a single artifacts with both el8 and el9 packages.
example from ovirt-release job:

unzip -t ../artifacts.zip 
Archive:  ../artifacts.zip
    testing: ovirt-node-ng-image-update-placeholder-4.5.0-0.0.master.20220117170638.git84521b4.el8.20220117170638.git84521b4.el8.20220117170638.git84521b4.el8.noarch.rpm   OK
    testing: ovirt-node-ng-image-update-placeholder-4.5.0-0.0.master.20220117170734.git84521b4.el9.20220117170734.git84521b4.el9.20220117170734.git84521b4.el9.noarch.rpm   OK
    testing: ovirt-release-host-node-4.5.0-0.0.master.20220117170638.git84521b4.el8.20220117170638.git84521b4.el8.noarch.rpm   OK
    testing: ovirt-release-host-node-4.5.0-0.0.master.20220117170734.git84521b4.el9.20220117170734.git84521b4.el9.noarch.rpm   OK
    testing: ovirt-release-master-4.5.0-0.0.master.20220117170638.git84521b4.el8.noarch.rpm   OK
    testing: ovirt-release-master-4.5.0-0.0.master.20220117170638.git84521b4.el8.src.rpm   OK
    testing: ovirt-release-master-4.5.0-0.0.master.20220117170734.git84521b4.el9.noarch.rpm   OK
    testing: ovirt-release-master-4.5.0-0.0.master.20220117170734.git84521b4.el9.src.rpm   OK
    testing: ovirt-release-master-4.5.0_master.tar.gz   OK
    testing: repodata/                OK
    testing: repodata/11c503a18a1ed5a97cfa80f01c8681112e9e393e2d28b59ad16544387b1db12c-primary.xml.gz   OK
    testing: repodata/3ebaf66261389c83682ebac85f8a4f29deaa7bc3dbfd812ba21b74cac209c95e-other.xml.gz   OK
    testing: repodata/3fefe7fabb8068a7d9a5d4e8df403c3b4c00808cb8b5050e44131ad6faa46d42-primary.sqlite.bz2   OK
    testing: repodata/489c87b1fcae9485fb713b13fda603a50ff6d9795acd64a2629f372796ab2558-primary.sqlite.bz2   OK
    testing: repodata/95f86c0c8d65ebdf440d4f288eebe56f2b422c11da4e628b0b6f921640cfa328-filelists.sqlite.bz2   OK
    testing: repodata/9b8ca954333dd035160100c804a8dbbed9a7bcaddc5300557dcee864d62e6b65-other.sqlite.bz2   OK
    testing: repodata/a03929317ac9e9b2c51e4bb7c22d982d7f912a1002d31de662fcca13cadf3788-filelists.sqlite.bz2   OK
    testing: repodata/aa42f9dbe1745153fb987c419545e2c13ffe007584b5e0323a4365ada01b04ab-other.xml.gz   OK
    testing: repodata/acbd9cae3475b5bd8ddbfce36a231f88976080fba3ffa669e04592031c97b749-other.sqlite.bz2   OK
    testing: repodata/b8e362190a6066e7e0bd2c67d36bb7713a51ba5384c1f2be8e02a7669bd2bd27-primary.xml.gz   OK
    testing: repodata/e008d216515e804dcaadb8912015916ab8c2b9fa3d9a39c9563b0f36d0ddb515-filelists.xml.gz   OK
    testing: repodata/ef24f7c5fa874a489f731fb36c0f6fa3db4be0602298da9dfd76ffcd323e8f54-filelists.xml.gz   OK
    testing: repodata/repomd.xml      OK

I would expect el8 packages within a el8 sub directory with its own repodata and el9 packages within a el9 subdirectory with its own repodata.

Recommend Projects