Adding the possibility to provide a pattern for the .ipa file name #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Jenkins » xcode-plugin #69 SUCCESS |
|
Sweet, thank you. I did not have the time lately to fix this issue. |
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
kohsuke
added a commit
that referenced
this pull request
Oct 2, 2013
Adding the possibility to provide a pattern for the .ipa file name
|
This feature has broken all my Jobs in Jenkins. When specifying a pattern wasn't supported, the default one was: Is it possible to change the default pattern in the next release to maintain backwards compatibility? Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Further I extracted the marketing and technical version to its own section. Don't worry, the german localization hasn't been pushed. I'll translate the rest and do a separate pull request.
As suggested I used the EnvVars for the ${BASE_NAME}, ${VERSION}, ${SHORT_VERSION} and ${BUILD_DATE} variables.
This extends this #29 pull request.