-
Notifications
You must be signed in to change notification settings - Fork 35
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update build pipeline, add CODEOWNERS and development docs (#114)
* Add CODEOWNERS and docs Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * TEMP: changes for testing Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Use GH CLI instead of github-release-cli Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Try to fix this one? Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Add another token Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Update Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Remove the IF Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Ok! Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Edit version Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Another try Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Prepare for release Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Use export syntax Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Skip signing Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Use GitHub token Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Reorder steps Signed-off-by: Shubham Sharma <shubhash@microsoft.com> * Add release notes Signed-off-by: Shubham Sharma <shubhash@microsoft.com> --------- Signed-off-by: Shubham Sharma <shubhash@microsoft.com>
- Loading branch information
1 parent
b2d6a57
commit 9863459
Showing
7 changed files
with
112 additions
and
40 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# These owners are the maintainers of this repo | ||
* @Azure/maintainers-azure-functions-dapr-extension |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
# Development | ||
|
||
* [Development](./development.md) - How to setup local development environment and build/test Azure Functions Dapr Extension. | ||
* [Release Process](./release-process.md) - How to release Azure Functions Dapr Extension. | ||
* [Setup Continuous Integration](./setup-ci.md) - How to setup GitHub Actions for Azure Functions Dapr Extension. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# Setup Local Development | ||
|
||
This document is a TODO. | ||
|
||
## Prerequisites | ||
|
||
## Clone the repository | ||
|
||
## Build the project | ||
|
||
## Run tests | ||
|
||
## Debugging |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
# Release Process | ||
|
||
This document describes the release process for Azure Functions Dapr Extension. | ||
|
||
## Trigger a release | ||
|
||
1. Create a new branch from `master` branch in the format of `release-<major>.<minor>` (e.g. `release-0.14`). | ||
2. Add a tag and push it. | ||
```bash | ||
$ git tag "v0.14.0-preview01" -m "v0.14.0-preview01" | ||
$ git push --tags | ||
``` | ||
3. CI will create a new release in GitHub, push the NuGet packages to Azure blob storage, and upload the sample image to Docker registry. | ||
4. [MICROSOFT PROCESS] Upload the NuGet packages to NuGet.org using the Azure DevOps pipeline. | ||
5. Edit the release notes if necessary. | ||
6. Test and validate the functionalities with the specific version | ||
7. If there are regressions and bugs, fix them in `release-*` branch and merge back to master | ||
8. Create new tags (with suffix -preview02, -preview03, etc.) and push them to trigger CI to create new releases | ||
9. Repeat from 6 to 8 until all bugs are fixed |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# Setup Continuous Integration | ||
|
||
This repository uses GitHub Actions to automate the build and release. As long as you have a GitHub Account, you can set up your own private Actions in your own fork. This document helps you set up the continuous integration for Azure Functions Dapr Extension. | ||
|
||
## Prerequisites | ||
|
||
A GitHub account. | ||
|
||
## Setup | ||
|
||
1. Fork [Azure/azure-functions-dapr-extension](https://github.com/Azure/azure-functions-dapr-extension) to your GitHub account. | ||
2. Go to `Settings`-> `Secrets and variables` -> `Actions`. | ||
3. Add the required repository secrets. | ||
|
||
### Required repository secrets | ||
|
||
| Name | Description | | ||
|--|--| | ||
| DOCKER_REGISTRY_ID | Username for Docker registry, required for uploading sample image| | ||
| DOCKER_REGISTRY_PASS | Password for Docker registry, required for uploading sample image| | ||
| DOCKER_REGISTRY | URL to Docker registry, required for uploading sample image | | ||
| AZCOPY_SPA_APPLICATION_ID | Service principal application ID for AzCopy, required for uploading NuGet packages | | ||
| AZCOPY_SPA_CLIENT_SECRET | Service principal client secret for AzCopy, required for uploading NuGet packages | | ||
| GITHUB_TOKEN | GitHub token, required for creating release | | ||
|
||
Notes | ||
- `GITHUB_TOKEN` is automatically set by GitHub Actions, so you don't need to set it manually. | ||
- `AZCOPY_*` secrets should not be set for forks, as they are only required for uploading NuGet packages for official release. The step that requires these secrets will be skipped for forks. | ||
|
||
4. Go to `Settings` -> `Actions` -> `General` and make sure to allow running GitHub Actions. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters