summaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)Author
2017-06-30[CI] Fail when CI_JOB_NAME is not recognizedVarac
2017-06-30[CI] Move more commands into functionsVarac
2017-06-30[CI] Use CI_JOB_NAME to determine what action to takeVarac
2017-06-30[CI] Check for mandatory env variables on platform buildsVarac
2017-06-30[CI] Pin leap_cli so fog-aws is installedVarac
2017-06-28platform test - pin ruby version to 2.1.10 when using rbenv, since that is ↵elijah
the latests that will work.
2017-06-23Use default apt component for CIVarac
Resolves: #8828
2017-06-17Renewed commercial cert for platform CIVarac
2017-06-16[CI] Use older commit for puppet-catalog-testVarac
After `puppet-catalog-test` has been recently updated it failed in our CI with: File[/etc/apt/sources.list] has notify relationship to invalid resource Exec[apt_updated] See #8814 for more details. Resolves: #8814 https://github.com/invadersmustdie/puppet-catalog-test/commit/ac386793c2c456d2071dd0adda716224128f0bb3
2017-06-16[CI] Use master branch of leap_cliVarac
We moved from develop to master some time ago so we should use master for CI testing as well.
2017-05-23[vagrant] Use private networking IP from eth1 if presentvarac
2017-05-23[vagrant] Move $OPTS to vagrant configvarac
2017-05-23Lint configure-leap.shvarac
2017-05-23[vagrant] Use private networking for direct accesvarac
Without private networking, the box cannot get directly accessed, only via port forwardings. https://www.vagrantup.com/docs/networking/private_network.html - Resolves: #7769
2017-05-10Remove pixelated submodule from the example providerTulio Casagrande
2017-04-27change environment names to match ci-build.shMicah Anderson
2017-04-27Improve ci-build.sh (Closes #8771)varac
* Change environment names for clarity: . Use staging for deploying to latest . Use production environments to deploy to demo: production/vpn production/mail * Install leap_cli if not present and define default values * Remove old nodes from cached runs * Remove no longer used SEEDS variable * Debugging improvements: . Hide secrets when calling ci-build.sh with xtrace enabled . Use unbuffer to we can add debug output locally . Add debugging to build_from_scratch()
2017-04-25Add a production environment for demovpn, demomailMicah Anderson
Pull duplicated bits into a function
2017-04-25Fix the pipefail by putting ts inside of ci-build.shMicah Anderson
2017-04-20switch to using CI_ENVIRONMENT_NAME and defaulting to the basic deploymentMicah Anderson
2017-04-20Enhance ci-build.sh for latest CI builds.Micah Anderson
. Reorganize script to allow for multiple builds . Add latest build, pulling from the ibex provider . Run the build as the cirunner unprivileged user . Set pipefail because job is run within a pipe . Change name of 'build' stage to 'deploy' . Setup an environment for the latest CI deployment
2017-04-20Ensure leap command is setup properly for CIMicah Anderson
Add a `leap help` command at the end of the CI setup.sh to ensure that the command is setup properly before continuing
2017-03-29Run leap info after deployvarac
2017-03-16Use http://deb.leap.se/platform jessie snapshots for platform CIvarac
2017-03-15[8144] Remove Haproxy testsvarac
2017-02-09tests: check process by either process scan or service name. closes #8753elijah
2017-01-31Platform CI: Dont run bundle install in parallelvarac
Closes: #8684
2017-01-10New unbound runs with debug flag by defaultvarac
2016-12-23bugfix: remove deprecated parameter from soledad test scriptdrebs
2016-12-23Change regex for soledad process checkvarac
2016-12-20[Vagrant] Remove versioning of provider configvarac
2016-12-08Use webapp/nickserver:master on leap_platform:master (#8678)varac
2016-11-24Merge branch 'bug/avoid-hanging-soledad-sync-test-scripts' into 'master' Varac
Bug/avoid hanging soledad sync test scripts See merge request !53
2016-11-22use lock to avoid running multiple soledad tests (#8590)drebs
If a soledad sync test script is already running, there's no need to run another one. This avoids having multiple test script hanging and eating up resources. We have seen this situation under development circumstances, when the soledad server has been modified in a way that the client hangs and never finishes.
2016-11-22add a timeout for the soledad sync test script (#8590)drebs
If for any reason a sync takes too long, the script will timeout and log an errro.
2016-11-09Don't do strict checking for nickservervarac
Sometimes nickserver is listed with `ruby /usr/bin/nickserver start` in the process table, sometimes with `/usr/bin/ruby /usr/bin/nickserver start`. We should do proper checking with `systemctl status nickserver` to make sure the service is up though (https://leap.se/code/issues/8579). Meanwhile it's ok to not do strict checking.
2016-11-08New nickserver is using fully qualified ruby path nowvarac
2016-10-25Change CI build webapp source branch to master.Micah Anderson
The develop branch was removed, and current master is the same as develop was before.
2016-10-18Fix Are_daemons_running test for nickservervarac
2016-10-18Use random vm name when running localvarac
when using gitlab-runner locally, CI_BUILD_ID is always 1 which will conflict with running/terminating AWS instances in subsequent runs therefore we pick a random number in this case
2016-10-18Use caching in setup.shvarac
2016-10-18Include secret variables from gitlab ci settingsvarac
- Assemble cloud.json from aws credential env vars - Deploy ssh private key from env var
2016-10-18Add public sshkey of gitlab-runner for platform buildsvarac
2016-10-18Checkin cloud.json template without credentialsvarac
2016-10-18Use leap vm for ci buildsvarac
2016-10-18Dont track facts.json and users/gitlab-runnervarac
2016-10-18Dont track provider/files/ssh/known_hostsvarac
2016-10-18Lint ci-build.shvarac
2016-10-11Use puppet-catalog-test from git to circumvent deprecation warnvarac
2016-09-01cherry pick from "break on every deploy error"elijah