Working on adding language support.

To do:

UI:

• [x] Login
• [x] Forgot Password
• [x] Reset Password
• [x] Dashboard
• [x] Project
  • [x] Add
  • [x] Edit
  • [x] View
• [x] Users
  • [x] Add
  • [x] Edit
  • [x] Edit Profile
  • [x] View
• [x] Settings
• [x] Builds
  • [x] List
  • [x] View
• [x] Plugins

Command Line Tools:

• [x] Install
• [x] Update
• [x] Poll
• [x] Create Admin
• [x] Run Builds
• [x] Builder
  • [x] Build Plugins

Languages

• [x] English
• [x] German (Provided by @thormeier)
• [x] Dutch (Provided by @matthiasmullie and @tvbeek)
• [x] Russian (Provided by @corpsee, @xboston, @ViGo5190)
• [x] French (Provided by @shulard)
• [x] Danish (Provided by @NamelessCoder)
• [x] Greek
• [x] Polish
• [ ] Arabic
• [ ] Spanish (Looking for volunteers)
• [x] Italian (Provided by @mavimo)
• [ ] Ukrainian (Provided by @borales)
• [ ] Brazilian Portuguese (Provided by @gustavoheinriq)
• [ ] Chinese (Looking for volunteers)
• [ ] Japanese (Looking for volunteers)

Oya,

I've just installed PHPCI and found out it's not working. The installation process went without problems but website itself is a bit blank. In logs I've found an error: Fatal error: Class 'PHPCI\\Controller' not found in /vendor/block8/b8framework/b8/Application.php on line 93

So, here's the Nginx config:

server {
  server_name ci.example.com;
  root /var/www/example.com/ci/public;
  access_log off;
  error_log /var/www/example.com/ci/error.log;
  index index.php;

  location / {
    try_files $uri $uri/ /index.php$is_args$args;
  }

  location ~ (index)\.php$ {
    include fastcgi_params;
    fastcgi_pass unix:/opt/php-5.5.12/var/run/phpci.sock;
    fastcgi_param SCRIPT_FILENAME /public$fastcgi_script_name;
  }
}

And here's the PHP pool config:

[ci.example.com]
listen = /opt/php-5.5.12/var/run/phpci.sock
listen.owner = www-data
listen.group = www-data
listen.mode = 0660
user = www-data
group = www-data
pm = dynamic
pm.max_children = 15
pm.start_servers = 2
pm.min_spare_servers = 2
pm.max_spare_servers = 10
chroot = /var/www/example.com/ci
chdir = /

My guess is that the problem might be somewhere in the fact that the application is locked in the chroot. I've dumped $_SERVER to see what is going in...

[SCRIPT_FILENAME] => /public/index.php
[SCRIPT_NAME] => /index.php
[REQUEST_URI] => /session/login
[DOCUMENT_URI] => /index.php

And then checked the $fc:

