Shell plugin status failed, but build successful

[TheRatG]

PHPCI build config setup: shell: command: ....

And get

Working copy created: / RUNNING PLUGIN: shell ... PLUGIN STATUS: FAILED BUILD SUCCESSFUL! Removing build.

Is it normal behavior?

[gumeniukcom]

Some times i have this problem too.

[swilla]

I have this problem as well, I'm using Laravel and a migration failed due to a syntax error, but the build was successful.

RUNNING PLUGIN: shell
Migration table created successfully.
   {"error":{"type":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","message":"Call to a member function after() on boolean","file":"\/phpci\/PHPCI\/build\/68\/app\/database\/migrations\/2015_02_04_141150_add_market_route_id_to_user_market_route_segment_states.php","line":19}}
PHP Fatal error:  Call to a member function after() on boolean in /app/database/migrations/2015_02_04_141150_add_market_route_id_to_user_market_route_segment_states.php on line 19
PHP Stack trace:
PHP   1. {main}() /artisan:0
PHP   2. Symfony\Component\Console\Application->run() /artisan:59
PHP   3. Symfony\Component\Console\Application->doRun() /vendor/symfony/console/Symfony/Component/Console/Application.php:124
PHP   4. Symfony\Component\Console\Application->doRunCommand() /vendor/symfony/console/Symfony/Component/Console/Application.php:193
PHP   5. Illuminate\Console\Command->run() /vendor/symfony/console/Symfony/Component/Console/Application.php:889
PHP   6. Symfony\Component\Console\Command\Command->run() /vendor/laravel/framework/src/Illuminate/Console/Command.php:100
PHP   7. Illuminate\Console\Command->execute() /vendor/symfony/console/Symfony/Component/Console/Command/Command.php:253
PHP   8. Illuminate\Database\Console\Migrations\MigrateCommand->fire() /vendor/laravel/framework/src/Illuminate/Console/Command.php:112
PHP   9. Illuminate\Database\Migrations\Migrator->run() /vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php:70
PHP  10. Illuminate\Database\Migrations\Migrator->runMigrationList() /vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:82
PHP  11. Illuminate\Database\Migrations\Migrator->runUp() /vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:111
PHP  12. AddMarketRouteIdToUserMarketRouteSegmentStates->up() /vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:135
PHP  13. Illuminate\Support\Facades\Schema::table() /app/database/migrations/2015_02_04_141150_add_market_route_id_to_user_market_route_segment_states.php:20
PHP  14. Illuminate\Support\Facades\Facade::__callStatic() /app/database/migrations/2015_02_04_141150_add_market_route_id_to_user_market_route_segment_states.php:20
PHP  15. Illuminate\Database\Schema\Builder->table() /bootstrap/compiled.php:3265
PHP  16. Illuminate\Database\Schema\Builder->createBlueprint() /vendor/laravel/framework/src/Illuminate/Database/Schema/Builder.php:94
PHP  17. Illuminate\Database\Schema\Blueprint->__construct() /vendor/laravel/framework/src/Illuminate/Database/Schema/Builder.php:186
PHP  18. AddMarketRouteIdToUserMarketRouteSegmentStates->{closure:/app/database/migrations/2015_02_04_141150_add_market_route_id_to_user_market_route_segment_states.php:17-20}() /vendor/laravel/framework/src/Illuminate/Database/Schema/Blueprint.php:49

Seeded: UserTableSeeder
User table seeded!
Seeded: OAuthSeeder
OAuth Client table seeded!
Seeded: PartnerSeeder
Partner table seeded!
PLUGIN: FAILED
...
BUILD SUCCESS
Removing Build.

Here is the Shell plugin settings inside the setup section:

shell:
        - "cd %BUILD_PATH% && nohup php artisan serve --host=local-api --port=8000 > /dev/null 2>&1&"
        - "cd %BUILD_PATH% && php artisan migrate" # Laravel Migrations
        - "cd %BUILD_PATH% && php artisan db:seed" # Seed the DB

[matt-gnu]

Same bug found also in current release 1.7.1:

failed to push changes upstream.
Zu Branch 'master' gewechselt
To ssh://git@<URL>.git
 ! [rejected]        master -> master (fetch first)
[...]
PLUGIN: FAILED
BUILD SUCCESS

my shell script is printing the error message failed to push changes upstream. and then calls exit 1 So @dancryer, could/should the 1.6-or-below label be removed?