-
Notifications
You must be signed in to change notification settings - Fork 56
Conversation
This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So good so far. POM definitely needs more cleanup to make the build green eventually
@@ -483,7 +413,6 @@ | |||
<id>jenkins-1.642.3</id> | |||
<properties> | |||
<jenkins.version>1.642.3</jenkins.version> | |||
<jenkins-test-harness.version>1.642.3</jenkins-test-harness.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not required though should not harm as well
<findbugs-maven-plugin.version>3.0.2</findbugs-maven-plugin.version> | ||
<jvnet-localizer-plugin.version>1.23</jvnet-localizer-plugin.version> | ||
<concurrency>1</concurrency> | ||
<forkCount>1</forkCount> | ||
<java.level>7</java.level> | ||
<slf4j.version>1.7.7</slf4j.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs to be removed for Plugin POM 3.2 IIRC
Thanks for the alert on JENKINS-47736 and JEP 200. Will look into the feasibility of using simple data types or instead utilize |
I have created https://issues.jenkins-ci.org/browse/JENKINS-48940 |
Routine POM cleanups, permitting tests to be run against newer Jenkins versions than the declared baseline.
Attempting to test against jenkinsci/jenkins#3120, since code inspection suggests that the
RemoteScanResult.scan
field will fail to be deserialized from agents in Jenkins 2.102+. Unfortunately you appear to have no functional tests whatsoever which would build on agents; when I triedit did not work, I suppose because you are using Java mocks rather than an actual mock (HTTP?) service, and mocks do not transfer across JVM boundaries.
I also have no idea how to test this plugin manually, and no inclination to try. The regression, if real, could most likely be corrected by creating a
src/main/resources/META-INF/hudson.remoting.ClassFilter
containingor by simply making the Remoting channel transfer only simpler datatypes, such as
String
, rather than relying on serialization of external libraries.@reviewbybees