chrisBrookes93 / robotframework-remoterunner

This library provides a robotframework agent, and accompanying robot executor script that allows you to run Robot Framework Test Suites remotely. It's designed to be a lightweight agent and can be used as an alternative, or with a CI Agent (e.g. Jenkins Agent).
MIT License
8 stars 8 forks source link

Migrated CI pipeline from GitLab to GitHub Actions to allow forked repos to run test pipelines #3

Closed chrisBrookes93 closed 3 years ago

chrisBrookes93 commented 3 years ago

Problem It appears the GitLab pipeline fails to run on branches/pull requests from forked repos. I've checked the hook log and its failing with HTTP 400 {"message":{"base":["Pull requests from fork are not supported"]}}

It looks as though this is a general limitation with GitLab (see https://jira.hyperledger.org/browse/IS-1497). This PR moves the CI away from GitLab to instead use GitHub Actions. This feels a lot tidier and means that this repo no longer needs to be mirrored on GitLab.

Solution Test Pipeline is now executed through GitHub Actions, triggered by a push or a pull request. This comes in the form of a GH Action Workflow and removal of the GitLab pipeline yaml file. Some improvements have also been added, namely testing against Python3.9 as well as MacOS and Windows.

Implications

Possible Future Work

adiroiban commented 3 years ago

This is how the main branch status looks in GitHub GUI and why I want short names for a workflow

image

adiroiban commented 3 years ago

Looks good. Thanks. image


It's ok to have the HTML log as artifact. You know best how to use the tool :p


It looks like your local $ git config user.email is configured with an email not register in GitHub, so GitHub things that the code was contributed by 2 different persons. This is why the merge on this PR looks like done by Chris and Chris :)