Normalize dependency scanning CI/CD variable naming
Release notes
Problem to solve
Historically, the DS_
prefix was utilized to prevent Dependency Scanning CI/CD variables from colliding with pre-existing variables. e.g. a pre-existing JAVA_VERSION
variable. This makes it harder to identify what variables are specific to Dependency Scanning when reading the documentation.
Proposal
We can improve this by prefixing all Dependency Scanning variables with DS_
and introducing the concept of global secure variables that utilize the SECURE_
prefix. As an example, say that SAST
and DS
both require a variable to configure the version of Java utilized. Without global variables, a an engineer would have to update the two different variables if they would like to configure the Java versions utilized by the SAST and DS jobs. With global variables this becomes much easier since both DS_JAVA_VERSION
and SAST_JAVA_VERSION
can defer to the value of SAST_JAVA_VERSION
if it's defined. The lookup of variables may look something like the following.
graph TD;
DS_JAVA_VERSION-->SECURE_JAVA_VERSION
SAST_JAVA_VERSION-->SECURE_JAVA_VERSION
Intended users
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.