Dependency to PHP Guzzle¶

Tuleap starts using Guzzle package from the EPEL repository (php-guzzle-Guzzle) instead of the package provided until now by the Tuleap repository (php-guzzle). You should check if this package is not ignored by your yum configuration.

A new option for setup.sh¶

Now setup.sh is checking if your domain name is valid. And for your automation or if you are sure, you can still bypass the check with option:

#> setup.sh --disable-domain-name-check

Changes in git plugin configuration¶

For Urls, Git plugin uses local.inc sys_default_domain instead of apache SERVER_NAME.

Changes in SVN multirepositories plugin¶

The public URL for repositories changes. All users will have to update their checkout/checkin links.

New dependency required for Tuleap¶

Tuleap now requires the package php-paragonie-random-compat to work. If you have followed the installation guide, the package will be installed automatically from the EPEL repository if you use CentOS 6 or from the Tuleap repository if you use CentOS 5.

If you have not followed the installation guide and the dependency can not be found you must install it by hand.

Planning v1 removal¶

Agile Dashboard Planning v1 (deprecated since 2 releases) is not anymore available. You can safely remove the following variable from your /etc/tuleap/conf/local.inc file:

// Display deprecated planning V1
$sys_showdeprecatedplanningv1 = 0;

Legacy themes removal¶

Few themes are removed:

• CodexSTN (tuleap-theme-codexstn)
• Dawn (tuleap-theme-dawn)
• savannah (tuleap-theme-savannah)
• Steerforge (tuleap-theme-steerforge)
• STTab (tuleap-theme-sttab)

They are automatically replaced by FlammingParrot, if you don’t have it installed yet it should be automatically fetched as a dependency. However, if it’s not, you should install it by hand:

#> yum install tuleap-theme-flamingparrot

For end users that where using the old theme, they are automatically switch to the default theme defined in local.inc. If the default theme was one of them, it’s flaming parrot that is used in last resort.

Legacy packages removed¶

OpenId (tuleap-plugin-openid) is gone. You can try OpenID connect instead (require manual setup as of 8.11).

Subversion packaging issue¶

Due to a packaging issue we strongly suggest you install or force the reinstall of the following packages: tuleap-core-subversion and tuleap-core-subversion-modperl.

Meaning that if these packages are not installed you can install them with:

#> yum install tuleap-core-subversion tuleap-core-subversion-modperl

If the packages are already installed, you can reinstall them with:

#> yum reinstall tuleap-core-subversion tuleap-core-subversion-modperl

Use tokens to authenticate a SVN user¶

It is now possible to use a token instead of a password to authenticate users for SVN operations. In order to make that possible, it is necessary to grant more rights to the database user used to authenticate a user. You must run the following commands on your database with a privileged user:

GRANT SELECT,UPDATE ON svn_token TO dbauthuser;
FLUSH PRIVILEGES;

If you use the LDAP plugin, you also need to grant this privilege:

GRANT SELECT ON plugin_ldap_user TO dbauthuser;
FLUSH PRIVILEGES;

Git evolution on CentOS 5 due to a system bug¶

To find a workaround a system bug, we have been forced to introduce a change. To kept the Git plugin fully functional, you must edit your sudoers file to match the following informations:

Defaults:gitolite !requiretty
Defaults:gitolite !env_reset
gitolite ALL= (codendiadm) SETENV: NOPASSWD: /usr/share/codendi/src/utils/php-launcher.sh /usr/share/codendi/plugins/git/hooks/post-receive.php*

Git evolution on CentOS 5 to import/export project archive¶

Now that it is possible to import a git repository alongside a project archive, you must edit your sudoers file to match the following informations:

Defaults:codendiadm !requiretty
Defaults:codendiadm !env_reset

# Gitolite restore tar repository
Cmnd_Alias RESTORE_TAR_REPO_CMD = %libbin_dir%/restore-tar-repository.php

# Gitolite clone bundle
Cmnd_Alias BUNDLE_CMD = /usr/share/tuleap/plugins/git/bin/gl-clone-bundle.sh

codendiadm ALL= (gitolite) SETENV: NOPASSWD: RESTORE_TAR_REPO_CMD, BUNDLE_CMD

Create artifact by mail¶

A new feature adding the possibility of creating an artifact by email has been added. check Activate reply to artifacts by email in Administration guide.

