codeBeamer 6.0.3 and higher have build in Smart HTTP support thus no apache installation is required any more. Accessing Mercurial via Apache is deprecated and not supported.
Table of Contents
Configuring Smart HTTP for Mercurial on WindowsTo be able to use Smart HTTP on windows you have to execute the folliowing steps:
Configuring Apache for MercurialAccessing Mercurial Repositories via Apache has a couple of advantages:
This page describes how to setup Apache to serve Mercurial repositories.
codeBeamer must be installed and started before this configuration can be used.
WindowsPlease choose the 32 bit version of all software mentioned below even if you are running 64 bits Windows We strongly recommended using the same versions shown on this page.This description assumes that codeBeamer has been installed into C:\Dokumente und Einstellungen\zk\Eigene Dateien\CB.
Append the lines of C:\Dokumente und Einstellungen\zk\Eigene Dateien\CB\repository\scmweb\httpd.conf.hgto the end of Apache httpd.conf. The variable WSGIPythonPath must contain the Python installation directory. WSGIPythonPath "C:/Programme/Python-2.6.6"
Linux/UnixIt is important that codeBeamer operating system user and apache belong to the same GID!UbuntuCodeBeamer requires Mercurial 1.8.5 (or newer). This description assumes that codeBeamer has been installed into /home/codebeamer/CB.
After these steps test the apache configuration with the following command: sudo apache2ctl configtest If the command runs without errors then the configuration's OK. You can restart apache: sudo /etc/init.d/apache2 restart RedHatCodeBeamer requires Mercurial 1.8.5 (or newer). This description assumes that codeBeamer has been installed into /home/codebeamer/CB.
sudo /etc/init.d/httpd restart Add codeBeamer user to Apache group (gid)If apache and codeBeamer operating system users are different (can be checked usingidcommand) apache and codeBeamer operating system users must belong to the same system group (gid). Typically the name of the apache group is www-dataon Ubuntu and apacheon Redhat (check your /etc/group). We suggest to add the codeBeamer user to the apache group. The example below shows that codeBeamer user id is 1002 and it belongs to gid 33 used by apache: $ id uid=1002(codebeamer) gid=33(www-data) groups=33(www-data),111(admin) Example: Clone a codeBeamer Repository and Commit with an Associated Issue
MercurialEclipse Plugin can be also used to work with Managed Mercurial Repositories. Hints ant tipsSolving HTTP Error 413: Request Entity Too Large errorsIf you receive an error like this - which can happen if you have lots of heads or branches in Mercurial: hg pull --verbose pulling from https://<url.of.mercurial.repo> searching for changes abort: HTTP Error 413: Request Entity Too Large The fix is to increase the HTTP request sizes from the default 16 Kbytes to 64kbytes. For this edit the following files, both in Apache configuration and also in codeBeamer's tomcat installation: /etc/httpd/conf/worker.properties #worker.ajp13_worker.max_packet_size=16384 worker.ajp13_worker.max_packet_size=65536 /etc/httpd/conf/httpd.conf #LimitRequestFieldSize 12392 LimitRequestFieldSize 65536 #LimitRequestLine 12392 LimitRequestLine 65536 and $CB_HOME/tomcat/conf/server.xml <Connector port="8009" protocol="AJP/1.3" ... etc... <!--packetSize="16384"--> packetSize="65536" /> For more details see: https://www.keycdn.com/support/413-request-entity-too-large/ |
Fast Links
codebeamer Overview codebeamer Knowledge Base Services by Intland Software |
This website stores cookies on your computer. These cookies are used to improve your browsing experience, constantly optimize the functionality and content of our website, furthermore helps us to understand your interests and provide more personalized services to you, both on this website and through other media. With your permission we and our partners may use precise geolocation data and identification through device scanning. You may click accept to consent to our and our partners’ processing as described above. Please be aware that some processing of your personal data may not require your consent, but you have a right to object to such processing. By using our website, you acknowledge this notice of our cookie practices. By accepting and continuing to browse this site, you agree to this use. For more information about the cookies we use, please visit our Privacy Policy.Your preferences will apply to this website only.