[JIRA] (JENKINS-47531) git-lfs: allow specifying separate credentials

2019-04-25 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-47531  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-lfs: allow specifying separate credentials   
 

  
 
 
 
 

 
 [~amatera] that pull request has been labeled as "[Later|https://github.com/jenkinsci/git-plugin/milestone/4?closed=1]".  That means that it is one of over 60 pull requests which were not progressing because they were not high enough priority for me and were not receiving significant attention from others.  I labeled those pull requests and closed them so that they would not spend time in the continuous integration servers.  They will be reopened when time allows me to visit them again.My current priorities are:# Resolve [git plugin 4.0 pre-release critical regressions|https://github.com/jenkinsci/git-plugin/milestone/3] and [git client plugin 3.0 pre-release critical regressions|https://github.com/jenkinsci/git-client-plugin/milestone/1]# Test and release git plugin 4.0# Resolve [BuildData bloat|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%221+-+BuildData%22+is%3Aclosed] bug (JENKINS-19022)# Test and release BuildData bloat fix# Improve [notifyCommit handling|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%222+-+notifyCommit%22+is%3Aclosed]# Test and release notifyCommit handling improvements# Improve [submodule handling|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%223+-+Submodules%22+is%3Aclosed]# Test and release submodule handling improvements# Improve [caching for large git repositories|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%224+-+Caching%22+is%3Aclosed]# Test and release git caching improvements# Improve [changelog handling|https://github.com/jenkinsci/git-plugin/pulls?q=label%3A%225+-+Changelog%22+is%3Aclosed]# Test and release changelog handling improvements# Other improvements (like this credentials improvement)If you are available to help and would like to experiment with this proposed change, you could build it yourself, install it in your environment (development or production depending on how much risk you are willing to take), and report the results of that experiment to the [pull request|https://github.com/jenkinsci/git-plugin/pull/546]. If you'd like guidance on how to build that pull request locally, I'm happy to help.  I'd prefer to provide that type of help in either the jenkinsci-dev mailing list or in the jenkins gitter channel, but I'm willing to help you build it yourself for testing and use.  If you test it and use it, that meets your immediate need and helps me by adding more people that are testing the code.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
  

[JIRA] (JENKINS-47531) git-lfs: allow specifying separate credentials

2019-04-25 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-47531  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-lfs: allow specifying separate credentials   
 

  
 
 
 
 

 
 Andrea Matera that pull request has been labeled as "Later". That means that it is one of over 60 pull requests which were not progressing because they were not high enough priority for me and were not receiving significant attention from others. I labeled those pull requests and closed them so that they would not spend time in the continuous integration servers. They will be reopened when time allows me to visit them again. My current priorities are: 
 
Resolve git plugin 4.0 pre-release critical regressions and git client plugin 3.0 pre-release critical regressions 
Test and release git plugin 4.0 
Resolve BuildData bloat bug (JENKINS-19022) 
Test and release BuildData bloat fix 
Improve notifyCommit handling 
Test and release notifyCommit handling improvements 
Improve submodule handling 
Test and release submodule handling improvements 
Improve caching for large git repositories 
Test and release git caching improvements 
Improve changelog handling 
Test and release changelog handling improvements 
Other improvements (like this credentials improvement) 
 If you are available to help and would like to experiment with this proposed change, you could build it yourself, install it in your environment (development or production depending on how much risk you are willing to take), and report the results of that experiment to the pull request.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

   

[JIRA] (JENKINS-47531) git-lfs: allow specifying separate credentials

2019-04-25 Thread andrea.t...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrea Matera commented on  JENKINS-47531  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-lfs: allow specifying separate credentials   
 

  
 
 
 
 

 
 Is possible to have some updates on this feature? Will be a very nice-to-have also for our company because we are using Bitbucket for git repos and JFrog Artifactory for git-lfs artifacs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47531) git-lfs: allow specifying separate credentials

2018-02-28 Thread meph...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 mephi42 commented on  JENKINS-47531  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-lfs: allow specifying separate credentials   
 

  
 
 
 
 

 
 Stephen Connolly, could you please take another look at the pull request? I have some time now to work on improving the pull request in case it's still required.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47531) git-lfs: allow specifying separate credentials

2018-02-23 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-47531  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-lfs: allow specifying separate credentials   
 

  
 
 
 
 

 
 Leon Blakey you could download the pull request build and test it in your environment. If it meets your needs and you note that in the pull request, it helps persuade me that the pull request benefits more than just the original submitter.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47531) git-lfs: allow specifying separate credentials

2018-02-23 Thread lord.quacks...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Leon Blakey commented on  JENKINS-47531  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-lfs: allow specifying separate credentials   
 

  
 
 
 
 

 
 Any progress? We host our own simple git server and LFS server due to size costs. A workaround is to add .git-credentials manually on the build slave, then for piplines replace "LFS after checkout" option with a step that runs "git -c credential.helper=store lfs pull origin". Related: Jenkins will keep trying the same credentials until it times out in 10 minutes. GIT_TRACE=1 shows it's stuck in a loop of seeing Basic auth, setting GIT_ASKPASS, post, 401 error, repeat.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.