Skip to main content

Initial setup

Before you create and run Pipelines on FPT Cloud DevOps Pipeline, confirm the following conditions are met. Each condition maps to one thing you will be asked for during Pipeline setup.

Confirm your FPT Cloud account​

  • Log in to FPT Portal at console.fptcloud.com with your FPT Cloud username and password.
  • Select the correct Tenant, Region, and VPC for the service.
  • If you do not have an FPT Cloud account yet, go to fptcloud.com, select Sign Up, and follow the on-screen instructions. The support team contacts you to confirm your details and activate your account.

Confirm your permissions​

You need access to a Project and permission to use DevOps Pipeline. Depending on your organization's policy, creating, editing, or running Pipelines may be restricted to:

  • Project Admin.
  • DevOps Engineer.
  • A user with the corresponding permission.

If you cannot create or edit a Pipeline, contact your Project Admin to request the required permissions.

Confirm you have a Project​

Pipelines are created and managed inside a Project. Before proceeding, confirm that:

  • You have at least one Project.
  • You have access to that Project.

If you don't have a Project yet, see Project management to create one.

Confirm your Source Connection​

To configure a Pipeline Source, the system must be connected to the appropriate data source. Supported sources include:

  • Git repository.
  • Container Registry.

Confirm the necessary connections are configured and you have access to the corresponding data source. See Manage credentials to connect a Git account, Container registry, or SonarQube server.

Confirm Auto Trigger prerequisites (optional)​

If you plan to use the Auto Trigger feature, confirm that:

  • The repository is hosted on a supported source control system.
  • You have permission to configure Webhooks on the repository.
  • A Webhook can be registered to send events to FPT Cloud DevOps Pipeline.
warning

Auto Trigger currently supports GitLab only.

Confirm your deployment environment (optional)​

If the Pipeline will deploy an application, confirm the target environment is ready and meets your project's deployment requirements. See Manage environments to connect a cluster and define one.

Next steps​