We’re evaluating CI/CD tools for our ELM 7.0.1 environment and need strong version control integration for build promotion workflows. Our requirements focus on branching support, baseline automation, and maintaining traceability between builds and test results.
Jenkins seems to have a mature plugin ecosystem with direct RTC SCM integration, but Bamboo claims better native support for baseline delivery and configuration management. We’re particularly interested in automating baseline creation when builds are promoted from dev to staging to production.
Has anyone compared these tools specifically for ELM version control scenarios? Which one handles complex branching strategies better when you need to track which baseline was used for each build? We have about 40 components across 6 project areas, so scalability and performance matter too.
Interesting perspectives. How do you both handle baseline synchronization when a build is promoted across environments? We need to ensure the same baseline used in dev testing is promoted to staging without manual intervention. Does either tool provide out-of-box support for this workflow?
Mark makes a good point about configuration drift. We’ve also found Bamboo’s audit trail superior for compliance scenarios. Every baseline promotion is logged with the deployment project history, making it easy to track which baseline was deployed where and when. For regulated industries, this built-in audit capability is valuable. Jenkins can achieve similar results but requires additional plugins or custom logging.
For Jenkins, we use pipeline scripts with the ELM REST API. When a build passes dev tests, the pipeline captures the baseline ID, stores it as a build parameter, and passes it to the staging deployment job. Not out-of-box, but the flexibility is worth it. We can also query baseline metadata to enforce promotion rules, like requiring all test cases in the baseline to pass before allowing staging deployment.