continuous-integration

问题 I'm looking for a plugin/approach that lets me set and read a persistent global variable for use between jobs. The scenario is that I have CI job that runs tests on various branches of the codebase and I want to associate a build number that corresponds to the last stable build of the release branch. i.e. Build No Branch Result GolbalSharedThingVal 5 release Success 1.5 6 dev Fail 1.5 7 dev Success 1.7 8 release Unstable 1.7 9 release Success 1.9 10 release Fail 1.9 Then in my deployment job

问题 I'm researching a way to integrate a staging environment on our IIS Server, where it is possible to warm up the application before swapping it with the production environment. The only real solution I can find is: Swapping directory settings Which to me sounds like a slow process, because the IIS will have to compile and warmup the new dir after the swap. ( Am I assuming this correctly?) Have two sites, and swap the bindings, after staging has been warmed up. Having a load balancer, and

问题 I know the procedure and also how to configure an automated docker hub from GitHub or BitBucket. But what I have to do right now is to create two docker hub repositories called Test/main and Test/depend . The first repository Test/main is connected with GitHub and whenever there is a new push the image will be automatically build. But I want to trigger another repository Test/depend whenever there is a change on the Test/main repository. Is it possible to configure such scenario? 回答1: This

问题 I know the procedure and also how to configure an automated docker hub from GitHub or BitBucket. But what I have to do right now is to create two docker hub repositories called Test/main and Test/depend . The first repository Test/main is connected with GitHub and whenever there is a new push the image will be automatically build. But I want to trigger another repository Test/depend whenever there is a change on the Test/main repository. Is it possible to configure such scenario? 回答1: This

问题 Is there an elegant way to tell ESLint to ensure that we're not using any ES6 / EMCAScript 2015 syntax / functions? I've found the following answer somewhat helpful but it seems that it doesn't take care of everything (e.g. I don't see how to catch the usage of Object.assign()): How to disable usage of certain ES2015 features with ESLint 2? 回答1: eslint-plugin-es5 is the package dedicated to your use case. For example the rule es5/no-es6-static-methods forbids the usage of Object.assign . 来源：

问题 Is there an elegant way to tell ESLint to ensure that we're not using any ES6 / EMCAScript 2015 syntax / functions? I've found the following answer somewhat helpful but it seems that it doesn't take care of everything (e.g. I don't see how to catch the usage of Object.assign()): How to disable usage of certain ES2015 features with ESLint 2? 回答1: eslint-plugin-es5 is the package dedicated to your use case. For example the rule es5/no-es6-static-methods forbids the usage of Object.assign . 来源：

问题 Is there an elegant way to tell ESLint to ensure that we're not using any ES6 / EMCAScript 2015 syntax / functions? I've found the following answer somewhat helpful but it seems that it doesn't take care of everything (e.g. I don't see how to catch the usage of Object.assign()): How to disable usage of certain ES2015 features with ESLint 2? 回答1: eslint-plugin-es5 is the package dedicated to your use case. For example the rule es5/no-es6-static-methods forbids the usage of Object.assign . 来源：

问题 I have a workflow for CI in a monorepo, for this workflow two projects end up being built. The jobs run fine, however, I'm wondering if there is a way to remove the duplication in this workflow.yml file with the setting up of the runner for the job. I have them split so they run in parallel as they do not rely on one another and to be faster to complete. It's a big time difference in 5 minutes vs. 10+ when waiting for the CI to finish. jobs: job1: name: PT.W Build runs-on: macos-latest steps:

问题 Using a builder to generate a smaller docker image, what would be a good way to run npm run test ? I seems like running it in the Dockerfile after the build would make sense but maybe I'm missing something Dockerfile # Global args to persist through build stages ARG docker_build_user ARG docker_build_time ARG docker_build_head ARG docker_build_head_short ARG docker_build_submodules_head FROM node:8.9.4-alpine as builder WORKDIR /app COPY . . RUN apk add --no-cache bash RUN apk add --no-cache

问题 I am using maven-dependency-plugin. I need to download only a ZIP file and exclude all jar files. Plugin configuration looks the following way. <execution> <id>copy-dependencies</id> <phase>package</phase> <goals> <goal>copy-dependencies</goal> </goals> <configuration> <!-- <outputDirectory>${project.build.directory}</outputDirectory> --> <overWriteReleases>false</overWriteReleases> <overWriteSnapshots>false</overWriteSnapshots> <overWriteIfNewer>true</overWriteIfNewer> <excludes>**/*.jar<