The Bazaarvoice platform provides businesses
with the ability to collect and publish authentic feedback from their
customers, who can review products and services, ask questions, and post photos
and videos of their experiences with products. The vendor says that leveraging
user-generated content can increase sales and build brand loyalty. Within the platform, the vendor provides seven core modules: Ratings & Reviews Questions & Answers Sampling…
N/A
GitHub
Score 9.1 out of 10
N/A
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$4
per month per user
Jenkins
Score 8.4 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
Microsoft Team Foundation Server was too heavy and too complex for fast dvelopment. The integration with opensource build solutions (i.e jenkins) was not explored but the main feedback on this tool was its complexity. CVS and SVN used to be standards in past years and fit …
Bitbucket supports Mercurial VCS in addition to Git. Since it is an Atlassian product, Bitbucket is very well integrated with the company's other tools, like JIRA (which is widely used in the development industry), Jenkins, and Bamboo. It offers many of the same features as …
Bitbucket has an interface that is much uglier and much more confusing to use. The learning curve is therefore much greater with Bitbucket. However, Bitbucket allows for free private repositories for small teams, which is a huge plus, and if your team is small enough, that …
GitLab CI and GitHub Actions are other powerful options in the market also with a rising popularity and high interoperability with their respective platform. But Jenkins is still a good option for complex pipelines that require scripting and logic. Also, Jenkins uses as runtime …
Verified User
Engineer
Chose Jenkins
Jenkins is highly customizable and flexible, supporting a wide range of plugins and integrations. Jenkins works with any version control system (Git, Subversion, etc.). Jenkins has a more mature ecosystem, and it may be better for large-scale, complex environments, especially …
I have used Spinnaker as a CD tool. Though it's a very powerful CD tool we still needed Jenkins for CI, so to save some hassle for us we opt Jenkins solely.
Both Jenkins and TeamCity do a good job of automating CI/CD. Jenkins runs much leaner than TeamCity - it only needs about a Gig of free memory, whereas TeamCity needs a fat 4 Gig free. Many tasks in Jenkins yml config can be very cumbersome, especially running local and …
Jenkins has been my favorite continuous integration tool I've used. It's easy to setup, intuitive to use, and very powerful. The software allows for building complex workflows, then having them run without thinking about it. This leads to savings in time and resources, and to …
When looking for alternatives for Jenkins we found CircleCI and TeamCity are good too. Jenkins was considered for reasons like it has a wide variety of plugins which integrate well with any kind of system. And its ease of use.
One of the other greater advantage is it is open …
TeamCity is another viable option for Continuous Integration/Development. We picked Jenkins in this case because there was a lot of support for Amazon CloudFormation and other AWS integrations which fit the task at hand. For just straight compiling Microsoft based builds, TeamCi…
Jenkins immense flexibility and its large and impressive selection of available community-driven plugins makes it ideal choice for solving non-traditional problems.
However, for CI/CD - consider the benefit of modern tools that enforce reusable, infrastructure as code design …
Travis CI and AppVeyor are good services that provide rudimentary support for builds, but they focus on Linux/OSX and Windows respectively, meaning that cross-platform builds will need to use both services. They are free for open source projects on GitHub, so they are seen …
Jenkins provides bare metal framework that people would be able to use and transform to their needs. In a lot of other cases, there are lot of configurations already available which make the softwares heavy ended and less customizable. Also, there are a lot of open source …
Jenkins is ideal for developing software with high-security demands. It is hosted and set up locally and has no outside connections. But these pros could become cons when you work on open source projects and need to waste time for initial setup and maintenance over a project's …
Bazaarvoice is overall a quite strong ratings and reviews platform. If you have a national brand and want to integrate ratings and reviews into your website, Bazaarvoice should be in your consideration set. If you have a small business or a tighter budget, you may find Bazaarvoice too robust or expensive of a platform. If your brand gets a lot of organic product reviews, Bazaarvoice will be a helpful tool to increase brand credibility and search engine rankings. If you need help getting consumers to review your products, Bazaarvoice offers sampling programs. These programs can get very pricy depending on how many SKUs you are looking for reviews on. Bazaarvoice also has a proprietary platform where they collect consumer reviews for many brands, and once you have the Bazaarvoice ratings and reviews platform, you may be able to purchase reviews of your products and have them sync to your website without having to run a sampling program.
GitHub is an easy to go tool when it comes to Version Controlling, CI/CD workflows, Integration with third party softwares. It's effective for any level of CI/CD implementation you would like to. Also the the cost of product is also very competitive and affordable. As of now GitHub lacks capabilities when it comes to detailed project management in comparison to tools like Jira, but overall its value for money.
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Bazaarvoice Curations makes it incredibly easy to pull in content from multiple social media platforms for us to review.
Once the content is pulled into the Curations dashboard, our marketing team can very easily scroll through all the images and decide which ones we would like to feature on our site.
Curations also makes it very easy to tag any of our products in the images. We are able to do this manually, but Bazaarvoice also offers the option of letting their team tag the products they see in our images.
Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
Their login to their portal is awful. They are working on creating a single sign on experience but right now there are different usernames and passwords depending on what dashboard you are attempting to access.
They could probably spend more time optimizing the cost of their initialization script. The size of the JavaScript concerns me.
They could work on their deployment and preview tools. The time for our staged changes to show on the live site doesn't seem to be as quick as it should be and the preview tools don't take into account the site's CSS files for display.
Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
We are happy with the product and really just need to optimise our deployment of it on an ongoing basis. There is a lot of functionality prebuilt within Bazaarvoice which we want to have on our site, and to recreate this in our platform would take significant effort which is not practical for us.
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.
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
I'm sure all processes and program can improve, however Bazaarvoice has reached a very easy usability level and hope this continues as the product improves over time.
GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
The Bazaarvoice team is always available via call, email, or any other platform to provide help, guidance, or to push or ask for the task we set earlier. They are talkative and easy to share information and discuss issues if there are any. Thay may have more out of box solutions for easy implementation, but as a whole, and regarding support I am satisfied.
There are a ton of resources and tutorials for GitHub online. The sheer number of people who use GitHub ensures that someone has the exact answer you are looking for. The docs on GitHub itself are very thorough as well. You will often find an official doc along with the hundreds of independent tutorials that answers your question, which is unusual for most online services.
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
Even though both PowerReviews and Bazaar Voice are capable of fulfilling the aforementioned needs, PowerReviews also provides free trials. PowerReview's style options aren't always user-friendly, but the app is worth checking out if aesthetic concerns aren't top of mind. Bazaar Voice, on the other hand, sounds really professional and is remarkably simple to use.
While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their integration will likely be much tighter. Gitlab on the other hand has a reputation as a very capable GitHub replacement with some features that are not available on GitHub like firewall tools.
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
This has had a positive impact on the way the company identifies user issues and complaints more easily/readily.
The negative impact is that departments seem to put a lot more expectations on our customers than this tool can provide (e.g., replies and follow-up), meaning that we aren't as able to provide additional information when requested.
It's uncertain whether responding to reviews adds a lot of value when all is said and done. Reviewers rarely adjust their ratings, even if/when we sufficiently address their concerns or resolve issues.
Team collaboration significantly improved as everything is clearly logged and maintained.
Maintaining a good overview of items will be delivered wrt the roadmap for example.
Knowledge management and tracking. Over time a lot of tickets, issues and comments are logged. GitHub is a great asset to go back and review why x was y.
