Problem brief
I develop a simple plugin for our self-hosted Bitbucket Server. In this plugin I have a web-panel, which appeared on each Pull Request in bitbucket.web.repository.banner.
On dev-localhost environment by Atlassian all my changes works and shows correctly. But after packaging my plugin to jar and sending to our admins for installation, something strange happens: the plugin is successfully installed, merge-checks work correctly, logs from the java-code successfully come, but I don't see my web-panel (but on dev-env I always can see it).
Context
atlassian-plugin.xml
<atlassian-plugin key="${atlassian.plugin.key}" name="${project.name}" plugins-version="2">
...
<web-panel key="specific-key-for-web-panel" location="bitbucket.web.repository.banner">
<resource name="view" type="velocity" location="/html/file-name.html"/>
<condition class="path.ConditionFileName" />
</web-panel>
...
</atlassian-plugin>
Questions
What could be the problem?
How can I catch the problem if I do not have direct access to the server? (I have access to atlassian-bitbucket.log file only)
UPD 1 (few plugins on the server)
UPD 2 (for the first time, everything was fine)
Hey @bukshev what web-resource context do you use to load the JS/CSS assets?
With Bitbucket 7.0 we introduced a new context name on the pull request page:
bitbucket.page.pullRequest.detail
https://developer.atlassian.com/server/bitbucket/reference/web-resource-contexts/
Let me know if that helps.
Thanks,
Maciej
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.