You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@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.
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.
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
The text was updated successfully, but these errors were encountered: