Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.oracle.com/en-us/iaas/Content/devops/using/getting_started.htm below:

Getting Started with DevOps

Before you begin using the DevOps service, you must meet the following prerequisites:

• You must have access to an Oracle Cloud Infrastructure tenancy.
• Each service in Oracle Cloud Infrastructure (OCI) integrates with Identity and Access Management (IAM) for authentication and authorization, for all interfaces (the Console, SDK and CLI, and REST API). Access permissions are provided to users within a particular compartment. You can create a compartment or reuse an existing one. See Managing Compartments.
• An administrator in your organization needs to set up groups, compartments , and policies  that control which users can access which services, and which resources, and the type of access they have. See Authentication and Authorization.

1. Create a group or use an existing group in your tenancy.

   Users of this group are allowed to manage the DevOps service.

2. Create users and add them to the group, or add existing users to the group.
3. Generate an auth token for each user using Git to interact with your code repositories. You can also use API signing keys.

   Auth tokens are a form of user credentials. They are Oracle-generated token strings, which you can use to authenticate with third-party APIs that do not support OCI's signature-based authentication. The auth token is used for authenticating to OCI on the command line when performing Git operations. Administrators can create and distribute auth tokens to other users. Auth tokens do not expire. Each user can have up to two auth tokens at a time. For more information, see Managing User Credentials.

To grant users permission to access the various DevOps resources such as build pipelines, deployment pipelines, artifacts, and code repositories you have to create dynamic groups and IAM policies. See Managing Dynamic Groups and Getting Started with Policies.

For creating dynamic groups and policies, refer the following examples:

• For build pipelines, see Build Pipeline Policies.
• For code repositories, see Code Repository Policies.
• For deployment pipelines, see Deployment Pipeline Policies.

For more details, see DevOps IAM Policies.

With the OCI DevOps service you can create a connection to external repositories such as GitHub, GitLab, Bitbucket Cloud, Bitbucket Server, GitLab Server, and Visual Builder Studio. Following are the ways to integrate:

• GitHub, GitLab, GitLab Server, and Visual Builder Studio: You have to retrieve a personal access token (PAT) from those providers and store your PAT securely in an OCI vault. For instructions, see Build Source Integration.
• Bitbucket Cloud: You need your Bitbucket username and create an app password, then store the app password in an OCI vault. See Generating an App Password for Bitbucket Cloud.
• Bitbucket Server: You must create HTTP access token and then store the access token in an OCI vault.

This process is required only for integrating with third-party code repositories and not with the OCI DevOps code repository.

Project notifications keep you apprised of important events and the latest DevOps project status. They also alert you if you need to take any necessary action such as approving a workflow. You must create a topic  and add subscription  to the topic. For creating a topic, see Creating a Topic. The topic is required when creating your DevOps project.

The DevOps service uses an OCI Container Registry repository or an Artifact Registry repository for containing the completed build artifacts. You can create either of these repositories.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4