Bugzilla vs. Google Kubernetes Engine

Buzilla is easy to use and provides basic functionality to use as a bug tracking tool. If big size attachments are allowed it would have been great. Also with Bugzilla home->Test management area is improved by allowing multiple sections it would be awesome!

Incentivized

If your application is complex, if it's planet-scale, or if you need autoscaling, then Kubernetes is best suited. If your application is straightforward, you can opt for App Engine or Cloud Run. In many cases, you can prefer to run the cloud on GKE. But once you deploy on Kubernetes, you get the flexibility to try different things. But if you don't seek flexibility, it's not an option for you.

Incentivized

• Open source! No license fee involved, no limit to the number of licenses.
• Easy to install and maintain. Installation is very easy and hardly needs any maintenance efforts, except when migrating from one version to other. Each project can have its own group of users.
• Includes all the core features/fields that are needed to log a software bug/issue.
• Multiple attachments are possible, supports various formats.
• Good for reporting. Filtering mechanism lets you query bugs by various parameters.

Incentivized

• Engine upgrade rollout strategy - well documented and configurable
• Integration with other Google Cloud services like the Compute Engine, SaaS databases, and some cloud networking like Cloud Armor
• Graphical interface for a lot of operations - either for a quick peek/overview or actual work done by administrators and/or developers (via the Google Cloud Console, for example)

Incentivized

• Cloud Based. I'd like to see bugzilla be cloud based. The company I currently work with made a final decision to change db's for this specific reason. Due to the frequency of travel in this company, they need access to bugzilla from differing national / international locations.
• Larger File Attachments. I believe the limit of a bugzilla content upload is 4 megabytes. For many of our video'd issues, this file size is simply impractical without the additional effort exertion on video compressor applications.

Incentivized

• Support of IPv6.
• Better GitOps.
• A "serverless" Kubernetes so we can install Google config connector will be really awesome.
• Container-native load balancers do not support internal TCP/UDP load balancers or network load balancers.

Incentivized

For future projects I will look at something that is hosted in the cloud that I don't have to manage. I would also like something that has a more modern feel to allow my customers to use it as well as my employees.

Incentivized

This is a pretty straightforward system. You put in the bug details, a ticket is created, the team is notified. The user interface reflects this very simple and straightforward flow. It's certainly much easier than trying to track bugs with using Excel and email.

• Google Kubernetes Engine has a good UI and documentation that facilitates setup and helps get projects moving along quickly
• Its built-in logging integrations with StackDriver make it easier to monitor the application and log issues quickly
• Automated orchestration, deployment, and scaling of nodes and networking are all easily configurable with yaml files

Incentivized

I used it.

Incentivized

I like this rating.

Incentivized

Since it is open source, it doesn't have customer service. However, the amount of information on forums is vast. If you can wade through it, you'll get what you need

Incentivized

Very good Kubernetes distribution with a reasonable total price. Integration with storage and load balancer for ingress and services speed up every process deployment.

Incentivized

I know it.

Incentivized

Implementation was pretty simple. Particularly because the product cannot be customized so there is not much to do apart from getting it up and running.

We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but because the organization was looking for cost savings, we ended up going with Bugzilla and it's FOSS model so as to avoid ongoing costs.

Incentivized

GKE spins up new nodes a LOT faster than AKS. GKE's auto scaler runs a lot smoother than AKS. GKE has a lot more Kubernetes features baked in natively.

Incentivized

I used it

Incentivized

• When issues came up, we reached out to some folks at GCP and they seemed to be very prompt and attentive to our needs. They were always willing to help and provide additional details or recommendations or links to resources. This kind of support is very helpful as it allows us to navigate GKE with more confidence.

Incentivized

• It has made the SDLC process more efficient. Bugs were logged and tracked in emails or in Excel sheets leading to slow communication and at time version issues with multiple files. Being an online tool, Bugzilla solved those issues, improved communication, instant status updates and improved efficiency.
• We have used Bugzilla with a lot of federal goverment agencies (DHS, CMS, SAMHSA, CDC, HHS etc). Project Directors adn Principle Investigators were at times given access to Bugzilla which provided a snapshot of open vs closed issues.
• Some groups would resist using Bugzilla with the email reminders being the main reason. Turning off or reminding them of features where we can 'control' email notification helped a lot.

Incentivized

• Reduced cloud computing costs.
• Easier management of applications.
• Extra time investment to learn how to setup applications in Google versus Amazon.

Incentivized