[INTPAK-127] Fix intermittent failure to push RPMs to Nexus Created: 15/Jan/18  Updated: 17/Jan/18  Resolved: 15/Jan/18

Status: Closed
Project: integration-packaging
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Daniel Farrell Assignee: Anil Belur
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Since about Jan 11th, packaging build jobs have been intermittently failing to deploy artifacts to Nexus. I don't think this is related to packaging logic.

Look at the recent history of these jobs. All of the red dots are failures due to this.

https://jenkins.opendaylight.org/releng/view/packaging/job/packaging-build-rpm-snap-carbon

https://jenkins.opendaylight.org/releng/view/packaging/job/packaging-build-rpm-snap-nitrogen

Oxygen failures seem more consistent, for some reason (maybe random unlucky)

https://jenkins.opendaylight.org/releng/view/packaging/job/packaging-build-rpm-snap-oxygen



 Comments   
Comment by Daniel Farrell [ 15/Jan/18 ]

It seems to be because there haven't been new artifacts published since the last daily job.
 
That seems a bit odd (no new builds for Carbon for multiple days, no new Oxygen builds since the 11th) but it's not a bug.

Comment by Anil Belur [ 17/Jan/18 ]

dfarrell07 I have enabled "Allow redploy" on the nexus repositories since these are daily staging/snapshot packages getting upload from daily builds only for the `*-devel` repositories and not the release repositories. I think the best practice here could be to verify package exists on nexus before trying to upload in the code.  

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