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

Commit1acae96

Browse files
authored
Update test reports with minio cloud storage settings (codefresh-io#363)
Added description for minio settings and image
1 parent0fba5d5 commit1acae96

File tree

2 files changed

+60
-7
lines changed

2 files changed

+60
-7
lines changed

‎_docs/testing/test-reports.md‎

Lines changed: 60 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,11 @@ toc: true
1010
Codefresh offers the capability to store your test results for every build and view them
1111
at any point in time.
1212

13-
Currently Codefresh supports the storage of test reports in[Google buckets](https://cloud.google.com/storage/docs/key-terms#buckets) or
14-
[S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html) or[Azure Storage](https://docs.microsoft.com/en-us/azure/storage/).
13+
Currently Codefresh supports the storage of test reports in:
14+
*[Google buckets](https://cloud.google.com/storage/docs/key-terms#buckets)
15+
*[S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html)
16+
*[Azure Storage](https://docs.microsoft.com/en-us/azure/storage/)
17+
*[MinIO objects](https://min.io/)
1518

1619
##Test report modes
1720

@@ -48,7 +51,7 @@ If you use the custom reporting mode, you can select any kind of tool that you w
4851
##Connecting your storage account
4952

5053
As a first step you need a cloud bucket to store your test results. You can use
51-
Google orAWSorAzure for this purpose. Codefresh will create subfolders in the bucket with names from every build id. It will then upload the reports for that build to the respective folder. Multiple pipelines can use the same bucket.
54+
Google,AWS, AzureorMinIO for this purpose. Codefresh will create subfolders in the bucket with names from every build id. It will then upload the reports for that build to the respective folder. Multiple pipelines can use the same bucket.
5255

5356
First go to your Account Configuration, by clicking on*Account Settings* on the left sidebar. On the first section called*Integrations* scroll down to*Cloud Storage*:
5457

@@ -93,7 +96,7 @@ For more information see the [official documentation](https://cloud.google.com/i
9396

9497
###Connecting an S3 bucket
9598

96-
For AWS, create an S3 bucket as explained in the documentation from the[GUI](https://docs.aws.amazon.com/quickstarts/latest/s3backup/step-1-create-bucket.html) or the[CLI](https://docs.aws.amazon.com/cli/latest/reference/s3api/create-bucket.html).Then once you have the Access and Secret keys,
99+
For AWS, create an S3 bucket as explained in the documentation, from the[GUI](https://docs.aws.amazon.com/quickstarts/latest/s3backup/step-1-create-bucket.html) or the[CLI](https://docs.aws.amazon.com/cli/latest/reference/s3api/create-bucket.html).Once you have the Access and Secret keys,
97100
enter an arbitrary name for your integration and fill the keys in the respective fields:
98101

99102
{% include
@@ -112,7 +115,7 @@ environment variable in your Codefresh pipeline as explained in the next section
112115
You can also
113116
use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/secret-storage/) (such as Kubernetes secrets) as values by clicking on the lock icon that appears next to field.
114117

115-
If you have already specified the resource field during secret definition the just enter on the text field the name of the secret directly, i.e.`my-secret-key`.
118+
If you have already specified the resource field during secret definition, just enter on the text field the name of the secret directly, i.e.`my-secret-key`.
116119
If you didn't include a resource name during secret creation then enter the full name in the field like`my-secret-resource@my-secret-key`.
117120

118121
###Connecting Azure storage
@@ -133,12 +136,62 @@ max-width="60%"
133136
Then click*Save* to apply settings. You will use the name of the integration as an
134137
environment variable in your Codefresh pipeline as explained in the next sections.
135138

136-
You can also
137-
use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/secret-storage/) (such as Kubernetes secrets) as values by clicking on the lock icon that appears next to field.
139+
You can also use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/secret-storage/) (such as Kubernetes secrets) as values by clicking on the lock icon that appears next to field.
138140

139141
If you have already specified the resource field during secret definition the just enter on the text field the name of the secret directly, i.e.`my-secret-key`.
140142
If you didn't include a resource name during secret creation then enter the full name in the field like`my-secret-resource@my-secret-key`.
141143

144+
###Connecting MinIO storage
145+
Before connecting to MinIO cloud storage, configure the MinIO server as described in the[official documentation](https://docs.min.io/docs/minio-quickstart-guide.html).
146+
147+
Once you get the Access and Secret keys, define the settings for MinIO cloud storage in your Codefresh account.
148+
149+
1. From the Add Cloud Storage dropdown, select**MinIO Cloud Storage**, and define the settings:
150+
{% include
151+
image.html
152+
lightbox="true"
153+
file="/images/pipeline/test-reports/cloud-storage-minio.png"
154+
url="/images/pipeline/test-reports/cloud-storage-minio.png"
155+
alt="MinIO cloud storage"
156+
caption="MinIO cloud storage"
157+
max-width="60%"
158+
%}
159+
160+
***NAME**: The name of the MinIO storage. Any name that is meaningful to you.
161+
***ENDPOINT**: The URL to the storage service object.
162+
***PORT**: Optional. The TCP/IP port number. If not defined, defaults to port`80` for HTTP, and`443` for HTTPS.
163+
***Minio Access Key**: The ID that uniquely identifies your account, similar to a user ID.
164+
***Secret Minio Key**: The password of your account.
165+
***Use SSL**: Select to enable secure HTTPS access. Not selected by default.
166+
167+
168+
See an example of the integration in a pipeline:
169+
```yaml
170+
version:"1.0"
171+
stages:
172+
-"clone"
173+
-"test"
174+
175+
steps:
176+
clone:
177+
title:"Cloning repository"
178+
type:"git-clone"
179+
repo:"https://github.com/vadim-kharin-codefresh/test/"
180+
revision:"master"
181+
stage:"clone"
182+
unit_test_reporting_step:
183+
title:Upload Mocha test reports
184+
image:codefresh/cf-docker-test-reporting
185+
working_directory:"${{clone}}"
186+
stage:"test"
187+
environment:
188+
-REPORT_DIR=mochawesome-report
189+
-REPORT_INDEX_FILE=mochawesome.html
190+
-BUCKET_NAME=codefresh-test-reporting
191+
-CF_STORAGE_INTEGRATION=minio
192+
-CF_BRANCH_TAG_NORMALIZED=test
193+
```
194+
142195
143196
## Producing Allure test reports from Codefresh pipelines
144197
121 KB
Loading

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp