Skip to content

Conversation

@v1v
Copy link
Member

@v1v v1v commented Sep 15, 2022

What

Support for an interactive pipeline, so every stage will require a prompt confirmation.

Why

This is handy when something happens during the release, and you would like to rerun the pipeline but skipping some stages.

Implementation details

Rather than running from a particular stage onwards, this interactive pipeline will allow further granularity about what stage should be run individually, a bit tedious but worthy in terms of running one stage from the middle if needed, besides a bit less complex

Actions

  • Agree with the team
  • Set release version requires an input parameter to gather some env variables

UI

I just recorded how this interactive approach will work, (it failed as my local playground doesn't have slack correctly configured)

Once selected the interactive option

image

Kapture 2022-09-15 at 12 40 19

@v1v v1v mentioned this pull request Sep 15, 2022
2 tasks
@ghost
Copy link

ghost commented Sep 15, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-09-15T11:44:22.457+0000

  • Duration: 37 min 36 sec

Test stats 🧪

Test Results
Failed 0
Passed 2518
Skipped 31
Total 2549

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • run benchmark tests : Run the benchmark tests.

  • run jdk compatibility tests : Run the JDK Compatibility tests.

  • run integration tests : Run the Agent Integration tests.

  • run end-to-end tests : Run the APM-ITs.

  • run windows tests : Build & tests on windows.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant