I want to automate the build apk process using azure devops.
I am trying to integrate azure devops CI/CD pipeline in my expo project with yarn.
I have created build pipeline but i am not able to create release pipeline.
Can anyone help me?
This is the link with video and documentation how to crate release pipeline
https://learn.microsoft.com/en-us/azure/devops/pipelines/release/?view=azure-devops
Make sure you publish the build Artifacts in the build pipeline so that the files are available in the Release pipeline. To create a release pipeline you will have to add install Google Play from the marketplace and then install the Google Play - Release or Google Play - Relase Bundle depending on if you have built .apk or .aab. In the task you will have to setup a Service Connection by going to the Google Play store and creating a service account and then copying the credentials back to the Service Connection.
It's a long process and I have created a comprehensive article specifically for that purpose. Here is the link.
Related
I'm trying to build a CI pipeline for a Kotlin project developed on Android Studio. Using Azure DevOps pipelines.
I'm having an issue finding a Kotlin plugin or Tasks for the pipeline as we can see in the picture.
Anyone have an idea about how can we implement this type of pipeline? I didn't find anything on the internet and Microsoft have no documentation.
If I understand correctly the answer you are looking for is the Gradle task. Here is a blog from someone using gradle and in azure devops with their Kotlin code. But I am sure there are more details around how to set up gradle task for kotlin build.
The issue was not with Kotlin or Java. The issue was with the SDK being used on the Hosting Agent.
The solution was the following steps:
Upload a SDK to Azure Blob Storage
Use the Use Java Task in order to install the specified SDK
Run the Android Pipeline with Sonarqube tasks, build was successfully run and SonarQube Code Review was successfully executed.
i'm already thankfull for anyone reading this.
I've stumbled across some problems trying to deploy a Nuxt application in a correct way. For testing purposes i've created a clean installed Nuxt application so i'm sure nothing is wrong with my codebase. What my ultimate goal is is to push all my nuxt code to github which than gets picked up from a azure deployment pipeline and generates the needed build files and drops them to the webapp service and runs the needed start command. There's no documentation to be find about Azure which is really annoying for me. I'm not used to deploying stuff through a pipeline but need this to be working for this project.
Has anyone experience with Nuxt and deployments through Github -> Azure pipeline -> Build -> Web app running immediatly
What's i've tried already is pushing all the source code to a repository which get's picked up by azure pipeline. The only thing the pipeline does is paste the code in the wwwroot folder. Which is obviously not enough to make the application run automated.
What i expect is some insight from someone who is experienced with nuxt and azure deployments through github/bitbucket (doesn't really make a difference)
You have to configure your pipeline to build the nuxt files and deploy them. You can usually achieve the first step through npm commands, npm install then npm run build.
There's a few different ways to deploy them, which you'll have to decide between depending on your use case and environment. You can create an endpoint pointing to a CDN serving a blob, zip the built files and publish the artifact which is then used by a release pipeline, etc. Once the next files are created, you have all you need to deploy.
My question is about separate package/deploy steps. What I want to do is to package the service at step 1 of the deployment process, then copy the content of the package to another machine and deploy from there. Can't make it work. I use no parameters, and "serverless package" seems to work fine (creates ".serverless" folder without an attempt to deploy), but when I copy the ".serverless" folder to another location and execute 'serverless deploy" it only says "packaging service" and does nothing. Is this how deployment of a package supposed to work? This happens on a vanilla aws node service.
The command serverless deploy --package path-to-package seems to be what you are looking for, as specified in the Serverless Framework documentation.
This deployment option takes a deployment directory that has already been created with serverless package and deploys it to the cloud provider. This allows you to easier integrate CI / CD workflows with the Serverless Framework.
You were probably missing the --package option.
I am very new to this and I want to know how to deploy spinnaker to PCF (on closed network) using spring cloud spinnaker. Do we need to build components of spinnaker before deploying, or can we directly push spring-cloud-spinnaker jar file to space. Please guide me with some reference.
You no longer have to build all submodules anymore. Just build the project and push to your PCF environment. From there you can use it per ref docs.
I am working on automating our ASP.Net projects' release, using Octopus Deploy. While creating release in Octopus, I am performing following testing completely manually:
I am checking if release is deploying
Everything expected
In the expected places
All required services or web services were restarted
All Pre/Post deploy scripts ran successfully
This means going to different servers and reading release log generated by Octopus Deploy. It leaves risk of introducing mistakes and any future change can make deployment unstable.
Is there any tool to perform a kind of integration testing for Octopus Deploy Release or automate the process mentioned above. I am also open to writing a quick tool automating my testing but then I was wondering what will be the best way to go about it.
Thanks!
For Octopus 2.0 we're building a powerful API that gives you access to everything in Octopus. Using the API you'll be able to create and deploy a release, as well as read the activity logs and see what was deployed. You could hook this up to an automated test (which is what we're doing internally for end-to-end automated testing).