build-ci-migration-assistant

Solid

Automatically migrates build systems and CI/CD configurations to target platforms. Use when modernizing build infrastructure, switching CI/CD providers, or standardizing across projects. Supports common migration paths including Maven↔Gradle, npm↔Yarn, Travis CI→GitHub Actions, CircleCI→GitHub Actions, Jenkins→GitLab CI, and GitLab CI→GitHub Actions. Analyzes existing configuration, generates equivalent target configuration, maps dependencies and commands, and provides validation and migration documentation.

DevOps & Infrastructure 160 stars 17 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%
73
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Build/CI Migration Assistant Automatically migrate build systems and CI/CD configurations to target platforms while preserving functionality. ## Workflow ### 1. Analyze Source Configuration Identify the current build system or CI/CD platform: **Build Systems:** - Maven (pom.xml) - Gradle (build.gradle, build.gradle.kts) - npm (package.json) - Yarn (package.json + yarn.lock) - Make (Makefile) - CMake (CMakeLists.txt) **CI/CD Platforms:** - Travis CI (.travis.yml) - CircleCI (.circleci/config.yml) - Jenkins (Jenkinsfile) - GitLab CI (.gitlab-ci.yml) - GitHub Actions (.github/workflows/*.yml) Read and parse the source configuration to understand: - Dependencies and their versions - Build commands and lifecycle - Test configuration - Environment variables and secrets - Caching strategy - Deployment steps ### 2. Map to Target Platform Consult the appropriate reference guide: - **Build systems**: See [references/build-systems.md](references/build-systems.md) - **CI/CD platforms**: See [references/ci-platforms.md](references/ci-platforms.md) Map source concepts to target equivalents: - Dependencies → Target dependency format - Build commands → Target command syntax - Lifecycle phases → Target stages/jobs - Environment variables → Target secrets/variables - Caching → Target caching mechanism ### 3. Generate Target Configuration Create the target configuration file(s): **For build systems:** - Generate new build file (build.gradle, pom.xml, etc.) - Preserve dependency v...

Details

Author
ArabelaTso
Repository
ArabelaTso/Skills-4-SE
Created
6 months ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category