Crucible vs GitHub

Need advice about which tool to choose?Ask the StackShare community!

Crucible

52
93
+ 1
12
GitHub

189K
155.8K
+ 1
10.2K
Add tool

Crucible vs GitHub: What are the differences?

Developers describe Crucible as "Review code, discuss changes, share knowledge, and identify defects". Review code, discuss changes, share knowledge, and identify defects with Crucible's flexible review workflow. It's code review made easy for Subversion, CVS, Perforce, and more. On the other hand, GitHub is detailed as "Powerful collaboration, review, and code management for open source and private development projects". GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

Crucible and GitHub are primarily classified as "Code Review" and "Code Collaboration & Version Control" tools respectively.

Some of the features offered by Crucible are:

  • Workflow-based reviews
  • Quick reviews with cut-and-paste snippets
  • Create reviews from the command line

On the other hand, GitHub provides the following key features:

  • Command Instructions
  • Source Browser
  • Git Powered Wikis

"JIRA Integration" is the top reason why over 4 developers like Crucible, while over 1750 developers mention "Open source friendly" as the leading cause for choosing GitHub.

According to the StackShare community, GitHub has a broader approval, being mentioned in 4647 company stacks & 5874 developers stacks; compared to Crucible, which is listed in 11 company stacks and 4 developer stacks.

Decisions about Crucible and GitHub
Elmar Wouters
CEO, Managing Director at Wouters Media · | 7 upvotes · 197K views

I first used BitBucket because it had private repo's, and it didn't disappoint me. Also with the smooth integration of Jira, the decision to use BitBucket as a full application maintenance service was as easy as 1, 2, 3.

I honestly love BitBucket, by the looks, by the UI, and the smooth integration with Tower.

See more
Weverton Timoteo

Do you review your Pull/Merge Request before assigning Reviewers?

If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:

  • Pick the correct target branch
  • Make Drafts explicit
  • Name things properly
  • Ask help for tools
  • Remove the noise
  • Fetch necessary data
  • Understand Mergeability
  • Pass the message
  • Add screenshots
  • Be found in the future
  • Comment inline in your changes

Read the blog post for more detailed explanation for each item :D

What else do you review before asking for code review?

See more
Weverton Timoteo

Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.

SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.

As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?

See more
Weverton Timoteo

One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.

It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.

See more
Kamaleshwar BN
Head of Engineering at Dibiz Pte. Ltd. · | 8 upvotes · 338.5K views

Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.

See more

Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!

See more
Nazar Atamaniuk
Shared insights
on
DeployPlaceDeployPlaceGitHubGitHubGitLabGitLab

At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Crucible
Pros of GitHub
  • 5
    JIRA Integration
  • 4
    Post-commit preview
  • 2
    Has a linux version
  • 1
    Pre-commit preview
  • 1.8K
    Open source friendly
  • 1.5K
    Easy source control
  • 1.2K
    Nice UI
  • 1.1K
    Great for team collaboration
  • 861
    Easy setup
  • 501
    Issue tracker
  • 484
    Great community
  • 480
    Remote team collaboration
  • 448
    Great way to share
  • 441
    Pull request and features planning
  • 144
    Just works
  • 130
    Integrated in many tools
  • 116
    Free Public Repos
  • 110
    Github Gists
  • 108
    Github pages
  • 81
    Easy to find repos
  • 60
    Open source
  • 58
    Easy to find projects
  • 56
    Network effect
  • 55
    It's free
  • 47
    Extensive API
  • 42
    Organizations
  • 41
    Branching
  • 33
    Developer Profiles
  • 32
    Git Powered Wikis
  • 29
    Great for collaboration
  • 23
    It's fun
  • 22
    Community SDK involvement
  • 21
    Clean interface and good integrations
  • 19
    Learn from others source code
  • 14
    It integrates directly with Azure
  • 14
    Because: Git
  • 13
    Wide acceptance
  • 10
    Large community
  • 9
    Newsfeed
  • 9
    Standard in Open Source collab
  • 8
    It integrates directly with Hipchat
  • 7
    Beautiful user experience
  • 7
    Fast
  • 6
    Easy to discover new code libraries
  • 6
    Cloud SCM
  • 5
    Graphs
  • 5
    Smooth integration
  • 5
    Nice API
  • 5
    Integrations
  • 5
    It's awesome
  • 4
    Remarkable uptime
  • 4
    Hands down best online Git service available
  • 4
    Reliable
  • 3
    Easy to use and collaborate with others
  • 3
    CI Integration
  • 3
    Free HTML hosting
  • 3
    Loved by developers
  • 3
    Quick Onboarding
  • 3
    Security options
  • 3
    Simple but powerful
  • 3
    Uses GIT
  • 3
    Unlimited Public Repos at no cost
  • 3
    Version Control
  • 2
    Nice to use
  • 1
    Free private repos
  • 1
    Easy deployment via SSH
  • 1
    Beautiful
  • 1
    Owned by micrcosoft
  • 1
    Free HTML hostings
  • 1
    Self Hosted
  • 1
    All in one development service
  • 1
    Easy to use
  • 1
    Good tools support
  • 1
    Easy source control and everything is backed up
  • 1
    Leads the copycats
  • 1
    Never dethroned
  • 1
    Ci
  • 1
    Issues tracker
  • 1
    Easy and efficient maintainance of the projects
  • 1
    IAM
  • 1
    IAM integration
  • 0
    Profound
  • 0
    1

Sign up to add or upvote prosMake informed product decisions

Cons of Crucible
Cons of GitHub
    Be the first to leave a con
    • 46
      Owned by micrcosoft
    • 36
      Expensive for lone developers that want private repos
    • 15
      Relatively slow product/feature release cadence
    • 10
      API scoping could be better
    • 8
      Only 3 collaborators for private repos
    • 3
      Limited featureset for issue management
    • 2
      GitHub Packages does not support SNAPSHOT versions
    • 1
      Have to use a token for the package registry
    • 1
      No multilingual interface
    • 1
      Takes a long time to commit

    Sign up to add or upvote consMake informed product decisions

    What is Crucible?

    It is a Web-based application primarily aimed at enterprise, and certain features that enable peer review of a code base may be considered enterprise social software.

    What is GitHub?

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Crucible?
    What companies use GitHub?
    See which teams inside your own company are using Crucible or GitHub.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Crucible?
    What tools integrate with GitHub?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Dec 8 2020 at 5:50PM

    DigitalOcean

    GitHubMySQLMongoDB+11
    2
    1862
    GitHubOptimizelySegment+3
    2
    1018
    Mar 18 2020 at 9:12AM

    LaunchDarkly

    GitHubLaunchDarkly+2
    6
    950
    JavaScriptGitHubReact+12
    5
    3531
    GitHubDockerReact+17
    34
    30408
    What are some alternatives to Crucible and GitHub?
    Bitbucket
    Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
    Forge
    Fastest possible way to host lighting-fast static websites for small businesses, web startups, and app developers.
    Fisheye
    FishEye provides a read-only window into your Subversion, Perforce, CVS, Git, and Mercurial repositories, all in one place. Keep a pulse on everything about your code: Visualize and report on activity, integrate source with JIRA issues, and search for commits, files, revisions, or people.
    ESLint
    A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
    Prettier
    Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary.
    See all alternatives