Eclipse Bugzilla

Eclipse Bugzilla
Name	Eclipse Bugzilla
Developer	Eclipse Foundation
Released	2001
Programming language	Perl, JavaScript
Repository	Eclipse Bugzilla
License	MPL/GPL/LGPL

Eclipse Bugzilla is the issue-tracking installation historically used by the Eclipse Foundation to manage defects, enhancements, and project tasks across the Eclipse ecosystem. It served as a centralized database for projects such as Eclipse IDE, Jetty (web server), Eclipse Che, Jakarta EE, and related technologies, enabling coordinated development among contributors from organizations like IBM, Red Hat, Oracle Corporation, and Google. The system interfaced with continuous integration services, code review tools, and mailing lists to support collaboration between vendors, academic contributors, and independent committers.

History

Eclipse Bugzilla originated as a deployment of the Bugzilla platform adapted for the needs of the Eclipse Foundation and related projects. Early adoption tied to the launch of the Eclipse IDE project after the IBM-led initial donation and formation of the Eclipse Consortium, aligning with governance practices later formalized under the Eclipse Foundation umbrella. Over time the deployment evolved alongside major software projects including Eclipse Platform, Eclipse Modeling Framework, PDT (PHP Development Tools), Mylyn, and Eclipse CDT. The lifecycle of tickets often intersected with events such as EclipseCon, FOSDEM, and vendor roadmaps from SAP, Tasktop Technologies, and IntelliJ IDEA (JetBrains), reflecting contributions from corporate engineering teams, open source contributors, and academic partners like University of Toronto and ETH Zurich.

Architecture and Features

The Bugzilla installation combined the core Bugzilla Perl backend with customizations to integrate authentication, product/component taxonomy, and workflow policies used by projects such as Eclipse Platform, Equinox, and EMF. It provided extensions for single sign-on linked to LDAP, SAML, and project contributor accounts from organizations like GitHub and GitLab. Features included custom fields for tracking CVE references, attachments integrating with Maven Central and Bintray, and metadata consumed by build systems like Jenkins, Travis CI, and Azure Pipelines. The schema supported relationships leveraged by tools such as JIRA imports, Phabricator conversions, and cross-references with Mailing lists and IRC logs. For scalability, the deployment used database engines comparable to MySQL, PostgreSQL, and mirrored indices for search systems like Elasticsearch and Apache Solr.

Workflow and Usage

Contributors created and triaged reports aligned to products and components associated with major projects such as Eclipse IDE, Eclipse JDT, Eclipse RCP, Eclipse Plug-in Development Environment, and Tycho builds. Typical workflows involved reporters, assignees, committers, and release managers from entities like IBM, Red Hat, Oracle Corporation, and independent developers affiliated via GitHub or GitLab. Integration with continuous integration tools such as Jenkins triggered automated tests that updated bug statuses; cross-references with Git commits, SVN repositories, and Gerrit code reviews provided traceability. Release engineering practices coordinated across Eclipse Project Management Committee and alignment with OSGi specifications and Jakarta EE milestones.

Integration and Tooling

Eclipse’s Bugzilla deployment worked with a spectrum of tooling: source control systems including Git, Subversion, and CVS; CI/CD platforms like Jenkins, Travis CI, and GitLab CI; and code review systems such as Gerrit and Phabricator. Issue data was consumed by project dashboards, release notes, and downstream consumers like Maven Central and Docker Hub automation. Integrations also touched ecosystem products such as Eclipse Marketplace, Eclipse Che, Eclipse Theia, and commercial IDEs from JetBrains and Microsoft (Visual Studio), while analytics tooling used exports for Grafana, Prometheus, and Kibana visualizations. Third-party migration and synchronization tools facilitated transfers to platforms like JIRA and GitHub Issues used by companies including Atlassian and GitHub, Inc..

Governance and Community

Governance of the Bugzilla deployment fell under the Eclipse Foundation operational teams and project leads from working groups including the Eclipse Project Management Committee and various project PMC equivalents. Community roles included committers, project leads, release engineers, and contributors from organizations like IBM, Red Hat, SAP, Oracle Corporation, Google, and independent open source contributors. Collaboration extended to community events such as EclipseCon, Open Source Summit, and regional meetups, with policy inputs influenced by licensing considerations like the Eclipse Public License and interactions with standards bodies such as OSGi Alliance and Apache Software Foundation projects.

Notable Incidents and Criticisms

The Bugzilla deployment attracted scrutiny over usability, search capabilities, and the volume of legacy issues originating from long-lived projects like Eclipse Platform and Eclipse CDT. Migration debates compared Bugzilla to alternatives favored by companies such as Atlassian (with JIRA) and platforms like GitHub Issues and GitLab Issues. Incidents included synchronization challenges during large-scale imports, historical ticket data quality concerns highlighted at events like EclipseCon, and discussions about modernization driven by vendors including Red Hat and IBM. Criticisms touched on workflow rigidity versus agile practices promoted by communities at FOSDEM and Open Source Summit, leading to eventual migrations and parallel adoption of issue trackers across projects such as Eclipse Che, Jakarta EE, and independent foundations.

Category:Eclipse Foundation projects