This is more of a feature request. We are extensively using https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin to promote certain builds. One of the promotions we would like to implement is to promote a git branch or tag for release. However, the git parameter does not work with promotions. Is there any chance we could have the plugin updated so that we can put the git repository config and credentials in the parameter config?

          [JENKINS-40482] Support promoted-builds plugin

          Hi emoshaya_cognitoiq
          I look at this in next week and I'll tell what I can do with that.

          Regards
          Boguslaw

          Boguslaw Klimas added a comment - Hi emoshaya_cognitoiq I look at this in next week and I'll tell what I can do with that. Regards Boguslaw

          Hi klimas7 have you had a chance yet to look at this feature request?

          Thanks

          Ebs

          Ebrahim Moshaya added a comment - Hi klimas7 have you had a chance yet to look at this feature request? Thanks Ebs

          Hi klimas7 sorry to bug you again, but have you had a chance to look at the above feature request?

           

          Thanks

          Ebrahim Moshaya added a comment - Hi klimas7 sorry to bug you again, but have you had a chance to look at the above feature request?   Thanks

          Hi klimas7 sorry to bug you again, but have you had a chance to look at the above feature request?

           

          Thanks

          Ebrahim Moshaya added a comment - Hi klimas7 sorry to bug you again, but have you had a chance to look at the above feature request?   Thanks

          Hi emoshaya_cognitoiq

          I looked at this, but i don't understand, how git-parameter plugin  would have supported 'Promoted Builds', I can support only those things which have definited url to git repository (directly or indirectly) . Could you describe something more 

          Boguslaw Klimas added a comment - Hi emoshaya_cognitoiq I looked at this, but i don't understand, how git-parameter plugin  would have supported 'Promoted Builds', I can support only those things which have definited url to git repository (directly or indirectly) . Could you describe something more 

          Hi klimas7, Use case for supporting the promoted build plugin would be to promote git tags for several repositories for production deployments.

          For example:

          • I have 5 repositories with Git Tags. I would have have one promotion with 5 x Git Parameters, one for each repository which I would then be able to list out all the tags for each repository and promote them for release to production.

          Is there any chance we can get the list of tags/branches from the "Use repository" field? The ssh keys are installed on the Jenkins machines but still the promotion shows blank when it lists out the tags/branches. If it really needs to fetch the credentials from the SCM configuration, could you not change it so that we can also override that and provide credentials through the git parameter itself?

           

           

          Ebrahim Moshaya added a comment - Hi klimas7 , Use case for supporting the promoted build plugin would be to promote git tags for several repositories for production deployments. For example: I have 5 repositories with Git Tags. I would have have one promotion with 5 x Git Parameters, one for each repository which I would then be able to list out all the tags for each repository and promote them for release to production. Is there any chance we can get the list of tags/branches from the "Use repository" field? The ssh keys are installed on the Jenkins machines but still the promotion shows blank when it lists out the tags/branches. If it really needs to fetch the credentials from the SCM configuration, could you not change it so that we can also override that and provide credentials through the git parameter itself?    

          I am considering defining git repository in plugin configuration. This could solve a few more problems.
          I have to think about how to reconcile the current action this field's,  with its new application.

          I will back to this issue in June.

          Regards

          Bogusław

           

           

          Boguslaw Klimas added a comment - I am considering defining git repository in plugin configuration. This could solve a few more problems. I have to think about how to reconcile the current action this field's,  with its new application. I will back to this issue in June. Regards BogusÅ‚aw    

            klimas7 Boguslaw Klimas
            emoshaya_cognitoiq Ebrahim Moshaya
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: