You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
Currently, a webhook trigger that actually results in a deploy, results in the following log output (in journald from stdout):
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.)
The text was updated successfully, but these errors were encountered: