Skip to main content
12 events
when toggle format what by license comment
Oct 28, 2013 at 8:56 vote accept JamesStuddart
Oct 28, 2013 at 8:56 comment added JamesStuddart Thanks for the input Joe, I do think the manual field is what I will need to do.
Oct 26, 2013 at 13:08 comment added Joe Strazzere @JamesStuddart - then manual is the way to go. Create a central document that everyone can access containing the "current" build number. Everyone who creates a build increments this number, then uses it. No more "disjointed" build numbers.
Oct 26, 2013 at 2:53 answer added DeonHeyns timeline score: 1
Oct 25, 2013 at 8:07 comment added JamesStuddart Are you not reading my posts? I have said I am unable to setup a build server, this is a business issue not my capabilities lacking here. I have been pushing for a build server but getting new hardware is a PITA here. Thats why I need an intermediate solution for the issue.
Oct 24, 2013 at 18:51 comment added Sam Woods I think Joe is still right. Your other options wouldn't be any better or less expensive than just setting up a build server. It's pretty simple to do these days and there are plenty of free options.
Oct 24, 2013 at 15:46 comment added JamesStuddart Yes I know that is the best way... I said that in the post. But at this moment in time thats not a possible option
Oct 24, 2013 at 15:20 comment added Joe Strazzere A build server is the best way. Manually setting the build number to match some centrally agreed-upon value would work as well.
Oct 24, 2013 at 15:07 comment added JamesStuddart we would need a build server to achieve this to some extent. also when building locally your build number increments independent of other machines?
Oct 24, 2013 at 14:59 comment added Joe Strazzere Is there a reason you don't want to fix the "disjointed build number" problem first, and use more team-wide build number that has real meaning?
Oct 24, 2013 at 14:43 review First posts
Oct 24, 2013 at 17:38
Oct 24, 2013 at 14:25 history asked JamesStuddart CC BY-SA 3.0