v1.8.0 Release Notes

Zadig v1.8.0 was released on January 7, 2022.

# Feature List

Workflow

• Can select existing build scripts when creating new services
• Support using YAML files to configure workflow triggers
• Added service visibility toggle in workflow build deployment steps
• Build and test support specifying clusters and configuring corresponding scheduling policies
• Optimized list loading efficiency when selecting multiple code repositories and branches

Integration Environment

• Support configuring different image registries for integration environments
• System no longer automatically configures resource policies when deploying K8s YAML services

Delivery Center

• Version delivery supports Helm scenarios

System Settings

• Support AWS image registry ECR
• Cluster resources can specify project usage scope

Developer Center

• Execute workflow API supports generating Helm type versions/callback functionality/image distribution
• Get workflow task details API adds service, image, test overview and detailed report link information

Bugfix

• Fixed GitLab code source unable to select code repositories in Subgroups
• Fixed build hang issue caused by oversized single-line logs during build process
• Fixed Helm Chart scenario where image version rollback does not take effect
• Fixed Pull Request triggering test tasks not correctly using PR
• Fixed setting failure when user-defined roles and public roles have the same name
• Fixed occasional timeout issue when authorizing GitHub code source integration
• Fixed Jenkins build unable to run jobs
• Fixed inaccurate workflow deployment status in Helm scenarios
• Fixed 403 prompt when authorized users view build logs
• Fixed 400 error when previewing values file during environment update in Helm scenarios

# Version Upgrade Process

# Database Backup

If already in production use, be sure to backup the database before upgrading

1. Database backup commands:

• Backup MongoDB data

mongodump -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE -o FILE_PATH

• Backup MySQL data

mysqldump -h <HOST> -P <PORT> -u root -p user > user.sql
mysqldump -h <HOST> -P <PORT> -u root -p dex > dex.sql

2. Database restore commands:

• Restore MongoDB data

mongorestore -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE --drop FILE_PATH

• Restore MySQL data

# Execute the following in MySQL:
mysql> drop database user;
mysql> create database user;
mysql> drop database dex;
mysql> create database dex;
# Execute the following data recovery operations from command line:
mysql -h <HOST> -P <PORT> -u root -p user < user.sql
mysql -h <HOST> -P <PORT> -u root -p dex < dex.sql

# Upgrade Operations

1. If installed using All in One Installation Mode or Installation on Existing Kubernetes, both use scripts from Installation on Existing Kubernetes^New for upgrade, with the following considerations:

2. If installed using Helm Command Installation, execute the following steps to upgrade to v1.8.0:

   1. Get helm values from Zadig environment, execute the following command.

   helm get values <Release Name> -n <Zadig Namespace>  > zadig.yaml
   

   1
   

   Check the zadig.yaml file. If the file contains image information (i.e., tag:a.b.c), it needs to be manually deleted.

   2. Execute upgrade command according to installation method.

   Domain method:

   export NAMESPACE=<Zadig Installation NAMESPACE>
   
   helm repo update
   helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} --version=1.8.0
   

   1
   2
   3
   4
   

   IP + PORT method:

   Warning

   Please use a different port than when installing v1.7.0/v1.7.1 to upgrade v1.8.0 to avoid upgrade failure due to port occupation.

   export NAMESPACE=<Zadig Installation NAMESPACE>
   export PORT=<Any port between 30000-32767, different from initially used port>
   
   helm repo update
   helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} \
       --set gloo.gatewayProxies.gatewayProxy.service.httpNodePort=${PORT} --version=1.8.0
   

   1
   2
   3
   4
   5
   6
   

# (Optional) Post-Upgrade Operations

If external clusters were integrated in the Zadig system before upgrade, after upgrading to v1.8.0, you need to disconnect the external cluster connection and re-integrate it, otherwise the functionality of using that cluster for builds will be abnormal. For cluster integration, refer to: Cluster Management.