The platform ¶
Five things are worth knowing before you start working. None of them need configuring on your side; this is how the platform is already set up for you.
How the pieces fit¶
flowchart TB
subgraph gl["code.vector.cloud"]
direction LR
repo["Your projects<br/>branches, merge requests"]
reg["Package & container<br/>registries"]
end
subgraph env["Your CI/CD environment"]
direction LR
run["Runners<br/>Linux and Windows"]
cache["Build caches<br/>optional"]
lic["License server<br/>Vector tools"]
end
repo -- "jobs" --> run
run -- "packages, images" --> reg
run --> cache
run --> lic
GitLab is shared; your runners are not. Everyone works on the same GitLab instance, separated by top-level group. The runners that run your pipelines, and the caches and storage they use, are in a network dedicated to your organization, and no other customer can reach them.
Your group
One top-level group for your organization, with a teams folder for people and a
registries folder for packages and images.
Runners
Your own Linux and Windows runners, how to choose them with tags, and the optional build caches.
Registries
Where packages and container images live, and how to pull from them and publish into them.
Licensing
A Vector license server is available to your pipelines. Every tool needs a license your organization has purchased, and your jobs have to add the server to the Vector License Client.
Network access
The hosts your IT department has to allow, and what to do when a job needs to reach an external server.