tencent cloud

Feedback

Build Plan Templates

Last updated: 2023-12-29 11:44:51
    
    title: Build Plan Templates - CODING Help Center pageTitle: Build Plan Templates pagePrevTitle: Group Management pagePrev: ci/manage/group.html pageNextTitle: Upload Generic Artifacts pageNext: ci/plugins/generic.html alias:
    ci/node/overview.html
    ci/team-template.html
    
    In CODING Continuous Integration (CODING-CI), you can create unified build plan templates. Members in a team can reuse configured standard templates across projects to configure build processes more efficiently and centrally manage universal build plans.
    Click the gear icon
    
    in the upper-right corner of your team homepage to go to the team settings. Select "Feature Settings" > "Build Plan Templates" to create a new build template.
    
    
    
    In a template, you can edit the process configuration, basic configurations, trigger rules, and variables and caches.
    Use the "Graphical Editor" or "Text Editor" to compose the execution process of the build template. The graphical editor allows you to view while writing a build process. You can add and delete steps in the graphical editor and convert the result to text. However, steps composed in the text editor may not be fully converted to graphics.
    
    
    
    In "Basic Configurations", you can change the template name and icon. From the "Actions" dropdown menu on the right, you can select "Delete Template" or Sync Template.
    
    
    
    If a template is updated, the creator of the template can click Sync Template to sync the updates to all build plans created from the template. Selecting "Sync Template" will overwrite the configurations in the related build plans. Refer to the sample scenarios.
    You can configure code source trigger, scheduled trigger, or manual trigger rules. The settings are the same as those of normal build plans. For more information, see Trigger Rules.
    You can add environment variables to a build plan. If you manually enable a build task, the environment variables will be used as the default values for startup parameters. For more information, see Environment Variables.
    After a build template is created, members of the team can use the build plan template in any project.
    
    
    
    "Template" will be shown in the upper-left corner of such a build plan. You can select the code source as required for a project.
    
    
    
    After you create the build plan, the build plan process, trigger configurations, environment variables, and default values are the same as the template, you can modify them according to the project. These modifications will not apply to the template. To modify the template, from your team settings, select "Feature Settings" > "Build Plan Templates".
    After a build plan template is modified, the creator of a template can sync the updates to all build plans created from the template.
    Sample scenario: Team A implements continuous integration build specifications. Most build plans are created from a standard build plan template. After some time, the previous specifications need to be updated and the template creator simply needs to modify the build plan template and sync the updates to all build plans created from the template.
    
    
    
    Syncing updates will not overwrite all contents in build plans. See the figure below for an example of "changes" that would be applied.
    
    
    
    ⚠️ Make sure you have known the effect before you perform the sync operation.
    ==== 2020/11/27 ====
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support