[RELENG-21] Jenkins Merge jobs does not deploy all builded artefacts Created: 15/Sep/15  Updated: 27/Feb/18  Resolved: 27/Feb/18

Status: Resolved
Project: releng
Component/s: Jenkins Job Builder
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Tony Tkacik Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: Zip Archive netconf-merge-46.zip    
External issue ID: 4312

 Description   

When merging patch: org.opendaylight.netconf:features-restconf:xml:features:1.3.0-SNAPSHOT into netconf project, pretty much each pom.xml file was changed.

Jenkins merge job for this project, just published a few of them to nexus, which resulted in broken pom files for netconf project (referencing not existing artefacts, versions, etc).

If you look into
https://jenkins.opendaylight.org/releng/job/netconf-merge-beryllium/46/

you could see that most of projects we're build but only a slew of them were uploaded to nexus.

 Comments   
Comment by Thanh Ha (zxiiro) [ 15/Sep/15 ]

Attaching log file for historical recording.

Comment by Thanh Ha (zxiiro) [ 15/Sep/15 ]

Attachment netconf-merge-46.zip has been added with description: netconf-merge-46

Comment by Thanh Ha (zxiiro) [ 15/Sep/15 ]

This may have been an intermittent issue since I see now that future netconf-merge jobs successfully deployed all artifacts. So we'll keep this bug on watch if it happens again.

I'm not sure why this would happen but I have seen once in awhile issues with Jenkins' Maven listener which sometimes gets disconnected from the build and loses track of the build. While Maven successfully completes the build Jenkins incorrectly detects which modules were built and reports incorrectly. This is not a JJB Template issue but likely a bug in Jenkins' Maven plugin.

Comment by Tony Tkacik [ 15/Sep/15 ]

Thanks for quick analysis, but honestly do not know better place to keep that bug open for future reference.

Comment by Thanh Ha (zxiiro) [ 15/Sep/15 ]

(In reply to Tony Tkacik from comment #3)
> Thanks for quick analysis, but honestly do not know better place to keep
> that bug open for future reference.

Leaving it here is fine.

Comment by Thanh Ha (zxiiro) [ 27/Feb/18 ]

I believe this is no longer an issue and this is a very old bug.

Generated at Wed Feb 07 20:37:17 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.