Git evolution on CentOS 5¶

With the introduction of the truncated notifications in the Git plugin, we have been forced to do some changes. To kept the Git plugin fully functional, you must add the following informations at the end of your sudoers file which is generally located at /etc/sudoers:

Defaults:gitolite !requiretty
Defaults:gitolite !env_reset
gitolite ALL= (codendiadm) SETENV: NOPASSWD: /usr/share/codendi/plugins/git/hooks/post-receive.php

Note that only Tuleap instances running on CentOS 5 are concerned.

User management via Active Directory¶

A new template has been added to help configure Tuleap with Active Directory. You can find it in the sources plugins/ldap/etc/ActiveDirectory.inc.dist

If you have an existing ldap set-up and wish to be compatible with Active Directory then you will need to update the file /etc/tuleap/plugins/ldap/etc/ldap.inc with these extra properties

// The type of the ldap server
$sys_ldap_server_type = 'ActiveDirectory';

// The identifier of a user group
$sys_ldap_grp_uid = 'sAMAccountName';

API Explorer update¶

We have updated the API Explorer. The package restler-api-explorer must be considered deprecated. To update to the new Explorer install the package tuleap-api-explorer and remove or at least comment the old Apache configuration. You probably have copied this configuration at /etc/httpd/conf.d/tuleap-plugins/tuleap-api-explorer.conf. After the removal, you need to restart Apache.

Drop support of insecure SSL/TLS configurations¶

With this release we have updated the default TLS Apache configuration we provide with Tuleap. All new instances of Tuleap will use this one but if you already have an installation, your configuration will be left untouched. However, we encourage you to update your configuration for security reasons. As a side effect, this change also prevents Internet Explorer 7 and Internet Explorer 8 on Windows XP to be able to connect to the HTTPS server.

If you want to update your configuration, replace the line SSLProtocol and SSLCipherSuite /etc/httpd/conf/ssl.conf by:

# SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect.  Disable SSLv2 and SSLv3 access by default:
SSLProtocol all -SSLv2 -SSLv3

#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA
SSLHonorCipherOrder on

Password storage¶

We have added a new and more secure way to store passwords in Tuleap. This feature is activated default on new intalls but the legacy way is kept on the already running instances for compatibility purposes. We greatly advise to use this new functionality if you can.

To activate the new password storage on a already existing instance you must add the following line in your local.inc:

$sys_keep_md5_hashed_password = 0;

Execute this script if you have the IM plugin installed:

#> /usr/share/tuleap/src/utils/php-launcher.sh /usr/share/tuleap/plugins/IM/bin/redeploy_auth_provider.php

Execute this script if you have the Proftpd plugin installed:

#> /usr/share/tuleap/plugins/proftpd/bin/switch_to_unix_password.php

Mediawiki¶

• Upgrade to mediawiki 1.23 check Administration guide

REST API¶

A new parameter in local.inc allow users to query api in HTTP without SSL. By default HTTPS is enforced.

// Can query REST API without using HTTPS
// /!\ This is unsafe unless you have something else (reverse-proxy)
//      providing the SSL Layer between you and the server /!\
$sys_rest_api_over_http = 0;

Logrotate¶

Logrotate might be configured to use “dateext” instead of .X. This might create garbage in logs and can be an issue when attempting to copy logs from /var/log/httpd/blalba.1 to /var/log/tuleap/YYYY/MM/blalba_YYYYMMDD.log. We prevent now this behavior by adding “nodateext” option to /etc/logrotate.d/httpd.

See /usr/share/tuleap/src/etc/logrotate.httpd.conf for reference.

CVS¶

We have enabled Tuleap to deal with incoming CVS commits from Windows machines. You can now toggle between allowing Windows encoding of the commit messages and utf-8 encoding. To set this up (CentOS 6):

Local.inc:

• Add $sys_cvs_convert_cp1252_to_utf8 = 1; at the end of the file.

System:

# Note: for CentOS 5, you need to manually source and install the package 'perl-Text-Iconv'
$> yum install perl-Text-Iconv
$> cp /usr/share/tuleap/src/utils/cvs1/log_accum /usr/lib/tuleap/bin/log_accum

FullText Search¶

It was reported that certain versions of elasticsearch do not allow for the indexation of files above, say, 100 MB. In order to prevent these files being mistakingly indexed and causing the operation to fail, we did several things:

