Linux installer

[artberri]

• lib/installers/Linux.js added
• README.md updated (change init.d with systemd)
• Added bash header to svc to run properly on linux.
• Fixes #2

[bryanmacfarlane]

Is journald a better choice? I believe if not specified, then journald is chosen and that was created by the folks that created systemd. Is there a reason to go with syslog?

[bryanmacfarlane]

Should we depend on network online? I guess that could be an option
http://unix.stackexchange.com/questions/126009/cause-a-script-to-execute-after-networking-has-started

[artberri]

• I will use journal, you are right
• I will double check about depending on network online

But I will also make some other changes, for example I will remove NODE_ENV=production, it causes node to not install devDependencies. It's a build server/agent, it is not production.

I'm checking it in a project that we are moving from Jenkins to VSO, once I have it working properly I'll came back with the fixes.

Thanks!

[artberri]

Hi again @bryanmacfarlane !

I think that now it's done. We have been running the vso-agent in Linux servers during a while (with systemd) successfuly, and we are now deploying to production with it also, (new VSTS Releases feature). Our migration from Jenkins was fine.

[bryanmacfarlane]

Cool. I'll merge

Note that we have a new agent replacing the node.
https://github.com/microsoft/vsts-agent

[artberri]

Cool!

Yeah! I saw it the some days ago. We will wait until it gets out from beta to use it, anyway I'll start doing some tests.

It will replace the node.js one, but... Is it intended to replace also the Windows one?

[bryanmacfarlane]

Yes. It will be the one agent.