Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bamboo spec proxy

I'm trying to migrate an existing Bamboo plan (built in the UI) as a Java Spec to a repository.

I've committed the Java exported from the UI to bamboo-specs folder and when I run Scan for Spec I get the following error log. The fact that the Bamboo server is behind a proxy and the failure occurs one minute after the "Downloading" line implies there is an issue getting to the internet. The Bamboo server has proxy settings configured and can see the internet (e.g. the Atlassian Marketplace). Are there other proxy settings required to get this download to work?

09-Jun-2020 10:44:37	[INFO] Error stacktraces are turned on.
09-Jun-2020 10:44:37	[INFO] Scanning for projects...
09-Jun-2020 10:44:37	[INFO] Downloading: https://repo.maven.apache.org/maven2/com/atlassian/bamboo/bamboo-specs-parent/7.0.4/bamboo-specs-parent-7.0.4.pom
09-Jun-2020 10:45:37	Unable to scan repository [snip] for Bamboo Specs
09-Jun-2020 10:45:37	com.atlassian.bamboo.repository.RepositoryException: Unable to scan repository [snip] for Bamboo Specs
09-Jun-2020 10:45:37		at com.atlassian.bamboo.configuration.external.rss.RepositoryStoredSpecsExecutionServiceImpl.lambda$runSpecsWithMaven$0(RepositoryStoredSpecsExecutionServiceImpl.java:194)
09-Jun-2020 10:45:37		at java.util.concurrent.FutureTask.run(FutureTask.java:266)
09-Jun-2020 10:45:37		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
09-Jun-2020 10:45:37		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
09-Jun-2020 10:45:37		at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:48)
09-Jun-2020 10:45:37		at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:26)
09-Jun-2020 10:45:37		at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:17)
09-Jun-2020 10:45:37		at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:41)
09-Jun-2020 10:45:37		at java.lang.Thread.run(Thread.java:748)
09-Jun-2020 10:45:37	Caused by: com.atlassian.utils.process.ProcessTimeoutException: process timed out
09-Jun-2020 10:45:37		at com.atlassian.utils.process.ExternalProcessImpl.wrapUpProcess(ExternalProcessImpl.java:664)
09-Jun-2020 10:45:37		at com.atlassian.utils.process.ExternalProcessImpl.finish(ExternalProcessImpl.java:161)
09-Jun-2020 10:45:37		at com.atlassian.utils.process.ExternalProcessImpl.execute(ExternalProcessImpl.java:114)
09-Jun-2020 10:45:37		at com.atlassian.bamboo.configuration.external.rss.RepositoryStoredSpecsExecutionServiceImpl.lambda$runSpecsWithMaven$0(RepositoryStoredSpecsExecutionServiceImpl.java:181)
09-Jun-2020 10:45:37		... 8 more

 

1 answer

1 accepted

0 votes
Answer accepted

Hi Craig! Yes, you are right, this is a networking error and it is caused by the fact that Maven cannot download libraries from Maven central. What happens when you add a specs repo in UI is:

* Bamboo tests connection to a remote host, clones the repo

* looks for bamboo-specs directory, and pom.xml in particular, to run a Maven build that will publish a plan (or whatever your specs code creates)

* Bamboo will look for tools/apache-maven-$version/bin directory to use mvn executable to run a Maven build and will fall back to mvn if it does not find it (this can happen only if you delete tools/apache-maven directory or there are permissions issues etc)

* This is good old Maven which means it'll will grab config from ${BAMBOO_DIR}/tools/apache-maven-$version/conf/settings.xml  or  ~/.m2/settings.xml (if exists, ~/.m2/settings.xml is preferred over the one in conf)

Solution:

Configure proxy in ${BAMBOO_DIR}/tools/apache-maven-$version/conf/settings.xml (it already has proxies block but commented out). Here's some docs to read and follow: https://maven.apache.org/guides/mini/guide-proxies.html

I have run a few tests with both settings.xml to malform them and build fails as expected, which means Maven does use settings.xml.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 7.2 is here!

I'm happy to announce that Bamboo 7.2 has been released and it’s overflowing with awesome new features. This will be the last major Server release before the launch of Bamboo DC. Bamboo logs We...

514 views 5 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you