Not up to standards ⛔

_{TIP This summary will be updated as you push new changes. Give us feedback}

The existing debug_mode is defined for each job separately and is given by the BackendNewJob message to the docker agent. So it is best to use a new environment variable to indicate if debug through the IDE is wanted. Any suggestions for a good variable name so it isn't confused for a parameter for the remote ssh debug ?

For a future PR for remote debugging :
As suggested we might want to use debug_host and debug_ports to specify the remote agent used and allow debug on the containers on that agent. However it is indicated that those configuration parameters are only to be used is the backend is on local. Does that mean we currently can't do remote ssh debugging if the backend is on a remote machine ?

# Only for backend: local
local-config:
    # debug_host: localhost  # host that will be indicated to users when they want to use the task remote debug feature. Automatically guessed by
                             # default
    debug_ports: 64000-64100 #port range use for remote debug feature

Any suggestions for a good variable name so it isn't confused for a parameter for the remote ssh debug ?

ide_debug or simply debugger

Actually it might be more productive to directly add the options in the webapp config file and the docker agent CLI arguments.

Does that mean we currently can't do remote ssh debugging if the backend is on a remote machine ?

If the docker agent is used on another host, the args are passed in the CLI. This local-config feature is used for small deployments and development.

In conclusion, debugger_host and debugger_port seems two good new options to add to local-config and docker agent CLI.

A message is now added to stderr if the debug server is not available. It does not fail the job anymore.

I have also fixed the time limit for a job to half an hour if the container debugging is enabled. Without it the job just stops after the set limit and debugging is not possible. Should I add that fixed limit as a config parameter ?