- Feb 20, 2020
-
-
GitLab Bot authored
-
- Feb 18, 2020
-
-
GitLab Bot authored
-
- Feb 13, 2020
-
-
GitLab Bot authored
-
- Jan 22, 2020
-
-
GitLab Bot authored
-
- Jan 10, 2020
-
-
GitLab Bot authored
-
- Dec 16, 2019
-
-
GitLab Bot authored
-
- Dec 12, 2019
-
-
GitLab Bot authored
-
- Dec 04, 2019
-
-
GitLab Bot authored
-
- Nov 26, 2019
-
-
GitLab Bot authored
-
- Oct 30, 2019
-
-
GitLab Bot authored
-
- Oct 02, 2019
-
-
GitLab Bot authored
-
- Sep 18, 2019
-
-
GitLab Bot authored
-
- Sep 17, 2019
-
-
GitLab Bot authored
-
- Aug 28, 2019
-
-
Kyle Wiebers authored
-
- Aug 27, 2019
-
-
Kyle Wiebers authored
-
Rémy Coutable authored
Signed-off-by:Rémy Coutable <remy@rymai.me>
-
- Aug 26, 2019
-
-
Stan Hu authored
Signed-off-by: -
Dennis Appelt authored
-
- Aug 21, 2019
-
-
Rémy Coutable authored
Signed-off-by:
-
- Aug 20, 2019
-
-
Dennis Appelt authored
-
- Jul 11, 2019
-
-
Also, `SAST_CONFIDENCE_LEVEL` has been renamed in https://gitlab.com/gitlab-org/security-products/sast/merge_requests/72
-
- Jun 25, 2019
-
-
Philippe Lafoucrière -- authored
Note: This commit relies on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26801 which brings support to multiple extends. While `cache: {}` can disable a cache being set globally, it doesn't work with extends, which will perform a reverse deep merge based on the keys. The cache defined in the base `.default-cache` job won't be disabled in the report jobs. As a side effect, the `code_quality`, `sast`, and `dependency_scanning` jobs are running on a larger code base than expected, leading to timeouts. fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/11303 fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/60879 fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/12021
-
- May 02, 2019
-
-
- Apr 17, 2019
-
-
Marcel Amirault authored
-
Matija Čupić authored
-
- Apr 15, 2019
-
-
Kamil Trzcińśki authored
-
