Docker agent running a jenkins job using wrong npm version(使用错误的NPM版本运行Jenkins作业的Docker代理)-6ren

Docker agent running a jenkins job using wrong npm version(使用错误的NPM版本运行Jenkins作业的Docker代理)

翻译作者：bug小助手更新时间：2023-10-26 22:45:09

Context :

I'm building a react app using a jenkins pipeline, where the agent is docker agent defined by a Dockerfile in the root of my project, the bug happens in the npm ci stage, where i the console prints warnings about the node version being old ( v12 ), which is wierd because i installed the latest using nvm ( see Dockelfile ).

我正在使用Jenkins管道构建一个Reaction应用程序，其中代理是由我的项目根目录中的Dockerfile定义的docker代理，错误发生在NPM ci阶段，在那里我的控制台打印关于节点版本是旧的(V12)的警告，这是奇怪的，因为我使用NVM安装了最新的(参见Dockelfile)。

The Problem :

In the build logs it says i'm using node v12, but when building the docker image i printed the node version and it was v20.

在构建日志中，它说我正在使用节点v12，但在构建docker映像时，我打印了节点版本，而它是v20。

This is my Jenkinsfile :

这是我的Jenkins文件：

pipeline {

    agent {
        dockerfile {
            filename 'Dockerfile.agent'
        }
    }

    environment {
        TAG="$env.BRANCH_NAME-v$BUILD_NUMBER"
        REGISTRY="foo"
        AWS_REGION="eu-north-1"
    }

    stages {
        stage('Build React App') {
            steps {
                script {
                    sh "npm ci"
                    sh "npm run build"
                }
            }
        }
        stage("Build Docker Image") {
            steps {
                sh "docker build -t staff-manager-admin-ui  ."
            }
        }
        stage('Push to Registry') {
            steps {
                script {
                    withCredentials([string(credentialsId: 'aws-key', variable: 'awsKey'), string(credentialsId: 'aws-secret', variable: 'awsSecret')]) {
                        withEnv(["AWS_ACCESS_KEY_ID=$awsKey", "AWS_SECRET_ACCESS_KEY=$awsSecret", "AWS_DEFAULT_REGION=$AWS_REGION"]) {
                            sh "aws ecr get-login-password --region $AWS_REGION | docker login --username AWS --password-stdin $REGISTRY"
                            sh "docker tag staff-manager-admin-ui $REGISTRY:$TAG"
                            sh "docker push $REGISTRY:$TAG"
                        }
                    }
                }
                
            }
        }
    }
}

this is the Dockerfile.agent :

这是Dockerfile.agent：

FROM jenkins/agent:latest

USER root

