search

AliSherKashif / codenameone

Automatically exported from code.google.com/p/codenameone
0 stars 0 forks source link

Add A Build Release Option That will build all targets #38

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
For simplified release updates, ideally it should also increment the version 
number where appropriate.

Original issue reported on code.google.com by shai.almog on 18 Feb 2012 at 2:00

GoogleCodeExporter commented 9 years ago 
And it would be helpful, if it can also take a svn revision number of the 
codenameone source so that the build can be targeted against that particular 
svn version. As once we release an app to public, there may be changes to users 
code and which will require a new release build. However currently since the 
codenameone source is also changing, it is not possible to know if everything 
that was working previously will continue to work. Hence, if we can restrict 
the build to a particular version of codenameone source against which the 
developer has done testing, it would be very helpful and reduce the need to 
have a local build.

Original comment by nir...@nvsoft.com on 17 Oct 2012 at 11:02

GoogleCodeExporter commented 9 years ago 
These will be featured in the 1.0 release and newer only for enterprise/pro 
users.
We won't accept random SVN version numbers since that would be impossible to 
support, however we will allow enterprise/pro users to pick a point release 
version (1.1, 1.0 etc.) against which they wish to build.
We will also allow them concurrent builds and CI which applies to the other 
portions of the issue.

Original comment by shai.almog on 17 Oct 2012 at 1:09