continuous-integration

问题 I'm getting following error when executing VSTS Developer Tools Build Tasks, I have included extension manifest, Please help me to resolve this. error: Failed Request: Bad Request(400) - Part URI is not valid per rules defined in the Open Packaging Conventions specification. tfx failed with error: Error: C:\agent_work_tools\tfx.cmd failed with return code: 4294967295 – <PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011"> <Metadata> <Identity Id=

问题 I have 2 jobs in Jenkins: Build and run unit tests (Build and) run integration tests Job-2 is a Downstream project of Job-1 . Job-1 initiates build and run unit tests on it. Job-2 initiates build as well and run integration tests. I would like to change that, and make Job-2 to run the tests on the result build that was initiated by Job-1 . 回答1: You could use Copy Artifact Plugin and use Job-1 artifacts from Job-2 to run some tests on them. Refer to this post for more information. Hope it will

问题 Cannot start jenkins. giving below logs when try to restart but doesnt work - -bash-3.2$ ./jenkins.sh start Jenkins is currently stopped... Starting Jenkins with command cd /eas/jenkins;/eas/jenkins/jenkins_jre/jre1.7.0_51/bin/java -Xms1024m -Xmx2048m - XX:MaxPermSize=512m -DJENKINS_HOME=/eas/jenkins/home -jar jenkins.war -bash-3.2$ standard in must be a tty Please help! 回答1: No, adding to sudoers file didnt solve it. there was issue with JVM where JDK was not able to initialize because of

问题 i have 4 environments : dev (developers area) test (test area) preprod (pre production environment) production (production environment) these environments needs different configuration to execute tests (differents urls, usernames, assets, and so on). how to pass there configurations to jest as a parameter in continous integration? 回答1: As you can read here, jest would not permits to pass custom arguments you can use to handle custom configuration loaded at runtime. i propose a workaround

问题 I am working on creating an entire CI/CD pipeline for my Data factory V1 project I am using VSTS for the implementation. I am able to carry out most of my task over VSTS which are required for deployment, However, I am not able to determine if it is possible to completely implement continuous deployment over my project. I have one common solution file responsible to hold 4 different data factory project & each project holds 4 data flow pipelines each. The issue is not every time is the case

问题 I am using github branch source plugin on jenkins to discover and build pull requests, but I would like to have the "Pull Requests" tab display the branch name in the "Name" column instead of just "PR-n" with n incrementing for every new PR. Is that possible? 来源： https://stackoverflow.com/questions/58656798/rename-pr-jobs-in-the-pull-requests-tab-of-a-multibranch-pipeline-in-jenkins

问题 What specific changes need to be made to the Jenkinsfile below in order to isolate the name of the branch of the commit into a variable that can be printed out in the logs? In the case below, the name of the branch is GWS-43-getissueforcommit . Here are the specifics: Jenkinsfile: The following Jenkinsfile prints out the branch name in the midst of the output produced by running the checkout(scm).GIT_ASKPASS command, but this information is lost when the subsequent line of code ( sh "echo

问题 What specific changes need to be made to the Jenkinsfile below in order to isolate the name of the branch of the commit into a variable that can be printed out in the logs? In the case below, the name of the branch is GWS-43-getissueforcommit . Here are the specifics: Jenkinsfile: The following Jenkinsfile prints out the branch name in the midst of the output produced by running the checkout(scm).GIT_ASKPASS command, but this information is lost when the subsequent line of code ( sh "echo

问题 What specific changes need to be made to the Jenkinsfile below in order to isolate the name of the branch of the commit into a variable that can be printed out in the logs? In the case below, the name of the branch is GWS-43-getissueforcommit . Here are the specifics: Jenkinsfile: The following Jenkinsfile prints out the branch name in the midst of the output produced by running the checkout(scm).GIT_ASKPASS command, but this information is lost when the subsequent line of code ( sh "echo

问题 Our company currently uses TFS for source control and build server. Most of our projects are written in C/C++, but we also have some .NET projects and wouldn't want to be limited if we need to use other languages in the future. We'd like to use Git for our source control and we're trying to understand what would be the best choice for a build server. We have started looking into TeamCity, but there are some issues we're having trouble with which will probably be relevant regardless of our