Shell plugin config

[frimdo]

• 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.

Brief issue explanation

When shell plugin is enabled by the wiki page, the shell is still disabled. I guess that the wiki is deprecated, and the shell plugin should be enabled in config.yml.

Expected behaviour

Shell plugin being enabled when configured according to wiki page

Actual behaviour

Build log of project that uses shell plugin looks like this

Cloning into '/var/www/html/PHPCI/build/3_3ca47'...

cde038b4d7e8ed768d9be6c9e63a7f684c0391c6
Working copy created: /
RUNNING PLUGIN: shell
Exception: The shell plugin is not enabled. Please enable it via config.yml.
PLUGIN: FAILED
Exception: Plugin failed: shell
RUNNING PLUGIN: shell
Exception: The shell plugin is not enabled. Please enable it via config.yml.
PLUGIN: FAILED
Removing Build.

Steps to reproduce

0. Configure PHPCI by the wiki page
1. Build project that uses shell plugin

Environment info

Operating System:

Debian GNU/Linux 8 

PHP Version:

PHP 7.1.2 (cli) (built: Feb 28 2017 17:47:07) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies

MySQL Version:

mysql  Ver 14.14 Distrib 5.7.17, for Linux (x86_64) using  EditLine wrapper

[frimdo]

Update: The plugin is enabled when configured according to wiki page, so the only issue is the message that says that it should be configured using config.yml

[vaanholtje]

Here the same problem system says its enabled but still getting the anoying message that causes builds to fail. Running php 5.6

[vaanholtje]

Restart of the worker was the solution!

[rafaelmb]

Hi @frimdo I've installed PHPCI again on my server three days ago and yesterday I have enabled the shell plugin. All I need to do was add the define at local_vars.php and the next build has shell available and working. The @vaanholtje comment points out that using daemon requires a restart but I use cron here. Can you check if this is fixed?