CI stage cannot be triggered by trigger of type: ARTIFACT
long-term
F
Fawn Antelope
When a CI stage is present in a pipeline and it gets triggered by a trigger of type ARTIFACT the pipeline throws this error
Invalid request: CI stage cannot be triggered by trigger of type: ARTIFACT
Log In
T
Turquoise Loon
Why is this request considered as a feature request instead of a bug when the documentation indicates that this is working?
N
Nofar Bluestein
Merged in a post:
Not possible to trigger the CI step with an artefact
V
Vital Ocelot
is there any specific reason why is it not possible to trigger the CI step using the newly published artefact?
In a situation, where a new Docker image is being published in the artefact repository, it would be great to create a new version of the chart that includes the newly published image. In current version of Harness, this seems not to be possible. Is there a way to remove this limitation?
N
Nofar Bluestein
marked this post as
long-term
F
Fawn Antelope
Any updates on this?
S
Safflower Unicorn
marked this post as
pending feedback
Fawn Antelope Thank you for submitting the feedback. Can you please describe your use-case?
F
Fawn Antelope
Safflower Unicorn: Yes, I had a support ticket and a whole conversation back and forth with support on enabling this feature until they saw it didn't exist? I have a pipeline building an ECR container based on another container. This pipeline is triggered on a new ECR artifact of the base container. The trigger works fine but the
build
stage to build the container and push to ECR throws the above error.F
Fawn Antelope
Safflower Unicorn: Let me know if you need anything else from me.