Erda v2.2.0 has been released.🎉 Welcome to use and feedback.

New Features

• [DevOps] Task R&D workflow

  • Support branch policy custom configuration and R&D mode configuration save, best practices for R&D mode based on feature branch with built-in Gitflow one erda.
  • The developer worked based on the task. Through the code submission, construction and deployment in the task workflow, the developer were truly immersed in task-based development.

• [DevOps] Support for temporary merging of feature branches, different branches of the same application can be deployed and tested in the same environment.

• [Gallery] New application Gallery

  • Based on the Actions and Addons, Gallery supports the release of products of projects/applications within the organization.

Improvements

• [Collaboration] Optimized worklist interaction, support for labels and custom states
• [Collaboration] Added the description of Deployment Blocking in project settings
• [Collaboration] Fields such as reopening times, creator and creation time are added to defect field information
• [QA] The reports of unit test support module-level coverage statistics
• [QA] The automated test scenario set name is case-sensitive
• [Artifact] Optimize project artifact creation/deployment filters
• [Pipeline] Application pipeline standardizes unified interaction according to application scenarios
• [Pipeline] The assembly line details page supports sharing
• [Pipeline] Action supports disable management and OOM promption
• [Pipeline] Supported execution record switching on the details page
• [Pipeline] Avoid pipeline log errors caused by network jitter
• [Deployment] Optimized pre-check, support check repeat deploy and image verification
• [Deployment] Supported Dice.yml format verification
• [Deployment] Supported switching between applications among Runtime pages
• [Deployment] The deployment center supported information about the workflow configuration
• [Performance] Optimization slow SQL
• [Performance] Optimization of ES Tracing related indicators performance problems
• [Monitor alert] Recovery notification is enabled by default for alarm rules
• [Log] Resolved logs cannot be downloaded after being degraded
• [Log] Supports traffic limiting on the log collection
• [Internaltional] Optimized platform i18n

Erda v2.1.0 has been released.🎉 Welcome to use and feedback.

New Features

• [Collaboration] Automate the workflow of collaboration issues
  • The task automatically turns to in progress when an MR is associated
  • The requirement automatically turns to in progress when any issue in its todo list is in progress
• [Collaboration] Improve the operational experience and information synchronization of issues
  • Support quick editing of status and other attributes in the todo list, with iteration information revealed
  • Synchronize changes to issues in the todo list in a semi-automated way after the requirement iteration or label changes, by giving a prompt to users
    
• [Collaboration] Support issue statistics on the iteration details page
• [Collaboration] The deadline of all issues in the iteration cannot be empty, otherwise, the system will automatically assign a value
  • Rule: If the start date of the iteration is later than the current date, the system will automatically set the start date as the issue deadline, otherwise, the current date is the deadline
  • Purpose: To let members make plans at an earlier stage of the iteration or of the current day, and to arrange issues reasonably
• [Collaboration] Support new interaction of issue details
• [Artifact] Enhance project artifact capabilities with one project artifact adapting to multiple deployment scenarios
• [Artifact] Support viewing addon information in the project artifact details
• [Artifact] Support label management for artifacts
• [Pipeline] Support classification management of pipelines (the platform provides built-in classification configuration now and custom configuration is coming soon), allowing pipeline creation with one click if a pipeline file is found in the code repository
• [Pipeline] Enhance the configuration capacity of project-level pipelines with pipeline parameter configuration and management supported
• [Deployment] Support job types in project artifacts
• [Deployment] Support addon addition or reuse according to the environment, reducing the maintenance cost of addons
• [Microservice observation and governance] Support cross-environment migration of custom dashboards by importing and exporting
• [Stability] Support configuration of container emptyDir and temporary storage available capacity in dice.yml

Improvements

• [Collaboration] Support quick switching to other iterations on the iteration details page
• [Collaboration] Optimize the categorization and sorting of filter criteria, to put commonly used fields on the left and person and date on the right
• [Collaboration] Remove the milestone
• [Artifact] Enhance the application filtering features when creating project artifacts
• [Pipeline] Optimize the pipeline details page to show the latest execution record after clicking
• [Pipeline] Optimize the default compensation mechanism for pipeline periodic scheduling, which is to stop according to the final status
• [Pipeline] Optimize the project pipeline page performance
• [Personal workbench] Improve the page loading performance
• [Microservice observation and governance] Connect the whole link from error calls in topology to traces and logs

Erda v2.0 is officially released with the following features: totally new visual interaction to optimize user experience deeply; new project-level R&D process to support project-level pipelines, artifacts and deployments based on CI/CD of a single application, making product development and delivery easier and more elegant.

Full Changelog

New Features

• Support new UI and optimize the user experience. #2443
• Optimize the path for new users by adding a landing page and project home page. #2567
• Support new R&D process with features of project-level pipeline, artifact and environmental deployment.
• Improve CLI tools with project initialization and code push supported.
• Support project-level artifact management and batch deployment. #4025 #4034
• Support artifact display in time order. #2843 #3813 #3941 #4150
• Support display of source file information in the pipeline list. #2998 #4135
• Support issue management in merge requests. #2965 #4094
• Support new service monitoring with features of tracing query, resource monitoring and call monitoring. #2363 #2478 #2556 #2586
• Support new front-end monitoring overview. #2597
• Support new alarm center. #3995
• Support new filter. #2825
• Support new menu layout for applications. #2941
• Optimize artifact upload and audit. #2519
• Enhance security with traffic limit of file download interface. #4089
• Use protobuf in artifact management. #3708 #4117

