Possibility of sharing files between Build and Deploy stages
long-term
R
Raw Jellyfish
We have a requirement where a properties files from a Git repo that was cloned during the build stage need to be available during the deploy stage. To make this possible we are currently cloning the same repository again during the deploy process.
We are looking for a solution to avoid cloning the same repository multiple times during the pipeline run and make the file available in the cache that can be leveraged as required during the later stages of the pipeline.
Log In
Canny AI
Merged in a post:
Share CI Artifacts Across Stages
Z
Zinnwaldite Swordfish
We have a case where we want to run multiple CI stages in parallel including building and scanning the docker image. If those parallel stages pass, then I would like to push the image built in the previous step to the our artifact registry.
Currently we would need to push this image to an artifact registry, which we don't want to do because there could be failing tests, other security issues, and we don't want this to persist past the lifecycle of the pipeline.
For example, if we could share folders between stages that would be extremely useful.
Canny AI
Merged in a post:
Pass on cloned GitHub commit from one step group to second step group in harness pipeline
Y
Yellow sunshine Vole
We have prepared one Harness template to deploy applications using AWS CDK. There we are using git Clone pipeline step in two separate step group.
In one step group we are cloning the github repo and running cdk diff command .
In the next step group we are cloning github repo again and running cdk deploy command.
Now when we cloning the repo again it's cloning the head commit from the mentioned branch. Rather we want to clone the same commit in the second step group which was cloned in the first step group.
Below is the pipeline template URL-
Can you please help us with the solution.
Regards,
Dipayan
Rohan Gupta
THis is supported today, you need to use the output variables from the previous stepgroup and reference it in the clone step in the new step group. If you need help with implementation, i recommend either engaging your account assigned implementation engineer, or if need be please reach out to support@harness.io they can guide you to fix it.
Rohan Gupta
long-term
Currently this is not possible due to the way CI and CD operate with the Harness Delegate. We are working to reduce this limitation in the future.