Skip to main content
Solved

Azure Pipeline

  • 29 March 2023
  • 7 replies
  • 132 views

Hi Team

I am working on cognite  Functions and  we have 3 cognite instances now,

Tiger-training

Demo-dev

demo-prod

I have created the pipeline such a way that it is built and deployed with the single run and it is pointing to either of the instance based on the credentials provided in azure.pipeline.yaml file.

functions-deploy-azure-pipelines/azure-pipelines.yaml at main · cognitedata/functions-deploy-azure-pipelines · GitHub 

I am using the same pipeline file which is mentioned in the above link

So now my requirement is to build a separate build pipeline  that will build our cognite functions code, it builds and zips the

Cognite functions and create separate release pipeline for  and Deploy the zipped functions code to 3 different instances independently.

Please help me on this as it is a show stopper for us, 

please set up a call anytime before 9 pm today and after 10.30 am tomorrow.

 

Regards,

Nidhi N G

This setup is not supported by our pipeline action. It will build the zip file and create the function in the same codebase.

What’s the value of doing it with a single zip file? The contents of the zip file will the same when ran on the same source code.

 

Not sure I fully understand the question, but if you need to deploy to separate projects, I guess you can add multiple “Deploy Functions to CDF” steps in the pipeline, each pointing to different secrets/clientID/tenantID

We want to deploy the function in automated fashion in lower environment (e.g dev-CDF project , test CDF -project) from the single code base, and for deploying to production we want to manually execute release pipeline (based on our CR approvals and process). We will be tagging the master/main (version control) for  production deployment after we test in test CDF  project

We want to isolate CD(release) from CI(build) pipeline

I think you should be able to do that by having a different pipeline trigger, for example deploy to test with a "pull request trigger", test it and merge it to master after approval which would then deploy to production 

Hi @N G Nidhi @jaydeep just checking in to see if you could use more information from us with regards to the above, or if you’re all good for now? 

Hi @Anita Hæhre  , I am able to deploy my functions to 3 different instances using a single pipeline.yaml file.

I am attaching the pipeline.yaml file here so that it will help others to have a reference.

Thanks for the support.

 

Regards,

Nidhi N G

Hi @N G Nidhi, thanks so much for sharing with the community! 🙌

Reply


Terms & ConditionsCookie Settings