Bug Fixes

• (71416) [Deployment] Cross-cluster deployment is not supported for artifacts. #1999 #2031
• (263463) Format error in project collaboration (1440px screen) #3974
• (269792) Cache information not updated when the edge cluster is added again. #3773
• (273037) When adding a new issue, the custom field is unavailable and the issue cannot be saved. #2862
• (279349) [Org Center] Incorrect member statistics in the project list. #4015
• (281291) Failed to view the password of MySQL addon account. #4193 #4196
• (282043) Failed to add automated test scenes. #4024
• (282456) No import and export records in automated testing. #4038
• (283363) Format error of add members. #2932
• (283444) [Automated Testing] Option list error when adding parameters in a new interface. #4096
• (283630) [Service Monitoring] Failed to query call transactions in call monitoring. #4093
• (283708) [Member Management in MSP Projects] An error occurs when adding or editing interface through the platform. #4167
• (284418) [Quality Report] Failed to view code defect, code vulnerability or code smell. #2963
• (284431) Adjust the link from registration center to runtime. #2963
• (284437) Adjust the link from domain name in cloud management platform to runtime details. #2963
• (284608) [Issue List] Failed to submit comments or close the issue. #2973
• (284629) An error occurs when clicking commits in a new application. #2975
• (285083) [Automated Testing] Debug error of a single interface. #4105
• (285086) [Automated testing] Tab error of configuration information in test scenes. #4109
• (286927) Infinite loop of the code coverage interface. #3007
• (287968) Action name display exception. #4183
• (288276) [Configuration Center] The number of total items is incorrect. #224
• (288943) [Alarm] An error occurs if add phone in notification method when editing custom alarm rules. #4223
• (289017) Failed to run the pipeline with buildpack and java actions included. #374

Erda v1.5 is officially released with a total of 202 new features and improvements, such as Gantt chart, a powerful tool for task planning in project management, and efficiency measure of requirements and tasks, allowing you to have a clearer picture of the progress and risks of iteration. For microservice governance, Erda supports new topology for services and flame graph for tracing analysis, making it easier for you to understand the overall service architecture of the product with cool visual effects. For more information, please get the latest version and gain new experiences of Erda. Thanks again to each of you who contributes to Erda. We will pay attention to and adopt suggestions from the community continuously, to promote the further development of Erda. Look forward to hearing from you! ​

Exciting New Features 🎉

The following will introduce some key features of the new version in details.

1. R&D efficiency measure - Requirement and task analysis

Based on the efficiency measure of version 1.4, the new version supports requirement and task analysis, to help you analyze progress, risks and issue workflow via burn down chart and cumulative flow diagram.The burn down chart shows the possible problems of your team by iteration filtering. Through the chart exception or deviation from the ideal curve, you can see problems such as progress ahead or behind, task overloaded or unsaturated, requirement granularity too low, task estimated inaccurately, requirement changes and progress updated untimely.

Path: DevOps platform > (Select project) > Projects > Efficiency measure

The cumulative flow diagram helps you view and analyze the cycle time, throughput rate and predicted release date of iterations of requirements and tasks in each workflow status.

2. Project plan management - Gantt chart

In project management, it is essential to make plans, manage task distribution and follow tasks. For this reason, Erda supports Gantt chart in this version, which allows team managers to have a global view on task distribution, allocate and manage tasks reasonably, and view the cost of each issue clearly, and team members to view the distribution and due status of their tasks conveniently. In addition, the chart shows the progress and risks of tasks that may affect others, and tells the reason why some tasks are delayed.

Path: DevOps platform > (Select project) > Projects > Project collaboration

3. Microservice governance - New topology

Erda supports a new topology of services and dependencies on the microservice platform. The platform automatically discovers and analyzes the upstream and downstream dependencies of services, and generates a service topology, making it easier for you to understand the overall service architecture of the product, and query service performance bottlenecks, error hotspots, and abnormal service dependencies.

Path: Microservice platform > (Select project) > Topology

4. Tracing analysis - Flame graph

The flame graph is created by Brendan Gregg, an expert in computing performance. Unlike other profiling methods, the flame graph takes a global view of time distribution, listing all call stacks that can lead to performance bottlenecks.Through the flame graph, you can clearly see where the performance resources are consumed, thus find out the performance bottlenecks of the application for further optimization. Erda also supports flame graph on the microservice platform now, to make tracing analysis visualized and more efficient.

5. System notification - DingTalk notification

Instant messaging apps have become an important way of communication in daily work, and traditional notification methods such as SMS and email cannot meet the demands of system notification. Therefore, Erda supports notification channel management of DingTalk. When an alarm is triggered or followed issue changes such as status updated or remark added, it will push a DingTalk notification to you timely to keep you updated.

