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

ci: trigger GitLab deployment pipeline when pushing #186

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

bolinocroustibat
Copy link
Contributor

@bolinocroustibat bolinocroustibat commented Oct 2, 2024

Closes datagouv/data.gouv.fr#1465.
Goes hand-to-hand with the GitLab MR.

For now, the trigger is sent only when we push on main.
We can imagine other policies?

@bolinocroustibat bolinocroustibat changed the title ci: add step to trigger GitLab ci: trigger GitLab when pushing on main Oct 2, 2024
@bolinocroustibat bolinocroustibat changed the title ci: trigger GitLab when pushing on main ci: trigger GitLab deployment when pushing on main Oct 2, 2024
@bolinocroustibat bolinocroustibat self-assigned this Oct 2, 2024
@bolinocroustibat bolinocroustibat force-pushed the auto-deploy branch 6 times, most recently from d223da7 to 3012f24 Compare October 3, 2024 08:17
@bolinocroustibat bolinocroustibat changed the title ci: trigger GitLab deployment when pushing on main ci: trigger GitLab deployment when pushing Oct 3, 2024
@bolinocroustibat bolinocroustibat marked this pull request as ready for review October 3, 2024 08:23
@bolinocroustibat bolinocroustibat force-pushed the auto-deploy branch 3 times, most recently from 88f28df to 413b54d Compare October 3, 2024 11:19
@bolinocroustibat bolinocroustibat changed the title ci: trigger GitLab deployment when pushing ci: trigger GitLab deployment pipeline when pushing Oct 3, 2024
@bolinocroustibat bolinocroustibat force-pushed the auto-deploy branch 4 times, most recently from 414f54d to 8e1a867 Compare October 3, 2024 12:11
@maudetes
Copy link
Contributor

maudetes commented Oct 3, 2024

I'd be willing to speak about the process live! I think having the job run after the publish would allow us to deploy the right pypi .dev version :)

Copy link
Contributor

@magopian magopian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks nice! Does it work? Is there any way to test it before it's merged in prod?

@bolinocroustibat
Copy link
Contributor Author

I'd be willing to speak about the process live! I think having the job run after the publish would allow us to deploy the right pypi .dev version :)

Makes sense. Just updated so that the "deploy" job runs after the "publish" job and depends on it. LMKWYT!

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.

[hydra] Deploy udata automatically on dev.data.gouv.fr when pushing on branch main of udata GitHub repo
3 participants