This is an automated email from the ASF dual-hosted git repository. lynwee pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
commit 0df4681d585abc63648c6fa6e4e45dc108150881 Author: Startrekzky <[email protected]> AuthorDate: Fri Dec 29 18:31:48 2023 +0800 docs: update the imgur images to local images --- .../images/dora-circleci-screenshot-1.png | Bin 0 -> 215276 bytes .../images/dora-circleci-screenshot-2.png | Bin 0 -> 1019910 bytes docs/Configuration/images/dora-config-label.png | Bin 0 -> 4873 bytes docs/Configuration/images/dora-dashboard.png | Bin 0 -> 383845 bytes docs/Configuration/images/dora-intro.png | Bin 0 -> 732609 bytes docs/DORA.md | 10 +++++----- .../images/dora-circleci-screenshot-1.png | Bin 0 -> 215276 bytes .../images/dora-circleci-screenshot-2.png | Bin 0 -> 1019910 bytes .../Configuration/images/dora-config-label.png | Bin 0 -> 4873 bytes .../Configuration/images/dora-dashboard.png | Bin 0 -> 383845 bytes .../version-v0.20/Configuration/images/dora-intro.png | Bin 0 -> 732609 bytes versioned_docs/version-v0.20/DORA.md | 10 +++++----- 12 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/Configuration/images/dora-circleci-screenshot-1.png b/docs/Configuration/images/dora-circleci-screenshot-1.png new file mode 100644 index 0000000000..6bb1421493 Binary files /dev/null and b/docs/Configuration/images/dora-circleci-screenshot-1.png differ diff --git a/docs/Configuration/images/dora-circleci-screenshot-2.png b/docs/Configuration/images/dora-circleci-screenshot-2.png new file mode 100644 index 0000000000..c647b8eb0a Binary files /dev/null and b/docs/Configuration/images/dora-circleci-screenshot-2.png differ diff --git a/docs/Configuration/images/dora-config-label.png b/docs/Configuration/images/dora-config-label.png new file mode 100644 index 0000000000..97a32df117 Binary files /dev/null and b/docs/Configuration/images/dora-config-label.png differ diff --git a/docs/Configuration/images/dora-dashboard.png b/docs/Configuration/images/dora-dashboard.png new file mode 100644 index 0000000000..a6ece92c11 Binary files /dev/null and b/docs/Configuration/images/dora-dashboard.png differ diff --git a/docs/Configuration/images/dora-intro.png b/docs/Configuration/images/dora-intro.png new file mode 100644 index 0000000000..0f48c8f947 Binary files /dev/null and b/docs/Configuration/images/dora-intro.png differ diff --git a/docs/DORA.md b/docs/DORA.md index 58ed1ea2af..93d28450e0 100644 --- a/docs/DORA.md +++ b/docs/DORA.md @@ -25,7 +25,7 @@ Stability is composed of two core metrics: - [Median Time to Restore Service](./Metrics/MTTR.md): How long does it take the team to properly recover from a failure once it is identified? - [Change Failure Rate](./Metrics/CFR.md): How often are your deployments causing a failure? - + To make DORA even more actionable, there are well-established benchmarks to determine if you are performing at "Elite", "High", "Medium", or "Low" levels. Inside DevLake, you will find the benchmarking table available to assess and compare your own projects. @@ -44,7 +44,7 @@ DevLake measures DORA metrics at the [project level](Configuration/HowToOrganize - Create a DevLake project, and associate the data connections with the project. Collect data to see DORA metrics - **Report**: DevLake provides a built-in DORA dashboard and another dashboard to help you debug DORA. See an example screenshot below or check out our [live demo](https://grafana-lake.demo.devlake.io/grafana/d/qNo8_0M4z/dora?orgId=1). -  +  DevLake now supports Jenkins, GitHub Action, GitLab CI, BitBucket and Azure Pipelines as the data sources for `deployments`; Jira boards, GitHub issues, TAPD workspaces and Zentao issues as the sources for `incidents` data; Github/BitBucket/Azure/GitLab repos as the sources for `Pull Requests` and `Commits`. @@ -76,7 +76,7 @@ In the next section, we will demonstrate how to configure DevLake to implement D  - To make it simple, fields with the  label are DORA-related configurations for every data source. Via these fields, you can define what "incidents" and "deployments" are for each data source. + To make it simple, fields with the  label are DORA-related configurations for every data source. Via these fields, you can define what "incidents" and "deployments" are for each data source. This project uses Jira issue type `DORA Incident` as "incident". Please select the `DORA Incident` for the `Incident` field. Jira issues belonging to this type will be converted to 'INCIDENT' in DevLake. @@ -103,7 +103,7 @@ Using CircleCI as an example, we demonstrate how to actively push data to DevLak 2.3 Head to your CircleCI's pipelines page in a new tab. Find your deployment pipeline and click `Configuration File`. -  +  2.4 Paste the curl command to the `config.yml`. Change the key-values in the payload. See the full payload schema [here](./Plugins/webhook.md/#deployment). @@ -153,7 +153,7 @@ workflows: 2.5 Run the CircleCI pipeline. Visit DevLake's DB to check if the deployments have been successfully pushed to DevLake. The deployments will appear in table [cicd_deployments](DataModels/DevLakeDomainLayerSchema.md#cicd_deployments) and [cicd_deployment_commits](DataModels/DevLakeDomainLayerSchema.md#cicd_deployment_commits) in DevLake's database. -  +   diff --git a/versioned_docs/version-v0.20/Configuration/images/dora-circleci-screenshot-1.png b/versioned_docs/version-v0.20/Configuration/images/dora-circleci-screenshot-1.png new file mode 100644 index 0000000000..6bb1421493 Binary files /dev/null and b/versioned_docs/version-v0.20/Configuration/images/dora-circleci-screenshot-1.png differ diff --git a/versioned_docs/version-v0.20/Configuration/images/dora-circleci-screenshot-2.png b/versioned_docs/version-v0.20/Configuration/images/dora-circleci-screenshot-2.png new file mode 100644 index 0000000000..c647b8eb0a Binary files /dev/null and b/versioned_docs/version-v0.20/Configuration/images/dora-circleci-screenshot-2.png differ diff --git a/versioned_docs/version-v0.20/Configuration/images/dora-config-label.png b/versioned_docs/version-v0.20/Configuration/images/dora-config-label.png new file mode 100644 index 0000000000..97a32df117 Binary files /dev/null and b/versioned_docs/version-v0.20/Configuration/images/dora-config-label.png differ diff --git a/versioned_docs/version-v0.20/Configuration/images/dora-dashboard.png b/versioned_docs/version-v0.20/Configuration/images/dora-dashboard.png new file mode 100644 index 0000000000..a6ece92c11 Binary files /dev/null and b/versioned_docs/version-v0.20/Configuration/images/dora-dashboard.png differ diff --git a/versioned_docs/version-v0.20/Configuration/images/dora-intro.png b/versioned_docs/version-v0.20/Configuration/images/dora-intro.png new file mode 100644 index 0000000000..0f48c8f947 Binary files /dev/null and b/versioned_docs/version-v0.20/Configuration/images/dora-intro.png differ diff --git a/versioned_docs/version-v0.20/DORA.md b/versioned_docs/version-v0.20/DORA.md index 8161eca48a..35d08441e0 100644 --- a/versioned_docs/version-v0.20/DORA.md +++ b/versioned_docs/version-v0.20/DORA.md @@ -25,7 +25,7 @@ Stability is composed of two core metrics: - [Median Time to Restore Service](./Metrics/MTTR.md): How long does it take the team to properly recover from a failure once it is identified? - [Change Failure Rate](./Metrics/CFR.md): How often are your deployments causing a failure? - + To make DORA even more actionable, there are well-established benchmarks to determine if you are performing at "Elite", "High", "Medium", or "Low" levels. Inside DevLake, you will find the benchmarking table available to assess and compare your own projects. @@ -44,7 +44,7 @@ DevLake measures DORA metrics at the [project level](GettingStarted/HowToOrganiz - Create a DevLake project, and associate the data connections with the project. Collect data to see DORA metrics - **Report**: DevLake provides a built-in DORA dashboard and another dashboard to help you debug DORA. See an example screenshot below or check out our [live demo](https://grafana-lake.demo.devlake.io/grafana/d/qNo8_0M4z/dora?orgId=1). -  +  DevLake now supports Jenkins, GitHub Action, GitLab CI, BitBucket and Azure Pipelines as the data sources for `deployments`; Jira boards, GitHub issues, TAPD workspaces and Zentao issues as the sources for `incidents` data; Github/BitBucket/Azure/GitLab repos as the sources for `Pull Requests` and `Commits`. @@ -76,7 +76,7 @@ In the next section, we will demonstrate how to configure DevLake to implement D  - To make it simple, fields with the  label are DORA-related configurations for every data source. Via these fields, you can define what "incidents" and "deployments" are for each data source. + To make it simple, fields with the  label are DORA-related configurations for every data source. Via these fields, you can define what "incidents" and "deployments" are for each data source. This project uses Jira issue type `DORA Incident` as "incident". Please select the `DORA Incident` for the `Incident` field. Jira issues belonging to this type will be converted to 'INCIDENT' in DevLake. @@ -103,7 +103,7 @@ Using CircleCI as an example, we demonstrate how to actively push data to DevLak 2.3 Head to your CircleCI's pipelines page in a new tab. Find your deployment pipeline and click `Configuration File`. -  +  2.4 Paste the curl command to the `config.yml`. Change the key-values in the payload. See the full payload schema [here](./Plugins/webhook.md/#deployment). @@ -153,7 +153,7 @@ workflows: 2.5 Run the CircleCI pipeline. Visit DevLake's DB to check if the deployments have been successfully pushed to DevLake. The deployments will appear in table [cicd_deployments](DataModels/DevLakeDomainLayerSchema.md#cicd_deployments) and [cicd_deployment_commits](DataModels/DevLakeDomainLayerSchema.md#cicd_deployment_commits) in DevLake's database. -  +  