Path: Org center > Settings > Notification channel

Full Changelog

New Features

• (228759) [Monitoring] Support new visual topology in microservice governance. #2229 #2256
• (230877) [Efficiency measure] Support efficiency measure of requirements and tasks. #3313 #3365 #3378
• (238380) [Collaboration] Support Gantt chart for project management. #3259
• (251153) [Monitoring] Support flame graph in tracing details. #2085
• (222543) [Testing] Support management of test space status and basic information. #2758
• (222561) [Testing] Support new label, reference, enable/disable, copy and parallel orchestration for test scene set. #266 #2453 #2989
• (224168) [Monitoring] Support trace/error and log data storage via ES. #60 #2633
• (231090) [Monitoring] Support alarm notification in levels and by SMS. #59 #2378
• (261239) [Notification] Support notification channels of phone and email. #2219
• (232241) [Notification] Support notification of DingTalk message. #3129
• (240364) Support viewing logs of Spark jobs. #3275
• (247411) [Cloud management] Add container resource menu. #1983
• (251136) [Monitoring] Support new homepage for the microservice platform. #3154
• (251135) [Monitoring] Adjust microservice platform menu. #3093
• (251137) [Monitoring] Support new service list and topology in service monitoring. #3336 #2388
• (252051) [Collaboration] Support new visual design for issues. #134 #2209
• (263984) Optimize structure of the project collaboration page. #141 #142 #143 #144 #3394 #3401 #3404 #3405
• (264027) Support buildlkitd instead of dockerd for erda packaging and building.
• (264280) Optimize progress percentage statistics of requirements. #3360
• (267570) Support scalable card component. #2341

​

Bug Fixes

