Always trigger hooks.exit_checks.exit_env_vars
#66
Comments
luispedro
added a commit
that referenced
this issue
Jan 31, 2020
The big changes are failed tasks (contributed by @unode). Also, environmental variables are now always checked and creating a file called `__jug_please_stop.txt` will stop a `jug execute` run in a clean way. Full ChangeLog * jug.backend.base_store has 1 new method `listlocks` * jug.backend.base_lock has 2 new methods `fail` and `is_failed` * Add 'jug execute --keep-failed' to preserve locks on failing tasks. * Add 'jug cleanup --failed-only' to remove locks from failed tasks * 'jug status' and 'jug graph' now display failed tasks * Check environmental exit variables by default (suggested by Renato Alves, issue #66) * Fix 'jug sleep-until' in the presence of barrier() (issue #71)
luispedro
added a commit
that referenced
this issue
Jan 31, 2020
The big changes are failed tasks (contributed by @unode). Also, environmental variables are now always checked and creating a file called `__jug_please_stop.txt` will stop a `jug execute` run in a clean way. Full ChangeLog * jug.backend.base_store has 1 new method `listlocks` * jug.backend.base_lock has 2 new methods `fail` and `is_failed` * Add 'jug execute --keep-failed' to preserve locks on failing tasks. * Add 'jug cleanup --failed-only' to remove locks from failed tasks * 'jug status' and 'jug graph' now display failed tasks * Check environmental exit variables by default (suggested by Renato Alves, issue #66) * Fix 'jug sleep-until' in the presence of barrier() (issue #71)
luispedro
added a commit
that referenced
this issue
Feb 21, 2020
The big changes are failed tasks (contributed by @unode). Also, environmental variables are now always checked and creating a file called `__jug_please_stop.txt` will stop a `jug execute` run in a clean way. Full ChangeLog * jug.backend.base_store has 1 new method `listlocks` * jug.backend.base_lock has 2 new methods `fail` and `is_failed` * Add 'jug execute --keep-failed' to preserve locks on failing tasks. * Add 'jug cleanup --failed-only' to remove locks from failed tasks * 'jug status' and 'jug graph' now display failed tasks * Check environmental exit variables by default (suggested by Renato Alves, issue #66) * Fix 'jug sleep-until' in the presence of barrier() (issue #71)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running
jug.hooks.exit_checks.exit_env_vars()if the specificJUG_*environment variables are not defined has no effect. It should therefore be safe to run at every execution.Could the behaviour introduced by this hook become a permanent feature such that you can always influence jug execution though
JUG_*variables without having to explicitly register the hook on every jugfile?The text was updated successfully, but these errors were encountered: