release

How to make Android app automatically configure w/ debug vs. release values?

由 [亡魂溺海] 提交于 2019-12-04 13:22:28
问题 I'm working on an Android app, specifically one that uses the Facebook Android SDK. In development mode, I'm working with a test Facebook app that goes by one ID. However, in release mode, the app will be working with second Facebook app with a different ID. I'm wondering how most Android (or Java might be a suitable enough realm of knowledge) developers here go about having their app automatically build with debug vs. release values. An ideal solution does not involve a manual switch (e.g.:

Erlang Release Best Practices?

由 六眼飞鱼酱① 提交于 2019-12-04 09:41:11
问题 I'm an Erlang noob, and I've been checking out Faxien+Sinan and Rebar, and the basic philosophy of Erlang OTP seems to be, install applications and releases on a single Erlang image instance. What are the best practices for keeping releases self contained? Is there a way to package releases such that you don't have to modify the site for machines that you're deploying to? How about gathering all dependencies into the codebase for management? Perhaps I'm going against the grain... I come from

android studio: release apk is not signed

由 被刻印的时光 ゝ 提交于 2019-12-04 09:06:59
问题 * I have rephrased the post since originally posted * When I try to run a just-built release apk, I get an error "the apk for your currently selected variant ... is not signed." This is in the Edit Configuration popup. Here are my steps: In the Build Variants tab, select "release" In the menu, choose Build -> Generate Signed APK In the popup, fill in the fields for the key store and passwords. In the second panel, change the destination folder to ...\app\build\outputs\apk (see note * below)

How often should you release software updates? [closed]

由 眉间皱痕 提交于 2019-12-04 09:04:53
问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 7 years ago . Moments ago Jeff Atwood said the following on twitter: Look, I love rapid new software releases, but the frequency of WordPress

软件发布版本区别介绍-Alpha,Beta,RC,Release

由 安稳与你 提交于 2019-12-04 08:56:02
一、 软件版本阶段说明 Alpha版: 此版本表示该软件在此阶段主要是以实现软件功能为主，通常只在软件开发者内部交流，一般而言，该版本软件的Bug较多，需要继续修改。 Beta版: 该版本相对于α版已有了很大的改进，消除了严重的错误，但还是存在着一些缺陷，需要经过多次测试来进一步消除，此版本主要的修改对像是软件的UI。 RC版: 该版本已经相当成熟了，基本上不存在导致错误的BUG，与即将发行的正式版相差无几。 Release版: 该版本意味“最终版本”，在前面版本的一系列测试版之后，终归会有一个正式版本，是最终交付用户使用的一个版本。该版本有时也称为标准版。一般情况下，Release不会以单词形式出现在软件封面上，取而代之的是符号(R)。 二、 版本命名规范 软件版本号由四部分组成： 第一个1为主版本号， 第二个1为子版本号， 第三个1为阶段版本号， 第四部分为日期版本号加希腊字母版本号，希腊字母版本号共有5种，分别为：base、alpha、beta、RC、release。例如：1.1.1.051021_beta。 三、版本号定修改规则 主版本号(1)：当功能模块有较大的变动，比如增加多个模块或者整体架构发生变化。此版本号由 项目决定 是否修改。 子版本号(1)：当功能有一定的增加或变化，比如增加了对权限控制、增加自定义视图等功能。此版本号由 项目决定 是否修改。 阶段版本号(1)

Commit some files while maven release:prepare

由 家住魔仙堡 提交于 2019-12-04 08:34:42
Is it possible to commit some file (no pom.xml) while mvn release:prepare? In My MultiModul Project I configured the rlease plugin with preparationGoals to change the Version in a sql file. <preparationGoals>clean verify org.codehaus.mojo:build-helper-maven-plugin:1.5:parse-version com.google.code.maven-replacer-plugin:replacer:1.5.0:replace</preparationGoals> Everything works fine but the changed sql File will not be commited. The sql File is in a subdirectory of the parent Folder. There are no pom.xml I use now a scm:checkin in the preparationGoals clean verify org.codehaus.mojo:build-helper

Jenkins + Gradle + Artifactory: Couldn't read generated build info

由 非 Y 不嫁゛ 提交于 2019-12-04 05:39:33
问题 I'm trying to push my artifacts to Artifactory with Jenkins Pipeline, which call Gradle tool. I am following the examples published on GitHub: Example1 Example2 My Jenkins Pipeline script: stage('Perform Gradle Release') { //ssh-agent required to perform GIT push (when tagging the branch on release) sshagent([git_credential]) { sh "./gradlew clean release unSnapshotVersion -Prelease.useAutomaticVersion=true -Prelease.releaseVersion=${release_version} -Prelease.newVersion=${development_version

Android App is too large and Linking disables functionality

由 …衆ロ難τιáo~ 提交于 2019-12-04 04:47:30
I'm done with my app and now I'm trying to build the .apk and test it on my phone (without debug, in release mode). Setting the Linking to " None " everything works fine. The Problem here is, that the App is too large - its 20MB and thats rubbish. I read that article about Linking: Click Here So I tried " Sdk Assemblies Only " and " Sdk and User Assemblies ". The second option (Both Assemblies) failed directly, I wasn't even able to see the first screen (Login) of my App. With Linking set to " Sdk Assemblies Only " I was able to come to the first screen (Loginscreen). The App is also 6.73MB

VSTS Rest API - Create Release

由 无人久伴 提交于 2019-12-04 01:43:03
问题 I'd like to start a release leveraging the VSTS Rest API defined here: https://www.visualstudio.com/en-us/docs/integrate/api/rm/releases#create-a-release but I need to set some of the variable values when I create the release. Looking at the ReleaseMetadata (https://www.visualstudio.com/en-us/docs/integrate/api/rm/contracts#ReleaseStartMetadata) I see there is a properties collection. Is this where I'd set the variable values? Is there any special naming convention I need to use in the

How to customise the tag format of the Maven release plugin?

由 南楼画角 提交于 2019-12-04 00:44:47
In our SVN repo, we store tags like this: trunk project_a project_b branches project_a branch_x branch_y project_b tags project_a 1.0 1.1 project_b 1.0 When I run the Maven release plugin's " prepare " goal on project A, by default it creates the tag as "tags/project_a-x.x", which does not match my tag naming scheme above. I am thus depending upon whoever does the release (i.e. a fallible human) to spot this and change the tag to "tags/project_a/x.x". How can I tell the release plugin to use the correct format by default? The "prepare" goal has a " tag " configuration option that claims to do
订阅 release