AWS CodePipeline is a fully managed continuous delivery service that helps users automate release pipelines for fast, reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of the release process every time there is a code change, based on the release model a user defines. This is to enable rapid, reliable delivery of features and updates. Users can integrate AWS CodePipeline with third-party services such as GitHub or with a custom plugin. AWS…
$1
per active pipeline/per month
BMC Helix ITSM (Remedy)
Score 6.9 out of 10
N/A
BMC Helix ITSM replaces Remedy. It is a broad suite of ITSM, tools with strong integrations to other BMC tools and in-built ITAM. The product is used mainly by global brands and is offered in on-premise and SaaS configurations.
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.
Large complex organisation, with complex technology that needs to manage Technology Services. It is very flexible and able to manage a large complex environment but the knowledge required to set this up correctly (foundation data and configuration) is the key factor for success. It can integrate with many other systems and tools and integrate data from many sources - whether that be AWS cloud, or an on premises bespoke system. I would not recommend for a Small Organisation without the resources to set up and maintain the underlying foundation data and configuration.
Integration with monitoring software like SolarWinds. where Remedy can transform notifications to work orders and assign to respective teams.
Detailed Customization capability to fit the exact needs of the organization.
Change management calendar, which integrates change orders from all organization departments and facilitates the scheduling process of project managers.
It can be offered as a cloud-based service, where you don't need to worry about server maintenance or database backup.
The interface (ironically). My company has made an attempt to replace the "classic" Remedy interface with some more functional, modern, but Remedy set to a particular look and feel (and consequently, functionality)
The API is hidden from the user: There exists an API for Remedy, that would make my job TONS easier, as I like to perform actions on Remedy in bulk (and therefore - programmatically). Exposing a user API is very much mainstream these days, so Remedy relying on its interface to perform ITIL is very limiting
By extension- the result of Remedy's interface is that it becomes very "click-happy": little buttons, and links stuffed into every corner of the screen, with options API logically together. API is old, but it still feels very rushed.
The primary tool for most of my ITIL operations is: searching. API of searching goes into finding assets, checking in equipment, finding users, tickets, etc. What Remedy could very much benefit from a "Google" -like interface
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.
At least Remedy is all contained in a single platform, so the interface is consistent. Also, the most heavily performed functions are generally usable. However, to use some of the more advanced modules can be a bit more cumbersome (such as Change Management and CMDB (Not Including ADDM)). So, overall BMC Remedy ITSM is better than some applications like CA SDM or HP SM, but not quite on par with ServiceNow.
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.
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.
The support is good in overall resolving the issues and even in the deployment phase. We are able to use it in production without any trained in-house engineer as the support team gets the job done. We can say that experts completed the deployment for us, and now it is functional.
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.
The decision to select BMC Remedy was made prior to my employment. We did conduct an RFC process for a new ITSM platform and BMC was considered but not selected. We looked at several platforms and ended up choosing Ivanti Service Desk (previously LANDESK) due to the features, ease of customization and price.
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.
When I was in Management discussion calls, and all the team is happy while using BMC Remedy so I don't find any specific negative impact on our organization.
I really enjoy Smart IT as the tool of choice for our incident management team.
Visibility of tickets is key. All support staff users can see tickets in consoles they have access to.
