AWS CodePipeline vs. BMC Helix ITSM

I think AWS CodePipeline is a great tool for anyone wanted automated deployments in a multi-server/container AWS environment. AWS also offers services like Elastic Beanstalk that provide a more managed hosting & deployment experience. CodePipeline is a good middle ground with solid, built-in automation with enough customizability to not lock people into one deployment or architecture philosophy.

Incentivized

BMC Helix ITSM fits our environment particularly well, where standardized, auditable processes are already in place: Incident and Problem Management can be structured cleanly, with clear ownership, escalations, and fully traceable documentation—crucial in a highly regulated banking context. Through the customer platform/portal, users can log incidents and requests consistently, track their status transparently, and use a single central communication channel across service boundaries. This supports a service-oriented setup spanning multiple business services and locations. It becomes less suitable—or at least more effort-intensive—when core foundation data is not yet stable: an immature CMDB, insufficient ITAM data quality, and an unstructured knowledge base limit the value of automation and self-service. In addition, heterogeneous integrations and strict authorization models can increase implementation and ongoing maintenance efforts, especially when SLAs are not harmonized across different customer environments.

• It is reliable and works without errors
• It integrates well with our repository and all other AWS functions as well as our end database

Incentivized

• AI drive incident correlation leading to identifying problems and major incidents quickly.
• Digital Workplace gives end-users a modern and personalized UI to submit requests, monitor service health, and receive self-help.
• As an enterprise ITSM, it is critical that Request, Incident, Problem, Asset, and Change Management are integrated and flow together. BMC Helix is built on this principle.

Incentivized

• Ease of use - things like CircleCI or other tools are a bit easier to learn.
• Ability to build from more sources.

Incentivized

• Service Level management configs can be lengthy, and when changes are needed to specific SLA, it does take a long time to configure. Templates work but only for certain things, lots of manual work is still required.
• The Online product documentation can be confusing or in same cases not correct.
• BMC products are sometimes expensive. When partners try to resell licenses or increase their own allotment, it becomes very expensive.

Incentivized

It provides the tool we need and is able to be customised to meet new requirements. Cost to change in training and integrations would be considerable.

Overall, I give AWS Codepipeline a 9 because it gets the job done and I can't complain much about the web interface as much of the action is taking place behind the scenes on the terminal locally or via Amazon's infrastructure anyway. It would be nicer to have a better flowing and visualizable web interface, however.

Incentivized

Overall the product enhances the capability of incident management, problem management and change management. The AI based framework helps generated better visibility and reports. The effectiveness of enhanced service desk suuport improves end user experience as the incidents are handled well in time and aged incidents are highlighted at the right time.

Incentivized

for now we are satisfied. first two months 😉

Incentivized

Our pipeline takes about 30 minutes to run through. Although this time depends on the applications you are using on either end, I feel that it is a reasonable time to make upgrades and updates to our system as it is not an every day push.

Incentivized

could be faster. db is slower from introducing postgresql

Incentivized

We didn't need a lot of support with AWS CodePipeline as it was pretty straightforward to configure and use, but where we ran into problems, the AWS community was able to help. AWS support agents were also helpful in resolving some of the minor issues we encountered, which we could not find a solution elsewhere.

Incentivized

Their tech support is top notch. They respond and get back to us, even on lower level incidents and issues, very quickly. It is rare that we deal with a support technician who does not know what they are doing.

the trainers dont have so much practical experiences. its mostly follow up and reading existing documentation withou own input. of course experiences people are on shore or have no free time. sad truth

Incentivized

Satisfied because I didn't have to do it!

Incentivized

CodeCommit and CodeDeploy can be used with CodePipeline so it’s not really fair to stack them against each other as they can be quite the compliment. The same goes for Beanstalk, which is often used as a deployment target in relation to CodePipeline.

CodePipeline fulfills the CI/CD duty, where the other services do not focus on that specific function. They are supplements, not replacements. CodePipeline will detect the updated code and handle deploying it to the actual instance via Beanstalk.

Jenkins is open source and not a native AWS service, that is its primary differentiator. Jenkins can also be used as a supplement to CodePipeline.

Incentivized

I believe Remedy's performance and market share exceeds its competitors. But it is worth mentioning that Microsoft's SCCM has excellent integration with Microsoft enterprise solutions and has is less expensive and not efficient. The IBM solution has better analytics but lacks the wide features and capabilities of Remedy. HP & CA are the real competitors for Remedy but lacks the stability, maturity, and effectiveness in Remedy

Incentivized

unclear. lot of for less

Incentivized

Again, always room for improvement, but a very stable product none-the-less.

Incentivized

• CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing.
• CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch.
• CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually.

Incentivized

• Positive: an introduction to ITIL and viewing Asset, User Management from the perspective of ITIL, and how BMC has implemented those processes
• Negative: The development team needs to communicate better with the sales and support side, and they need offer an open API
• Negative: Currently the Asset Management side has little security and validation of Asset input: anyone can make API (mostly), at any item, which is a problem that I am apart of solving.
• The UX needs updating, badly. Its quality is poor: it functions, but it is cumbersome, click-heavy and requires several hours to understand how to function with it. Also, it needs to ditch IE11 support, altogether.

Incentivized