use latest completed pipeline in target branch for scan result policy comparison
Published 1 year ago • 45 plays • Length 5:42Download video MP4
Download video MP3
Similar videos
-
4:39
multi pipeline comparison for scan result policies
-
7:10
overview of gitlab scan result policies
-
25:21
dast project level scan execution policies technical walkthrough
-
1:23
group level scan result policies
-
35:02
how to set up security scan policies in gitlab
-
9:39
git merge vs rebase: the definitive guide
-
6:20
gitlab 17 - api security and fuzzing enhancements and configuration
-
48:36
🌏 continuous integration
-
6:11
security policies: support additional filtering for scan result policies
-
8:14
migration from vulnerability-check rules to scan result policies with automated script
-
15:22
integrating 3rd party security scanners with gitlab
-
2:21
keep the main branch always green with gitlab merge trains
-
3:04
pipelines for merged results
-
1:42
is your ci pipeline failing? use gitlab to find failed jobs on your merge requests.
-
9:19
getting to merge trains - ways in which gitlab ci evaluates your pipeline jobs for execution
-
15:20
merge trains!
-
15:04
end-to-end pipeline tests for gitlab
-
4:09
add security scanning to your ci/cd pipeline in under 1 min
-
15:31
container scanning and scan results policies csm/cse enablement
-
13:07
044 gitlab ci: testing the merged state
-
10:33
gitlab: devsecops: part 10/12: how to do a merge request: the complete guide