AlibabaCloud DevOps MCP Server

[Pipeline Management] Create a pipeline using structured parameters extracted from user descriptions and environment context.

🔧 Built-in Capabilities:

• ✅ Automatically retrieves default service connection IDs when not specified

• ✅ Handles repository and service connection logic internally

• ✅ Auto-extracts project name from repository URL (git@host:org/repo.git → repo)

• ✅ Supports both IDE detection and explicit parameter specification

📖 Recommended Workflow:

1. 🎯 PARSE user description for explicit parameters

2. 🔍 DETECT missing info from IDE environment FIRST:

   • Run git config --get remote.origin.url → repoUrl

   • Run git branch --show-current → branch

   • Auto-extract serviceName from repoUrl

   • Check project files for tech stack:

     • pom.xml → buildLanguage='java', buildTool='maven'

     • build.gradle → buildLanguage='java', buildTool='gradle'

     • package.json + package-lock.json → buildLanguage='nodejs', buildTool='npm'

     • package.json + yarn.lock → buildLanguage='nodejs', buildTool='yarn'

     • requirements.txt → buildLanguage='python', buildTool='pip'

     • go.mod → buildLanguage='go', buildTool='go'

     • *.csproj → buildLanguage='dotnet', buildTool='dotnet'

3. 🚀 CALL this tool with collected parameters

⚠️ Important Guidelines:

• DO NOT call list_repositories unless user explicitly asks to choose from available repositories

• DO NOT call list_service_connections unless user explicitly asks to choose from available connections

• ALWAYS try IDE detection first before making any API calls

• If IDE detection fails, THEN consider API calls as fallback

🎯 Parameter Priority:

1. 👤 USER EXPLICIT (highest) - buildLanguage, buildTool, versions, deployTarget

2. 🔍 IDE DETECTION (preferred) - repoUrl, branch, serviceName, tech stack

3. 🤖 TOOL DEFAULTS (automatic) - serviceConnectionId, organizationId

🔍 IDE Detection Rules (MUST TRY FIRST):

• 📂 Repository: git config --get remote.origin.url → repoUrl

• 🌿 Branch: git branch --show-current → branch

• 🏷️ Service Name: Auto-extracted from repoUrl (git@host:org/repo.git → repo)

• ☕ Java Maven: pom.xml exists → buildLanguage='java', buildTool='maven'

• 🏗️ Java Gradle: build.gradle exists → buildLanguage='java', buildTool='gradle'

• 🟢 Node npm: package.json + package-lock.json → buildLanguage='nodejs', buildTool='npm'

• 🧶 Node yarn: package.json + yarn.lock → buildLanguage='nodejs', buildTool='yarn'

• 🐍 Python: requirements.txt → buildLanguage='python', buildTool='pip'

• 🐹 Go: go.mod → buildLanguage='go', buildTool='go'

• 💙 .NET: *.csproj → buildLanguage='dotnet', buildTool='dotnet'

📝 Version Detection (from project files):

• ☕ JDK: Read pom.xml <maven.compiler.source> → jdkVersion

• 🟢 Node: Read package.json engines.node → nodeVersion

• 🐍 Python: Read .python-version, pyproject.toml → pythonVersion

• 🐹 Go: Read go.mod go directive → goVersion

🎯 Deployment Parsing:

• '部署到主机/VM/虚拟机' → deployTarget='vm'

• '部署到Kubernetes/K8s' → deployTarget='k8s'

• '只构建/构建制品' → deployTarget='none'

🔗 Service Connection Strategy (3 scenarios):

1. User specifies ID explicitly (e.g., '使用服务连接ID abc123') → ✅ Pass serviceConnectionId=abc123 directly, NO list_service_connections call needed

2. User doesn't specify any ID (most common case) → ✅ Pass serviceConnectionId=null, tool will auto-retrieve default ID internally

3. User wants to choose from available options (e.g., '显示可用的服务连接让我选择') → 🔍 Call list_service_connections first, then let user choose, then create pipeline

🤔 When to Use Other Tools:

• User asks to "select from available repositories" → use list_repositories first

• User wants to "choose from service connections" → use list_service_connections first

• User wants to see options before deciding → gather info first, then create

• For quick creation with current repo → directly use IDE detection

✅ Required: organizationId, name, buildLanguage, buildTool