Skip to content

Trigger GitLab CI automatically #513

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 15, 2021
Merged

Trigger GitLab CI automatically #513

merged 1 commit into from
Feb 15, 2021

Conversation

mcserep
Copy link
Collaborator

@mcserep mcserep commented Feb 14, 2021

Currently the tarball building and publishing pipeline must be manually triggered in GitLab CI.
With this PR the pipeline is automatically triggered for the master branch if the tests in GitHub Action succeeded.

Manual triggering remains still possible.

@mcserep mcserep added Kind: Enhancement 🌟 Target: Developer environment Developer environment issues consist of CodeCompass or 3rd-party build tooling, configuration or CI. labels Feb 14, 2021
@mcserep mcserep added this to the Future milestone Feb 14, 2021
@mcserep mcserep requested a review from intjftw February 14, 2021 14:28
@intjftw intjftw merged commit e3f32a6 into master Feb 15, 2021
@mcserep mcserep deleted the ci branch February 15, 2021 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Kind: Enhancement 🌟 Target: Developer environment Developer environment issues consist of CodeCompass or 3rd-party build tooling, configuration or CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants