We’ve made some changes to how you install the Atlassian plugin SDK and where it is hosted.
As part of these changes, we have decided that it will no longer be possible to install the SDK via apt-get in Debian & Ubuntu distributions. You can find updated installation instructions here. If you already have the SDK installed in this way, and wish to update you should first uninstall the SDK and then re-install it using the instructions provided.
The URL for accessing the Atlassian Plugin SDK install files will remain as sdkrepo.atlassian.com and you will also still be able to access the release notes and install files via marketplace.atlassian.com.
Thanks for your understanding and patience, please do let us know if you experience any problems accessing the Atlassian Plugin SDK installation files.
Melissa, thanks for the heads up. The installation instructions for Debian/Ubuntu that you linked to still use apt-get, but require manually seeing an Atlassian package repo. So will we still use apt-get to install or some other method?
Thanks for letting me know @dmitry - I’m waiting for the new instructions to be published (apologies - I didn’t realise there was such a delay), for the moment you can also find them on the ecosystem JIRA ticket [ATLASSDK-122] - Ecosystem Jira.
Can you explain why Atlassian chose to make this change? From a naive developer’s point of view, this makes my & my colleagues’ life harder for no apparent gain.
A decision was made that the infrastructure that SDKRepo was hosted on (along with a number of other services) would no longer going to be managed. As the Server Ecosystem Engineering team is small, we had to make a decision to use infrastructure which we had the capacity to support going forward. Unfortunately the service we have chosen doesn’t currently support apt-get installation.
If there’s enough demand, we’ll certainly consider looking into supporting apt-get in the future, however at this time we have made the decision to focus on improving the reliability of AMPS and the SDK themselves, rather than focussing on the infrastructure.
If you’d like to see this functionality in the future, please do feel free to vote on ATLASSDK-126.
