New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux installer #3
Linux installer #3
Conversation
unit += '[Service]' + "\n"; | ||
unit += 'ExecStart=' + service.command + "\n"; | ||
unit += 'Restart=always' + "\n"; | ||
unit += 'StandardOutput=syslog' + "\n"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?
But I will also make some other changes, for example I will remove 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! |
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. |
Cool. I'll merge Note that we have a new agent replacing the node. |
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? |
Yes. It will be the one agent. |
lib/installers/Linux.js
added