You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploy Package action fails with error 'Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run'
#625
Open
parvezghumra opened this issue
Feb 18, 2025
· 0 comments
We have a single job in a Github Action workflow which attempts to deploy multiple different Package Deployer packages in sequential steps that use the 'Deploy Package' action
Although the deployment of the package succeeds according to the logs, it fails to upload the logs artifact with this error:
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
I see that in the latest release of the actions (v1.8.0) v4 of the upload artifact action is being used internally. According to this issue for that action artifact names must be unique, though I'm not sure whether this means unique across the workflow run, or unique for the specific job?
Since the 'Deploy Package' action does not enable a way to control the name of the artifact, this forces us to have a separate workflow/job for each package we need to deploy. The product we are trying to deploy is split across multiple packages and that is how the vendor ships it to us and we have no control over this. However, we require all the packages to deployed.
**EDIT 18-02-2025 16:51 GMT: From further testing it seems that the artifact name must be unique across the entire workflow. Therefore, even separating out each package deployment into a separate job in the workflow does not satisfy the uniqueness criteria. I'm reluctant to have a separate workflow run for each package as it complicates our deployment logic. **
My request is for the 'Deploy Package' action to provide a way to control the name of the logs artifact that is uploaded**
The text was updated successfully, but these errors were encountered:
We have a single job in a Github Action workflow which attempts to deploy multiple different Package Deployer packages in sequential steps that use the 'Deploy Package' action
Although the deployment of the package succeeds according to the logs, it fails to upload the logs artifact with this error:
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
I see that in the latest release of the actions (v1.8.0) v4 of the upload artifact action is being used internally. According to this issue for that action artifact names must be unique, though I'm not sure whether this means unique across the workflow run, or unique for the specific job?
Since the 'Deploy Package' action does not enable a way to control the name of the artifact, this forces us to have a separate workflow/job for each package we need to deploy. The product we are trying to deploy is split across multiple packages and that is how the vendor ships it to us and we have no control over this. However, we require all the packages to deployed.
**EDIT 18-02-2025 16:51 GMT: From further testing it seems that the artifact name must be unique across the entire workflow. Therefore, even separating out each package deployment into a separate job in the workflow does not satisfy the uniqueness criteria. I'm reluctant to have a separate workflow run for each package as it complicates our deployment logic. **
My request is for the 'Deploy Package' action to provide a way to control the name of the logs artifact that is uploaded**
The text was updated successfully, but these errors were encountered: