在jenkins中使用maven编译报错:程序包com.sun.deploy.util不存在

最新推荐文章于 2024-04-30 22:52:08 发布
原创 最新推荐文章于 2024-04-30 22:52:08 发布 · 1w 阅读 · 7 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#jenkins #StringUtils

本文解决在使用StringUtils.join方法时遇到的程序包com.sun.deploy.util不存在的问题。建议引入commons-lang3库，具体版本为3.9，以确保StringUtils方法的正确运行。 
使用StringUtils.join时报程序包com.sun.deploy.util不存在,此时请使用包
<dependency>
    <groupId>org.apache.commons</groupId>
    <artifactId>commons-lang3</artifactId>
    <version>3.9</version>
</dependency>

里的StringUtils方法

nanjizhiyin
关注
Jenkins升级启动报错
Bertram的博客
02-26 978
Jenkins升级启动报错
Centos7下搭建Jenkins+GitLab+Maven 实现代码自动打包编译发布
qq_24442273的博客
10-18 2291
基于Jenkins+GitLab+Maven 实现代码自动打包、编译、发布的自动化持续集成相关硬核干货。全文内容包含Jenkins、Gitlab、Git、Maven、JDK、Tomcat等全套环境搭建、以及相关组件配置、IDEA中创建代码演示、Jenkins跑通全套自动化持续集成案例
程序包com.sun.deploy.net不存在
weixin_70215297的博客
04-28 1360
程序包com.sun.deploy.net不存在
关于maven打包 “程序包com.sun.deploy.net不存在” 的问题
2301_79779756的博客
04-30 3445
Maven是一个流行的Java项目管理和构建自动化工具，它使用项目对象模型（POM）的概念来管理项目的构建、依赖和文档。然而，在使用Maven进行项目打包时，有时可能会遇到特定的错误，例如“程序包com.sun.deploy.net不存在”的错误。这个错误通常表明Maven项目试图编译或使用了一个不存在的Java包或类。
Maven打包程序出现 程序包com.sun.*包不存在处理
枫叶
02-17 3472
开发中碰到的，就记录下来了，加上就可以打包了，原因是因为这个包在maven下是没有的，是存在于java下的。
maven打包出错：程序包com.sun.deploy.net不存在
qq_43734039的博客
02-02 7962
今天将写好的springboot项目通过本地方式打包发现了这个错误 然后去对应的java文件中查看发现com.sun.deploy.net这个包是不需要。因为之前使用idea编译的，我将自动导包打开了，idea将不需要的包导入了进来。 所以我将这个import去掉就可正常打包了！ ...
centos8搭建maven私服（含nexus-3.28.1-01.tar.gz下载链接）
weixin_44798288的博客
12-23 3117
centos8搭建maven私服简介mavenmaven私服仓库简介Nexus仓库类型介绍私服搭建环境安装nexus创建目录下载拷贝压缩文件至/usr/local目录下解压创建用户修改属组和属主配置环境变量启动验证Repositories介绍私服配置指定本地仓库配置私服镜像地址配置阿里镜像地址配置认证信息配置profile配置activeProfile在项目中的使用获取依赖包发布包加入systemctl管理并设置开机自启动将nexus加入systemctl管理创建nexus.service服务文件重新加载服
Jenkins+Maven+Gitlab+Tomcat 自动化构建打包、部署
宇博士的博客
11-23 1975
这里的username与password需要到tomcat的conf文件夹中的tomcat-users.xml修改。tomcat URL就是你希望把war包部署到的tomcat所在IP地址，最后面不需要再加斜杠/。tomcat-users.xml中的用户名及密码默认是注释掉的，所以需要修改，也可以直接复制以下代码到之前。WAR/EAR files：输入war包的相对路径，如我的war包在新建目录的target下。② 轮询 SCM：*/2 * * * * ，每隔2分钟检查一次。
2025-09-12 03:59:46.390+0000 [id=63] INFO jenkins.InitReactorRunner$1#onAttained: System config adapted 2025-09-12 03:59:46.403+0000 [id=47] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 2025-09-12 03:59:46.411+0000 [id=76] INFO jenkins.InitReactorRunner$1#onAttained: Configuration for all jobs updated 2025-09-12 03:59:46.427+0000 [id=53] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 2025-09-12 03:59:46.473+0000 [id=36] INFO hudson.lifecycle.Lifecycle#onReady: Jenkins is fully up and running 2025-09-12 06:23:41.833+0000 [id=882] WARNING hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 147b3c82bca9ebd1fa602daaf99e15931ab6f23e4863689a02a1634c924c7fef. If you are calling this URL with a script, please use the API Token instead. More information: https://www.jenkins.io/redirect/crumb-cannot-be-used-for-script 2025-09-12 06:23:41.834+0000 [id=882] WARNING hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for /view/%E5%87%AF%E5%88%A9/job/%E6%8C%87%E6%8C%A5%E5%A4%A7%E5%B1%8Fapi-pipeline/descriptorByName/org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition/checkScriptCompile by admin. Returning 403. 2025-09-12 09:21:05.113+0000 [id=2548] WARNING j.p.p.BapSshClient#waitForExec: null java.lang.InterruptedException at java.base/java.lang.Object.wait(Native Method) at java.base/java.lang.Thread.join(Unknown Source) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.waitForExec(BapSshClient.java:567) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.exec(BapSshClient.java:481) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.endTransfers(BapSshClient.java:242) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.endTransfers(BapSshClient.java:51) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher$Performer.endTransfers(BapPublisher.java:283) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher$Performer.perform(BapPublisher.java:233) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher$Performer.access$000(BapPublisher.java:205) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher.perform(BapPublisher.java:158) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:65) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:38) at hudson.FilePath.act(FilePath.java:1210) at hudson.FilePath.act(FilePath.java:1193) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPInstanceConfig.perform(BPInstanceConfig.java:141) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPPlugin.perform(BPPlugin.java:126) at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123) at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:101) at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71) at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:49) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) 2025-09-12 09:21:05.113+0000 [id=2640] WARNING j.p.p.BapSshClient$ExecCheckThread#run: sleep interrupted java.lang.InterruptedException: sleep interrupted at java.base/java.lang.Thread.sleep(Native Method) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient$ExecCheckThread.run(BapSshClient.java:592) 2025-09-12 09:21:05.114+0000 [id=2548] WARNING j.p.p.BPCallablePublisher#invoke: Exception when publishing, exception message [Exec timed out or was interrupted after 64,625 ms] jenkins.plugins.publish_over.BapPublisherException: Exec timed out or was interrupted after 64,625 ms at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.waitForExec(BapSshClient.java:577) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.exec(BapSshClient.java:481) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.endTransfers(BapSshClient.java:242) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.endTransfers(BapSshClient.java:51) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher$Performer.endTransfers(BapPublisher.java:283) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher$Performer.perform(BapPublisher.java:233) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher$Performer.access$000(BapPublisher.java:205) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher.perform(BapPublisher.java:158) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:65) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:38) at hudson.FilePath.act(FilePath.java:1210) at hudson.FilePath.act(FilePath.java:1193) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPInstanceConfig.perform(BPInstanceConfig.java:141) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPPlugin.perform(BPPlugin.java:126) at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123) at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:101) at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71) at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:49) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) 2025-09-12 09:21:05.115+0000 [id=2548] WARNING j.p.p.BPInstanceConfig#perform: An exception was caught when invoking perform jenkins.plugins.publish_over.BapPublisherException: Exec timed out or was interrupted after 64,625 ms at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.waitForExec(BapSshClient.java:577) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.exec(BapSshClient.java:481) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.endTransfers(BapSshClient.java:242) at PluginClassLoader for publish-over-ssh//jenkins.plugins.publish_over_ssh.BapSshClient.endTransfers(BapSshClient.java:51) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher$Performer.endTransfers(BapPublisher.java:283) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher$Performer.perform(BapPublisher.java:233) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher$Performer.access$000(BapPublisher.java:205) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BapPublisher.perform(BapPublisher.java:158) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:65) Caused: jenkins.plugins.publish_over.BapPublisherException: Exception when publishing, exception message [Exec timed out or was interrupted after 64,625 ms] at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:69) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:38) at hudson.FilePath.act(FilePath.java:1210) at hudson.FilePath.act(FilePath.java:1193) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPInstanceConfig.perform(BPInstanceConfig.java:141) at PluginClassLoader for publish-over//jenkins.plugins.publish_over.BPPlugin.perform(BPPlugin.java:126) at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123) at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:101) at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71) at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:49) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007604e4b3ec9f, pid=7, tid=170 # # JRE version: OpenJDK Runtime Environment Temurin-17.0.16+8 (17.0.16+8) (build 17.0.16+8) # Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.16+8 (17.0.16+8, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64) # Problematic frame: # V [libjvm.so+0x83dc9f] java_lang_Throwable::fill_in_stack_trace(Handle, methodHandle const&, JavaThread*)+0x95f # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -F%F -- %E" (or dumping to //core.7) # # An error report file with more information is saved as: # /tmp/hs_err_pid7.log # # If you would like to submit a bug report, please visit: # https://github.com/adoptium/adoptium-support/issues # Running from: /usr/share/jenkins/jenkins.war webroot: /var/jenkins_home/war 2025-09-12 09:22:52.973+0000 [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file 2025-09-12 09:22:53.005+0000 [id=1] WARNING o.e.j.ee9.nested.ContextHandler#setContextPath: Empty contextPath 2025-09-12 09:22:53.025+0000 [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-12.0.22; built: 2025-06-02T15:25:31.946Z; git: 335c9ab44a5591f0ea941bf350e139b8c4f5537c; jvm 17.0.16+8 2025-09-12 09:22:53.151+0000 [id=1] INFO o.e.j.e.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.ee9.jsp.JettyJspServlet 2025-09-12 09:22:53.168+0000 [id=1] INFO o.e.j.s.DefaultSessionIdManager#doStart: Session workerName=node0 2025-09-12 09:22:53.313+0000 [id=1] INFO hudson.WebAppMain#contextInitialized: Jenkins home directory: /var/jenkins_home found at: EnvVars.masterEnvVars.get("JENKINS_HOME") 2025-09-12 09:22:53.347+0000 [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started oeje9n.ContextHandler$CoreContextHandler@1813f3e9{Jenkins v2.516.2,/,b=file:///var/jenkins_home/war/,a=AVAILABLE,h=oeje9n.ContextHandler$CoreContextHandler$CoreToNestedHandler@28cb9120{STARTED}} 2025-09-12 09:22:53.353+0000 [id=1] INFO o.e.j.server.AbstractConnector#doStart: Started ServerConnector@72458efc{HTTP/1.1, (http/1.1)}{0.0.0.0:8080} 2025-09-12 09:22:53.357+0000 [id=1] INFO org.eclipse.jetty.server.Server#doStart: Started oejs.Server@b9b00e0{STARTING}[12.0.22,sto=0] @603ms 2025-09-12 09:22:53.357+0000 [id=43] INFO winstone.Logger#logInternal: Winstone Servlet Engine running: controlPort=disabled 2025-09-12 09:22:53.400+0000 [id=36] INFO jenkins.model.Jenkins#<init>: Starting version 2.516.2 2025-09-12 09:22:53.430+0000 [id=50] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 2025-09-12 09:22:53.490+0000 [id=79] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 2025-09-12 09:22:54.524+0000 [id=108] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 2025-09-12 09:22:54.531+0000 [id=65] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins 2025-09-12 09:22:54.532+0000 [id=65] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions 2025-09-12 09:22:54.725+0000 [id=27] INFO h.p.b.g.GlobalTimeOutConfiguration#load: global timeout not set 2025-09-12 09:22:55.091+0000 [id=94] INFO jenkins.InitReactorRunner$1#onAttained: System config loaded 2025-09-12 09:22:55.092+0000 [id=50] INFO jenkins.InitReactorRunner$1#onAttained: System config adapted 2025-09-12 09:22:55.114+0000 [id=95] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 2025-09-12 09:22:55.115+0000 [id=69] INFO jenkins.InitReactorRunner$1#onAttained: Configuration for all jobs updated 2025-09-12 09:22:55.139+0000 [id=83] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 2025-09-12 09:22:55.204+0000 [id=36] INFO hudson.lifecycle.Lifecycle#onReady: Jenkins is fully up and running
最新发布
09-13
- 限制并行任务数量（例如在`Jenkinsfile`中使用`lock`或`semaphore`）。 4. **检查节点连接**：确保Agent节点网络稳定，避免断开。 ### 三、执行超时异常（如`java.net.ConnectException: Connection timed out`...
deploy.jar 第三方jar包
02-18
deploy 部署 不是很常用的jar包，希望对大家有点帮助
java: 程序包sun.net.util不存在
qq_34486648的博客
03-15 2483
common module jdk版本导致的问题。
关于maven打包 程序包com.sun.deploy.net不存在 解决方法
qq_35862393的博客
06-21 1315
【代码】关于maven打包 程序包com.sun.deploy.net不存在 解决方法。
Jenkins打包Maven项目时提示程序包不存在
老刀
05-27 6020
公司小伙开发遇到一个问题，项目代码在本地eclipse中编译、启动没有问题，使用jenkins打包时却报找不到程序包： 第一反应是看nexus私服是否有问题，检查了一下，没有问题，控制台没有提示download错误。 打开eclipse去看该项目的项目依赖，发现引用的这个包是在某个被引用的功能中作为runtime作用域引用的。 so，在当前项目pom中增加了对该jar包的依赖，重新打包，搞定! ...
“程序包com.sun.tools.javac.util不存在” 问题解决
CarfLearningCode
08-09 3788
所以该包位置在：/Library/Java/JavaVirtualMachines/jdk1.8.0_331.jdk/Contents/Home/lib 路径下的tools.jar中，只要将jar包放入到项目环境中即可解决该问题。com.sun.tools.javac.util 该包是jdk中自带的，位置在jdk安装路径下的lib文件里：本人的是Mac环境，...
jekins/maven打包:程序包com.sun.deploy.net不存在
weixin_44443569的博客
03-02 1283
jekins里面的报错信息 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project user-service: Compilation failure: Compilation failure: [ERROR] /var/lib/jenkins/workspace/basics-service/user-service/s
程序包com.sun.deploy.net不存在的解决方法
m0_68700019的博客
11-03 2027
打包时，程序包com.sun.deploy.net不存在的解决方法
Maven编译项目显示 程序包com.sun.*包不存在 【原因及三种解决方案】
热门推荐
am_Sun的博客
05-27 5万+
maven 编译时报错： [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin: 程序包com.sun.…… 不存在 程序包com.sun.xml.internal.ws.spi不存在 【官方解释】：javac uses a special symbol table that does not include all Sun-proprietary classes.When javac is comp.
jenkins编译项目报错Caused by: hudson.remoting.ProxyException: java.lang.reflect.InvocationTargetException
01-07
### 解决Jenkins编译过程中的`hudson.remoting.ProxyException: java.lang.reflect.InvocationTargetException`错误 当遇到`hudson.remoting.ProxyException: java.lang.reflect.InvocationTargetException`这类异常时，通常意味着远程调用过程中发生了未预期的情况。此类问题可能由多种因素引起，包括但不限于环境配置不当、依赖库版本冲突或是特定工具链之间的兼容性问题。 #### 检查Jenkins及其插件版本 确保使用的Jenkins版本是最新的稳定版之一。旧版本可能存在已知缺陷或与当前软件生态系统的兼容性问题。对于提及的具体情况，建议升级至更高版本的Jenkins以获得更好的支持和稳定性[^1]。 #### 更新Maven版本 如果项目构建涉及Maven，则应确认所使用的Maven版本是否适合该项目的要求。有时降低或提升Maven版本可以绕过一些潜在的问题。例如，从较高版本回退到较低版本可能会解决问题，正如之前的经验所示，调整Maven版本确实帮助解决了某些情况下出现的问题[^2]。 #### 审视代码变更历史记录 仔细审查最近提交的历史记录，特别是那些引入新功能或重构现有逻辑的部分。任何破坏性的更改都可能是触发此异常的原因所在。重点检查是否有对类加载器进行了操作或者是反射机制的应用场景。 #### 调整Java虚拟机参数 适当调节启动Jenkins服务时传递给Java虚拟机(JVM)的相关选项也可能有助于缓解该问题。比如增加堆内存大小(-Xmx)，启用更多的垃圾回收日志输出等措施可以帮助诊断根本原因。 #### 启用详细的调试信息 为了更深入地了解发生的位置以及上下文条件，在Jenkins的日志级别设置中开启DEBUG模式能够提供额外的信息用于分析。这一步骤往往能揭示更多关于失败背后的故事线索。 ```bash java -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog \ -Dorg.apache.commons.logging.simplelog.showdatetime=true \ -Dorg.apache.commons.logging.simplelog.log.org.jenkinsci.plugins.git.traits=debug \ -jar jenkins.war ```
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值