Jump to: navigation, search

Difference between revisions of "Mylyn/Bugzilla Connector"

(Preventing excessive logfile fill up)
(Preventing excessive logfile fill up)
Line 3: Line 3:
 
=== Bugzilla Server Optimization ===
 
=== Bugzilla Server Optimization ===
 
* [[Cached Repository Configuration]] - This page describs the solution taken by Eclipse.org webmasters to reduce the bandwidth requirements due to Mylyn clients updating their repository configuration.
 
* [[Cached Repository Configuration]] - This page describs the solution taken by Eclipse.org webmasters to reduce the bandwidth requirements due to Mylyn clients updating their repository configuration.
 +
 +
===GZIP encoding and content negotiation===
 +
The Mylyn Bugzilla Connector has been modified to accept gzip encoding on all requests, and will do content negotiation. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=205708 bug 205708].
  
 
=== Preventing excessive logfile fill up ===
 
=== Preventing excessive logfile fill up ===

Revision as of 03:32, 27 November 2007


Bugzilla Server Optimization

  • Cached Repository Configuration - This page describs the solution taken by Eclipse.org webmasters to reduce the bandwidth requirements due to Mylyn clients updating their repository configuration.

GZIP encoding and content negotiation

The Mylyn Bugzilla Connector has been modified to accept gzip encoding on all requests, and will do content negotiation. See bug 205708.

Preventing excessive logfile fill up

  • When running /bugzilla/ locally, one can prevent Mylyn filling up the log files by adding this to httpd.conf:

<DirectoryMatch /bugzilla/ >
    BrowserMatchNoCase mylyn mylyn=1
</DirectoryMatch>
CustomLog "/private/var/log/httpd/access_log" combined env=!mylyn

Users

Developer Resources

Mylyn Offline Refactoring