• (204238) The UI release takes too long. #1220
• (205361) The dashboard can be saved when the required chart type is not selected. #1952
• (209158) The release action in pipeline failed to report metadata. #3043
• (209165) [Addon] It is not checked whether there is an addon in the project to be deleted. #1615 #3419 #3450
• (210151) [Automated testing] If the interface is configured with a loop, the loop strategy should be expanded and displayed by default. #3020
• (222146) Pipeline cache conflicts. #3318
• (223455) [Automated testing] After turning the page and editing an execution plan, the page reloads and turns to the first page. #3137
• (226938) The time fields are incomplete in the exported Excel file of project collaboration, such as closed time. #2882
• (227823) The error message that occurs when relating repeated issues is unclear. #2990
• (228378) The timeout configuration is unavailable as there is no timeout input field in the action of test plan. #3125
• (231292) The support account only has permissions of audit log in the org center. #2159
• (234806) [DOP] When referencing test cases in manual testing, selecting all only works with cases on the current page. #1984
• (237839) [Automated testing] The orchestration relationship of parallel orchestrated interfaces or scene sets cannot be viewed in the execution details. #2892
• (240758) [Deployments] An extra runtime card appears in the deployments when updating deployment via artifact. #3340
• (246603) The pipeline execution details do not match the selected branch. #2051
• (246738) Parameter details requires interaction optimization. #2161
• (247460) The test plan cannot be filtered by iteration. #1957 #3140
• (247463) The plan name column is too narrow to see full information. #3032
• (247656) The environment order is inconsistent on different pages. #1968
• (248026) [Manual testing] The test cases under test subset loads incorrectly. #3076 #3099
• (248120) The scaled out value of the instance is inconsistent with the limit value displayed in monitoring. #2004
• (248127) The total number of interfaces, execution rate and pass rate are missed in the automated test case. #3041
• (248918) Project issue information displays in the personal dashboard though no project is joined. #3092
• (248931) The organization announcement information is not updated as organization changes. #2008
• (248966) [Log query] When entering the real-time tail page, the query conditions brought from the log query page should be bracketed. #172
• (248985) [Active monitoring] The URL cannot be modified when editing. #1986
• (249009) The percentage of used quota is wrong. #1997
• (249051) [Log query] On the real-time tail page, the label filter button should be displayed. #172
• (249116) Failed to import tasks with a 502 error. #3136
• (249137) [Pipeline] The pipeline gets a panic on erda cloud. #3126
• (249463) Failed to deploy across cluster. #266
• (249480) [Automated testing] The execution pass rate in test plan is not precise to decimals. #3065
• (249529) [Alarm] The alarm level in alarm rules and notification objects is incorrect after the old data is upgraded. #2001
• (249553) [Alarm] Enter the alarm list page, edit the alarm rule for the first time, and the value field of the filter rule cannot be edited. #2001
• (249566) [Notification Channel] When adding a notification channel, the AccessKeyId and AccessKeySecret fields have default values. #2001
• (249626) [Test space] Failed to query when data exceeds one page. #3064
• (249629) [Test space] There are two scroll bars on the page. #2018
• (249666) Unable to view logs on V1.3. #3416
• (249684) [Service analysis] After using ES to store trace/error and log data, the charts in the service overview show incorrectly. #2007
• (249688) [O&M dashboard] The data of old dashboard cannot show. #2007
• (249689) [Deployment log] After using ES to store trace/error and log data, the log of runtime deployment cannot show. #3073 #3077
• (249764) [Upgrade test] The audit information is incorrect when the quota is configured as 0 before upgrade. #3349
• (249796) [Alarm] Mobile phone is optional in the notification method of notification object in the alarm strategy. #2021
• (249887) There is a scroll bar on the project quota page. #2156
• (249894) The project name is displayed incompletely. #2154
• (249948) The search experience of the backend management requires optimization. #183
• (250216) [Alarm] When adding multiple notification groups in an alarm strategy, only the first one is displayed in the list. #2023
• (250275) [Alarm] The old custom alarm rules are not compatible. #3088
• (250388) [Alarm] It goes wrong when selecting all for comparison method in filter rules. #3102
• (250393) [Alarm] It goes wrong when selecting not match for comparison method in filter rules. #78 #86
• (250611) [Error analysis] No data on the error analysis page. #77
• (250655) [Project collaboration] The view mode of markdown requires adjustment. #2075
• (250657) [Notification channel] The creator field is displayed as the account in the notification channel list. #3216
• (250658) [Alarm] The page of adding a new alarm strategy shows incorrectly. #2050
• (250660) The page of adding a new dashboard shows incorrectly. #2048
• (250877) Failed to turn the page of project members. #2052
• (250883) [Test space] The dot color should change according to the test status. #3143
• (251601) The description and default value of the get parameter in API management are not displayed after release. #2078
• (251616) [Pipeline] The cron compensator still creates pipeline. #3119
• (252139) The interface execution rate and pass rate exceed 100% in the execution details of test plan. #3126
• (252476) After cancelling sorting order, the resources rank in descending. #2107
• (252574) Failed to switch to a joined organization as admin. #3182
• (252654) In Microservice Platform > Diagnose Analysis > Error Insight, the page of error details crashes. #2079
• (252901) Failed to execute the automated test case, but the execution result is empty. #3161
• (256203) [Alarm] Alarms are ignored as multiple notification methods are configured. #85
• (256222) [Execution plan] The added test plan is not displayed. #3165
• (256289) [Notification channel] The switching tab of notification channel switching requires improvement. #2112
• (256376) [Execution plan] Test scenes are not parallel. #3166
• (256434) [Microservice governance] The page title shows incorrectly on the microservice homepage. #2118
• (256435) The resource allocation rate and allocated in the cluster list are wrong. #3173
• (256437) Failed to go to the page of token management. #2116
• (256535) After switching organization, the cluster list shows the clusters of the previous organization. #3173
• (256550) The ascending and descending order of quota usage is reversed. #3173
• (256552) Failed to copy scenes to an empty scene set. #3170
• (256557) Only K8s clusters are watermarked in the cluster list. #2121
• (256579) [Microservice governance] The number of services in msp project is wrong on the microservice homepage. #3181
• (256635) [Execution plan] Failed to get the latest execution result when a scene is referenced by multiple scene sets. #3166
• (256636) No data in resource monitoring of pod details. #3169
• (256648) No data in resource monitoring when clicking node in the pod details to enter the node details page. #3174
• (256721) [Alarm] The original notification method of DingTalk should be changed to DingTalk group in custom alarm rules. #3177 #3195
• (256805) The name and value in the cluster list do not match. #3179
• (256807) The value of memory quota in the cluster list is wrong. #3179
• (256994) No data of resource statistics occasionally in the cluster list. #3184
• (257036) Failed to view container resources when switching to terminus-dev cluster. #3185
• (257042) [Microservice homepage] The number of services in the project shows 0. #3196
• (257182) An error occurs when editing scenes of automated testing. #3199
• (257257) [Test management] The statistics page requires performance optimization. #3222 #3230
• (257960) [Project collaboration] Performance optimization is required. #3208
• (257968) [Test report] Performance optimization is required. #3208
• (257975) The error message that occurs when deleting a project requires optimization. #3362
• (258142) [Application development] Performance optimization is required. #3256
• (258272) The statistics page is moved up automatically after filtering. #2167
• (258275) The statistics chart of automated testing shows wrong. #3233
• (258315) [Automated testing] Each loop result is printed when viewing the execution result of an interface with loop. #3270
• (259829) The automated test plan references a scene set. The referenced scene set executes successfully but the referencing scene set is failed. #3244
• (260508) An error occurs when saving the edited pipeline. #3262
• (260709) [Gantt chart] An error occurs when selecting multiple iterations. #2199
• (260722) [Gantt chart] The historical data lacks start time. #3289
• (260727) [Gantt chart] The tasks already included should be excluded. #3286
• (260744) [Gantt chart] Failed to click to view details of the included tasks. #2200
• (260745) [Gantt chart] The default iteration is wrong when there is no iteration in progress. #3284
• (260843) [Gantt chart] The page is slow with a lot of requirements. #2205
• (260845) [Gantt chart] Manual refresh is required after removing the relation. #2260
• (260939) [Gantt chart] An error occurs occasionally when viewing plans. #2202
• (260946) [Custom dashboard] The metrics group is unavailable when creating a new dashboard. #2204
• (261267) The Gantt chart date is inconsistent with that of issues. #2211
• (261274) The old data at 00:00 of Gantt chart needs to be fixed. #2211
• (261286) The Gantt chart filtering requires optimization. #3276
• (261331) The list of tasks included in the requirement does not show the status. #2231
• (261389) The UXD of Gantt chart requires optimization. #2269
• (261398) [Automated testing] No secondary confirmation when deleting scenes. #3277
• (261505) The iteration oder is not fixes in Gantt chart. #3282
• (261837) [Gantt chart] The filled in time is inconsistent with that of timeline. #2220
• (261852) The date is not displayed when the mouse hovers on Gantt chart. #2220
• (262206) The pod list in the DaemonSet details page shows incorrectly. #3290
• (262534) [Deployments] The domain name set for the service does not take effect. #3322 #3323
• (262586) [Automated testing] The button on the interface add/edit page is wrong. #2224
• (262614) The data of issue due today and tomorrow on the homepage is wrong. #3354
• (262679) [Automated test Platforming] Failed to view the configuration sheet log when executing a single test scene. #3304
• (263116) [Automated testing] The pagination in execution details is incorrect. #3371
• (263172) Failed to deploy API gateway in the testing environment. #3331
• (263196) Create a bug with one click in ticket, and the page crashes when clicking the related issues in bug details. #2236
• (263214) [Test environment] The admin cannot access the operation management platform. #2243
• (263260) [Service list] The error rate of the services in the list always shows 0. #3339
• (263281) [Service list] The average delay of service apm-demo-dubbo is inconsistent with that in topology. #2242
• (263293) The efficiency measure in test environment requires optimization. #2254
• (263359) [Topology] The page crashes after clicking the gateway node and external service node in the topology. #2244
• (263409) [Service list] An error occurs when entering the service list of a msp project. #2245
• (263474) [Automated testing] The interface execution takes 5 hours and the loop termination condition does not work. #3329
• (263572) The status not required in the process should not be displayed. #2255
• (263575) Icon is required for issue complexity. #2270
• (263634) dice.yml error leads to orchestrator panic. #3351
• (263635) [Gantt chart] Manual refresh is required after filtering by assignee. #3335
• (263765) [Gantt chart] The dragged date is incorrect. #2269
• (263766) The refresh button does not work on the project collaboration page. #2271
• (264118) [Service analysis] The data of RPC call is incorrect. #2279
• (264469) [Automated testing] The later interface cannot get the output parameters of the previous interface when executing the plan. #3402
• (264516) The addon oversold ratio is invalid in test environment. #3383
• (265589) [Microservice governance] The HTTP status chart of service node in the topology is incorrect. #3397
• (265590) [Gantt chart] An error occurs when dragging the date. #3390
• (265633) The environment variables are not injected when running workflow via SPRAK-OPERATOR. #3392
• (265656) [Topology] The number of unhealthy services and free services is wrong in topology analysis. #2297
• (265684) [Topology] MySQL and Redis nodes are not displayed in the topology. #3414
• (265721) [Topology] The HTTP status chart of services node details is not displayed completely with a certain number of status. #2297
• (265728) [Topology] The services in topology overview and topology analysis include external nodes. #2297
• (265844) The link in DingTalk notifications is incorrect. #3400
• (265949) The application cannot be scaled out. #3398
• (266007) The scroll bar style in test statistics is wrong. #2304
• (266027) The service list is empty when adding service instance for addon. #2305
• (266168) The organization member list requires optimization. #2343
• (266407) [Service list] The average throughput and average delay in the chart is inconsistent with that in the list. #3414 #3445
• (266408) [Service list] The services in the unhealthy service list are not filtered. #3414
• (266409) [Service monitoring] The abscissa axis time in the chart is incorrect when the query time is longer than one hour. #3414
• (266410) [Service list] The unhealthy services in the unhealthy service ranking is inconsistent with that in topology. #3414
• (266411) [Service list] An error occurs on the service list page. #3414
• (266412) [Service monitoring] The time unit in the slow response API and slow response SQL is unreasonable. #3414
• (266417) [Service monitoring] No unit for the response time. #2316
• (266446) [Filter] No profile photo in kanban. #3412
• (266447) [Project collaboration] An error occurs when turning page or refreshing list. #3413
• (266448) [Project collaboration] Add conditions to the custom filter conditions, the filter status turns to changed, but the added conditions are not displayed after clicking filter. #2320
• (266449) [Project collaboration] The filter conditions in the issue list cannot be displayed normally. #2321
• (266450) [Project collaboration] Add two filter items after selecting all, click cancel and open again, then the two items are still displayed. #2322
• (266452) [Project collaboration] No load more in kanban. #3412
• (266454) [Project collaboration] There are two scroll bars in kanban. #2323
• (266455) [Project collaboration] The kanban filter in iteration requires modification. #3412
• (266456) [Project collaboration] The delete icon (x) style requires adjustment. #2322
• (266458) [Project collaboration] The start date and end date cannot be the same in the kanban filter. #2327
• (266459) [Project collaboration] Severity should be changed to complexity in requirement filter. #3469
• (266460) [Project collaboration] Logic error of filter interval in kanban. #2327
• (266461) [Project collaboration] The filter cursor requires optimization. #2326
• (266463) [Project collaboration] The labels are not displayed completely. #2328
• (266466) [Service monitoring] The overview page shows incorrectly. #2336
• (266908) [Artifact management] No artifact displayed when quickly updating from artifacts. #2358
• (267323) [Service list] The page number of unhealthy services page and no traffic services page is incorrect. #3488
• (267696) [Org center] The project information page of msp projects is wrong. #2351
• (267958) [Monitoring] The page of notification channel and access configuration of msp projects does not respond. #3458
• (267968) [Microservice governance] An error occurs when returning to the microservice homepage from the service list page. #2363
• (267978) [Tracing] No data returned when querying by dubboMethod. #3490 #2405
• (267990) Assignee style error. #2362
• (268044) Click the related requirement or task but no issue is found. #2365
• (268052) The requirement deadline should change as its included task is removed. #3470
• (269998) Failed to change the issue status in the issue list. #3515

