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

Commit06785a0

Browse files
committed
Merge branch 'master' into support-kb-migration
2 parentscffc87a +e9d56b7 commit06785a0

18 files changed

+374
-111
lines changed

‎_docs/administration/account-user-management/access-control.md‎

Lines changed: 289 additions & 78 deletions
Large diffs are not rendered by default.

‎_docs/administration/account-user-management/add-users.md‎

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,13 +52,18 @@ Once you add a user to your Codefresh account, you can do the following to manag
5252

5353

5454
##Teams in Codefresh
55-
Teams are users who share the same permissions, roles, or requirements defined according to company processes. Teams allow you to enforce access control through ABAC (Attribute Based Access Control).
55+
Teams are users who share the same permissions, roles, or requirements defined according to company processes. Teams allow you to enforce access control through ABAC (Attribute Based Access Control).
56+
5657
By default, there are two teams:
5758
* Users
5859
* Admins with users[invited as collaborators](#assign-a-user-to-a-team)
5960

6061
>Only Enterprise customers can add new teams. Other Codefresh plans can only use the predefined*Users* and*Admin* teams.[Contact us](https://codefresh.io/contact-us/){:target="\_blank"} to upgrade to an Enterprise plan.
6162
63+
###Automatically creating projects for teams
64+
65+
As part of the global pipeline settings for an account, when creating a team, you can also automatically create a project and a project tag with the same name as that of the team. Enabling**auto-create projects for teams** (disabled by default), simplifies permissions setup for pipelines and projects, as it also creates a Read rule for the project. See[Auto-create projects for teams]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#auto-create-projects-for-teams).
66+
6267
###Create a team in Codefresh
6368

6469
Create a team in Codefresh and then assign users to the team. You can assign the same user to multiple teams, as in most companies, users have overlapping roles.

‎_docs/integrations/git-providers.md‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -376,12 +376,14 @@ The Using means the following use cases:
376376

377377
You will get an error of Permission Denied or Forbidden to a Git Context that you do not have the correct permissions for that action.
378378

379-
###Tagging the Git Context
380-
381-
1. Navigate to Account Settings > Integrations > Configure for Git.
382-
1. Hovering over the integration name (Git Context), you will see "Edit Tags" just before the edit symbol.
383-
1. Select "Edit Tags," and you can add and remove tags.
384-
1. Click Save when done.
379+
###Assigning tags to Git Contexts
380+
381+
1. In the Codefresh UI, on the toolbar, click the**Settings** icon, and then from Configuration in the sidebar, select[**Pipeline Integrations**](https://g.codefresh.io/account-admin/account-conf/integration){:target="\_blank"}.
382+
1. Click Configure for Git to see the list of Git provider integrations (Git contexts).
383+
1. Select the row with the integration for which to add tags.
384+
1. On the right, click**Edit Tags**.
385+
1. Type in the tag or tags.
386+
1. Click**Save**.
385387

386388
###Setting the Permissions
387389

‎_docs/pipelines/configuration/pipeline-settings.md‎

Lines changed: 70 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -9,17 +9,10 @@ toc: true
99
---
1010

1111

12-
You can define globalparameters for all the pipelines in the account. Users can still override someof these options for individual pipelines.
12+
You can define globalsettings for all the pipelines in the account. Users can still override somesettings for individual pipelines.
1313

14-
{% include image.html
15-
lightbox="true"
16-
file="/images/pipeline/pipeline-settings/pipeline-settings-ui.png"
17-
url="/images/pipeline/pipeline-settings/pipeline-settings-ui.png"
18-
alt="Pipeline settings"
19-
caption="Pipeline settings"
20-
max-width="80%"
21-
%}
2214

15+
##Access pipeline settings
2316
1. In the Codefresh UI, on the toolbar, click the**Settings** icon.
2417
1. From Configuration in the sidebar, select[**Pipeline Settings**](https://g.codefresh.io/account-admin/account-conf/pipeline-settings){:target="\_blank"}.
2518

@@ -40,9 +33,75 @@ file="/images/pipeline/pipeline-settings/pause-pipeline-enabled.png"
4033
url="/images/pipeline/pipeline-settings/pause-pipeline-enabled.png"
4134
alt="Pause Build Execution pipeline setting enabled"
4235
caption="Pause Build Execution pipeline setting enabled"
43-
max-width="80%"
36+
max-width="60%"
4437
%}
4538

39+
##New pipeline as templates
40+
41+
Here you can define global template behavior. The options are:
42+
43+
* Enable[pipeline templates]({{site.baseurl}}/docs/pipelines/pipelines/#using-pipeline-templates) for users. If this is enabled some pipelines can be marked as templates and users can still select them when creating a new pipeline.
44+
* Decide if users can clone an existing pipeline (along with its triggers and associated parameters) when[creating a new pipeline]({{site.baseurl}}/docs/pipelines/pipelines/#creating-a-pipeline).
45+
46+
Note that templates are simply pipelines “marked” as templates. There is no technical difference between templates and actual pipelines.
47+
48+
##Auto-create projects for teams
49+
Enabled by default, auto-create projects for teams, automatically creates projects whenever you create teams in your account. It also creates access-control rules for the same team to projects and pipeline, simplifying setup and saving time.
50+
51+
{% include image.html
52+
lightbox="true"
53+
file="/images/pipeline/pipeline-settings/auto-create-projects-setting.png"
54+
url="/images/pipeline/pipeline-settings/auto-create-projects-setting.png"
55+
alt="Auto-create projects for teams"
56+
caption="Auto-create projects for teams"
57+
max-width="60%"
58+
%}
59+
60+
###What does auto-create project do?
61+
When you create a team, the auto-create project option:
62+
* Creates a_project_ with the same name as the team, and a_tag_ for the project, also with the team name
63+
64+
{% include image.html
65+
lightbox="true"
66+
file="/images/pipeline/pipeline-settings/auto-create-project-results.png"
67+
url="/images/pipeline/pipeline-settings/auto-create-project-results.png"
68+
alt="Auto-created project with same name and tag as the team"
69+
caption="Auto-created project with same name and tag as the team"
70+
max-width="60%"
71+
%}
72+
73+
* Creates a_Project rule_ for the team with Read access to this project, and other projects with the same project tag
74+
75+
{% include image.html
76+
lightbox="true"
77+
file="/images/pipeline/pipeline-settings/auto-create-project-rule.png"
78+
url="/images/pipeline/pipeline-settings/auto-create-project-rule.png"
79+
alt="Auto-created rule for Project entity"
80+
caption="Auto-created rule for Project entity"
81+
max-width="60%"
82+
%}
83+
84+
* Creates a_Pipeline rule_ for the team, with all privileges, excluding Debug
85+
86+
{% include image.html
87+
lightbox="true"
88+
file="/images/pipeline/pipeline-settings/auto-create-project-pipeline-rule.png"
89+
url="/images/pipeline/pipeline-settings/auto-create-project-pipeline-rule.png"
90+
alt="Auto-created rule for Pipeline entity"
91+
caption="Auto-created rule for Pipeline entity"
92+
max-width="60%"
93+
%}
94+
95+
>Once created, there is no synchronization between the project and the team. Modifying or deleting the team has no impact on the project and its tags.
96+
97+
**What are the benefits?**
98+
As you can see, this option both simplifies and strengthens access-control:
99+
100+
* Use the Project rule automatically created for the team to grant access to additional projects simply by assigning the same tag to the other projects.
101+
* Avoids the need to create rules per pipeline for the same project. The Pipeline rule automatically created for the team, automatically grants the same permissions to all pipelines in the same project. New pipelines in the project automatically inherit these permissions.
102+
* Easily grant the same permissions to other teams for the same pipelines by creating Pipeline rules for the teams with the same project tags.
103+
104+
46105
##Enabling cluster-contexts for pipelines
47106
By default, all pipelines in the account can access all clusters integrated with Codefresh. Restrict pipeline access to clusters by enabling cluster-injection for individual pipelines in the account.
48107

@@ -67,14 +126,7 @@ max-width="60%"
67126
You can then select specific clusters for individual pipelines, through the**Kubernetes cluster** option in the[Pipeline's Policies section]({{site.baseurl}}/docs/pipelines/pipelines/#policies).
68127

69128

70-
##Template section
71-
72-
Here you can define global template behavior. The options are:
73-
74-
* Enable[pipeline templates]({{site.baseurl}}/docs/pipelines/pipelines/#using-pipeline-templates) for users. If this is enabled some pipelines can be marked as templates and users can still select them when creating a new pipeline.
75-
* Decide if users can clone an existing pipeline (along with its triggers and associated parameters) when[creating a new pipeline]({{site.baseurl}}/docs/pipelines/pipelines/#creating-a-pipeline).
76129

77-
Note that templates are simply normal pipelines “marked” as a template. There is no technical difference between templates and actual pipelines.
78130

79131
##Pipeline YAML section
80132

@@ -122,7 +174,7 @@ Here you can set the defaults for advanced pipeline behavior. The options are:
122174

123175
Note that the first option affects pipeline resources and/or billing in the case of SaaS pricing. It will also affect users of existing pipelines that depend on this behavior. It is best to enable/disable this option only once at the beginning.
124176

125-
##DefaultBehavior forBuild Step
177+
##Defaultbehavior forbuild step
126178

127179
Here you can decide if the build step will push images or not according to your organization’s needs. The options are:
128180

‎_docs/pipelines/triggers/git-triggers.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -182,8 +182,7 @@ The *modified files* field is a very powerful Codefresh feature that allows you
182182
files affected by a commit are in a specific folder (or match a specific naming pattern). This means that
183183
you can have a big GIT repository with multiple projects and build only the parts that actually change.
184184

185-
>Currently the field*modified files* is available only for GitHub, GitLab, Azure DevOps and[Bitbucket Server and Data Center](https://confluence.atlassian.com/bitbucketserver/manage-webhooks-938025878.html){:target="\_blank"} repositories, since they are the only GIT providers
186-
that send this information in the webhook. We will support other GIT providers as soon as they add the respective feature.
185+
>Currently the field*modified files* is available only for GitHub, GitLab, Azure DevOps, Bitbucket Server and Bitbucket (Cloud) repositories. We will support other Git providers as soon as they add the respective feature.
187186
188187
###Using the Modified files field to constrain triggers to specific folder/files
189188

‎_docs/quick-start/gitops-quick-start/create-github-action-ci.md‎

Lines changed: 0 additions & 6 deletions
This file was deleted.
146 KB
Loading
146 KB
Loading
147 KB
Loading
61.2 KB
Loading

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp