| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ssh://greyhound.leap.se:4422/usr/local/bin/platform_test
|
|
|
|
|
|
(#6935)
|
|
to get send
|
|
pushed, i.e. rebased
|
|
leap-platform-test, and a different one that indicates the last deploy failed
|
|
|
|
|
|
|
|
|
|
if this option is passed, and the lockfile exists, then deploys will not
happen and an email will be generated. If it doesn't exist, a deploy
will happen and then tests will be run. If the tests fail, the lockfile
is set, and will not be removed unless tests pass, or if it is manually
removed.
I have set this option on the regular cron test, but not on the push to
the repository, this makes it so a push to the repository will still
allow deploys to happen, and removes the lockfile if tests succeed,
otherwise the regular deploys will not happen (allowing us to investigate)
|
|
|
|
|
|
|
|
|
|
leap local destroy $vm), then run a bootstrap_nodes() on the nodes,
which will do a leap local start on the node, then a leap node init, and
then a leap deploy.
This should do a full cycle test
|
|
|
|
|
|
|
|
|
|
|
|
|
|
kernel modules after a kernel update (#6494)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
filters
|
|
|
|
better use a file that is touched instead. more robust.
|
|
|
|
|
|
|
