UL/ulapp
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: default releases to Jenkins build number

Browse Source
This commit is contained in:
Brent Perteet
2026-08-24 20:24:36 -05:00
parent 0e95da26b4
commit 3ecb8e9965
2 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Jenkinsfile.release
View File

@@ -4,8 +4,8 @@ pipeline {
parameters { parameters {
string( string(
name: 'IOS_BUILD_NUMBER', name: 'IOS_BUILD_NUMBER',
defaultValue: '2', defaultValue: '',
description: 'Positive, monotonically increasing App Store build number.' description: 'Optional App Store build number override. Blank uses the Jenkins build number.'
) )
} }
@@ -41,7 +41,7 @@ pipeline {
stage('Signed iOS IPA') { stage('Signed iOS IPA') {
steps { steps {
sh './scripts/ci/build-ios-signed.sh "$IOS_BUILD_NUMBER"' sh './scripts/ci/build-ios-signed.sh "${IOS_BUILD_NUMBER:-$BUILD_NUMBER}"'
} }
} }
} }

9
doc/iOS_TestFlight.md
View File

@@ -45,10 +45,11 @@ the installed `UM Trace App Store` profile, and prints the generated `.ipa` path
## Create a signed IPA in Jenkins ## Create a signed IPA in Jenkins
The manually run `um-trace-ios-release` pipeline uses `Jenkinsfile.release`. Supply an The manually run `um-trace-ios-release` pipeline uses `Jenkinsfile.release`. By default it uses the
`IOS_BUILD_NUMBER` that is higher than every build previously uploaded to App Store Connect. The monotonically increasing Jenkins build number as the App Store build number. Set
pipeline runs the tests, signs with the distribution identity and `UM Trace App Store` profile, `IOS_BUILD_NUMBER` only when an explicit higher override is required. The pipeline runs the tests,
verifies the resulting bundle signature and identity, and archives the IPA plus its SHA-256 file. signs with the distribution identity and `UM Trace App Store` profile, verifies the resulting
bundle signature and identity, and archives the IPA plus its SHA-256 file.
This pipeline only creates a signed artifact. It does not upload or submit anything to App Store This pipeline only creates a signed artifact. It does not upload or submit anything to App Store
Connect, so TestFlight release remains a separate, deliberate step. Connect, so TestFlight release remains a separate, deliberate step.