[JIRA] [git-client-plugin] (JENKINS-35501) GIT .gitattributes - line feed configuration not work

1 view
Skip to first unread message

m.beumer@thalia.de (JIRA)

unread,
Jun 9, 2016, 10:48:01 AM6/9/16
to jenkinsc...@googlegroups.com
Michael Beumer created an issue
 
Jenkins / Bug JENKINS-35501
GIT .gitattributes - line feed configuration not work
Issue Type: Bug Bug
Assignee: Mark Waite
Components: git-client-plugin, git-plugin
Created: 2016/Jun/09 2:47 PM
Environment: Jenkins 2.7, Git-Client-Plugin 1.19.6, Git plugin 2.4.4
Labels: git
Priority: Minor Minor
Reporter: Michael Beumer

We have the following problem after the jenkins update from Version 1.629 to 2.7.

Now our Build failed because of a JUnit-Test needs some files with the line feeds CRLF instead of LF. In the .gitattributes file of the git repository is this configured. But the git plugin in the jenkins job ignored this configuration. The .DAT files are with the line feed LF in the workspace.

This is the content of the .gitattributes file:

* text=lf

*.DAT text eol=crlf

Why is now the .gitattributes file ignored by checking out the git repository?

Could this be fixed?

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 21, 2016, 10:08:02 AM6/21/16
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
Change By: Mark Waite
Assignee: Mark Waite
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

wearymango (JIRA)

unread,
Aug 25, 2016, 6:22:02 PM8/25/16
to jenkinsc...@googlegroups.com
Gavin Kingsley commented on Bug JENKINS-35501
 
Re: GIT .gitattributes - line feed configuration not work

An observation on priority: if I can't get my source code (in the form I need) I can't build my product. I would have thought this issue was core to the mission of Jenkins.

jglick@cloudbees.com (JIRA)

unread,
Feb 28, 2017, 6:51:02 PM2/28/17
to jenkinsc...@googlegroups.com

Are you using JGit or command-line Git? Prefer the latter in all cases.

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 28, 2017, 10:38:01 PM2/28/17
to jenkinsc...@googlegroups.com

I've attempted to duplicate the problem and don't seem to see the issue. Can you provide more details to show the problem, preferably with a public repository?

The steps I took to try to duplicate the problem included:

  1. Clone, build, and run the docker instance
      $ git lfs clone https://github.com/MarkEWaite/docker-lfs JENKINS-35501
      $ cd JENKINS-35501
      $ git lfs fetch origin origin/lts-with-plugins
      $ git checkout -b lts-with-plugins -t origin/lts-with-plugins
      $ docker build -t jenkins:JENKINS-35501 .
      $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-35501
    
  2. Connect a web browser to that docker instance (http://localhost:8080)
  3. Open the "Bugs - Pipeline Checks"
  4. Open the "jenkins-bugs" multi-branch pipeline job
  5. Click the "Scan Multibranch Pipeline" link and then the "Run Now" link to start branch indexing
  6. Review the JENKINS-35501 job results, confirm file contents remain as expected on Windows and Linux
  7. Open the "Bugs - Individual Checks" folder
  8. Open the "JENKINS-35501-*" job, and run it
  9. Confirm that file contents remain as expected on the execution platform

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 28, 2017, 10:43:02 PM2/28/17
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-35501
I've attempted to duplicate the problem and don't seem to see the issue.  Can you provide more details to show the problem, preferably with a public repository?

The steps I took to try to duplicate the problem included:

# Clone, build, and run the docker instance
{code}

  $ git lfs clone https://github.com/MarkEWaite/docker-lfs JENKINS-35501
  $ cd JENKINS-35501
  $ git lfs fetch origin origin/lts-with-plugins
  $ git checkout -b lts-with-plugins -t origin/lts-with-plugins
  $ docker build -t jenkins:JENKINS-35501 .
  $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-35501
{code}
# Connect a web browser to that docker instance (http://localhost:8080)
# Open the "Bugs - Pipeline Checks"
# Open the "jenkins-bugs" multi-branch pipeline job
# Click the "Scan Multibranch Pipeline" link and then the "Run Now" link to start branch indexing
# Review the JENKINS-35501 job results, confirm file contents remain as expected on Windows and Linux
# Open the "Bugs - Individual Checks" folder
# Open the "JENKINS-35501-*" job, and run it
# Confirm that file contents remain as expected on the execution platform

The [JENKINS-35501 branch|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-35501] includes the history of my attempts to duplicate the bug, including some brief notes on puzzling behaviors that I saw on some tests when setting the text attribute.

mark.earl.waite@gmail.com (JIRA)

unread,
Oct 22, 2019, 9:33:05 PM10/22/19
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Cannot Reproduce
 
Change By: Mark Waite
Status: Resolved Closed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages