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

[RFE] Detect language & frameworks being used in repositories on import #131

Open
jwmatthews opened this issue Jun 27, 2023 · 2 comments
Open
Milestone

Comments

@jwmatthews
Copy link
Member

As a user importing a source code repository to Konveyor I would like to see Konveyor understand the languages and frameworks used in the source code (prior to running a full code Analysis), similar to the kind of view GitHub provides on a repository with a break out of language percentages...plus more metadata to help get a sense of the frameworks being used.

One possibility to consider for achieving this is to explore leveraging 'Alizer':
https://github.com/redhat-developer/alizer which is a component of https://devfile.io/

Related to #122

@rromannissen
Copy link
Contributor

@jortel I imagine this could be implemented by running the discovery rules automatically when an application has repository info and (optionally if required) credentials associated to it. We should make sure to implement the concept of priorities for tasks, as these automated tasks should have lower priority than anything scheduled by the user.

@rromannissen rromannissen added this to the 0.4.0 milestone Nov 7, 2023
@shawn-hurley
Copy link
Contributor

I would be concerned about doing it that way when we don't know the language and which rulesets/targets to use for discovery, IMO.

It will have to be potentially a two-step process: 1. figure out languages (and therefore the provider/rulesets that are needed) and 2. run the discovery rules for all rulesets that are for a particular language, would be my guess.

@rromannissen rromannissen modified the milestones: 0.4.0, v0.4.0 Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants