-
Notifications
You must be signed in to change notification settings - Fork 125
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
Discover plugin to fetch sources from dist-git #742
Conversation
This pull request introduces 5 alerts when merging 68aec87 into c5b5172 - view on LGTM.com new alerts:
|
68aec87
to
2b92a82
Compare
A lot of work ahead however seems to be doing something
|
/packit test |
Note to self: https://pagure.io/standard-test-roles/blob/master/f/roles/standard-test-source/library/source-lookaside.py doesn't use *pkg binary, lets get inspired. |
2b92a82
to
a938494
Compare
Reworked after today's discussion on the hacking session.
Future plans: Allow to run |
This pull request introduces 1 alert when merging a938494 into 73cbb21 - view on LGTM.com new alerts:
|
a938494
to
a2d07a5
Compare
ouch. |
a2d07a5
to
3ce81c9
Compare
Seems there's one more:
|
3ce81c9
to
9b34672
Compare
Do we want to support fetching URL first and extract sources from there? E.g.
EDIT: Currently not supported (either from or url/ref) but this could be handy for using integration tests.... |
9b34672
to
c3be05a
Compare
Updated to support url/ref/path and added documentation. Now the question is about 'path' when used in from: sources. First is handy for ad-hoc (and mostly local) experiments (see "Path pointing to the DistGit (Fedora)" test) How about making sure absolute vs relative path works? When used with |
6a8b616
to
7799a14
Compare
For loading internal distgit #925 could be used |
From hacking session notes:
How about
Probably not for |
I like the idea of explicitly mentioning
Or, in order to make it a bit more user-friendly, use the distinct part of the class name only?
Or should it be rather |
I've found https://github.com/release-engineering/dist-git so |
50b2ae3
to
5c10bb4
Compare
This pull request introduces 1 alert when merging 5c10bb4 into cb4dd64 - view on LGTM.com new alerts:
|
5c10bb4
to
f9356a7
Compare
Tests failed with:
Looks like a forgotten file? |
f9356a7
to
68e0832
Compare
Renamed file to distigit . And it was easier to run the test directly (not using tmt) :/ |
LGTM. |
Structure the spec documentation into sections. Update option names to make the config working. Extend the test with a basic plan/config scenario. Plus a couple of minor code style adjustments.
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.
Thanks a lot for implementing this, @lukaszachy. Looks good in general. I just ran into problem with wrong option names which caused the feature would not work when enabled from a plan. This should now be fixed by cccc94e. I've also extended the test a bit and updated the spec to make it structured (the list of available options was already quite long). Please, have a look and check if everything's ok.
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 for the adjustments @psss
First step on #585