>> Is there a public API to obtain the actual subfolder of the Git repositories >> of a pipeline?
> Anyway how would that even work if the > checkout is done, say, in a Kubernetes pod which is then discarded? > You would have to implement `SCMListener.onCheckout` and do your > analysis the moment the checkout happens, while the remote filesystem > is still live. Well, 99% of the use cases in my plugin are quite similar to the following pseudo code 1. Checkout from SCM 2a Build 2b Record warnings and blame authors in affected files 3. Discard node So in 2b I still have access to the workspace and the SCM, or am I missing something? (If someone uses the recordIssues step after 3 it will not work.) I cannot do the Git analysis before 2b because I do not yet know the files with warnings. So is it ok to listen for SCMListener.onCheckout events and create actions in the run that store the Git workspace path? It seems to be a little bit overkill for my plugin, but it is feasible. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B3E97658-3B4B-4EA9-9CBA-F6843623917B%40gmail.com. For more options, visit https://groups.google.com/d/optout.
