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.

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

Jump to bottom

Improve circle-ci build and deploy pipeline #5539

Closed
Tracked by #5709
Aadesh-Baral opened this issue Jan 24, 2023 · 3 comments
Closed
Tracked by #5709

Improve circle-ci build and deploy pipeline #5539

Aadesh-Baral opened this issue Jan 24, 2023 · 3 comments
Assignees
@eternaltyro
Labels
ci/cd scope: infrastructure status: in progress status: testing Does it really work or is it pretending to work?

Comments

@Aadesh-Baral
Copy link
Contributor

I believe there are several improvements that might be done to the CircleCI build.

  1. Separate frontend and backend build jobs so that they may be easily restarted if one of them fails. Currently, if one step fails, the entire build process must be restarted.
  2. Only trigger the frontend build and deployment (staging) if a change in the frontend directory is detected. (A similar case should be made for backend build and deployment).

What are your thoughts on this? @dakotabenjamin @ramyaragupathy @eternaltyro
@Aadesh-Baral Aadesh-Baral changed the title Improve circle-ci build tests Improve circle-ci build Jan 24, 2023
@Aadesh-Baral Aadesh-Baral changed the title Improve circle-ci build Improve circle-ci build and deploy pipeline Jan 25, 2023
@eternaltyro eternaltyro added ci/cd status: testing Does it really work or is it pretending to work? labels Apr 12, 2023
@eternaltyro
Copy link
Contributor

I am currently working on this.

@eternaltyro eternaltyro self-assigned this Apr 12, 2023
This was referenced Apr 13, 2023
Open
Merged
Merged
Merged
Merged
Merged
Closed
Open
@eternaltyro
Copy link
Contributor

  1. Separate frontend and backend build jobs so that they may be easily restarted if one of them fails. Currently, if one step fails, the entire build process must be restarted.

This piece is done.

@ramyaragupathy
Copy link
Member

closing it here, partly resolved. needs a comprehensive plan that should be tracked separately

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eternaltyro eternaltyro

Labels
ci/cd scope: infrastructure status: in progress status: testing Does it really work or is it pretending to work?
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@eternaltyro @ramyaragupathy @Aadesh-Baral