Generic Workflow to build component packages

[shailesh-vaidya]

We should use generic workflow to build component rpm's . I have created one for Provisioner at provisioner-build.yml . It will also need changes in Dockerfile's .

jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
    # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
    - uses: actions/checkout@v2
    
    - name: Checkout
      uses: actions/checkout@v2
      with:
        # Repository name with owner. For example, actions/checkout
        repository: Seagate/cortx-prvsnr
        token: ${{ secrets.TOKEN }}
        path: provisioner

    # Runs a set of commands using the runners shell
    - name: Build Provisioner packages
      run: |
        echo "${{ secrets.GITHUB_TOKEN }}" | docker login docker.pkg.github.com -u ${{ github.actor }} --password-stdin
        docker pull docker.pkg.github.com/seagate/cortx-re/cortx_centos:7.7.1908
        docker run -i -v $PWD:/build docker.pkg.github.com/seagate/cortx-re/cortx_centos:7.7.1908 'sh /build/build_scripts/build_provisoiner.sh'
       
    - name: Upload files to a GitHub release
      uses: svenstaro/upload-release-action@2.0.0
      with:
        repo_token: ${{ secrets.TOKEN }}
        release_name: provisioner
        file: provisioner/release/*.rpm
        tag: 1.0.0
        file_glob: true
        body: "Provisioner Release"

There are some better actions available to upload artifacts to GitHub releases. We can try out them. Do review and provide suggestions.

[stale]

This issue/pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gauravchaudhari02]

@shailesh-vaidya Which better action you are talking for upload a release. Could you give a reference here?

[gauravchaudhari02]

@shailesh-vaidya Working Generic Workflow for RPM build. Please have a look

jobs:
  build:
    runs-on: ubuntu-latest
    env:
       GITHUB_TOKEN: ${{secrets.ACCESS_TOKEN}}
       TAG: 7.7.1908
    steps:
    - name: Checkout ${{ github.event.repository.name }}
      uses: actions/checkout@v2
      with: 
        token: ${{ env.GITHUB_TOKEN }} 
        submodules: 'recursive'
    - name: GitHub registry login
      run: docker login docker.pkg.github.com -u ${{ github.actor }} -p ${{ env.GITHUB_TOKEN }}
    - name: Build ${{ github.event.repository.name }} RPM
      run: |
        docker run -i -e build_number=${GITHUB_RUN_NUMBER} -v $GITHUB_WORKSPACE:/workspace -w /workspace docker.pkg.github.com/${{ github.repository }}/${{ github.event.repository.name }}:${{ env.TAG }} 'sh <Path to RPM building shell script>'
    - name: Create ${{ github.event.repository.name }} release
      uses: softprops/action-gh-release@v1
      with:
       tag_name: "1.0.0-${{ github.run_number }}"
       files: '${{ github.event.repository.name }}*.rpm'
      env:
       GITHUB_TOKEN: ${{ env.GITHUB_TOKEN }}

[shailesh-vaidya]

@gauravchaudhari02 Workflow looks good to me.
@mukul-seagate11 Lets follow above workflow for all the components . Let me know if any review comments.

[mukul-seagate11]

@shailesh-vaidya, looks good
Just one point here as base image will always be ubuntu-latest or there are other images available too

[hessio]

@shailesh-vaidya can you provide an update on this issue?

[shailesh-vaidya]

Hi @hessio - We can close this issue for now. This was created as part of one of the tasks to track Jenkins -> GitHub Actions migration.

[hessio]

ok thanks :)