GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
N/A
Sourcetree
Score7.7 out of 10
N/A
Sourcetree, by Atlassian, is a free version control client for Mac and Windows that works with Git and Mercurial repositories. It's distributed version control allows developers to visualize code, review changesets, stash, cherry-pick between branches or commit with a single click.
Previously, our team used Jenkins. 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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Sourcetree is a great tool for any Git user. Whether you're well versed using Git commands in the terminal or a newbie, this tool wonderfully supplements your workflow. A quick glance at the UI and you know where your project stands. I find it most helpful when I need to determine what changed in a particular file in past commits. Having a visual graph of branches helps me to understand the big picture. Even though I'm comfortable operating Git most often in the command line, I always have Sourcetree open to check my work and see where my colleagues are.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
As an Atlassian product i'd have expected smart integrations/features with their other developer products like Jira or BitBucket, but this is not the case. It can sometimes pick up on Jira ticket IDs and show them as a label or as a unique piece of work to follow. But there's no actual integration to Jira and is just simple pattern matching.
For the majority of developers it's just overwhelming and overkill. There's a plethora of metadata, supporting information, and many many actions/tools to help perform complex git actions. This is great if you're managing complex repos or need to perform an audit, but to the average user it's just not a user friendly experience due to how bloated it can feel.
Very simple git actions such as 'git pull' have been massively overcomplicated. When pressing the pull button you get a popup with multiple dropdowns, checkboxes and settings on how you want to pull and the followup actions to run after the pull, both on the remote repo and local repo. It's just unnecessary and adding complexity where it's not needed.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
It is one of the best Git GUIs out there, I have worked with multiple GUIs and this provides more insights and features compared to others, the Tree view and History helps keeping track and reverting commits, With help of different UI elements it helps the new developers to learn git using standards as well.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins 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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Sourcetree allows seamless integration across all widely used GIT services and is cross-platform compatible. This client is capable of managing workflows of any difficulty and its cross-compatibility eliminates the need to use different or multiple GIT clients altogether.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
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
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
