Hi everyone! Jenkins can "dynamically" provide tools and configurations to jobs via config file provider plugin, global tool configuration etc.
When debugging a job however, things get painful because you usually don't have said configurations/tools available in your environment (i.e. when a user logs on to the slave). Is there a way to store configurations that would allow someone to manually re-create the build environment of the Jenkins job? I am thinking of something like a shell script that could be sourced so you would have the proper JDK, Maven version and settings.xml available and you could just type "mvn clean install" to debug your build. Our developers mainly need this to debug E2E test runs. Cheers Steffen -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/5E63738AB9896844AF1601A1D09467737C0131FA%40SMBXKO2.cgm.ag. For more options, visit https://groups.google.com/d/optout.
