Make sure you’re using the drop down list from the grid (not the one at the top of the dialog), and do not check the “Create new solution configurations” checkbox when adding your new project configuration.
A couple things I can think of: user credentials are wrong url to server is wrong user does not have access to the deployment repository user does not have access to the specific repository target artifact is already deployed with that version if it is a release (not -SNAPSHOT version) the repository is not suitable … Read more
EDIT2 (2020-03-09) If you are using gradle 6.0 in your gradle-wrapper.properties, you may also encounter a similar situation because there is this bug in 6.0 version. Try 6.0.1 instead. Yesterday (2018-03-27) Android Studio published an official update from 3.0.1 to 3.1, and it looks like a lot of people (including me) start running into this … Read more
The best solution for this is to create a simple parent pom file project (with packaging ‘pom’) generically for all projects from your organization. <?xml version=”1.0″ encoding=”UTF-8″?> <project xmlns=”http://maven.apache.org/POM/4.0.0″ xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd”> <modelVersion>4.0.0</modelVersion> <groupId>your.company</groupId> <artifactId>company-parent</artifactId> <version>1.0.0-SNAPSHOT</version> <packaging>pom</packaging> <distributionManagement> <repository> <id>nexus-site</id> <url>http://central_nexus/server</url> </repository> </distributionManagement> </project> This can be built, released, and deployed to your local nexus … Read more
You need 2 servers and a load balancer. Here’s in steps: Turn all traffic on Server 2 Deploy on Server 1 Test Server 1 Turn all traffic on Server 1 Deploy on Server 2 Test Server 2 Turn traffic on both servers Thing is, even in this case you will still have application restarts and … Read more
I originally saw this error after upgrading from 0.2.13 to 0.3. These instructions have been updated for the release of Android Studio 0.5.2. These are the steps I completed to resolve the issue. 1.In build.gradle make sure gradle is set to 0.9.0 buildscript { repositories { mavenCentral() } dependencies { classpath ‘com.android.tools.build:gradle:0.9.0’ } } 2.In … Read more
Update 2019: These days, the question would be seen in a context using Git, and 10 years of using that distributed development workflow (collaborating mainly through GitHub) shows the general best practices: master is the branch ready to be deployed into production at any time: the next release, with a selected set of feature branches … Read more
Meanwhile I have found the (for me) perfect solution: nexe, which creates a single executable from a Node.js application including all of its modules. It’s the next best thing to an ideal solution.
I have written a detailed essay on this topic here: http://blog.itaysk.com/2017/11/20/deployment-strategies-defined In my opinion, the difference is whether or not the new ‘green’ version is exposed to real users. If it is, then I’d call it Canary. A common way to implement Canary is regular Blue/Green with the addition of smart routing of specific users … Read more
I’ve seen this happen a few times on my HTC Desire. I’ve never figured out whether the problem is in adb or the device but I usually do the following: Restart adb by issuing ‘adb kill-server’ followed by ‘adb start-server’ at a cmd prompt Disable and re-enable USB debugging on the phone Rebooting the phone … Read more