Release process and steps

Release process and steps iOS

1. Creating an RC build.

• https://server.jenkins.couchbase.com/job/build-from-manifest-new
• MANIFEST: couchbase-lite-ios/ (.xml) (see list https://github.com/couchbase/manifest/tree/master/couchbase-lite-ios)

FORCE yes

TRIGGER_BLACKDUCK yes

Depending on version (3.0 or 3.1+), the above will launch a series of Jenkins jobs.

• 3.0 (Lithium) https://mobile.jenkins.couchbase.com/job/couchbase-lite-ios-edition-build-old/ Note: it is the same for ObjC and Swift

• 3.1+ (Helium+)

  • Swift - https://mobile.jenkins.couchbase.com/job/couchbase-lite-ios-swift-edition-build/

  • ObjC - https://mobile.jenkins.couchbase.com/job/couchbase-lite-ios-objc-edition-build/

• Make sure that couchbase-lite-ios-testapp is green.

2. Verify XCs for the RC

• Run staging-e2e-test-ios from http://jenkins.mobiledev.couchbase.com

3. Post the RC build link to the release tracking ticket.

• https://latestbuilds.service.couchbase.com/builds/latestbuilds/couchbase-lite-ios/ - grab your specific build (by version first and then by build number). This should be the exact same as the one the Jenkins was run for.

4. QE will have to validate all the platforms RCs before it is going up to build team. In case there is an issue on the QE side, assist them.

5. Build team publishes the binary on S3(Downloads Page), CocoaPods and Carthage.

CocoaPods

• https://mobile.jenkins.couchbase.com/job/lite-ios-cocoapods-publish/
• The build team makes use of the podspecs from ios-ee.

For users to build from source via Cocoapods a PR will be automatically raised by build team to update CE podspecs, after publish - more info here

Carthage

• https://mobile.jenkins.couchbase.com/job/couchbase-lite-ios-carthage-build/
• This is automatically triggered by another job and is running https://github.com/couchbaselabs/couchbase-lite-ios-ee/blob/master/Scripts/generate_carthage_package.sh Engineer should solve/assist if any problems arise.

6. Update Package.swift and README corresponding to release/branch - by PR:

Update url and checksum in Package.swift. You can generate the checksum by running swift package compute-checksum /path/to/.zip. It needs to be done for:

1. Community Edition 4.0+ or Community Edition 3.x - GHA validated.

2. Enterprise Edition - GHA validated.

3. Not always, Vector Search - Validation will be done in next step.

7. Verify the release.

Run this pipeline http://jenkins.mobiledev.couchbase.com/job/validate-ios/ Will validate for each release method iOS has, currently 4. A job for each.

8. Tag and publish Git release.

• Community Edition

• Community SPM 4.0+ or Community SPM 3.x

• Enterprise Edition

• Enterprise SPM

9. Update manifest via Gerrit.

---

TL;DR for Engineer:

1. Create an RC build via https://server.jenkins.couchbase.com/job/build-from-manifest-new
2. Run staging-e2e-test-ios from http://jenkins.mobiledev.couchbase.com for the above build and hand it to QE.
3. Assist Build team if any Jenkins job fails on the publishing side of things.
4. Verify the release via http://jenkins.mobiledev.couchbase.com/job/validate-ios/.
5. Tag the release.
6. Bump up manifest via Gerrit.