2024-07-23

Zadig Launches on Lark's Official Market: Advanced Organization, Efficient Collaboration Solution

Advanced Teams, Smart R&D Leading Solution!

Advanced Teams, Start with Feishu! As the new generation of efficient collaboration tools, using Feishu has become the work style of advanced teams.

Get It Right, and Everything Falls into Place! Zadig, a DevOps platform built on cloud-native technology and engineering best practices, is now officially available on Feishu: truly connecting the entire lifecycle from demand to release, providing enterprises with a one-stop efficient collaboration solution for product and R&D.

What magical effects does the combination of Zadig and Feishu, representing advanced productivity, bring?

# Zadig x Feishu: Integrated Product, R&D, and Operations Solution

Zadig integrates with Feishu's project management, approval, IM notifications, bots, and other collaboration tools, deeply merging to make product and R&D collaboration smoother and more efficient in the following four scenarios:

Demand Management: Reduce demand management costs, clarify demand progress, and facilitate product version planning.
Development and Self-Testing: Through a stable test environment and automated workflows, reduce manual operations, lower R&D costs, and improve delivery efficiency.
Test Integration and Validation: Embrace the test-driven development philosophy, shift the testing process forward, detect issues early, reduce communication and repair costs, and achieve safe, reliable, and efficient business changes.
Operations and Production Release: Automate the execution of R&D release standards, enhance management and collaboration efficiency, and reduce the probability of human errors.

# Scenario 1: Demand Management

In traditional document management methods, demands are disorganized, progress is unclear, and scheduling is difficult and opaque. The project view in Feishu can visualize the demand process, making progress clear at a glance; it supports key metrics to drive continuous organizational iteration.

# Scenario 2: Development and Self-Testing

R&D engineers face the following pain points during self-testing and joint debugging:

Manually deploying new versions to the development environment is cumbersome and error-prone. Diagnosing issues is difficult, and demand delivery efficiency is low.
Multiple people sharing a self-test environment leads to frequent resource conflicts; environmental changes are not transparent and cannot be traced, making smooth team collaboration challenging.

Zadig provides flexible and easy-to-use high-concurrency workflows, enabling multiple microservices to be built, deployed, and tested in parallel, thus improving code verification efficiency. It can quickly set up several independent development environments, with transparent and traceable environment operation records. It supports Feishu project triggers and IM notifications, automatically updating the status of Feishu work items after workflow tasks are completed and promptly pushing environment update information to achieve efficient collaboration.

# Scenario 3: Test Integration and Validation

Test engineers face the following pain points in team collaboration:

Multiple members sharing a test environment can only test a fixed version, making it impossible to verify multiple features in parallel, thus reducing the efficiency of functional verification.
Test case management is difficult, and the credibility of locally executed tests is questioned, making it hard to demonstrate the value of automated testing.
Test results are communicated verbally, leading to fragmented communication within the team and difficulty in tracing information.

Zadig supports setting up multiple independent verification environments with controllable service versions, enabling parallel verification. The automated test execution process is transparent and traceable, and when combined with workflow test result feedback, it shifts testing forward and empowers development. When the status of Feishu work items changes, the Zadig workflow is automatically triggered to achieve automated test processes and reduce communication costs.

# Scenario 4: Operations and Production Release

Enterprises face the following pain points during production and release:

Automating production and release is challenging, and manual operations are labor-intensive.
Before release, a lot of time is spent manually sorting and summarizing release version information. Manual errors can lead to incomplete online versions and even serious production accidents.
Traditional release approval systems are lengthy and lack precision; there are discrepancies between the approval content and the actual release content, making version tracing difficult.

Zadig's release workflow can flexibly configure changes to Nacos/Apollo configurations and DMS/MySQL data, supporting various release strategies such as blue-green, canary, batched, and Istio, to achieve safe and reliable release management. It presents the state of the production environment through multi-cluster and multi-project perspectives, ensuring transparency, reliability, and traceability in the release process. At key nodes in the release process, it initiates change approval requests to the responsible person through the release workflow, allowing quick access to Zadig to review release details, reducing communication costs and minimizing information gaps.

# One More Thing: Agile Performance Dashboard

Zadig provides integrated support from demand to release, automatically collecting the entire process and result data of R&D delivery, and supports custom enterprise-level XOps agile performance dashboards to drive growth with data.