Likelihood to Recommend
Previously, our team used
. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
Read full review
One scenario I believe HP Agile Manager is well suited is for a team of 5 or more developers who are releasing new features or addressing defects. Another scenario where it is beneficial is for teams of QA Automation engineers, where again, the objectives are clear. A scenario where I believe it would be less appropriate is for operations-type teams where objectives are not always clear cut, and the roles must be more reactive.
Read full review Pros Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM. The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones. Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems. Read full review Agile manager is particularly good for planning out sprints in an Agile methodology The Task Board in AGM gives clear swim-lanes to indicate progress/status, or to gauge that of another team member. The Dash Board gives visibility to team members capacity and the overall team burn down. Read full review Cons UI can be improved Location for settings can be re-arranged API for setting up pipeline Read full review Removing stories from a Sprint results in them being difficult to find later. Editing story details is slightly cumbersome. It's somewhat unclear how capacity fills up for stories split from prior sprints. Read full review Alternatives Considered
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
Read full review
HP Agile Manager is beefy enough to work for bigger teams. In this way it matches closely to what is offered with Rally. One area it comes up short when compared to Rally is the apparent lack of a test management capability, where requirements can be entered then mapped to test cases. Agile Manager has some of the agile feel offered by
and Waffle but the added functionality that makes it more valuable for bigger teams.
Read full review Return on Investment ROI has been good since it's open source Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date Read full review It has allowed us to plan our Sprint work more effectively It has made it more clear how to accurately estimate certain problems It has given clarity over time as to the skill and work speed of team members Read full review ScreenShots