Plugin only works when run from Maven

190 views
Skip to first unread message

Anthony DeMartini

unread,
Dec 9, 2014, 1:05:10 PM12/9/14
to jenkin...@googlegroups.com

Hello,

 

We are having a strange issue with our Jenkins plugin.  In the development environment (running using mvn), the plugin works perfectly fine.  But when we install the plugin (using marketplace or hpi file) to seemingly any version of Jenkins, it is totally broken.  Our post-build action (publisher) registers but our configuration form is completely blank.  It only shows the delete button to remove the action.  What could be different about running from maven (hpi:run) vs installing from the marketplace or hpi file?

 

Kind Regards,

 

Anthony

Ryan Campbell

unread,
Dec 9, 2014, 1:34:17 PM12/9/14
to jenkin...@googlegroups.com
What do the logs say? Does the hpi's jar contain the views. I've never seen this.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/DM2PR0801MB0794E5F5E26996B4D07CA8ACEB650%40DM2PR0801MB0794.namprd08.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Anthony DeMartini

unread,
Dec 9, 2014, 1:47:44 PM12/9/14
to jenkin...@googlegroups.com

Ryan,

 

Thanks for the response.  Yes, the HPI file does contain the config.jelly file for the publisher.  The only errors I see in the logs are related to DNS, such as this one:

 

Dec 09, 2014 1:39:57 PM javax.jmdns.impl.DNSIncoming readAnswer

WARNING: There was an OPT answer. Not currently handled. Option code: 65002 data: 2DC591555FDEBD1A

 

Or this one:

 

SEVERE: bad domain name: possible circular name detected. Bad offset: 0xffffffff at 0x1ab

Dec 09, 2014 10:16:47 AM javax.jmdns.impl.constants.DNSRecordType typeForIndex

 

 

I don’t believe these kinds of errors are related, since other plugins work fine.  This is the plugin:

 

https://github.com/jenkinsci/codedx-plugin

 

https://wiki.jenkins-ci.org/display/JENKINS/Code+Dx+Plugin

 

 

Kind Regards,

 

Anthony

Anthony DeMartini

unread,
Dec 10, 2014, 12:41:23 PM12/10/14
to jenkin...@googlegroups.com

I see the render HTTP request going out when adding the post build action but the response doesn’t have any data.  I do see all of the Jelly files in the packaged build, so I’m pretty stumped.

 

Is there some way of turning on an uber-logging mode to show what may be happening?

 

The only messages I see in the logs worth mentioning are the ones complaining about DNS errors shown below, but I still think these are not relevant.

 

Anthony

Anthony DeMartini

unread,
Dec 15, 2014, 10:48:39 AM12/15/14
to jenkin...@googlegroups.com

Just a gentle nudge, has anyone seen anything like this before?

Anthony DeMartini

unread,
Dec 22, 2014, 10:17:59 AM12/22/14
to jenkin...@googlegroups.com

I was able to figure out the issue.  My publisher was called CodeDxPublisher.  And the resources package was org.jenkinsci.plugins.codedx.codedxpublisher.  I had to change the resources package to org.jenkinsci.plugins.codedx.CodeDxPublisher.  The capitalization apparently matters, but not when running from Maven.  Strange!  Hopefully this post will help someone in the future.

 

Thanks,

Daniel Beck

unread,
Dec 22, 2014, 11:17:18 AM12/22/14
to jenkin...@googlegroups.com

On 22.12.2014, at 16:17, Anthony DeMartini <Anthony....@avi.com> wrote:

> but not when running from Maven. Strange!

Case insensitive file system?

Anthony DeMartini

unread,
Dec 22, 2014, 2:32:26 PM12/22/14
to jenkin...@googlegroups.com
I used the same file system in both situations.

-----Original Message-----
From: jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com] On Behalf Of Daniel Beck
Sent: Monday, December 22, 2014 11:17 AM
To: jenkin...@googlegroups.com
Subject: Re: Plugin only works when run from Maven


On 22.12.2014, at 16:17, Anthony DeMartini <Anthony....@avi.com> wrote:

> but not when running from Maven. Strange!

Case insensitive file system?

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/07596FC3-A8A2-4187-B0DB-F81FC886FC4B%40beckweb.net.

James Nord

unread,
Dec 23, 2014, 12:18:01 PM12/23/14
to jenkin...@googlegroups.com, Anthony DeMartini
When run in Jenkins the resources are loaded from the archive not the filesystem.
So windows will load a resource named Bob from the filesytem when it's called boB, but when it's in a jar the case must match exactly.
So as Daniel pointed out I guess your maven build is on a case insensitive filesystem.


On 22 December 2014 19:32:17 GMT+00:00, Anthony DeMartini <Anthony....@avi.com> wrote:
I used the same file system in both situations.

-----Original Message-----
From: jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com] On Behalf Of Daniel Beck
Sent: Monday, December 22, 2014 11:17 AM
To: jenkin...@googlegroups.com
Subject: Re: Plugin only works when run from Maven


On 22.12.2014, at 16:17, Anthony DeMartini <Anthony....@avi.com> wrote:

 but not when running from Maven.  Strange!

Case insensitive file system?

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Reply all
Reply to author
Forward
0 new messages