• All files above a certain size are skipped;
• The corresponding system event contains a warning;
• The system administrator is notified by mail

In order for this to work you need to add the following lines to /etc/tuleap/plugins/fulltextsearch/etc/fulltextsearch.inc

// The maximum file size (in bytes) that can be indexed- be careful
// not to go above your server limits
$fulltextsearch_max_indexed_file_size = 100000000;

This value can then be managed via the Tuleap Admin area -> plugin adminstration -> FullText Search.

Git¶

• We drop the embedded version of gitphp in favor of the packaged one. This is reflected by the $gitphp_path in /etc/tuleap/plugins/git/etc/config.inc
• New installations have git HTTP access activated.
• Existing installations without HTTP access can enable it by setting $git_http_url = "https://%server_name%/plugins/git"; in /etc/tuleap/plugins/git/etc/config.inc
• Existing installations with HTTP access should keep existing HTTP access as default (without anonymous access) but can communicate to their users about the new URL https://%server_name%/plugins/git/%repo_path% for test.
• gitolite3 path in sudoers.d/gitolite3-http file has been changed: codendiadm ALL= (gitolite) SETENV: NOPASSWD: /usr/share/gitolite3/gitolite-shell

LDAP¶

• Default search for daily syncho is now the whole LDAP subtree.
  • If $sys_ldap_daily_sync was enabled (= 1), you should monitor duration of ROOT_DAILY system event (each night at 00:10)
    • If duration is the same after upgrade, everything is fine
    • If duration is really longer (20-30% longer). You can switch back to previous mode with $search_depth = 'onelevel'; in ldap configuration /etc/tuleap/plugins/ldap/etc/ldap.inc
  • If $sys_ldap_daily_sync was disabled ( = 0), you should be able to enable it
    • Do it first on a QA server
    • You should expect some people to be suspended on first run
    • If most users get suspended, there is something wrong and you should keep the synchro disabled and report the issue

Core¶

The default backup path for deleted projects is /var/tmp. See $sys_project_backup_path in /etc/tuleap/conf/local.inc.

Full text search¶

The default time-out for a request to an elasticsearch server is 5 seconds. Now, administrators can choose the maximum time-out value in the configuration of the the fullTextSearch plugin.

For upgrades, you need to copy a variable from /usr/share/codendi/plugins/fulltextsearch/etc/fulltextsearch.inc.dist to /etc/tuleap/plugins/fulltextsearch/etc/fulltextsearch.inc

$max_seconds_for_request = 10;

General¶

Starting this release, the tuleap system logs are handled by logrotate. The default configuration is to rotate on weekly basis and to keep 4 weeks of logs.

Local.inc:

• $sys_create_project_in_one_step is no longer needed as legacy project creation is gone.
• New option $sys_strip_outlook = 0; allow to test removal of outlook quote in tracker email reply (experimental)
• New option $sys_default_mail_domain = ""; Define the email domain for email gateway feature (By default, email domain = default Tuleap domain )

Full text search¶

You need to clean and re-index all previously indexed projects:

# Of course, you need to adapt username, password, servers and port to
# your configuration
$> curl -u superuser:Adm1n -X DELETE "localhost:9200/tracker"
$> curl -u superuser:Adm1n -X DELETE "localhost:9200/docman"
$> curl -u superuser:Adm1n -X DELETE "localhost:9200/wiki"
$> curl -u superuser:Adm1n -X PUT "localhost:9200/tracker" -d '{
    "settings" : { "index" : { "number_of_shards" : 1, "number_of_replicas" : 0 }}
}'
$> curl -u superuser:Adm1n -X PUT "localhost:9200/docman" -d '{
    "settings" : { "index" : { "number_of_shards" : 1, "number_of_replicas" : 0 }}
}'
$> curl -u superuser:Adm1n -X PUT "localhost:9200/wiki" -d '{
    "settings" : { "index" : { "number_of_shards" : 1, "number_of_replicas" : 0 }}
}'

Then, as a site admin, trigger re-index of projects.

Git¶

You can configure git and http urls in git/etc/config.inc:

// Urls
// By default, only ssh is available for use and you can setup HTTP(s) access
// to your server.
// For convenience, you can either hardcode the URLs or you can use %server_name%
// variable that will be replace automatically by the value of $_SERVER['SERVER_NAME']
// this is typical the URL the user see in location bar of the browser
// Tell to Tuleap that an HTTPS server for git is available at the given
// address
// $git_http_url = "https://%server_name%/git";

