Our mission is to make cloud computing as easy and accessible as mobile computing. You can find our Next.js community here.

# Micro

Asynchronous HTTP microservices

Trending conversations
503 on deployment
@codelayer · 22d
ENV variables
@remotealex · 4h
BRU1 instances are timing out
@helguita · 31d
Could someone point me toward strategies for decreasing my PHP lambda size?
@unitof · 5h
Images not showing on CRA deployment
@passingmagic · 5h

Now for GitHub + CI

December 7, 2018 at 8:23am

We're using Now v2

I'm looking for a way to block deploys with "Now for Github" until our CI checks are complete, but I can't see a way to do that.

I presume that we could run our tests as part of the build and so prevent the deploy that way, but this'll mean running the suite once in CI and during deploy in order to get those reassuring green ticks on our Pull Requests. That seems wasteful and I'm not even sure that we can get our whole app/build tools/test tools into the space limit of a v2 build.

Am I missing something? Or maybe going about this wrongheadedly?

January 5, 2019 at 5:43pm

I have the same question! Currently I'm running the deployment as a CI step, but I'd love to use now+github if there is a way for it to play nicely with CI tests

  • reply
  • like

January 14, 2019 at 10:11am

Shameless plug, this sounds like the perfect use case for Plek:

It gives you a way to deploy with Now from your CI including GH status updates.

For a short introduction I also wrote this blog post:

Let me know what you think!

  • reply
  • like