Releases: apache/incubator-devlake
v0.19.0-beta6
Bug Fixes
- [Jenkins] Fixes missing to show the full pipeline name when selecting the Data Scope for Jenkins: #6280
- [ConfigUI] Fixes can't edit scope config: #6005
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (Formerly referred to as 'ENCODE_KEY' in versions preceding v0.18.0). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.19.0-beta6
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.19.0-beta6
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.19.0-beta6
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.
v0.19.0-beta5
Bug Fixes
- [Dora] fixes pull request connected to failed deployment commit: #6224
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (Formerly referred to as 'ENCODE_KEY' in versions preceding v0.18.0). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.19.0-beta5
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.19.0-beta5
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.19.0-beta5
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.
v0.18.1-beta2
Bug Fixes
- [Dora] fixes pull request connected to failed deployment commit: #6224
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (Formerly referred to as 'ENCODE_KEY' in versions preceding v0.18.0). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.18.1-beta2
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.18.1-beta2
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.18.1-beta2
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.
v0.19.0-beta4
Bug Fixes
- [Jenkins] Fixes data scope problem: #6178
- [Webhook] Fixes a webhook to a blueprint with a large scope fails with nginx error 413: #6160
- [GitHub] Avoid skipped jobs counting as a successful production deployment: #5885
- [Jira] Fixes issue_relationship lost data: #6250
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (Formerly referred to as 'ENCODE_KEY' in versions preceding v0.18.0). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.19.0-beta4
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.19.0-beta4
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.19.0-beta4
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.
v0.19.0-beta3
Bug Fixes
- [Config-UI] Fixes existing config value will be missed when editing jira scope config: #6083
- [ZenTao] Fixes the started_date and completed_date fields in the sprints table have incorrect values: #6028
- [Gitlab] Fixes the raw data of gitlab pipeline detail is not collected: #6027
- [Gitlab] Fixes some projects can not show: #6161
- [Bamboo] Fixes incorrect url field in cicd_scopes table: #6081
- [Bamboo] Fixes the value duration_sec field is empty in cicd_tasks table: #6082
- [Bamboo] Fixes the value of the repo_url field is incorrect in the cicd_pipeline_commits table: #6083
- [Bamboo] Fixes cicd_pipelines.result is missing a state: #6083
- [Bamboo] Change the splicing of cicd_scopes.name and cicd_pipelines.name: #6106
- [Pagerduty] Fixes unable to collect incidents with API token: #6112
- [Sonarqube] Fixes error data too long for column file_metrics_key: #6150
- [Sonarqube] Fixes error data too long for column component: #6166
- [Helper] Fixes ScopeGenericHelper updates the wrong fields: #6083
- [GitExtractor] Fixes cloneGitRepo ended unexpectedly: reference delta not found: #6159
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (Formerly referred to as 'ENCODE_KEY' in versions preceding v0.18.0). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.19.0-beta3
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.19.0-beta3
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.19.0-beta3
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.
v0.19.0-beta2
Bug Fixes
- [Jenkins] connect test is ok, but cant collect jobs data: #6034
- [Gitlab] pipeline duration inconsistant: #5988
- [ZenTao] The issue_id in the issue_repo_commit table is incorrect: #6012
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (Formerly referred to as 'ENCODE_KEY' in versions preceding v0.18.0). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.19.0-beta2
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.19.0-beta2
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.19.0-beta2
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.
v0.18.1-beta1
Bug Fixes
- [Jenkins] connect test is ok, but cant collect jobs data: #6034
- [Gitlab] pipeline duration inconsistant: #5988
- [ZenTao] The issue_id in the issue_repo_commit table is incorrect: #6012
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (Formerly referred to as 'ENCODE_KEY' in versions preceding v0.18.0). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.18.1-beta1
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.18.1-beta1
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.18.1-beta1
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.
v0.19.0-beta1
New Features
- [PagerDuty] Add data source dashboard for PagerDuty: #5605
- [Config UI] Improve the ux of the sync frequency setting: #5382
- [Config UI] Allow Data Scope search when creating a Blueprint in the user flow: #5203
- [Config UI] Adding more info to the project list: #4654
- [Data Model] Modeling issue relations: #5688
- [Bamboo] Collect Bamboo deployments: #5381
- [Bamboo] Use Plan as the data scope of Bamboo CI: #5317
- [GitLab] Filter out the GitLab repos that users only have the Guest permission when setting data scope: #5104
Bug Fixes
- [Framework] Explicit manual migrations for Remote plugins: #5689
How to Upgrade
For docker-compose users, please update your docker-compose.yml file with the following image tags:
- apache/devlake:v0.19.0-beta1
- apache/devlake-dashboard:v0.19.0-beta1
- apache/devlake-config-ui:v0.19.0-beta1
For helm users, please follow our docs
v0.18.0
New Features
- [Config UI] Adds data scope to the connections section: #4760
- [Config UI] Combines data entities and transformation rules into a scope config, simplifying the configuration process: #5159
- [Config UI] Allows users to customize the Grafana URL on the sidebar of the Config UI for a personalized experience: #4121
- [Framework] Enables enrichment to be run independently without executing the entire blueprint, improving flexibility and efficiency: #4866
- [Framework] Supports project, blueprint, and scope deletion for better management of DevLake components: #4864
- [Data Schema] Supports multiple assignees for issues in the issue tracking domain: #4738 (Requires re-running the pipeline for correct data)
- [Data Schema] Adds an "original_status" field to the "pull_requests" table, using "status" to indicate standardized statuses: #4745 (Requires re-running the pipeline for correct data)
- [Data Schema] Provides a "calendar_months" table or view to simplify SQL queries for time-series metrics: #4747
- [Jira] Collects data in the Jira development panel: #4304
- [Zentao] Collects Zentao issue changelogs and issue_repo_commits: #5189 , #5190
- [GitHub] Enhances the capability of Github to allow multiple labels to match a single regular expression: #5079
Bug Fixes
- [Config UI] Fixes the readability and consistency of task names displayed on the status page: #5088
- [Data Schema] Fixes inconsistency in the data transformation logic to the DevLake domain layer, ensuring accurate and reliable data processing: #5193
Breaking Changes
- [Refactor] Renames "ENCODE_KEY" to "ENCRYPTION_SECRET" and makes the .env file readonly and optional: #5235
- [Grafana] Upgrades Grafana to the latest version, providing enhanced features and improvements: #5017 （Please note that the built-in Grafana has been replaced by the official Grafana dependency. Remember to delete the existing Grafana deployment before upgrading to avoid any errors.）
- [Config UI] Combines data entities and transformation rules into a scope config, simplifying the configuration process: #5159
- [Data Schema] Renames the table "finished_commits_diffs" to "_tool_refdiff_finished_commits_diffs": #5193
- [Framework] Enables enrichment to be run independently without executing the entire blueprint, improving flexibility and efficiency: #4866
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (previously known as "ENCODE_KEY"). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.18.0
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.18.0
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.18.0
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.
v0.18.0-beta9
Bug Fixes
- [Azure DevOps] Fixed Azure DevOps db connection fail. #5978
- [Azure DevOps] Fixed can't associate scope config. #5802
- [Config UI] Fixs error project name convert. #5976
- [ZenTao] Fixes completed_date and ended_date value logic are reversed. #5968
- [ZenTao] Fixes iteration data without "closed" status in sprints table. #5969
- [ZenTao] Fixes closed sprint's status in domain layer's sprints table. #5984
- [ZenTao] Fixes the board.url is incorrect. #5960
How to Upgrade
Please follow the steps below to upgrade Apache Incubator DevLake:
Important Note: This upgrade requires manual configuration for the "ENCRYPTION_SECRET" (Formerly referred to as 'ENCODE_KEY' in versions preceding v0.18.0). You can copy the value of your existing "ENCODE_KEY" and set it as the value for "ENCRYPTION_SECRET".
For Docker Compose and Kubernetes (k8s) Users:
- Update your docker-compose.yml or k8s-deploy.yaml file with the following image tags:
- devlake.docker.scarf.sh/apache/devlake:v0.18.0-beta9
- devlake.docker.scarf.sh/apache/devlake-dashboard:v0.18.0-beta9
- devlake.docker.scarf.sh/apache/devlake-config-ui:v0.18.0-beta9
- Set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY". Please refer to the documentation at Docker Compose Setup for detailed instructions based on your installation method.
For Helm Users:
- Follow the instructions provided in the documentation at Helm Setup.
- Ensure that you have set the value for "ENCRYPTION_SECRET" by copying the value of your existing "ENCODE_KEY".
Upgrade Notes:
For detailed upgrade instructions and further information, please refer to the documentation at Upgrade Guide.