In Erda 2.1 version, focusing on the main line of R&D full-process automation, we focused on releasing the features of R&D automation such as automatic synchronization of collaborative event information and automatic discovery and classification of pipelines. R&D automation is a large and complex content, and Erda products will be built around this goal and will steadily advance through multiple iterative versions.
Erda 2.2 version mainly focuses on the R&D workflow of events , focusing on the release of R&D mode custom configuration, branch temporary merge deployment, task-side R&D workflow, etc. A total of 31 features have been added and improved .
Aiming at the goal of visualization and automation of the entire R&D process, this version has taken a substantial "step". I very much hope to receive your expectations and suggestions for us in the process of using it. You are also welcome to actively participate in the construction of the Erda community. , together to help improve the R&D efficiency of enterprises!
Let's take a look at the highlights of this new version and meet with you~
Feature 1 Erda Gallery's new unified enterprise asset management platform is online
As the field of application software becomes more and more subdivided, the black-box problem of software purchased by various departments of the enterprise, use of IT assets, and self-developed similar software between departments has gradually evolved into a relatively common and difficult topic.
So how to make enterprise IT asset management simple? How to make the use of enterprise IT assets be governed by chaos? How to make software delivery from slow to fast?
This Erda 2.2 version brings you a brand new Gallery solution, which mainly helps enterprise users solve the following scenarios.
- Scenario 1: Efficient reuse of enterprise R&D applications to avoid repetitive car manufacturing. In terms of research and development results, relying on Erda's application/project product management features, the product version is released to the organization Gallery for sharing, and other members of the organization can use the product in the Gallery for one-click deployment and use, reducing repetitive car manufacturing and version management confusion The problem.
- Scenario 2: Project delivery is implemented efficiently. One-click download/installation from the Gallery In the project delivery and implementation stage, the project implementation and delivery students can easily access the corresponding version from the Gallery and quickly deploy on the customer project side, reducing a lot of inefficiencies in the delivery and R&D sides to determine the version. Collaboration also effectively guarantees the quality of delivery and deployment.
- Scenario 3: Unified management of enterprise IT assets The current application software field is becoming more and more finely divided, and the number of self-developed application software within the enterprise is also rising unconsciously. How to unified management and unified disclosure to internal members has become a comparison A major topic, Erda Gallery provides the function of automatic release based on the DevOps platform (manual release of outsourced software is not yet open) from the dimension of enterprise IT asset management, so that all employees of the enterprise can use all the applications of the enterprise in one place.
Highlight function 2 R&D workflow based on event collaboration is launched
How to improve the efficiency of software R&D is a big and complex problem. Users may not be able to solve the problem by stacking a bunch of DevOps tools. Of course, this is definitely not a problem of the tools. The tools are used in a standardized and efficient manner (usually referred to as best practices) And specification reproducibility is the crux of the matter.
In order to allow users to accumulate or replicate successful best practices on the DevOps platform to improve efficiency, Erda 2.2 brings you a task-based R&D workflow feature. I hope that through this workflow, developers can immerse themselves in code development. The project team The R&D model specification is supported by the platform, allowing users to complete it without perception. The specific features include the following:
- R&D Workflow—Configuration of R&D Mode Workflow. The user completes the custom R&D mode configuration through the branch strategy configuration and R&D workflow configuration (currently the mainstream R&D mode is: Gitflow or trunk development mode).
-
Branch strategy configuration: configure the branch list, and set the branch strategy where this branch comes from and where it needs to be merged
-
R&D workflow configuration: configure what branch is used for what, what product is generated, and what environment can it be deployed to
Configuration entry: DevOps platform -> project settings for specific projects
- The task side chooses to use workflow, and solves the problem of environment and resource conflicts by temporarily merging and deploying branches, so that task development students can complete the whole process of task development from code, deployment, self-test, and submission and merging based on tasks.
Other improvements
The improvement content mainly comes from your daily use feedback. We also hope that you will contact us if you have any questions in the future. The specific contents are as follows:
- [Collaboration] The interaction of the work order list is improved, supporting labels and custom status
- [Collaboration] Added explanatory text to the enterprise network closure set by the project to prevent users from not understanding the consultation
- [Collaboration] New fields such as restart times, creator, creation time, etc. are added to the defect field information, and the person responsible for the defect specifies automatic optimization.
- [Automated testing] Support module-level coverage statistics in unit test reports
- [Automated test] The name of the automated test scenario set supports case sensitivity
- [Artifacts] Optimize and enhance project artifact creation/deployment filters
- [Pipeline] The application pipeline performs standardized and unified interaction according to the usage scenarios
- [Pipeline] The pipeline details page supports sharing, making it more convenient to synchronize the information of the test or R&D students to troubleshoot problems.
- [Pipeline] Actions in the pipeline support disable management
- [Pipeline] Pipeline action supports oom error prompt
- [Pipeline] Execution record switching is supported in the pipeline details.
- [Pipeline] Pipeline log error report to avoid network jitter and avoid user misunderstanding
- [Pipeline] Supports the disclosure of deployment environment and deployer information in the pipeline notification
- [Deployment] The ability to deploy Precheck is enhanced, and the verification of repeated deployments is supported.
- [Deployment] The ability to deploy Precheck is enhanced to support the verification of image existence
- [Deployment] Dice.yml adds file format Precheck function
- [Deployment] Quick object switching is supported in the Runtime details page of the DevOps platform
- 【Performance】Platform slow SQL performance optimization
- [Performance] Optimize the performance of Tracing-related indicators in ES
- [Monitoring alarms] In the alarm rules, it is supported to enable the recovery notification by default.
- [Log] In the Runtime console, solve the problem that the log cannot be downloaded after downgrading
- [Log] Support current limit on the log collection end
- [Log] Optimize the Fluent-bit problem on the log collection end
- [tools] Support Erda deployment via new CRD
- [API Gateway] API Gateway supports callback authentication capability
- 【Environment】In the environment of the deployment center, the information supporting workflow configuration is effectively disclosed, which is convenient for users to use
- 【Internationalization】Optimization of product internationalization
Erda V2.2 Changelog: https://github.com/erda-project/erda/releases/tag/v2.2.0