Replace Legacy .zip packaging with the new DualityTemplates .zip packaging
See original GitHub issueSummary
Right now, the NightlyBuilder will pack a binary .zip that will no longer be usable with the v4.0 pre-release. It will show up as a CI artifact and could otherwise confuse any future maintainers or users. This can be fixed by replacing it with the new DualityTemplates .zip that is generated on build.
Analysis
- Remove all legacy
.zipcode from NightlyBuilder, e.g. this block, this block and all related config variables. - Remove the legacy AdditionalFiles folder and related config entries, and some more. This will leave the nightly builder with only build, test,
.chmdocs and package steps remaining as-is. - Update the CI artifact path for the template download
.zipto point to the new template.zip- or adjust the output path of the templates project to match it.
Simplifying NightlyBuilder as outlined above will also make it a little easier to talk about retiring NightlyBuilder altogether because there’s less moving parts left to identify for replacement.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Maven creating flat zip assembly
NET) into a single zip file. I'm having 2 problems: If I change packaging in my POM to zip <packaging>zip</packaging> , I get...
Read more >AdamsLair/duality: a 2D Game Development Framework
Duality is a plugin based 2D game development framework based on C# and OpenTK. To get a quick overview, ... You can find...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Its not meant for archival purposes because they clean it after 6 months 😃.
I believe the max artifact storage capacity is around 50GB (in case its not enough they are even willing to increase) so we would need alot of builds happening in 6 months to fill this up. Probably still best to just put a branch condition on it (only master/release) but commenting it out shouldn’t be necessary.
I never ran into problems with this as most CI’s auto clean after a while. Just don’t assume the files are there forever.
Some advantages:
EDIT: Its about 13MB per build (the duality zip is now alot smaller since it no longer has binaries) with 50GB that means we need to have almost 4000 builds happening within 6 months. Considering that duality doesnt even have that much commits during its entire history I don’t think we will ever reach that much so might as well just publish artifacts on every build. https://ci.appveyor.com/project/AdamsLairBot/duality/builds/33459842/artifacts
Will look into this the coming week