Reference page for Build package


In the Servoy Cloud Control Center, 'Packages' are often referred to as 'build packages' or simply 'builds'. They are the result of a process called a 'job'. When you initiate a job, it starts to produce a build package.

Package details

Package details section is where you can view the outcome of a build, from build details (build date, build number, build version etc.) and build markers to package details like commits, artifacts, build configuration changes, and quality reports.

Build details

In the Servoy Cloud Control Center, each build package includes important information. Here's what you'll find:

  • Build Status: This shows the result status for each build.

  • Build Number: A unique identifier for each build.

  • Build Version: Depending on the job type, this could be:

    • For 'Build and Deploy' or 'Build' jobs, it's the version of Servoy used.

    • For 'Mobile' or 'Desktop' jobs, it's the version of your application.

  • Build Result: This indicates the outcome of the build process. It could be 'Building', 'Successful', 'Failed', 'Aborted', or 'Unstable'.

  • Build Date: The date when the build was initiated.

  • Number of Commits: The count of code changes committed for this build.

  • Number of Configuration Changes: The count of changes made to the build's configuration.

  • Number of Binary Downloads: The count of binary files downloaded produced as result of the build.

Build Status


When you initiate a job, the system begins creating a new build package. If you need to halt this process, navigate to the "Active builds" section and click on the "Stop" button corresponding to the build you wish to halt. This action results in a build package with an "Aborted" status. Please note that this action is not applicable for Mobile and Desktop builds.


A job can only generate one build package at a time. If a new job is initiated while a build is already in progress, the new build will be queued. If you wish to remove a build from the queue, simply press the "Stop" button. Again, note that Mobile and Desktop builds cannot be removed from the queue.


When a build process completes without any errors, the resulting build package is marked as "Successful".


If a build process is halted using the "Stop" button in the "Active builds" view, the resulting build package is marked as "Aborted".


If a build encounters an error that prevents the successful generation of the build package, the build is marked as "Failed". The reason for the failure can be found in the Package Details section, highlighted in red. Some failure reasons may provide additional details in the log files located in the Artifacts section of the Package details page.

If a build fails for an unknown reason, the support team is automatically notified and will investigate the issue.


An "Unstable" status indicates that the build process has finished, but there are issues with deploying the build package or starting the server.

This could happen due to errors during the pre-import or post-import of the application. If such a situation arises, a link will be provided in the package detail section. You can click this link to navigate to the specific log time window, which can help you identify and troubleshoot the error.

How to access

You can navigate to Package Details by clicking on package build numbers throughout the Cloud Control Center or from the Builds Package History section by clicking on any of the build packages.

Last updated