Skip to content

Highlight refactoring step for CI release pipeline #47

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.

Sign up for GitHub

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

Open
Antoine-Studer wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Highlight refactoring step for CI release pipeline #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/step4_further_improvements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Every suggested improvements will be followed with clue(s) to achieve it.

:star::star: Create the CI Pipeline for releases and connect it to our CD Pipeline

→ At this step, CI release pipeline could just be single or multiple jobs (for both frontend & backend) executed before CD pipeline Jobs. Spliting into two distinct workflows is further refactoring step.
→ At this step, CI release pipeline could just be single or multiple jobs (for both frontend & backend) executed before CD pipeline Jobs. **Spliting into two distinct workflows is further refactoring step**.

→ The CI release pipeline would (in parallel or sequentially) :
- For Frontend app :
Expand Down Expand Up @@ -92,4 +92,4 @@ If all workflow is trigger by a tag → it should match the following pattern

→ Solution should keep all previous features

→ Don't forget secrets and azure things ... :eyes:
→ Don't forget secrets and azure things ... :eyes: