Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47531

git-lfs: allow specifying separate credentials

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      Jenkins ver. 2.73.2
      Git plugin ver. 3.6.0
    • Similar Issues:

      Description

      I have a git repo, which itself is located on ssh:// remote, but whose [lfs] url points to https:// address.

      When I try to check it out, Jenkins job gets stuck at
      using GIT_SSH to set credentials
      > git lfs pull origin
      command. When I run it manually, I see that it is interactively asking for username and password. I don't see any additional settings for "Git LFS pull after checkout" behavior, so I wonder if it would be possible to allow specifying credentials there?

        Attachments

          Issue Links

            Activity

            Hide
            markewaite Mark Waite added a comment - - edited

            Gad Maor instead of the workaround that you're using, you could download and install a plugin build with the proposed change to add support for separate LFS credentials. Report your results on that pull request so that others know what you observed.

            If that solves the problem then you've avoided the workaround and have helped the Jenkins community evaluate the pull request.

            If that doesn't solve the problem, you return to your workaround and have helped the Jenkins community evaluate the pull request.

            You'll need to install the git client plugin beta release from the experimental update center as well, which will also help the Jenkins community.

            Show
            markewaite Mark Waite added a comment - - edited Gad Maor instead of the workaround that you're using, you could download and install a plugin build with the proposed change to add support for separate LFS credentials. Report your results on that pull request so that others know what you observed. If that solves the problem then you've avoided the workaround and have helped the Jenkins community evaluate the pull request. If that doesn't solve the problem, you return to your workaround and have helped the Jenkins community evaluate the pull request. You'll need to install the git client plugin beta release from the experimental update center as well, which will also help the Jenkins community.
            Hide
            afunix Pavel Malyshev added a comment -

            For me the plugin fails to load, since I have an outdated Jenkins version.
            It's a bit hard to update a live server or a plugin on a live server which serves hundreds builds hourly.

            Show
            afunix Pavel Malyshev added a comment - For me the plugin fails to load, since I have an outdated Jenkins version. It's a bit hard to update a live server or a plugin on a live server which serves hundreds builds hourly.
            Hide
            markewaite Mark Waite added a comment -

            Pavel Malyshev the pre-release plugin depends on git client plugin 3.0.0 beta releases. Be sure that you've installed the updated git client plugin before you install the pre-release git plugin.

            Git client plugin 3.0.0 provides a much newer version of JGit and drops the support for Jenkins versions before 2.60.3.

            Git plugin 4.0.0 pre-release (like this case) should run on any Jenkins version 2.60.3 or newer.

            If your Jenkins version is older than 2.60.3, then you won't be able to use this enhancement anyway. It won't be included in a git plugin version before git plugin 4.0.0, and git plugin 4.0.0 will require at least Jenkins 2.60.3.

            Show
            markewaite Mark Waite added a comment - Pavel Malyshev the pre-release plugin depends on git client plugin 3.0.0 beta releases. Be sure that you've installed the updated git client plugin before you install the pre-release git plugin. Git client plugin 3.0.0 provides a much newer version of JGit and drops the support for Jenkins versions before 2.60.3. Git plugin 4.0.0 pre-release (like this case) should run on any Jenkins version 2.60.3 or newer. If your Jenkins version is older than 2.60.3, then you won't be able to use this enhancement anyway. It won't be included in a git plugin version before git plugin 4.0.0, and git plugin 4.0.0 will require at least Jenkins 2.60.3.
            Hide
            amatera Andrea Matera added a comment -

            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.

            Show
            amatera Andrea Matera added a comment - 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 .
            Hide
            markewaite Mark Waite added a comment - - edited

            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:

            1. Resolve git plugin 4.0 pre-release critical regressions and git client plugin 3.0 pre-release critical regressions
            2. Test and release git plugin 4.0
            3. Resolve BuildData bloat bug (JENKINS-19022)
            4. Test and release BuildData bloat fix
            5. Improve notifyCommit handling
            6. Test and release notifyCommit handling improvements
            7. Improve submodule handling
            8. Test and release submodule handling improvements
            9. Improve caching for large git repositories
            10. Test and release git caching improvements
            11. Improve changelog handling
            12. Test and release changelog handling improvements
            13. 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.

            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.

            Show
            markewaite Mark Waite added a comment - - edited 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 . 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.

              People

              • Assignee:
                Unassigned
                Reporter:
                mephi42 mephi42
              • Votes:
                5 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated: