Closed fjmilens3 closed 4 years ago
Hi, any news on this PR ? Thanks.
@cderv not as of yet, I take it this would be useful for you?
We have a nexus repository for our DevOps process in my company. However, it is no use for datascientist like me as it is difficult to use with R. I tried to make it work but not so easy. Currently, for R development we are testing other repository solutions.
Unfortunately I am not a Java guy... so it is difficult me to help on this one. I was curious about the status.
@jlstephens89 no major reason not to, I can try and freshen it up and use StreamCopier amongst other things
event-driven generation of PACKAGES.gz was created in separate PR according to a new structure. This PR could be closed. #97
Treats the
PACKAGES.gz
file as an actual file for purposes of R hosted repositories rather than dynamically generating on each request. Much of this is based on our current practices for the Nexus 3 Yum implementation, adjusted for the various differences in format and design.This pull request makes the following changes:
RPackagesBuilderFacet
responsible for event-driven generation of packages metadata.RHostedFacetImpl
to serve up existing content rather than using dynamic generaton.Note that this only deals with the
PACKAGES.gz
file, not the introduction of otherPACKAGES
types. Also note that this change is not backward compatible as-is (it should not be included in a subsequent release) since existing repos could be populated with content, but as of this PR we only regenerate metadata when a change is detected; therefore you could end up with perfectly-working repos having noPACKAGES.gz
to serve up.We could deal with this a couple of ways, including the addition of a task, or adding something to this PR that kicks off an invalidation request if we ever detect that we don't have a
PACKAGES.gz
file present. (This would probably be my first inclination as it could go in this PR rather than leaving things in the middle.)It relates to the following issue #s: