Introduce a "security" remote concept to release-tools
Currently in release-tools, whenever a task specifies it should be treated as "security", we only use the dev.gitlab.org
remote.
In order to move security development to gitlab.com, we need to adapt release-tools to perform actions in a private project on gitlab.com rather than dev
.
However, because tagging/building ultimately happens on dev.gitlab.org, we can't remove the concept of "dev" entirely, it just needs to be decoupled from the "security" process.
-
Add security
remotes to all release-tools projects that point to the private projects -
Update security tasks to use those remotes rather thandev
Edited by Robert Speicher