I followed the documentation examples for bamboo specs.
When I create a linked repository manually or via build/specs, and I press "scan", the text is not updated and says
"This repository was never scanned." after a brief busy.
Furthermore, the site displays:
"No specs logs yet
Bamboo hasn't detected any specs in your repository"
The bamboo logs also don't show anything at all related to specs or repository updates.
Bamboo 6.6.2 build 60606
What could be wrong here?
Maybe a little late as a reply (although I see people were still struggling with this as late as October!) but in trying to get Bamboo Specs working I came across this thread and shortly afterwards worked out what (for me) turned out to be the issue and the answer.
In the log files, there's something like this :
2019-12-27 12:21:52,765 INFO [15-BAM::SpecsDetection:pool-22-thread-1] [RssDetectionRunnable] Exception while executing RSS detection for repository 2654209
java.lang.UnsupportedOperationException: JGit implementation does not support this operation, please use native Git
Now I already had a native git installed but just needed to ensure this was available as a 'Server Capability':
Administration -> Overview -> Server capabilities -> 'Add Capability' -> Select Git & correct path, etc ...
Once this 'capability' was available, the scanning of the linked repo containing the specs worked fine.
Hope that helps anyone else in the same situation.
Can you please tell if bamboo-specs folder is in the root of your repository?
Are you able to update plan configuration from local environment with command
More details in this tutorial https://confluence.atlassian.com/bamboo/tutorial-create-a-simple-plan-with-bamboo-java-specs-894743911.html
I have the same problem.
I've configured Bamboo Server with the Bitbucket Cloud Repo and set up the webhook.
When clicked "Test connection", it says "Connection successful".
In the repository "tutorial" I've a folder "bamboo-specs". Inside there is a file "bamboo.yml".
name: Launch Ship
- First Build Stage:
- Build Ship Server
Build Ship Server:
- echo 'Hello world!'
I've added to my project "TutorialRepo" (Kye: "ROCKET") in the Bamboo Specs repositories the repository "tutorial" and enabled the "Scan for Bamboo Specs" and scanned by hand.
It never gave any error, and always says:
"This repository was never scanned.
No specs logs yet
Bamboo hasn't detected any specs in your repository."
I'm using Bamboo 6.9.0.
I've double checked and consulted online about this and still nothing...
I'm having the same problem (as before), and no matter what I try, it doensn't work. I can publish the java specs manually with maven, but for some reason Bamboo server doesn't seem to pick it up automatically.
The annoying thing is, that it gives no indication visually or in the logs of what's wrong, so it can be fixed.
This is the layout:
It was all generated from the tutorial with Maven and archtetype.
@Hendrik Beijeman can you please enable DEBUG log level for class com.atlassian.bamboo.configuration.external.RepositoryStoredSpecsServiceImpl. You can do it without Bamboo restart at BAMBOO_URL/admin/configLog4j.action.
Then click Scan button for repository.
Share Bamboo logs starting from line
Hello Alexey, Victor,
Thank you very much for your quick response!
We've just tested with the log message to DEBUG, as Alexey instructed. Stragely, nothing (specs-related) appears in the atlassian-bamboo.log file.
I did not restart (I also don't have the permission to).
The result is the same - "allow repository to be scanned" is "on". Status is "repository is never scanned", then when forcing with the scan button - a notification pops up that its scannign the repo. And after that, same status - repository is never scanned.
We jus ttried it with the yaml file(s) as well. Same result, except that the "scan duration" is almost immediately while with java specs it takes a few seconds.
We're running Atlassian Bamboo version 6.8.0 build 60803 - 30 Jan 19 in a hosted, corporate environment, no cloud.
One more action. Enable DEBUG log level for class com.atlassian.bamboo.configuration.external.RssDetectionServiceImpl and click Scan button again. Then check logs
Expected log messages
2019-04-26 10:59:57,599 DEBUG [http-nio-6990-exec-1] [RssDetectionServiceImpl] Enqueuing Bamboo Specs detection for repository: 5111809
2019-04-26 10:59:57,600 DEBUG [http-nio-6990-exec-1] [AccessLogFilter] END: 204 admin POST http://localhost:6990/bamboo/rest/api/latest/repository/5111809/scanNow 312620kb-2087kb 2ms
2019-04-26 10:59:57,749 DEBUG [15-BAM::SpecsDetection:pool-22-thread-1] [RssDetectionServiceImpl] Skipping Specs detection. Specs revision not detected in repository 'no specs' on branch 'master'.
I don;t see my previous answer, I added some screenshots.
In any case, I added that logline, and it made no difference.
It almost seems as if the entire feature, or support thereof, is missing from the local installation. Is there an option during install to disable this? Can I check somehow for its presence?
Correct. I presume I should see some activity in the logs, when I push to the repo or manually press scan. Yet there is no event/trigger whatsoever.
Here is the complete list:
...roperties: -Dbamboo.bitbucket.cloud.use.workspace.api=true There are patches available for Bamboo versions 6.8.3, 6.9.2, and 6.10.5 on the bug report that add support for the System Property. T...
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