Athanasios Voutsadakis bef80e3414 Use eval to run the command instead of exec ...

`exec` is replacing the current shell to run the command, which means that
the script execution stops at that line.

Passing it to the background with `exec "$@" &` won't work either,
because the script will move directly to the next command where it
looks for the `.pid` files that have not yet been created because celery
takes a few seconds to spin up all the processes.

Using `sleep X` to remedy this seems just wrong given that

1. we can use `eval` that blocks until the command returns
2. there is no obvious benefit in sticking with `exec`

2018-02-28 14:16:15 +00:00

..

bootstrap.sh

update bootstrap to use new command

2017-11-23 17:12:13 +00:00

check_if_new_migration.py

update bootstrap to use new command

2017-11-23 17:12:13 +00:00

common_functions.sh

Create Docker build image, build project with Docker

2016-08-22 17:25:41 +01:00

delete_sqs_queues.py

use flake8 instead of pycodestyle

2017-11-28 14:28:01 +00:00

fix_migrations.py

add warning to fix_migrations script for when the filename is different

2017-12-07 10:41:10 +00:00

generate_manifest.py

Only update existing manifest variables when adding env secrets

2018-01-09 10:45:03 +00:00

run_app_paas.sh

Lower the termination timeout to 10s

2018-02-27 17:44:16 +00:00

run_app.sh

Remove flask-script, move commands to click

2017-11-23 17:04:58 +00:00

run_celery_beat.sh

First schedule

2016-03-09 14:41:36 +00:00

run_celery.sh

Add a stop celery script into the scripts folder.

2017-02-08 16:17:50 +00:00

run_multi_worker_app_paas.sh

Use eval to run the command instead of exec

2018-02-28 14:16:15 +00:00

run_single_test.sh

Rename test with duplicate name

2017-01-27 15:21:59 +00:00

run_tests.sh

Merge pull request #1661 from alphagov/pytest-env

2018-02-15 09:34:49 +00:00