You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Could someone help me with this error? I'm building an Android project with the default Android pipelines yml on a existing project and I am getting this error. When creating a new project everything seems to work, but this existing project is keep giving me this error.
We got the same error, it was due to a plugin we added.
'com.google.android.libraries.mapsplatform.secrets-gradle-plugin'
We weren't really using it, so removing it fixed the issue for us.
Same here, I was not using the lib yes and removing it solved the problem. However in case someone wants to use the plugin I am not sure how it's done.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To fix the issue with secrets-gradle-plugin, simply add a local.defaults.properties file to your source control with all the keys assigned with safe default values. Configure the created file in your module's gradle file as:
secrets { defaultPropertiesFileName = 'local.defaults.properties' }
Please refer to the documentation for more.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Norbert,
The file is indeed not there (also not in the project that is working though). Doesn't bitbucket add this directory when cloning it itself (so it makes sense it's not there in my local project)?
Cheers,
Bart
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bart,
Thank you for your reply.
Basically how Pipeline works is that it clones the content of your repository in the "/opt/atlassian/pipelines/agent/build" directory.
Can you let me know whether if the "local.properties" file is there in your repository's root directory?
Best Regards,
Norbert
Atlassian Bitbucket Cloud Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Norbert,
Yes the file is there (in both the working project and the not working)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @scrollbart
Please excuse me for the late reply. Unfortunately I'm not really familiar with building Android projects with Pipelines. Can you try to debug this issue locally using Docker as it's mentioned in this documentation?
This way we can verify whether if this is a Bitbucket Pipelines or a build issue.
Also would it be possible for you to try @Vijith Menonsuggestion? Does Vijith's workaround works for you?
Please let me know.
Best Regards,
Norbert
Atlassian Bitbucket Cloud Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @scrollbart
Thank you for contacting Atlassian Community, my name is Norbert and I'm a Bitbucket Cloud Support Engineer, it's nice to meet with you! Welcome to the Atlassian Community!
Based on the error message, the "/opt/atlassian/pipelines/agent/build/local.properties" file can't be found, once you're trying to do the build.
To verify if the file is there or not, can you run the following command and give me the output?
ls -lthra /opt/atlassian/pipelines/agent/build/local.properties
I'm looking forward to hear from you.
Best Regards,
Norbert
Atlassian Bitbucket Cloud Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.