This section seems quite stale; it doesn't look like darc get-subscription-history exists any more.
|
#### 5. Validate |
|
|
|
At this time we don't have a way to notify users if something went wrong while updating dependencies but this work is tracked by |
|
https://github.com/dotnet/arcade/issues/821. |
|
|
|
To validate that created subscriptions and channels work as expected you'd need to verify that a PR has been created on your subscription's `targetRepository` once a build from `sourceRepository` has successfully completed. If a PR was not created something went wrong and we can use darc to find out what happened |
|
|
|
1. Obtain the id of the non-functioning subscription: |
|
``` |
|
darc get-subscriptions |
|
``` |
|
You can use various parameters to filter the list and find the subscription you're interested in. For instance: |
|
``` |
|
darc get-subscriptions --target-repo corefx |
|
https://github.com/dotnet/arcade (.NET Eng - Latest) ==> 'https://github.com/dotnet/corefx' ('master') |
|
- Id: c297d885-0692-40f8-6b97-08d61f281b4c |
|
- Update Frequency: everyDay |
|
- Merge Policies: |
|
AllChecksSuccessful |
|
ignoreChecks = |
|
[ |
|
"WIP", |
|
"license/cla" |
|
] |
|
- Last Build: N/A |
|
``` |
|
2. Use the ID and query for the subscription history: |
|
``` |
|
darc get-subscription-history --id <id> |
|
``` |
|
For example: |
|
``` |
|
darc get-subscription-history --id d2d2e80d-8b31-4744-1959-08d6175791f6 |
|
10/19/2018 9:15:17 AM: (Success) - Checking merge policy for pr 'https://api.github.com/repos/dotnet/arcade-minimalci-sample/pulls/129' |
|
10/19/2018 9:10:15 AM: (Success) - Checking merge policy for pr 'https://api.github.com/repos/dotnet/arcade-minimalci-sample/pulls/129' |
|
10/19/2018 9:05:14 AM: (Success) - Checking merge policy for pr 'https://api.github.com/repos/dotnet/arcade-minimalci-sample/pulls/129' |
|
10/19/2018 9:05:04 AM: (Success) - Updating subscription for build '146' |
|
``` |
|
Any failed actions will be marked as such, along with a retry command. |
|
3. Let @alexperovich, @jcagme or @mmitche know about the errors in the unsuccessful entry |
What's the latest best practice here?