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: src/artifacts-helper/NOTES.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,10 +49,21 @@ This ensures any custom scripting in place during Codespaces build process will
49
49
The shim scripts (e.g., `dotnet`, `npm`, `nuget`) now include a wait mechanism for the Azure DevOps authentication helper. When invoked, these scripts will:
50
50
51
51
1. Wait up to 3 minutes for the `ado-auth-helper` to become available (configurable via `MAX_WAIT` environment variable)
52
-
2. Display progress indicators every 20 seconds while waiting
52
+
2. Display progress indicators every 20 seconds while waiting (only when `ARTIFACTS_HELPER_VERBOSE=true`)
53
53
3. Continue execution once authentication is successful
54
54
4.**Continue with the underlying command even if authentication is not available** after the timeout
55
55
56
+
By default, the authentication process runs silently. To enable verbose logging (useful for troubleshooting), set the `ARTIFACTS_HELPER_VERBOSE` environment variable to `true`:
57
+
58
+
```bash
59
+
export ARTIFACTS_HELPER_VERBOSE=true
60
+
```
61
+
62
+
When verbose mode is enabled, you will see step-by-step messages like:
63
+
-`::step::Waiting for AzDO Authentication Helper...`
This ensures that package restore operations can proceed even if there's a slight delay in the authentication helper installation, which can occur in some codespace initialization scenarios. Commands will still execute without authentication, though they may fail to access private Azure Artifacts feeds.
57
68
58
69
The scripts are designed to be sourced safely, meaning they won't terminate the calling shell if authentication fails - they will simply return an error code and allow the underlying tool to execute. This allows you to work with public packages or other package sources even when Azure Artifacts authentication is unavailable.
0 commit comments