On Thu, Mar 22, 2018 at 8:19 PM, Oleg Nenashev <[email protected]> wrote:
>> We could introduce a new system property or environment variable pointing
>> to a custom WAR file
>> path for `WarExploder` to use, perhaps.
>
> It would require plugins to update to the recent JTH, but it's not a problem
> since we can always pass Maven property when running builds in CI/PCT.
I think it is fine to say that if you want this to work from your
plugin’s tests, it just needs to have a sufficiently new POM. That is
something we can require for Essentials plugins at least.
>> The actual test runs will go back to the local Maven
>> repository for a `jenkins-war` artifact with the specified version number
>
> It is fine with me, because Custom War Packager installs artifacts to the
> local repo anyway.
> Obviously there are some limitations on groupId and artifactId to make such
> approach running, but it works.
Good enough! Just please use `SNAPSHOT`-labelled versions so cron jobs like
find -L ~/.m2/repository \( -type d -name '*-SNAPSHOT' -prune -o -type
f -name maven-metadata-local.xml \) -exec rm -rf {} \;
can clean up.
--
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/CANfRfr31TuU1%2BqoH2hDZQncfZdq6hAUYQ%3DGkNb8u%3DNUVSowTnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
