Successfully integrating the Cloud Edge Distribution (CED) into your project lifecycle requires assembling a few key components. This setup ensures seamless deployment and management processes aligned with your existing systems. The integration involves configuring the ced.json instruction file, automating workflows within your Version Control System (VCS), and adapting to different VCS environments to maintain workflow consistency and efficiency.
Creating the CED Instruction File (ced.json)
The ced.json file is a cornerstone for integrating CED into your project. This file defines the settings and configurations required for your deployment within the CED system, specifying how your project interacts with the cloud and edge services. For a comprehensive understanding of its structure and significance, refer to the details provided in the Merthin documentation on ced.json.
Configuring Automation at VCS Level
Merthin CLI Runner Image: The Merthin CLI runner image facilitates the integration of CED commands into your CI/CD pipelines, minimizing vendor lock-in and enhancing compatibility across different environments. This setup enables seamless automation and standardization in deployment processes. More details can be found in the Merthin guide on navigating CI solutions.
Current VCS Compatibility and Flexibility: The flexibility of CED allows for easy adoption across various VCS platforms, ensuring that you can maintain your existing workflows while integrating new functionalities offered by CED. This compatibility supports a smooth transition and scaling within diverse project environments.
Sample Workflow Integrations Here are examples of how to integrate CED within GitHub and BitBucket pipelines, demonstrating practical applications of the Merthin CLI runner image:
GitHub Workflow:
name: Push CED Source
env:
PROJECT_PATH: spa
MERTHIN_CLI_TOKEN: ${{ secrets.MERTHIN_CLI_TOKEN }}
on:
push:
branches:
- master
paths:
- "spa/**"
jobs:
deploy:
runs-on: ubuntu-latest
container:
image: merthin/ced-cli-runner:0.3
steps:
- uses: actions/checkout@v2
- name: Run command in Docker container with environment variables
run: |
cd $PROJECT_PATH
ced-checkout
BitBucket Pipeline:
image: merthin/ced-cli-runner:0.3
pipelines:
branches:
master:
- step:
name: Push SPA Source to CED
condition:
changesets:
includePaths:
- "spa/**"
script:
- cd spa
- ced-checkout
These samples illustrate how to configure the CED CLI within CI/CD pipelines, leveraging environmental variables and specific commands to manage deployments effectively.