Help Center/ ServiceStage/ User Guide/ Component Management/ Redeploying a Component/ Redeploying a Component in Single-batch Release Mode
Updated on 2025-08-12 GMT+08:00

Redeploying a Component in Single-batch Release Mode

You can select a historical version configuration from the deployment record list and use the version configuration as a template to redeploy components in single-batch release mode.

During component redeployment in single-batch release mode, component services will be interrupted. This is applicable only to the test upgrade scenario or the upgrade scenario where services are to be stopped.

Prerequisites

Redeploying a Component in Single-batch Release Mode

  1. Log in to ServiceStage.
  2. Use either of the following methods to go to the View Deployment History page.

    • On the Application Management page, click the application to which the component belongs, click the target component in Component List, and choose Deployment Records in the left navigation pane.
    • On the Component Management page, click the target component and choose Deployment Records in the left navigation pane.

  3. In the Deployment Records list, select the deployment record of the historical version to be used as the configuration template.
  4. Click Redeploy in the upper right corner of the page. The Redeploy dialog box is displayed.
  5. Select Single-batch Release for Deployment Type and click OK.
  6. Configure the component version by referring to the following table. Parameters marked with an asterisk (*) are mandatory.

    Parameter

    Description

    Stack

    Select a component technology stack and version.

    For details, see Technology Stack.

    *YAML Mode

    Whether to use YAML configurations to redeploy components.

    • Disabled: The UI configurations are used to redeploy components.
    • Enabled: The YAML configurations are used to redeploy components. The latest load information of the component is automatically synchronized from CCE where the target component is deployed for component redeployment after modification. Alternatively, click Import YAML File to import the edited YAML configuration file of the target component.

      The parameters in the YAML configuration file are described in Deployment.

    *Software Package/Image

    The value is fixed to the package type selected during component creation and deployment.

    • YAML Mode disabled: If you select Source code repository, create authorization by referring to Creating Repository Authorization and set the code source. If you select a software package or image package, the option is fixed to the software package type (JAR, WAR, or ZIP) or image package type selected during component creation and deployment. It is determined by the selected technology stack type. For details, see Table 1.
    • YAML Mode enabled: If you select Source code repository, create authorization by referring to Creating Repository Authorization and set the code source. If you select a software package, the option is fixed to the software package type (JAR, WAR, or ZIP) selected during component creation and deployment. It is determined by the selected technology stack type. For details, see Table 1.

    *Upload Method

    • YAML Mode disabled: If the component source is software package or image package, select an uploaded software package or image package. For details about the upload method, see Component Source.

      If you select an image package:

      • If Multi-container is selected in Creating and Deploying a Component, select a container and click to specify it as the initialization container for installing tools or scripts before the service container starts. At least one container must be specified as the service container (non-initialization container). For details about container initialization, see Init Containers.
      • You can customize the container name. The name contains 1 to 63 characters, including lowercase letters, digits, and hyphens (-), and must start with a lowercase letter and end with a lowercase letter or digit.
      • Click in the upper right corner of the selected container to change the container image package source.
    • YAML Mode enabled: If the component source is software package, select an uploaded software package. For details about the upload method, see Component Source.
    • If the package type is software package and you need to use JFrog (example) as the software package repository, you can select Custom file address.
      1. Enter the HTTP/HTTPS custom file address where the software package is located.
      2. Determine whether to enable authentication.

        If authentication is disabled, any user can download the software package in the custom file address by default.

        Click to enable authentication. Only authenticated users can download the software package in the custom file address. Authentication mode can be User name and password authentication or User-defined Header Authentication. The authentication mode and the corresponding authentication parameters are determined by the authentication mode supported by the server where the custom file directory is located.

    Image Access Credential

    An image access credential is a secret, which is used to store the authentication information required for pulling images from a private repository. For a public repository image, you can retain the default settings or do not set this parameter. For a private repository image, this parameter is mandatory. Otherwise, the image fails to be pulled.

    • You can select up to 16 image access credentials.
    • Click Create Secret to create an image access credential. Secret Type must be kubernetes.io/dockerconfigjson. For details, see Creating a Secret.

    *Command

    This parameter is mandatory when YAML Mode is disabled, the package type is Source code repository, and the selected technology stack type is Java, Tomcat, Node.js, Python, or PHP.

    • Default command or script: preferentially executes build.sh in the root directory. If build.sh does not exist, the code will be compiled using the common method of the selected language. Example: mvn clean package for Java.
    • Custom command: Commands are customized using the selected language. Alternatively, the default command or script is used after build.sh is modified.
      • If Custom command is selected, exercise caution when inputting sensitive information in the echo, cat, or debug command, or encrypt sensitive information to avoid information leakage.
      • To run the compilation command in the project subdirectory, you need to go to the project subdirectory and then run other script commands. For example:

        cd ./weather/

        mvn clean package

    *Dockerfile Address

    This parameter is mandatory when YAML Mode is disabled, the package type is Source code repository, and the selected technology stack type is Java, Tomcat, Node.js, Python, or PHP.

    Dockerfile Address is the directory where the Dockerfile is located relative to the root directory (./) of the project. The Dockerfile is used to build an image.

    If Dockerfile Address is not specified, the system searches for the Dockerfile in the root directory of the project by default. If the Dockerfile does not exist in the root directory, the system automatically generates the Dockerfile based on the selected operating environment.

    *Component Version

    Component version number, which can be automatically generated or customized.

    • Automatically-generated: Click Generate. By default, the version number is the time when you click Generate. The format is yyyy.mmdd.hhmms, where s is the ones place of the second in the timestamp. For example, if the timestamp is 2022.0803.104321, the version number is 2022.0803.10431.
    • Customized: Enter a value in the format of A.B.C or A.B.C.D. A, B, C, and D are natural numbers. For example, 1.0.0 or 1.0.0.0.

      The customized version number must be unique and cannot be the same as any historical version number of the component. Otherwise, the current deployment record will overwrite the historical deployment record of the same version.

    *Container Name

    This parameter is mandatory when the technology stack is not Docker.

    The name contains 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.

    Resources

    When YAML Mode is disabled, the configuration of the selected historical version is used and cannot be modified.

    JVM Parameters

    When YAML Mode is disabled and the technology stack type is Java or Tomcat, the memory parameter size configured for running the Java code of the selected historical version is used and cannot be changed.

    Tomcat

    When YAML Mode is disabled and the technology stack type is Tomcat, the configuration, such as Tomcat request path and port number, of the selected historical version is used and cannot be changed.

    Cloud Service Settings

    When YAML Mode is disabled, the configuration of the selected historical version is used and cannot be modified.

    Container Settings

    When YAML Mode is disabled, the configuration of the selected historical version is used and cannot be modified.

    Application Settings

    When YAML Mode is disabled, the configuration of the selected historical version is used and cannot be modified.

    Log Settings

    When YAML Mode is enabled, the configuration of the selected historical version is used and cannot be modified.

    Advanced Settings

    When YAML Mode is disabled, the configuration of the selected historical version is used and cannot be modified.

  7. Click Upgrade.

    • During component redeployment, if the component configuration is incorrect, you can click Suspend to stop the redeployment. Then, click Upgrade and reconfigure the component by referring to Upgrading a Single Component.
    • Wait until the component status changes from Upgrading/Rolling back the component to Running, indicating that the component has been redeployed.
    • On the View Deployment History page, view the deployment logs.

      If "Querying the Status of a Workload Instance" is displayed, click View Event to view details.