Repository navigation
CI/CD Pipeline #493
Description
Activity
- changed the title
[-][SPIKE] Research approaches to CI/CD pipeline[/-][+][SPIKE] CI/CD pipeline[/+]on Jun 5, 2023 - added this to the milestone
on Jul 2, 2023 Hey, @Andrewgl22 @angeldzzz23! I'll be setting up a meeting for us to go through any of your findings and choose a path forward. Nothing needs to be perfect or final. :)
@glenflorendo Yeah sounds good.
Great thanks Glen. Have been digging through the repo but still having some trouble understanding how everything is set up.
@angeldzzz23 @Andrewgl22 Any updates on your progress on this ticket? Any blockers?
@angeldzzz23 @Andrewgl22 Hello, we haven't had progress on this for a while now, so I will reassign this. Please let us know when you are available, and we can reallocate work to you. Thank you!
Hi I have been working on this ticket and would like to keep working on it if possible. I am in the midst of testing a system using CDK with Docker and Elastic Beanstalk to create the pipeline.
6 remaining items
@Andrewgl22 We haven't received any progress updates on this ticket in a while. The leads will be re-assessing this ticket, so you'll be unassigned for now. Thanks!
Cc: @glenflorendo
Reacted by Glen Paul Florendo@dannycpham @glenflorendo Ok. I'm sorry I have not been giving updates. You are right to unassign me. I have a nearly finished pipeline I would be happy to push if someone else wants to complete it.
- added a parent issue
on Sep 5, 2025 - added a sub-issue
on Sep 5, 2025
User Story
As a developer, I want a continuous integration/continuous deployment (CD/CD) pipeline, so that I can deliver code changes more frequently and reliably.
Description
GitHub and AWS will be our main technology stack for CI/CD (unless you know better ones).
POSSIBLE APPROACH
Ideally, we will have (at the very least) a staging environment and a production environment.
We have two permanent branches (
mainandstable). Each of these branches should be deployed to a specific environment (staging and production, respectively).We should have domains set up for our staging and production environments:
We can possible use AWS Amplify to implement the CD part.
A bonus if we can have temporary feature environments where each branch in this repository will be automatically deployed to.
The CI part will not have much, as we do not have testing suites implemented, but the pipeline should be extensible so we can quickly add that (and other things) in later.
Note that we work in a monorepo code structure, so our approach needs to be able to handle that.
We should have legacy infrastructure someone, so that could serve as a basis for our implementation.
Acceptance Criteria
Design References
No response
Technical References
No response
Additional Information
No response