search

QEDjl-project / QEDprocesses.jl

[WIP]: QEDprocesses.jl: Modeling of scattering processes for QED.jl
MIT License
1 stars 3 forks source link

add initial .gitlab-ci.yaml #2

Closed SimeonEhrig closed 10 months ago

SimeonEhrig commented 1 year ago

Add also a GitHub Action to accelerate the start of the GitLab CI. We use the official GitHub mirror to Gitlab CI feature of gitlab.com.

This feature works quit well, but it has a big disadvantage. gitlab.com is looking from time to time, if something changed in your GitHub repository and if yes, it triggers the mirror process. The check interval depends on the server utilization of gitlab.com. Therefore a CI start can vary from a few seconds until some minutes.

We solved the problem, with a GitHub Action jobs. The job starts directly after pushing a commit or open a pull request and simply push the changes to gitlab.com. This triggers the CI and gitlab creates the CI link in the pull request. With the GitHub action the CI startup time is constant about some seconds.

A positive side effect is also, that we have a GitHub Action job, which represent the GitLab CI. With this job, we can also configure a execution order between GitHub Action jobs and GitLab CI.

SimeonEhrig commented 1 year ago

@szabo137 Do you know, why the GitHub Action is not started?

SimeonEhrig commented 10 months ago

GitHub Action does not work to test forks in GitLab CI