You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/try_new_features_before_release.md
+19-7Lines changed: 19 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,16 @@
1
1
# Try new features before release
2
2
3
-
This documentation shows how to try new features in commit or PR before release even if the PR is not merged.
3
+
This documentation shows how to try new features in commits or PRs before release even if the PR is not merged.
4
4
5
-
Azure CLI releases new versions every 3 weeks. Many customers and developers are eager to try and test new features before the formal release. Fortunately, Azure CLI project builds artifacts for every commit and PR and you can download them.
5
+
Azure CLI release schedule can be found at https://github.com/Azure/azure-cli/milestones. Many customers and developers are eager to try and test new features before the formal release. Fortunately, Azure CLI project builds artifacts for every commit and PR and you can download them.
6
6
7
-
## Tutorial for commit
7
+
## Install edge builds for `dev` branch
8
+
9
+
The most convenient way is to [install edge builds](https://github.com/Azure/azure-cli#edge-builds) released for every commit on `dev` branch.
10
+
11
+
If no edge builds are released for your platform, you may directly install the artifacts built by the CI pipeline as described below.
12
+
13
+
## For commits
8
14
9
15
Step 1. Select a commit. Click the √ or × symbol. Click "Details" of a "build package" item.
10
16
@@ -22,7 +28,7 @@ Step 4. Download your favorite artifact.
22
28
23
29

24
30
25
-
## Tutorial for PR
31
+
## For PRs
26
32
27
33
Step 1. Open a PR no matter it is merged or not. Click "Checks" tab.
28
34
@@ -39,19 +45,22 @@ Follow the same steps in previous sessions and find artifact page. Click `pypi`
`azure_cli-2.6.0-py3-none-any.whl`, `azure_cli_command_modules_nspkg-2.0.3-py3-none-any.whl`, `azure_cli_core-2.6.0-py3-none-any.whl`, `azure_cli_nspkg-3.0.4-py3-none-any.whl`, `azure_cli_telemetry-1.0.4-py3-none-any.whl` are packages of Azure CLI. `azure_mgmt_imagebuilder-1.0.0-py2.py3-none-any.whl` is a package of Image Builder resource provider. You should change it to your own SDK package containing the new feature.
50
+
`azure_cli-2.6.0-py3-none-any.whl`, `azure_cli_core-2.6.0-py3-none-any.whl`, `azure_cli_telemetry-1.0.4-py3-none-any.whl` are packages of Azure CLI. `azure_mgmt_imagebuilder-1.0.0-py2.py3-none-any.whl` is a package of Image Builder resource provider. You should change it to your own SDK package containing the new feature.
45
51
46
52
We recommend using a virtual environment to install the `.whl` files. This is an optional step.
47
53
Example commands in PowerShell:
48
54
49
55
```powershell
50
-
# Create a virtual environment
56
+
# Create a virtual environment
51
57
python -m venv env
52
58
53
59
# Activate it
60
+
# PowerShell
54
61
env\Scripts\activate.ps1
62
+
# Linux/MacOS Bash
63
+
. ./env/bin/activate
55
64
```
56
65
57
66
## Install from source code
@@ -70,7 +79,10 @@ git checkout <branch>/<commit>
70
79
python -m venv env
71
80
72
81
# Activate the virtual environment
82
+
# PowerShell
73
83
env\Scripts\activate.ps1
84
+
# Linux/MacOS Bash
85
+
. ./env/bin/activate
74
86
75
87
# Install azdev - the development tool for Azure CLI
0 commit comments