[JIRA] [git-plugin] (JENKINS-32998) add condition to the GIT clone/pull step

[gil@tikalk.com (JIRA)]

Gil Shinar created an issue

Jenkins / JENKINS-32998 add condition to the GIT clone/pull step Issue Type: New Feature Assignee: Mark Waite Components: git-plugin Created: 17/Feb/16 1:51 PM Priority: Minor Reporter: Gil Shinar The thing is as follows: I use building blocks, Jenkins jobs, that are usually being used by upstream jobs but I want them to be able to run on their own. If I use the Git plugin step in the upstream project, it is no use to run this plugin's procedure again in the downstream job. I would like to be able to pass a Boolean parameter from the upstream job to the downstream job that'll avoid the Git plugin's step, if the parameter evaluates to false. (It can, off course, be a string evaluation or any other comparison parameter or expression). Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[gil@tikalk.com (JIRA)]

Gil Shinar updated an issue

Jenkins / JENKINS-32998 add condition to the GIT clone/pull step

Change By: Gil Shinar

The thing is as follows:

I use building blocks, Jenkins jobs, that are usually being used by upstream jobs but I want them to be able to run on their own  as well .

If I use the Git plugin step in the upstream project, it is no use to run this plugin's procedure again in the downstream job.  I would like to be able to pass a Boolean parameter from the upstream job to the downstream job that'll avoid the Git plugin's step, if the parameter evaluates to false. (It can, off course, be a string evaluation or any other comparison parameter or expression).

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-32998 add condition to the GIT clone/pull step

Change By: Mark Waite Assignee: Mark Waite

Add Comment

[robertosena86@gmail.com (JIRA)]

Roberto Sena commented on JENKINS-32998

Re: add condition to the GIT clone/pull step I too would like to see a condition on the Git checkout. I currently have jobs that don't need to do a checkout every time. I would love to be able to handle that with a passed in parameter that I can check against rather than have separate jobs that check out, build, and deploy. and one job that wraps those to know which to do.

Add Comment

[michael_giroux@choicehotels.com (JIRA)]

michael giroux commented on JENKINS-32998

Re: add condition to the GIT clone/pull step

Perhaps the Git plugin is overkill for this type of job. Have you considered setting SCM to none and using a simple build step to execute a shell script that tests the parameter, and does the checkout as appropriate? [ "$ {parameter} " = "checkout" ] && git checkout ...

Add Comment

[gil@tikalk.com (JIRA)]

Gil Shinar commented on JENKINS-32998

Re: add condition to the GIT clone/pull step

Problem is Git plugin does many things that "protect" you from whatever exists in the workspace at the moment the clone/pull occurs and I want that "protection"

Add Comment

[sebastien.bonami@gmail.com (JIRA)]

Sebastien Bonami commented on JENKINS-32998

Re: add condition to the GIT clone/pull step

Any news on this? I would also like this.

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[andersbergsten@yahoo.se (JIRA)]

Anders Bergsten commented on JENKINS-32998

Re: add condition to the GIT clone/pull step

I'm very interested in such a feature. I have a Jenkins project that starts twelve downstream projects where each clones the same Git repo. That adds time to the build process and wastes disk space. It would be awesome if all twelve downstream projects could make use of the Git repo already cloned by the parent project. The catch here is that it must be possible to build each downstream project separately where it first deletes the workspace and clones the Git repo. I am keeping my fingers crossed this ticket is prioritized.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)