-
Notifications
You must be signed in to change notification settings - Fork 443
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
Duplication of jars in packaged zip artifact (unpredictable) #759
Comments
Duplicated entries in the I would close this issue and reopen it, if we can somehow reduce this problem to a more specific error source. Zipping has some issue, but mostly with executable flags being dismissed. At this point I would blame cosmic bitflipping :D Also this is unrelated to #657 as there are duplicated entries, but with different paths. |
Yeah, I just wanted to record this issue as a focus in case anyone else ever experienced it again... hopefully they won't! |
No real further details to report, other than this issue happened again 😿 Same build process and same clashing jars. guardian/members-data-api#97 & @tomverran were the victims this time. Maybe we should add a final step to our build process validating that the zip files are ok... |
Happened again today (builds 9055 & 9054) - still the same jar!
|
Are you using native zipping or the java nio2 zipping facility? |
Deployment of PR #1358 failed due to sbt/sbt-native-packager#759, where jars in an artifact built with native packager occurred twice within the zip file. #1358 (comment) On the recommendation of Nepomuk Seiler, we tried using `useNativeZip` on a different project: guardian/members-data-api#100 ...and it seemed to help.
Using In my root project
then in my sub project I repeat that same mappings command above (thus running it twice). Pretty obvious, but just wanted to point it out. It is possible! |
Thanks for sharing! 🤗 |
These jars in an artifact built with native packager (v1.0.1) both occurred twice within the zip file with the same path:
So using GNU
unzip
on the archive produces this deploy-halting query:I have to confess, I have not been able to reproduce this issue locally - it just seemed to happen once on our TeamCity server (EC2 cloud agent, java-8-openjdk-amd64, Linux 4.2.0-27-generic). Subsequent builds have been fine so far. This issue may well not be the fault of native-packager, just some cosmic-bitflipping occurring with an AWS EC2 box, I just wanted to record that this problem had occurred. I think it's unrelated to #657 ?
The project in question was public: https://github.com/guardian/members-data-api/ - you can try to reproduce the issue like this if you like:
The text was updated successfully, but these errors were encountered: