nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Updating Bamboo Specs from repository failed

Jon Freedman_gnzvmr

I have added a Java specs project to an existing repository under the bamboo-specs subdirectory. Once I merged this into master this triggered Bamboo to scan, e.g. I see a line in the Specs status tab on the relevant linked repository, but Specs status is "Error in Bamboo Specs"

I see the following error in atlassian-bamoo.log

2018-11-05 08:23:27,429 INFO [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-5] [BitbucketServerRssStatusUpdater] Sending RSS notification to Stash (repository: ...)
2018-11-05 08:23:31,598 INFO [15-BAM::SpecsDetection:pool-23-thread-1] [RssDetectionRunnable] Exception while executing RSS detection for repository 2359297
java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: Expected authority at index 7: http://
 at com.google.common.base.Throwables.propagate(Throwables.java:160)
 at com.atlassian.bamboo.configuration.external.RepositoryStoredSpecsServiceImpl.generateBambooYamlsFromSpecs(RepositoryStoredSpecsServiceImpl.java:500)

I don't see anything obviously relevant in atlassian-bitbucket.log

Both Bamboo and Bitbucket sit behind an apache reverse proxy providing HTTPS so I suspect this is the root cause of the issue. Please advise on how to configure this correctly.

Accepted answers

All comments

Gerhard Forster

This KB should get you all details needed to secure your connection behind an Apache reverse Proxy: https://confluence.atlassian.com/kb/securing-your-atlassian-applications-with-apache-using-ssl-838284349.html

It's thought to be used for all Atlassian applications, so it's suitable for Bamboo and for Bitbucket.

Hope this helps, Jon.

Cheers, Gerhard

Jon Freedman_gnzvmr

I'm able to access both Bamboo and Bitbucket using the https reverse proxy urls and they are functional as in I can create a plan manually which is triggered from a commit to one of our repos. It's the specs scan specifically which does not work.

Gerhard Forster

Hi Jon,

I found this resolved bug ticket for you: https://jira.atlassian.com/browse/BAM-18796

Sound like what you're facing. I'm not sure what Bamboo version you use. If below 6.3.0, please consider a Bamboo upgrade.

Otherwise your case seems to be a bit more complex and we'd need more details from you for which best is to open a support case. Describe your situation there incl. your environment (Bamboo version, on what OS, inside Docker?, on same box as Bitbucket / other repo, etc.) and preferribly directly attach your Bamboo Support Zip.

Thanks, Gerhard

Jon Freedman_gnzvmr

I created https://getsupport.atlassian.com/servicedesk/customer/portal/35/CA-591584 with a support.zip - FYI the UX on your attachment upload is poor, it's non-obvious that a file has been uploaded, hence you get the support zip 6 times...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

bamboo