-
-
Notifications
You must be signed in to change notification settings - Fork 297
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
War downloaded and exploded every time #594
Comments
Hi @cdupont - just a fellow developer (not maintainer here). I am using a docker and prepared a custom Dockerfile where:
If you are not using docker you can just run that on your machine I hope it helps 🙏 |
Maybe help for a future reader, obvious, but something I initially overlooked: After you have exploded the
|
I am not sure the auto-download feature should be kept as a default behavior. The current Java implementation is less efficient than wget/curl. It makes sense to keep it, but behind an |
Manually downloading and decompressing the WAR is more effort than specifying a Jenkins version, but it seems necessary to skip a long download and extraction process. Would it be more user friendly to cache the extracted directory per Jenkins version? |
I use V1.0-beta30.
I get this for every invocation of jenkinsfile-runner:
Is it possible to cache the exploded war to save on time?
The text was updated successfully, but these errors were encountered: