v3.2.0 Release Notes
Zadig v3.2.0 was released on November 1, 2024.
# Feature List
Iterative management
- Support process management
- Support iterative boards
- Support work item management
Workflow
- Workflow supports independent notification tasks
- Workflow tasks support code information delivery
- The manual execution phase of the workflow task allows system administrators to operate
- Workflow build task support references to other task service components
- Workflow deployment tasks support updating initcontainer images
- Workflow image distribution tasks support multi-region synchronization using cloud vendor image synchronization
- Workflow General Task Support Service Component Multitasking Execution
- Workflow universal task custom variables support dynamic variables
- Supports flexible adjustment of service deployment order when the workflow performs construction and deployment tasks
- Workflow Approver supports runtime input and from other approval tasks
- Workflow JIRA triggers support specified state changes
- Build logs support search
- Code scanning supports exporting files
- Code scanning and testing support email and webhook notifications
- Test HTML report embed CSS
Services and Environment
- Add mirror information to the list of the environment service history versions
- Support service tag management and business directory search service based on tags
- Helm environment service page keeps the current search results after refreshing
System settings and resource configuration
- Account system OAuth Integration Add user mobile attribute fields
- Workflow tasks performed on AWS clusters support IRSA authentication
Other Repairs and Optimizations
- Optimize the performance of the release plan list
- Optimize the workflow execution frame style
- Optimize workflow approval task style
- Fixed the issue where configuration filter variables are not effective when executing in deployment tasks
- Fixed the problem of truncation error reporting when executing Chinese name workflow tasks
- Fixed an error issue in adding preperties variables in Apollo task
- Fixed an issue where a project sets a user group affecting the permissions of other projects
- Fixed an issue where a service was not mirrored in the environment caused the created version to fail to list the service
- Fixed and analyzed the error status problem in Junit test report
- Fixed the issue that the selection of cluster resources is not effective when configuring cache resources
- Fixed the issue of workflow task variables citing Chinese names and the variable value was empty
- Fixed the problem that there was no Mask on the task sensitive information on the host
- Fixed the issue of Secret in the environment not being updated after modifying the image registry password
- Fixed an error issue when the Gerrit repository name is used by a newly created service.
- Fixed an issue where the code base cannot be updated in Git triggers
- Fixed an issue where multiple Git triggers cannot be triggered in a workflow at the same time
- Fixed the problem of not debugging workflow when there are special characters in task variables
# Business Change Statement
Task Cloning Logic Change
Zadig v3.2.0 version updates the workflow cloning task feature. If the workflow configuration changes, cloning of old tasks is no longer allowed to avoid the occurrence of cloning new processes by cloning tasks after the workflow configuration changes.
After upgrading v3.2.0, cloning is no longer supported by old tasks. The cloning function of the new task is not affected and can be used normally.
Database Version Upgrade
The built-in MongoDB version of Zadig v3.2.0 Chart has been upgraded. If you have used a built-in database before, to prevent data loss, it is recommended to replace it with an external database (MongoDB version 4.4+) before upgrading, or take measures to ensure data security on your own.
# Version Upgrade Process
Warning
If the MongoDB is deployed in Replica Set mode, please make sure that the system libraries such as admin/local/config/test are not used as Zadig's business library; if it is used, please manually migrate the data first. If the current system version is available < v3.1 please upgrade to v3.1 first. For the specific upgrade process, please refer to the v3.1 upgrade method , and then upgrade to v3.2.0
Please perform the corresponding upgrade process according to different installation methods:
- Install using script commands: Upgrade reference documentation
- Use Helm Command Installation: Upgrade Reference Document
- Official channel installation: Upgrade reference document