# Install stuff needed for 
RUN apt-get update && \
    apt-get install -y npm docker awscli default-jdk && \
    rm -rf /var/lib/apt/lists/*

# install npm & node
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash \
    && . ~/.nvm/nvm.sh \
    && nvm install node \
    && node -e "console.log('Running Node.js ' + process.version)"

# Add nvm path to bashrc and source it
RUN echo 'export NVM_DIR="$HOME/.nvm"' >> $HOME/.bashrc \
    && echo '[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"' >> $HOME/.bashrc

# Source bashrc to make nvm available in this shell
RUN . $HOME/.bashrc


# Add the commands to fix npm permissions
RUN mkdir -p /.npm
RUN chown -R 1002:1002 /.npm


# USER jenkins
USER 1002:1002

Here's a screenshot of the relevant part of the Docker image building

下面是Docker镜像构建相关部分的截图

and then during npm ci it says i'm using v12 ?

然后在NPM Ci期间，它说我正在使用V12？

More context :

Repo : https://github.com/HL-Abdallah/staff-manager-admin-ui-cloudsec/tree/acceptation

回购：https://github.com/HL-Abdallah/staff-manager-admin-ui-cloudsec/tree/acceptation

Full job log :

完整作业日志：

Started by user Abdallah
20:42:02 Connecting to https://api.github.com using github-access
Obtained Jenkinsfile from 58cd4b60dcc9413beca260ed4c601098ab04d2eb
[Pipeline] Start of Pipeline
[Pipeline] node
Running on gp-agent in /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
The recommended git tool is: NONE
using credential github-access
Fetching changes from the remote Git repository
Fetching without tags
Checking out Revision 58cd4b60dcc9413beca260ed4c601098ab04d2eb (acceptation)
Commit message: "switch to node form --lts"
 > git rev-parse --resolve-git-dir /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/.git # timeout=10
 > git config remote.origin.url https://github.com/HL-Abdallah/staff-manager-admin-ui-cloudsec.git # timeout=10
Fetching upstream changes from https://github.com/HL-Abdallah/staff-manager-admin-ui-cloudsec.git
 > git --version # timeout=10
 > git --version # 'git version 2.40.1'
using GIT_ASKPASS to set credentials 
 > git fetch --no-tags --force --progress -- https://github.com/HL-Abdallah/staff-manager-admin-ui-cloudsec.git +refs/heads/acceptation:refs/remotes/origin/acceptation # timeout=10
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 58cd4b60dcc9413beca260ed4c601098ab04d2eb # timeout=10
 > git rev-list --no-walk 5fa8c7de33f5f562f88479983a05899d360ec4eb # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Agent Setup)
[Pipeline] isUnix
[Pipeline] readFile
[Pipeline] sh
+ docker build -t d89fb2028932cbbd1bd5b845c31cdbc6219edd4c -f Dockerfile.agent .
Sending build context to Docker daemon  500.1MB

Step 1/9 : FROM jenkins/agent:latest
 ---> 7ae825327b31
Step 2/9 : USER root
 ---> Using cache
 ---> e4b66e958c34
Step 3/9 : RUN apt-get update &&     apt-get install -y npm docker awscli default-jdk &&     rm -rf /var/lib/apt/lists/*
 ---> Using cache
 ---> a8ee6e6ff6de
Step 4/9 : RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash     && . ~/.nvm/nvm.sh     && nvm install node     && node -e "console.log('Running Node.js ' + process.version)"
 ---> Running in 4d7be2cfef8e
[91m [0m[91m % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    [0m[91mL[0m[91me[0m[91mf[0m[91mt[0m[91m  Speed

  0     0    0    [0m[91m [0m[91m0[0m[91m    0     0      0      0 --:--:-- --:--:[0m[91m-- --:--:--     0[0m[91m
100 15916  100 15916    0     0  98857      0 --:--:-- --:--:-- --:--:-- 98857
[0m=> Downloading nvm from git to '/root/.nvm'

=> [91mCloning into '/root/.nvm'...
[0m* (HEAD detached at FETCH_HEAD)
  master
=> Compressing and cleaning up git repository

=> Appending nvm source string to /root/.bashrc
=> Appending bash_completion source string to /root/.bashrc
=> Close and reopen your terminal to start using nvm or run the following to use it now:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
Downloading and installing node v20.6.1...
[91mDownloading https://nodejs.org/dist/v20.6.1/node-v20.6.1-linux-x64.tar.xz...
[0m[91m
####################################[0m[91m                                      50.7%[0m[91m
##########[0m[91m###[0m[91m#[0m[91m##[0m[91m#[0m[91m#[0m[91m#[0m[91m#[0m[91m#[0m[91m################################################### [0m[91m100.0%
[0m[91mComputing checksum with sha256sum
[0m[91mChecksums matched!
[0mNow using node v20.6.1 (npm v9.8.1)
Creating default alias: default -> node (-> v20.6.1 *)
Running Node.js v20.6.1
Removing intermediate container 4d7be2cfef8e
 ---> 79b3a1d0adc5
Step 5/9 : RUN echo 'export NVM_DIR="$HOME/.nvm"' >> $HOME/.bashrc     && echo '[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"' >> $HOME/.bashrc
 ---> Running in d5c5907ade58
Removing intermediate container d5c5907ade58
 ---> 95c5e8081970
Step 6/9 : RUN . $HOME/.bashrc
 ---> Running in d3a90d73d2d4
nvm
Removing intermediate container d3a90d73d2d4
 ---> af3c6dc532dd
Step 7/9 : RUN mkdir -p /.npm
 ---> Running in 0fdf60936204
Removing intermediate container 0fdf60936204
 ---> 57945aa41a9f
Step 8/9 : RUN chown -R 1002:1002 /.npm
 ---> Running in a0cb6cfe91bf
Removing intermediate container a0cb6cfe91bf
 ---> 7a63cd0f10b1
Step 9/9 : USER 1002:1002
 ---> Running in 50723e1eb398
Removing intermediate container 50723e1eb398
 ---> 4fabe0bf14a4
Successfully built 4fabe0bf14a4
Successfully tagged d89fb2028932cbbd1bd5b845c31cdbc6219edd4c:latest
[Pipeline] }
[Pipeline] // stage
[Pipeline] isUnix
[Pipeline] withEnv
[Pipeline] {
[Pipeline] sh
+ docker inspect -f . d89fb2028932cbbd1bd5b845c31cdbc6219edd4c
.
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] withDockerContainer
gp-agent does not seem to be running inside a container
$ docker run -t -d -u 1002:1002 -w /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation -v /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation:/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation:rw,z -v /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation@tmp:/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** d89fb2028932cbbd1bd5b845c31cdbc6219edd4c cat
$ docker top 12defe4dd2ae7e0342482472c54957b43a2411e7d25cb517180fbd789eba55ea -eo pid,comm
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Build React App)
[Pipeline] script
[Pipeline] {
[Pipeline] sh
+ npm ci
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@csstools/[email protected]',
npm WARN EBADENGINE   required: { node: '^14 || >=16' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@faker-js/[email protected]',
npm WARN EBADENGINE   required: { node: '^14.17.0 || ^16.13.0 || >=18.0.0', npm: '>=6.14.13' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@mui/[email protected]',
npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@mui/[email protected]',
npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@remix-run/rout[email protected]',
npm WARN EBADENGINE   required: { node: '>=14' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=14' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=14' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=14' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=14' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.12', npm: '7.5.2' }
npm WARN EBADENGINE }
npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.
npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated @material-ui/[email protected]: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.
npm WARN deprecated @material-ui/[email protected]: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.

added 2135 packages in 2m

257 packages are looking for funding
  run `npm fund` for details
[Pipeline] sh
+ npm run build

> [email protected] build
> react-scripts build

internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module 'tapable'
Require stack:
- /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/enhanced-resolve/lib/Resolver.js
- /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/enhanced-resolve/lib/ResolverFactory.js
- /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/enhanced-resolve/lib/index.js
- /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/webpack/lib/CacheFacade.js
- /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/webpack/lib/Compilation.js
- /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/webpack/lib/NormalModule.js
- /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/webpack-manifest-plugin/dist/index.js
- /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/react-scripts/config/webpack.config.js
- /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/react-scripts/scripts/build.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/enhanced-resolve/lib/Resolver.js:8:60)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/enhanced-resolve/lib/Resolver.js',
    '/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/enhanced-resolve/lib/ResolverFactory.js',
    '/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/enhanced-resolve/lib/index.js',
    '/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/webpack/lib/CacheFacade.js',
    '/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/webpack/lib/Compilation.js',
    '/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/webpack/lib/NormalModule.js',
    '/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/webpack-manifest-plugin/dist/index.js',
    '/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/react-scripts/config/webpack.config.js',
    '/home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation/node_modules/react-scripts/scripts/build.js'
  ]
}
npm ERR! code 1
npm ERR! path /home/jenkins_khaled/jenkins/workspace/Admin_Frontend_React_acceptation
npm ERR! command failed
npm ERR! command sh -c react-scripts build

npm ERR! A complete log of this run can be found in:
npm ERR!     /.npm/_logs/2023-09-09T20_46_34_033Z-debug.log
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build Docker Image)
Stage "Build Docker Image" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Push to Registry)
Stage "Push to Registry" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
$ docker stop --time=1 12defe4dd2ae7e0342482472c54957b43a2411e7d25cb517180fbd789eba55ea
$ docker rm -f --volumes 12defe4dd2ae7e0342482472c54957b43a2411e7d25cb517180fbd789eba55ea
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1

GitHub has been notified of this commit’s build result

Finished: FAILURE

更多回答

优秀答案推荐

When you have multiple RUN commands in your Dockerfile, each of them is run in an independent process. So anything set in the environment of one RUN command is not persisted in the environment of next RUN command.

当你的Dockerfile中有多个RUN命令时，每个命令都在一个独立的进程中运行。因此，在一个RUN命令的环境中设置的任何内容都不会在下一个RUN命令的环境中持久化。

This is actually required because nvm sets the NODE_VERSION in the environment variable to determine the default version to use.

这实际上是必需的，因为NVM在环境变量中设置NODE_VERSION以确定要使用的默认版本。

There are a couple of ways to solve this:

有几种方法可以解决这个问题：

You can use a node version specific base image for your Dockerfile. That way, you wont even need nvm. Check out some of the images here: https://hub.docker.com/_/node/ (eg: 20-bullseye-slim)

You can use the ENV command to persist the environment variables that nvm uses, like NVM_DIR, NODE_PATH, NODE_VERSION and PATH.

# Create the directory to store nvm
RUN mkdir -p /usr/local/nvm

# export this env var
ENV NVM_DIR /usr/local/nvm

# set the node version you want here
ENV NODE_VERSION v20.6.1

# download nvm
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash

RUN /bin/bash -c "source $NVM_DIR/nvm.sh && nvm install $NODE_VERSION && nvm use --delete-prefix $NODE_VERSION"

# persist the paths that nvm normally does
ENV NODE_PATH $NVM_DIR/versions/node/$NODE_VERSION/bin
ENV PATH $NODE_PATH:$PATH

RUN node -v

Fixed by applying these changes to the Dockerfile.agent

已通过将这些更改应用于Dockerfile.agent修复

FROM jenkins/agent:latest

USER root

# Install stuff needed for building & deploying
RUN apt-get update && \
    apt-get install -y docker awscli default-jdk

RUN apt-get update && apt-get install -y \
    software-properties-common \
    npm
RUN npm install npm@latest -g && \
    npm install n -g && \
    n latest

# Add the commands to fix npm permissions
RUN mkdir -p /.npm
RUN chown -R 1002:1002 /.npm
USER 1002:1002

更多回答

文章推荐： Simple recursive descent parser(简单递归下降解析器)

Laravel 在完成 Job 后调度一个 Job 占用内存然后失败
我想做的是分派(dispatch)一个 Job，然后在前一个 Job 完成后继续分派(dispatch)同一个 Job，这样就可以连续循环分派(dispatch) Job。如选项一所示，这以前是与数据
sql - 当 JOB 执行的过程没有完成时，JOB 何时再次执行它时会发生什么？
我想知道当一个过程通过一个作业执行时会发生什么，在它完成之前是作业调用该过程的下一次执行的时间。这是我创建的工作: DECLARE X NUMBER; BEGIN SYS.DB
powershell - 将写入进度添加到 Get-Job/Wait-Job
我使用以下代码显示超时为 120 秒的 PowerShell 作业的结果。我想通过合并 Write-Progress(基于完成的作业数)来增强此代码。我尝试使用 this example然而，作为引用
powershell - 将写入进度添加到 Get-Job/Wait-Job
我使用以下代码显示超时为 120 秒的 PowerShell 作业的结果。我想通过合并 Write-Progress(基于完成的作业数)来增强此代码。我尝试使用 this example然而，作为引用
javascript - ECMAScript : Some questions about Job and Job queue
这个关于 ECMAScript 规范(ECMA-262 第 8 版)的问题这些天，我对作业和作业队列有点困惑。这里有一些问题。 1:在ECMA-262中，有两种作业队列。一个是 ScriptJob
c++ - 由 JOB 中的进程启动的子进程能否将 JOB 属性设置为脱离作业？
子进程是作业的一部分，由创建作业的进程启动。父进程尚未设置作业属性以允许脱离作业。需要在 JOB 上设置“JOB_OBJECT_LIMIT_BREAKAWAY_OK”标志以允许子进程脱离作业，但未设置
iOS job queue类似于Path的android priority job queue
有没有人有类似于Path's Android Priority Job Queue的iOS作业队列？他们不介意与社区分享？我是 iOS 的新手，所以我不确定平台本身是否提供这样的解决方案。在 Andr
Heroku 调度程序 : timed job OK but not for schedulee job
我正在关注 this在 Heroku 上安排我的 Django cron 作业。程序文件: web: gunicorn tango.wsgi --log-file - clock: python c
kotlin - “job + UI”上下文和使用 “parent = job”有什么区别？
UI协同程序指南包含有关如何管理UI协同程序生命周期的section。它说明了我们应该创建一个顶级Job实例，并将复合协程上下文contextJob + UI传递给我们启动的所有协程: launch(
java - 如何解决Spark流程序中的 "Error running job streaming job"？
我在 Spark 上创建了一个 Master 和一个 Worker。然后我创建了一个 Spark 流作业并尝试提交它，但在 Master 上它显示了一长串 java 错误使用此命令启动主控: spa
java - Spring 启动批处理: How to run job with job parameters
我必须在 Spring Batch 上设置 jobparemeters，但使用 Spring Boot Batch 则无法轻松做到这一点。我需要重新运行作业，但如果参数相同，spring-batch
hadoop - Pig 如何从第一个 Job 和它的下一个 Job 传递数据
众所周知，Apache Pig 是一种数据流语言。如果我编写了一个 Pig 脚本并且 Pig 决定拆分并运行两个或多个作业来执行手头的任务，那么 Pig 如何存储它从作业 1 传递到作业 2 的数据？
java - job.setOutputKeyClass 和 job.setOutputReduceClass 指的是哪里？
我以为他们指的是 Reducer 但在我的程序中我有 public static class MyMapper extends Mapper 和 public static class MyReduc
Spring 批处理 :Restart a job and then start next job automatically
我需要创建一个恢复模式。在我的模式中，我只能在给定的时间窗口内启 Action 业。如果作业失败，它只会在下一个时间窗口重新启动，完成后我想开始为此窗口提前计划的计划作业。作业之间的唯一区别是时
scala - 在 Play 框架中处于测试模式时禁用 play.jobs.Job 运行
使用 play 框架 1.2.4 和 scala。我几乎没有类似的游戏工作 @OnApplicationStart class MyOtherJob extends Job { ... } @Ev
sql-server - "When the Job Succeeds"和 "When the Job Completes"之间的区别
作业通知选项“作业成功时”和“作业完成时”有何区别。从表面上看，我假设“作业完成时”选项包含作业成功和作业失败，而“作业成功时”选项仅包含作业成功运行时。这是正确的吗？最佳答案作业成功时作业成功完
版本 "v1"中的 kubernetes Job 无法作为 Job : 处理
我正在尝试创建迁移，但由于以下错误而失败: Error from server (BadRequest): error when creating "kubernetes/migration-job.
java - Cron Job 和 Hybris 中的 Job 的区别
Cron Job 和 hybris 中的 Job 有什么区别？两者的创建/实现之间有什么区别？最佳答案下图描述了 Hybris 中 Jobs/Cronjobs 工作原理的完整 View
java - Spring 批处理 : How to set up a job repository for every job
我正在运行多个作业，并且我希望每个作业都有一个单独的作业存储库(内存中实现)。请在下面找到我尝试过的 bean 定义。请注意，我尝试指定具有作用域原型(prototype)的 bean。我收到 j
java - quartz : How to remove a set of jobs when another job is started?
Quartz 中是否有一种机制可以在启动另一个作业时删除现有作业？我需要暂停其他作业的原因是因为新作业需要所有资源可用，只有当其他作业未运行时才会如此。这是一个示例: 我有 2 份工作:工作 A 和

bug小助手

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城