Deploying to same iflow to same tenant but to different package like QA

[itstushar22]

I have build jobs to deploy to same tenant but in different package.

• I copy the same iflow "TestCICD" artifacts and move to new package. And rename with same "TestCICD_Q" and add the new properties folder. Here is the repo structure.

• New iflow creation works with designtime creation but deploy to runtime is not working. see the screenshot below

• 

• Also if i try to redeploy using the same job the update fails at designtime since this iflow already exist ,see the screenshot below

[engswee]

Hi @itstushar22

1. For the deployment, the error shows that artifact-ids is not set. Please check your configuration
2. For updating the same IFlow to a different package and IFlow ID, I can't tell what is causing the problem from the screenshot. If you could share the configuration of the job, that may help. Alternatively, I suggest you check out https://github.com/engswee/flashpipe-demo/tree/azure-pipelines that shows how an artefact can be deployed multiple times to the same tenant but with different package/ID. Note the example is for Azure Pipelines, but the approach should be similar for GitHub Actions.

[itstushar22]

i will check this jobs, Thanks!