The buildpack management feature provides flexible and powerful custom buildpack capabilities. You can deploy custom buildpacks and flexibly extend existing buildpacks. Buildpacks help the Application Management module manage the software packages and deployment scripts to be installed and executed during application service publish. Common system buildpacks SOFA Lite and Sprint are provided. You can also customize buildpacks as required.
This topic describes how to customize a Spring Boot buildpack. For more information, see Buildpack user guide.
You can perform the following operations on the Buildpack Management page.
The following operations apply only to custom buildpack instances. You can only clone and view the buildpack instances provided by the system.
Create a custom buildpack instance
Log on to the Application Management console. In the left-side navigation pane, click Buildpack Management.
On the Buildpack Management page, click Create in the upper-left corner to create a buildpack instance.
Set the following parameters and click OK:
Buildpack: Select a framework for the buildpack to be created.
Buildpack Version: Enter the version prefix. The suffix is the tenant name by default.
Supported OS: The CentOS 6.5 64-bit, CentOS 7.2 64-bit, CentOS 7.6 64-bit, and CentOS 7 64-bit OSs are supported.
Debugging Mode: If this parameter is selected, a buildpack can still be modified after it is published, and you can perform integrated debugging for the buildpack on the cloud. A buildpack in debugging mode cannot be shared with other tenants. After you cancel the debugging mode for a published buildpack, you cannot enable the debugging mode for it again, but you can share it with other tenants.
Description: Enter the description of the buildpack with a maximum of 500 characters.
Buildpack Package: Click Upload File to upload a local buildpack package.
Environment Parameters: Click Add and configure environment parameters.
The created buildpack is in the Unpublished state.
Publish a buildpack instance
Log on to the Application Management console. In the left-side navigation pane, click Buildpack Management.
On the Buildpack Management page, find a buildpack instance in the Unpublished state and choose More > Publish in the Actions column.
In the message that appears, click OK.
The published buildpack is in the Published state.
Discard a custom buildpack instance
Log on to the Application Management console. In the left-side navigation pane, click Buildpack Management.
On the Buildpack Management page, find the buildpack instance that you want to discard and choose More > Discard in the Actions column.
In the message that appears, click OK.
The discarded buildpack is in the Discarded state.
Clone a buildpack instance
Log on to the Application Management console. In the left-side navigation pane, click Buildpack Management.
On the Buildpack Management page, find the buildpack instance that you want to clone and choose More > Clone in the Actions column.
In the dialog box that appears, modify the buildpack information and click OK.
The cloned buildpack is in the Unpublished state.
Delete a buildpack instance
You can delete only a custom buildpack instance that is not used.
Log on to the Application Management console. In the left-side navigation pane, click Buildpack Management.
On the Buildpack Management page, find the buildpack instance that you want to delete and choose More > Delete in the Actions column.
In the message that appears, click OK.
View a buildpack instance
Log on to the Application Management console. In the left-side navigation pane, click Buildpack Management.
On the Buildpack Management page, find the buildpack instance that you want to view and choose More > View in the Actions column.
On the read-only details page of the buildpack instance, view detailed information.
Versions of system buildpacks
SOFAStack provides the SOFABoot (2.0) and NodeJS system buildpacks and other common system buildpacks. For more information, see Buildpack version description.