Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define pre-release ecosystem tests setup #1143

Open
9 tasks
larsrickert opened this issue May 22, 2024 · 0 comments
Open
9 tasks

Define pre-release ecosystem tests setup #1143

larsrickert opened this issue May 22, 2024 · 0 comments
Labels
dev Requires technical expertise

Comments

@larsrickert
Copy link
Collaborator

larsrickert commented May 22, 2024

Why?

The idea is based on https://github.com/nuxt/ecosystem-ci
Basically: Nuxt updates are run against projects in the Nuxt ecosystem to test for breaking changes or regressions.

Acceptance criteria

  • A running PoC was built
  • We are able to trigger a run in an Azure DevOps project
  • We are able to receive success/failure messages of these runs and display them
    • Check how Nuxt or Vue integrate the results
    • Define how the results are reported and integrated

Definition of Done

  • follow-up tickets were created if necessary
  • updated version + documentation is deployed
  • Set task to In Approval

Approval

  • Deployed Docs
  • approved by dev

Implementation details

Basic concept:

  • Pre-Release triggers Eco-System CI
  • Eco-System CI triggers runs (e.g., via web hooks) for registered ecosystems, which in turn report their status back to us

Reference implementations

@larsrickert larsrickert added this to onyx May 22, 2024
@larsrickert larsrickert converted this from a draft issue May 22, 2024
@larsrickert larsrickert changed the title Define pre-release ecosystem Define POC for setting up pre-release ecosystem tests May 22, 2024
@JoCa96 JoCa96 changed the title Define POC for setting up pre-release ecosystem tests Define pre-release ecosystem tests setup May 22, 2024
@mj-hof mj-hof added this to the Release preparation milestone May 29, 2024
@JoCa96 JoCa96 moved this from New to Backlog in onyx Jun 19, 2024
@mj-hof mj-hof added the dev Requires technical expertise label Jun 26, 2024
@mj-hof mj-hof added the 0-refinement All issues that can or need to be estimated in our next refinement label Aug 20, 2024
@JoCa96 JoCa96 moved this from Backlog to Ready in onyx Aug 20, 2024
@JoCa96 JoCa96 removed their assignment Aug 20, 2024
@mj-hof mj-hof removed the 0-refinement All issues that can or need to be estimated in our next refinement label Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev Requires technical expertise
Projects
Status: Ready
Development

No branches or pull requests

3 participants