| Age | Commit message (Collapse) | Author |
|---|
|
|
|
from https://docs.gitlab.com/ce/ci/yaml/README.html#cache:
"By default caching is enabled and shared between pipelines and jobs,
starting from GitLab 9.0"
|
|
|
|
present
|
|
Because this is used in some places, such as tor configuration, it can be useful
to have this set to something real for contact purposes.
|
|
Fixes: #8427, #8812
|
|
Resolves: #8891
|
|
|
|
|
|
|
|
It is more useful to check to see if Soledad is running before running the
webapp tests that require soledad to be running.
|
|
|
|
|
|
Updating platfrom 0.9 (soledad 0.8.0) to 0.10 (soledad 0.10.3) requires a
soledad-server migration. This integrates the migration in the CI
upgrade_test. Fixes #8881
|
|
They might be meaningful response codes for some scenarios. But
so far we are not conciously sending them out. If they occur that
is because we handed them down from couch. So we might want to
fix the underlying issue. Couch 409s should be caught by the webapp
and handled there.
|
|
Fix the order of the leap repository so it matches the correct repository
layout. Fixes #8888.
|
|
|
|
webapp#8806 needs couch design docs that allow invite codes
to be sorted by date. This updated needs to be deployed in sync
with the new webapp version.
|
|
|
|
For the CI, we were using the gitlab-runner ssh key for all provider builds,
this replaces it with an unique one for each provider.
|
|
subrepo:
subdir: "puppet/modules/tor"
merged: "4380e2ea"
upstream:
origin: "https://leap.se/git/puppet_tor"
branch: "master"
commit: "4380e2ea"
git-subrepo:
version: "0.3.1"
origin: "https://github.com/ingydotnet/git-subrepo"
commit: "a7ee886"
|
|
Resolves: #8879
|
|
0255d8a42fc2c37cfaa660a43936ae546b6178ef removed this class, but it still was
being referenced. Since it is not needed, we can just remove the reference.
Fixes: #8878
|
|
|
|
In order to refactor the tor services, we need to split them out into three
different services. This adds the hidden service class that is necessary to
support the previous commits. Fixes #8864.
|
|
Simply disabling exit policies is not enough to disable an exit node, it also
needs to be explicitly disabled. This may change in future versions of tor, but
for now, explicitly adding 'ExitRelay 0' to the configuration is needed. This
fixes #8863.
|
|
The 'tor' service is now three separate services, 'tor_exit', 'tor_relay', or 'hidden_service'.
|
|
The apt sources lines for people using more experimental software was
wrong, we abolished the 'experimental' repository some time ago and
develoment happens now in the master branch.
solves #8862, #8876
|
|
We'll release soon so we pin both git repos
to there release version branches instead of
pulling from master.
|
|
For newer than jessie the 'old' code was enough. This bug didn't show up
because our testing images had the keys and sources lines already
included within /etc/apt…
solves #8862
|
|
Resolves: #8871
|
|
fog-aws gem was not installed so Job #19895 failed for b566104d
The reason was that caching was configured wrongly so files got
cached vertically for each job.
After re-configuring the gitlab-runner cache on beluga, caches
were lost and resulted in failing builds.
This commit configures caching in a way that we define one global
cache for all platform pipelines.
Resolves: #8872
|
|
|
|
|
|
|
|
Commit 55b784f2 fixed this for mail.bitmask.net, but
not for demo.bitmask.net. See
https://0xacab.org/leap/platform/commit/55b784f2ccd6336db4bab9157a8498cb87c562ff
This fixes #8843.
|
|
Soledad is now taking care of the design of said database.
Closes #8428
|
|
|
|
Boolean facts must be escaped with str2bool. This commit includes
new tests to catch VPN problems like this in the future.
|
|
|
|
hidden service should be activated iff tor is among the active services and
tor.hidden_service.active == true
|
|
|
|
|
|
ssh error. closes #8811
|
|
The old client is compatible, just the version check did not allow
it. People are still relying on the old client for a while, and this
prevents people from upgrading. This fixes #8850.
|
|
Provider checkout was being done to a pre-existing directory, which
resulted in an error about the directory already existing
(see https://0xacab.org/leap/platform/-/jobs/15730), this should fix
that problem.
|
|
Fix indentation; setup some more clear variables.
Add a third variable to ensure the proper platform branch is checked
out. This is necessary because otherwise environment deploys get stuck
because the platform directory is in a detached state and then the
environment deploys will not proceed because the branch check
fails. This will fix #8843.
|
|
|
|
The example had many tabs causing my eyes to bleed. It also didn't use
the template properly to fix an issue.
|
|
4173154a177b00c11a36b3168b1ce12af59f04af or later (>1.9.2). resolves #8474. create new invites with `leap run invite`
|
