git-plugin icon indicating copy to clipboard operation
git-plugin copied to clipboard

Git repository access for Jenkins jobs

Results 141 git-plugin issues
Sort by recently updated
recently updated
newest added

When investigating JENKINS-57772 I have found that contrary to this comment the git plugin does not set the timestamp for annotated tags to the tag date. Currently I can not...

imported-jira-issue
component:git-plugin
priority:major
resolution:unresolved

The pipeline checkout step, in the context of GitSCM, does not pass the Build or Node environment variables down to the launched git process. As an example, if you pass...

imported-jira-issue
component:git-plugin
priority:minor
resolution:unresolved
component:git-client-plugin
component:workflow-scm-step-plugin

I have a multibranch pipeline project that uses LFS. LFS pull is enabled in the project configuration, and LFS objects are fetched from the server, however "git lfs install" is...

imported-jira-issue
component:git-plugin
priority:minor
resolution:unresolved

When specifying tag checkout behaviour explicitly in the git plugin, tags are only checked out if the workspace already exists and contains a git repository. Reproduce by creating a git...

imported-jira-issue
component:git-plugin
priority:major
resolution:unresolved

After we changed the authentication method of our Bitbucket Branch Source Plugin to OAuth2, we discovered that all Build Jobs does not detect the right Revision from the last Build....

imported-jira-issue
component:git-plugin
priority:major
resolution:unresolved

We are observing a issue never encountered before when setting up a new multibranch pipeline and pointing it to git repository and Jenkinsfile within that. Everything looks fine at first,...

imported-jira-issue
component:git-plugin
priority:minor
resolution:unresolved

Hi, I'm experiencing some inconsistent behaviours with the gitlfspull extension and if/how it respects the .lfsconfig include/exclude fetch filters, e.g.: [lfs]   fetchexclude=dir_to_exclude/**/* I'm finding that for normal branches (not filed...

imported-jira-issue
component:git-plugin
priority:major
resolution:unresolved

Using strategy: Default [poll] Last Built Revision: Revision 5a5549ff682d32d98a9ebf0c7e88cea84b5d85f6 (refs/remotes/origin/sprint_29) Selected Git installation does not exist. Using Default The recommended git tool is: NONE using credential 4bf47db3-4a46-4546-8ad0-54f157d0a78c > git --version...

imported-jira-issue
component:git-plugin
priority:major
resolution:unresolved

Steps to reproduce Clone the git plugin's repository, then add the following to pom.xml: org.jenkins-ci.plugins github-branch-source 2.11.3 test Then run GlobalLibraryWithModernJCasCCompatibilityTest. Expected results The test passes Actual results The test...

imported-jira-issue
component:git-plugin
priority:minor
resolution:unresolved
component:github-branch-source-plugin

When force pushing a pull request branch via bitbucket, jenkins keeps building the first commit that the pull request was created with. Bitbucket-push-and-pull-request-plugin on jenkins receives the payload from the...

imported-jira-issue
component:git-plugin
priority:major
resolution:unresolved