opendevstack / opendevstack/ods-provisioning-app

ODS Dashboard / Visual Studio Code Extension

Open
#648 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
14
Forks
20
Avg merge
3h 35m
Merged PRs (30d)
1

Description

Up till today a usual project powered by ODS comes along with a zoo of tools scattered all over a given OpenShift cluster. All those tools offer interesting or important information about...

  • running/successful/failed builds (Jenkins)
  • unit test reports (Jenkins)
  • OpenShift projects related to a project (OpenShift)
  • routes related to OpenShift projects (OpenShift)
  • code quality metrics (SonarQube)
  • etc.

How about we make these pieces of information available inside the provisioning app and therby extend the provisioning app's scope into something like an ODS Dashboard app, where the provisioning topic is one part of.

Alternatively or even in addition (maybe by using the same backend API) we can provide an ODS Extension for VSCode. This would allow us to also trigger actions from there, e.g.

  • enter Jira issue number and one-click >>self-assign+put "In Progress"+create branch in Bitbucket+git checkout<<
  • one-click pull request creation: creates PR in Bitbucket from current branch in VSCode
  • rerun Jenkins builds
  • provision new component
  • clone OpenShift project and rebuild it from current branch
  • etc.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the provisioning app and the proposed shared backend API, then compare the ODS Dashboard and VS Code extension options. Identify which Jenkins, OpenShift, SonarQube, Jira, and Bitbucket information or actions are in scope; the issue is complete only when a concrete scope and implementation direction are agreed.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot, vscode
Domain
developer-experience, devops, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.