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.
Hello,
I'm working as a consultant on a project using Bitbucket and Bamboo (both installed on Windows). Neither did I install the tools, nor do I have direct access to the installation, but I can make requests for config changes. Here's the problem:
I need to build an artifact which is supposed to be used on a Linux machine. While I can properly checkout text files using Git Extensions (with core.autocrlf=input) on my local(!) Windows machine and verify that in the repo the files have Unix-style line endings (LF), the artifact produced by my Bamboo build plan (using "Source Code Checkout" task) contains Windows-style endings (CRLF), which breaks my deployment process on the Linux box.
How can I influence the behaviour of the "Source Code Checkout" task in my build plan to enforce Unix-style line endings (like setting core.autocrlf to input or false)?
Create .gitattributes file in the repository with the following content:
* text
eol=lf
Thank you so much! So far I only considered only git config, but your solution is just perfect for my case, appreciate it!
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.