continuous-integration

问题 I am trying to automate existing sql server database deployment automation using Jenkins. One of the ways to automate is to include the SQL scripts (stored procedures, views, table creation) in a SQL server Database project using Visual Studio. Use MSBuild to build the project and deploy dacpac using SQLPackage.exe. However, the existing database has reference to other databases inside Stored Procedures/Views so I have import other databases inside the SQL Server Database project.

问题 Swift Package Manager got a new feature in Xcode 12.5: Swift Package Manager caches package dependencies on a per-user basis, which reduces the amount of network traffic and increases performance of dependency resolution for subsequent uses of the same package. If needed, you can disable cache use in xcodebuild by using the new -disablePackageRepositoryCache flag. (72204929) I would like to know where this is cached. Maybe we can use this to easily cache those dependencies in continuous

问题 I would like to run specific jobs on the .gitlab-ci.yaml if and only if files within specific directories of the repository have changed. Is there a way to do this with gilab's ci/cd tooling or would it be easier just to run a custom build script? 回答1: Changes policy introduced in GitLab 11.4. For example: docker build: script: docker build -t my-image:$CI_COMMIT_REF_SLUG . only: changes: - Dockerfile - docker/scripts/* - dockerfiles/**/* - more_scripts/*.{rb,py,sh} In the scenario above, if

问题 I would like to run specific jobs on the .gitlab-ci.yaml if and only if files within specific directories of the repository have changed. Is there a way to do this with gilab's ci/cd tooling or would it be easier just to run a custom build script? 回答1: Changes policy introduced in GitLab 11.4. For example: docker build: script: docker build -t my-image:$CI_COMMIT_REF_SLUG . only: changes: - Dockerfile - docker/scripts/* - dockerfiles/**/* - more_scripts/*.{rb,py,sh} In the scenario above, if

问题 I would like to run specific jobs on the .gitlab-ci.yaml if and only if files within specific directories of the repository have changed. Is there a way to do this with gilab's ci/cd tooling or would it be easier just to run a custom build script? 回答1: Changes policy introduced in GitLab 11.4. For example: docker build: script: docker build -t my-image:$CI_COMMIT_REF_SLUG . only: changes: - Dockerfile - docker/scripts/* - dockerfiles/**/* - more_scripts/*.{rb,py,sh} In the scenario above, if

问题 I have a workspace with few projects that must be built as static libraries and I have schemes with tests for them. I want to configure TeamCity to build and test each of those libraries, but it does not work with following error: ... /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace code/MyApplication/My Framework.xcworkspace -scheme One Of Tests TEST_AFTER_BUILD=YES clean build -configuration Debug -sdk iphonesimulator6.1 in directory: /Users/Me/TeamCity/buildAgent

问题 I have a workspace with few projects that must be built as static libraries and I have schemes with tests for them. I want to configure TeamCity to build and test each of those libraries, but it does not work with following error: ... /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace code/MyApplication/My Framework.xcworkspace -scheme One Of Tests TEST_AFTER_BUILD=YES clean build -configuration Debug -sdk iphonesimulator6.1 in directory: /Users/Me/TeamCity/buildAgent

问题 On an internal GitLab server there is one project with a CI script not tolerating concurrent execution of multiple pipelines (external side effects in Kubernetes). So if two commits are pushed in succession with less time in between than the first pipeline needs to finish, the two pipelines will run concurrently, which causes both to fail. Globally setting concurrent = 1 for the CI runner (one K8s runner used across multiple repos) is not practicable in that case, because pipelines of other

问题 On an internal GitLab server there is one project with a CI script not tolerating concurrent execution of multiple pipelines (external side effects in Kubernetes). So if two commits are pushed in succession with less time in between than the first pipeline needs to finish, the two pipelines will run concurrently, which causes both to fail. Globally setting concurrent = 1 for the CI runner (one K8s runner used across multiple repos) is not practicable in that case, because pipelines of other

问题 I am using jenkins for continuous integration. I have created seperate views like view A for server A , view B for server B etc. Each view builds my project based on the server's environment properties. But i could see that irrelevant upstream and downstream are getting created even when it is not created explicitly. Is there any solution for this? :( 回答1: In Jenkins,When you have projects that depend on each other, Jenkins can track which build of the upstream project is used by which build