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

Remove the GIT SCM configuration prerequisites

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-parameter-plugin
    • None
    • Jenkins 2.60.3
      Git parameter 0.9.6
      Git client 2.7.1
      Git 3.8.0

      Goal:

      For both pipeline and freestyle job. To have a way to configure a Git parameter with an URL,  and without a Scm configuration. Then as usual, we can select on of the list of branches/tags. All of that without checkout by Git Parameter.

      Essentially, I would like to have a light behavior that only does git ls-remote, but no checkout, and with a Url configuration in the Git Parameter, but not on the Scm configuration.

      Why:

      1. Because in our project, we have multiple repositories to select version. Except for Jenkinsfile checkout, we don't want to checkout other repositories because we do that in the pipeline. This way, we prevent space and time lost.
      2. Also, in the case where we have a scripted pipeline in the Job (so no Jenkinsfile in Git repo), but we also want to list Git branches/tags of some repo. This is not possible because we can't both have a SCM configuration for pipeline AND a scripted job pipeline.

      Workaround:

      Remove Git Parameter from the job, add in the pipeline a input step with a list of  choice, populated with manual "git ls-remove" command.

      Doc to adapt (source here):

       

      Important! 
      There is no need to set up anything special in plugin settings. 
      This plugin will read GIT SCM configuration from your projects.
      This plugin used directly the Git Plugin and Git Client Plugin.

       

       Thank you!

       

          [JENKINS-57225] Remove the GIT SCM configuration prerequisites

          Jose Then added a comment -

          I agree this would be a great improvement. I am currently hitting this need when trying to configure a scripted pipeline with the Kubernetes Plugin. I am trying to get a list of Tags before I clone within one of my pods.

          Jose Then added a comment - I agree this would be a great improvement. I am currently hitting this need when trying to configure a scripted pipeline with the Kubernetes Plugin. I am trying to get a list of Tags before I clone within one of my pods.

          Dennis Witzig added a comment -

          Same for me. Adding a second repo to the SCM configuration just makes things unnecessarily complex and breaks the Lightweight checkout for me, which unfortunately is a must have.

          Dennis Witzig added a comment - Same for me. Adding a second repo to the SCM configuration just makes things unnecessarily complex and breaks the Lightweight checkout for me, which unfortunately is a must have.

            klimas7 Boguslaw Klimas
            antoinetran Antoine Tran
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: