|
|
| (12 intermediate revisions by 9 users not shown) |
| Line 1: |
Line 1: |
| =General Questions=
| | See [[Bugzilla:FAQ#General_Questions]]. |
| ==What license is Bugzilla distributed under?==
| |
| Bugzilla is covered by the Mozilla Public License.
| |
| See details at http://www.mozilla.org/MPL/. | |
| | |
| ==How do I get commercial support for Bugzilla?==
| |
| http://www.bugzilla.org/support/consulting.html is a list of companies and individuals who have asked us to list them as consultants for Bugzilla.
| |
| | |
| There are several experienced Bugzilla hackers on the mailing list/newsgroup who are willing to make themselves available for generous compensation.
| |
| Try sending a message to the mailing list asking for a volunteer.
| |
| | |
| ==What major companies or projects are currently using Bugzilla for bug-tracking?==
| |
| | |
| There are dozens of major companies with public Bugzilla sites to track bugs in their products.
| |
| We have a fairly complete list available on our website at http://bugzilla.org/installation-list/.
| |
| If you have an installation of Bugzilla and would like to be added to the list, whether it's a public install or not, simply e-mail Gerv <gerv@mozilla.org>.
| |
| | |
| ==Who maintains Bugzilla?==
| |
| A [http://www.bugzilla.org/developers/profiles.html core team], led by Dave Miller (justdave@bugzilla.org).
| |
| | |
| ==How does Bugzilla stack up against other bug-tracking databases?==
| |
| We can't find any head-to-head comparisons of Bugzilla against other defect-tracking software.
| |
| If you know of one, please get in touch.
| |
| In the experience of Matthew Barnson (the original author of this FAQ), though,
| |
| Bugzilla offers superior performance on commodity hardware, better price (free!),
| |
| more developer-friendly features (such as stored queries, email integration,
| |
| and platform independence), improved scalability, greater flexibility,
| |
| and superior ease-of-use when compared to commercial bug-tracking software.
| |
| | |
| If you happen to be a vendor for commercial bug-tracking software,
| |
| and would like to submit a list of advantages your product has over Bugzilla,
| |
| simply send it to <documentation@bugzilla.org>
| |
| and we'd be happy to include the comparison in our documentation.
| |
| | |
| ==Why doesn't Bugzilla offer this or that feature or compatibility with this other tracking software?==
| |
| It may be that the support has not been built yet,
| |
| or that you have not yet found it.
| |
| While Bugzilla makes strides in usability, customizability, scalability,
| |
| and user interface with each release,
| |
| that doesn't mean it can't still use improvement!
| |
| | |
| The best way to make an enhancement request is to file a bug at
| |
| [https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla bugzilla.mozilla.org]
| |
| and set the Severity to 'enhancement'.
| |
| Your 'request for enhancement' (RFE) will start out in the UNCONFIRMED state,
| |
| and will stay there until someone with the ability to CONFIRM the bug reviews it.
| |
| If that person feels it to be a good request that fits in
| |
| with Bugzilla's overall direction, the status will be changed to NEW;
| |
| if not, they will probably explain why and set the bug to RESOLVED/WONTFIX.
| |
| If someone else has made the same (or almost the same) request before,
| |
| your request will be marked RESOLVED/DUPLICATE,
| |
| and a pointer to the previous RFE will be added.
| |
| | |
| Even if your RFE gets approved,
| |
| that doesn't mean it's going to make it right into the next release;
| |
| there are a limited number of developers,
| |
| and a whole lot of RFEs... some of which are quite complex.
| |
| If you're a code-hacking sort of person,
| |
| you can help the project along by making a patch yourself
| |
| that supports the functionality you require.
| |
| If you have never contributed anything to Bugzilla before,
| |
| please be sure to read the Developers' Guide and Contributors' Guide
| |
| before going ahead.
| |
| | |
| ==Why MySQL? I'm interested in seeing Bugzilla run on PostgreSQL/Sybase/Oracle/Msql/MSSQL==
| |
| MySQL was originally chosen because it is free, easy to install,
| |
| and was available for the hardware Netscape intended to run it on.
| |
| | |
| There is currently work in progress to make Bugzilla work on PostgreSQL;
| |
| track the progress of this initiative in [https://bugzilla.mozilla.org/show_bug.cgi?id=98304 bug 98304].
| |
| | |
| Sybase support is no longer being worked on.
| |
| Even if it eventually happens,
| |
| it's VERY unlikely to work without the end-user-company
| |
| having to stick a few developers on making several manual changes.
| |
| Sybase is just NOT very standards-compliant (despite all the hype),
| |
| and it turned out that way too much had to be changed to make it work --
| |
| like moving half of the application logic into stored procedures
| |
| to get any kind of decent performance out of it.
| |
| [https://bugzilla.mozilla.org/show_bug.cgi?id=173130 Bug 173130] is the relevant bug. | |
| | |
| Red Hat once ran a version of Bugzilla that worked on Oracle,
| |
| but that was long, long ago; that version (Bugzilla 2.8) is now obsolete,
| |
| insecure, and totally unsupported.
| |
| Red Hat's current Bugzilla (based on Bugzilla 2.17.1) uses PostgreSQL,
| |
| and work is being done to merge those changes into the main distribution.
| |
| (See above.) At this time we know of no recent ports of Bugzilla to Oracle.
| |
| (In our honest opinion, Bugzilla doesn't need what Oracle offers.)
| |
| | |
| [https://bugzilla.mozilla.org/show_bug.cgi?id=237862 Bug 237862] is a good bug to read through if you'd like to see
| |
| what progress is being made on general database compatibility.
| |
| | |
| ==What is /usr/bonsaitools/bin/perl?==
| |
| Bugzilla used to have the path to perl on the shebang line
| |
| set to /usr/bonsaitools/bin/perl because when Terry first started
| |
| writing the code for mozilla.org he needed a version of Perl
| |
| and other tools that were completely under his control.
| |
| This location was abandoned for the 2.18 release in favor of
| |
| the more sensible /usr/bin/perl.
| |
| If you installed an older version of Bugzilla
| |
| and created the symlink we suggested, you can remove it now
| |
| (provided that you don't have anything else, such as Bonsai,
| |
| using it and you don't intend to reinstall an older version of Bugzilla).
| |
| | |
| ==My perl is located at /usr/local/bin/perl and not /usr/bin/perl. Is there an easy to change that in all the files that have this hard-coded?==
| |
| The easiest way to get around this is to create a link from one to the other:
| |
| '''ln -s /usr/local/bin/perl /usr/bin/perl'''.
| |
| If that's not an option for you, the following bit of perl magic will change
| |
| all the shebang lines (that is to say,
| |
| the line at the top of each file that starts with '#!' and contains the path)
| |
| to something else:
| |
| | |
| perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl
| |
| | |
| Sadly, this command-line won't work on Windows unless you also have Cygwin.
| |
| However, MySQL comes with a binary called replace which can do the job:
| |
| | |
| C:\mysql\bin\replace "#!/usr/bin/perl" "#!C:\perl\bin\perl" -- *.cgi *.pl
| |
| | |
| If your perl path is something else again,
| |
| just follow the above examples and replace /usr/local/bin/perl with your own perl path.
| |
| | |
| Once you've modified all your files,
| |
| you'll also need to modify the t/002goodperl.t test,
| |
| as it tests that all shebang lines are equal to /usr/bin/perl.
| |
| (For more information on the test suite, please check out
| |
| the appropriate section in the Developers' Guide.)
| |
| Having done this, run the test itself:
| |
| | |
| perl runtests.pl 2 --verbose
| |
| | |
| | |
| to ensure that you've modified all the relevant files.
| |
| | |
| If using Apache on Windows, you can avoid the whole problem
| |
| by setting the ScriptInterpreterSource directive to 'Registry'.
| |
| (If using Apache 2 or higher, set it to 'Registry-Strict'.)
| |
| ScriptInterperterSource requires a registry entry
| |
| "HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command" to associate .cgi files
| |
| with your perl executable.
| |
| If one does not already exist,
| |
| create it with a default value of "<full path to perl> -T",
| |
| e.g. "C:\Perl\bin\perl.exe -T".
| |
| | |
| ==Is there an easy way to change the Bugzilla cookie name?==
| |
| At present, no.
| |
| | |
| ==Does bugzilla run under mod_perl?==
| |
| At present, no.
| |
| Work is slowly taking place to remove global variables, use $cgi, and use DBI.
| |
| These are all necessary for mod_perl (as well as being good for other reasons).
| |
| Visit [https://bugzilla.mozilla.org/show_bug.cgi?id=87406 bug 87406]
| |
| to view the discussion and progress.
| |
| | |
| =[[Bugzilla:FAQ:Managerial_Questions|Managerial Questions]]=
| |
| =[[Bugzilla:FAQ:Administrative_Questions|Administrative Questions]]=
| |
| =[[Bugzilla:FAQ:Bugzilla_Security|Bugzilla Security]]=
| |
| =[[Bugzilla:FAQ:Bugzilla_Email|Bugzilla Email]]=
| |
| =[[Bugzilla:FAQ:Bugzilla_Database|Bugzilla Database]]=
| |
| =[[Bugzilla:FAQ:Bugzilla_and_Win32|Bugzilla and Win32]]=
| |
| =[[Bugzilla:FAQ:Bugzilla_Usage|Bugzilla Usage]]=
| |
| =[[Bugzilla:FAQ:Bugzilla_Hacking|Bugzilla Hacking]]=
| |