[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Tomasz Śniatowski commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines So with pipelines, what is the recommended way of completely stopping a busy Jenkins instance for maintenance? The maintenance is in part due to a broken pipeline resume a'la JENKINS-50199, so I specifically don't want any additional half-done pipelines waiting to be resumed. I also would prefer to avoid having to abort jobs. In JENKINS-38316 there's an explicit mention that "prepare for shutdown" is not that: The whole idea of "Prepare for shutdown" is to [...] allow you to finish currently running freestyle (Maven, matrix, …) builds. So if you /safeRestart Jenkins will restart as soon as any of those are completed, and running Pipeline builds will be left alone. What should I do then? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Cyrille Le Clerc commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Ulli Hafner can you please help us understand why analysis-core is pulling xercesImpl-2.11 that seem to cause problems with JVM's built-in XML parser on Java 8? The only usage I found of xerces code in analysis-core is the SaxSetup.java class that has been deprecated in 2016. https://github.com/jenkinsci/analysis-core-plugin/blob/analysis-core-1.95/src/main/java/hudson/plugins/analysis/util/SaxSetup.java The problem is: java.lang.IllegalAccessError: tried to access method org.apache.xerces.parsers.XML11Configuration.getFeature0(Ljava/lang/String;)Z from class org.apache.xerces.parsers.XIncludeAwareParserConfiguration at org.apache.xerces.parsers.XIncludeAwareParserConfiguration.getFeature(Unknown Source) at org.apache.xerces.parsers.AbstractDOMParser.reset(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-51404
Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
[~drulli] can you please help us understand why analysis-core is pulling xercesImpl-2.11 that seem to cause problems with JVM's built-in XML parser on Java 8?The only usage I found of xerces code in analysis-core is the SaxSetup.java class that has been deprecated in 2016. Could analysis-core remove its dependency on xercesImpl, rely on the JVM's built-in parser (Jenkins now requires Java 8 that provides all the needed XML parsing capabilities) and remove SaxSetup.java? https://github.com/jenkinsci/analysis-core-plugin/blob/analysis-core-1.95/src/main/java/hudson/plugins/analysis/util/SaxSetup.javaThe problem is:{noformat}java.lang.IllegalAccessError: tried to access method org.apache.xerces.parsers.XML11Configuration.getFeature0(Ljava/lang/String;)Z from class org.apache.xerces.parsers.XIncludeAwareParserConfiguration at org.apache.xerces.parsers.XIncludeAwareParserConfiguration.getFeature(Unknown Source) at org.apache.xerces.parsers.AbstractDOMParser.reset(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-52773) Upgrade to newer version
Title: Message Title vikram katta updated an issue Jenkins / JENKINS-52773 Upgrade to newer version Change By: vikram katta Attachment: JenkinsError_Snap.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52773) Upgrade to newer version
Title: Message Title vikram katta updated an issue Jenkins / JENKINS-52773 Upgrade to newer version Change By: vikram katta Attachment: JenkinsInstallLog.txt Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52773) Upgrade to newer version
Title: Message Title vikram katta commented on JENKINS-52773 Re: Upgrade to newer version Hi Daniel, Thanks for the update Upgraded Jenkins LTS version. Even after upgrading the Jenkins still I do see some dependency errors due to which we are unable to install HP Automation Tools Plug in successfully. Attached "JenkinsError_Snap" and "JenkinsUpgradeInstallLog.txt" file for the complete details Please help us in resolving the issues again. Thanks for your support Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53029) Does anyone know if Jenkins supports IBM J9 plus TLSv1.2 ?
Title: Message Title Jacky Bie created an issue Jenkins / JENKINS-53029 Does anyone know if Jenkins supports IBM J9 plus TLSv1.2 ? Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2018-08-14 08:12 Environment: OS: Redhat 6.9+Jenkins+IBM J9 JRE 1.8 The jenkins configuration as below: /etc/sysconfig/jenkins JENKINS_HOME="/var/lib/jenkins" JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -Dhttps.protocols=TLSv1.2" JENKINS_HTTPS_PORT="8443" JENKINS_HTTPS_KEYSTORE="/var/lib/jenkins/keystore/jenkins_ibmjre8.jks" JENKINS_HTTPS_KEYSTORE_PASSWORD="tivoli4u" JENKINS_ARGS="--httpsKeyManagerType=IbmX509" The certificate for jenkins: keytool -list -keystore "/var/lib/jenkins/keystore/jenkins_ibmjre8.jks" -storepass tivoli4u Keystore type: jks Keystore provider: IBMJCE Your keystore contains 5 entries cn=ibm internal intermediate ca, o=international business machines corporation, c=us, Aug 9, 2018, trustedCertEntry, Certificate fingerprint (SHA1): F0:46:B4:00:B8:52:24:6E:A2:94:6B:17:CE:83:23:49:54:9A:3A:49 caintermediatecert, Aug 8, 2018, trustedCertEntry, Certificate fingerprint (SHA1): F0:46:B4:00:B8:52:24:6E:A2:94:6B:17:CE:83:23:49:54:9A:3A:49 myjenkinsreq, Aug 9, 2018, keyEntry, Certificate fingerprint (SHA1): C2:8C:5D:46:0E:A7:D7:A3:15:40:8B:5E:F3:69:43:5B:CE:F9:53:B2 cn=ibm internal root ca, o=international business machines corporation, c=us, Aug 9, 2018, trustedCertEntry, Certificate fingerprint (SHA1): 66:7C:48:44:D0:B6:0B:EF:1A:F7:ED:D5:2D:C3:55:76:B0:1A:02:73 carootcert, Aug 8, 2018, trustedCertEntry, Certificate fingerprint (SHA1): 66:7C:48:44:D0:B6:0B:EF:1A:F7:ED:D5:2D:C3:55:76:B0:1A:02:73 The certificate for IBM J9 JRE 1.8: keytool -list -keystore /var/ibm-java8/jre/lib/security/cacerts|grep my_jenkins_host Enter keystore password: changeit my_jenkins_host, Aug 10, 2018, trustedCertEntry, Priority: Major Reporter: Jacky Bie
[JIRA] (JENKINS-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Volker Gimple created an issue Jenkins / JENKINS-53030 Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException Issue Type: Bug Assignee: Denis Saponenko Attachments: Log114.txt, support_2018-08-14_07.44.30.zip Components: pipeline-multibranch-defaults-plugin Created: 2018-08-14 08:18 Environment: Jenkins 2.121.1 installed on Ubuntu Server 12.04. Plugin Pipeline: Multibranch at version 2.19. Nodes running Windows 7 x64 and ubu1204 (x86_64, i686, armv7l), ubu1604 (x86_64, i686, armv7l, aarch64) and ubu1804 (x86_64). See also support core zip in the attachments. Labels: ioexception2 SAXParseException parallel Priority: Major Reporter: Volker Gimple I am working on a build + test + deployment script for multiple platforms. So far the script is still mostly a dummy with the actual work still left to fill in. Nevertheless, when running the script I get intermittent (about one in three or four runs) failures caused by always the same two exceptions: org.xml.sax.SAXParseException; systemId: file:/var/lib/jenkins/jobs/Temp.ScriptTest/branches/branches-nodenesting.skpm19/builds/109/changelog2.xml; lineNumber: 1; columnNumber: 1; Premature end of fil
[JIRA] (JENKINS-53023) Fix broken coverage calculating
Title: Message Title Share Cheng started work on JENKINS-53023 Change By: Share Cheng Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53021) Impossible to get available plugins list
Title: Message Title Michael Dethline commented on JENKINS-53021 Re: Impossible to get available plugins list All works fine after completely reinstalled java. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53023) Fix broken coverage calculating
Title: Message Title Share Cheng updated JENKINS-53023 Jenkins / JENKINS-53023 Fix broken coverage calculating Change By: Share Cheng Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-38442) View sequential stages in the pipeline visualization graph
Title: Message Title Gert van Dijk updated an issue Jenkins / JENKINS-38442 View sequential stages in the pipeline visualization graph Change By: Gert van Dijk Attachment: jenkins-weird-masked2.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-38442) View sequential stages in the pipeline visualization graph
Title: Message Title Gert van Dijk commented on JENKINS-38442 Re: View sequential stages in the pipeline visualization graph First of all, I really like nested sequential stages, because I use a build tool already running things in maximum parallel (bazel), I don't want to run things with parallel stages which will be blocking on the Bazel server anyway. However, I noticed a very annoying visualization issue when a sub-stage has FAILED (due to a failed step): the parent stage is marked SUCCESS. I would assume the failed state would propagate up to its parent. It not only hides the error in the graph and makes it's hard to spot where in the pipeline the error occurred, it also hides the existence of the sub-stage. In the screenshot below, the "Code Style" stage has multiple sub-stages, that got somehow merged with its parent in this view, but the steps shown are part of one of the sub-stages. Sub-stages are shown during the run, though. As this Jira issue is still in-progress, I didn't want to open a new one. And I couldn't find any other issue reporting similar issues. (Seeing this on 1.7.2 / Core 2.121.2) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52975) In some cases, the pod cannot be deleted correctly.
Title: Message Title Carlos Sanchez commented on JENKINS-52975 Re: In some cases, the pod cannot be deleted correctly. can you paste the logs with the correct newlines? hard to read Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52259) Read pod template yaml from external file
Title: Message Title Carlos Sanchez resolved as Fixed isn't that JENKINS-52623 ? please do not reopen, and file a new issue instead if that's not the case Jenkins / JENKINS-52259 Read pod template yaml from external file Change By: Carlos Sanchez Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53030) Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException
Title: Message Title Volker Gimple commented on JENKINS-53030 Re: Intermittent hudson.util.IOException2 + org.xml.sax.SAXParseException After doing some more testing with more finely grained and selective try/catch blocks I can add the following details: If it does occur, then the IOException2 always occurs during the scm checkout call in BuildAndTestStep() I cannot confirm my earlier impression that the exception is more likely to happen for one of the ARM platforms (in fact the scm step is usually not executed on one of those as these are typically used for testing only, not for building) I have not seen the exception fly when there is no workspace left from the previous run When the exception is thrown, the sources on the affected machines have not been updated to the latest scm version For the moment I am working around this by sleeping something between 500 and 1500 milliseconds before retrying the scm checkout step. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52627) Prepare for final presentation
Title: Message Title Share Cheng resolved as Fixed Jenkins / JENKINS-52627 Prepare for final presentation Change By: Share Cheng Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52934) Preparing for final presentation
Title: Message Title Share Cheng resolved as Fixed Jenkins / JENKINS-52934 Preparing for final presentation Change By: Share Cheng Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Dirk Heinrichs commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves But the problem still persists (here too, BTW.). So why file a new issue for the VERY SAME problem? Reopening a ticket is common practice in such cases. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53023) Fix broken coverage calculating
Title: Message Title Share Cheng updated JENKINS-53023 Jenkins / JENKINS-53023 Fix broken coverage calculating Change By: Share Cheng Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53017) Jenkins slave can't connect via ssh to GCE instance
Title: Message Title Alexander O'Donovan-Jones commented on JENKINS-53017 Re: Jenkins slave can't connect via ssh to GCE instance Is there any way I can debug this? The log output from the plugin is insufficient to work out why this is happening. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53029) Does anyone know if Jenkins supports IBM J9 plus TLSv1.2 ?
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53029 Does anyone know if Jenkins supports IBM J9 plus TLSv1.2 ? Change By: Oleg Nenashev Labels: java-ibm Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53029) Does anyone know if Jenkins supports IBM J9 plus TLSv1.2 ?
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53029 Does anyone know if Jenkins supports IBM J9 plus TLSv1.2 ? Change By: Oleg Nenashev Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53029) Does anyone know if Jenkins supports IBM J9 plus TLSv1.2 ?
Title: Message Title Oleg Nenashev commented on JENKINS-53029 Re: Does anyone know if Jenkins supports IBM J9 plus TLSv1.2 ? Technically it does. Practically - not sure about this particular issue Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53024) Unable to deploy well with this below Jenkinsfile
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-53024 Unable to deploy well with this below Jenkinsfile Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53024) Unable to deploy well with this below Jenkinsfile
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53024 Unable to deploy well with this below Jenkinsfile Change By: Oleg Nenashev Component/s: pipeline Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53024) Unable to deploy well with this below Jenkinsfile
Title: Message Title
Oleg Nenashev updated JENKINS-53024
Not sure what is expected on the Jenkins side. "parseText("${params.payload}")" returns null in your case, and your Pipeline code does not check for it. So it fails. The script needs to be fixed Please reopen if you see an issue in the Jenkins behavior
Jenkins / JENKINS-53024
Unable to deploy well with this below Jenkinsfile
Change By:
Oleg Nenashev
Status:
Open Fixed but Unreleased
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-53031) Failed to deserialize response to UserRequest:org.jfrog.hudson.generic.GenericArtifactsDeployer$FilesDeployerCallable
Title: Message Title Ramesh Muthuraj created an issue Jenkins / JENKINS-53031 Failed to deserialize response to UserRequest:org.jfrog.hudson.generic.GenericArtifactsDeployer$FilesDeployerCallable Issue Type: Bug Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2018-08-14 10:18 Environment: Prod Priority: Major Reporter: Ramesh Muthuraj After i upgrading my Jenkins server into version v.21.121.2 & artifactory-plugin version as 2.11.0 i can see some errors once the pipeline has completed Error:- java.lang.SecurityException: Rejected: org.jfrog.build.api.Artifact; see https://jenkins.io/redirect/class-filter/ at hudson.remoting.ClassFilter.check(ClassFilter.java:77) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:131) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1826) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1713) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2000) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:422) at java.util.ArrayList.readObject(ArrayList.java:791) at sun.reflect.GeneratedMethodAccessor70.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1058) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2136) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2027) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:422) at hudson.remoting.Use
[JIRA] (JENKINS-53032) Support dynamic defintion of parallel running stages
Title: Message Title
Fabian Holler created an issue
Jenkins / JENKINS-53032
Support dynamic defintion of parallel running stages
Issue Type:
New Feature
Assignee:
Unassigned
Components:
pipeline
Created:
2018-08-14 10:26
Priority:
Minor
Reporter:
Fabian Holler
We often have the usecase that we need to define stages that we run in parallel during runtime. E.g.: we run a script to determine which application changed in a branch and want to run in parallel for each application stages like Build, Test, Check etc. It seems to be not supported currently. I couldn't find a way to realize it. I tried different variations of the syntax but couldn't make it work. Example of what I would like to do:
pipeline {
agent none
stages {
stage('Discover Changed Applications') {
steps {
script {
apps = ["app-one", "app-two"]
}
}
}
stage('parallel') {
steps {
script {
pstages = [:]
for (int i = 0; i < apps.size(); i++) {
app = apps[i]
pstages[app] = {
stages {
stage('Build application ') {
agent { label 'build' }
steps{
sh 'echo build'
}
}
stage('Test application ') {
agent { label 'test' }
steps{
sh 'echo test'
}
}
}
}
}
parallel(pstages)
}
}
}
}
}
[JIRA] (JENKINS-37152) Support Win32-OpenSSH
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-37152 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-37152) Support Win32-OpenSSH
Title: Message Title Ivan Fernandez Calvo updated JENKINS-37152 Jenkins / JENKINS-37152 Support Win32-OpenSSH Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53032) Support dynamic defintion of parallel running stages
Title: Message Title
Fabian Holler updated an issue
Jenkins / JENKINS-53032
Support dynamic defintion of parallel running stages
Change By:
Fabian Holler
We often have the usecase that we need to define stages that we run in parallel during runtime.E.g.: we run a script to determine which application changed in a branch and want to run in parallel for each application stages like Build, Test, Check etc.It seems to be not supported currently. I couldn't find a way to realize it. I tried different variations of the syntax but couldn't make it work.Example of what I would like to do:{code:java}pipeline { agent none stages { stage('Discover Changed Applications') { agent any steps {script { apps = ["app-one", "app-two"] } } } stage('parallel') { steps {script { pstages = [:] for (int i = 0; i < apps.size(); i++) { app = apps[i] pstages[app] = { stages {stage('Build application ') { agent { label 'build' } steps{ sh 'echo build' }}stage('Test application ') { agent { label 'test' } steps{ sh 'echo test' }} } } } parallel(pstages)} } } }}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to th
[JIRA] (JENKINS-53033) stuck but be able to continue after aborting build
Title: Message Title Shoo Yoo Yoon created an issue Jenkins / JENKINS-53033 stuck but be able to continue after aborting build Issue Type: Bug Assignee: Lev Mishin Attachments: build_name_setter_stuck.png Components: build-name-setter-plugin Created: 2018-08-14 10:48 Environment: windows 7 x64 Jenkins ver. 2.136 java.runtime.version 1.8.0_171-b25 build-name-setter 1.6.9 Priority: Critical Reporter: Shoo Yoo Yoon This is an intermittent issue. A build get stuck at step build-name-setter. Especially build can be continued after be aborted. However, then build-name-setter show empty. As the attached image, build-name-setter is stuck about 30 minutes and my build can only continue after I abort it. Add Comment
[JIRA] (JENKINS-53034) xUnit plugin fails to parse NUnit 2 report format generated by NUnit
Title: Message Title Jan-Jaap van der Geer created an issue Jenkins / JENKINS-53034 xUnit plugin fails to parse NUnit 2 report format generated by NUnit Issue Type: Bug Assignee: Nikolas Falco Attachments: TestResults.xml Components: xunit-plugin Created: 2018-08-14 10:51 Environment: Jenkins & Agents: Windows 2012R2 64 bit Jenkins 2.137 xUnit: 2.2.1 Priority: Major Reporter: Jan-Jaap van der Geer In may I registered JENKINS-51561. It may be that that actual problem was solved but xUnit still cannot parse our NUnit 2 files. The build log reports: 12:25:17 WARNING: The file 'C:\jks\ws\Classic-AMIS_Trunk_Build\Classic-AMIS-AdapterCommon\target\TestResults.xml' is an invalid file.12:25:17 WARNING: At line 29 of file:/C:/jks/ws/Classic-AMIS_Trunk_Build/Classic-AMIS-AdapterCommon/target/TestResults.xml:cvc-complex-type.2.4.d: Invalid content was found starting with element 'test-suite'. No child element is expected at this point.12:25:17 ERROR: Failed to parse POMs12:25:17 org.jenkinsci.plugins.xunit.service.TransformerException: The result file 'C:\jks\ws\Classic-AMIS_Trunk_Build\Classic-AMIS-AdapterCommon\target\TestResults.xml' for the metric 'NUnit' is not valid. The result file has been skipped.12:25:17 at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:112)12:25:17 at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.in
[JIRA] (JENKINS-53034) xUnit plugin fails to parse NUnit 2 report format generated by NUnit
Title: Message Title
Jan-Jaap van der Geer updated an issue
Jenkins / JENKINS-53034
xUnit plugin fails to parse NUnit 2 report format generated by NUnit
Change By:
Jan-Jaap van der Geer
In may I registered JENKINS-51561. It may be that that actual problem was solved but xUnit still cannot parse our NUnit 2 files. The build log reports: { noformat code:java }12:25:17 WARNING: The file 'C:\jks\ws\Classic-AMIS_Trunk_Build\Classic-AMIS-AdapterCommon\target\TestResults.xml' is an invalid file.12:25:17 WARNING: At line 29 of file:/C:/jks/ws/Classic-AMIS_Trunk_Build/Classic-AMIS-AdapterCommon/target/TestResults.xml:cvc-complex-type.2.4.d: Invalid content was found starting with element 'test-suite'. No child element is expected at this point.12:25:17 ERROR: Failed to parse POMs12:25:17 org.jenkinsci.plugins.xunit.service.TransformerException: The result file 'C:\jks\ws\Classic-AMIS_Trunk_Build\Classic-AMIS-AdapterCommon\target\TestResults.xml' for the metric 'NUnit' is not valid. The result file has been skipped.12:25:17 at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:112)12:25:17 at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:39)12:25:17 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084)12:25:17 at hudson.remoting.UserRequest.perform(UserRequest.java:210)12:25:17 at hudson.remoting.UserRequest.perform(UserRequest.java:53)12:25:17 at hudson.remoting.Request$2.run(Request.java:358)12:25:17 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)12:25:17 at java.util.concurrent.FutureTask.run(FutureTask.java:266)12:25:17 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)12:25:17 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)12:25:17 at hudson.remoting.Engine$1$1.run(Engine.java:94)12:25:17 at java.lang.Thread.run(Thread.java:745)12:25:17 Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from chdev1074.intern.csam.no/10.14.80.130:4964812:25:17 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)12:25:17 at hudson.remoting.UserResponse.retrieve(UserRequest.java:389)12:25:17 at hudson.remoting.Channel.call(Channel.java:955)12:25:17 at hudson.FilePath.act(FilePath.java:1070)12:25:17 at hudson.FilePath.act(FilePath.java:1059)12:25:17 at org.jenkinsci.plugins.xunit.XUnitProcessor.processTestsReport(XUnitProcessor.java:180)12:25:17 at org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:150)12:25:17 at org.jenkinsci.plugins.xunit.XUnitBuilder.perform(XUnitBuilder.java:114)12:25:17 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)12:25:17 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)12:25:17 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)12:25:17 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.bu
[JIRA] (JENKINS-52773) Upgrade to newer version
Title: Message Title Daniel Gront commented on JENKINS-52773 Re: Upgrade to newer version Hey is there a reason you're installing HPE Application Automation Tools version 5.3.4 beta? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53034) xUnit plugin fails to parse NUnit 2 report format generated by NUnit
Title: Message Title
Jan-Jaap van der Geer updated an issue
Jenkins / JENKINS-53034
xUnit plugin fails to parse NUnit 2 report format generated by NUnit
Change By:
Jan-Jaap van der Geer
In may I registered JENKINS-51561. It may be that that actual problem was solved but xUnit still cannot parse our NUnit 2 files. The build log reports:{code:java}12: 24:23 INFO: Processing NUnit-2.x (default)12: 25: 16 INFO: [NUnit-2.x (default)] - 15 test report file(s) were found with the pattern '**/target/TestResults.xml' relative to 'C:\jks\ws\Classic-AMIS_Trunk_Build' for the testing framework 'NUnit-2.x (default)'.12:25: 17 WARNING: The file 'C:\jks\ws\Classic-AMIS_Trunk_Build\Classic-AMIS-AdapterCommon\target\TestResults.xml' is an invalid file. 12:25:17 WARNING: At line 29 of file:/C:/jks/ws/Classic-AMIS_Trunk_Build/Classic-AMIS-AdapterCommon/target/TestResults.xml:cvc-complex-type.2.4.d: Invalid content was found starting with element 'test-suite'. No child element is expected at this point. 12:25:17 ERROR: Failed to parse POMs12 POMs12 :25:17 org.jenkinsci.plugins.xunit.service.TransformerException: The result file 'C:\jks\ws\Classic-AMIS_Trunk_Build\Classic-AMIS-AdapterCommon\target\TestResults.xml' for the metric 'NUnit' is not valid. The result file has been skipped. 12:25:17 at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:112) 12:25:17 at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:39) 12:25:17 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) 12:25:17 at hudson.remoting.UserRequest.perform(UserRequest.java:210) 12:25:17 at hudson.remoting.UserRequest.perform(UserRequest.java:53) 12:25:17 at hudson.remoting.Request$2.run(Request.java:358) 12:25:17 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 12:25:17 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 12:25:17 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 12:25:17 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 12:25:17 at hudson.remoting.Engine$1$1.run(Engine.java:94) 12:25:17 at java.lang.Thread.run(Thread.java:745) 12:25:17 Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from chdev1074.intern.csam.no/10.14.80.130: 4964812 4964812 :25:17 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) 12:25:17 at hudson.remoting.UserResponse.retrieve(UserRequest.java:389) 12:25:17 at hudson.remoting.Channel.call(Channel.java:955) 12:25:17 at hudson.FilePath.act(FilePath.java:1070) 12:25:17 at hudson.FilePath.act(FilePath.java:1059) 12:25:17 at org.jenkinsci.plugins.xunit.XUnitProcessor.processTestsReport(XUnitProcessor.java:180) 12:25:17 at org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:150) 12:25:17 at org.jenkinsci.plugins.xunit.XUnitBuilder.perform(XUnitBuilder.java:114) 12:25:17 at hudson.tasks.B
[JIRA] (JENKINS-52773) Upgrade to newer version
Title: Message Title vikram katta updated an issue Jenkins / JENKINS-52773 Upgrade to newer version Change By: vikram katta Attachment: HPAutomationtools_InstallError.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52773) Upgrade to newer version
Title: Message Title vikram katta commented on JENKINS-52773 Re: Upgrade to newer version We wanted to integrate Load Runner with Jenkins to execute LR scripts So while we are trying to install HP Automation Tools Plug in, it giving lot of errors. attached snapshot Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52773) Upgrade to newer version
Title: Message Title vikram katta updated an issue Jenkins / JENKINS-52773 Upgrade to newer version Change By: vikram katta Attachment: HPAutomationtools_InstallError.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52973) Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2
Title: Message Title Chetan Rajiv sirigiri updated an issue Jenkins / JENKINS-52973 Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2 Change By: Chetan Rajiv sirigiri Attachment: image-2018-08-14-16-47-41-794.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52973) Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2
Title: Message Title Chetan Rajiv sirigiri commented on JENKINS-52973 Re: Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Mike Scholze updated an issue Jenkins / JENKINS-51136 Jenkins UI hangs 2.117 - 2.119 Change By: Mike Scholze Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50154) Webhook delivery failed as X-Hub-Signature did not match calculated
Title: Message Title Bowen Sun updated an issue Jenkins / JENKINS-50154 Webhook delivery failed as X-Hub-Signature did not match calculated Change By: Bowen Sun Attachment: Screenshot 2018-08-14 12.32.55.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50154) Webhook delivery failed as X-Hub-Signature did not match calculated
Title: Message Title Bowen Sun commented on JENKINS-50154 Re: Webhook delivery failed as X-Hub-Signature did not match calculated We are seeing the same problem, but it wasn't tied to specific PR/branch, completely random and then just disappear. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53035) Jenkins upgrade
Title: Message Title Amit Kumar created an issue Jenkins / JENKINS-53035 Jenkins upgrade Issue Type: Bug Assignee: Stephen Connolly Attachments: error2018-08-14 17-03-12.png, version-2018-08-14 17-03-30.png Components: javancss-plugin Created: 2018-08-14 11:36 Environment: Production Priority: Minor Reporter: Amit Kumar Hi , I just upgraded my jenkins version from version 2.107.3 to version 2.121.2 and restarted. but i am keep getting error on GUI . This Jenkins appears to have crashed. Please check the logs. Error log:- A fatal error has been detected by the Java Runtime Environment: # SIGSEGV (0xb) at pc=0x7f667e79ddfa, pid=10630, tid=0x7f65dbfff700 # JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13) Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops) Problematic frame: C [libc.so.6+0x88dfa] strlen+0x2a # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # If you would like to submit a bug report, please visit:
[JIRA] (JENKINS-52582) AMI includes batmat ssh public key
Title: Message Title Baptiste Mathus updated JENKINS-52582 Jenkins / JENKINS-52582 AMI includes batmat ssh public key Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52582) AMI includes batmat ssh public key
Title: Message Title Baptiste Mathus commented on JENKINS-52582 Re: AMI includes batmat ssh public key Resolved by using ami-cfe4b2b0 for both the master and agents, then init scripts to install the missing package for each case. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title Florian P created an issue Jenkins / JENKINS-53036 NULL pointer exception when parsing JUnit files created with phpunit Issue Type: Bug Assignee: Nikolas Falco Attachments: phpunit.xml Components: xunit-plugin Created: 2018-08-14 12:05 Environment: Jenkins: 2.121.2 xUnit: 2.2.1 Priority: Major Reporter: Florian P JUnit files created with phpunit started to cause a NULL-pointer exception after an upgrade from xUnit 2.1.0 to 2.2.1: java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.recordTestResult(XUnitProcessor.java:354) at org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:157) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:161) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1823) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at
[JIRA] (JENKINS-53032) Support dynamic definition of parallel running stages
Title: Message Title Fabian Holler updated an issue Jenkins / JENKINS-53032 Support dynamic definition of parallel running stages Change By: Fabian Holler Summary: Support dynamic defintion definition of parallel running stages Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Murat Gundogdu edited a comment on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen We're having this problem for the latest TFS plugin versions, too. This needs urgent fix since when we get this error, all of the jobs start to fail until a Jenkins restart. Restarting Jenkins solves the issue temporarily until it happens again (usually in 24 hours). We are using up to date Jenkins and TFS Plugin versions. --> Currently, Jenkins: v2.121.2 / TFS Plugin: v5.139.2 We had this issue before with Jenkins v2.60.1 + TFS Plugin: v5.139.1 before we upgraded our Jenkins setup to the latest version.I can confirm that TFS Plugin v5.121.0 doesn't have this bug. So we downgrade downgraded to this version. However it has its own bugs :/ Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49042) Update Robot Framework logo to new one
Title: Message Title Tatu Kairi resolved as Fixed Released in 1.6.5 Jenkins / JENKINS-49042 Update Robot Framework logo to new one Change By: Tatu Kairi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53005) com.thoughtworks.xstream.mapper.CannotResolveClassException: html
Title: Message Title
Umesh Gachinmath edited a comment on JENKINS-53005
Re: com.thoughtworks.xstream.mapper.CannotResolveClassException: html
Hi DanielI am able to run the performance test successfully as per your advise, but with new {color:#172b4d}plugin version is '5.4.3-beta-SNAPSHOT'{color} Thank you :)
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-53005) com.thoughtworks.xstream.mapper.CannotResolveClassException: html
Title: Message Title Umesh Gachinmath commented on JENKINS-53005 Re: com.thoughtworks.xstream.mapper.CannotResolveClassException: html Hi Daniel I am able to run the performance test successfully as per your advise, but with new plugin version is '5.4.3-beta-SNAPSHOT' Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-46052) GIT: UserIdentity does not work on pipeline
Title: Message Title Alexander Evseev commented on JENKINS-46052 Re: GIT: UserIdentity does not work on pipeline Today faced with the same issue. Jenkins 2.100 Git plugin 3.7.0 Pipeline: SCM Step plugin 2.6 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-37600) Dashboard View Test Statistics Grid showing only zeros for Robot Framework tests
Title: Message Title Tatu Kairi closed an issue as Not A Defect We in the maintenance team have never even heard of Dashboard View before these issues got reported. Thanks for bringing the issue up! Since Dashboard View is separate plugin (ie. not default Jenkins behaviour), we most certainly do not support whatever it expects. Therefore we need the capability first to begin with, which is covered in JENKINS-22603. Thus, as we do not have anything to fix, I'm closing this issue. Please follow the JENKINS-22603 ticket for when we can support Dashboard VIew to begin with. Jenkins / JENKINS-37600 Dashboard View Test Statistics Grid showing only zeros for Robot Framework tests Change By: Tatu Kairi Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop recei
[JIRA] (JENKINS-52518) Finalise documentation
Title: Message Title Abhishek Gautam resolved as Fixed Jenkins / JENKINS-52518 Finalise documentation Change By: Abhishek Gautam Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52843) Push SPRP specific YAML syntax to sub-element
Title: Message Title Abhishek Gautam updated JENKINS-52843 Jenkins / JENKINS-52843 Push SPRP specific YAML syntax to sub-element Change By: Abhishek Gautam Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52495) Add more unit tests
Title: Message Title Abhishek Gautam updated JENKINS-52495 Jenkins / JENKINS-52495 Add more unit tests Change By: Abhishek Gautam Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52495) Add more unit tests
Title: Message Title Abhishek Gautam updated JENKINS-52495 Jenkins / JENKINS-52495 Add more unit tests Change By: Abhishek Gautam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52516) Do not append default extension to script name
Title: Message Title Abhishek Gautam updated JENKINS-52516 Jenkins / JENKINS-52516 Do not append default extension to script name Change By: Abhishek Gautam Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53035) Jenkins upgrade
Title: Message Title Oleg Nenashev commented on JENKINS-53035 Re: Jenkins upgrade There is no vidence it is related to the javancss plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53035) Jenkins upgrade
Title: Message Title Oleg Nenashev edited a comment on JENKINS-53035 Re: Jenkins upgrade There is no vidence evidence it is related to the javancss plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53035) Jenkins upgrade
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53035 Jenkins upgrade Change By: Oleg Nenashev Component/s: _unsorted Component/s: git-client-plugin Component/s: javancss-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53035) Jenkins upgrade: SIGSEGV in Git Client Invocation
Title: Message Title Oleg Nenashev assigned an issue to Mark Waite Jenkins / JENKINS-53035 Jenkins upgrade: SIGSEGV in Git Client Invocation Change By: Oleg Nenashev Assignee: Stephen Connolly Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53035) Jenkins upgrade: SIGSEGV in Git Client Invocation
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53035 Jenkins upgrade: SIGSEGV in Git Client Invocation Change By: Oleg Nenashev Summary: Jenkins upgrade : SIGSEGV in Git Client Invocation Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53035) Jenkins upgrade: SIGSEGV in Git Client Invocation
Title: Message Title Oleg Nenashev commented on JENKINS-53035 Re: Jenkins upgrade: SIGSEGV in Git Client Invocation Mark Waite I do not think it is really related to Git Client logic, but maybe you know something about this kind of issues. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53037) Input approval not always updating UI
Title: Message Title Thomas Buys created an issue Jenkins / JENKINS-53037 Input approval not always updating UI Issue Type: Bug Assignee: Tom FENNELLY Components: blueocean-plugin, sse-gateway-plugin Created: 2018-08-14 12:47 Environment: os.arch: amd64 os.name: Linux os.version: 3.16.0-4-amd64 Jenkins version: 2.136 Java version: 1.8.0_171 AnsiColor - 0.5.2 Ant Plugin - 1.8 Apache HttpComponents Client 4.x API Plugin - 4.5.5-3.0 Authentication Tokens API Plugin - 1.3 Autofavorite for Blue Ocean - 1.2.2 Bitbucket Branch Source Plugin - 2.2.12 Bitbucket Pipeline for Blue Ocean - 1.7.2 Blue Ocean - 1.7.2 Blue Ocean Core JS - 1.7.2 Blue Ocean Pipeline Editor - 1.7.2 bouncycastle API Plugin - 2.16.3 Branch API Plugin - 2.0.20 Build Environment Plugin - 1.6 Cobertura Plugin - 1.12.1 Command Agent Launcher Plugin - 1.2 Common API for Blue Ocean - 1.7.2 Conditional BuildStep - 1.3.6 Config API for Blue Ocean - 1.7.2 Credentials Binding Plugin - 1.16 Credentials Plugin - 2.1.18 Dashboard for Blue Ocean - 1.7.2 Design Language - 1.7.2 Discard Old Build plugin - 1.05 Display URL API - 2.2.0 Display URL for Blue Ocean - 2.2.0 Docker Commons Plugin - 1.13 Docker Pipeline - 1.17 Durable Task Plugin - 1.25 embeddable-build-status - 1.9 Events API for Blue Ocean - 1.7.2 Extensible Choice Parameter plugin - 1.6.0 External Monitor Job Type Plugin - 1.7 External Workspace Manager Plugin - 1.1.2 Favorite - 2.3.2 Folders Plugin - 6.5.1 Git client plugin - 2.7.3 Git Pipeline for Blue Ocean - 1.7.2 Git plugin - 3.9.1 GIT server Plugin - 1.7 GitHub API Plugin - 1.92 GitHub Authentication plugin - 0.29 GitHub Branch Source Plugin - 2.3.6 GitHub Pipeline for Blue Ocean - 1.7.2 GitHub plugin - 1.29.2 GitHub Pull Request Coverage Status - 1.10.0 Handy Uri Templates 2.x API Plugin - 2.1.6-1.0 HTML Publisher plugin - 1.16 HTML5 Notifier Plugin - 1.5 i18n for Blue Ocean - 1.7.2 Icon Shim Plugin - 2.0.3 Jackson 2 API Plugin - 2.8.11.3 java.io.tmpdir cleaner plugin - 1.3 Javadoc Plugin - 1.4 _javascript_ GUI Lib: ACE Editor bundle plugin - 1.1 _javascript_ GUI Lib: Handlebars bundle plugin - 1.1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin - 1.2.1 _javascript_ GUI Lib: Moment.js bundle plugin - 1.1.1 JDK Tool Plugin - 1.1 JIRA Integration for Blue Ocean - 1.7.2 JIRA plugin - 3.0.0 Job Restrictions Plugin - 0.7 jQuery plugin - 1.12.4-0 JSch dependency plugin - 0.1.54.2 JUnit Plugin - 1.24 JWT for Blue Ocean - 1.7.2 LDAP Plugin - 1.20 Mailer Plugin - 1.21 Matrix Authorization Strategy Plugin - 2.3 Matrix Project Plugin - 1.13 Maven Integr
[JIRA] (JENKINS-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title Nikolas Falco commented on JENKINS-53036 Re: NULL pointer exception when parsing JUnit files created with phpunit It's very strange that NPE because all cases seems covered. Could you please send me the job configuration? The issue is not related to the report file. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title Nikolas Falco commented on JENKINS-53036 Re: NULL pointer exception when parsing JUnit files created with phpunit I got it seems happens on non pipeline job with old configuration Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-15234) Robot plugin should mark build as unstable if there are failed non-critical tests
Title: Message Title Tatu Kairi commented on JENKINS-15234 Re: Robot plugin should mark build as unstable if there are failed non-critical tests Brendan Mannix duly noted! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-15234) Robot plugin should mark build as unstable if there are failed non-critical tests
Title: Message Title Tatu Kairi closed an issue as Duplicate Closing since duplicate of JENKINS-12106 Please follow that issue for furher development Jenkins / JENKINS-15234 Robot plugin should mark build as unstable if there are failed non-critical tests Change By: Tatu Kairi Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-47227) failed to uncoerce hudson.plugins.robot.RobotPublisher@1f5a660a java.lang.UnsupportedOperationException: no public field ‘enableCache’ (or getter method) found in class hudson.p
Title: Message Title Tatu Kairi updated JENKINS-47227 Released in 1.6.5 Jenkins / JENKINS-47227 failed to uncoerce hudson.plugins.robot.RobotPublisher@1f5a660a java.lang.UnsupportedOperationException: no public field ‘enableCache’ (or getter method) found in class hudson.plugins.robot.RobotPublisher Change By: Tatu Kairi Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-38338) Opening Robot Framework report failes
Title: Message Title Tatu Kairi closed an issue as Duplicate Closing this issue since this is, still, a duplicate of JENKINS-32118 Jenkins / JENKINS-38338 Opening Robot Framework report failes Change By: Tatu Kairi Status: Reopened Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-34469) robotframework pipeline-plugin compatibility
Title: Message Title Tatu Kairi commented on JENKINS-34469 Re: robotframework pipeline-plugin compatibility Bassam Khouri we do not have ETAs as we are maintaining this plugin alongside our full-day jobs. This is definitely on our radar, as it is annoyance to us as well. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-32118) Document Jenkins security settings so Robot Framework log/report can be opened
Title: Message Title Tatu Kairi commented on JENKINS-32118 Re: Document Jenkins security settings so Robot Framework log/report can be opened Subodh Agnihotri the workaround thus work, though. I'd suggest you double check have you employed it correctly. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53038) Jenkins fails to start on port that is open
Title: Message Title Phillip Johnson moved an issue Jenkins / JENKINS-53038 Jenkins fails to start on port that is open Change By: Phillip Johnson Project: Infrastructure Jenkins Key: INFRA JENKINS - 1749 53038 Workflow: classic default workflow JNJira + In-Review Component/s: core Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50154) Webhook delivery failed as X-Hub-Signature did not match calculated
Title: Message Title Josh McCullough commented on JENKINS-50154 Re: Webhook delivery failed as X-Hub-Signature did not match calculated I'm also seeing this issue this morning but only for a specific repo (1 out of 20+). Looking at the webhook history, this was working fine and then this same repo starting showing failed webhook as of 2018-08-09 14:36:05. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52942) Load Options load directory doesn't substitute a parameter
Title: Message Title John Czukkermann commented on JENKINS-52942 Re: Load Options load directory doesn't substitute a parameter Related to this, possibly a separate issue, the Poll SCM support does not substitute the build parameter for the workspace/stream name either. This issue is a big problem for me because my team develops in multiple streams. I don't want to create/maintain different Jenkins jobs for each such stream. I want one job that does the thing I need it to do using the stream/workspace I specify in the build parameter. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50154) Webhook delivery failed as X-Hub-Signature did not match calculated
Title: Message Title Josh McCullough edited a comment on JENKINS-50154 Re: Webhook delivery failed as X-Hub-Signature did not match calculated I'm also seeing this issue this morning but only for a specific repo (1 out of 20+). Looking at the webhook history, this was working fine and then this same repo starting showing failed webhook as of 2018-08-09 14:36:05. Note that we do not have repo-level hooks, just a single org-level hook. All other builds are working fine! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53038) Jenkins fails to start on port that is open
Title: Message Title Oleg Nenashev commented on JENKINS-53038 Re: Jenkins fails to start on port that is open The ports may be blocked by firewalls or services which do not always appear in netstat. Are you able to start another web service on this port when Jenkins fails? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52904) Clean up Error Telemetry tests to use expect and make sure they're testing the hook methods correctly
Title: Message Title Mandie Smith updated JENKINS-52904 Jenkins / JENKINS-52904 Clean up Error Telemetry tests to use expect and make sure they're testing the hook methods correctly Change By: Mandie Smith Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51766) Save flavor during registration and serve different manifest depending on it
Title: Message Title Mandie Smith updated JENKINS-51766 Jenkins / JENKINS-51766 Save flavor during registration and serve different manifest depending on it Change By: Mandie Smith Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52905) Update shunit tests to have messages on every assert
Title: Message Title Mandie Smith updated JENKINS-52905 Jenkins / JENKINS-52905 Update shunit tests to have messages on every assert Change By: Mandie Smith Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53033) stuck but be able to continue after aborting build
Title: Message Title Oleg Nenashev commented on JENKINS-53033 Re: stuck but be able to continue after aborting build Would it be possible to get a stacktrace? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53033) stuck but be able to continue after aborting build
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-53033 stuck but be able to continue after aborting build Change By: Oleg Nenashev Assignee: Lev Mishin Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50154) Webhook delivery failed as X-Hub-Signature did not match calculated
Title: Message Title Josh McCullough edited a comment on JENKINS-50154 Re: Webhook delivery failed as X-Hub-Signature did not match calculated I'm also seeing this issue this morning but only for a specific repo (1 out of 20+). Looking at the webhook history, this was working fine and then this same repo starting showing failed webhook webhooks as of 2018-08-09 14:36:05. Note that we do not have repo-level hooks, just a single org-level hook. All other builds are working fine! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title Florian P updated an issue Jenkins / JENKINS-53036 NULL pointer exception when parsing JUnit files created with phpunit Change By: Florian P Attachment: config-xunit-2.1.0.xml Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title
Pieter-Jan Busschaert commented on JENKINS-53036
Re: NULL pointer exception when parsing JUnit files created with phpunit
Exactly the same issue on our setup. Also started happening immediately after the upgrade to 2.2.1 Most of our builds have 2 xUnit steps at the end, to collect unittest information in 2 different formats. {{INFO: Starting to record. INFO: Processing QTestlib-Version 5.x INFO: [QTestlib-Version 5.x] - 1 test report file(s) were found with the pattern 'Apps/*_qtest.xml' relative to '...' for the testing framework 'QTestlib-Version 5.x'. INFO: Processing GoogleTest-1.6 INFO: [GoogleTest-1.6] - 18 test report file(s) were found with the pattern 'Apps/*_gtest.xml' relative to '...' for the testing framework 'GoogleTest-1.6'. ERROR: Build step failed with exception java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.recordTestResult(XUnitProcessor.java:354) at org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:157) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:161) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Publish xUnit test result report' marked build as failure}}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" g
[JIRA] (JENKINS-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title
Pieter-Jan Busschaert edited a comment on JENKINS-53036
Re: NULL pointer exception when parsing JUnit files created with phpunit
Exactly the same issue on our setup. Also started happening immediately after the upgrade to 2.2.1Most of our builds have 2 xUnit steps at the end, to collect unittest information in 2 different formats. { { noformat} INFO: Starting to record.INFO: Processing QTestlib-Version 5.xINFO: [QTestlib-Version 5.x] - 1 test report file(s) were found with the pattern 'Apps/*_qtest.xml' relative to '...' for the testing framework 'QTestlib-Version 5.x'.INFO: Processing GoogleTest-1.6INFO: [GoogleTest-1.6] - 18 test report file(s) were found with the pattern 'Apps/*_gtest.xml' relative to '...' for the testing framework 'GoogleTest-1.6'.ERROR: Build step failed with exceptionjava.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.recordTestResult(XUnitProcessor.java:354) at org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:157) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:161) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Build step 'Publish xUnit test result report' marked build as failure {noformat } }
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google G
[JIRA] (JENKINS-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title Florian P updated an issue Jenkins / JENKINS-53036 NULL pointer exception when parsing JUnit files created with phpunit Change By: Florian P Attachment: config-xunit-2.2.1.xml Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title Florian P commented on JENKINS-53036 Re: NULL pointer exception when parsing JUnit files created with phpunit I attached both configs. The working one with 2.1.0 and the non-working version with 2.2.1. This is indeed a non-pipeline job. The job configuration is built and deployed with Jenkins Job Builder 2.2.1 (latest as of writing). Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52555) Declarative pipeline functions cannot access defined environment variables from environment block
Title: Message Title Brian Skarda commented on JENKINS-52555 Re: Declarative pipeline functions cannot access defined environment variables from environment block Ah, interesting. Thanks for the explanation Andrew. Is variable resolution documented anywhere or could I open a PR to add declarative pipeline variable resolution into one of the documentation sources? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52762) Automatically deploy ingest.json based off webhooks from jenkins-infra/evergreen
Title: Message Title R. Tyler Croy started work on JENKINS-52762 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51458) Provide documentation for the essentials client/server setup
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-51458 Provide documentation for the essentials client/server setup Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52569) Write end user docs to start instance (docker and aws flavors)
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-52569 Write end user docs to start instance (docker and aws flavors) Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50197) Incorporate "pre-release" builds of plugins into Jenkins Essentials
Title: Message Title R. Tyler Croy updated JENKINS-50197 Jenkins / JENKINS-50197 Incorporate "pre-release" builds of plugins into Jenkins Essentials Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51458) Provide documentation for the essentials client/server setup
Title: Message Title R. Tyler Croy assigned an issue to Mandie Smith Passing this over to Mandie Smith, would you mind just making sure the client/README.adoc and services/README.adoc are in a good shape for posterity? Jenkins / JENKINS-51458 Provide documentation for the essentials client/server setup Change By: R. Tyler Croy Assignee: R. Tyler Croy Mandie Smith Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52728) FreeStyle and Native Maven jobs should be disabled
Title: Message Title R. Tyler Croy updated JENKINS-52728 Jenkins / JENKINS-52728 FreeStyle and Native Maven jobs should be disabled Change By: R. Tyler Croy Status: In Review Resolved Assignee: Baptiste Mathus R. Tyler Croy Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53039) Rename to Jenkins Evergreen
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-53039 Rename to Jenkins Evergreen Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-08-14 15:00 Priority: Minor Reporter: R. Tyler Croy Need to: Send an FYI to the dev list Update JEP documents Update Jira information Update past blog posts Add Comment