Erda v1.4.0 has been released.🎉 Welcome to use and feedback.

New Features

• Support parallel scene sets in automated testing. #2173
• Support scene set importing and exporting in automated testing. #2470
• Support step copying and pasting in automated testing. #2481
• Support step enabling and disabling in automated testing. #2453
• Accelerate the loading of manual test related pages. #2910
• Support issue dashboard with history data displayed in bar chart, pie chart, etc. #2294 #2462
• Support setting resource quotas according to the project's workspace granularity in the management center. #2283
• Support resource usage ranking of projects in the cloud management platform. #2525
• Support sending SMS alerts through custom notification channels in microservice and cloud management platforms. #2460
• Support Elasticsearch as a backend storage in the microservice platform. #2861
• Support automatically adding the .yml suffix to the file name when user creates a pipeline in the DevOps platform. #2685
• Support K8s versions below 1.16 in the Kubernetes dashboard of cloud management platform.#2852
• Support dynamic configuration search depth of git search interface in the DevOps platform.#2872
• Optimize the alarm trigger conditions and alarm expressions in the microservice platform. #2739
• Support service analysis of microservice&DevOps projects in the microservice platform.#2782 #2833

Bug Fixes

• Fix the bug that action will not automatically synchronize the latest version of GitHub. #2507
• Fix the bug that it is not checked whether there is a cycle in the scene set when it is moved. #2309
• Fix the bug that the execution action of automated test plan cannot monitor whether the plan is executed. #2407
• Fix the bug that the .yml suffix is not added when creating a pipeline. #2685
• Fix the bug of incorrect calculation of execution time of pipeline loop task. #2816
• Fix the bug that the pipeline with the same ID is scheduled repeatedly. #2921
• Fix the bug of slower requests as automated testing tasks apply for a large number of tokens. #2991
• Fix the bug that application deletion failed without returning an error message. #2613
• Fix the bug that add a unique index to the application table to avoid applications with the same name. #2611
• Optimize the audit message for org update. #2706
• Fix the bug that the parent context is recycled from which the child context gets data, causing the gittar component to panic. #2348
• Optimize the API statistics of automated testing. #2806
• Fix the bug that the execution details of the scene set in the automated testing cannot show the execution environment at the time. #2529
• Fix the bug that when click to retry pipeline timing tasks, the trigger time will not change. #2560
• Fix the bug that the imported scene set contains configuration sheet and an eoor occurs when click to view details. #2609
• Fix the bug that the status in the test space records of importing and exporting is inconsistent with that in the test space list. #2624
• Fix the bug that the execution time of steps in automated testing is 00:00. #2650
• Fix the bug that in case of multiple instances in the pipeline, the number quried by queue manager is inconsistent. #2742
• Fix the bug that branch variables are not injected in the pipeline. #2797
• Fix the bug of incorrect issue status. #2268
• Fix the bug of incorrect filtering result. #2504
• Fix the bug that an error occurs when the namespace does not have aliyun secret in scheduler. #2456
• Fix the bug that the filtering rules of custom alarm created in msp and cmp are incorrect. #2860
• Fix the bug that span of tracing is missing in the microservice platform. 2849, 2820
• Fix the bug that log index cache gets overwritten when multi esurls exist in Erda cluster. #2887
• Modify the git-push address of mobile template in the DevOps platform. #2808
• Fix the bug that pipeline does not reset the execution start time of the cyclic task in the DevOps platform. #2816
• Fix the bug that write data to etcd after handleServiceGroup function in scheduler. #2604
• Fix the bug that the execution of test plan leaves out archived plans in the DevOps platform. #2663
• Fix the bug that one of the tasks in the pipeline of automated testing may be in execution after canceling in the DevOps platform. #2684
• Fix the bug that the environment variables of container resource are not updated when scaling the service group in the DevOps platform. #2672
• Fix the bug that admin account queries all organizations in the DevOps platform. #2692

