dotnet / dotnet/arcade-services
Validation pipeline after the release
- Dominant language
- C#
- Stars
- 86
- Forks
- 86
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 35
Description
There are already few validation steps we have in the pipeline. Some of them are pre-validation done before the release step starts and then there are plenty of them we would like to run after the all releases are done. It should validate over all consistency of published assets, packages, checksums and manifest data.
## Goal
Have one release validation pipeline which would have variety of jobs checking consistency.
It will be run after the release process to confirm that the release did correct things.
It would be possible to run it even whenever in non-release bound period and it will do the same consistency checks.
# Steps
- Create post-release-validation pipeline
- Put it close to the release pipelines
- Add it to the release tracker to have a visibility how to trigger it and see the run results (from AppInsights)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.