CI/CD and Transport for BTP Applications

Keep this: job aid

BTP release pipeline checklist

• Build once: one versioned .mtar travels from development to production.
• Raise the MTA version for every release candidate; never reuse a version for new content.
• Pipeline stages: Build, unit tests, malware scan, acceptance; compliance and transport in the release pipeline.
• Technical users and stored credentials only; no secrets in Git or in repository descriptors.
• Hand off with Export from (Cloud ALM-driven) or Upload to; set the test node to forward Manual after sign-off.
• Same destination names everywhere; each subaccount points them at its paired S/4HANA system.
• Upload an extension descriptor in every import queue that needs one; check its version binding.
• Fatal = connection problem, re-import after the fix; Error = content problem, fix in a new version.
• Gate owners, exit criteria and evidence written down before the first release.
• Blue-green: test the idle version, keep changes compatible, and plan rollback separately.