[JIRA] (JENKINS-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title yuan kang updated an issue Jenkins / JENKINS-53780 jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins Change By: yuan kang Labels: jira- plugin -3.0.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53812) jenkins pipeline maven build error when workspace contain Chinese characters
Title: Message Title yuan kang edited a comment on JENKINS-53812 Re: jenkins pipeline maven build error when workspace contain Chinese characters May be the pipeline job workspace should not Chinese character. If the job worksapce contains Chinese characters , the maven build was failed . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53812) jenkins pipeline maven build error when workspace contain Chinese characters
Title: Message Title yuan kang updated an issue Jenkins / JENKINS-53812 jenkins pipeline maven build error when workspace contain Chinese characters Change By: yuan kang Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53812) jenkins pipeline maven build error when workspace contain Chinese characters
Title: Message Title yuan kang commented on JENKINS-53812 Re: jenkins pipeline maven build error when workspace contain Chinese characters May be the pipeline job workspace should not Chinese character. If the job worksapce contains Chinese characters , the maven build was failed . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53812) jenkins pipeline maven build error when workspace contain Chinese characters
Title: Message Title
yuan kang updated an issue
Jenkins / JENKINS-53812
jenkins pipeline maven build error when workspace contain Chinese characters
Change By:
yuan kang
Use maven build java project ,I am sure there is a pom.xml file in this diectory , but I get error : [Pipeline] withMaven[withMaven] Options: [] [withMaven] Available options: [withMaven] using JDK installation JDK-1.8 [withMaven] using Maven installation 'maven-3.3.9'[Pipeline]{[Pipeline] sh[pipeline_job_for_SCM] Running shell script + mvn clean package - withMaven Wrapper script - Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/data/.jenkins/workspace/.../pipeline_job_for_test_env/pipeline_job_for_SCM@tmp/withMavena780b9e4/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/data/.jenkins/workspace/.../pipeline_job_for_test_env/pipeline_job_for_SCM@tmp/withMavena780b9e4" Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T00:41:47+08:00) Maven home: /opt/module/maven Java version: 1.8.0_101, vendor: Oracle Corporation Java home: /usr/java/jdk1.8.0_101/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux", version: "2.6.32-431.el6.x86_64", arch: "amd64", family: "unix"[WARNING][WARNING] Some problems were encountered while building the effective settings[WARNING] Unrecognised tag: 'enabled' (position: START_TAG seen ... \n ... @71:18) @ /root/.m2/settings.xml, line 71, column 18[WARNING][INFO] Scanning for projects...[INFO] [INFO] BUILD FAILURE[INFO] [INFO] Total time: 0.187 s[INFO] Finished at: 2018-09-27T17:19:15+08:00[INFO] Final Memory: 16M/966M[INFO] [WARNING] The requested profile "downloadSources" could not be activated because it does not exist.[ERROR] {color:#de350b}The goal you specified requires a project to execute but there is no POM in this directory{color} ( {color:#de350b} /data/.jenkins/workspace/???/pipeline_job_for_test_env/pipeline_job_for_SCM {color} ). Please verify you invoked Maven from the correct directory. ->[Help 1][ERROR][ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR][ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] [http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException][Pipeline] }
[JIRA] (JENKINS-53812) jenkins pipeline maven build error when workspace contain Chinese characters
Title: Message Title yuan kang updated an issue Jenkins / JENKINS-53812 jenkins pipeline maven build error when workspace contain Chinese characters Change By: yuan kang Summary: jenkins pipeline use maven build project error "The goal you specified requires a project to execute but there is no POM in this directory " when workspace contain Chinese characters Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53812) jenkins pipeline use maven build project error "The goal you specified requires a project to execute but there is no POM in this directory "
Title: Message Title
yuan kang updated an issue
Jenkins / JENKINS-53812
jenkins pipeline use maven build project error "The goal you specified requires a project to execute but there is no POM in this directory "
Change By:
yuan kang
Use maven build java project , and I am sure there is a pom.xml file in this diectory , but I get error : [Pipeline] withMaven[withMaven] Options: [] [withMaven] Available options: [withMaven] using JDK installation JDK-1.8 [withMaven] using Maven installation 'maven-3.3.9' [Pipeline]{[Pipeline] sh[pipeline_job_for_SCM] Running shell script + mvn clean package - withMaven Wrapper script - Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/data/.jenkins/workspace/ 配管（配置管理）部署工作区 ... /pipeline_job_for_test_env/pipeline_job_for_SCM@tmp/withMavena780b9e4/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/data/.jenkins/workspace/ 配管（配置管理）部署工作区 ... /pipeline_job_for_test_env/pipeline_job_for_SCM@tmp/withMavena780b9e4" Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T00:41:47+08:00) Maven home: /opt/module/maven Java version: 1.8.0_101, vendor: Oracle Corporation Java home: /usr/java/jdk1.8.0_101/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux", version: "2.6.32-431.el6.x86_64", arch: "amd64", family: "unix" [WARNING] [WARNING] Some problems were encountered while building the effective settings [WARNING] Unrecognised tag: 'enabled' (position: START_TAG seen ... \n ... @71:18) @ /root/.m2/settings.xml, line 71, column 18 [WARNING] [INFO] Scanning for projects... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.187 s [INFO] Finished at: 2018-09-27T17:19:15+08:00 [INFO] Final Memory: 16M/966M [INFO] [WARNING] The requested profile "downloadSources" could not be activated because it does not exist. [ERROR] {color:#de350b}The goal you specified requires a project to execute but there is no POM in this directory{color} (/data/.jenkins/workspace/???/pipeline_job_for_test_env/pipeline_job_for_SCM). Please verify you invoked Maven from the correct directory. -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] [http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException][Pipeline] }
[JIRA] (JENKINS-53812) jenkins pipeline use maven build project error "The goal you specified requires a project to execute but there is no POM in this directory "
Title: Message Title
yuan kang updated an issue
Jenkins / JENKINS-53812
jenkins pipeline use maven build project error "The goal you specified requires a project to execute but there is no POM in this directory "
Change By:
yuan kang
Use maven build project , and get error :[Pipeline] withMaven[withMaven] Options: [][withMaven] Available options: [withMaven] using JDK installation JDK-1.8[withMaven] using Maven installation 'maven-3.3.9'[Pipeline] {[Pipeline] sh[pipeline_job_for_SCM] Running shell script + mvn clean package - withMaven Wrapper script - Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/data/.jenkins/workspace/配管（配置管理）部署工作区/pipeline_job_for_test_env/pipeline_job_for_SCM@tmp/withMavena780b9e4/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/data/.jenkins/workspace/配管（配置管理）部署工作区/pipeline_job_for_test_env/pipeline_job_for_SCM@tmp/withMavena780b9e4" Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T00:41:47+08:00) Maven home: /opt/module/maven Java version: 1.8.0_101, vendor: Oracle Corporation Java home: /usr/java/jdk1.8.0_101/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux", version: "2.6.32-431.el6.x86_64", arch: "amd64", family: "unix"[WARNING] [WARNING] Some problems were encountered while building the effective settings[WARNING] Unrecognised tag: 'enabled' (position: START_TAG seen ... \n... @71:18) @ /root/.m2/settings.xml, line 71, column 18[WARNING] [INFO] Scanning for projects... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.187 s [INFO] Finished at: 2018-09-27T17:19:15+08:00 [INFO] Final Memory: 16M/966M [INFO] [WARNING] The requested profile "downloadSources" could not be activated because it does not exist.[ERROR] {color:#de350b} The goal you specified requires a project to execute but there is no POM in this directory {color} (/data/.jenkins/workspace/???/pipeline_job_for_test_env/pipeline_job_for_SCM). Please verify you invoked Maven from the correct directory. -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] [http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException][Pipeline] }
[JIRA] (JENKINS-53812) jenkins pipeline use maven build project error "The goal you specified requires a project to execute but there is no POM in this directory "
Title: Message Title
yuan kang created an issue
Jenkins / JENKINS-53812
jenkins pipeline use maven build project error "The goal you specified requires a project to execute but there is no POM in this directory "
Issue Type:
Bug
Assignee:
Unassigned
Components:
maven-plugin, pipeline
Created:
2018-09-27 10:20
Environment:
jenkins version 2.90 maven version 3.3.9 linux version 2.6.32-431.el6.x86_64
Priority:
Major
Reporter:
yuan kang
Use maven build project , and get error : [Pipeline] withMaven[withMaven] Options: [] [withMaven] Available options: [withMaven] using JDK installation JDK-1.8 [withMaven] using Maven installation 'maven-3.3.9'[Pipeline] {[Pipeline] sh[pipeline_job_for_SCM] Running shell script + mvn clean package - withMaven Wrapper script - Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/data/.jenkins/workspace/配管（配置管理）部署工作区/pipeline_job_for_test_env/pipeline_job_for_SCM@tmp/withMavena780b9e4/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/data/.jenkins/workspace/配管（配置管理）部署工作区/pipeline_job_for_test_env/pipeline_job_for_SCM@tmp/withMavena780b9e4" Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T00:41:47+08:00) Maven home: /opt/module/maven Java version: 1.8.0_101, vendor: Oracle Corporation Java home: /usr/java/jdk1.8.0_101/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux", version: "2.6.32-431.el6.x86_64", arch: "amd64", family: "unix"[WARNING] [WARNING] Some problems were encountered while building the effective settings[WARNING] Unrecognised tag: 'enabled' (position: START_TAG seen ... \n ... @71:18) @ /root/.m2/settings.xml, line 71, column 18[WARNING] [INFO] Scanning for projects... [INFO]
[JIRA] (JENKINS-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title yuan kang updated an issue Jenkins / JENKINS-53780 jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins Change By: yuan kang Environment: centos 6.8、 jenkins 2.90 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title yuan kang commented on JENKINS-53780 Re: jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins After jenkins restart , Jira issue comment add trigger jenkins job works well ,but Jira issue update trigger jenkins job do not work. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title yuan kang updated an issue Jenkins / JENKINS-53780 jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins Change By: yuan kang I install jira-plugin and integrate with Jira ,it's works well ,but when I restart jenkins ,I got following errors: Failed to instantiate Key[type=hudson.plugins.jira.JiraProjectProperty$DescriptorImpl, annotation=@com.google.inject.name.Named(value=hudson.plugins.jira.JiraProjectProperty.DESCRIPTOR)]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors:1) Tried proxying hudson.plugins.jira.JiraProjectProperty$DescriptorImpl to support a circular dependency, but it is not an interface.1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:482) at hudson.ExtensionList.load(ExtensionList.java:366) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:304) at hudson.ExtensionList.iterator(ExtensionList.java:158) at jenkins.model.Jenkins.getDescriptor(Jenkins.java:1497) at jenkins.model.Jenkins.getDescriptorOrDie(Jenkins.java:1511) at hudson.model.AbstractDescribableImpl.getDescriptor(AbstractDescribableImpl.java:42) at com.cloudbees.plugins.credentials.CredentialsProviderTypeRestriction.getDescriptor(CredentialsProviderTypeRestriction.java:71) at com.cloudbees.plugins.credentials.CredentialsProviderManager.restrictions(CredentialsProviderManager.java:332) at com.cloudbees.plugins.credentials.CredentialsProviderManager.filter(CredentialsProviderManager.java:145) at com.cloudbees.plugins.credentials.CredentialsProvider.isEnabled(CredentialsProvider.java:1050) at com.cloudbees.plugins.credentials.CredentialsProvider.lookupCredentials(CredentialsProvider.java:411) at hudson.plugins.jira.CredentialsHelper.migrateCredentials(CredentialsHelper.java:50) at hudson.plugins.jira.JiraSite.(JiraSite.java:221) at hudson.plugins.jira.JiraSite.readResolve(JiraSite.java:304) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at
[JIRA] (JENKINS-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title yuan kang created an issue Jenkins / JENKINS-53780 jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2018-09-26 07:48 Environment: centos 6.8、jenkins 2.90 Labels: plugin Priority: Major Reporter: yuan kang I install jira-plugin and integrate with Jira ,it's works well ,but when I restart jenkins ,I got following errors: annotation=@com.google.inject.name.Named(value=hudson.plugins.jira.JiraProjectProperty.DESCRIPTOR)]; skipping this component com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Tried proxying hudson.plugins.jira.JiraProjectProperty$DescriptorImpl to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at