New Features

• The DevOps platform now supports code coverage dashboard & bugs dashboard.#2342
• Optimize HTTP active monitoring in the microservice platform #2377
• The scenario set of the automated test platform now supports parallel execution.#2412
• Optimize load speed of k8s dashboard's nodes list. #2355

Bug Fixes

• Fix the bug that batch cluster upgrade has wrong permission.#2308
• Fix the bug that cluster-agent module missing privileged param.#2367
• Fix the bug that there is no user information in the notification group of the microservice platform.#2393
• Fix the bug that start same k8s dashboard sever redundantly when watch multi clusters. #2366

Erda v1.3.0 has been released.🎉 Welcome to use and feedback.

New Features

• Cloud management module add k8s dashboard。#1542 #1585 #1703
• Add admin role and system-auditor role.#1031
• Projects collaborate with item creators and handlers to increase the ability to modify item types.#1347 #2090
• Adjust audit log max retention days to 180 days.#2142
• Support read all unread mbox with one click.#1593
• Add execute-time and pass-rate in autotest-plan table component.#1684
• Add audit for runtime deploy operate.#1653
• Add application filter in authorize modal.#1371
• Pipeline actions support multi containers monitor.#1585 #1777
• Improvement of the Api-Design module.#1632 #1575
• Improvment on security of gittar access.#1607 #1663
• Improvement on MicroService module, support opentracing integration.#1829
• MicroService module support member management.#1659
• Improvement on request-tracing feature.#1553
• Add inspection for MQ requests.#1676
• Improvement on Log Query, support AND, OR operator.#1960
• Add new log analytics addon.#1547
• Change log max lines limit to 5000.#1348

