Skip to content
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

Improve logging #1

Open
tomwassenberg opened this issue Mar 19, 2019 · 0 comments
Open

Improve logging #1

tomwassenberg opened this issue Mar 19, 2019 · 0 comments

Comments

@tomwassenberg
Copy link
Contributor

Currently, a webhook trigger that actually results in a deploy, results in the following log output (in journald from stdout):

Mar 19 21:27:39 sadserver sudo[462]:      aas : TTY=unknown ; PWD=/var/www/aas/aas.svsticky.nl ; USER=root ; COMMAND=/usr/bin/systemd-run --no-block --property After=deploy-static-sticky.service -- systemctl start deploy-static-sticky.service
Mar 19 21:27:39 sadserver sudo[462]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 19 21:27:39 sadserver pipenv[31706]: Running as unit: run-r062e3550f3c24bd69f37d823c54eaa70.service
Mar 19 21:27:39 sadserver sudo[462]: pam_unix(sudo:session): session closed for user root

It would be nice if all triggers are logged, in one or two lines of output, and that it would include whether the trigger resulted in a deploy or not. (Which is currently only based on the branch.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant