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

[Deployment]Set Up Automated Deployment Pipeline for Production Environment in Todo Frontend #13

Open
6 of 10 tasks
VaibhavSingh8 opened this issue Dec 30, 2024 · 0 comments

Comments

@VaibhavSingh8
Copy link
Contributor

Issue Description

The deployment pipeline must be set up for the production environment in the Todo Frontend repository to ensure seamless deployment and testing of features before release.

Expected Behavior

When a pull request is merged into the main branch:

  1. A deployment should be triggered, deploying the latest changes to the production environment.
  2. The production environment should be accessible via the designated URL for live use.
  3. The pipeline should ensure proper build and deployment, including running any tests or lint checks.

Current Behavior

Currently:

  1. There is no automated deployment process for the main branch.
  2. The production environment is either missing.

Screenshots

N/A

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Merge a pull request into the main branch and verify that no deployment is triggered.
  2. There is no prod URL present.

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Additional Information

Checklist

  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.
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

No branches or pull requests

1 participant