[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Vincent Massol commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Cyrille Le Clerc https://ci.xwiki.org is now using mysql. I'll let you know in a few days if we still have problems and report the displayed times. Thx 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-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Cenk Tosun commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) i have also identical log outputs (even identical sha1) for the builds which are triggered Started on Nov 22, 2018 8:37:06 AM no polling baseline in @libs\shared-library-repo on Using strategy: Default [poll] Last Built Revision: Revision (refs/remotes/origin/master) Using strategy: Default [poll] Last Built Revision: Revision (refs/remotes/origin/master) Using strategy: Default [poll] Last Built Revision: Revision (refs/remotes/origin/master) Done. Took 5 ms Changes found 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-51103) Sometimes failed to save the information into jenkins job after selecting required information on wizard dialog.
Title: Message Title Jane Zhang closed an issue as Cannot Reproduce cannot reproduce the defect, close it for now, please reopen it if it happens again. Jenkins / JENKINS-51103 Sometimes failed to save the information into jenkins job after selecting required information on wizard dialog. Change By: Jane Zhang Status: Open Closed Resolution: Cannot Reproduce 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-51101) MC Wizard dialog shows empty during the first time successfully login.
Title: Message Title Jane Zhang commented on JENKINS-51101 Re: MC Wizard dialog shows empty during the first time successfully login. cannot reproduce the defect, close it for now, please reopen it if it happens again. 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-54765) JEP-200 org.apache.maven.artifact.versioning.ComparableVersion$ListItem
Title: Message Title sakshi sood created an issue Jenkins / JENKINS-54765 JEP-200 org.apache.maven.artifact.versioning.ComparableVersion$ListItem Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2018-11-22 08:37 Labels: JEP-200 Priority: Minor Reporter: sakshi sood I am gettting below error in logs even when i have added an entry in /etc/sysconfig/tomcat6 in JAVAOPTS="org.apache.maven.artifact.versioning.ComparableVersion$ListItem " so the workaround does not work in this case. Please check this issue WARNING: org.apache.maven.artifact.versioning.ComparableVersion$ListItem in file:/var/hudson/master/plugins/maven-plugin/WEB-INF/li b/maven-artifact-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ java.lang.SecurityException: Class rejected by the class filter: org.apache.maven.artifact.versioning.ComparableVersion$ListItem at jenkins.security.ClassFilterImpl.notifyRejected(ClassFilterImpl.java:335) at jenkins.security.ClassFilterImpl.lambda$isBlacklisted$1(ClassFilterImpl.java:185) at java.util.Map.computeIfAbsent(Map.java:957) at java.util.Collections$SynchronizedMap.computeIfAbsent(Collections.java:2672) at jenkins.security.ClassFilterImpl.isBlacklisted(ClassFilterImpl.java:140) at hudson.remoting.ClassFilter$1.isBlacklisted(ClassFilter.java:121) at hudson.util.XStream2$BlacklistedTypesConverter.canConvert(XStream2.java:567) at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:59) at com.thoughtworks.xstream.XStream$1.lookupConverterForType(XStream.java:498) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:56) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:393) at hudso
[JIRA] (JENKINS-51101) MC Wizard dialog shows empty during the first time successfully login.
Title: Message Title Jane Zhang closed an issue as Cannot Reproduce cannot reproduce the defect, close it for now, please reopen it if it happens again. Jenkins / JENKINS-51101 MC Wizard dialog shows empty during the first time successfully login. Change By: Jane Zhang Status: Open Closed Resolution: Cannot Reproduce 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-20679) Define manifest header in the jpi file to capture minimum Java requirement
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-20679 Define manifest header in the jpi file to capture minimum Java requirement Change By: Oleg Nenashev Assignee: Daniel Beck Oleg Nenashev 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-53795) Build Flow: Non-fatal issues when running core build with JDK 11 (Powermock tests)
Title: Message Title Oleg Nenashev resolved as Fixed It was resolved by updating PowerMock and Mockito in the Jenkins Core Jenkins / JENKINS-53795 Build Flow: Non-fatal issues when running core build with JDK 11 (Powermock tests) Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed 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-51998) Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51998 Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller Change By: Oleg Nenashev Summary: Pipeline serialization fails on Java 10 11 : java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller 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-51998) Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller
Title: Message Title Oleg Nenashev commented on JENKINS-51998 Re: Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller Samuel Gabriel yes, it was closed due to the temporary workaround we applied for the hackfest. Currently I am working on making this workaround available in update centers somehow. There is a separate story for a production-grade solution which is needed for the Java 11 GA availability (JENKINS-52187) 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-44616) groovy increment does not work
Title: Message Title Yuriy Burtsev closed an issue as Fixed Jenkins / JENKINS-44616 groovy increment does not work Change By: Yuriy Burtsev Status: Resolved Closed 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-52187) Java 10+: Upstream the Pipeline: Support patches
Title: Message Title Oleg Nenashev commented on JENKINS-52187 Re: Java 10+: Upstream the Pipeline: Support patches I will try to implement a workaround for it for Java 11 preview availability: JENKINS-51998 . But we will still need a solution for GA, and it does not look to be "just upstreaming" due to the compatibility issues discovered by Sam Van Oort 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-40025) Conflict active-choices-plugin with jquery-plugin
Title: Message Title Yuriy Burtsev closed an issue as Cannot Reproduce Jenkins / JENKINS-40025 Conflict active-choices-plugin with jquery-plugin Change By: Yuriy Burtsev Status: Resolved Closed 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-52187) Pipeline: Support. Integrate JBoss Remoting patches in the common release
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52187 Pipeline: Support. Integrate JBoss Remoting patches in the common release Change By: Oleg Nenashev Summary: Java 10+: Upstream the Pipeline: Support . Integrate JBoss Remoting patchesin the common release 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-36355) Xvfb does not export DISPLAY variable
Title: Message Title Yuriy Burtsev updated JENKINS-36355 Jenkins / JENKINS-36355 Xvfb does not export DISPLAY variable Change By: Yuriy Burtsev Status: Fixed but Unreleased Closed 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-36355) Xvfb does not export DISPLAY variable
Title: Message Title Yuriy Burtsev updated JENKINS-36355 Jenkins / JENKINS-36355 Xvfb does not export DISPLAY variable Change By: Yuriy Burtsev Status: Open Fixed but Unreleased Resolution: Fixed 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-51998) Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51998 Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller Change By: Oleg Nenashev Issue Type: Improvement Bug 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-20679) Define manifest header in the jpi file to capture minimum Java requirement
Title: Message Title Oleg Nenashev commented on JENKINS-20679 Re: Define manifest header in the jpi file to capture minimum Java requirement As discussed with Daniel Beck I will take a look at these stories. Some of them may be helpful to deliver a custom version of Pipeline: Support for Java 11 preview availability: JENKINS-51998 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-35430) Regression if Jenkins-in-docker builds of Pipeline in 2.x
Title: Message Title Yuriy Burtsev closed an issue as Incomplete Jenkins / JENKINS-35430 Regression if Jenkins-in-docker builds of Pipeline in 2.x Change By: Yuriy Burtsev Status: Resolved Closed 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down yep, the move from trilead-ssh2 to trilead-api is to be able to use a different trilead-ssh2 library than code. The reason to make it is to do not have to upgrade the core to change only a library, this change is similar a change made with the bouncycastle library. My mistake was not testing this change with the PCT and I have screwed up every plugin with the ssh-slaves dependency for a day and a half. Right now (1.29.1), ssh-slaves has the trilead-ssh2 dependency but still uses the trilead-ssh2 because I removed the option to mask core classes, so the next step it is to find every plugin that depends on it and make a PR to be able to make this change in next months, it's gonna be more longer than I like. I also working on a branch 2.0.0 that introduces the concept of SSHProvider, it allows using different libraries or methods to make the SSH connection. The first alternative method will be using the native SSH client, it would improve performance and stability. Another important new feature is one to have several commands profiles, right now, the commands used are hardcoded and are only compatible with agents that have bash installed (even do it works on PowerShell and others), it makes that you can introduce a compatibility issue by modified a simple command, and stops to make improvements in others. By using the commands profiles you will select your command profile for your agent bash, Python, PowerShell, cmd, ... whatever you want. 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-54601) Include some changes from 1.9.40
Title: Message Title Evaristo Gutierrez commented on JENKINS-54601 Re: Include some changes from 1.9.40 Released as 1.7.24.2 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-54601) Include some changes from 1.9.40
Title: Message Title Evaristo Gutierrez updated JENKINS-54601 Jenkins / JENKINS-54601 Include some changes from 1.9.40 Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed 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-54395) Snapshot management feature in GCE-plugin
Title: Message Title Michael Vasiliev commented on JENKINS-54395 Re: Snapshot management feature in GCE-plugin Hi Craig Barber. Do you have any updates on this feature? Would you like more input from me? 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-54700) Findbugs SAXParser not found
Title: Message Title Christian Asselmeyer commented on JENKINS-54700 Re: Findbugs SAXParser not found For me, collecting SpotBugs results works again after downgrading back to 1.0.0-beta4. 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-54766) Missing target dependency to sue demo-* targets
Title: Message Title Adrien Lecharpentier created an issue Jenkins / JENKINS-54766 Missing target dependency to sue demo-* targets Issue Type: Improvement Assignee: Adrien Lecharpentier Components: plugin-compat-tester Created: 2018-11-22 10:04 Priority: Minor Reporter: Adrien Lecharpentier Currently, the Makefile target for demo-jdk8 and demo-jdk11 rely on the existence of the cli jar file. However, there is no dependency on the target to build that file. Add Comment This message was sent by A
[JIRA] (JENKINS-54767) Global variables are overriding local variables
Title: Message Title
fisnik hajredini commented on JENKINS-54767
Re: Global variables are overriding local variables
The following was generated using this groovy script:
Jenkins.instance.pluginManager.plugins.each{
plugin ->
println ("${plugin.getDisplayName()} (${plugin.getShortName()}): ${plugin.getVersion()}")
}
Durable Task Plugin (durable-task): 1.26 Pipeline: Nodes and Processes (workflow-durable-task-step): 2.25 Nexus Artifact Uploader (nexus-artifact-uploader): 2.10 GitHub Branch Source Plugin (github-branch-source): 2.4.1 Pipeline: SCM Step (workflow-scm-step): 2.7 Pipeline (workflow-aggregator): 2.6 Pipeline: API (workflow-api): 2.31 Pipeline: Declarative (pipeline-model-definition): 1.3.2 Pipeline: GitHub Groovy Libraries (pipeline-github-lib): 1.0 Ant Plugin (ant): 1.8 Apache HttpComponents Client 4.x API Plugin (apache-httpcomponents-client-4-api): 4.5.5-3.0 Workspace Cleanup Plugin (ws-cleanup): 0.36 Command Agent Launcher Plugin (command-launcher): 1.2 SSH Slaves plugin (ssh-slaves): 1.28.1 Windows Slaves Plugin (windows-slaves): 1.3.1 _javascript_ GUI Lib: Moment.js bundle plugin (momentjs): 1.1.1 Pipeline: Basic Steps (workflow-basic-steps): 2.12 Lockable Resources plugin (lockable-resources): 2.3 JDK Tool Plugin (jdk-tool): 1.1 Pipeline: REST API Plugin (pipeline-rest-api): 2.10 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.12 Folders Plugin (cloudbees-folder): 6.6 JSch dependency plugin (jsch): 0.1.54.2 Build Timeout (build-timeout): 1.19 Job Configuration History Plugin (jobConfigHistory): 2.18.3 Credentials Binding Plugin (credentials-binding): 1.16 PAM Authentication plugin (pam-auth): 1.4 Token Macro Plugin (token-macro): 2.5 Matrix Authorization Strategy Plugin (matrix-auth): 2.3 Docker Commons Plugin (docker-commons): 1.13 Pipeline: Milestone Step (pipeline-milestone-step): 1.3.1 LDAP Plugin (ldap): 1.20 Green Balls (greenballs): 1.15 External Monitor Job Type Plugin (external-monitor-job): 1.7 Copy Artifact Plugin (copyartifact): 1.41 Resource Disposer Plugin (resource-disposer): 0.12 Pipeline: Build Step (pipeline-build-step): 2.7 _javascript_ GUI Lib: Handlebars bundle plugin (handlebars): 1.1.1 Pipeline: Supporting APIs (workflow-support): 2.21 Gradle Plugin (gradle): 1.29 Pipeline: Job (workflow-job): 2.26 Structs Plugin (structs): 1.17 Pipeline: Groovy (workflow-cps): 2.60 Matrix Project Plugin (matrix-project): 1.13 Simple Theme Plugin (simple-theme-plugin): 0.5.1 GitHub Authentication plugin (github-oauth): 0.29 Branch API Plugin (branch-api): 2.0.20 GitHub API Plugin (github-api): 1.92 Pipeline: Stage View Plugin (pipeline-stage-view): 2.10 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5 Pipeline: Stage Tags Metadata (pipeline-stage-tags-metadata): 1.3.2 bouncycastle API Plugin (bouncycastle-api): 2.17 Jackson 2 API Plugin (jackson2-api): 2.8.11.3 Email Extension Plugin (email-ext): 2.63 _javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1 Docker Pipeline (docker-workflow): 1.17 GitHub plugin (github): 1.29.3 Pipeline: Multibranch (workflow-multibranch): 2.20 JUnit Plugin (junit): 1.26.1 SSH Credentials Plugin (ssh-credentials): 1.14 Node and Label parameter plugin (nodelabelparameter): 1.7.2 Credentials Plugin (credentials): 2.1.18 Nexus Platform Plugin (nexus-jenkins-plugin): 3.3.20181025-134249.614c5f4 Authentication Tokens API Plugin (au
[JIRA] (JENKINS-54767) Global variables are overriding local variables
Title: Message Title fisnik hajredini created an issue Jenkins / JENKINS-54767 Global variables are overriding local variables Issue Type: Task Assignee: Oleg Nenashev Components: _unsorted Created: 2018-11-22 10:06 Environment: Jenkins 2.138.2 and 2.138.3 Priority: Major Reporter: fisnik hajredini We had this issue since 2.138.2, now we are on 2.138.3 When running a build, its always ignoring the local parameters and its always taking into consideration only the global parameters. This makes it impossible for us to run builds with different parameters as they will always only follow the global parameters. The only way this could work is when there is no global parameters. If there is only Local parameters then they wont be overriden. Add Comment
[JIRA] (JENKINS-54733) After 10 builds Pipeline Stage View disappears.
Title: Message Title Omar Malik updated an issue Jenkins / JENKINS-54733 After 10 builds Pipeline Stage View disappears. Change By: Omar Malik Priority: Minor Major 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-54767) Global variables are overriding local variables
Title: Message Title
fisnik hajredini edited a comment on JENKINS-54767
Re: Global variables are overriding local variables
The following was generated using this groovy script:{code:java}Jenkins.instance.pluginManager.plugins.each{ plugin -> println ("${plugin.getDisplayName()} (${plugin.getShortName()}): ${plugin.getVersion()}")}{code}Durable Task Plugin (durable-task): 1. 26 28 Pipeline: Nodes and Processes (workflow-durable-task-step): 2. 25 26 Nexus Artifact Uploader (nexus-artifact-uploader): 2.10 GitHub Branch Source Plugin (github-branch-source): 2.4.1 Pipeline: SCM Step (workflow-scm-step): 2.7 Pipeline (workflow-aggregator): 2.6 Pipeline: API (workflow-api): 2. 31 33 Pipeline: Declarative (pipeline-model-definition): 1.3.2 Pipeline: GitHub Groovy Libraries (pipeline-github-lib): 1.0 Ant Plugin (ant): 1. 8 9 Apache HttpComponents Client 4.x API Plugin (apache-httpcomponents-client-4-api): 4.5.5-3.0 Workspace Cleanup Plugin (ws-cleanup): 0.36 Command Agent Launcher Plugin (command-launcher): 1.2 SSH Slaves plugin (ssh-slaves): 1.28.1 Windows Slaves Plugin (windows-slaves): 1.3.1 _javascript_ GUI Lib: Moment.js bundle plugin (momentjs): 1.1.1 Pipeline: Basic Steps (workflow-basic-steps): 2.12 Lockable Resources plugin (lockable-resources): 2.3 JDK Tool Plugin (jdk-tool): 1.1 Pipeline: REST API Plugin (pipeline-rest-api): 2.10 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.12 Folders Plugin (cloudbees-folder): 6. 6 7 JSch dependency plugin (jsch): 0.1.54.2 Build Timeout (build-timeout): 1.19 Job Configuration History Plugin (jobConfigHistory): 2.18.3 Credentials Binding Plugin (credentials-binding): 1. 16 17 PAM Authentication plugin (pam-auth): 1.4 Token Macro Plugin (token-macro): 2.5 Matrix Authorization Strategy Plugin (matrix-auth): 2.3 Docker Commons Plugin (docker-commons): 1.13 Pipeline: Milestone Step (pipeline-milestone-step): 1.3.1 LDAP Plugin (ldap): 1.20 Green Balls (greenballs): 1.15 External Monitor Job Type Plugin (external-monitor-job): 1.7 Copy Artifact Plugin (copyartifact): 1.41 Resource Disposer Plugin (resource-disposer): 0.12 Pipeline: Build Step (pipeline-build-step): 2.7 _javascript_ GUI Lib: Handlebars bundle plugin (handlebars): 1.1.1 Pipeline: Supporting APIs (workflow-support): 2. 21 22 Gradle Plugin (gradle): 1.29 Pipeline: Job (workflow-job): 2. 26 30-rc928.54893f9a5f5c Structs Plugin (structs): 1.17 embeddable-build-status (embeddable-build-status): 1.9 Pipeline: Groovy (workflow-cps): 2.60 Matrix Project Plugin (matrix-project): 1.13 Simple Theme Plugin (simple-theme-plugin): 0.5.1 GitHub Authentication plugin (github-oauth): 0.29 Branch API Plugin (branch-api): 2. 1.1Trilead API Plugin (trilead-api): 1. 0. 20 1 GitHub API Plugin (github-api): 1.92 Pipeline: Stage View Plugin (pipeline-stage-view): 2.10 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5 Pipeline: Stage Tags Metadata (pipeline-stage-tags-metadata): 1.3.2 bouncycastle API Plugin (bouncycastle-api): 2.17 Jackson 2 API Plugin (jackson2-api): 2. 8 9 . 11 7 . 3 1 Email Extension Plugin (email-ext): 2.63 _javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1 Docker Pipeline (docker-workflow): 1.17 GitHub plugin (github): 1.29.3 Pipeline: Multibranch (workflow-multibranch): 2.20 JUnit Plugin (junit): 1.26.1 SSH Credentials Plugin (ssh-credentials): 1.14 Node and Label parameter plugin (nodelabelparameter): 1.7.2 Credentials Plugin (credentials): 2.1.18 Nexus Platform Plugin (nexus-jenkins-plugin): 3.3.20181025-134249.614c5f4 Authentication Tokens API Plugin (authentication-tokens): 1.3 Script Security Plugin (script-security): 1.48 _javascript_ GUI Lib: jQuery bundles (
[JIRA] (JENKINS-54733) After 10 builds Pipeline Stage View disappears.
Title: Message Title Omar Malik commented on JENKINS-54733 Re: After 10 builds Pipeline Stage View disappears. When looking at the stack trace I see. Stack trace java.lang.IllegalStateException: Matching start node 3 lost from deserialization at org.jenkinsci.plugins.workflow.graph.BlockEndNode.getStartNode(BlockEndNode.java:65) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.getNodeType(ForkScanner.java:190) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:592) at org.jenkinsci.plugins.workflow.graphanalysis.AbstractFlowScanner.next(AbstractFlowScanner.java:212) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.next(ForkScanner.java:564) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:768) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:633) at com.cloudbees.workflow.rest.external.RunExt.createNew(RunExt.java:321) at com.cloudbees.workflow.rest.external.RunExt.create(RunExt.java:309) at com.cloudbees.workflow.rest.external.JobExt.create(JobExt.java:131) at com.cloudbees.workflow.rest.endpoints.JobAPI.doRuns(JobAPI.java:69) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30) Caused: java.lang.RuntimeException: Unexpected exception while serving JSON at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:860) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:237) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:214) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilte
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Notes: https://ci.xwiki.org/job/XWiki/job/xwiki-commons/job/master/447/console [withMaven] Publishers: Invoker Publisher: 255 ms, Junit Publisher: 49 ms, Concordion Publisher: 42 ms, Dependencies Fingerprint Publisher: 9327 ms, Findbugs Publisher: 27 ms, JGiven Publisher: 63 ms, Jacoco Publisher: 28 ms, Pipeline Graph Publisher: 462 ms, SpotBugs Publisher: 19 ms, Open Task Scanner Publisher: 12 ms [withMaven] Publishers: Invoker Publisher: 624 ms, Junit Publisher: 4588 ms, Concordion Publisher: 37 ms, Dependencies Fingerprint Publisher: 22172 ms, Findbugs Publisher: 21 ms, JGiven Publisher: 46 ms, Jacoco Publisher: 29 ms, Pipeline Graph Publisher: 760 ms, SpotBugs Publisher: 27 ms, Open Task Scanner Publisher: 11 ms [withMaven] Publishers: Junit Publisher: 127 ms, Dependencies Fingerprint Publisher: 341 ms, Pipeline Graph Publisher: 5 ms, Open Task Scanner Publisher: 9 ms [withMaven] Publishers: Invoker Publisher: 83 ms, Junit Publisher: 39867 ms, Concordion Publisher: 21 ms, Dependencies Fingerprint Publisher: 22369 ms, Findbugs Publisher: 9 ms, JGiven Publisher: 31 ms, Jacoco Publisher: 11 ms, Pipeline Graph Publisher: 398 ms, SpotBugs Publisher: 8 ms, Open Task Scanner Publisher: 13 ms [withMaven] Publishers: Junit Publisher: 783 ms, Dependencies Fingerprint Publisher: 505 ms, Pipeline Graph Publisher: 5 ms, Open Task Scanner Publisher: 9 ms [withMaven] Publishers: Invoker Publisher: 482 ms, Junit Publisher: 65348 ms, Concordion Publisher: 20 ms, Dependencies Fingerprint Publisher: 27459 ms, Findbugs Publisher: 7 ms, JGiven Publisher: 37 ms, Jacoco Publisher: 10 ms, Pipeline Graph Publisher: 1071 ms, SpotBugs Publisher: 8 ms, Open Task Scanner Publisher: 57 ms [withMaven] Publishers: Junit Publisher: 1305 ms, Dependencies Fingerprint Publisher: 651 ms, Pipeline Graph Publisher: 6 ms, Open Task Scanner Publisher: 12 ms Add Comment
[JIRA] (JENKINS-54674) PCT: Add Docker packaging for Java 11
Title: Message Title Adrien Lecharpentier assigned an issue to Adrien Lecharpentier Jenkins / JENKINS-54674 PCT: Add Docker packaging for Java 11 Change By: Adrien Lecharpentier Assignee: Adrien Lecharpentier 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Vincent Massol commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Cyrille Le Clerc Yes but thats on commons and we almost never have problems on commons. The main problems we have are on xwiki-platform, i.e. https://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/master/ (it's executing right now). Thanks! 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Vincent Massol edited a comment on JENKINS-49337 Re: InterruptedException - Exception processing the logs [~cleclerc] Yes but thats that's on commons and we almost never have problems on commons. The main problems we have are on xwiki-platform, i.e. https://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/master/ (it's executing right now). Thanks! 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-54766) Missing target dependency to sue demo-* targets
Title: Message Title Adrien Lecharpentier started work on JENKINS-54766 Change By: Adrien Lecharpentier Status: Open In Progress 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-54674) PCT: Add Docker packaging for Java 11
Title: Message Title Adrien Lecharpentier started work on JENKINS-54674 Change By: Adrien Lecharpentier Status: Open In Progress 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-54766) Missing target dependency to sue demo-* targets
Title: Message Title Adrien Lecharpentier updated JENKINS-54766 Jenkins / JENKINS-54766 Missing target dependency to sue demo-* targets Change By: Adrien Lecharpentier Status: In Progress Review 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-54462) PCT: Add support of running CLI with Java 11
Title: Message Title Adrien Lecharpentier commented on JENKINS-54462 Re: PCT: Add support of running CLI with Java 11 Oleg Nenashev I think you can mark this one as solved as we merged PR-84 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-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title Baptiste Mathus started work on JENKINS-54755 Change By: Baptiste Mathus Status: Open In Progress 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-54758) Plugin Manager is available on AWS flavor
Title: Message Title Baptiste Mathus updated JENKINS-54758 Jenkins / JENKINS-54758 Plugin Manager is available on AWS flavor Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed 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-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title Baptiste Mathus updated JENKINS-54755 Jenkins / JENKINS-54755 Disable "Require branches to be up to date before merging" on Evergreen repo Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed 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-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54755 Disable "Require branches to be up to date before merging" on Evergreen repo Change By: Baptiste Mathus Attachment: updated new configuration.png 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-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title Baptiste Mathus updated JENKINS-54755 Jenkins / JENKINS-54755 Disable "Require branches to be up to date before merging" on Evergreen repo Change By: Baptiste Mathus Status: In Progress Review 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-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title Baptiste Mathus commented on JENKINS-54755 Re: Disable "Require branches to be up to date before merging" on Evergreen repo Done. New config: 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-54100) Need plugin that has incompatible format from one version to the next to test evergreen snapshot restore
Title: Message Title Baptiste Mathus closed an issue as Won't Fix I don't think I'll need to do this this way finally. Jenkins / JENKINS-54100 Need plugin that has incompatible format from one version to the next to test evergreen snapshot restore Change By: Baptiste Mathus Status: Open Closed Resolution: Won't Fix 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-54725) Do not publish older releases for JDK1 (esp. LTS)
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54725 Do not publish older releases for JDK1 (esp. LTS) Change By: Baptiste Mathus Assignee: Carlos Sanchez Baptiste Mathus 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-54725) Do not publish older releases for JDK1 (esp. LTS)
Title: Message Title Baptiste Mathus started work on JENKINS-54725 Change By: Baptiste Mathus Status: Open In Progress 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Vincent Massol don't worry I didn't celebrate victory. I saw that the hard part is xwiki-platform and that we have to wait for few more hours to see the result. Moreover, I don't ignore that your MySQL database is probably empty today so the performances may evolve with more volume in the database. Note on xwiki-commons build: dependencies fingerprinting and junit test archiving can take huge amount of time (resp ~22172ms and ~ 65348ms). I'm not sure that parallelising these tasks would improve the duration of the build as I suspect that the contention is IOs either on the agent or on the master. 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-49337 Re: InterruptedException - Exception processing the logs [~vmassol] don't worry I didn't celebrate victory. I saw that the hard part is xwiki-platform and that we have to wait for few more hours to see the result. Moreover, I don't ignore that your MySQL database is probably empty today so the performances may evolve with more volume in the database. Note on xwiki-commons build: dependencies fingerprinting and junit test archiving can take huge amount of time (resp ~22172ms and ~ 65348ms). I'm not sure that parallelising these tasks would improve the duration of the build as I suspect that the contention is IOs either on the agent or on the master. Note: the try/catch on InterruptedException is not great, I'm about to improve the collect of troubleshooting data. 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-54768) not able to save the build job after creating a job of zap and jenkins integration
Title: Message Title Mayuri Joshi created an issue Jenkins / JENKINS-54768 not able to save the build job after creating a job of zap and jenkins integration Issue Type: Bug Assignee: Goran Sarenkapa Components: zaproxy-plugin Created: 2018-11-22 10:50 Environment: Jenkins ver 2.32 official owasp zaproxy plugin Labels: plugin Priority: Minor Reporter: Mayuri Joshi when I am trying to create a build to run a any scan (spider scan or active scan). for spider scan the build is giving correct expected result but when I am trying to configure that build and try to do changes in the same build job It is giving me the below-mentioned error. Please help me for the same javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize hudson.model.Project#builders for class hudson.model.FreeStyleProject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) at hudson.util.PluginServletFilt
[JIRA] (JENKINS-54768) not able to save the build job after creating a job of zap and jenkins integration
Title: Message Title Mayuri Joshi created an issue Jenkins / JENKINS-54768 not able to save the build job after creating a job of zap and jenkins integration Issue Type: Bug Assignee: Goran Sarenkapa Components: zaproxy-plugin Created: 2018-11-22 10:50 Environment: Jenkins ver 2.32 official owasp zaproxy plugin Labels: plugin Priority: Minor Reporter: Mayuri Joshi when I am trying to create a build to run a any scan (spider scan or active scan). for spider scan the build is giving correct expected result but when I am trying to configure that build and try to do changes in the same build job It is giving me the below-mentioned error. Please help me for the same javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize hudson.model.Project#builders for class hudson.model.FreeStyleProject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) at hudson.util.PluginServletFilt
[JIRA] (JENKINS-54768) not able to save the build job after creating a job of zap and jenkins integration
Title: Message Title Mayuri Joshi assigned an issue to Ulli Hafner Jenkins / JENKINS-54768 not able to save the build job after creating a job of zap and jenkins integration Change By: Mayuri Joshi Assignee: Goran Sarenkapa Ulli Hafner 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-54674) PCT: Add Docker packaging for Java 11
Title: Message Title Adrien Lecharpentier commented on JENKINS-54674 Re: PCT: Add Docker packaging for Java 11 Oleg Nenashev would it be acceptable to use something like getopts in the shell script to ease the configuration of the script? This way, with one arguments, like --jdk11, we could set the required JVM and CLI parameters. I would also have to review the script a bit. 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-54759) Groovy Parsers - improve help text
Title: Message Title Norbert Lange updated an issue Jenkins / JENKINS-54759 Groovy Parsers - improve help text Change By: Norbert Lange Summary: Groovy Parsers - improve help text Issue Type: Bug Improvement 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-54759) Groovy Parsers
Title: Message Title Norbert Lange commented on JENKINS-54759 Re: Groovy Parsers Scanning of the console log is done on the master currently, all other files are scanned on the agentDo you have a better idea? I would try to move all processing to the agent(s), its not obvious to me why this split exists (has to exist). Can’t you pipe your log output to a file on the agent? Yes I can, but not without issues. Some variants: not piping would be the most clear, and similar to the scripts you would run on a local build piping it just to a file will remove all visible status during execution naively splitting it (eg. | tee file.log) will mean the error state of the script doing the build will vanish. see here additionally storing and restoring the errors state of the script adds boilerplate code That's why I asked about a recommendation (a bug tracker is the wrong place, but you don't have a forum?) As for the split, keep the help-text issue here, and handle the rest in JENKINS-52237? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54769) Ticket creation fails while trying to set mandatory select list field
Title: Message Title
Harshad Kashikar created an issue
Jenkins / JENKINS-54769
Ticket creation fails while trying to set mandatory select list field
Issue Type:
Bug
Assignee:
Catalin Luta
Components:
jiratestresultreporter-plugin
Created:
2018-11-22 11:49
Environment:
Jenkins version: 2.133 Plugin version: 2.0.7
Priority:
Major
Reporter:
Harshad Kashikar
Below is the code snippet for creating defect,
testDataPublishers: [
jiraTestResultReporter(
configs: [
jiraStringField(fieldKey: 'summary', value: '${DEFAULT_SUMMARY}'),
jiraStringField(fieldKey: 'description', value: '${DEFAULT_DESCRIPTION}'),
jiraStringArrayField(fieldKey: 'labels', values: [jiraArrayEntry(value: 'Jenkins'), jiraArrayEntry(value:'Automation')]),
jiraStringArrayField(fieldKey: 'components', values: [jiraArrayEntry(value: 'System Test')]),
jiraStringField(fieldKey:'customfield_19030', value:"No - New Use Case" )
],
projectKey: 'CAS',
issueType: '1',
autoRaiseIssue: true,
autoResolveIssue: false,
autoUnlinkIssue: false,
)
]
field customfield_19030 is a custom field of type select (Single select). I tied using both jiraStringField as well as jir
[JIRA] (JENKINS-54770) A new client object is created each time the plugin needs to connection to K8s
Title: Message Title Félix Belzunce Arcos started work on JENKINS-54770 Change By: Félix Belzunce Arcos Status: Open In Progress 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-54770) A new client object is created each time the plugin needs to connection to K8s
Title: Message Title Félix Belzunce Arcos assigned an issue to Félix Belzunce Arcos Jenkins / JENKINS-54770 A new client object is created each time the plugin needs to connection to K8s Change By: Félix Belzunce Arcos Assignee: Carlos Sanchez Félix Belzunce Arcos 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-54770) A new client object is created each time the plugin needs to connection to K8s
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-54770 A new client object is created each time the plugin needs to connection to K8s Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-11-22 11:53 Priority: Major Reporter: Félix Belzunce Arcos Max connections to Kubernetes API is set to 32 by default in the shared cloud configuration but this doesn't prevent the K8s plugin to open hundreds of connections to the K8s API, each connection using 2 threads leading to an exhaustion of the available memory. The consequences of the bug are instabilities and crash of masters when all available memory in the master container is exhausted. Each time the plugin needs to connect to K8s, it creates a new client object. Each client is limited to 32 connections but there's no limit on the number of clients created. The client object should be a singleton. Add Comment
[JIRA] (JENKINS-41074) UX Issue with Polling in Multibranch Pipeline
Title: Message Title Hezi Zisman commented on JENKINS-41074 Re: UX Issue with Polling in Multibranch Pipeline What is the recommenations for those who use webhooks and branch indexing? We expirencing allot of duplicated builds... Disabling branch indexing will cause new branches not to get indexed and built Disabling webhooks will break a build per push bond we need... 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title fisnik hajredini commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. The issue doesnt seem that minor anymore. The [variant] is not searchable through CTRL+F. Also if u view the logs as plain text, you get no information of the variants. Having ~10MB of logs with >5 different variants makes it difficult to track the variant. 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-54771) NPE in logs after using groovy script to add slave template
Title: Message Title
Chris Penhaligon created an issue
Jenkins / JENKINS-54771
NPE in logs after using groovy script to add slave template
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Attachments:
AddNewEC2Slave.groovy
Components:
ec2-plugin
Created:
2018-11-22 12:06
Environment:
jenkins = 2.138.3 ec2-plugin = 1.41
Labels:
groovy ec2 ec2-plugin aws npe
Priority:
Minor
Reporter:
Chris Penhaligon
We've written a groovy script (sample attached) that we're hoping to use to add slave templates to our EC2 cloud. At the moment, we're only executing via the script console but we have plans to eventually automate the process and run it as part of a build. The script executes successfully and when we check under the EC2 cloud settings, we can see our new template there. However, when we try to run a build with a label matching that of the new slave template, we see the following node provisioning error in the logs:
hudson.plugins.ec2.EC2Cloud provision
INFO: SlaveTemplate{ami='', labels='oracle-dbupgrade-f30e32f
'}. Attempting to provision slave needed by excess workload of 1 units
hudson.triggers.SafeTimerTask run
SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker
[JIRA] (JENKINS-54753) SV 5.00 is not supported
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54753 SV 5.00 is not supported Change By: Daniel Gront Labels: SV 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-54458) regression in UFT discovery when new Jenkins plugin is used with old Octane - tests are not reported to Octane
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54458 regression in UFT discovery when new Jenkins plugin is used with old Octane - tests are not reported to Octane Change By: Daniel Gront Labels: octane 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Vincent Massol commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs > Vincent Massol don't worry I didn't celebrate victory. I saw that the hard part is xwiki-platform and that we have to wait for few more hours to see the result. Moreover, I don't ignore that your MySQL database is probably empty today so the performances may evolve with more volume in the database. > Note on xwiki-commons build: dependencies fingerprinting and junit test archiving can take huge amount of time (resp ~22172ms and ~ 65348ms). I'm not sure that parallelising these tasks would improve the duration of the build as I suspect that the contention is IOs either on the agent or on the master. I'm not sure what you mean with parallelising these tasks. Is that something you're working on or an idea you were having? Is there something to do on my side? Regarding fingerprinting I'm keeping since I think it's necessary to perform automatic trigger or downstream jobs. This is the comment I had put in the XWiki pipeline job at https://github.com/xwiki/xwiki-jenkins-pipeline/blob/d0b2330b1cedad2f2a38b3eb575cc7c81d4d0bdd/vars/xwikiBuild.groovy#L61 : > // fingerprintDependencies = false (default to true since it's required by the withMaven dependency graph feature >// in order to have builds trigger automatically other builds when dependencies are built) Could you confirm that it's correct? > Note: the try/catch on InterruptedException is not great, I'm about to improve the collect of troubleshooting data. I assume you're referring to some try/catch you have in Jenkins's code. Let me know when some new version is available and I'll upgrade. Thanks for working actively on this! 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
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Vincent Massol edited a comment on JENKINS-49337 Re: InterruptedException - Exception processing the logs bq. Vincent Massol don't worry I didn't celebrate victory. I saw that the hard part is xwiki-platform and that we have to wait for few more hours to see the result. Moreover, I don't ignore that your MySQL database is probably empty today so the performances may evolve with more volume in the database.:)bq. Note on xwiki-commons build: dependencies fingerprinting and junit test archiving can take huge amount of time (resp ~22172ms and ~ 65348ms). I'm not sure that parallelising these tasks would improve the duration of the build as I suspect that the contention is IOs either on the agent or on the master.I'm not sure what you mean with parallelising these tasks. Is that something you're working on or an idea you were having? Is there something to do on my side?Regarding fingerprinting I'm keeping since I think it's necessary to perform automatic trigger or downstream jobs. This is the comment I had put in the XWiki pipeline job at https://github.com/xwiki/xwiki-jenkins-pipeline/blob/d0b2330b1cedad2f2a38b3eb575cc7c81d4d0bdd/vars/xwikiBuild.groovy#L61 : bq. // fingerprintDependencies = false (default to true since it's required by the withMaven dependency graph featurebq. // in order to have builds trigger automatically other builds when dependencies are built)Could you confirm that it's correct? > bq. Note: the try/catch on InterruptedException is not great, I'm about to improve the collect of troubleshooting data.I assume you're referring to some try/catch you have in Jenkins's code. Let me know when some new version is available and I'll upgrade.Thanks for working actively on this! 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+unsubsc
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Vincent Massol edited a comment on JENKINS-49337 Re: InterruptedException - Exception processing the logs > bq. Vincent Massol don't worry I didn't celebrate victory. I saw that the hard part is xwiki-platform and that we have to wait for few more hours to see the result. Moreover, I don't ignore that your MySQL database is probably empty today so the performances may evolve with more volume in the database.:) > bq. Note on xwiki-commons build: dependencies fingerprinting and junit test archiving can take huge amount of time (resp ~22172ms and ~ 65348ms). I'm not sure that parallelising these tasks would improve the duration of the build as I suspect that the contention is IOs either on the agent or on the master.I'm not sure what you mean with parallelising these tasks. Is that something you're working on or an idea you were having? Is there something to do on my side?Regarding fingerprinting I'm keeping since I think it's necessary to perform automatic trigger or downstream jobs. This is the comment I had put in the XWiki pipeline job at https://github.com/xwiki/xwiki-jenkins-pipeline/blob/d0b2330b1cedad2f2a38b3eb575cc7c81d4d0bdd/vars/xwikiBuild.groovy#L61 : > bq. // fingerprintDependencies = false (default to true since it's required by the withMaven dependency graph feature > bq. // in order to have builds trigger automatically other builds when dependencies are built)Could you confirm that it's correct?> Note: the try/catch on InterruptedException is not great, I'm about to improve the collect of troubleshooting data.I assume you're referring to some try/catch you have in Jenkins's code. Let me know when some new version is available and I'll upgrade.Thanks for working actively on this! 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
[JIRA] (JENKINS-54753) SV 5.00 is not supported
Title: Message Title Pavel Chuchma updated JENKINS-54753 Jenkins / JENKINS-54753 SV 5.00 is not supported Change By: Pavel Chuchma Status: In Progress Fixed but Unreleased Resolution: Fixed 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-54772) computer//systemInfo doesn't report full Environment
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-54772 computer//systemInfo doesn't report full Environment Issue Type: Bug Assignee: Pavel Janoušek Components: core Created: 2018-11-22 12:23 Priority: Minor Reporter: Pavel Janoušek computer//systemInfo page gather values for the table of environment variables from EnvVarsSlaveInfo class which uses Computer.getEnvVars() resp. Computer.getEnvironment() for obtaining an EnvVars structure. The EnvVars class stores values as a TreeMap with the case-insensitive comparator. When the keys are different, but the difference is only in character cases, it stores all such keys in one key. It is un-deterministic which environment variable name you will see, it depends on the order returned by System.getenv() (the first occurrence is used as the key for map) - it's a natural behavior of TreeMap. In case you have more keys with a difference in the case character(s) only you don't have a real view what is exactly the running environment. EnvVars is used in many cases in the core hence I don't want to break a backward-compatibility so I'd propose a fix that don't use EnvVars for display this output, but obtain a full real environment variable collection from the agent at the time of page generation.
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title Reinhold Füreder commented on JENKINS-41845 Re: Suppress default pipeline output Jesse Glick Can it be that this ability to collapse sections with "(hide)" links is actually broken? Please note that I have not even known that something like this exists, so either I have never noticed that because I am blind, or are these links (that only appear via mouse over) actually new? (I just updated Jenkins plugins – and having a lot of guts – including "workflow-job:2.29") 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-47213) Opening a PR when the branch is still building with "Exclude branches that are also filed as PRs" leads to a never ending build in BitBucket
Title: Message Title Thomas Keller commented on JENKINS-47213 Re: Opening a PR when the branch is still building with "Exclude branches that are also filed as PRs" leads to a never ending build in BitBucket Yeah, I think this is a duplicate of JENKINS-45643. 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-45643) Bitbucket PRs are blocked by excluded branches not being able to report progress
Title: Message Title Thomas Keller commented on JENKINS-45643 Re: Bitbucket PRs are blocked by excluded branches not being able to report progress This is really a blocker for the usage of this plugin. The only way to circumvent this issue is to build each PR twice, by disabling the option "exclude branches that are also filed as PRs", but this will just raise the load on the node for no reason. I figured if a branch pattern could be applied that would only apply to non-PR branches this could also be worked around (by including only named, important branches there), but sadly, the implemented regex / wildcard filters read NOTE: this filter will be applied to all branch like things, including change requests so this is not an option. Any reason why the quickfix from Benjamin Fuchs hasn't been considered yet? 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-54773) Jacoco plugin 3.0.4 ignores minimum****Coverage options
Title: Message Title Dmitry Zhukov created an issue Jenkins / JENKINS-54773 Jacoco plugin 3.0.4 ignores minimumCoverage options Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2018-11-22 12:48 Priority: Critical Reporter: Dmitry Zhukov Jacoco plugin ignores minimum***Coverage options and sets it to 0 when maximum***Coverage weren't set. We call Jacoco this way (pipeline stage step) jacoco(execPattern: '**/*.exec', changeBuildStatus: true, exclusionPattern: '**/*Test*.class', inclusionPattern: '**/*.class', minimumMethodCoverage: '10') But in log I see this: Health thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0] On the other side, in case when jacoco calls this way (we've added maximumMethodCoverage option): jacoco(execPattern: '**/*.exec', changeBuildStatus: true, exclusionPattern: '**/*Test*.class', inclusionPattern: '**/*.class', minimumMethodCoverage: '10', maximumMethodCoverage: '80') And in log something new: Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=10, maxM
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Andrew Sumner started work on JENKINS-50976 Change By: Andrew Sumner Status: Open In Progress 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-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Andrew Sumner Status: Resolved Closed 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-54773) Jacoco plugin 3.0.4 ignores minimum****Coverage options
Title: Message Title
Dmitry Zhukov updated an issue
Jenkins / JENKINS-54773
Jacoco plugin 3.0.4 ignores minimumCoverage options
Change By:
Dmitry Zhukov
Jacoco plugin ignores minimumCoverage options and sets it to 0 when maximumCoverage weren't set. We call Jacoco this way (pipeline stage step){code:java}jacoco(execPattern: '**/*.exec', changeBuildStatus: true, exclusionPattern: '**/*Test*.class', inclusionPattern: '**/*.class', minimumMethodCoverage: '10'){code} But in log I see this: {code:java} Health thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0] {code} On the other side, in case when jacoco calls this way (we've added maximumMethodCoverage option): {code:java}jacoco(execPattern: '**/*.exec', changeBuildStatus: true, exclusionPattern: '**/*Test*.class', inclusionPattern: '**/*.class', minimumMethodCoverage: '10', maximumMethodCoverage: '80') {code}And in log something new:{code:java}Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=10, maxMethod=80, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0]{code} Probably, issue in the class JacocoHealthReportThresholds (package hudson.plugins.jacoco) in method public void ensureValid(), e.g.: # maxClass was parsed as 0 (not set) and applyRange returns 0 ; # minClass was set to 10 and applyRange is called with params 0, 10, 0 and return 0 . See: [ https://github.com/jenkinsci/jacoco-plugin/blob/master/src/main/java/hudson/plugins/jacoco/JacocoHealthReportThresholds.java#L49-L59 ]
Add Comment
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Andrew Sumner resolved as Fixed Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Andrew Sumner Status: In Progress Resolved Resolution: Fixed 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-53734) Declarative pipeline - Support for parallel stages inside sequential stages
Title: Message Title
Alexey Marin commented on JENKINS-53734
Re: Declarative pipeline - Support for parallel stages inside sequential stages
I agree that this will be very useful. I use sequential stages to lock a single resource (DB) for multiple stages (as suggested in JENKINS-43336) For example, a pipeline like this one is currently impossible:
pipeline {
agent any
stages {
stage ('Non-production') {
options {
lock 'DB1'
}
stages {
stage ('Deploy') {
steps {
echo 'Deploy'
}
}
stage ('Test') {
parallel {
stage ('Unit testing') {
steps {
echo 'Unit'
}
}
stage ('E2E testing') {
steps {
echo 'E2E'
}
}
}
}
}
}
stage ('Production') {
stages {
stage ('Deploy') {
steps {
echo 'Deploy'
}
}
}
}
}
}
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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Gabriel Lavoie commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Ivan Fernandez Calvo thanks for the explanation. This said, how much time can I expect before my PR is reviewed and possibly integrated in a new version of the ssh-slaves 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-54674) PCT: Add Docker packaging for Java 11
Title: Message Title Oleg Nenashev commented on JENKINS-54674 Re: PCT: Add Docker packaging for Java 11 Yes, it will acceptable imho 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down review and merged in the trilead-ssh probably this week (it depends on my spare time), integrated on trilead-api can be also this week, for the ssh-slaves will not be time soon because as I said it depends on the trilead-ssh core plugin, but if you are testing stuff I can release a beta version with the dependency of the trilead-api. It probably requires to patch some plugins to do not break the thing. 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-54768) not able to save the build job after creating a job of zap and jenkins integration
Title: Message Title Ulli Hafner commented on JENKINS-54768 Re: not able to save the build job after creating a job of zap and jenkins integration Why did you assign the issue to me? 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs https://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/master/1211 > Regarding fingerprinting I'm keeping since I think it's necessary to perform automatic trigger or downstream jobs. This is the comment I had put in the XWiki pipeline job at https://github.com/xwiki/xwiki-jenkins-pipeline/blob/d0b2330b1cedad2f2a38b3eb575cc7c81d4d0bdd/vars/xwikiBuild.groovy#L61 : > // fingerprintDependencies = false (default to true since it's required by the withMaven dependency graph feature > // in order to have builds trigger automatically other builds when dependencies are built) > Could you confirm that it's correct? Fingerprinting is NOT required to trigger downstream pipelines. The "Pipeline Graph Publisher" is self sufficient and does not need any other publisher. It works on the semantic dependencies between Maven artifacts to trigger downstream pipelines > I assume you're referring to some try/catch you have in Jenkins's code. Let me know when some new version is available and I'll upgrade. Correct, improvement of the try/catch in the plugin https://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/master/1211 [withMaven] Publishers: Invoker Publisher: 20 ms, Junit Publisher: 18273 ms, Concordion Publisher: 4 ms, Dependencies Fingerprint Publisher: 115889 ms, Findbugs Publisher: 3 ms, JGiven Publisher: 24 ms, Jacoco Publisher: 3 ms, Pipeline Graph Publisher: 797 ms, SpotBugs Publisher: 3 ms, Open Task Scanner Publisher: 13 ms [withMaven] Publishers: Dependencies Fingerprint Publisher: 5 ms, JGiven Publisher: 1 ms, Pipeline Graph Publisher: 2 ms, Open Task Scanner Publisher: 14 ms [withMaven] Publishers: Junit Publisher: 5753 ms, Dependencies Fingerprint Publisher: 2941 ms, Pipeline Graph Publisher: 17 ms, Open Task Scanner Publisher: 18 ms [withMaven] Publishers: Junit Publisher: 3718 ms, Dependencies Fingerprint Publisher: 14 ms, JGiven Publisher: 3 ms, Pipeline Graph Publisher: 10 ms, Open Task Scanner Publisher: 17 ms [withMaven] Publishers: Junit Publisher: 8112 ms, Dependencies Fingerprint Publisher: 6 ms, Pipeline Graph Publisher: 4 ms, Open Task Scanner Publisher: 15 ms [withMaven] Publishers: Junit Publisher: 115970 ms, Dependencies Fingerprint Publisher: 385 ms, JGiven Publisher: 24 ms, Pipeline Graph Publisher: 3 ms, Open Task Scanner Publisher: 102 ms [withMaven] Publishers: Junit Publisher: 152231 ms, Dependencies Fingerprint Publisher: 317 ms, Pipeline Graph Publisher: 7 ms, Open Task Scanner Publisher: 223 ms [withMaven] Publishers: Junit Publisher: 4669 ms, Dependencies Fingerprint Publisher: 1585 ms, Pipeline Graph Publisher: 13 ms, Open Task Scanner Publisher: 19 ms [withMaven] Publishers: Invoker Publisher: 1 ms, Junit Publisher: 8472 ms, Dependencies Fingerprint Publisher: 27 ms, JGiven Publisher: 7 ms, Pipeline Graph Publisher: 12 ms, Open Task Scanner Publisher: 18 ms [withMaven] Publishers: Junit Publisher: 11656 ms, Dependencies Fingerprint Publisher: 585 ms, Pipeline Graph Publisher: 2 ms, Open Task Scanner Publisher: 7 ms The pipeline seems to have run without any problem caused by withMaven
[JIRA] (JENKINS-54768) not able to save the build job after creating a job of zap and jenkins integration
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-54768 not able to save the build job after creating a job of zap and jenkins integration Change By: Ulli Hafner Assignee: Ulli Hafner 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Gabriel Lavoie commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down I can wait until an official release. Thank you for the heads up! 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-44310) Generic fields for server credentials (Maven settings)
Title: Message Title Michele Vanini commented on JENKINS-44310 Re: Generic fields for server credentials (Maven settings) Also proxy settings missing credentials management in config-file-provider..there are any chances to achieve this enhancement? 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-54774) svn: E200015: E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Marco Andraschko created an issue Jenkins / JENKINS-54774 svn: E200015: E200015: ISVNAuthentication provider did not provide credentials Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: subversion-plugin Created: 2018-11-22 13:45 Environment: Jenkins ver. 2.138.2 Subversion Plug-in 2.12.1 Pipeline: Multibranch 2.20 WindowsServer 2012R2 Priority: Major Reporter: Marco Andraschko Hello, the 'Subversion Polling Log' shows the following error for all svn:externals: Received SCM poll call on master for latest on Nov 22, 2018 2:06:01 PM Using sole credentials in realm ‘< https://subversion01:443 > VisualSVN Server’ ERROR: Failed to check repository revision for https://subversion01/svn/WindowsSoftware/Tools/InternalManagement/BuildManagement/tags/Hilscher/1.0100.5.4534/src org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:66) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:910) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:702) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.
[JIRA] (JENKINS-54774) svn: E200015: E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-54774 svn: E200015: E200015: ISVNAuthentication provider did not provide credentials Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Vincent Massol commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Fingerprinting is NOT required to trigger downstream pipelines. The "Pipeline Graph Publisher" is self sufficient and does not need any other publisher. It works on the semantic dependencies between Maven artifacts to trigger downstream pipelines ok cool, I'll try to remove fingerprinting of dependencies. Could you tell in which case fingerprinting of dependencies is useful? I could not see that info on https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-ReportPublishers ? The pipeline seems to have run without any problem caused by withMaven Yes this is cool and encouraging! 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-54772) computer//systemInfo doesn't report full Environment
Title: Message Title Pavel Janoušek started work on JENKINS-54772 Change By: Pavel Janoušek Status: Open In Progress 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-54645) Send queue data in JSON Payload
Title: Message Title Jakub Bochenski commented on JENKINS-54645 Re: Send queue data in JSON Payload Markus Winter I like the idea of having an extension point for adding extra data. This should allow people to opt-in for the extra data without having to add a ton of switches to the main 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-48148) writeJson step to serialize to string variable
Title: Message Title Dmitry Bigunyak commented on JENKINS-48148 Re: writeJson step to serialize to string variable I'd also love to see this feature implemented, especially that readJSON can read from both file and string variable, would be great if writeJSON would be able to write to string variable. 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-54645) Send queue data in JSON Payload
Title: Message Title Jakub Bochenski reopened an issue Jenkins / JENKINS-54645 Send queue data in JSON Payload Change By: Jakub Bochenski Resolution: Duplicate Status: Closed Reopened 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-54645) Send queue data in JSON Payload
Title: Message Title Jakub Bochenski commented on JENKINS-54645 Re: Send queue data in JSON Payload Mike Delaney why did you close the issue as a duplicate? I don't think we have a duplicate ticket for sending the queue data.. 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-54645) Send queue data in JSON Payload
Title: Message Title Jakub Bochenski edited a comment on JENKINS-54645 Re: Send queue data in JSON Payload [~mwinter69] I like the idea of having an extension point for adding extra data. This should allow people to opt-in for the extra data without having to add a ton of switches to the main plugin > Precondition would be JENKINS-54685 I think.I don't think it's a blocker. Actually maybe it would make sense to have an extension point that could filter/transform the data -- then implement JENKINS-54685 as an EP. 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-54725) Do not publish older releases for JDK1 (esp. LTS)
Title: Message Title Baptiste Mathus updated JENKINS-54725 Jenkins / JENKINS-54725 Do not publish older releases for JDK1 (esp. LTS) Change By: Baptiste Mathus Status: In Progress Review 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-54685) data ecomony
Title: Message Title Jakub Bochenski commented on JENKINS-54685 Re: data ecomony Markus Winter I'm not sure – I think most of it is static, but some aren't: test results build result build (env) variables build duration I think this would require some refactor to split the actually static data from mutable one 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-43469) Artifact is copied from failed promotion
Title: Message Title Dmitry Mikhirev commented on JENKINS-43469 Re: Artifact is copied from failed promotion Are there any chances that someone will start working on this? 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-52035) (Jenkins integration with HP PC for Perf testing)Jenkins doesnt show raw results or complete analysis file , it only shows HTML file as result.
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-52035 (Jenkins integration with HP PC for Perf testing)Jenkins doesnt show raw results or complete analysis file , it only shows HTML file as result. Change By: Daniel Gront Issue Type: Task Improvement 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-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Steve Graham commented on JENKINS-54261 Re: Submit ( go ) on Email Template Testing produces blank screen also fixed in standard release 2.152 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.