PHPCI\Application Object
(
    [route:protected] => 
    [controller:protected] => 
    [request:protected] => b8\Http\Request Object
        (
            [params:protected] => Array
                (
                )

            [data:protected] => Array
                (
                    [path] => n/login
                    [parts] => Array
                        (
                            [0] => n
                            [1] => login
                        )

                )

        )
...

And there is something... The path value is n/login instead of session/login.

So, in case you get a spare minute or two, I'd be happy if you've checked what might be a cause and how to fix it.

I think that it would be nice if the got the color based on the last build status I mean if the last build was a success it should be green , even if he had for example 3 builds failed out of 5 .

the visuality here should be based on the last build not the whole project status.

When trying to install phpci according to https://github.com/Block8/PHPCI/wiki/Installing-PHPCI and calling the Application from my browser I am redirected from https://...../phpci to https://...../phpci/session/login

Also included the mod_rewrite lines within an .htaccess and put it into my apache configuration (+restart). Does not make any difference

A more full featured codeception plugin. Parses the XML return from codeception test results and uses some of them in the display. Stores all of them in the meta table.

Hi

I'm using the Slack Notifier plugin and every time a build runs and completes, no matter what status, the message in my Slack channel is always:

Status: Failed

Does anyone know why this is?

With this plugin, users are able to run shell commands. Here is an example of phpci.yml file

https://raw.github.com/kinncj/moving-bazar/master/phpci.yml

Is also exposed a %buildpath% variable

%buildpath% is optional.
%buildpath% is switched by the real build path on build execution.

Just cloned PHPCI and can't get it to work. The install went okay, and the DB has been created, but now I get redirect to /session/login which ends with a redirect loop

it appears validateSession is redirecting to the login page because I am not logged in

    protected function validateSession()
    {
        if (!empty($_SESSION['user_id'])) {
            $user = b8\Store\Factory::getStore('User')->getByPrimaryKey($_SESSION['user_id']);

            if ($user) {
                $_SESSION['user'] = $user;
                return true;
            }

            unset($_SESSION['user_id']);
        }

        if ($this->request->isAjax()) {
            $this->response->setResponseCode(401);
            $this->response->setContent('');
        } else {
            $this->response = new RedirectResponse($this->response);
            $this->response->setHeader('Location', PHPCI_URL.'session/login');
        }

        return false;
    }

Any ideas on what went wrong?

Running php v5.4 on centos

thanks :)

Seeing two errors when trying to build a laravel4 project, first, i don't think the composer plugin is working, and secondly, PHPUnit seems to not be working, and generating the TAP error below:

Cloning into '/var/phpci/PHPCI/build/project1-build10'...
Working copy created: /
RUNNING PLUGIN: env
PLUGIN STATUS: SUCCESS!
RUNNING PLUGIN: composer
PLUGIN STATUS: FAILED
RUNNING PLUGIN: php_unit
EXCEPTION: TapParser only supports TAP version 13
PLUGIN STATUS: FAILED
BUILD FAILURE
Removing build.

My phpci.yml:

setup:
  env:
    TEST_DB_DB: "sss"
    TEST_DB_HOST: "127.0.0.1"
    TEST_DB_USER: "sss"
    TEST_DB_PWD: "sss"

  composer:
    action: "install"

test:
  php_unit:
    config:
      - "phpunit.xml"
    directory:
          - "app/tests/"

Contribution Type: new plugin Link to Intent to Implement: #1262

This pull request affects the following areas:

• [x] Front-End
• [x] Build Plugins

In raising this pull request, I confirm the following (please check boxes):

• [x] I have read and understood the contributing guidelines?
• [x] I have checked that another pull request for this purpose does not exist.
• [x] I have considered, and confirmed that this submission will be valuable to others.
• [ ] I have created or updated the relevant documentation for this change on the PHPCI Wiki.
• [x] Do the PHPCI tests pass?

Detailed description of change:

~~A new plugin is introduced instead of updating the existing one because of all the changes required, plus it will ease the comparison between the two plugins.~~ UPDATE: Updates were merged into the original plugin.

The new phpunit plugin is fully backwards compatible with the original one so it can potentially replace it. The plugin is broken into three testable components: an options parser, result parser and the plugin itself.

Features:

1. The args option in the configuration file now supports a named list of CLI arguments. Ex:

   php_unit:
   args:
       filter: "test"
       group:
           - "groupOne"
           - "groupTwo"
   

2. The build log will now include the default phpunit output.

3. New JSON result parser to deal with outstanding issues of the TAP parser. Ref: #571 , #624

4. Failures and errors are now also stored in the Errors tab of the front-end.

5. Failures and errors will include a collapsed stack trace in front-end Information tab.

Not sure if it would duplicate existing functionality, but having a lint task that will simply check the syntax of files might be nice:

lint:
    directories:
        directoryA:
            - .php
            - .html
        directoryB:
            - *
    files:
        - lala.php
        - foo.html

The task would search inside directories for files ending with the given extensions. Each file would then be executed with php -l <file>.

