Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

CR-4360 google artifact registry#312

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
kostis-codefresh merged 1 commit intomasterfromCR-4360-Google-Artifact-Registry
Aug 24, 2021
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion_data/nav.yml
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -406,6 +406,8 @@
url: "/amazon-ec2-container-registry"
- title: "Google Container Registry"
url: "/google-container-registry"
- title: "Google Artifact Registry"
url: "/google-artifact-registry"
- title: "JFrog Bintray.io/Artifactory"
url: "/bintray-io"
- title: "Quay.io"
Expand All@@ -428,7 +430,7 @@
url: "/jira"
- title: Jenkins Integration
url: "/jenkins-integration"
title: Codecov Integration
- title: Codecov Integration
url: "/codecov-integration"
- title: Google Cloud builder
url: "/gcloud-builder"
Expand Down
16 changes: 8 additions & 8 deletions_docs/integrations/docker-registries.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -12,14 +12,14 @@ toc: true
---
Codefresh enables you to integrate with several Docker container registries, including (but not limited to):

* [Docker Hub](docker-hub)
* [Azure Container Registry](azure-docker-registry)
* [Google Container Registry](google-container-registry)
* [Amazon EC2 ContainerRegistry](amazon-ec2-container-registry)
* [Bintray.io/Artifactory](bintray-io)
* [Quay.io](quay-io)
* [Github Container Registry](github-container-registry)

* [Docker Hub](docker-hub)
* [Azure Container Registry](azure-docker-registry)
* [Google Container Registry](google-container-registry)
* [Google ArtifactRegistry](google-artifact-registry)
* [Amazon EC2 Container Registry](amazon-ec2-container-registry)
* [Bintray.io/Artifactory](bintray-io)
* [Quay.io](quay-io)
* [Github Container Registry](github-container-registry)

For a different registry choose to configure using the [Other](other-registries) option.

Expand Down
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
---
title: "Google Artifact Registry"
description: "Learn how to use Google Artifacrt Registry with Codefresh pipelines"
group: integrations
sub_group: docker-registries
toc: true
---
To configure Google Artifact Registry, select Google Artifact Registry from the new registry drop down and then provide the following:

* Registry Name - A unique name for this configuration.
* Key File - The contents of a JSON key file. See below for [instructions](#generating-a-json-key-file).

## Generating a JSON key file

The JSON key file holds your credentials for a given [Service Account](https://cloud.google.com/compute/docs/access/service-accounts). To generate your key file, follow these instructions:

1. Go to your [Cloud Platform Console Credentials page](https://console.cloud.google.com/apis/credentials).
2. Select the project that you want to use for the credentials.
3. To set up a new service account, click **Create credentials** and then select Service account key.
4. Choose the service account to use for the key.
5. Choose to download the service account's public/private key as a JSON file.

You can find the complete guide [here](https://support.google.com/cloud/answer/6158849#serviceaccounts).

## Working with multiple projects

If you have more than one repository/project in Google Cloud, you can connect multiple Artifact Registries and define one as the “primary” for the `*docker.pkg.dev` domain.

This option means that every time Codefresh needs to pull an image, it will use that integration. If you wish to use another project to pull images, you can use the `registry_context` property as described in [working with multiple registries]({{site.baseurl}}/docs/docker-registries/working-with-docker-registries/#working-with-multiple-registries-with-the-same-domain).
3 changes: 2 additions & 1 deletion_docs/whats-new/whats-new.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -11,15 +11,16 @@ toc: true
## Recent Codefresh Updates:

## August 2021

- Using AWS Service Account for ECR Integration - [documentation]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/#setting-up-ecr-integration---service-account)
- Approval steps now have an extra confirmation - [documentation]({{site.baseurl}}/docs/codefresh-yaml/steps/approval/)
- Using Bitnami Sealed Secrets with GitOps - [documentation]({{site.baseurl}}/docs/yaml-examples/examples/gitops-secrets/)
- App proxy is now available for Bitbucket server - [documentation]({{site.baseurl}}/docs/administration/codefresh-runner/#optional-installation-of-the-app-proxy)
- Public Marketplace Registry - [documentation]({{site.baseurl}}/docs/administration/pipeline-settings/#advanced-pipeline-options)
- Google Artifact Registry - [documentation]({{site.baseurl}}/docs/integrations/docker-registries/google-artifact-registry)

## July 2021


- New platform IP addresses - [documentation]({{site.baseurl}}/docs/administration/platform-ip-addresses/)

## June 2021
Expand Down
[8]ページ先頭
©2009-2025 Movatter.jp