Continuous Component Construction

For application developers, in the past, our main development and debugging method was local. This mode has many problems in complex collaboration scenarios and complex application architecture scenarios, resulting in low efficiency. The Kato-based application development model allows each developer to have their own development environment, or deploy different development environments according to different project requirements. Developers can continue to submit source code based on the online development environment and continue to perform CI and CD to achieve the effect of agile development.


  1. The first deployment of the component has been carried out
  2. The source code corresponding to the component can be continuously modified or the mirror image of the component can be continuously released.

Operation Method

Manual Continuous Build

Kato supports component-level construction and application-level construction. After each code submission, if only a certain component is involved, just click the build button on the upper right of the component control page to trigger the component construction task. By default, the deployment and upgrade process starts after the component is built, and the existing running version is replaced with the new version.

If you do not want to automatically upgrade after the build is completed, you can turn off the automatic upgrade after component build function in the other settings of the component.

Every build process will generate a new component version regardless of whether the code version is changed. If the changed code involves multiple components in the application, such as the entire application created in the Java Maven multi-module mode. At this time, you can click the build button of the application in the application view to trigger the rebuilding of all components of the entire application. Application layer construction will control the orderly upgrade of involved components.

After the component is built and upgraded, developers can access the services provided by the component to view the running status of the component, and continue development.

Automatic Continuous Construction

Developers who are pursuing high efficiency definitely hope that the above process can be separated from the platform and can be automatically completed directly when the code is submitted or other designated time. For this part, please refer to Component Auto Build

Version Management

Each time the component is built, the component version number is generated according to the time when the task is in progress. If the component is created from the source code, each version records the corresponding source code submission Commit information, which is convenient for developers to check the code accordingly. The currently running version information is displayed on the component overview page, and you can enter the component version list query page by clicking on the entry of the version information distribution. Kato keeps version records within 30 days by default, and the historical version automatically cleans up.

The component version mainly includes the running image version. Currently, the component properties do not support version control.