Android Studio with Jenkins Integration - android-studio

I guess many of you have performed here continuous integration of Jenkins with Android Studio.
I have performed the following steps:
Created a project from Android Studio.
Created a repository in GitHub.
Pushed the code base into the Github.
Configured Jenkins.
Now, my target is that whenever I perform some checkin operation of the Android code into the Github, then automatically Jenkins will create a build on the latest codebase.
I already have downloaded the necessary plugins that are required for Jenkins.
Can anybody tell me step by step how can I achieve the same, since I am not sure, how Jenkins will get the apk file that is getting created once Jenkins performs the build operation on the new codebase?

It is an old question, and may of no use for questioner, but it may help others looking for solution.
If you are looking for apk file then it is available in build path of workspace.
It looks like you are interested in CD part, then you can use "Google Play Android Publisher". It enables Jenkins to manage and upload Android app files (AAB or APK) to Google Play. please refer to following doc help from Jenkins:
https://plugins.jenkins.io/google-play-android-publisher/

Related

cordova integrate files into the prject

Good day everyone; having project and must update to cordova 9.0.0 and at least to android 8.0.0 to publish in google play, when i try to build the build fail because (Could not resolve all artifacts for configuration ':classpath'), the most likely cause is connections errors the question is
can i set a proxy program (say for example tor) through the node.js command prompt (and not through android studio because it doesn't work)
if that not possible, if i manged to download the required files manually (example bundletool-0.13.2.jar https://dl.google.com/dl/android/maven2/com/android/tools/build/bundletool/0.13.2/bundletool-0.13.2.jar) is there a way to integrate them somehow to the project as a work around
Thanks in advance

Why are my gradle dependencies in Android Studio not being cached?

I downloaded Google's Android Sceneform example project, solarsystem, under the samples folder in the hyperlink. I intend to use it as a base for an AR Application I need to create. However, I need to take the project to an offline environment.
While I am connected to the internet, the project builds without issue. However, when I go offline, I end up with a
No cached version of com.android.tools.build:aapt2:3.4.1-5326820 available for offline mode.
I have no problem syncing the project, but I am unable to build anything. I have tried downloading the appt2 dependency from Google's Maven Repository directly and including it in my project's dependencies in the build.gradle folder but I still get the same error. My project MUST be built offline.
I have also searched online for a few solutions, but none have worked for me so far. I found out that Google did remove the version of aapt2 that I am using, but I was still able to download it from their repository. As I understand, Android should be able to build my project so long as the dependencies have been cached. I am just trying to identify the problem at this point. Why has this one dependency not been cached and why despite including it's jar directly have I not been able to run it?

Visual Studio Code won't compile or submit USQL script

I am using Visual Studio Code (VS Code) to compile and then submit usql scripts on our Azure platform.
Something happend and I cannot compile or submit any usql jobs anymore, with following error message:
I tried multiple solutions to fix it:
Reinstall visual studio code
Updated to the latest version (1.38)
Reinstall the Azure Data Lake Tools package
Remove all generated folders and files and start from scratch
I made sure this is not access-related (I can run jobs on Azure web portal)
The script does not have any bugs and it is supposed to run (checked on Azure web portal)
I work on MS Windows VM x64, VS Code version 1.38.
I am completely puzzled by that, any help greatly appreciated!
I can't reproduce your issue on my side. I follow steps in this detailed guide and it works well for me.
Since you already sorted out several possible issues, I would suggest you checking if you missed some installations follow above link. In particular, the following steps:
2.1 To install BuildTools, click visualcppbuildtools_full.exe in the LocalRunDependency folder, then follow the wizard instructions.
2.2 To install Win10SDK 10240, click sdksetup.exe in the LocalRunDependency/Win10SDK_10.0.10240_2 folder, then follow the
wizard instructions.
And and run ADL: Start Local Run Service.
Just for summary, it works after updating sdk version to 1.38.1.

Azures Visual Studio Team Services (VSTS) Build & Release process fetches more projects than just the project I am wanting to build

My VSTS Repository contains 50+ Visual Studio projects of Azure Web Apps and I was requested to get an automated build and release process in place for one of them. I went thru and selected a Visual Studio template and on the build solution I selected only the one project I wanted to do a build and release on but when I queue the build to run it starts doing a get latest on every project in the repository. This is unacceptable because it would take hours to get latest on all the projects just to compile and publish one website. This makes no sense to me. Is there a way to limit what the build does a get latest on?
Depends on the repository type you're using. In case you're using TFVC, you can go to the Repositories tab and configure your workspace mappings to match exactly what you need for your project.
If you're using Git, then you're out of luck, the way git repositories are synced, the whole repository is always fetched when a build is initiated.
If you're using your own build agent, you can configure it to retain the sources directory, in which case only the differences are synced when a build runs.

create azure package with build

I was just upgrading my project from sdk 1.3 to 1.7 and I noticed that now when I build the application the package(cspkg) is not created with the build. I have go click on publish to create a package. Is there a way to tell VS to create a package everytime a build is triggered.
Also using msbuild is there a way to do the same thing. I have multiple projects under a solution, Most of which are just libraries and then there is this azure app. Is there a way to specify a single msbuild statement with params to tell the azure app to create the package as well as build the other projects. Also when I specify debug the debug package should be created and when I specify release switch the release package should be created.
How could I do the same thing on my build server as well where I have a .proj file which specifies the sln to build. How could I mention a switch to build the package there.
Thanks,
Kunal
You can configure CSPACK command (Be sure to have CSPACK.exe launched from SDK 1.7 Path otherwise you will get some schema related errors with SDK 1.6 project) as Post Build event in your Windows Azure Application Build settings. This way when you will build, after successful build CSPACK command will run and package your application. Same way you can configure your MSBuild configuration. I just tested and it worked for me.
Visit this MSDN article on packaging a cloud service to learn more.
You can do this using msbuild as well. See the Resolution section of this question.

Resources