[NCBC-13] generating shippable artifacts Created: 12/Jan/12 Updated: 07/Feb/14
|Project:||Couchbase .NET client library|
|Reporter:||Matt Ingenthron||Assignee:||Jeff Morris|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Comment by Jeff Morris [ 29/Oct/13 ]|
Can you provide more detailed expectations regarding what exactly should be delivered for this ticket?
|Comment by Matt Ingenthron [ 04/Dec/13 ]|
(replied via email long ago, just copying the comment here)|
This was meant to mean that we have CI generating shippable artifacts. I still think this should be done, but I'll leave it to your judgement.
I know it's less important with something like .Net versus say C code, but toolchain matters. Meaning, there can be subtle differences based on versions of the software that builds the artifacts we ship. We don't want to accidentally have your product change because a patch was applied, for instance.
We should have a documented, change-controlled toolchain and use it to generate shippable artifacts under CI.