You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
robocoder opened this issue
Mar 12, 2012
· 2 comments
Assignees
Labels
TaskIndicates an issue is neither a feature nor a bug and it's purely a "technical" change.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
Right now, the PHP version (and some runtime options) used by the CI server for testing can be set by Jenkins via environment variables, e.g.,
PHP_VERSION - the default is currently 5.3.10
However, these env vars are lost when using curl requests; the server then falls back to the defaults.
This ticket proposes:
on curl requests to localhost or 127.0.0.1, we set an X- header for the desired PHP version, e.g., X-PHP; this can be further protected by a config option (default suppresses this header) or maybe an alternate adapter (i.e., if we refactor Http.php)
the php-cgi wrapper script would then select the PHP version specified by (in order of preference) X_HTTP_PHP, PHP_VERSION, default.
The text was updated successfully, but these errors were encountered:
Does it mean that we are closer to being able to test multiple PHP versions on Jenkins? :)
X- header is a good solution, only set the header when the config setting was set (which should only be used on the Piwik QA server and not by users anyway).
TaskIndicates an issue is neither a feature nor a bug and it's purely a "technical" change.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
Right now, the PHP version (and some runtime options) used by the CI server for testing can be set by Jenkins via environment variables, e.g.,
However, these env vars are lost when using curl requests; the server then falls back to the defaults.
This ticket proposes:
The text was updated successfully, but these errors were encountered: