Hi !

Thanks to provide this feature ! I need it for a few monthes

Some concerns I have with the actual version of the plugin :

• It would be great to lower the minimum jenkins version required to use the plugin (at least, going to the latest LTS 1.424). It's nothing than changing the parent pom version in your plugin artefact (and it would allow more people including me to use your plugin)
• When I created a new job using the git parameter, the first time I launched the plugin, list was empty. Is it normal ? How do you retrieve tag lists (do you retrieve remote tags ? or local tags ?)
• I would love to have a new parameter type : "every existing refs" (ie "every tags or branches in the git repo"). Typically, when I want to deploy my app, I want to either deploy a tag or a branch HEAD

Thanks for the work though

Hi,

I can't make this plugin to read new tag from original repository, what I'm getting is list of tags or SHA-1 hashes from previously cloned repository in Jenkis workspace.

This is pretty useless because most often I need to choose most recent tag before cloning that repository to the workspace to be able to process this most recent in build steps.

Could you please tell me how to get list of current tags from the original repository not old workspace clone?

Besides it somehow cashes the results and after adding new tags I need to go to job configuration to switch from tag to revision, make a build, then switch backwards from revision to tag get tag list up to date (I tried that on two different Jenkins instances on different servers)

Hi, 

Has anyone managed to get this working? When I specify a git parameter and build, the page doesn't respond and hangs. 

Thanks

How do you indicate the repository?  I'm seeking to use this as a replacement for the List Subversion Tags parameter as we migrate from SVN to Git.

Thanks,

Dan

.

How does this plugin set the git directory?  Currently I see in the log that it is using D:\Jenkins but that directory doesn't exist and it is not the value of the JENKINS_HOME variable

Thank you,

I think this is the right plugin that I'm looking for but I'm not sure how to configure it correctly to accomplish what I want. I'm trying to configure a Jenkins project to build ONLY if my git commit contains a specific tag named (demo). Could anyone assist me on configure this correctly? Thank you in advanced!

Hi all,

how to set the default value - the most top value from the list?

Has anyone figured out what the 'branch' and 'tag filter' options are working?
I would like to list only all 'release/*' branches, but neither branch nor tag filter doesn't seem to have any effect!?

Its fixed by Boguslaw Klimas and was supposed to release by 04/02/16. Any updates on this ?? when will it be released?

It would be really useful if this plugin will allow us to specify the repository source for getting the branches or releases as these are usually not the ones from the same repository where we keep our build scripts.

How do I have Jenkins checkout the selected revision? I was able to get the branch option working by naming the parameter named Branch, then for the jobs Branches To Build setting, I just referenced the environmental variable Branch.

But I don't see where I can do that for the revision?

Thanks

Can anybody please help me with plugin configuration for multiple repository project?

I have following issue using plugin.

I have an Ansible deployment scenario managed by Jenkins. All Ansible scripts are located in repository https://<some host>/sops.git

Ansible scripts deploy a war to application server. Source code for war file is located in repository https://<some host>/platform.git.

To deploy necessary war file I need to enter GIT revision that is included into war build number.

I'm trying to use Git parameter plugin.

