The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why does Git submodule checkout succeed during the normal build but fail during the Specs Scan on El

Pavankumar
Contributor
December 3, 2025

We are using Bamboo Elastic Agents to run our build plans.

When running the plan normally, source code checkout succeeds and Git submodules clone correctly.
This only works if we enable:

  • Use submodules (Repository → Advanced options)
  • SSH key applies to submodules

With these options enabled, the build runs successfully and submodules are cloned from our Bitbucket repository

Problem: Specs Scan Fails on Elastic Agents

When Bamboo runs a Specs Scan, the exact same repository configuration fails.
The error indicates that submodules cannot be cloned during the Specs Scan stage.

What we also noticed:

  • Changes to the Specs files do not trigger a Specs Scan automatically
  • We have to run the scan manually, which disrupts the workflow
  • Regular plan builds work, but Specs Scans fail specifically on Elastic Agents

0 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

TAGS
AUG Leaders

Atlassian Community Events