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

Add config option to ignore certificate errors

      This plugin currently has no configuration option to allow it to ignore errors with the certificate being used on Bitbucket. This means that if someone has a self-signed cert, they have to import it into the JVM trust store used by Jenkins before branch indexing will work. Doing this is a bit of a hassle. Most other integrations of this sort have a check box option to allow the user to disable certificate validation.

          [JENKINS-54150] Add config option to ignore certificate errors

          Mark Waite added a comment -

          nfalco asked:

          This is not the first request of this kind that I have received from users. I have read the environment variables that git-plugin makes available and I was wondering if there was a specific reason why the repository name is not among them.
          Currently some users are analyzing the URL used in the git clone to get this value.

          I am not sure that there is a clear meaning for repository name. Can you help me understand the repository name for the following cases:

          git@github.com:MarkEWaite/bin.git
          https://markewaite@bitbucket.org/git-client-plugin.git
          https://git.assembla.com/git-plugin.3.git
          git@git.assembla.com:git-plugin.3.git
          git@bitbucket.org:markewaite/jenkins-pipeline-utils.git
          https://markewaite@bitbucket.org/markewaite/jenkins-pipeline-utils.git
          mwaite@git.markwaite.net:git/bare/jenkins/git-client-plugin.git
          https://gitea.com/Mark-Waite/git-client-plugin.git
          git@gitea.com:Mark-Waite/git-client-plugin.git
          git@gitlab.com:MarkEWaite/bin.git
          https://gitlab.com/MarkEWaite/bin.git
          markwaite@vs-ssh.visualstudio.com:v3/markwaite/elisp/elisp
          https://markwaite.visualstudio.com/DefaultCollection/elisp/_git/elisp
          

          Mark Waite added a comment - nfalco asked: This is not the first request of this kind that I have received from users. I have read the environment variables that git-plugin makes available and I was wondering if there was a specific reason why the repository name is not among them. Currently some users are analyzing the URL used in the git clone to get this value. I am not sure that there is a clear meaning for repository name. Can you help me understand the repository name for the following cases: git@github.com:MarkEWaite/bin.git https: //markewaite@bitbucket.org/git-client-plugin.git https: //git.assembla.com/git-plugin.3.git git@git.assembla.com:git-plugin.3.git git@bitbucket.org:markewaite/jenkins-pipeline-utils.git https: //markewaite@bitbucket.org/markewaite/jenkins-pipeline-utils.git mwaite@git.markwaite.net:git/bare/jenkins/git-client-plugin.git https: //gitea.com/Mark-Waite/git-client-plugin.git git@gitea.com:Mark-Waite/git-client-plugin.git git@gitlab.com:MarkEWaite/bin.git https: //gitlab.com/MarkEWaite/bin.git markwaite@vs-ssh.visualstudio.com:v3/markwaite/elisp/elisp https: //markwaite.visualstudio.com/DefaultCollection/elisp/_git/elisp

            Unassigned Unassigned
            owenmehegan Owen Mehegan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: