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] Deploy new version on production using gitlab CI #8689

Open
novicecpp opened this issue Sep 4, 2024 · 0 comments
Open

[CI] Deploy new version on production using gitlab CI #8689

novicecpp opened this issue Sep 4, 2024 · 0 comments
Assignees

Comments

@novicecpp
Copy link
Contributor

One of our CI wishlist, second checkbox #7958

It still use tag-and-push pattern, or trigger through WebUI, which does not have a beautiful interface like Jenkins, but might be more convenient.

The pipeline would have 3 stages: deploy -> runtest -> checktest, to make sure the newly deployed services are running properly.

To deploy on prod, you need 2 variables:

  • DEPLOY_PROD, value is container tag you want to deploy.
  • DEPLOY_SERVICE, value is all or service name (REST/TaskWorker/Publisher_schedd/Publisher_rucio)

The main blocker (or not?) is to negotiate with Aroosha, to allow us to deploy REST from CI, like we do on testbed, on production backend cluster. I am not sure if she has any security concern about this.

@novicecpp novicecpp self-assigned this Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant