soledad.git - [soledad]

Age	Commit message (Collapse)	Author
2017-06-28	[pkg] ensure repo has tags from upstream	drebs

2017-06-28	[test] remove double avoidance of synchronous benchmark tests	drebs

2017-06-27	[pkg] Note about missing manpage to .gitlab-ci.yml	Varac

2017-06-26	[pkg] Use git-buildpackage image for packaging	Varac

2017-06-26	[pkg] Disable stretch builds until lintian is fixed	Varac
	see https://0xacab.org/varac/soledad/-/jobs/12934 Resolves: #8894
2017-06-26	[pkg] LINTIAN_OPTS is now a string	Varac

2017-06-26	[pkg] Lint .gitlab-ci.yml	Varac

2017-06-26	[pkg] Ignore lintian warnings until they get fixed	Varac

2017-06-26	[pkg] Add package building stage	Varac

2017-05-10	[feat] Build/push docker (see leap/platform#8755).	Micah Anderson
	When the testing/docker directory is changed, the `build_docker_image` CI job is triggered to build the docker image and push it to the soledad container registry. This is part of an effort to move all the docker images into their own project's container registry, and to build/provide them automatically (see leap/platform#8755). This is accomplished by the following: added the necessary overlay DOCKER_DRIVER variable to .gitlab-ci.yml added a build_docker_image job with docker:dind service enabled enabled container registry in soledad project added LEAP_CODE_O_MATIC_PRIVATE_TOKEN to project moved docker image from scripts:docker/soledad to soledad:testing/docker docker push gitlab-buildpackage:soledad to soledad container registry removed gitlab-buildpackage:soledad image and scripts/docker/soledad changed image in .gitlab-ci.yml to use new location Note: until https://gitlab.com/gitlab-org/gitlab-ce/issues/19813 is resolved, we have to use this method.
2017-04-19	[test] use soledad image from 0xacab registry in ci	drebs

2017-04-04	[bug] cache pip instead of tox	Victor Shyba
	Caching .tox breaks when installing new dependencies. Caching pip instead and asking tox to always recreate will ensure newer dependencies are installed while getting existing ones from cache.
2017-04-03	Post benchmark results to elastticsearch	varac
	In order to do this from CI, please create a secret variable (at i.e. https://0xacab.org/varac/soledad/settings/ci_cd) called PYTEST_OPTS and use this example: --benchmark-autosave --benchmark-storage="elasticsearch+https://USER:PASSWORD@moose.leap.se:9200"
2017-03-17	[test] Fix Shared Runner config	efkin

2016-12-19	[test] remove benchmark from ci pipeline	drebs

2016-12-17	[test] add couchdb tag for tests	drebs

2016-12-12	[test] configure baremetal gitlab ci runner	drebs

2016-12-12	[test] rename benchmark tests directory and tag	drebs

2016-10-21	[tests] cache tox folder	Victor Shyba
	This should avoid tox virtualenv recreation.
2016-10-21	[feature] use latest image	Victor Shyba
	Instead of hardcoding a version. This should give us the flexibility of changing images without changing code.
2016-09-30	[test] add flake8 code check and generalize name of tox env	drebs

2016-09-09	[test] add tagged perf job for gitlab-ci	drebs
	In order to configure performance tests to run in a specific machine we need to add a tagged job to .gitlab-ci.yml file. That job will only execute the perf tests, and then we can have runners that will only run those jobs.
2016-09-02	[tests] add pep8 in main tox run from within the gitlab script	Kali Kaneko
	add coverage reports too. (hereby we swear not to write stupid tests just because it feels good to have an increased coverage metric). - Resolves: #8416
2016-08-09	[test] use "leapcode" in docker image name	drebs
	"leapcode" is the LEAP docker hub organisation varac could squat (https://hub.docker.com/r/leap/ was already taken).
2016-08-01	[test] use docker image with couchdb service to run tests	drebs

2016-07-12	[test] use tox in gitlab-ci	drebs

2016-06-22	[test] use docker for gitlab-ci tests	drebs

2016-06-08	[feat] add .gitlab-ci.yml	drebs