In software engineering, continuous integration (CI) refers to the practice of merging copies of all developers’ work into the trunk several times a day. Automated unit testing, code review, compilation build, contract testing, and even automated deployment of each code submission can greatly reduce the workload of developers, reduce many unnecessary repetitions, and continuously improve code quality and development efficiency.

Coding continuous integration is fully compatible with Jenkins continuous integration services, and has done a lot of optimization work on the basic functions and services provided by Jenkins. It supports Java, Python, Node.js and other major languages, and supports the construction of Docker image. By graphical arrangement, multi-job parallel construction of high allocation cluster can speed up the construction task comprehensively. The continuous integration service of CODING supports mainstream Git code repositories, including CODING code hosting, GitHub, GitLab, etc. At the same time, it can also import GitHub repository with one click, automatically backup, and synchronize all changes of the remote repository at any time.

The core component of continuous integration is the build plan, which has been updated with new pages and intuitive design, striving to bring a better user experience

Function to guide

  • Build plan card

The new build plan is presented in the form of card-based design, and the code source, build nodes, and the latest build record are clear at a glance.

  • Latest build record

The build plan shows the latest build record by default, including the current build status, trigger information, code version and other information. It can also easily set the build plan and filter the build record.

Links can be used to quickly locate build branches and revisions within a single build record, as well as to view the build process, build snapshots, and change records.

Star Marks and Groups

The new build plan also supports star and grouping, allowing you to quickly locate the build plan of interest.

  • The star functions

After the star function is set, it is only effective for individuals, and it is suitable for individuals to mark common build plans, so that they can pay close attention to common build plans.

  • Group function

The grouping function is a global option, open to users with “continuous integration management” rights, and the set build plan grouping grouping is visible to members of the project.

After creating a group, you can modify the group name and sort, also support to create and delete groups, as well as bulk organize the build plan, for quick classification, to help you efficiently and conveniently complete the sorting work of the build plan.

Filter and Sort

In the build plan search bar, you can filter by build plan name. Select [Filter] -> [See I Trigger Only], the build plan will display the build record last triggered by the user, and this filter button can also be turned on in the build record display page. Not only is it supported to sort by the build plan’s creation time, but it can also be sorted by the trigger time of the latest build record of the build plan, making it easy to quickly query the required content.

Update forecast

In order to bring a more flexible and convenient use experience, “CODING continuous integration” is also being refined and optimized, and will bring the following updates in the near future, please look forward to it: 1. Team building planning template: it will support team managers to create various building planning templates, which can be reused by team members and help the team to customize the standardized building process. 2. Team plug-in management: it will support custom plug-in and team-level plug-in management to achieve the personalized needs of the team.

Coding is recommended in October

One-click synchronization, keep up with the trend, CODING is now supported into the GitHub warehouse, click to see details

Coding continuous integration invites you to experience cloud automated code building