Did Atlassian SDK install JIRA automatically? - jira

I followed the steps here: https://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project to install Atlassian SDK for JIRA plugin development.
To my surprise, when I ran "atlas-run", JIRA was launched. I was wondering if SDK installed JIRA during the installation?
The reason why I asked this is that I followed this documentation: https://developer.atlassian.com/docs/getting-started/learn-the-development-platform-by-example/create-a-plugin-skeleton to create a refapp skeleton. But when I tried to launch JIRA, JIRA launched failed withe the following error:
JIRA Startup Failed
The following plugins are required by JIRA, but have not been started:
Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)
JIRA Projects Plugin (com.atlassian.jira.jira-projects-plugin)
Atlassian OAuth Consumer Plugin (com.atlassian.oauth.consumer)
Atlassian Navigation Links Plugin (com.atlassian.plugins.atlassian-nav-links-plugin)
Atlassian JIRA - Plugins - OAuth Service Provider SPI (com.atlassian.jira.oauth.serviceprovider)
Atlassian JIRA - Plugins - Issue Navigation (com.atlassian.jira.jira-issue-nav-plugin)
Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit-plugin)
Atlassian OAuth Admin Plugin (com.atlassian.oauth.admin)
Atlassian REST - Module Types (com.atlassian.plugins.rest.atlassian-rest-module)
Atlassian JIRA - Plugins - Project Config Plugin (com.atlassian.jira.jira-project-config-plugin)
Atlassian JIRA - Plugins - REST Plugin (com.atlassian.jira.rest)
Opensocial Plugin (com.atlassian.gadgets.opensocial)
Applinks Product Plugin (com.atlassian.applinks.applinks-plugin)
Atlassian OAuth Service Provider Plugin (com.atlassian.oauth.serviceprovider)
Atlassian JIRA - Plugins - Look And Feel Logo Upload Plugin (com.atlassian.jira.lookandfeel)
Embedded Gadgets Plugin (com.atlassian.gadgets.embedded)
Gadget Spec Publisher Plugin (com.atlassian.gadgets.publisher)
Atlassian JIRA - Plugins - OAuth Consumer SPI (com.atlassian.jira.oauth.consumer)
RPC JIRA Plugin (com.atlassian.jira.ext.rpc)
Gadget Directory Plugin (com.atlassian.gadgets.directory)
Atlassian JIRA - Plugins - SAL Plugin (com.atlassian.sal.jira)
Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)
I suspect JIRA is locked so I need to delete the .jira.lock file, which I need to figure out what the JIRA_Home directory is

The Atlassian SDK does not "install" JIRA out of the box. If you issue atlas-run from within a plugin project, the SDK will fetch all necessary dependencies for a JIRA instance via Maven and install a development version of JIRA into the target folder of your current plugin.
I'd suggest to create a clean plugin from scratch via atlas-create-jira-pluginas the refapp may be outdated.
https://developer.atlassian.com/docs/developer-tools/working-with-the-sdk/command-reference/atlas-create-jira-plugin

Related

Team Foundation Server plugin is not available in Jenkins

The Team Foundation Server plugin is not available in Jenkins. The Jenkins official page shows the message:
Distribution of this plugin has been suspended due to unresolved security vulnerabilities
Is there any alternative to this plugin using which I can integrate Team Foundation Server with Jenkins?
MS have effectively abandoned support for TFVC and for the plugin.
You can still grab the plugin from the GitHub TFS plugin releases page and upload manually. ({JENKINS_URL}/pluginManager/advanced ). You may have to reconcile any dependencies manually.
MS recommended alternative is the tf command line from a shell step (brutal), which they also silently abandoned support for TFS SDK/CLI.
ps: aside from the vulnerability ( SECURITY-1506 / CVE-2020-2249 ), it does not meet the OSI open source license requirements - INFRA-2751 to be made available via the plugins site.
2021-03-30: It appears the OSI licensing issue has been resolved. This Jenkins Community post suggests a fix to SECURITY-1506 / CVE-2020-2249 is available in a fork but additional security issues ( SECURITY-2283 / CVE-2021-21636, CVE-2021-21637 (permission check), CVE-2021-21638 (CSRF) ) are outstanding, need to be resolved and released, or someone steps up to adopt the plugin.
pss: M$ also announced (23 February, 2021) retirement for Azure plugins for Jenkins, effective February 29, 2024.

Resolving Jira Comments in Jenkins

We are using JIRA 7, and our Jenkins version is 1.647. Our scm is SVN, and we want to resolve labels, and mail it to concerned teams.
Lets say a developer updated svn cmnt with EARN-34, our plugins should resolve as jira.xyz.com, and mail it to concerned team.
I have installed JIRA plugin, and configured the url and password. I have used the pattern '(EARN-[0-9]+)' in JIRA lugin, and JIRA ext plugins. The same thing I have configured in jira ext plugins:url ,and pattern. Is there anything else I need to add.

Modifying Jira Server Add-on for Jira Cloud instances

I have developed Jira Server add-on/plugin for Jira 7 which now needs to be installed into a cloud instance of Jira. However on the marketplace-page of my plugin it says:
This hosting is not available for this add-on.
What do I have to do to make my plugin installable into a cloud instance?
The manner to create an add-on on Jira cloud is totally different from the one with Jira server. In this case, you need to extend and integrate with Atlassian Connect.
In fact, with jira cloud, your add-ons are web applications that are integrated into Jira via iframes. You can find the Atlassian connect documentation here: https://developer.atlassian.com/static/connect/docs/latest/index.html.
The Hello World tutoral is very useful to understand how Atlassian Connect works.
Note that Atlassian connect works for Confluence Cloud too.

How to enable Jira RPC Plugin in Jira trial version

I am trying to integrate Jira with TestLink. Found issue with enabling RPC plugin in JIRA. I am unable to find RPC Jira plugin in System settings. Where can we find RPC jira plugin in the Jira trial version?
JIRA's SOAP and XML-RPC remote APIs were removed in JIRA 7.0 for Server (see the announcement).
In older versions of JIRA the RPC plugin should be active by default.
If you are using an older version, you should be able to find it under Administration -> Add-ons -> Manage add-ons.
Select "System" in the drop down menu to list all add-ons that ship with JIRA.
(Screenshot from JIRA 6.4)

Jira Startup failed with unloaded plugins

I was deploying a Jira report plugin with SDK 3.10 and ran into this:
The following plugins are required by JIRA, but have not been started:
Gadget Directory Plugin (com.atlassian.gadgets.directory)
Atlassian JIRA - Plugins - Project Config Plugin (com.atlassian.jira.jira-project- config-plugin)
Atlassian OAuth Admin Plugin (com.atlassian.oauth.admin)
Embedded Gadgets Plugin (com.atlassian.gadgets.embedded)
Atlassian JIRA - Plugins - Shared Application Access Layer (SAL) Plugin(com.atlassian.sal.jira)
Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)
Atlassian JIRA - Plugins - Look And Feel Logo Upload Plugin (com.atlassian.jira.lookandfeel)
Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)
Atlassian REST - Module Types (com.atlassian.plugins.rest.atlassian-rest-module)
FishEye Plugin (com.atlassian.jirafisheyeplugin)
Gadget Spec Publisher Plugin (com.atlassian.gadgets.publisher)
Atlassian JIRA - Plugins - REST Plugin (com.atlassian.jira.rest)
Atlassian OAuth Service Provider Plugin (com.atlassian.oauth.serviceprovider)
Opensocial Plugin (com.atlassian.gadgets.opensocial)
RemarK: i do not have Jira installed on my laptop. is that a problem? also, I am using Java SE 1.6
I think you have to provide more information, for example pom.xml base pom and dependencies, and maybe some logs. JIRA SDK produces compilation log file, that you could include.
Another thing, you could skip harness test. Try to build plugin with:
mvn clean package -Patlassian -Dmaven.test.skip=true

Resources