-
Notifications
You must be signed in to change notification settings - Fork 64
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
Fetcher approach is too narrow #552
Comments
ryan-beisner
pushed a commit
to ryan-beisner/charm-tools
that referenced
this issue
Oct 4, 2019
ryan-beisner
pushed a commit
to ryan-beisner/charm-tools
that referenced
this issue
Oct 4, 2019
ryan-beisner
pushed a commit
to ryan-beisner/charm-tools
that referenced
this issue
Oct 4, 2019
ryan-beisner
pushed a commit
to ryan-beisner/charm-tools
that referenced
this issue
Oct 4, 2019
johnsca
pushed a commit
that referenced
this issue
Oct 8, 2019
As mentioned in the PR, at the very least, the existing git fetcher classes should be refactored to inherit from |
timClicks
pushed a commit
to timClicks/charm-tools
that referenced
this issue
May 6, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a notion of "fetchers" in charm-tools, which might seem to allow for a wide range of approaches (source code repos). However, in moving one project from Github.org to Opendev.org, we end up with a
No fetcher or url
error.Perhaps there should be a generic https fetcher?
https://bugs.launchpad.net/charm-barbican/+bug/1846263
The text was updated successfully, but these errors were encountered: