[HAP-316] NPE in BuildUniqueIdentifierHelper when building downstream job Created: 28/May/12  Updated: 31/May/12  Resolved: 31/May/12

Status: Resolved
Project: Jenkins Artifactory Plug-in
Component/s: Maven2
Affects Version/s: 2.1.0
Fix Version/s: 2.1.1

Type: Bug Priority: Critical
Reporter: Johno Crawford Assignee: Shay Yaakov (Inactive)
Resolution: Fixed Votes: 0
Labels: artifactory, artifacts, maven2
Environment:

Jenkins ver. 1.465



 Description   

After updating to the latest Artifactory plugin we were met with an NPE on next build.

Deploying artifacts of module: .....
ERROR: null
java.lang.NullPointerException
at org.jfrog.hudson.util.BuildUniqueIdentifierHelper.getUpstreamIdentifier(BuildUniqueIdentifierHelper.java:106)
at org.jfrog.hudson.maven2.ArtifactsDeployer.deployArtifact(ArtifactsDeployer.java:170)
at org.jfrog.hudson.maven2.ArtifactsDeployer.deploy(ArtifactsDeployer.java:127)
at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:300)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)
at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:994)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632)
at hudson.model.Run.run(Run.java:1459)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Build step 'Deploy artifacts to Artifactory' changed build result to FAILURE



 Comments   
Comment by Johno Crawford [ 28/May/12 ]

Might be related to https://github.com/jenkinsci/artifactory-plugin/commit/840d357458d93109b4cfddc41e287c8d60d4b521 . I will try downgrading to 2.0.9 during our next maintenance window @ 13:30-14:30 EEST.

Comment by Shay Yaakov (Inactive) [ 28/May/12 ]

We will need to look into that, as a workaround please check the
"Enable isolated resolution for downstream builds (requires Artifactory Pro)"
Under the post build actions "Deploy artifacts to Artifactory"

Comment by Johno Crawford [ 29/May/12 ]

Thanks for the fast response. Just letting you know that after the downgrade to 2.0.9 and "Enable isolated resolution for downstream builds (requires Artifactory Pro)" unchecked the job is able to successfully execute the "Deploy artifacts to Artifactory" build step.

Generated at Wed May 22 00:46:52 UTC 2019 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.