Im struggling with using steps to persist information/state.
I had assumed the parallel steps inherit their container from the previous step. This is correct, I can not get it to work.
If this, isnt correct doest that mean parallel steps, are meant to have lots of duplicate code (for example installing packages, and prepring envs to run tests etc..)
Hi, @AS!
Thank you for reaching out to Atlassian Community!
First, I would like to explain how containers work. Your assumption was:
I had assumed the parallel steps inherit their container from the previous step.
Actually, for every step in the YAML file, a Docker container starts. The repo is cloned in that container, and then the script commands are executed. Then, the container gets destroyed. For the next step, a new container will start. So, if you install some tools in one step, they won’t be available in the next step. If you generate files in one step, they will only be available in the next steps if you define them as artifacts.
You mentioned parallel steps. Artifacts defined in a certain parallel step are not available in steps of the same parallel set. Only in subsequent steps that are not part of the parallel set.
I don’t know how this tool (Poetry) is installed, and whether simply defining as artifacts certain directories it generates will make it available in the next steps or not. So, if you could let us know how you do the installation, we can check this further.
Looking forward to hearing from you.
Kind regards,
Caroline
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.