continuous-deployment

问题 This is error message I got ./gradlew clean assembleRelease /Users/bhanukaisuru/.jenkins/workspace/OrelGo@tmp/durable-b74adbad/script.sh: line 1: ./gradlew: No such file or directoryPipeline Script Pipeline Script stage('Build Release APK') { sh "./gradlew clean assembleRelease" } 回答1: You do not need to specify the Jenkins workspace with the commands sh and bat if you want to execute a command on the root level of it. sh 'mkdir test' would create a folder in <jenkins_workspace>/test for

问题 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

问题 I am trying to get travis-ci to run a custom deploy script that uses awscli to push a deployment up to my staging server. In my .travis.yml file I have this: before_deploy: - 'curl "https://s3.amazonaws.com/aws-cli/awscli-bundle.zip" -o "awscli-bundle.zip"' - 'unzip awscli-bundle.zip' - './awscli-bundle/install -b ~/bin/aws' - 'export PATH=~/bin:$PATH' - 'aws configure' And I have set up the following environment variables: AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION with their

问题 I've got multiple Android apps that are currently distributed via Google Play and the Amazon store. My goal is to automate the app upload process to minimize the time required to upload a new update. I've already done that for Google Play by using the Google Play Developer API. Is there an equivalent API for the Amazon store for uploading new app versions or do I have reverse engineer the data send by the browser and develop an API library based on that? I already searched but didn't found

问题 I'm developing a ASP.NET Core 1.0 application using Visual Studio Code and I can't/won't use the built-in publishing tools in Visual Studio IDE. I have this working for ASP.NET 5 RC1 (dnx-clr-win-x86.1.0.0-rc1-update1) but I don't know how to update this to ASP.NET Core 1.0 and the tools does not seem to be updated yet. For ASP.NET 5 RC1 I used the azure-cli package to generate a deploy.cmd file with the following command: azure site deploymentscript --aspNet5 .\server\project.json -p .

问题 Currently I have my git set up for AngularJS Projects. I do testing locally and if the tests pass I commit the code to Git repo. What I want to do is set up the UI project with CI and CD such that even after testing locally when I commit the code to Git repo it should trigger tests and then build (for Angular2 or minify for example for AngularJS) the project ready to be used. If the tests fail it should reject the push/changes. It should then push the passed code to the appropriate deployment

问题 i have a Jenkins multibranch Pipeline configured which should fetch sources from a remote GIT repository for a build. Jenkins no seems to "randomly" pick an old commit for the build an showing the message "Multiple candidate revisions" in Build log files. My Pipeline is looking like: checkout( [ $class: 'GitSCM', branches: [[name: "release/0.0.1"]], doGenerateSubmoduleConfigurations: false, extensions: [ [$class: 'MessageExclusion', excludedMessage: '(?s)^\\[DOC\\] Robot.*'] ], submoduleCfg:

问题 I have an API developed in NodeJS and have successfully set up continuous integration via a .gitlab-ci.yml file. The next stage is to set up continuous deployment to Heroku if all tests pass on the master branch. There are plenty of tutorials covering the deployment of Ruby and Python apps but nothing on NodeJS. Currently my .gitlab-ci.yml file looks like this: image: node:latest job1: script: "ls -l" test: script: "npm install;npm test" production: type: deploy script: - npm install - npm

问题 I have an API developed in NodeJS and have successfully set up continuous integration via a .gitlab-ci.yml file. The next stage is to set up continuous deployment to Heroku if all tests pass on the master branch. There are plenty of tutorials covering the deployment of Ruby and Python apps but nothing on NodeJS. Currently my .gitlab-ci.yml file looks like this: image: node:latest job1: script: "ls -l" test: script: "npm install;npm test" production: type: deploy script: - npm install - npm

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 5 months ago . From what I have seen so far, nodejs apps get deployed either by creating a completely static bundle (e.g. angular), or by pulling the source from the repo and running npm install and npm start (usually seen when express/mongo are used). However, I am developing an express/mongo