[JCBC-5] automatically deploying to download locations Created: 12/Jan/12 Updated: 03/Jun/13 Resolved: 03/Jun/13 |
|
| Status: | Resolved |
| Project: | Couchbase Java Client |
| Component/s: | infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | .next |
| Security Level: | Public |
| Type: | Task | Priority: | Major |
| Reporter: | Matt Ingenthron | Assignee: | Deepti Dawar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Idea here is that each commit to the master branch should automatically update a maven snapshot repository. This way, approved code is automatically available for use.
If the artifact's git describe matches a release, it should deploy to the production repository. For example 1.0.0 is a release 1.0.0_2_gf36ab47 is 2 changes past the last release The latter should go to a snapshot maven repo, while the former should go the production repository. |
| Comments |
| Comment by Deepti Dawar [ 03/Jun/13 ] |
| Fixed as per http://www.couchbase.com/issues/browse/SDKQE-289 |