Skip to content
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

Add CD job for deployment through gitlab #52

Merged
merged 4 commits into from
Mar 3, 2022

Conversation

GabrieleCalarota
Copy link
Contributor

Related to #50
Fixes #22

@GabrieleCalarota
Copy link
Contributor Author

@DomiiBunn I've submitted this

@DomiiBunn
Copy link
Collaborator

And we're sure it will just run deploy only on master?

@DomiiBunn DomiiBunn mentioned this pull request Mar 3, 2022
@DomiiBunn
Copy link
Collaborator

Sorry i just noticed
if: github.event_name == 'push' && github.ref == 'refs/heads/main'

@DomiiBunn DomiiBunn merged commit 1ae579c into kinshukdua:main Mar 3, 2022
@DomiiBunn
Copy link
Collaborator

So I don't see an error and it certainly didn't trigger the gitlab CI
https://github.com/kinshukdua/LiveActionMap/runs/5413715608?check_suite_focus=true
These ware triggered by hand sadly
image

@DomiiBunn DomiiBunn mentioned this pull request Mar 3, 2022
@GabrieleCalarota
Copy link
Contributor Author

These are the logs of the github actions:

image

@GabrieleCalarota
Copy link
Contributor Author

So the github actions and triggers are working fine, at the right moment

@DomiiBunn
Copy link
Collaborator

All i know is that using curl it triggers gitlabs ci with no issue and i don't understand anything from the log

@edubacco
Copy link
Contributor

edubacco commented Mar 7, 2022

Have you tried adding debug: true input variable to the action configuration to see if it logs something useful?

If you have a working curl call, probably it's easier to just use that command instead of using an external action (remember to use github secrets)

@DomiiBunn
Copy link
Collaborator

Can I ask you really nicely if you could pr a change to use curl? I'm really green if it comes to GitHub ci

curl --request POST "https://gitlab.example.com/api/v4/projects/34155787/trigger/pipeline?token=<token>&ref=main"

The token env is GITLAB_TOKEN

I hope it will be hidden in the ci it's self

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add CI/CD and Tests
3 participants