[JIRA] (JENKINS-53754) svn, git plugin have different interfaces, and not good pipeline documentation

[rupert.thurner@credit-suisse.com (JIRA)]

rupert je thurner created an issue

Jenkins / JENKINS-53754 svn, git plugin have different interfaces, and not good pipeline documentation Issue Type: Improvement Assignee: Mark Waite Components: git-plugin, subversion-plugin Created: 2018-09-24 18:57 Priority: Minor Reporter: rupert je thurner the subversion plugin supports multiple roots and sets variables like SVN_REVISION_1. the git-plugin does the same and sets GIT_COMMIT. the suversiom-plugin sets SVN_URL_1, the git plugin sets GIT_URL, or GIT_URL_1 for the first one, depending how many there are.  there is a request JENKINS-34271 to add GIT_COMMIT_n to the git plugin, which was closed with "use pipeline plugin", without referring to more details. it would be great to make this consistent. and document it so it can be found easily. Add Comment

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

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

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-53754 svn, git plugin have different interfaces, and not good pipeline documentation

Change By: Mark Waite Assignee: Mark Waite

Add Comment

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

Mark Waite commented on JENKINS-53754

Re: svn, git plugin have different interfaces, and not good pipeline documentation Refer to the following resources for additional information on the results of a checkout: Jenkins Minute video that describes how to use git environment variables Pipeline SCM Step for checkout How to customize checkout for Multibranch Pipeline

Add Comment

[rupert.thurner@credit-suisse.com (JIRA)]

rupert je thurner assigned an issue to Mark Waite

Jenkins / JENKINS-53754

svn, git plugin have different interfaces, and not good pipeline documentation

Change By: rupert je thurner Assignee: Mark Waite

Add Comment

[rupert.thurner@credit-suisse.com (JIRA)]

rupert je thurner commented on JENKINS-53754

Re: svn, git plugin have different interfaces, and not good pipeline documentation thank you so much for the documentation. there is nothing on how to check out 2 git urls and use the variables?

Add Comment

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

Mark Waite commented on JENKINS-53754

Re: svn, git plugin have different interfaces, and not good pipeline documentation

There is nothing on how to checkout two git URLs and use the variables. If two different Git URL's are being used from within a single Pipeline job then each checkout must be performed in a separate subdirectory with a separate checkout command performed for each repository. The git plugin does not support mixing checkouts from two unrelated repositories in the same working directory.

Add Comment

[rupert.thurner@credit-suisse.com (JIRA)]

rupert je thurner commented on JENKINS-53754

Re: svn, git plugin have different interfaces, and not good pipeline documentation

ah, that is really interesting and seems powerful. i saw : https://stackoverflow.com/questions/37395860/jenkinsfile-with-two-git-repositories   https://stackoverflow.com/questions/40224272/using-a-jenkins-pipeline-to-checkout-multiple-git-repos-into-same-job  https://qa.nuxeo.org/jenkins/pipeline-syntax/globals  https://jenkins.io/doc/pipeline/steps/workflow-scm-step/  i saw that one has "scm", "currentBuild". how would you get the author, and commit-id ? how would you put an example of such a deploy snipped if you have another jenkinsfile which is loaded, containing e.g. deploy scripts?

Add Comment

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

Mark Waite commented on JENKINS-53754

Re: svn, git plugin have different interfaces, and not good pipeline documentation

The Jenkins Minute video shows how to use the GIT_COMMIT environment variable. Other environment variables are available with a similar technique. Scripted Pipeline can use the return value of the checkout step as a map which contains the environment variables for that checkout. Other variables are included in the JENKINS-45489 test case. A simpler example is in the JENKINS-50401 test case. A different example is in the JENKINS-51218 test case.

Add Comment

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

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-53754

svn, git plugin have different interfaces, and not good pipeline documentation

Change By: Mark Waite Assignee: Mark Waite

Add Comment

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

Mark Waite resolved as Won't Fix

Won't attempt to make the git plugin consistent with Subversion plugin because it risks breaking too many existing users.

Jenkins / JENKINS-53754 svn, git plugin have different interfaces, and not good pipeline documentation

Change By: Mark Waite Status: Open Resolved Resolution: Won't Fix

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

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

Mark Waite closed an issue as Won't Fix

Jenkins / JENKINS-53754 svn, git plugin have different interfaces, and not good pipeline documentation

Change By: Mark Waite Status: Resolved Closed

Add Comment