1. I added both repositories into jenkins job SCM list (first repository is https://<some host>/sops.git, second is https://<some host>/platform.git)
2. I added parameter war_revision in the list of build parameters as a GIT parameter with type revision. To specify repository I entered full repository path to "Use repository" field
3. When Im trying to start parameterized build - message "No GIT repository configured in SCM configuration" is shown in parameter value select field
4. If I clean  "Use repository" field parameter field in a start build form is populated with repository https://<some host>/sops.git revisions - and that is not what i need 

What do I need to do to get things done and have my repository https://<some host>/platform.git revisions list in parameter field?

I'm using plugin version 0.8.0 with Jenkins 1.652

KR, Sergey

I've problem to set a Tag Filter.

I need to get last tag of origin/master branch 

On plugin i've insered this value:

--points-at origin/master

The complete git instruction should be:

git tag -l --points-at origin/master

This command on terminal works correctly, but on plugin i don't see nothing

Do you have any Idea?

Note:

git version 2.11.0

Could someone provide me with an example of how to use this plugin within a Jenkinsfile please. 

Me too please, I cannot find any documentation on it anywhere

backgound information:

1. we have two branch with the similar name: origin/master, origin/master-2015
2. We tried to set the default value to origin/master, however, the selection pick up origin/master-2015 instead
3. we are trying to use negative lookahead to filter out the origin/master-2015 branch, but the list is populated with letters and numbers like "A" "B" "C"...
4. The regex that I am using in the filter is ^((?!master-2015).)*$

so, 

1. is the issue addressed in the point 2 a known issue?
2. Does negative lookahead regex works for this plugin?

Issue 2 should be fixed by  JENKINS-50776 - Getting issue details... STATUS .

Hi

 I have noticed that git plugin is checking out old and stale branches but not the latest . I am passing below parameters 

Repository URL:git@github.XXXXXXXX:XXXX/XXXXX.git

Branch Specifier (blank for 'any') ::^(?!origin/master$).*

I am using above configuration, in this case It shoud filter all the tags created in Lab2_Release branch. But it is fetching all tags form other branches as well. So could you plesae suggest whats wrong?

Hi, thanks for this, but please complete the documentation with some clear and concise examples for pipeline users.
You mention Quick Filter up there but just the heading - what's the attribute name?  How about a table listing all the option attribute names and values?

I tried guessing 'quickFilter' but just got an error.  Much digging through code reveals the option name is 'quickFilterEnabled'. 

Is there any way to make this work with scripted pipeline rather than declarative, or any plan to add support for that if currently not possible?

Played with this plugin in Declarative Pipeline job, works nice with one issue - list of tags is not updated based on the current run, but on the previous one. Is there any solution for that?

For those who are using "Pipeline Script" (which is part of Jenkins Pipeline Project), you cannot define your repos in the GUI.

You can, however (just like it is explained above in this documentation), define these repos in your Jenkinsfile (e.g. Pipeline Script).

This is how to do it.  I suggest making a brand new project to build understanding first before implementing to your main pipeline:

1. Create a new Jenkins Project: Pipeline Project
2. Go way to the bottom and select "Pipeline Script"

3. Paste the following contents in (in this example we are fetching the branch name that is passed by the user on Jenkins "Build with Parameters"):

   // Replace these URL to your target projects


   def project1 = "https://github.com/klimas7/exampleA.git" // you can use the scp url here as well. Doesn't matter"


   def project2 = "https://github.com/klimas7/exampleB.git" // you can use the scp url here as well. Doesn't matter"


   


   pipeline {
    agent any
    parameters {

           gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'MY_BRANCH_A', type: 'PT_BRANCH', useRepository: "${project1}"
        gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'MY_BRANCH_B', type: 'PT_BRANCH', useRepository: "${project2}"
    }
    stages {
        stage('Example') {
            steps {
                git branch: "${params.MY_BRANCH_A}", url: "${project1}"
                git branch: "${params.MY_BRANCH_B}", url: "${project2}"
            }
        }
    }
}

   Please do NOT remove the "origin" or the "defaultValue" or anything from this sample!  We need a default branch to run successfuly at least once in order for this to work!

4. Click "Save"
5. On the outside (inside that Pipeline Project), click the "Build" button.
6. Once the project builds successfully, refresh the page.  The "Build" button should now be "Build with Parameters"

7. You should now be able to see the branches
   
   Question: I changed the URL inside the Jenkinsfile... but now the dropdown boxes aren't showing me the correct values.  What is going on?
   Answer: If you plan to update the URL, you must go inside the "Configuration" of the project, then uncheck the "This project is parameterized" (or whatever it says) checkbox.
   Once you uncheck it,  click the "save" button.
   The "Build with Parameters" button should now reset to "Build".  Click the "Build" button to update the parameters dropdown boxes values
   
   Question: Do we have to rebuild each time in order to keep the dropdown boxes up-to-date with our latest branches?
   Answer: No, you do not.  It will automatically be up-to-date... even if you haven't ran the build in weeks
   
   Question: What about credentials?  How do I handle credentials for my Jenkinsfile to login to my Git Server?
   Answer: You will have to get the credentialsId and append that to your code

   ...

   stages {
        stage('Example') {
            steps {
                git branch: "${params.MY_BRANCH_A}", url: "${project1}" credentialsId: '12345-1234-4696-af25-123455'

   ...

   In order to get the credentialsId:

   1. Click on your jenkins project (that you wish to get the credentialsId for)
   2. On the left-panel, click "Pipeline Syntax"

   3. Select the type of repo you are handling... then click "Generate" button

Providing steps here for those who are struggling like I did all day.  Good luck.

Suggestion:

Is it possible to connect this plugin with the "Choice Parameter"? 

So if I choose a branch-name of the choice parameter, this plugin will load the git-app from the "Choice Parameter", refreshing itself?

Would be awesome.  This would be used for those who are looking for a "One-Jenkinsfile-pipeline" that allows the acceptance-tester to switch off the head at any time.

Just a suggestion!