Ruk-Com PaaS Packaging Standard for CI/CD Automation
This guide is maintained for Ruk-Com PaaS. Screens and options may vary by platform version and account permissions.
Confirm the environment, region and account permissions, and back up current settings before changing a production system.
Objective
This guide explains how to use Ruk-Com PaaS Packaging Standard for CI/CD Automation on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
JPS(Ruk-Com PaaS Packaging Standard) is a tool for provisioning ready-to-use applications and add-ons. Such pre-configured methods can be integrated into cloud platforms with just one click, which makes installation and configuration for any type of application easier.
The JPS package is based on the JSON implementation. This file is used to describe environment creation, application deployment and configuration operations. Resource allocation Setting scaling limits for each server within the environment
This technology automates complex CI/CD scenarios and easily distributes ready-to-go solutions with a one-click installation widget.
Application CI/CD Automation with Cloud Scripting
Developed by Ruk-Com PaaS, the cloud scripting language enables JPS packaging technology to fully automate application delivery steps, such as automatically transferring each new application version through the development, testing, and production stages. This is ensured by using the required project processing logic through method connections.Ruk-Com PaaS APIin various ways
This is because it offers a wide range of customization and automation options. You can deploy it to almost any desired scenario using Cloud Scripting - from relatively simple operations to maintaining complex applications and clusters. You can create your own solutions with CS. You can:
- Define the desired configuration properties in advance and declare the expected application behavior with appropriate actions.actions
- Bind these operations to the application lifecycle.eventsespecially
- Retrieve informationinputof users and internal use
- runcustom scriptInside the created container
Widget for Instant Application Deploy
Once your application is compiled into JPS, you can make the widget available to other developers for quick installation. This improves the efficiency of distributing the application and increases its attractiveness due to ease of deployment. This also reduces the cost of supporting your project and managing post-installation along the way.
Widget consists ofmanifest(or link to resources) with a description of the cloud environment required for this application and instructions on automatic installation and configuration.
To install an application package into the cloud, the user must initiate the installation using the selected widget and receive a confirmation URL via the provided email address. When you follow the link The system automatically parses and processes the manifest data to create or optimize the environment and connect the required nodes. As a result, users receive a fully functional and configured application without any additional configuration steps.
Use these documents below to find more information on how to properly write an application manifest and create such a widget installation:
- Application Manifest
- Application Manifest Example
- Placeholders
Note:After filling the application according to our instructions. You can contact your hosting provider to add your JPS solution set within the Ruk-Com PaaS Marketplace dashboard. This way your app will be automatically available within the platform.
