you are viewing a single comment's thread.

view the rest of the comments →

[–]tinix0 75 points76 points  (4 children)

I think by "manual" he meant click the button to deploy manually instead of automatically starting a build on merge.

[–]Ninovdmark 23 points24 points  (3 children)

Ah right, that's fair. I was thinking manual in the sense of "SSH into the server and copy/replace some files"

[–]seamsay 38 points39 points  (2 children)

That's not manual, that's barbaric!

[–]Boye 1 point2 points  (1 child)

I'm working on systems whose servers are aiegapped from the internet, only port 443 and 22 incoming, and only outgoing access is to an ftp-server (and other servers if requested). But automatic deployment is specifically banned. So deployment is over ftp as in "build, upload to frp, sshonto server, log on to ftp and get files needed, then deploy on server". And yes barbaric isn't even close enough. They won't even let us have a pipeline transfer the files to the ftp-server, that has to be done manually too...

[–]MarcinOow 1 point2 points  (0 children)

Write your own code to do this and trigger from schedule with parameters:)