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.
Related
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.
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 have appfuse maven project , is it better to deploy it using Click start Tomcat or as a Jenkin Maven project? I have tried both but it does not seem to be working in any ways. I have created database and bound it to the app. still it gives error for spring bean creation etc. Can anyone help in this scenario?
If I would need to deploy my appfuse maven application on CloudBees platform, I will try two different ways:
Use the Tomcat 7 Maven ClickStart as a template changing the SCM to your repo.
Use the CloudBees SDK to deploy your application.
In this last case, you just need to generate your .war file, in case you use maven, launching:
mvn clean package
And then you can deploy your application from the CLoudBees SDK using:
bees app:deploy -t tomcat7 -a APPID MYFILE.war
You say that when you deploy your application it gives error for spring bean creation. However, you don't attach any stacktrace to your question, so it is difficult to do any kind of diagnosis on our end.
I just figured out, how to release to CB hosted maven "release" repository. I am trying to figure out, how to deploy tagged version to CB application.
I understand, I can manually upload WAR file but is there any script. As far as I know maven plugin for CB doesn't support it.
I have one appserver is running snapshot builds from jenkins.
I have other appserver, which I want to deploy only tagged/released artifact.
There are four ways to deploy applications to the CloudBees RUN#cloud service:
Using the bees command provided by the SDK
Using the bees-maven-plugin
Using the manual upload via the web GUI
Using the CloudBees Deployer plugin for Jenkins
Which option you choose depends on where the deployment will take place from... And the from I am talking about is which machine is doing the deployment not where the file is sourced.
If running from a Jenkins job, the best bet is the Jenkins plugin.
If running from your own laptop, the web ui or the bees command is simplest.
If running as part of a maven build, the maven plugin is simplest... (Though I should warn that the maven plugin (temporarily removing my cloudbees hat and putting on my maven PMC hat) is shite and does it all arsewise ;-) )
Your best bet is to set up a Jenkins job that uses dependency:get to pull the artifact from the repo and then add a cloudbees deployer build step to push to RUN#cloud
The good news is that bashing the maven plugin into something more maven like is on our roadmap... Hopefully that will enable actions like you can achieve with the ship-maven-plugin#mojo where you can specify a specific released version for "shipping" to production.
I suppose, that what you want to do is to deploy a release artifact to your repository.
have a look at maven-release-plugin.
Briefly, what you need to do is:
$ mvn release:prepare
$ mvn release:perform
it's not so trivial, since you need to configure appropriately your pom.xml to get it working. Have a look at the maven-release-plugin examples and usage pages.
Are you creating the tag/release from a Jenkins build? If so you could probably use the Deploy to CloudBees post-build step with target/checkout/something.war.
More generally I guess you would want to write a script to use mvn dependency:get followed by the Bees SDK to obtain the latest released artifact and deploy it.
I have an existent deployed spring app up on cloudfoundry, deployed from one PC. Now I set up Eclipse with my project on another PC and I added my existent cloudfoundry deployment via the Cloudfoundry Eclipse plugin. The problem is that the CF Server with my deployed app is not sync-ed with my local eclipse project, so I cannot deploy any changes from my project.
Is there any way of doing this sync after I add my Cloudfoundry Server?
Thanks
The cloudfoundry deployment approach will not automatically (dynamically) maintain synchronization between your two eclipse environments. You might use a source control approach where you push your version from one eclipse environment to github and use that as the synchronization mechanism by cloning it and importing the project into one or the other eclipse environments.