Re: Updating build number for built product only
Re: Updating build number for built product only
- Subject: Re: Updating build number for built product only
- From: Luther Baker <email@hidden>
- Date: Thu, 24 Oct 2013 18:03:14 -0500
You may not be using it this way but a build number often refers to a specific, reproducible build ... which makes it somewhat incumbent to have said number in the source to prove or label subsequent pulls equivalent to the build in question.
If you don't actually commit the build number to source control, it seems like you'd need some other out of band way to map builds to specific commits - which, on the surface, seems more administrative than just committing the build #.
Or, maybe you've got that worked out and I'm just adding noise to the conversation.
On Oct 24, 2013, at 4:42 PM, Rick Mann <email@hidden> wrote:
> There are many solutions online for automatically updating a build number in the Info.plist. The problem is that all the ones I've seen update the Info.plist file itself prior to building, thus modifying the file and making it appear as needing to be checked in to source control.
>
> Is there any way to modify this file within the built product, prior to code signing or packaging, so that the original source file can remain unmodified? Alternatively, is there a way for the Info.plist to refer to some symbol that can be defined in a transient file created by a pre-build script (and set to be ignored by source control)?
>
> --
> Rick
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden