Yes this can be done, Azure Pipelines can ingest a yaml file, configuring the pipeline as code. These yaml files should be source controlled and the pipeline can be set up to build in an automated way.
You can also reuse steps within the pipeline
This is not supported by Azure DevOps pipelines yet. Microsoft will provide it soon. Will update this post once they made it available.
Pretty straight forward way to get last commit user in Bash:
git log -1 --pretty=format:'%an'
Steps for download are described here: How To Download Azure BLOB Storage Using Azure PowerShell. According to this article, you have to use the connection string from the Access keys page. You can create your custom secret variable (Variables) and save a connection string in your new variable. Then in your ps scripts you can reference to connection string (...
I found the solution.
As build artifact you need to publish, firebase.json, .firebaserc and whole functions folder including package.json (without node_modules)
Then in release using sudo firebase deploy --token $(firebase-token) --project $(firebase-project) --only functions --force
I noticed that the description for the filepath properties of the pack command is different than the descriptions in the test and publish commands:
Pattern to search for csproj or nuspec files to pack.
You can separate multiple patterns with a semicolon, and you can
make a pattern negative by prefixing it with '-:'. Example:
A few questions so I can better understand your use case:
How often would this deployment/build of yours be run?
Will there ever be any changes going into Master that do not come from develop?
If you plan to run this deploy/build which would create a PR to merge to Master for each change in develop, then I would recommend to delete the develop branch and ...
You can set up Branch Policies on your develop branch which requires a build to pass successfully before the Pull Request can be completed.
I have set this up for my team with great success; we very rarely will have a broken master branch. The PR does not run the main build, but instead runs a separate, slimmed down build that checks that the code compiles ...
I would look into Azure Functions. Create a gate trigger and enable azure function after a successful release.