[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-57712 Allow entering search path for git blame Change By: Ulli Hafner Status: In Progress Resolved Resolution: Fixed Released As: 7.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.18008.1571820650195%40Atlassian.JIRA.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57712 Allow entering search path for git blame Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/219 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.10519.1571409540977%40Atlassian.JIRA.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Ulli Hafner started work on JENKINS-57712 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.10515.1571409540814%40Atlassian.JIRA.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Ulli Hafner commented on JENKINS-57712 Re: Allow entering search path for git blame I'm not sure if a better solution for JENKINS-57260 would be to record the Git repositories of a build and use that information later on. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.15424.1563460861494%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57712 Allow entering search path for git blame Change By: Ulli Hafner Component/s: git-forensics-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.15426.1563460861677%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Alexander Ukhanov assigned an issue to Ulli Hafner Jenkins / JENKINS-57712 Allow entering search path for git blame Change By: Alexander Ukhanov Assignee: Alexander Ukhanov Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.13595.1559046660408%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Alexander Ukhanov assigned an issue to Alexander Ukhanov Jenkins / JENKINS-57712 Allow entering search path for git blame Change By: Alexander Ukhanov Assignee: Ulli Hafner Alexander Ukhanov Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.13590.1559046600324%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title
Norbert Lange created an issue
Jenkins / JENKINS-57712
Allow entering search path for git blame
Issue Type:
Improvement
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-05-28 11:26
Environment:
Jenkins 2.164.3-alpine via docker Warnings NG Plugin 5.0.0 Analysis plugin 5.1.0
Priority:
Minor
Reporter:
Norbert Lange
The warnings plugin searches the build directory and parents for a git repository, but this fails for out-of-tree-builds.
out-of-tree build is preferred, having for ex. ${WORKSPACE}/src for sources and ${WORKSPACE}/build for build output.
the build runs in the build directory, hence paths are based on it and the warningsplugin should run from this directory
switching across agents/docker containers could make things even harder (need to stash/unstash).
eg. "checkout agent" checks out from git, stashes sources without the .git database (or might make a shallow clone). "build agent" unstashes sources, starts a docker container for the build and runs the warning plugin afterwards. I dont have a perfect solution, but having a parameter for either adding the path to the git repository on disk would help. even better would be to give the plugin the repository + commit information so it can pull more stuff if needed.
