Skip to content
This repository was archived by the owner on Oct 11, 2022. It is now read-only.

Conversation

@mxstbr
Copy link
Contributor

@mxstbr mxstbr commented May 31, 2018

Status

  • WIP
  • Ready for review
  • Needs testing

As @brianlovin noticed in #3199, the CD for the desktop app wasn't working because CircleCI only runs builds for commits that are associated with a PR.

While we could set CircleCI to run builds for all branches, that's a very suboptimal solution as it would run a ton of unnecessary builds.

I came to wondering, why does the CD for alpha work if it doesn't build branches? Hidden in the CircleCI docs I found this snippet:

Note: For your default branch, we will always build all commits.

Which explains why alpha CD works, but production CD doesn't.

This patch is a very simple solution to this problem: we run desktop CD on the alpha branch. That is fine because the desktop CD only creates a draft GitHub release and we have to manually publish that release for anybody to get the update, so it doesn't matter if we CD from alpha or production!

As @brianlovin noticed in #3199, the CD for the desktop app wasn't
working because CircleCI only runs builds for commits that are
associated with a PR.

While we could set CircleCI to run builds for all branches, that's a
very suboptimal solution as it would run a ton of unnecessary builds.

I came to wondering, why does the CD for alpha work if it doesn't build
branches? Hidden in the CircleCI docs I found this snippet:

> Note: For your default branch, we will always build all commits.

Which explains why alpha CD works, but production CD doesn't.

This patch is a very simple solution to this problem: we run desktop CD
on the alpha branch. That is fine because the desktop CD only creates a
draft GitHub release and we have to manually publish that release for
anybody to get the update, so it doesn't matter if we CD from alpha or
production!
@brianlovin
Copy link
Contributor

@mxstbr sounds fine with me, we'll just end up with a lot of drafts - not the end of the world.

Tbh I didn't necessarily mind just doing yarn run release:desktop to do this as a one-off anytime we upgrade the app. CD is great, but may end up taking more time if we have to try and remember which release drafts are real updates or not :P

@mxstbr
Copy link
Contributor Author

mxstbr commented May 31, 2018

@mxstbr sounds fine with me, we'll just end up with a lot of drafts - not the end of the world.

It doesn't do that! It just updates the existing one until we hit publish on that

@brianlovin
Copy link
Contributor

Oh, well that's ideal then! Good to know

@brianlovin brianlovin merged commit 53e843e into alpha May 31, 2018
@brianlovin brianlovin deleted the fix-desktop-cd branch May 31, 2018 15:15
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants