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

Run analysis directly and upload results to hub #193

Open
djzager opened this issue Apr 12, 2024 · 0 comments
Open

Run analysis directly and upload results to hub #193

djzager opened this issue Apr 12, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@djzager
Copy link
Member

djzager commented Apr 12, 2024

Use case: A user wants to analyze a specific application. Situation dictates that manual intervention is required to setup the project AND the analysis cannot be containerized. What we need is a way for the user to analyze their project directly (engine + provider(s) not containerized) and submit the results to the hub for aggregation.

A more specific example would be the nerd-dinner analysis scenario where a lot of pre-work must be done before the analysis can be performed. Rather than telling the user to then do some work in the UI, it would be great if the user could stay on the host and execute a combination of commands that:

  • Setup the dotnet-external-provider (although it may be okay for this to be manual, I don't know that we want to jump into a plugin architecture).
  • Starts the provider and configures it to listen on some local port
  • Runs the analysis and generates results
  • Results uploaded to some konveyor UI endpoint for aggregation

cc @pranavgaikwad @rromannissen

@djzager djzager added triage/accepted Indicates an issue or PR is ready to be actively worked on. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 12, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Apr 12, 2024
@eemcmullan eemcmullan moved this from 🆕 New to 📋 Backlog in Planning May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant