[FAAS-5] jenkins build failure due to commons.faas pom Created: 07/Oct/15 Updated: 19/Oct/17 Resolved: 15/Oct/15 |
|
| Status: | Resolved |
| Project: | faas |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Henry Yu | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4428 |
| Description |
|
ERROR LOG: [INFO] Deployment in http://nexus.opendaylight.org/content/repositories/opendaylight.release/ (id=opendaylight-release,uniqueVersion=true) |
| Comments |
| Comment by Thanh Ha (zxiiro) [ 07/Oct/15 ] |
|
The reason for the failure is that the faas project build is trying to push SNAPSHOT artifacts to opendaylight.release repo which only accepts release artifacts. It should be pushing to opendaylight.snapshot repo. Is there some artifacts in the faas build which is accidently set to be non-SNAPSHOT versions? |
| Comment by Thanh Ha (zxiiro) [ 07/Oct/15 ] |
|
Found it. The property <faas.base.version>1.0.0</faas.base.version> in commons.faas is setting another artifact "base" to be a release version of 1.0.0. Either: 1) <faas.base.version> needs to be 1.0.0-SNAPSHOT I would go with option 1) because autorelease version bump script will not be able to update your version otherwise. |
| Comment by Henry Yu [ 07/Oct/15 ] |
|
Thanh: Thanks a lot for the analysis. I will make the change. |