I'm not happy with the structure of the definition, but like this it covers most features I would expect.

Contribution Type: refactor Link to Intent to Implement: Link to Bug:

This pull request affects the following areas:

• [X] Front-End
• [ ] Builder
• [ ] Build Plugins

In raising this pull request, I confirm the following (please check boxes):

• [X] I have read and understood the contributing guidelines?
• [X] I have checked that another pull request for this purpose does not exist.
• [X] I have considered, and confirmed that this submission will be valuable to others.
• [ ] I have created or updated the relevant documentation for this change on the PHPCI Wiki.
• [X] Do the PHPCI tests pass?

Detailed description of change:

I've added all spanish missing translations and translated somes

Contribution Type: cosmetic (up to date dependency)

In raising this pull request, I confirm the following (please check boxes):

• [x] I have read and understood the contributing guidelines?
• [x] I have checked that another pull request for this purpose does not exist.
• [x] Do the PHPCI tests pass?

Detailed description of change: just use supported package for slack see https://github.com/maknz/slack/issues/94

Contribution Type: bug fix Link to Intent to Implement: none Link to Bug: https://github.com/dancryer/PHPCI/issues/1143

This pull request affects the following areas:

• [ ] Front-End
• [x] Builder
• [ ] Build Plugins

In raising this pull request, I confirm the following (please check boxes):

• [x] I have read and understood the contributing guidelines?
• [x] I have checked that another pull request for this purpose does not exist.
• [x] I have considered, and confirmed that this submission will be valuable to others.
• [x] I have created or updated the relevant documentation for this change on the PHPCI Wiki.
• [x] Do the PHPCI tests pass?

Detailed description of change:

• changed regex for correct parse ports and vendors starting with number .
• added 2 tests for parsing gitlab ssh address.

Contribution Type: bug fix Link to Intent to Implement: - Link to Bug: -

This pull request affects the following areas:

• [ ] Front-End
• [x] Builder
• [ ] Build Plugins

In raising this pull request, I confirm the following (please check boxes):

• [x] I have read and understood the contributing guidelines?
• [x] I have checked that another pull request for this purpose does not exist.
• [x] I have considered, and confirmed that this submission will be valuable to others.
• [x] I have created or updated the relevant documentation for this change on the PHPCI Wiki.
• [x] Do the PHPCI tests pass?

Detailed description of change:

Fix clone by ssh method for mercurial build

Before submitting your issue, please make sure that you've checked all of the checkboxes below.

• [ ] You're running the latest release version of PHPCI.
• [ ] Ensure that you're running at least PHP 5.3.6, you can check this by running php -v
• [ ] You've run composer install --no-dev -o from the root of your installation.
• [ ] You have set up either the PHPCI Worker, Daemon or Cron Job to run builds.

To help us better understand your issue, please answer the following.

Expected behaviour

Please describe what you're expecting to see happen.

Actual behaviour

Please describe what you're actually seeing happen.

Steps to reproduce

If your issue requires any specific steps to reproduce, please outline them here.

Environment info

Operating System: PHP Version: MySQL Version:

Logs or other output that would be helpful

(If logs are large, please upload as attachment).

Cloning into '/home/wwwroot/phpci/PHPCI/build/21_20e6a'...

dc61336420091713043c86477e3d5c174549a78e Working copy created: / RUNNING PLUGIN: composer Composer could not find a composer.json file in /home/wwwroot/phpci/PHPCI/build/21_20e6a To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section

PLUGIN: FAILED Exception: Plugin failed: composer Removing Build.

To help us better understand your issue, please answer the following.

Expected behaviour

Please describe what you're expecting to see happen.

Actual behaviour

Please describe what you're actually seeing happen.

Steps to reproduce

If your issue requires any specific steps to reproduce, please outline them here.

Environment info

Operating System: Debian 9 64bit PHP Version: 7.1.7 MySQL Version: 5.6.3 I have set up the composer.json into repo

Logs or other output that would be helpful

(If logs are large, please upload as attachment).