Add Notes in Create Pipeline Using Jenkinsfile/Editing Panels-v3.1 #1296
Conversation
Signed-off-by: Felixnoo <felixliu@yunify.com>
ks-ci-bot
added
the
size/M
|
/assign @Sherlock113 Please review the updates I made in those two documents, thanks. |
|
@kubesphere/sig-devops Please help review the updates I made in this PR when you guys are available, thanks. |
|
|
||
| {{< notice note >}} | ||
|
|
||
| The **Sync Status** colume shows the synchronization result between KubeSphere and Jenkins, and you can see the icon of **Success** if the synchronization is successful. | ||
|
|
||
| {{</ notice >}} |
There was a problem hiding this comment.
Please hold on about this part. We're still under discussion about this. See also kubesphere/kubesphere#3639
There was a problem hiding this comment.
I'll remove this part in the PR.
|
|
||
| {{< notice note >}} | ||
|
|
||
| In KubeSphere v3.1, only pipeline creator, account with the role of admin in the project, or the account you specify will have the authority to continue or terminate the pipeline. |
There was a problem hiding this comment.
There're two cases here:
- First, anyone who can run this pipeline, then he can approve or reject it if there are no specific approvers
- Second, same as you described above
There was a problem hiding this comment.
Thanks for the comment and I made some changes in this commit.
Signed-off-by: Felixnoo <felixliu@yunify.com>
Signed-off-by: Felixnoo <felixliu@yunify.com>
|
/cc @LinuxSuRen I added new words about sync status in this commit. Please take a look when you are available, thanks. |
|
@LinuxSuRen Hi, do you have any comments about this pr? |
|
@LinuxSuRen Hi, please take a look at this PR when you are available. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Felixnoo, LinuxSuRen The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| @@ -302,6 +311,12 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n | |||
|
|
|||
|  | |||
|
|
|||
| {{< notice note >}} | |||
|
|
|||
| In KubeSphere v3.1, the account that can run the pipeline will be able to continue or terminate the pipeline if there is no approver specified. Moreover, pipeline creator, account with the role of admin in the project, or the account you specify will have the authority to continue or terminate the pipeline. | |||
There was a problem hiding this comment.
->
In KubeSphere v3.1, the account that can run a pipeline will be able to continue or terminate the pipeline if there is no reviewer specified. Pipeline creators, accounts with the role of admin in a project, or the account you specify will be able to continue or terminate a pipeline.
|
|
||
| {{< notice note >}} | ||
|
|
||
| On the **Pipelines** page, you can click the three dots on the right side of the pipeline and then select **Copy Pipeline** to create a copy of it. If you need to concurrently run multiple pipelines that don't contain multiple branches, you can select all of those pipelines and then click **Run** to run them in a batch. |
There was a problem hiding this comment.
select all of those pipelines
->
select all of these pipelines
| @@ -205,6 +205,13 @@ The account `project-admin` needs to be created in advance since it is the revie | |||
|
|
|||
|  | |||
|
|
|||
| {{< notice note >}} | |||
|
|
|||
| - You can click the three dots on the right side of the pipeline and then select **Copy Pipeline** to create a copy of it. If you need to concurrently run multiple pipelines that don't contain multiple branches, you can select all of those pipelines and then click **Run** to run them in a batch. | |||
There was a problem hiding this comment.
select all of those pipelines
->
select all of these pipelines
|
|
||
| {{< notice note >}} | ||
|
|
||
| In KubeSphere v3.1, the account that can run the pipeline will be able to continue or terminate the pipeline if there is no approver specified. Moreover, pipeline creator, account with the role of admin in the project, or the account you specify will have the authority to continue or terminate the pipeline. |
There was a problem hiding this comment.
->
In KubeSphere v3.1, the account that can run a pipeline will be able to continue or terminate the pipeline if there is no reviewer specified. Pipeline creators, accounts with the role of admin in the project, or the account you specify will be able to continue or terminate the pipeline.
Signed-off-by: Felixnoo <felixliu@yunify.com>
|
/lgtm |
Signed-off-by: Felixnoo felixliu@yunify.com