[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Pietro Pepe assigned an issue to Unassigned Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Pietro Pepe Assignee: Pietro Pepe 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.7530.1561392840168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Pietro Pepe assigned an issue to Pietro Pepe Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Pietro Pepe Assignee: Pietro Pepe 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.7527.1561392720364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Pietro Pepe commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Also in our infrastructure we get the same issue using BlueOcean 1.17.0 (on Jenkins 2.176.1) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.7525.1561392720314%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56829) Wrong basedir calculation during Jenkins maven build with jaxb2-maven-plugin
Title: Message Title Pietro Pepe commented on JENKINS-56829 Re: Wrong basedir calculation during Jenkins maven build with jaxb2-maven-plugin The issue seems to be related to these: https://github.com/mojohaus/jaxb2-maven-plugin/issues/5 https://stackoverflow.com/questions/30834601/using-xjb-with-jaxb2-maven-plugin 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-56829) Wrong basedir calculation during Jenkins maven build with jaxb2-maven-plugin
Title: Message Title
Pietro Pepe updated an issue
Jenkins / JENKINS-56829
Wrong basedir calculation during Jenkins maven build with jaxb2-maven-plugin
Change By:
Pietro Pepe
Hi,We experienced a strange behavior during a maven build using a Jenkins Maven Job where the basedir path is not correctly calculated.The Jenkins infrastructure is distrubuited and the slave is a linux virtual machine. In particular we have a super pom that invoke a lot of sub poms and one of this has the following configuration related to the {color:#33}*jaxb2-maven-plugin* {color} {code:java}// code placeholderjaxb2-maven-plugin 2.4 generate-sources xjc xjc com.company.flow.customview src/main/resources/xsd {code} {color:#33}the error with {color:#172b4d} {color}*{color:#33}jaxb2-maven-plugin:2.4{color}* is the following: {color} {code:java}// [INFO] --- jaxb2-maven-plugin:2.4:xjc (xjc) @ com.company.flow.customview --- [INFO] Created EpisodePath [/home/jenkins/workspace/DEV/flow/DEV/01-SRV/flow-cf-bl/Baseline/services/com.company.flow.customview/target/generated-sources/jaxb/META-INF/JAXB]: true [INFO] Ignored given or default xjbSources [/home/jenkins/workspace/DEV/flow/DEV/01-SRV/flow-cf-bl/Baseline/services/com.company.flow.customview/src/main/xjb], since it is not an existent file or directory. [INFO] Created EpisodePath [/home/jenkins/workspace/DEV/flow/DEV/01-SRV/flow-cf-bl/Baseline/services/com.company.flow.customview/target/generated-sources/jaxb/META-INF/JAXB]: true [ERROR] null [-1,-1] org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'file:/home/jenkins/workspace/DEV/flow/DEV/01-SRV/flow-cf-bl/Baseline/services/com.company.flow/.customview/src/main/resources/xsd/CustomViewDefinition.xsd',{code} using {color:#33} * {color:#33} jaxb2-maven-plugin:2.3.1 {color} * the error is {color} {code:java}// [INFO] --- jaxb2-maven-plugin:2.3.1:xjc (xjc) @ com.company.flow.customview --- [INFO] Created EpisodePath [/home/jenkins/workspace/DEV/flow/DEV/01-SRV/flow-cf-bl/Baseline/services/com.company.flow.customview/target/generated-sources/jaxb/META-INF/JAXB]: true [INFO] Ignored given or default xjbSources [/home/jenkins/workspace/DEV/flow/DEV/01-SRV/flow-cf-bl/Baseline/services/com.company.flow.customview/src/main/xjb], since it is not an existent file or directory. [ERROR] null [-1,-1] org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'file:/home/jenkins/workspace/DEV/flow/DEV/01-SRV/flow-cf-bl/Baseline/services/com.company.flow/customview/src/main/resources/xsd/CustomViewDefinition.xsd',{code} {color:#33} If we run the maven build locally everithing works without issues.Can you help up us ? {color} {color:#33}Thank you.{color}
[JIRA] (JENKINS-56829) Wrong basedir calculation during Jenkins maven build with jaxb2-maven-plugin
Title: Message Title Pietro Pepe created an issue Jenkins / JENKINS-56829 Wrong basedir calculation during Jenkins maven build with jaxb2-maven-plugin Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2019-04-01 08:19 Environment: jenkins docker version 2.164.1 Jenkins Maven plugin 1.23 Maven toolchain version 3.5.2 Maven toolchain version 3.6.0 jaxb2-maven-plugin 2.3.1 and 2.4 Labels: plugin jenkins maven-plugin maven jaxb2 Priority: Major Reporter: Pietro Pepe Hi, We experienced a strange behavior during a maven build using a Jenkins Maven Job where the basedir path is not correctly calculated. The Jenkins infrastructure is distrubuited and the slave is a linux virtual machine. In particular we have a super pom that invoke a lot of sub poms and one of this has the following configuration related to the jaxb2-maven-plugin // code placeholder jaxb2-maven-plugin 2.4 generate-sources xjc xjc com.company.flow.customview src/main/resources/xsd the error with jaxb2-maven-plugin:2.4 is the following:
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Pietro Pepe commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Currently I'm experiencing this issue on Jenkins 2.150.1 and plugin version 5.142.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.
