mauroc / squiddio_pi

squiddio_pi
3 stars 13 forks source link

free opensource MacOs builder plan on circleci: limit to 500 minutes/month #59

Closed mauroc closed 4 years ago

mauroc commented 5 years ago

one more reason to trigger builds only upon new versions submissions (e.g. git push origin v1.0.14) like in travis.

500 minutes/month is not a lot if you consider that these are time consuming build processes. ....

I don't know if I just got the "johnny come lately" plan or it's the same limitation for everyone. Just a thought. Not particularly urgent

rgleason commented 5 years ago

I was told by circleci support to remove the config.yml lines related to macos build because that requires a different plan, and she thought these lines were causing the particular errors I had, however I see the MacOs build worked.

rgleason commented 5 years ago

Found this page Build on macOS https://circleci.com/open-source/ ...If you’re building on macOS, CircleCI offers 25,000 credits per month ($180 annual value) free to open source builds. To get access, contact us at billing@circleci.com.

leamas commented 5 years ago

The macos builds tend to take around 5 minutes. That makes 100 builds, or three per day. It might not be a problem in the long run.

one more reason to trigger builds only upon new versions submission

Indeed. Would be a simple fix. But a pain if there are bugs from the past popping up.

I suggest the dreaded wait and see approach... If we run out of macos build time at the end of the month it shouldn't really be that big a problem

rgleason commented 4 years ago

Based on mauro's current master, before Jon's commit, this branch had appveyor and travis complete, circleci had an error due to macos not enabled. Circleci is going to enable it I believe. https://github.com/rgleason/squiddio_pi/commits/reset35-rg

I wonder if pushing a git tag will create a release?

rgleason commented 4 years ago

Perhaps it would be useful to be able to turn on and off the circleci deployment? Similar to pushing a tag to github to push new version files to the release tab? ..initiate it when you think it is ready, or maybe even a trial test first to be able to correct things, before the actual file deployment? Or is that too complicated?

rgleason commented 4 years ago

Skipping or Canceling a Build https://circleci.com/docs/2.0/skip-build/#section=jobs "adding a [ci skip] or [skip ci] tag anywhere in a commit’s title or description. This not only skips the marked commit, but also all other commits in the push."

mauroc commented 4 years ago

"adding a [ci skip] or [skip ci] tag anywhere in a commit’s title or description. This not only skips the marked commit, but also all other commits in the push."

this is really helpful and may take care of the 500 minute cap on Macos for the time being. Based on this, and alec's suggestion for the wait and see approach, I am going to close the issue