In April 2000, Weissman handed over control of the Bugzilla project to Tara Hernandez. īugzilla 2.0 was the result of that port to Perl, and the first version was released to the public via anonymous CVS. Bugzilla was originally written in Tcl, but Weissman decided to port it to Perl before its release as part of Netscape's early open-source code drops, in the hope that more people would be able to contribute to it, given that Perl seemed to be a more popular language at the time. History īugzilla was originally devised by Terry Weissman in 1998 for the nascent project, as an open source application to replace the in-house system then in use at Netscape Communications for tracking defects in the Netscape Communicator suite. Red Hat uses it, but is gradually migrating its product to use Jira. Bugzilla is used, among others, by the Mozilla Foundation, WebKit, Linux kernel, FreeBSD, KDE, Apache, Eclipse and LibreOffice. Released as open-source software by Netscape Communications in 1998, it has been adopted by a variety of organizations for use as a bug tracking system for both free and open-source software and proprietary projects and products. For more information, refer to mw:Phabricator/versus Bugzilla.Bugzilla is a web-based general-purpose bug tracking system and testing tool originally developed and used by the Mozilla project, and licensed under the Mozilla Public License. Requests to are redirected to either or. In November 2014, Wikimedia migrated from Bugzilla to Phabricator. Gerrit Notification Bot (Bugzilla–Gerrit integration via Gerrit's hooks-bugzilla).It is recommended to use Bugzilla's JSON or XML RPC API. Installation instructions - Note: The defunctional Bugzilla REST API was removed in August 2013 (see RT #5582). sudo contrib/ archived information Notes.do a dry run and make sure "-p0" is the right thing (look at file pathes in patch file relative to current dir).cd to /srv/org/wikimedia/bugzilla and copy the.scp the file over to "kaulen" and login via ssh.diff file including the patch, for example from hexmode, the bugmeister Testing patches: See instructions for Bugzilla Labs instanceĬurrently patches are still applied manually, but this should be changed soon.Change the product of the affected Bugzilla ticket.Now that we have moved from Bugzilla to Phabricator: When a ticket that was in a public Bugzilla product needs to be moved into the Security product in Bugzilla (to reflect the situation of the corresponding ticket in Phabricator which also got access restricted), the following steps need to be performed: Moving a ticket to Security product in old-bugzilla Now that Bugzilla is read-only (though you can still log in to old-bugzilla to access your votes or saved searches) after the move to Phabricator in November 2014, such actions are unlikely to be needed anymore. The account allows marking specific comments and attachments as private, and banning specific users (by going to "Administration -> Users"). The credentials are on fenari under /home/wikipedia/doc/bugzilla. We have a shared admin account root users can use for emergencies. Most users had their admin rights revoked to ease coordination and for security reasons, see wmf:Bugzilla administrator rights policy. Restore the MySQL database from the backup dump. ![]() Move the backed up Bugzilla back to its original location.Its a good thing we backed up our database and Bugzilla 3.0.8 home directory as part of the upgrade This cron job is currently set up to run once an hour at 15 past the hour. More information on this is available in Section 2.3.3. With custom templates and tweaks in the Git repository wikimedia/bugzilla/modifications.gitįor whining to work, a special Perl script must be executed at regular intervals.zirconium - web frontend (since 02/2014 before kaulen).6.1 Moving a ticket to Security product in old-bugzilla.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |