Apache Archiva vs. GitHub

Well suited for small organizations to medium-sized teams/organizations. Apache Archiva is well suited for:

• It acts as a central repository/proxy of the artifacts generated and used by the teams.
• It provides control on which open source repositories can be utilized by the team.
• Saves network bandwidth by reducing outbound traffic.

Apache Archiva is less appropriate for organizations where immediate support/bug resolutions are required.

Incentivized

GitHub is well suited for software development, GitHub is particularly well suited for software development projects, where teams need to collaborate on code, track changes, and review code changes. Also for open-source projects, GitHub is an ideal platform for open-source projects, where teams of developers from all over the world can collaborate on code and contribute to projects. For documentation, GitHub provides a platform for creating and sharing documentation, making it an ideal solution for teams that need to create and maintain documentation. On small and medium-sized teams GitHub is well suited as those teams that need to collaborate on software projects and track changes to their code.

• It's an open source project and therefore saves cost.
• It allows exchange of artifacts/libraries between different teams.
• It allows managing internal and external repositories with ease.

Incentivized

• As a repository it's great. It houses almost all the open-source applications/code that anyone can fork and play with. A huge collection of sample codes available with problem statements across different domains make Github a one-stop location.
• I use GitHub with Windows and the Git Bash is superb. It [is] a powerful alternative to the Command Prompt and Powershell. Allows me to run shell scripts and UNIX commands inside the terminal [on] a Windows PC.
• GitHub integration with almost all cloud development/deployment platforms is amazing. Deploying a new application in Azure is really smooth. Just link the GitHub repositories and it's good to go. From automatic build to deployment everything is just amazing.

• Muti-tenancy was hard to achieve.
• UI can be improved. Its seems bit dated.
• It is a bit tricky to setup.

Incentivized

• When browsing history of a file, GitHub could make it easier to see the file after a particular commit instead of just being able to quickly view the commit. I'd like to be able to see the commit or the file itself in one click.
• I would like to be able to view commits by user.
• I would love to be able to traverse code on GitHub (go to definition, etc) - the good news here is that they are working on these features!

Incentivized

GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.

- Easy to use compared to other version control software. UI interface makes it easy to use, as well as protects against making a major mistake by deleting code, etc. - UI looks modern. - Support for multiple platforms, which I assume will only get better with time. - Student benefits are awesome! - The size limitations on their repositories make sense to me. Not too crazy but realistic from a business perspective.

Incentivized

It's a testament to how easy it is to use GitHub and how many others use it that you can pretty much find the answer to any problem you have by searching online. Consequently, I've never needed to use their support. It's an incredibly easy tool to set up initially, so it won't require much onboarding expertise to get started.

Incentivized

• Apache Archiva is a great choice for organizations with a limited budget.
• Alternatives are expensive to acquire Archiva comes offers REST API(s) which allows the creation of customized UI.
• With Apache Archiva, it is easy to manage the remote proxy repositories.
• RBAC helps with managing user access to the repository.
• Configuration can be achieved using UI and stored in archiva.xml.
• Backup of configuration is quite simple.

Incentivized

At the time to evaluation - Bitbucket was very tightly integrated into Atlassian’s suite of tools. For an organization that is starting out and looking to spend limited funds effectively - the cost/benefit of using that suite of tools usually doesn’t make sense. Granted things may have changed since then (its been over 5 years) - but at the time GitHub was effective - and all prospective engineers knew about it and already had accounts. This made it very easy to add to the organization and not lose time in training, etc. Developers seem to really love GitHub above most other tools out there - so that plays into the decision making as well.

Incentivized

• The impact of Apache Archiva on ROI has been positive. Since it is open source. It is free.
• It has allowed teams to store artifacts centrally, thus leading to a reduced need for multiple servers
• Security audits can be easily performed on the artifacts.

Incentivized

• Github has increased our rate of code development, increasing our publishing rate. This helps bring attention to the research we are doing and ultimately brings in more funding for further research.
• Because GitHub makes my team more efficient, we are able to put more hours into code development / report writing rather than agonizing over different versions of code created without version control software.
• We use a paid version of GitHub, because we work through private repositories, but the increase in productivity, efficiency, and research progress is definitely worth the price.

Incentivized