Runbooks - Rundeck Validation

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem Statement

Executable Runbooks are a must for many companies, in #9427 (closed) we address many of the feature requirements to include:

• Be able to see what the status is
• Which tasks on track
• What is failing
• Tie a release to a runbook
• Release pages/lists should link to the runbook and show at least minimal status of the runbook (running, complete, etc.)

Reach

• Release Manager
• Delivery Manager
• Non-technical release parties

3.0 = Significant reach (~25% to ~50%).

Impact

1.0 = Medium impact

Confidence

50% = Low confidence

Effort

We have scoped and provided docs for Jupyter Hub , this issue will serve as the validation ground for leveraging Rundeck within GitLab for Runbook creation.

Stages

• Investigate Rundeck feature functionality
• Assess engineering effort for the integration
• Craft implementation plan
• Investigate API, UI, UX progression

What does success look like, and how can we measure that?

• MVC: Create runbooks in GitLab with API
• MVC: Edit, configure and execute runbooks GitLab with API
• MVC: Runbook status is available in API
• Create Runbooks in GitLab in UI
• Linking Runbooks to a release in UI
• See Runbook status in GitLab UI on a deployment page

Links / references

• Rundeck Docs