continuous-deployment

We have a creat-react-app application, which includes a couple of variables that are different (react) build time, depending on where the build will be deployed. For example, we need to specify build time which URL will be used, e.g. https://app-stage.company.com for a release-x.y.z build vs. https://app.company.com for a master build (please refer to this article about GitFlow ). We've already created such a build pipeline as suggested here , which will build with the appropriate react config for any commit to branches master , release-x.y.z , dev , hotfix-x.y.z . We would like to create a

​In our Web API application, Continuous deployment need a following scenario. User will check in code in VS, Code will get automatically build, Code will be Published, Code will be deployed. But If we are using Entity Framework Code First approach, How can we update database without manual commands (Add-Migration/Update Database)and make database up to date with that check-in. You can try to run Add-Migration/Update Database commands in the build/deploy process. Assume you are using vNext build, Add a " Nuget Installer " task in your build definition first to restore the Entity Framework

I have a dotnet core app. I am building a pipeline in teamcity. and once the teamcity detects the change in the cource code, It downloads the source code runs dotnet restore dotnet build and copies the content in the output folder to Azure app service. I believe to run the app i need to run the command dotnet nameoftheprojectdll.dll but how can I run this command on the app service. and I need to run this command as part of a build script. The Short Answer You need to use the dotnet publish command to package your application for IIS deployment, and copy that output (not the output from dotnet

I have a single solution full of projects that are to be shared amongst my organization as general nuget packages. The solution is encompassed by one git repository and we have TeamCity running our builds for us, although we are not overly advanced in that we manually kick off the Teamcity builds when we are ready to generate/publish a new Nuget package for a given project in the solution, every project has its own TeamCity build configuration. When built, the projects generate nuget packages via the .csproj <project/> tag: GeneratePackageOnBuild we also control the versioning via version tags

i am trying to deploy the spring boot app to AWS EC2 instances. i have seen lot of blog and tutorial explained deployment process completely which is understandable. i am struggling how to do continuous deployment or delivery in jenkins which main feature where spring boot app name or jar file name changes that time. my pipeline pipeline { agent any tools{ maven 'localmaven' } stages { stage('Build') { steps { sh 'mvn clean package' } post { success { echo 'Now Archiving...' archiveArtifacts artifacts: '**/target/*.jar' } } } stage('Deliver') { steps { sh 'scp -v -o StrictHostKeyChecking=no -i

I have a Java application, which runs inside web container (Jetty at the moment) and responds to requests via web services. Now I want to create a mechanism, which allows to deploy (transfer the WAR file to the server, install the new version there) a new version of the application to Amazon EC2 instance as easily as possible (ideally - by running some Maven command). I'm using Beanstalk for my version control and they offer deployment support, but I couldn't figure out how to apply it to my scenario. Are there any tutorials on how to deploy web applications to Amazon EC2 with Maven (with or

UPDATE 2017/02/28 The tags in the release triggers are not source control tags, they are tags that can be generated by your build step. You can tag your builds automatically (see below), or manually during a build, I haven't tried this yet. My assumption about the tags were flawed , which makes this question pretty much invalid. However I am going to try and see if I can find some sort of workaround for my exact scenario, and then I will post it here. Background I am setting up our CI/CD pipeline using VSTS, and part of our branching strategy is that only release/* branches that are tagged