Core updater vs thirtybees updater

[cprats]

Just for clarification:

Which is the difference between the newly released module Core updater and the thirtybees updater? One is in substitution of the other? Should we run both of them, or should we only use core updater from now on?

I've installed it and I've used it. I like it. I've updated files in the same latest TB version and it did some minor changes.

Should we uninstall thirtybees updater, or it will keep some functions not found in core updater?

[AndyC]

good question , never thought of that , but I realise where the files go though

[Traumflug]

Currently one can use both. After an update with the old updater, the new one would see everything is fine already and do (almost) nothing. Using the new updater first, the old one would refuse to do anything and just report 'your installation is up to date'.

That said, forthcoming thirty bees releases are planned to get provided by the new updater, only. Less work for thirty bees developers, more reliability for merchants. I don't think anybody will miss the old one.

[Traumflug]

D'oh. Forgot the question about whether the old updater should get uninstalled.

The answer is No. The old updater is still needed for updating not thirty bees core, but modules. Plan is to move code needed for updating modules back into core, so eventually the module becomes obsolete, but not for the time being.

[cprats]

Thank-you @Traumflug for your explanation.

[the.rampage.rado]

So if we uninstall the old updater we won't see the available updates in Modules page?

[AndyC]

Judging by what's been said ,if you remove you wont see module updates until they finish the core updater

[datakick]

14 minutes ago, the.rampage.rado said:

So if we uninstall the old updater we won't see the available updates in Modules page?

That's correct. It's stupid, isn't it 🙂

[yaniv14]

@TraumflugBut isn't the old updater is the only one that support db upgrades?

let say you want to upgrade from v1.0.2 to current version, you will need to use the old updater?

[datakick]

I believe that new core updater module handles database migration as well: https://github.com/thirtybees/coreupdater/blob/e58130881076265a0bc1a

[yaniv14]

Thank you for clarifying

[colorful-ant]

Thanks for clarifying

Edited February 12, 2019 by colorful-ant

[DaoKakao]

What is the source of updates via core updater?

 

Usually i update TB thru git pull, with the 1.0.x branch chosen.

However, after such updates the core updater module says that my shop still need to update some files.

So, the question is - which version is the most recent?

As i see in the git pero, the 'markus' branch is updatedmore frequent, while the '1.0.x' branch seems to be more 'stable'

2 @Traumflug : could you clarify the differences, please?

[Traumflug]

Uhm. Core Updater is not made to update developer installations, just like tbupdater wasn't.

Branch markus is where I push my current work. Often intentionally broken stuff, to test/improve Travis CI. Workflow goes like this: http://jump-ing.com/traumflugs/github_best_practices#avoid_broken_code_on_the_main_branch

[the.rampage.rado]

@Traumflug would you recommend updating to the latest version with core updater on production site? (of course keeping in mind backups, etc)

[wakabayashi]

I did that. Worked fine for me.

[Traumflug]

If "latest version" means v1.0.8, then yes.

[Pedalman]

On 3/9/2019 at 10:11 PM, Traumflug said:

If "latest version" means v1.0.8, then yes.

And if we opt to update to bleeding edge I noticed that after doing it so once I could not do it again. In other words it seems once you are on the 0.x train file comparisson does not work anymore. At least in my case. I went the normal way from 1.0.7 to 1.0.8 with the Thirtybees updater. Then I used the coreupdater to patch up to bleeding edge (it was git status mid January since I had issues with Warehouse and hoped that they are solved by some commits from Petr). Since then I can not get the latest patches/commits it seems.

[Traumflug]

I see what you mean.

The secret is, what Core Updater provides as 1.0.x is currently static. While the module its self is complete, there's still a background script missing which translates commits from the development repository (the one on Github) to the Core Updater repository automatically and for every commit. The latter holds release files, e.g. also all the files in vendor/.

This script is forthcoming, of course, but not on the TODO list before the 1.1.0 release.