I have been working on a project of migrating Atlassian suites (Confluence/Jira/...) to AWS. This is not a simple lift and shift migration. We actually redesigned everything from ground up. Here is the CICD that I designed. The source codes are stored in on-premise BitBucket, the build tools is AWS Dev Tools (mainly CodeBuild). Development … Continue reading CICD Design for Atlassian Suites in AWS
While setup New Relic Java agent in Jira, I found out that there is an extra option '-Datlassian.org.osgi.framework.bootdelegation.extra=com.newrelic.*' that you need to add into JVM parameters to make New Relic Java Agent to work with Jira. This is due to Jira uses OSGI framework, and the default boot class loader does not load the extra … Continue reading Use New Relic Java Agent with Jira
Have you seen this error in your Jira log? If so, then you are in the right place to solve it 🙂 2019-10-10 02:03:34,970 Caesium-1-4 ERROR ServiceRunner [c.a.j.p.devstatus.provider.DefaultDevSummaryPollService] Refresh failurecom.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider refresh failed with error code 400 and message - HTTP status 400 ] at com.atlassian.jira.plugin.devstatus.provider.DefaultCachingProviderHelper.refreshProvider(DefaultCachingProviderHelper.java:79) at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.handlePollingSuccess(DefaultDevSummaryPollService.java:69) at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.lambda$performPull$1(DefaultDevSummaryPollService.java:51) at com.atlassian.jira.plugin.devstatus.provider.source.applink.PollResult$PollResultSuccess.fold(PollResult.java:51) at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.performPull(DefaultDevSummaryPollService.java:47) … Continue reading Refresh failure com.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider refresh failed with error code 400 and message – HTTP status 400
When building Confluence Data Center on AWS, I was wondering how Confluence Data Centre manages the index file. As we run Confluence cluster in auto-scaling group, the Confluence nodes come and go (not that frequent though, as Confluence is not good at dynamic scaling. It is more schedule based scaling). The newly launched instance gets … Continue reading How Confluence Data Center Manage the Index File?
Stateful Set in Kubernetes is specifically designed for stateful application, and it works well with Confluence Data Center. This is how I designed to run Confluence Data Center on Kubernetes (AWS EKS). And here is a quick demo of scaling up and down.
I have been working on the Confluence space archiving project recently. Here is my design which is already in production. And it works like a charm 🙂 I will explain a bit deeper into the two major automations: Confluence Online Archiving Automation The Online archiving does 3 things: Set the space status to Archive. This … Continue reading Confluence Auto Archive Solution
If your synchrony cluster failed to start in AWS, the Collaborative Edit in Confluence will not work. And if your environment meet all the following criteria. Then I think you are in the right place. As I had the same issue, and finally figured it out that Synchrony has seperate JVM settings. The proxy settings … Continue reading Synchrony cluster failed to start with outbound proxy in AWS