-
Notifications
You must be signed in to change notification settings - Fork 8
MTA-5378 Developer Lightspeed: Running an Analysis and Applying Fixes #175
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
base: main
Are you sure you want to change the base?
Conversation
5afd729
to
d663406
Compare
|
||
* Displays issues in all the files in your project in the *Issues* pane. | ||
* While generating suggestions to resolve issues, you can view the migration hints that explain the resolution and in which files the updates are applied. | ||
* Generates new files in *Resolutions* pane. These files have the updates to the code that resolves the issues detected in the current analysis. You can review the changes, apply, or revert the updates. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Generates new files in *Resolutions* pane. These files have the updates to the code that resolves the issues detected in the current analysis. You can review the changes, apply, or revert the updates. | |
* Generates new files in the *Resolutions* pane. These files have the updates to the code that resolve the issues detected in the current analysis. You can review the changes, apply or revert the updates. |
.. *All*: lists all incidents identified in your project. | ||
.. *Files*: lists all the files in your project for which the analysis identified issues that must be resolved. | ||
.. *Issues*: lists all issues across different files in your project. | ||
. Use the *Category* drop down to filter issues based on the how crucial the fix is for the target migration. You can filter mandatory, potential, and optional issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
. Use the *Category* drop down to filter issues based on the how crucial the fix is for the target migration. You can filter mandatory, potential, and optional issues. | |
. Use the *Category* drop-down to filter issues based on how crucial the fix is for the target migration. You can filter mandatory, potential, and optional issues. |
= Running an analysis in agent mode | ||
|
||
[role="_abstract"] | ||
In the agent mode, {mta-dl-plugin} planning agent creates the context about an issue and picks a sub agent that is most suited to resolve the issue. The sub agent runs an automated analysis to detect issues and generate files with the updated resolutions in one stream. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the agent mode, {mta-dl-plugin} planning agent creates the context about an issue and picks a sub agent that is most suited to resolve the issue. The sub agent runs an automated analysis to detect issues and generate files with the updated resolutions in one stream. | |
In the agent mode, {mta-dl-plugin} planning agent creates the context about an issue and picks a sub-agent that is most suited to resolve the issue. The sub-agent runs an automated analysis to detect issues and generate files with the updated resolutions in one stream. |
[role="_abstract"] | ||
In the agent mode, {mta-dl-plugin} planning agent creates the context about an issue and picks a sub agent that is most suited to resolve the issue. The sub agent runs an automated analysis to detect issues and generate files with the updated resolutions in one stream. | ||
|
||
You can review the updated files and approve or reject the changes to the code. The agent runs another automated analysis to detect new issues in the code or diagnostic issues that your tool may generate following a previous analysis. If you allow the process to continue, {mta-dl-plugin} runs the stream again and generates a new files with the latest updates. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can review the updated files and approve or reject the changes to the code. The agent runs another automated analysis to detect new issues in the code or diagnostic issues that your tool may generate following a previous analysis. If you allow the process to continue, {mta-dl-plugin} runs the stream again and generates a new files with the latest updates. | |
You can review the updated files and approve or reject the changes to the code. The agent runs another automated analysis to detect new issues in the code or diagnostic issues that your tool may generate following a previous analysis. If you allow the process to continue, {mta-dl-plugin} runs the stream again and generates a new file with the latest updates. |
. Click *Start* to start the {ProductShortName} RPC server. | ||
+ | ||
. Click *Run Analysis* on the *Konveyor Analysis View* page. | ||
The *Resolution Details* tab opens where you can view the automated analysis that makes changes in applicable files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The *Resolution Details* tab opens where you can view the automated analysis that makes changes in applicable files. | |
The *Resolution Details* tab opens, where you can view the automated analysis that makes changes in applicable files. |
. Open *Source Control* to access the updated file. | ||
+ | ||
. In the *Resolution Details* view, accept the proposal from {mta-dl-plugin} to make further changes. | ||
The stream of analysis repeats after which you can review and accept change. {mta-dl-plugin} creates the file with the code changes and the stream continues until you reject the proposal for further analysis. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The stream of analysis repeats after which you can review and accept change. {mta-dl-plugin} creates the file with the code changes and the stream continues until you reject the proposal for further analysis. | |
The stream of analysis repeats, after which you can review and accept change. {mta-dl-plugin} creates the file with the code changes, and the stream continues until you reject the proposal for further analysis. |
.Prerequisites | ||
|
||
* You installed the {ProductShortName} distribution version 8.0.0 in your system. | ||
* You installed Jave 17+ and Maven 3.9.9+ in your system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* You installed Jave 17+ and Maven 3.9.9+ in your system. | |
* You installed Java 17+ and Maven 3.9.9+ in your system. |
+ | ||
. Click *Start* to start the {ProductShortName} RPC server. | ||
+ | ||
. Click *Run Analysis* on the *Konveyor Analysis View* page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
. Click *Run Analysis* on the *Konveyor Analysis View* page. | |
. Click *Run Analysis* on the *Konveyor Analysis View* page. |
+ | ||
. Click *Run Analysis* on the *Konveyor Analysis View* page. | ||
|
||
To resolve the identified issues, see Applying resolutions after a solution server analysis. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will you be adding a link or xref later... just looks a little weird
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great start... wee bit of polishing and a few tiny issues
But it is a great start.
JIRA
Version
Preview