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

Commit08d90dc

Browse files
Github action no longer requires a registry
1 parent5725ab6 commit08d90dc

File tree

3 files changed

+7
-11
lines changed

3 files changed

+7
-11
lines changed

‎_docs/integrations/github-actions.md‎

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ In order to use a Github action in Codefresh you need to make sure that the foll
3030

3131
1. The[Github action](https://github.com/marketplace?type=actions) you have selected is Docker based and has a self-contained and valid Dockerfile
3232
1. You have read the documentation of the Github action and know what arguments/input it requires
33-
1. You have at least one Docker registry connected to your Codefresh account.
33+
3434

3535
Also notice that since Github actions are created by the community, it is your responsibility to filter and curate any Github actions that you wish to use in Codefresh pipelines. If for example you use a Github action, and then it is removed by its creator, the Codefresh pipeline that uses it will break as well.
3636

@@ -41,7 +41,7 @@ Also notice that since Github actions are created by the community, it is your r
4141
Codefresh offers a github-action-to-codefresh step converter. This converter has two functions
4242

4343
1. When you create your pipeline it will analyze the Github action and try to find what arguments it requires. You must then fill the values needed by yourself
44-
1. When the pipeline runs, it will automatically find the Dockerfile of the Github action, build it, push it in theDocker registry that you specify and then use it as a standard Codefresh step.
44+
1. When the pipeline runs, it will automatically find the Dockerfile of the Github action, build it and make available thedocker image in any subsequent step in the same pipeline.
4545

4646
All this process is automatic. You just need to make sure that all arguments/inputs of the Github action as provided using[pipeline variables]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#creating-new-pipelines),[shared configuration]({{site.baseurl}}/docs/configure-ci-cd-pipeline/shared-configuration/) or any other standard mechanism you already use in Codefresh.
4747

@@ -73,18 +73,16 @@ Then click on the Github action that you want to use in your pipeline. On the ri
7373

7474
{% include image.html
7575
lightbox="true"
76-
file="/images/integrations/github-actions/snyk-arguments.png"
77-
url="/images/integrations/github-actions/snyk-arguments.png"
76+
file="/images/integrations/github-actions/snyk-action-arguments.png"
77+
url="/images/integrations/github-actions/snyk-action-arguments.png"
7878
max-width="70%"
7979
caption="Using the Snyk Github action"
8080
alt="Using the Snyk Github action"
8181
%}
8282

83-
This YAML snippet is a template and the following need to be filled under the`arguments` block:
83+
This YAML snippet is a template and you need to fill the`env` block under the`arguments` block:
84+
The required environment variables are specific to each Github action so check the documentation of the action itself.
8485

85-
*`env` - a list of arguments. They are specific to each Github action so check the documentation of the action itself
86-
*`registry` - the name of a[registry connected to Codefresh]({{site.baseurl}}/docs/docker-registries/external-docker-registries/). You can find the names in your[integrations page](https://g.codefresh.io/account-admin/account-conf/integration/registry)
87-
*`registry_repo` - the repository/account that you wish to use in the registry for storing the Github action. In the case of Dockerhub it is your Dockerhub username, for the Codefresh registry it is your Codefresh username and so on.
8886

8987
In the example above we are using the Snyk Github action. By visiting the[documentation page](https://github.com/marketplace/actions/snyk-cli-action) we find that this action expects a`SNYK_TOKEN` as input.
9088

@@ -115,8 +113,6 @@ steps:
115113
envs:
116114
- SNYK_TOKEN: '${{SNYK_TOKEN}}'
117115
cmd: test alpine@latest
118-
registry: dockerhub
119-
registry_repo: codefreshplugins
120116
{% endraw %}
121117
{% endhighlight %}
122118

@@ -143,7 +139,6 @@ Once the pipeline reaches the Github action step, the converter will do automati
143139

144140
1. Find the Dockerfile of the Github action
145141
1. Build the Dockerfile
146-
1. Push the resulting image to the connected Codefresh registry
147142
1. Take the resulting image and insert it as Codefresh step
148143
1. Pass the environment variables as arguments to the Github action
149144
1. Run the`cmd` command

‎_docs/whats-new/whats-new.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ Recent Codefresh updates:
1616
- New variable`CF_BRANCH_TAG_NORMALIZED_LOWER_CASE` -[documentation]({{site.baseurl}}/docs/codefresh-yaml/variables/#system-provided-variables)
1717
- Trigger a Kubernetes Deployment from a Dockerhub Push Event -[documentation]({{site.baseurl}}/docs/yaml-examples/examples/trigger-a-k8s-deployment-from-docker-registry/)
1818
- Uploading or Downloading from a Google Storage Bucket -[documentation]({{site.baseurl}}/docs/yaml-examples/examples/uploading-or-downloading-from-gs/)
19+
- Use Github actions no longer requires a Registry -[documentation]({{site.baseurl}}/docs/integrations/github-actions/#how-it-works)
1920

2021
###March 2020
2122

61.3 KB
Loading

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp