wyBuild- Is there really not a more efficient way?

I'm running into a wall with wyBuild. I just can't work with the way it requires me to store every single file of every single update ever. My project has about 1000 files, totalling around 1GB. I've been using wybuild for 2 months now and made over 10 updates, and now build time is just getting ridiculous.

If I want to release a change to just the main .exe file, I have to setup the whole lot again in wybuild, and it will compare EVERY file. Currently the update building process takes about 2 hours. For me the whole point of an auto updater is that I can release regular updates, but this isn't going to work at this rate.

My request is for these new features:

1 - The option in wybuild to make a new update that just says "Hey, just change this file, leave everything else the same". This would cut down on build-time, disk space, and me juggling files all the time.

2 - The option to have have a multiple update path. It needs to re-use some of the older updates. example: I have 10 versions, I make version 11, wybuild throws away all the old update builds and makes a completely new set (1-11, 2-11, 3-11....etc up to 10-11). This takes hours for me (and no doubt others with large projects.) It needs to reaach a point where I can say "keep all the old updates up to 10, and start from 10 for now on". So wyupdate will use update 1-10 to update the app to v10, then do a second update 10-11 to update to v11.

I know it will result in larger downloads, I don't mind. The most important thing for me is to be able to release quick bugfixes efficiently, it should take 5 minutes to update the main exe, not 2 hours.And yes I know there is an option for a "catch-all" update, but that would be a 600mb file, compared to the usual 5-10mb updates.

OR 3 - make a "catch-all" update that updates from version 1->latest, rather than just having the whole app in it. That would mean I could delete all the intermidiary versions (eg 2-8) and cut down the build time, without worrying about any users with version 4 getting a "no updates available" message and thinking there hasn't been any forever more.

2 - The option to have have a multiple update path. It needs to re-use some of the older updates. example: I have 10 versions, I make version 11, wybuild throws away all the old update builds and makes a completely new set (1-11, 2-11, 3-11....etc up to 10-11). This takes hours for me (and no doubt others with large projects.) It needs to reaach a point where I can say "keep all the old updates up to 10, and start from 10 for now on". So wyupdate will use update 1-10 to update the app to v10, then do a second update 10-11 to update to v11.

We're adding that with wyBuild 2.7 -- that is, the ability to do incremental patches (A->B, B->C) instead of just "direct patches" (A->C, B->C) like wyBuild does now.

1 - The option in wybuild to make a new update that just says "Hey, just change this file, leave everything else the same". This would cut down on build-time, disk space, and me juggling files all the time.

We were thinking about putting a serious re-think of of wyBuild lets you handle you original files in wyBuild 2.7.x (that is a point release a couple months after the initial 2.7 release). However, if this is critical for you we can push it up to 2.7.0 (but we'll have to drop something else for 2.7.x or the release date will get pushed back).

Do you want us to switch things around for you?

Thats great news, I'm glad to hear you guys already have the ideas.

That really would be awesome if you could up the priority of that. I doubt its just me, the main exe is always going to be the most frequently updated file so it would hopefully be helpful for everyone. It would give us the ability to quickly throw out quick updates and emergency bugfixes without hassle.

Pretty old thread now but the topic is still hot.When will that promising version 2.7 available. I also got a GB application that really needs incremental updates 😲

It's coming. It got delayed for a number of reasons that we've gone into in other threads.

Reply
Discard post