Thanks. I run it locally like this:
mvn clean deploy
Locally mvn can read the pom.yml because it loads the .mvn/extensions.xml
in the project directory first.
It looks like the Jenkins maven functionality just can't do this, judging
by your answer recommending the command line approach.
Is there anything on the horizon to add the functionality? Yaml really
makes the maven pom so much more readable, I'd hate to ditch it and I'm not
going to persuade other team members to change their poms over to yaml if
they can't use the straight-forward Jenkins freestyle or maven job types :(
Regards
Adam
On Thursday, 25 October 2018 00:06:33 UTC+1, Jan Monterrubio wrote:
> How do you run this locally? You should be able to use the same command
> either through the Pipeline DSL in an ‘sh “command”’ block.
>
> pipeline {
>
> agent any
>
> stages {
>
> stage('Example') {
>
> steps {
>
> sh 'mvn clean deploy'
>
> }
>
> }
>
> }
>
> }
>
> On Wed, Oct 24, 2018 at 12:48 Adam Hardy <adam....@cyberspaceroad.com
> <javascript:>> wrote:
>
>> The simple maven job bombs because it's a yam pom and maven needs the
>> io.takari.polyglot:polyglot-yaml extension, defined in the
>> .mvn/extensions.xml in the repo.
>>
>>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/1e7b5704-8dd1-4f11-89f9-a84ea808ebe0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
