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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Using a private repo with "Fetch whole repository" enable.
It's a java/gradle project that uses this pluging to retrieve repo/branch information
gradle.plugin.com.gorylenko.gradle-git-properties:gradle-git-properties:2.2.2
It throws the following exception
16-Jun-2020 16:12:30 Execution failed for task ':generateGitProperties'.
16-Jun-2020 16:12:30 > org.eclipse.jgit.errors.MissingObjectException: Missing unknown ....2b49aa19472cec0750ba8
It works ok locally on my computer.
The same problem. On Bamboo CI, "com.gorylenko.gradle-git-properties" plugin can retrieve git branch name, but it fails on "git.commit.id", "git.commit.time", etc.. (from Bitbucket repository). Running on a local computer (Mac) all repo info retrieved OK.
The only thing I noticed - that plugin can not retrieve "git.commit.id" (not failed, just no value in results) before I open PR from branch on Bitbucket, but after creating PR all info are available.
As a temporary workaround I use Bamboo environment variables in conjunction with SpringBoot's buildInfo() plugin for Gradle:
springBoot {
buildInfo {
properties {
additional = [
'buildNumber': java.util.Optional.ofNullable(System.getenv("bamboo_buildNumber")).orElse("[not available]"),
'gitCommitId': java.util.Optional.ofNullable(System.getenv("bamboo_planRepository_revision")).orElse("[not available]"),
'gitBranch': java.util.Optional.ofNullable(System.getenv("bamboo_planRepository_branchName")).orElse("[not available]")
]
}
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.