Cli: simple command to trigger build

Created on 5 Nov 2018 · 11Comments · Source: netlify/cli

- Do you want to request a feature or report a bug?

feature

- What is the current behavior?

netlify deploy uploads stuff.

sometimes i just want to trigger deploy. maybe call it netlify trigger? optionally have it accept netlify trigger deploy just for fun?

this is needed so that we dont have to jump back to the web UI when demoing addons (or really anything else using CLI in future)

Source

sw-yx

👍3

All 11 comments

sometimes people may type netlify deploy when they actually mean to netlify trigger (i certainly would). might want to add a "you may want.." message in "netlify deploy" to minimize surprise/guide people to what they mean to do

sw-yx on 5 Nov 2018

👍1

Seems like this happens when you git push

Is this issue still relevant? 😃

DavidWells on 2 Jul 2019

what if i dont have any git changes but still want to rebuild for content reasons?

sw-yx on 2 Jul 2019

I see. So external content changes (like contentful)

Yeah makes sense.

How does this command sound to you?

netlify deploy:trigger
// or
netlify deploy --trigger

This way we keep top level api smaller

DavidWells on 2 Jul 2019

i like the second option

edit from 2020: actually i take that back, i would rather netlify deploy:trigger but i'm honestly not super opinionated about it

sw-yx on 3 Jul 2019

Hey @sw-yx, I’m not understanding the nuance of a trigger versus a deploy?

Is there a way I can have Netlify simply ship the build folder from my GitHub instead of having them download my yarn project and build it everytime? (This is slower than desired because I’m using playwright — large binary — for e2e testing)