Strange issue during "Grails War" command

[craigburke]

Strange issue during "Grails War" command

[craigburke]

Hmmm that is strange. What does your Jenkins job look like?

[randyaa]

it executes this shell script:

export PROJECTHOME=/apps/data/www/jenkins/jobs/job-name
mkdir -p ${PROJECTHOME}/workspace/.repository/.grails
mkdir -p ${PROJECTHOME}/lib

Then it uses the Grails Plugin (referencing Grails 2.4.1) to execute the target(s):

clean "war --verbose --stactrace"

[craigburke]

I'm not sure why war works locally for you but not on your Jenkins server. That's very odd.

Looks like your --stacktrace flag is misspelled. Do you get a more meaningful error message after correcting that?

[randyaa]

so... I fixed the typo and rebuilt and got a weird failure with a message of:

"pluginpath\grails-app\conf does not exist!"

I added a Placeholder.groovy to the Plugin's conf directory so it would force the conf directory to exist in the plugin distribution... and now the build works just fine.

Those are the only changes &i have absolutely no idea why those changes impacted the build process as it relates to the Angular-Template-Asset-Pipeline, but i think we're all good now, so sorry to bother you!

[craigburke]

No worries, man, I'm glad you got it resolved.

That does seems strange. I wonder if that's a bug with the Asset Pipeline plugin itself.

[randyaa]

I'm thinking it might be a Grails 2.4.1 issue. i could try bumping to 2.4.3 but at this point i need to make some progress on my real work so i'm going to let it go now that it's working.

[craigburke]

Makes sense. Let me know if you figure anything else out about that.