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 Staging Web Pipeline #4108

Merged
merged 4 commits into from
Sep 7, 2023
Merged

Add Staging Web Pipeline #4108

merged 4 commits into from
Sep 7, 2023

Conversation

Cliftonz
Copy link
Contributor

@Cliftonz Cliftonz commented Sep 5, 2023

This Pull Request adds a new pipeline to run and update novu's staging deployment for web.

Updates the same way as dev.

# This workflow contains a single job called "build"
deploy_web:
needs: test_web
environment: Development
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't be Staging?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, because it is the same as the dev env but with production specs.

.github/workflows/staging-deploy-web.yml Outdated Show resolved Hide resolved
.github/workflows/staging-deploy-web.yml Outdated Show resolved Hide resolved
REACT_APP_SENTRY_DSN: https://[email protected]/4505829158158336
REACT_APP_ENVIRONMENT: dev
REACT_APP_MAIL_SERVER_DOMAIN: staging.inbound-mail.novu.co
REACT_APP_LAUNCH_DARKLY_CLIENT_SIDE_ID: ${{ secrets.DEV_LAUNCH_DARKLY_CLIENT_SIDE_ID }}
Copy link
Contributor

Choose a reason for hiding this comment

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

We need to add a secret called STAGING_LAUNCH_DARKLY_CLIENT_SIDE_ID.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not at this time, the system is set up with the same variables as dev.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'd recommend not to do that as Launch Darkly provides the extra environment and we won't face the situations of someone touching the Dev env FF configuration and affecting staging, that as far as I remember we meant to have the closest situation as production for load testing and reliability testing. If I missed some of the nuances of the goal of Staging and it is meant to be a replica of Dev, we can go the way you suggest it. 👍🏻

Copy link
Contributor

@p-fernandez p-fernandez left a comment

Choose a reason for hiding this comment

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

After what we discussed privately let's go with this configuration as we need to stress test the system as soon as possible.

@Cliftonz Cliftonz merged commit e741310 into next Sep 7, 2023
21 checks passed
@Cliftonz Cliftonz deleted the staging-updates branch September 7, 2023 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants