Commit 60efc791 authored by Dan Gordon's avatar Dan Gordon

fix comps battlecard info template and align all bc files

parent 4e95c48e
Pipeline #33292515 passed with stages
in 27 minutes and 25 seconds
......@@ -2,39 +2,36 @@
layout: markdown_page
title: "Azure DevOps"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison to GitLab
#### Features
- link to comparison page <-- comment. delete this line
#### Value/ROI
- link to ROI calc? <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
<!-- ## On this page
## On this page
{:.no_toc}
-->
- TOC
{:toc}
......@@ -112,5 +109,4 @@ MS pushes Visual Studio subscriptions and refers customers who are only interest
Excluding CapEx and Windows operating system license, a standalone TFS license through a reseller in classic purchasing model is approximately $225 per year per instance. The approximate Client Access License is approximately $320 per year.
## Comparison
......@@ -2,36 +2,36 @@
layout: markdown_page
title: "Atlassian Bamboo"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison
- link to comparison page <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
<!-- ## On this page
## On this page
{:.no_toc}
-->
- TOC
{:toc}
......
......@@ -2,38 +2,36 @@
layout: markdown_page
title: "Atlassian BitBucket"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison
- link to comparison page <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
<!--
## On this page
{:.no_toc}
-->
- TOC
{:toc}
......
......@@ -2,30 +2,31 @@
layout: markdown_page
title: "Google CloudBuild"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison
- link to comparison page <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
......@@ -35,22 +36,27 @@ tact so that others can see where new sections should be added.
- TOC
{:toc}
### Comments/Anecdotes
## Summary
Cloud Build lets you build software quickly across all languages. Get complete control over defining custom workflows for building, testing, and deploying across multiple environments such as VMs, serverless, Kubernetes, or Firebase.
## Comments/Anecdotes
- From GitLab PM
> It is competitive, but I don't see it getting a significant amount of usage. It's been around for awhile and we never really saw it competitively. This rebranding/marketing push may move the needle on awareness, but they take a pretty rigid approach to how you define your builds which will turn people off I think. It's hard to use for common tasks.
### Resources
## Resources
* [Google CloudBuild](https://cloud.google.com/cloud-build/)
### Integrations
## Integrations
* Google CloudBuild and GitLab partnered to create a demo for Google Next 2018. This showed 2 use cases:
- Using GitLab for SCM-only and CloudBuild for CI/CD
- Using GitLab CI/CD test and deploy, but offloading the build stage to CloudBuild
[Full details, as well as links to the demo and sample code](https://about.gitlab.com/2018/07/27/google-next-2018-recap/#google-cloud-build--gitlab-cicd) are on the GitLab blog.
[Full details, as well as links to the demo and sample code](https://about.gitlab.com/2018/07/27/google-next-2018-recap/#google-cloud-build--gitlab-cicd) are on the GitLab blog.
### Pricing
## Pricing
- [Google Pricing Guide](https://cloud.google.com/cloud-build/pricing)
- First 120 build-minutes per day - Free
- Additional build-minutes - $0.0034 per minute
- Note: Google Cloud Platform costs apply on top of these costs
## Comparison
......@@ -2,6 +2,33 @@
layout: markdown_page
title: "Codefresh"
---
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
## FAQs
- about the product <-- comment. delete this line
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
## On this page
{:.no_toc}
......@@ -9,19 +36,19 @@ title: "Codefresh"
- TOC
{:toc}
### Summary
## Summary
Codefresh is a CI/CD tool designed for containers and Kubernetes. Codefresh features a [GitLab integration](https://codefresh.io/docs/docs/integrations/git-providers/) that allows you to use GitLab for version control and run Codefresh pipelines on your code. Codefresh has some features that make it more mature that GitLab for running pipelines across multiple projects. But it lacks the benefits of a [single application](/handbook/product/single-application/).
Codefresh charges for builds per month, as well as concurrent builds. GitLab has no such limitations with the ability to elastically scale Runners to handle as many concurrent builds as needed on demand and then scale down so you aren't paying to keep inactive Runners up.
Codefresh only offers a self-managed option for Enterprise pricing. Free, Basic, and Pro tiers are for SaaS-only. GitLab offers self-managed and SaaS options at every price point.
### Website
## Resources
- [Codefresh homepage](https://codefresh.io/)
- [Comparison page on their site](https://codefresh.io/continuous-integration/codefresh-versus-gitlabci/)
- [Codefresh GitLab integration](https://codefresh.io/docs/docs/integrations/git-providers/)
### Comments/Anecdotes
## Comments/Anecdotes
- Codefresh makes some claims in their blog comparing themselves to GitLab that are not really accurate.
- "GitlabCI isn’t designed for micro-services since everything is tied to a single project"
- Although we can improve our microservices support, this claim is not true. GitLab has [multi project pipelines](https://docs.gitlab.com/ee/ci/multi_project_pipelines.html) and can [trigger pipelines for mulit-projects via API](https://docs.gitlab.com/ee/ci/triggers/README.html#ci-job-token). In fact, The CI working group for CNCF chose GitLab to run their multi-project multi-cloud pipelines: [CNCF case study](/customers/cncf/), [CNCF video](https://www.youtube.com/watch?time_continue=372&v=Jc5EJVK7ZZk)
......@@ -32,7 +59,9 @@ Codefresh only offers a self-managed option for Enterprise pricing. Free, Basic,
- [Group level Kubernetes clusters](https://gitlab.com/gitlab-org/gitlab-ce/issues/34758)
- [Make container building first class](https://gitlab.com/gitlab-org/gitlab-ce/issues/48913)
### Pricing
## Pricing
- [Codefresh Pricing](https://codefresh.io/pricing/)
- Codefresh prices per build and per concurrent build
- $299 Pro tier is only 3 concurrent builds, to get more you have to call for pricing
## Comparison
......@@ -2,40 +2,36 @@
layout: markdown_page
title: "Atlassian Crucible"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison
#### Features
- link to comparison page <-- comment. delete this line
#### Value/ROI
- link to ROI calc? <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
<!--
## On this page
{:.no_toc}
-->
- TOC
{:toc}
......
......@@ -2,40 +2,36 @@
layout: markdown_page
title: "Gerrit"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison
#### Features
- link to comparison page <-- comment. delete this line
#### Value/ROI
- link to ROI calc? <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
<!--
## On this page
{:.no_toc}
-->
- TOC
{:toc}
......@@ -53,9 +49,6 @@ In contrast, GitLab provides a git server, with issues and issue tracking, as we
* No group ability
* Not intuitive - additional training required for any more complex workflows
## Resources
* [Gerrit website](https://www.gerritcodereview.com/index.html)
* [Gerrit wikipedia](https://en.wikipedia.org/wiki/Gerrit_%28software%29)
......
......@@ -2,37 +2,36 @@
layout: markdown_page
title: "GitHub"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison
- link to comparison page <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
<!--
## On this page
{:.no_toc}
-->
- TOC
{:toc}
......
......@@ -2,36 +2,36 @@
layout: markdown_page
title: "Jenkins"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison
- link to comparison page <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
<!-- ## On this page
## On this page
{:.no_toc}
-->
- TOC
{:toc}
......
......@@ -2,30 +2,31 @@
layout: markdown_page
title: "Jira Software"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison
- link to comparison page <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
......@@ -35,7 +36,7 @@ tact so that others can see where new sections should be added.
- TOC
{:toc}
### Summary
## Summary
Jira Software is an issue tracker and agile project management application.
Portfolio for Jira Portfolio is a separate add-on that enables portoflio management in Jira Software.
Jira Service Desk is a separate application to enable IT and customer service capablilities.
......@@ -47,7 +48,7 @@ Jira is available via 3 deploment models:
- Server: self-managed version that can be deployed on a single server
- Data Center: self-managed version that can be deployed to multiple servers for high availability.
### Comments/Anecdotes
## Comments/Anecdotes
* From [customer comment](https://gitlab.com/gitlab-org/gitlab-ce/issues/50478#note_95584769) on why they won't switch from Jira:
> Probably some of these features could be worked around in GitLab (e.g. by using labels exclusively). In particular for our organization we have been using Jira for much longer than GitLab. Migrating to another issue tracking system for existing project would be less than trivial, i.e. if one wants to maintain the history.
* From [HackerNews JIRA customer](https://news.ycombinator.com/item?id=18145109) about JRA and how it makes their developers feel:
......@@ -55,17 +56,17 @@ Jira is available via 3 deploment models:
- > JIRA makes it dangerously easy to implement overly bureaucratic processes. A certain kind of organization is drawn to it for that reason. Even a healthy organization switching to JIRA can get carried away with the tools now at its disposal.
### Resources
## Resources
* [Jira Software](https://www.atlassian.com/software/jira)
* [Jira Portoflio](https://www.atlassian.com/software/jira/portfolio)
* [Jira Service Desk](https://www.atlassian.com/software/jira/service-desk)
* [Jira Core](https://www.atlassian.com/software/jira/core)
### Integrations
## Integrations
GitLab has [Jira integration](https://about.gitlab.com/features/jira/) that allows Jira Software to be used as an issue tracker for the planning stage while using GitLab for the rest of the DevOps lifecycle: source code managment, CI/CD, and monitoring.
### Pricing
## Pricing
[Jira Software pricing](https://www.atlassian.com/software/jira/pricing)
- Cloud
- Flat $10 per month for up to 10 users
......@@ -94,8 +95,7 @@ GitLab has [Jira integration](https://about.gitlab.com/features/jira/) that allo
- Small teams: $10 One-time payment for up to 10 users
- Growing teams: $13,200 one-time payment (500 users)
### Comparison
[Compare to GitLab](https://about.gitlab.com/comparison/jira-vs-gitlab-ultimate.html)
## Comparison
A few missing features in GitLab that JIRA has from [this comment](https://gitlab.com/gitlab-org/gitlab-ce/issues/50478#note_95584769)
- The concept of "Components" with a configurable set of default assignee's and associate component watchers (this is separate from "Labels", which also exist in Jira)
......
......@@ -3,4 +3,4 @@ layout: markdown_page
title: "Nothing to see here"
---
Nothing to see here. [Move along . . .](/devops-tools/)
Nothing to see here. [Move along . . .](/comparison/)
......@@ -2,33 +2,31 @@
layout: markdown_page
title: "Tool Name"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources
## Resources
- links to communities, etc <-- comment. delete this line
- bulleted list <-- comment. delete this line
### FAQs
## FAQs
- about the product <-- comment. delete this line
### Integrations
### Pricing
## Integrations
## Pricing
- summary, links to tool website <-- comment. delete this line
### Comparison
#### Features
- link to comparison page <-- comment. delete this line
#### Value/ROI
- link to ROI calc? <-- comment. delete this line
### Questions to ask
### Value/ROI
- link to ROI calc? <-- comment. delete this line
## Questions to ask
- positioning questions, traps, etc. <-- comment. delete this line
## Comparison
- features comparison table will follow this <-- comment. delete this line
<!------------------Begin page additions below this line ------------------ -->
......@@ -37,3 +35,5 @@ tact so that others can see where new sections should be added.
- TOC
{:toc}
## Summary
......@@ -2,33 +2,31 @@
layout: markdown_page
title: "Redmine"
---
<!-- This is the template for sections to include and the order to include
them. If a section has no content yet then leave it out. Leave this note in
tact so that others can see where new sections should be added.
### Summary
### Strengths
### Challenges
### Who buys and why
### Comments/Anecdotes
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
## Summary
- minimal requirement <-- comment. delete this line
## Strengths
## Challenges
## Who buys and why
## Comments/Anecdotes
- possible customer issues with product <-- comment. delete this line
- sample benefits and success stories <-- comment. delete this line
- date, source, insight <-- comment. delete this line
### Resources