cd-demo | Simple CD pipeline demo with Jenkins Swarm | Continuous Deployment library

You need to bootstrap all of your (target) accounts to trust the CICD account.

Otherwise, you would have to create and manage the cross-account access by yourself.

• IAM Roles + Policies (in all accounts)
• S3 Bucket for artifacts + bucket policies (in CICD account)
• Key Management Service -> Customer Managed Key + Policies to allow the target accounts

You can spot here an example architecture, which is applying that:

If it's possible for you, you might switch to the CDK Pipelines. In this guide, also the bootstrapping (incl. trusting) is being applied and every step/resource mentioned from above is being created and properly configured. It has a few drawbacks as of now, but it's in developer preview and has a quite decent usability and makes your life a lot easier already.

Update:

Thanks for ennth's sharing. This error comes from changing of functionAppName.

(Since FunctionAppName need unique in all of the world when deployed, it will generate a string of numbers by default.)

Original Answer:

mvn azure-functions:deploy is mainly used for the first time, because the files it produces are not specified. It will It generates random resources, which is by design.

Have a look of this:

https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-java-maven?pivots=java-build-tools-maven#deploy-the-function-to-azure

Use mvn azure-functions:deploy should not face problem. Have you set something in pom.xml? There must be no character like - in storage account name.

This is my pom.xml, and it is no problem:

http://maven.apache.org/xsd/maven-4.0.0.xsd"> 4.0.0

The job is stuck because your runners have tags but your jobs don't. Follow these 4 steps to enable your runner to run without tags:

Or set tags to your jobs. For more info: Configuration of your jobs with .gitlab-ci.yml - Tags

Shared runners will run for any branch, so for the master branch too (unless you configure otherwise).

Additionally,

• you can pick-up a specific runner if you define a tag for your job.
• you can filter if the job will be triggered via only and/or except directives.

For example, following job will trigger for any push, despite the branch:

It will run on that node, which Jenkins thinks, is the best right now.

But you can define in your groovy-code on which node single steps or the whole pipeline should run, by the following code:

It will only run the job for your testing branch, have you added the .gitlab-ci.yml file to that branch too?