Bug Fixes

• Fix the bug that non-exist branch page loop request error.#1090
• Fix the bug that action form edit struct-array error.#1132
• Fix the bug that project-pipeline pageNo change error.#1211
• Fix the bug that node information arrangement style bug of clusters management nodes detail.#1322
• Fix the bug that scene sets would display Chinese in English mode.#1330
• Fix the issue that add default value for enumerated custom fields when quick create issue.#1351
• Fix the bug that Ellipsis tooltip error.#1353
• Fix the bug that api-design missing url params when click left menu.#1375
• Fix the issue that add placeholder for contractive-filter / adjust backlog filter item.#1384
• Fix the bugs of Form validation on the API design page and the display bug of the response params example.#1395
• Modify the error message returned。#1709
• Fix the issue that autotest step input param do not support '.'.#2065
• Fix the bug that menu of AppMonitor display error.#2077 #2084
• Fix the issue that get execute env from report env.#2088
• Modify micro_service dop role-list.#2135
• Support cms for pipeline with cron enabled.#1741

Refactor

• Refactor the uc component, support intergrate with kratos.#1460
• Fix single point problem of core components.
• Refactor the OpenApi，support declare grpc api expose to OpenApi.#1584
• Add etcd distributed lock.#1548
• Refactor api of the Hepa to grpc.#1744
• Gittar remove skipAuth.#1856
• Rename worker cluster tag.#2124

The release version v1.3.0 is coming soon!

You can use Erda to realize the Vision: Build any application, Deploy anywhere, Monitor anything!

Bug fixes / Improvements

• Fix the issue of table style for manual test case. #953
• Fix the bug that occured when switching the source type for the first time after resetting the form while adding tags. #957
• Fix the bug of regular expression of repository address field. #958
• Fix the issue of purple label without background color. #962
• Fix the bug that the empty page icon is not displayed when there is no branch on the API design page. #970
• Fix the bug of tracking details type.#975
• Fix the bug that cluster_name and application_id do not take effect when they exist in custom filter rules. #1459
• Fix the issue that the ES index of log analysis is not scrolling.#1464#1465
• Fix the issue of memory leak when getting the instance list.#1493
• Support getting the specified pod when obtaining the pod status list.#1495
• Support production scale deployment. #30
• Optimized Erda helm chart structure. #14
• Support configuration Erda and dependent high-availability parameter. #35

Erda v1.2.0 has been released.🎉 Welcome to use and feedback.

New Features

• Optimize overview and project list in MSP. #809
• Support sending test messages when configuring DingTalk notifications. #777
• Support importing and exporting automation test sets. #749
• Enable more features of multi-cloud management platform for free users. #759
• Optimize the way to add EDAS clusters. #750
• Optimize markdown editor interaction and style. #853
• Optimize pipeline log style. #802
• Optimize pipeline notification content. #1189
• Optimize the execution logic of automation test cases. #1103
• Support filtering test case executor by unassigned person in the test plan. #732
• Add precheck for front-end applicaiton packaging.

Bug Fixes

