What’s the expected behaviour? Note, I cannot guess how exactly the addons server works, it’s really important that you explain what’s the expected behaviour and how it works.
usually , when one releases a new version from bamboo , the version is released both to Jfrog and addons , at the same time. That s what i would expect .
So, I didn’t implement add-ons and I don’t have any knowledge how it works. The code is in our github and I assume the docs are either in the README or the wiki.
What I know is that when we do a release from bamboo, it will only deploy to jfrog. I don’t know how things go from jfrog to addons. Are you able to find any documentation about it?
We know that some point after the 4th December, the integration between Jfrog and bintray stopped working. There’s nothing obvious on the JFrog screens, nothing in the documentation to let us know how to proceed.
So I raised a ticket with Jfrog asking for help to understand why their product is not doing what I thought it’s supposed to work.
We got just an automated message so far, but I believe support will eventually help. Might be a configuration problem, might be anything, but it’s nothing I know how to solve.
The repository gave us quite some trouble, and it’s currently working as expected.
We didn’t have bintray automatically deployed. Even if I could host both, I would still need to raise a support ticket to understand how the application works.
We wanted to support a distributed ecosystem that allows people in the community to publish their OpenMRS add-ons wherever they want, as GitHub Releases, to Bintray, to Maven, etc. And then addons merely indexes them for easy searching, in one unified index. Hence making it easier for end-users to find relevant add-ons, and making it easier for developers to publish new releases in their preferred workflow.