GitHub Action - RPM Build

This GitHub Action builds RPMs from spec file and using repository contents as source (wraps the rpmbuild utility). Integrates easily with GitHub actions to allow RPMS to be uploaded as Artifact (actions/upload-artifact) or as Release Asset (actions/upload-release-asset).

Usage

Pre-requisites

Create a workflow .yml file in your repositories .github/workflows directory. An example workflow is available below. For more information, reference the GitHub Help Documentation for Creating a workflow file.

Note: You need to have a spec file in order to build RPM.

Inputs

• sources: Repo relative path to build directory containing your build artifacts (tar.gz files and systemd .service files) [required]
• spec_file: The path to the spec file in your repo. [required]
• supplement_sources: A list of additional files to incorporate into the rpm sources directory

Outputs

• rpm_dir_path: path to RPMS directory
• binary_rpm_path: path to Source RPM file
• binary_rpm_dir_path: path to SRPMS directory
• binary_rpm_name: name of Source RPM file
• rpm_content_type: Content-type for RPM Upload

This generated RPMS can be used in two ways.

1. Upload as build artifact You can use GitHub Action @actions/upload-artifact
2. Upload as Release assest If you want to upload as release asset ,You also will need to have a release to upload your asset to, which could be created programmatically by @actions/create-release as show in the example workflow.

Example workflow - build RPM

Basic:

name: RPM Build
on: push

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2

    - name: build RPM package
      id: rpm
      uses: geonet/naveenrajm7-rpmbuild-action@el8
      with:
        sources: dist/
        spec_file: "cello.spec"

    - name: Upload artifact
      uses: actions/[email protected]
      with:
        name: Binary RPM
        path: ${{ steps.rpm.outputs.rpm_dir_path }}

This workflow triggered on every push , builds RPM and Source RPM using cello.spec and contents of that git ref that triggered that action. Contents are retrived through GitHub API [downloaded through archive link]. The generated RPMs or SRPMS can be uploaded as artifacts by using actions/upload-artifact. The outputs given by rpmbuild action can be used to specify path for upload action.

Above workflow will create an artifact like

Use with Release:

on:
    push:
      # Sequence of patterns matched against refs/tags
      tags:
        - 'v*' # Push events to matching v*, i.e. v1.0, v20.15.10

name: Create RPM Release

jobs:
    build:
        name: Create RPM Release
        runs-on: ubuntu-latest

        steps:

        - name: Checkout code
          uses: actions/checkout@master

        - name: Create Release
          id: create_release
          uses: actions/create-release@latest
          env:
              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # This token is provided by Actions, you do not need to create your own token
          with:
              tag_name: ${{ github.ref }}
              release_name: Release ${{ github.ref }}
              body: |
                Changes in this Release
                - Create RPM
                - Upload Binary RPM
              draft: false
              prerelease: false

        - name: build RPM package
          id: rpm_build
          uses: geonet/naveenrajm7-rpmbuild-action@el8
          with:
            sources: dist/
            spec_file: "cello.spec"
        - name: Upload Release Asset
          id: upload-release-asset
          uses: actions/upload-release-asset@v1
          env:
              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          with:
              upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
              asset_path: ${{ steps.rpm_build.outputs.binary_rpm_path }}
              asset_name: ${{ steps.rpm_build.outputs.binary_rpm_name }}
              asset_content_type: ${{ steps.rpm_build.outputs.rpm_content_type }}

Note on distribution: If your RPMs are distribution specific like el7 or el8.

• Use geonet/docker-rpmbuild@stream8 for el8 [el8]

- name: build RPM package
    id: rpm_build
    uses: geonet/naveenrajm7-rpmbuild-action@el8
    with:
        sources: dist/
        spec_file: "cello.spec"

Contribute

Feel free to contribute to this project. Read CONTRIBUTING Guide for more details.

References

• RPM Packaging Guide
• GitHub Learning Lab
• Container Toolkit Action

Influences

• https://github.com/ublue-os/rpmbuild
• https://github.com/naveenrajm7/rpmbuild

License

The scripts and documentation in this project are released under the GNU GPLv3