Closed martinvw closed 4 years ago
AFAIK further updates are provided by KAR files and not new distros.
So that makes sense because the core will not be updated and can use the newest addons :-)
Any chance to get more information related to this? I am running the latest stable 2.5.1 docker image and I can't use the latest 2.5.2-snapshot addons with this image, while they can be downloaded from the Jenkins repository. It seems to me a 2.5.x-snapshot build should be available.
No, releases will only use released versions of add-ons, no snapshots.
So, how do we test the 2.5.2-snapshot add-ons? My point was to have 2.5.x-snapshot docker image available. Not to use 2.5.2-snapshot add-ons with 2.5.1 release.
I do believe we might be able to provide an 2.5.x-SNAPSHOT build which contains the stable core and has the proper reference to the snapshot repo such as we discussed @ FOSDEM.
@kaikreuzer would you be okay with such a solution?
You mean a distro build? No, I don't think it makes sense to do snapshot builds, while never intending to do a release build of it. Why not simply edit the repo url manually, when people want to test snapshot add-ons?
No I mean a docker build. Thus the stable distro with the changed repo url wrapped as a docker image.
Either this or expose an environment variable that would be used by the update script to update the add-ons locations to use the latest 2.5 snapshot add-ons KAR files.
No I mean a docker build.
Then don't ask me, but decide together with the @openhab/docker-maintainers :-)
I would prefer to keep it simple and add an image using the 2.5.2-SNAPSHOT distro (even though it may never be released).
Rationale:
@wborn just a thought, if 2.5.2-SNAPSHOT docker image is added, should it be considered as the default snapshot image over 3.0.0-SNAPSHOT until the latter is usable?
I think it's quite subjective to determine when 3.0.0-SNAPSHOT is usable. It may never be usable for OH1 add-on users.
It may never be usable for OH1 add-on users.
That's actually a fact 😄 My comment was more oriented on some of the major functionalities, such as persistence, that still need to be ported over. Preventing most users from running 3.0.0-SNAPSHOT right now. Anyway, this was just a thought.
using the 2.5.2-SNAPSHOT distro
Ah, I only noticed now that this is still built - I was actually believing that the build only produces the add-ons artifacts now as that was the plan. But maybe it is easier to keep the distro after all, even if it means that the 2.5.2 release will be identical to 2.5.1. But it probably cause less confusion, if the download page shows the distro of the same latest version as we ship the add-ons.
@wborn Thanks for merging the change. I noticed the 2.5.2-snapshot-alpine
tag is not available while all the associated 2.5.2-SNAPSHOT tags are.
$ docker pull openhab/openhab:2.5.2-snapshot-alpine
Error response from daemon: manifest for openhab/openhab:2.5.2-snapshot-alpine not found
Thanks for spotting that @jsetton! It seems to have been missing for a while :blush: and should be fixed with https://github.com/openhab/openhab-docker/pull/279.
Seems like the alpine images still fail to deploy because the Alpine v3.11 armhf image is missing :disappointed:
See: https://github.com/multiarch/alpine/issues/30
So maybe it's best to downgrade back to v3.10 if that still works.
As far as I can see, only 2.5.2-snapshot-alpine
tag is missing from Docker hub. All the other alpine
tags have been generated in the last update. That's very odd.
Those tags are a couple of weeks old and were generated when Alpine v3.10 was still used.
I've downgraded the version with https://github.com/openhab/openhab-docker/pull/280 and it will now properly fail the build when commands fail. That helps a lot because it also showed that the OH 3.0.0-SNAPSHOT build fails on Alpine because there is no openjdk11 package for armhf (https://github.com/openhab/openhab-docker/issues/281). :-/
I was able to pull the 2.5.2-snapshot-alpine
docker image and is working great. Thanks!
But maybe it is easier to keep the distro after all, even if it means that the 2.5.2 release will be identical to 2.5.1. But it probably cause less confusion, if the download page shows the distro of the same latest version as we ship the add-ons.
@wborn FYI, I am keeping the distro artifact in place with the current 2.5.2 build, so you can also provide docker images for the release version (as you do for the snapshots).
Thanks! I've updated the build for the new stable/snapshot versions with #282.
Hello,
Is there already a 2.5.x snapshot build?
Currently, 3.0.0 is not yet stable enough so it would be great to have a 2.5.x snapshot build.
Thanks!
cc: @wborn :-)