>
> On Wed, Jul 10, 2019 at 5:14 PM Ullrich Hafner <
ullrich...@gmail.com> wrote:
>> 1. Checkout from SCM
>> 2a Build
>> 2b Record warnings and blame authors in affected files
>
> Yet there is a `dir` step in there. So are you talking about this?
>
> dir('src') {
> checkout scm
> sh 'mvn install'
> parseWarnings()
> }
>
> In this case the contextual `FilePath` available to the
> `parseWarnings` step will be in the subdirectory—so you do not need to
> do anything special.
>
Ah, thanks for noting that! This is exactly the use case I am trying to solve, sorry for the confusion.
I did not know that the FilePath context element is actually using the dir argument.
> For that matter, even if someone writes
>
> dir('sources') {
> checkout scm
> sh 'mvn install'
> }
> parseWarnings files: 'sources/src/main/java/**.java'
>
> then the filenames you receive will be absolute, and if you want to
> run `git blame` on something you can trivially find the repository
> root simply by searching up the directory tree for a child directory
> named `.git`.
>
> Perhaps I am missing something about what you are really asking.
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3qBhb%2BYcxLNtm-JP_T8rcVvikP-kVwYiknnFJv25jskQ%40mail.gmail.com.
> For more options, visit
https://groups.google.com/d/optout.