Gleb Bahmutov

it is hard to say what is going one (try running with DEBUG flag), but maybe just use commands instead of NPM script names - this is possible since v1.8.0...

I did not have time to look into this Sent from my iPhone > On Apr 29, 2020, at 15:46, Peter Boomsma wrote: > >  > Any progress on...

So the user would manually set `SITE` environment variable (I see the Lighthouse plugin uses this for example)? I could read it, but to me this would not work with...

I did not see `SITE` environment variable until I have set it myself for deploy

I have tried using `URL` env variables like this ``` const baseUrl = process.env.DEPLOY_URL || process.env.DEPLOY_PRIME_URL || process.env.URL ``` but for example for this run https://app.netlify.com/sites/condescending-knuth-7cff53/deploys/5da0af7510b65eacdab96a44 the passed first url...

how does one access `build.publish` folder? Also, the plugin would need to serve the pages (statically) by itself before testing, right? On Fri, Oct 11, 2019 at 12:43 PM David...

super, will change the plugin so it could test both postBuild and postDeploy On Fri, Oct 11, 2019 at 12:53 PM David Wells wrote: > Yeah the site would need...

I agree, there is no good option and this concerns the other Linux CIs - they just don't panic and shut down the container :)

I say yellow color is a good step :)

I definitely see value in retrying everything even things that have side-effects - especially if the user really wants to. Real world problem solved here: https://github.com/cypress-io/cypress/issues/3135#issuecomment-454445249