So I have front-end and backend apps. When I make changes to them I need to deploy them both. But when I push both, then one gets cancelled and only one component gets deployed :D ( Like wtf )
And I can’t manually force a component to run a deploy again on the front-end project :D
Like what should I do?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer

👋🏼 @MihkelL

I see that you have each app in a different repo. If you have Deploy on Push enabled and you make a commit to your repo, it will create a new deployment to deploy the changes. Generally speaking, whenever a deployment is created, it cancels any in progress ones and starts building.

But, all deployments will deploy all components and not just the one that triggered it via commit. So, the second deployment will pick up the changes/commit from the canceled deployment. This is also the case when you manually click the Deploy button.

Though I realize that the deployment descriptions (commit <hash> pushed to <repo>) can be a bit confusing as they only list one commit. So you can definitely just push to both repos and all changes will be automatically deployed.

For example, if you have repos frontend and backend:

  1. You push commit to frontend
  2. App Platform refreshes the latest commit and creates a new deployment
  3. You push a commit to backend
  4. App Platform refreshes the latest commit and creates a new deployment. The first deployment is canceled and this one starts. However it will both new commits on both repos, and not just the one that was just pushed to backend.

You can confirm by looking at the build logs for the second deployment. In the first few lines you will see the commit hashes that are used. I hope this clears things up!