Debugging pipelines' environment variables

[Maxim Leonov]

https://confluence.atlassian.com/bitbucket/debug-your-pipelines-locally-with-docker-838273569.html

The above is all nice and well.

But how would one go about debugging the pipelines when one needs to access pipelines' environment variables?

At the moment I just duplicate a repo, do a bunch of pipelines runs on it and then manually transfer all the changes onto the original repo.

Clunky.

Not to mention that this chews up the pilines usage minutes which it doesn't have to while one is technically developing/testing pipelines.

[Philip Hodder]

Hi Maxim,

Indeed, as you use more features it starts to get a bit more complicated to use Docker to debug Pipelines locally.

In regards to environment variables, the best I can offer is to add them in as part of the Docker run command: https://docs.docker.com/engine/reference/commandline/run/#set-environment-variables--e---env---env-file

I acknowledge that this isn't the best approach if you have secrets in your environment variables.

We also have a feature request for a better debugging experience here, that may be relevant: https://bitbucket.org/site/master/issues/12824/allow-ssh-access-into-my-pipelines

If you have any other thoughts, feel free to share them or create a new feature request.

Thanks,

Phil 

[Maxim Leonov]

Hi Philip

Thank you for the response.

I appreciate the complexity of exposing Pipelines environment for debugging.

I voted for the "Allow SSH access into my Pipelines container" you quoted.

Looking forward to news in this space.

Thanks,

Maxim