Answers: <p>I would suggest adding a job that checks changes in the latest commit and build only that service where some files have been changed.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-05-05T23:49:51.073Z
Answers: can you post a code snippet ?
Answers: nab
Answers: CC BY-SA 4.0
Answers: 2020-04-28T06:35:52.203Z
Answers: 2020-04-28T06:35:52.203Z
Answers: Prokop Simek
Body: <p>I have a nodejs application using expressjs. This server is handing a website built on vuejs, an application using angular and another angular app. Everything is working and I deployed to AWS eb using a pipeline. The problem is when a website change is made I build it and commit the change to AWS code commit.</p>
  
  <p>Is there a way to make this automatic?</p>
  
  <p>Should I keep all projects in the same repo?</p>
  
  <p>What I want is: website change -> commit -> build website only -> push to AWS.</p>
  
  <p>The only solution I can think of is to rebuild the 3 projects every time.</p>
  
Comments: CC BY-SA 4.0
Comments: 2020-04-29T00:35:05.117Z
Comments: See if this helps: https://medium.com/@taleodor/using-monorepo-do-not-rebuild-unchanged-components-in-ci-c386e7c03426
Comments: taleodor
Comments: CC BY-SA 4.0
Comments: 2020-05-05T23:50:15.267Z
Comments: @taleodor i don't use docker
Comments: nab
Comments: CC BY-SA 4.0
Comments: 2020-05-05T23:57:48.887Z
Comments: Hm, why would it matter? Docker is absolutely not required there. The idea is that you need to check your directories for changes against previous state.
Comments: taleodor
Comments: CC BY-SA 4.0
Comments: 2020-05-28T08:14:58.287Z
Comments: "Is there a way to make this automatic?" Not quite sure what part isn't automatic yet. You mean the actual build & deploy steps aren't automatic?
Comments: Andrei Mustață
Tags: <continuous-integration><git><continuous-deployment><continuous-delivery><aws-codepipeline>
Title: Continuous deployment
UserDisplayName: nab
ThreadText: # Continuous deployment
  
  (Asked by: username_0 on 2020-04-27)
  
  I have a nodejs application using expressjs. This server is handing a website built on vuejs, an application using angular and another angular app. Everything is working and I deployed to AWS eb using a pipeline. The problem is when a website change is made I build it and commit the change to AWS code commit.
  
  Is there a way to make this automatic?
  
  Should I keep all projects in the same repo?
  
  What I want is: website change -> commit -> build website only -> push to AWS.
  
  The only solution I can think of is to rebuild the 3 projects every time.
  
  **Tags:** continuous-integration, git, continuous-deployment, continuous-delivery, aws-codepipeline
  
  > **Comments:**
  > **username_1**: See if this helps: https://medium.com/@username_1/using-monorepo-do-not-rebuild-unchanged-components-in-ci-c386e7c03426  
  > **username_0**: @username_1 i don't use docker  
  > **username_1**: Hm, why would it matter? Docker is absolutely not required there. The idea is that you need to check your directories for changes against previous state.  
  > **username_2**: "Is there a way to make this automatic?" Not quite sure what part isn't automatic yet. You mean the actual build & deploy steps aren't automatic?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2020-04-28. Score: 1
  
  I would suggest adding a job that checks changes in the latest commit and build only that service where some files have been changed.
  
  > **Comments:**
  > **username_0**: can you post a code snippet ?  
  
  ---
  
  