• Fix a bug of cluster parameter in the project pipeline. #737
• Fix the bug of data duplication in repo file comparison. #744
• Modify markdown editor style. #763
• Fix a bug of env parameter in the project pipeline. #765
• Fix the style issue when dragging and droppping Nusi component tree. #769
• Fix the error of operation key value in action form. #771
• Fix the mandatory verification error of custom labels in the form. #778
• Fix the button style issue of markdown editor. #782
• Fix the issue of yml editor add node disappearance and actionForm componentization data error. #781
• Fix the bug of the drop-down width when selecting artifact ID in deployment center.#827
• Add registration command and retry initialization operations for EDAS cluster. #840
• Fix the bug of extension service form in project. #863
• Fix the possible crash bug when adding members using nicknames with special characters. #862
• Fix the bug that projectId is missing in the request application list. #873
• Fix the bug that Git repositories can be cloned without account password.#877
• Fix the bug that the text prompt is incomplete caused by invalid form in trace debugging. #857
• Fix the data error of related issues after changing issue to backlog. #902
• Fix the bug that two scroll bars appear when scrolling the item in backlog table. #839
• Fix the API error reported after deleting files in repo. #910
• Fix the error occured when initializing pipeline action form. #912
• Fix some table issues: column width too long or insufficient, table exceeds the page and uniform overflow omission. #736
• Fix the style issue that the item name of extended query column is too long. #739
• Fix the bug that required fields in project collaboration are not marked as required.#746
• Add width to the table in OrgCenter > Projects. #755
• Fix the bug of style validation occured when adding issue in Issues > Backlog. #757
• Fix the bug that in Multi-Cloud Management Platform > Alarm Record, click a record for details, then all list items are expanded when clicking the expand button before the list items.#754
• Fix the bug that when editing issues, the month in datepicker cannot be changed.#761
• Increase the width of the member table. #767
• Fix the bug that the row representing the folder in the test case table shows an extra column for the interface pass rate. #768
• Increase the width of the test case table. #774
• Add a mouse-over style to tables with row click events. #766
• Adjust the width of the related issue table. #775
• Fix the loop refresh issue when the path is /-. #780
• Fix the bug that the left arrow faces wrongly when the tree on the left side of the test case is expanded, and the parent node occasionally collapses when the child node is clicked.#773
• Fix the bug that some rows in the test case table go beyond the right side. #790
• Fix the incorrect address of application repository in application settings. #797
• Fix the issue that the color of alert list icon is black. #808
• Fix the issue that error occured when editing custom addon of extended service. #812
• Fix the issue that the text field of trace debugging body is too long to see the tabs above. #820
• Fix the bug that logs cannot be downloaded when using the default duration. #842
• Fix the bug that the search box does not display when the data is empty. #906
• Migrate Affix and InputNumber from Nusi to Antd.#779
• Change the grouping rules to mandatory when creating custom alarm rules. #752
• Fix the issue that the setting of runtime rollback number does not take effect.

Refactor

The interfaces of msp and monitor modules are all defined by proto. Optimize Quick-Start for one-click deployment of Erda Standalone mode on the local machine. [#1242]https://github.com/erda-project/erda/pull/1242

The patched version v1.1.1 has been released and deployed on Erda.Cloud.

Bug Fixes

• EDAS and K8S use the same agent now. (#1277)
• Enable cloud management platform for free users. (#810)
• Fixed the issue that error occured when editing custom addon of extended service. (#813)

See the CHANGELOG for more details.

The release version v1.2.0 is coming soon!

You can use Erda to realize the Vision: Build any application, Deploy anywhere, Monitor anything!

Erda v1.1.0 has been released and deployed on Erda.Cloud.:tada: Welcome to use and feedback.

New Features

• Support existing clusters importing by users (#806)
• Support subscription to issue changes, to receive notifications timely when followed issue is modified (#451)
• Support asynchronous import and export of manual test cases (#380)
• Support auto page refresh for automated test plan (#446)
• Support bug closed time viewing and filtering (#445)
• Add project-level applications to realize rapid project migration (#350)
• Support page turning in Issues > Backlog (#395)
• Optimize clone address of code repository (#155)
• Optimize size of sliding window and description area for issue editing (#314)
• Support size adjusting for table pagination (#1031)
• Turn enter search to delayed auto search for personal dashboard (#324)
• Optimize the downloaded file name and suffix format of container log: service name_timestamp.log (#684)
• Upgrade logo (#688)

Bug Fixes

• Safari page crashes when access Code Repository > Commit History (#384)
• The list order remains unchanged after viewing MR (#661)
• The certificate file is uploaded but its name is not displayed (#639)
• Canceling the edit of merge request will clear the comparison result (#638)
• Failed to download files in code repository (#588)
• The pipeline node shows the previously failed error (#422)
• Members will automatically log out if exit the organization (#347)

Refactor

• Split out new platform services of dop, msp, cmp and ecp.
  • dop (#392)
  • msp (#407)
  • cmp (#416)
  • ecp (#419)
• Remove components of qa, apim, cmdb, ops and tmc
• Add core components of cluster manager
• Add cluster-dialer instead of soldier to handle inter-cluster communication
• Add a new way to define an interface using protobuf protocol, and the msp component has been migrated

See the CHANGELOG for more details.

The release version v1.1.0 is coming soon!

You can use Erda to realize the Vision: Build any application, Deploy anywhere, Monitor anything!

See the CHANGELOG for more details.

The patched version v1.0.1 has been released and deployed on Erda.Cloud.

It provides some new features, such as:

• Support individuals to create organization if he/she doesn't belong to any organizations
• Support scaling application without restarting the existing instances

See the CHANGELOG for more details.

Erda v1.0.0 is released!

Start your Erda journey in two ways:

• Quick start in your local machine
• Install with K8s

The first release version v1.0.0 is coming soon!

You can use Erda to realize the Vision: Build any application, Deploy anywhere, Monitor anything!