// Define a custom ssh URL to get access to the sources
// You can disable display of this url by activating this variable and setting
// to '' (empty string)
//
// $git_ssh_url = 'ssh://gitolite@%server_name%:2222';

The $grokmanifest_path is no longer needed on server (you can remove grokmirror too).

Old Docman migration¶

This release comes with a tool to assist admin of very old Tuleap to migrate from docman v1 to docman v2 (plugin). This might be relevant to you if you installed Tuleap before 2009. Check Administration guide

Git¶

Another change in this release is a dependency on a recent version of git. We know for sure that there are issues with git <= 1.7.4.1

If in doubt, then you should upgrade to the latest version.

$> yum update git

Full text search¶

The index mapping for artifact’ss follow-up comments changed, you need to delete the current index and to create an empty new one (all previously indexed comments will be lost):

# Of course, you need to adapt username, password, servers and port to
# your configuration
$> curl -u superuser:Adm1n -X DELETE "localhost:9200/tracker"
$> curl -u superuser:Adm1n -X PUT "localhost:9200/tracker" -d '{
    "settings" : { "index" : { "number_of_shards" : 1, "number_of_replicas" : 0 }}
}'

Mediawiki extra plugins compatibility mode¶

Tuleap 7.4 comes with a maturity about the limits of integrating Medaiwiki and its numerous plugins such as “wiki editor” into Tuleap. In order to avoid impossible javascript and css conflicts there is now a compatibility that can be enabled if needed. It needs to be enabled at a forge level before it can be enabled at a project level and this is how:

New option in /etc/<tuleap|codendi>/plugins/mediawiki/etc/mediawiki.inc

$enable_compatibility_view = true;

This option can then be toggled by site administrators in the “plugins administration” area.

Activating the compatibility view for a project is then done in the “Administration” section of a given mediawiki in the UI.

CentOs packages dependency¶

For Tuleap 7.3, we updated our mediawiki package by adding new modules. For a new extension, we create a dependency with a packahe named htmldoc

This package is only available in EPEL repositories. So, in order to be able to update your Tuleap, you have to activate EPEL on your server.

FlamingParrot Variants¶

Tuleap 7.3 introduce new FlamingParrot theme variants. To be more concrete, new colors are available for our new theme.

You are able to choose which variants you want to enable on your Tuleap by adding a new enrty in the local.inc file (by default, all variants are activated):

// List of available theme variant in forge
// Available variants:
// * FlamingParrot_Orange
// * FlamingParrot_Blue
// * FlamingParrot_Green
// * FlamingParrot_BlueGrey
// * FlamingParrot_Purple
// * FlamingParrot_Red
// * FlamingParrot_DarkOrange
// * FlamingParrot_DarkBlue
// * FlamingParrot_DarkGreen
// * FlamingParrot_DarkBlueGrey
// * FlamingParrot_DarkPurple
// * FlamingParrot_DarkRed
$sys_available_theme_variants = 'FlamingParrot_Orange,FlamingParrot_Blue,FlamingParrot_Green,FlamingParrot_BlueGrey,FlamingParrot_Purple,FlamingParrot_Red,FlamingParrot_DarkOrange,FlamingParrot_DarkBlue,FlamingParrot_DarkGreen,FlamingParrot_DarkBlueGrey,FlamingParrot_DarkPurple,FlamingParrot_DarkRed';

In addition, you can choose your default color for the whole platforme by adding a variable in your local.inc file:

// Default theme variant in forge
$sys_default_theme_variant = 'FlamingParrot_Orange';

Tracker¶

New option in local.inc

// Allow users to reply by mail to artifact notifications
// As of today only adding a follow-up comment is supported
$sys_enable_reply_by_mail = 0;

See plugins/tracker/README.emailgateway.mkd for details about sudoers deployment.

Subversion¶

New option in local.inc

// Allow (or not) users to do a SVN commit without any commit message
// Set to 0 to force commit message to not be empty
$sys_allow_empty_svn_commit_message = 1;

Full text search¶

A lot of changes on full text search

1. Elasticsearch must now be 1.2.x version
2. The index mapping for docman was totally rewamped. Hence, all previously indexed documents will no longer be reachable and admin should re-do the mapping.