I would like to help populate the marketplace. But it seems there currently is an issue with the OH2 PR build. As a result the items in Artifactory do not update. Most PR builds show the following build error:
23:58:07.502 | [ERROR] Cannot resolve project dependencies:
23:58:07.502 | [ERROR] Software being installed: org.openhab.binding.feed 2.1.0.qualifier
23:58:07.502 | [ERROR] Missing requirement: org.openhab.binding.feed 2.1.0.qualifier requires 'package com.rometools.rome.feed 0.0.0' but it could not be found
23:58:07.502 | [ERROR]
23:58:07.502 | [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
23:58:07.504 | [ERROR] Cannot resolve dependencies of MavenProject: org.openhab.binding:org.openhab.binding.feed:2.1.0-SNAPSHOT @ /scratch/jenkins/workspace/PR-openHAB2-Addons/addons/binding/org.openhab.binding.feed/pom.xml: See log for details -> [Help 1]
@Olymp You can also download the builds directly from Jenkins in case they fail to deploy to Artifactory. E.g. the IoT Marketplace also worked for me after downloading Build #835.
Thank you for the suggestions @Kai! I’ve fixed these things.
I really like the idea of the marketplace! Is there a way that dependencies could be installed automatically in the future? In case of the MySensors binding “openhab-transport-serial” is needed.
Removing and re-creating whenever a fresh development branch starts would be a hassle I guess. A “disable” button on the marketplace would be nice, so I can hide my entry and restart it quickly whenever I start making changes again.
Where would I create enhancement requests for the marketplace? Eclipse bugzilla perhaps?
Yes, the plan is to also support Karaf features/archive packaging in future - this would allow to automatically consider all dependencies. The current jar-only approach was what I was able to implement rather quickly for a start and I wanted to have that in place as quickly as possible. From this, we can also learn what else we might expect from the marketplace.
Using apt on Ubuntu with SNAPSHOT builds and I am not seeing the new IoT Marketplace. Looking at cloudbees it appears builds have been unsuccessful since #826. The logs tend to all have the same pattern:
14:52:16.241 | Uploading archive online-repo-2.1.0-SNAPSHOT.zip
15:30:08.779 | Build timed out (after 60 minutes). Marking the build as aborted.
15:30:08.791 | Build was aborted
Not sure if this helps isolate a problem, but trying to be helpful.
Thanks for all the great work on this project. Cheers.
@Kai Kai, is this valid for new PR only? I see that some old historical PR are not in the l-p-l folder (example: KNX). If so, people concerned should close PR and make new ones…
A good PR builder should really save people time on all sorts of hosting issues. I ran into some hosting issues because my submitted bindings failed to download. The only error that showed was “Error reading bundle content.”
Here is some information that may help other people debugging such issues:
The IoT Marketplace does not host the bundle JARs or JSON files, it only provides links to them. So put these on a reliable host that can handle some traffic.
The Marketplace content is currently loaded from this catalog. So after approval, it should contain the right URLs.
Before submitting a binding you can also check if your binding bundle can be properly downloaded/installed via the console by issuing: bundle:install http://yourhost.org/yourbinding.jar
In the end my hosting issue turned out to be the Cloudflare Browser Integrity Check that disallowed Apache Karaf from downloading files.
PR builds are triggered whenever you push a new commit. If you don’t have anything to push, you can also briefly close and directly re-open an existing PR.
Right, this is what I mentioned here. In the past that was always only a temporary problem; I have no clue why it is failing this time so often in a row…
@wborn - did you find a solution to the build problem? My PR (https://github.com/openhab/openhab2-addons/pull/2009) is having the exact same problem with the Feed binding. I can even reproduce the error on a clean clone of the OpenHAB2 Addons repository (none of my code).