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
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.
If I issue:
git log --all --pretty=oneline
on my local machine I get all commits. If I issue the same command in my pipeline I get a truncated list. The specific commit that I'm looking for is from 19 Dec 2019. If I issue:
git log --all --pretty=oneline --before "2020-02-01"
I still get a truncated list but it starts with commits from 1 Feb 2020 so it is shorter. But I don't get the commit I'm looking for. The list ends at the same point even though it is shorter. It is as if the pipeline only goes back so far and the commit i'm looking for is too far in the past.
Obviously, git log is not what I want to do in my pipeline but it is an example of the problem I have. What I actually want to do is a git diff between that 'missing' commit and HEAD.
Just to reiterate these commands all give the expected results when run on my local machine. It is only the pipeline that is truncated. Any ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.