-
Notifications
You must be signed in to change notification settings - Fork 138
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
Extend leappdb with more execution information #1152
Conversation
Thank you for contributing to the Leapp project!Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergeable.
Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build. If you need a different version of leapp from PR#42, use It is possible to schedule specific on-demand tests as well. Currently 2 test sets are supported,
[Deprecated] To launch on-demand regression testing public members of oamg organization can leave the following comment:
Please open ticket in case you experience technical problem with the CI. (RH internal only) Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra. |
I've rebased the branch against up-to-date upstream. |
Related to changes extending the information stored in the leapp db. After this comment, the command line arguments as well as the environment variables modifying the leapp execution (env vars starting with `LEAPP_`) will be stored in the database. Works on: OAMG-8402
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.
lgtm! thanks!
Work like a charm:
|
Related to changes extending the information stored in the leapp db. After this comment, the command line arguments as well as the environment variables modifying the leapp execution (env vars starting with
LEAPP_
) will be stored in the database.JIRA: OAMG-8402