First steps

From a newly created account to a working setup. Allow about an hour.

No access yet?

Start at Get access instead. This page assumes you have been added to the platform and have a Vector ID.

Suspect the network if the service is not loading

Your company network might need to permit access to a few URLs. See Network access.

1. Sign in

  • Go to code.vector.cloud and sign in with your Vector ID. No Vector ID yet? Sign up at portal.vector.com.
  • Accept the Terms of Use. They are shown once, on your first sign-in.

2. Set up multi-factor authentication

MFA is optional. Turn it on yourself on your Vector ID. Turn it on anyway: the account reaches your organization's source code.

3. Set up Git authentication

There is no password login

Username-and-password authentication is disabled for the web interface and for Git. You sign in with your Vector ID, and Git authenticates with an SSH key or an access token.

Choose one. An SSH key is the better default; a token is preferable behind a proxy that blocks SSH, and you need one anyway to pull images or packages onto your computer.

4. Find your projects

  • Open your group. Everything belonging to your organization sits under one top-level group named after it. Your projects, your registries and your teams are all inside it.
  • Check what you can see. A project you expected but cannot find is usually a team membership question: how to ask.

How your group is laid out

5. Run your first pipeline

  • Clone a project and look at its .gitlab-ci.yml.
  • Choose a runner. Each job in a pipeline runs on a runner, matched by tag, and your group has its own. What these terms mean. What types of runners are deployed depends on your agreement with Vector.
  • Push a branch and watch the pipeline under Build → Pipelines.

Runners and tags

6. Know what needs Vector

You have Developer permissions: branches, merge requests, pipelines, publishing packages into your group. These stay with Vector:

You want to Ask your Vector contact
Create a new project or group Yes
Add or change a CI/CD variable or secret Yes
Get a package or tool made available Yes
Get more or different runners Yes
Extend someone's access Yes

The full list, and how to ask

Accounts go dormant

An account unused for 90 days is deactivated automatically. If you are away for a while, expect to ask for reactivation when you get back.

What next

Git on the platform


The branching model and the merge request workflow.

Git

Local setup


What differs between a pipeline and your computer, mainly licenses and image access.

Local setup