-
Notifications
You must be signed in to change notification settings - Fork 19
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
add some args (upload/download interval and parallelism on upload) #5
Conversation
… ao publisher: * target.uploadInterval * target.concurrentUploads * dryRun
src/main/java/io/github/netmikey/mvncloner/mvncloner/Publisher.java
Outdated
Show resolved
Hide resolved
src/main/java/io/github/netmikey/mvncloner/mvncloner/Publisher.java
Outdated
Show resolved
Hide resolved
src/main/java/io/github/netmikey/mvncloner/mvncloner/Publisher.java
Outdated
Show resolved
Hide resolved
@cleciusjm I added a couple of improvements according to what we discussed above. I don't have test Nexus servers at hand anymore unfortunately. Would you mind testing my changes to see if they work as described in the README and don't break existing behavior? |
nice, only check action feel like duplicated code to me, but ok my new nexus is in production, i cant run publish action, but mirror and check seems ok to validate here |
I agree about the code duplication. The 3 lines of Anyway, let me know when you've been able to test-drive the mirror and check actions :-) |
nvm, I got rid of the duplicated |
Check is failing because target address itself resolves as 404, but internal artifact addresses prefixed by it are funcional.
|
that's why my previus check action was targeting artifacts from mirror, and check everything working status without only uploading new data |
Well, if you ran your initial code against an empty target repository, this repository would've also returned 404 since you were doing an http HEAD on the target artifacts themselves, which aren't present on an empty repository. The thing is that you accepted http 404 as the expected return code and went on. So in short, I think without writing to the target there's nothing else we can do but check that we get an http 200 (or 404) in response to the root URL, which would be the only existing URL in an empty repository. I added a commit that accepts http 404 now too for the target check. |
Created some args to allow more personalized usage: