Our complete deployment process is driven by Gitlab CI/CD (before that, we were using Jenkins). Plugins for the Atlassian Marketplace used to be an exception for several years. Annoyed by this situation, we decided to develop a Maven plugin which integrates smoothly into Atlassian’s plugin build process and allows an easy deployment to the Marketplace. However, for us the last submission step (switching the version from “Private” to “Public”) remains manual.
Insert into your pom.xml’s
After integrating into your pom, an additional target
deploy is available:
Supported configuration properties
Username for Atlassian Marketplace.
Token for Atlassian Marketplace (passwords are not supported any more). The token has to be encrypted using
Build number, if not set computed from semantic version.
buildPattern (Default: %1d%03d%03d)
Pattern for computing build number from semantic version.
Default value according to Atlassian versioning proposals.
License type (COMMERCIAL, COMMERCIAL_FREE, BSD, ASL, GPL, LGPL, EPL or ATLASSIAN_CLOSED_SOURCE).
Payment Model (FREE, PAID_VIA_VENDOR or PAID_VIA_ATLASSIAN).
status (Default: PRIVATE)
Status of version after upload (PRIVATE, PUBLIC or SUBMITTED).
This is only for completeness, please always use PRIVATE and submit manually.
supported (Default: true)
Is this version supported?
beta (Default: false)
Is this a beta version?
type (Default: JAR)
Type of artifact (JAR or OBR).