Move from drone to Github Actions

[mitulshah-suse]

Move from drone to GHA.

• removed the existing drone.yml
• added new github workflow

ref: SURE-7991

[jiaqiluo]

The PR looks good to me overall, and I have one request for changes:
could you add the permissions to each job? AFAIK, all jobs need the permission contents: read to prevent privilege escalation, and the job that reads the credential needs the permission id-token: write (see example here).

[mitulshah-suse]

@jiaqiluo Thanks for pointing that out. Have updated permissions for the jobs.
Also realised that GHA runs jobs in parallel by default instead of sequentially like drone. So added needs to the jobs to create dependency and run them sequentially. Had to merge a couple of jobs as well, since there is no gaurantee of everything executing on the same runner as well, so changes in 1 job would not necessarily reflect in the next.
Added a timeout for each of the jobs as well, since the default is 360 mins which is too long.

Also, do you know if we need to use the containerized runners specified by EIO?
ex: runs-on: org-${{ github.repository_owner_id }}-{{ arch }}-k8s or we can continue using the github provided ones like ubuntu-latest

[jiaqiluo]

Also, do you know if we need to use the containerized runners specified by EIO?
ex: runs-on: org-${{ github.repository_owner_id }}-{{ arch }}-k8s or we can continue using the github provided ones like ubuntu-latest

Hi @mitulshah-suse, you continue using the GitHub provided ones.

[HarrisonWAffel]

I'm generally a fan of creating multiple workflow files for different actions. For example, one for PRs, another for merges and one for tagging. IMO that pattern is easier to read and maintain, gets rid of skipped checks in the github UI when raising PRs, and allows us to avoid the use of if statements depending on what action is invoking the workflow. Adding conditionals like this can make it harder to determine what should and shouldn't execute given a particular on statement.

I don't work with this repo often, so I won't hold up this PR based off this, but it's something that should be considered.