[JIRA] [view-job-filters] (JENKINS-21862) Build Filter (Wrapper) column not properly showing results for Parameterized builds
Jonathan Csanyi updated JENKINS-21862 Build Filter (Wrapper) column not properly showing results for Parameterized builds Change By: Jonathan Csanyi (03/Oct/14 6:49 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven-plugin] (JENKINS-11964) [Regression] Cannot build a single module in a Maven multi-module job with Maven 3
SCM/JIRA link daemon commented on JENKINS-11964 [Regression] Cannot build a single module in a Maven multi-module job with Maven 3 Code changed in jenkins User: Olivier Lamy Path: src/main/java/hudson/maven/MavenBuild.java src/test/java/hudson/maven/AbstractMaven3xBuildTest.java http://jenkins-ci.org/commit/maven-plugin/eceb0289ce3a8ffee6792148fa5aa2ed0032e462 Log: Merge pull request #29 from goober/master JENKINS-11964 Enable single module build for Maven3. Compare: https://github.com/jenkinsci/maven-plugin/compare/299ccd301ea2...eceb0289ce3a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven-plugin] (JENKINS-11964) [Regression] Cannot build a single module in a Maven multi-module job with Maven 3
SCM/JIRA link daemon commented on JENKINS-11964 [Regression] Cannot build a single module in a Maven multi-module job with Maven 3 Code changed in jenkins User: Mathias Åhsberg Path: src/main/java/hudson/maven/MavenBuild.java src/test/java/hudson/maven/AbstractMaven3xBuildTest.java http://jenkins-ci.org/commit/maven-plugin/b3f08bd4411cbf138db34de879c9af638cc7ac95 Log: JENKINS-11964 Enable single module build for Maven3. Pull Request #9 has been the source for the implementation. However, only parts that was needed to enable single module build for Maven3 projects have been used. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Oliver Gondža commented on JENKINS-20769 Failed to execute command Pipe.EOF Andrew Erickson: The LTS changelogs are not reliable in this regard. You are right to say that fix went into 1.554.1. See cloudbees changlog that tends to be accurate: http://release-notes.cloudbees.com/release/Jenkins+OSS+LTS/1.554.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [plugin] (JENKINS-24959) Parameterized Build Report doesn't show any colors for Builds Report
Slick T commented on JENKINS-24959 Parameterized Build Report doesn't show any colors for Builds Report Sorry. I updated this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [plugin] (JENKINS-24959) Parameterized Build Report doesn't show any colors for Builds Report
Slick T reopened JENKINS-24959 Parameterized Build Report doesn't show any colors for Builds Report Change By: Slick T (03/Oct/14 6:16 AM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [view-job-filters] (JENKINS-21862) Build Filter (Wrapper) column not properly showing results for Parameterized builds
Jonathan Csanyi commented on JENKINS-21862 Build Filter (Wrapper) column not properly showing results for Parameterized builds I am noticing this same problem. Basically, none of the wrapper columns seem to work properly. Some (status, weather, num builds) display exactly the same as the unwrapped versions. Others (last success, last failure, last duration) always display N/A. Is there anything I can do to help troubleshoot this issue? I'm running Jenkins 1.582, with version 1.26 of the plugin. -Jonathan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [plugin] (JENKINS-24959) Parameterized Build Report doesn't show any colors for Builds Report
Slick T updated JENKINS-24959 Parameterized Build Report doesn't show any colors for Builds Report Change By: Slick T (03/Oct/14 6:10 AM) Description: Jenkins ver. 1.583Plugin ver. 1.3 Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-12276) Redirect loop on logout with container managed (legacy) security
Daniel Beck commented on JENKINS-12276 Redirect loop on logout with container managed (legacy) security Is this still an issue in recent Jenkins versions? Would you be willing to test a build with an attempt at fixing this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-13712) kill running project raises InterruptedException which is not properly handled
Daniel Beck resolved JENKINS-13712 as Cannot Reproduce kill running project raises InterruptedException which is not properly handled Cannot reproduce on 1.583. If this still occurs on recent (no older than eight weeks) versions of Jenkins, please file a new bug report and explain how to set up a project so this issue can be reproduced. Thanks! Change By: Daniel Beck (03/Oct/14 1:38 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-13903) configure page breaks for first configure after a fresh installation
Daniel Beck resolved JENKINS-13903 as Cannot Reproduce configure page breaks for first configure after a fresh installation Cannot reproduce on 1.565.2, assuming obsolete. Change By: Daniel Beck (03/Oct/14 1:35 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-8499) windows batch command cannot redirect output to file
Daniel Beck commented on JENKINS-8499 windows batch command cannot redirect output to file Does the originally reported issue still occur on recent Jenkins versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-16070) Deadlock using Windows native calls
Daniel Beck updated JENKINS-16070 Deadlock using Windows native calls Change By: Daniel Beck (03/Oct/14 1:25 AM) Labels: jna This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-17131) Some weird exceptions while archiving with raspberry as slave
Daniel Beck updated JENKINS-17131 Some weird exceptions while archiving with raspberry as slave Change By: Daniel Beck (03/Oct/14 1:24 AM) Labels: archive artifact jna raspberry slave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-17611) WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null
Daniel Beck commented on JENKINS-17611 WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null Does this issue still occur on recent Jenkins versions? A few fixes related to symlinks happened in the mean time, so it'd be good to know whether this still occurs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-17945) Downstream Dependency has broken, Also breaks Dependency Graph Plugin, and Build Pipeline Plugin
Daniel Beck commented on JENKINS-17945 Downstream Dependency has broken, Also breaks Dependency Graph Plugin, and Build Pipeline Plugin Do you know whether this has changed since 1.514, what's the current state of this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-13843) envionment variable from label expression, inconsistent casing on nodes
Daniel Beck commented on JENKINS-13843 envionment variable from label _expression_, inconsistent casing on nodes This behaves as designed, as mindbogglingly stupid as it is. Documentation: http://javadoc.jenkins-ci.org/hudson/FilePath.html Resolve as Won't Fix, or relabel as an Improvement? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-13843) envionment variable from label expression, inconsistent casing on nodes
Daniel Beck edited a comment on JENKINS-13843 envionment variable from label _expression_, inconsistent casing on nodes This behaves as designed, as mindbogglingly stupid as it is. Env vars are case insensitive inside Jenkins, and case preserving. Documentation: http://javadoc.jenkins-ci.org/hudson/EnvVars.html Resolve as Won't Fix, or relabel as an Improvement? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory] (JENKINS-18506) Duplicates of user accounts on 'People' view
Daniel Beck commented on JENKINS-18506 Duplicates of user accounts on 'People' view Are you still experiencing this issue on recent versions of Jenkins and the AD plugin? If so, which versions of Jenkins and the plugin? Are you on Windows or Linux? Would you be willing to run a diagnostic script or two to determine the cause? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-18561) InvalidClassException in slave communication
Daniel Beck resolved JENKINS-18561 as Cannot Reproduce InvalidClassException in slave communication Report does not contain enough information to investigate further, so resolving as Cannot Reproduce. Should be filed as a new issue if this occurs again on a recent (no older than eight weeks) version of Jenkins, maybe we can investigate further then. Change By: Daniel Beck (03/Oct/14 1:03 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-16095) Heap memory leak (possibly jclouds plugin related)
Daniel Beck resolved JENKINS-16095 as Fixed Heap memory leak (possibly jclouds plugin related) Most recent comment indicates this was resolved long ago. Change By: Daniel Beck (03/Oct/14 1:01 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-19065) Failed to create symlink - access denied
Daniel Beck commented on JENKINS-19065 Failed to create symlink - access denied Does this issue still occur on recent Jenkins versions? A few fixes related to symlinks happened in the mean time, so it'd be good to know whether this still occurs. If so, please post the relevant folders' contents (e.g. the job folder, the build folder) and mention what file system they're on (NTFS, FAT, ...). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-13823) Changing the configuration of any project results in "Connection Reset" Error
Daniel Beck resolved JENKINS-13823 as Cannot Reproduce Changing the configuration of any project results in "Connection Reset" Error No response to comment asking for updated information, so assuming this is obsolete. Please file a new issue if this occurs on a recent (no older than 8 weeks) instance of Jenkins, don't reopen this issue. Change By: Daniel Beck (03/Oct/14 12:56 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-6211) Downstream build view not working
Daniel Beck commented on JENKINS-6211 Downstream build view not working Is this still a problem in recent Jenkins versions? How can this be reproduced on a vanilla Jenkins instance? What is the expected result, what happens instead? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-19497) JobProperty::prebuild() does not throw AbortException
Daniel Beck commented on JENKINS-19497 JobProperty::prebuild() does not throw AbortException Pinged you on Github. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-19512) "Failed to get Environment Vars from build" on z/Linux64 slave
Daniel Beck commented on JENKINS-19512 "Failed to get Environment Vars from build" on z/Linux64 slave Fred G: Does your last comment mean this isn't a bug, but misconfiguration e.g. use of undefined variables? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-17772) Sort by columns broken in Internet Explorer
Daniel Beck resolved JENKINS-17772 as Duplicate Sort by columns broken in Internet Explorer Duplicates JENKINS-21729 (fixed in 1.561 under that ID). Change By: Daniel Beck (03/Oct/14 12:51 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation
Daniel Beck commented on JENKINS-19743 Massive parallel builds sometimes cause errors in LogRotation Does this issue still occur on recent Jenkins versions? How can this be reproduced? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [remoting] (JENKINS-19798) Build occasionally hanging on Maven project build
Daniel Beck updated JENKINS-19798 Build occasionally hanging on Maven project build Appears to be remoting related. Does this issue still occur on recent Jenkins versions with recent Maven Project plugin? Change By: Daniel Beck (03/Oct/14 12:48 AM) Component/s: remoting Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [copyartifact] (JENKINS-14653) Copy Artifacts plugin does not accept Maven module as Project Name with TriggeredBuildSelector
ikedam started work on JENKINS-14653 Copy Artifacts plugin does not accept Maven module as Project Name with TriggeredBuildSelector Change By: ikedam (03/Oct/14 12:43 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [copyartifact] (JENKINS-14653) Copy Artifacts plugin does not accept Maven module as Project Name with TriggeredBuildSelector
ikedam commented on JENKINS-14653 Copy Artifacts plugin does not accept Maven module as Project Name with TriggeredBuildSelector https://github.com/jenkinsci/copyartifact-plugin/pull/48 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-16834) A Range header beyond the end of the file generates a 500 error
Joshua Kugler closed JENKINS-16834 as Fixed A Range header beyond the end of the file generates a 500 error This appears to not be an issue in the latest version (1.582) Change By: Joshua Kugler (03/Oct/14 12:13 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-24985) Perforce configVersion is not set
Mario Vuong
created JENKINS-24985
Perforce configVersion is not set
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
02/Oct/14 11:21 PM
Description:
When seeding a job that uses the Perforce plugin, the configVersion is not set. This causes certain features to not be supported, such as disableChangeLogOnly(). If I explicitly set the configVersion, such features are used.
Example (does not work):
scm {
p4(viewspec) { node ->
node / p4Client("\${JOB_NAME}")
node / p4Port("server:1666")
node / disableChangeLogOnly(true)
}
}
Example (works, using monkey patch):
ScmContext.metaClass.myP4 = { String viewspec, Closure configure = null ->
p4(viewspec, configure)
// By default, the DSL does not set configVersion, which should force the Perforce SCM plugin to set configVersion to latest.
// See: https://github.com/jenkinsci/perforce-plugin/blob/master/src/main/java/hudson/plugins/perforce/PerforceSCM.java#L633
//
// However, it doesn't seem to work which requires us to set it explicitly.
// If it is not set, features such as "disableChangeLogOnly" does not work.
//
// Setting configVersion from the closure doesn't seem to work.
// So, find the Node and set it there.
Node p4Node = scmNodes.find() { it.name() == "scm" && it.attribute("class") == "hudson.plugins.perforce.PerforceSCM"}
// configVersion is set to the default version in the Jenkins Perforce SCM plugin.
// See: https://github.com/jenkinsci/perforce-plugin/blob/master/src/main/java/hudson/plugins/perforce/PerforceSCM.java#L332
p4Node.appendNode("configVersion", "2")
}
use (my.DslExtensions) {
scm {
myP4(viewspec) { node ->
node / p4Client("\${JOB_NAME}")
node / p4Port("server:1666")
node / disableChangeLogOnly(true)
}
}
}
Environment:
Jenkins 1.571
Jenkins Job DSL Plugin 1.25
Perforce Plugin 1.3.27
Project:
Jenkins
Priority:
Minor
Reporter:
Mario Vuong
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [ivy] (JENKINS-15002) Parameterized trigger passes no parameters from Ivy Project
Darren Rowley commented on JENKINS-15002 Parameterized trigger passes no parameters from Ivy Project I have just tried this again after doing a bunch of updates, and I can confirm this is now working, at least for my setup. Jenkins 1.583 Ivy Plugin 1.24 and parameterized trigger plugin 2.25. It's been a long time since I last tried it so it's possible it was fixed in versions earlier than this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-24961) GCC output in console badly parsed/modified
Daniel Beck resolved JENKINS-24961 as Not A Defect GCC output in console badly parsed/modified Appears to not be a Jenkins defect: The slave uses 7 bit ASCII and cannot handle GCC output. Change By: Daniel Beck (02/Oct/14 9:52 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-11757) Editing a slave configuration producse Error 500 with JSONObject["name"] not found
Daniel Beck commented on JENKINS-11757 Editing a slave configuration producse Error 500 with JSONObject["name"] not found John: Could you provide more information? Is this something I can reproduce without paying money? If so, how? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven-plugin] (JENKINS-24770) Jenkins Stuck While Parsing POM's
Daniel Beck edited a comment on JENKINS-24770 Jenkins Stuck While Parsing POM's (comment removed – sorry about that outburst) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mstestrunner] (JENKINS-24984) MSTestRunner is not usable as part of the conditional-buildstep plugin
Scott Christensen created JENKINS-24984 MSTestRunner is not usable as part of the conditional-buildstep plugin Issue Type: Bug Assignee: Unassigned Components: mstestrunner Created: 02/Oct/14 9:10 PM Description: MSTestRunner is not an option in the conditional-buildstep plugin. According to the plugin documentation this is because the descriptor doesn't extend hudson.tasks.BuildStepDescriptor. It would be nice if this plugin was updated so it could be used in the conditional-buildstep plugin. Project: Jenkins Priority: Major Reporter: Scott Christensen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [selenium-axis] (JENKINS-24983) selenium-axis-plugin is a gradle-jpi-plugin component
Jeremy Marshall created JENKINS-24983 selenium-axis-plugin is a gradle-jpi-plugin component Issue Type: Bug Assignee: Unassigned Components: selenium-axis, test-stability Created: 02/Oct/14 8:54 PM Description: The selenium-axis plugin is built with the gradle-jpi-plugin and fails testing https://jenkins.ci.cloudbees.com/job/plugins/job/selenium-axis-plugin/ Can it please be setup like the job-dsl plugin to test via the gradle plugin Environment: Cloudbees Project: Jenkins Priority: Minor Reporter: Jeremy Marshall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [script-security] (JENKINS-24982) Bottom-up white/blacklisting vs top-down
Kohsuke Kawaguchi created JENKINS-24982 Bottom-up white/blacklisting vs top-down Issue Type: New Feature Assignee: Jesse Glick Components: script-security Created: 02/Oct/14 8:29 PM Description: When whitelisting methods, sometimes you want to whitelist specific implementation (say groovy.json.JsonBuilder.toString()) of a generic signature defined in the base type (java.lang.Object.toString() in this case.) In other times, you want to whitelist all the method definitions that override an interface/class method. For example, another person might want to allow all java.lang.Object.toString() invocation regardless of the receiver type. script-security plugin currently doesn't have means to do this in Whitelist. GroovyCallSiteSelector.method picks one Method instance and all the decision making happens on this single method call. Preferably, the call site selection should find the actual method definition getting invoked, as well as methods in the super types that it overrides, so that Whitelist can make decisions by using them all. Project: Jenkins Priority: Minor Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [kpp-management] (JENKINS-24981) Overwrite keychain and delete keychain options should be removed.
Tom Jones created JENKINS-24981 Overwrite keychain and delete keychain options should be removed. Issue Type: Improvement Assignee: Unassigned Components: kpp-management Created: 02/Oct/14 8:22 PM Description: Put simply, if there's a use-case for not overwriting the keychain, it's far outnumbered by the use-cases where the job should overwrite the keychain. Not overwriting the keychain with the new one effectively stops the job from getting any certificate updates, which causes more problems than it solves. If there really is a need for this feature, it should be marked with a warning that this behavior is not the norm. Deleting the keychain after build creates unexpected behavior because of a defect in xcode-plugin. Hard to explain, but it has to do with how xcodeplugin keeps track of which keychain is the current keychain. Project: Jenkins Priority: Minor Reporter: Tom Jones This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xcode] (JENKINS-24980) Keychain Management issue.
Tom Jones created JENKINS-24980 Keychain Management issue. Issue Type: Improvement Assignee: Unassigned Components: xcode Created: 02/Oct/14 8:15 PM Description: At the beginning of a build, after the keychain is copied the following commands are issued: security list-keychain -s security default-keychain -d user This creates some unintended effects. Imagine two jobs longjob and shortjob that are started in that order on jenkins. when longjob starts it sets the keychain-list and default keychain to its keychain, displays the signing identities and all seems right with the world. longjob starts its build.. shortjob starts and sets the keychain-list and default keychain to its keychain, displays the signing identities and all seems right with the world. longjob is nearly finished and tries to sign the build, but alas, it can't find its keychain (because its keychain is not in the searchlist) and its signing credentials are not in shortjob's keychain (which is the default keychain, and the only keychain in the list) so longjob fails with a signing error. shortjob signs its build correctly and succeeds. A job's keychain should be added to the keychain list, instead of replacing the list. Project: Jenkins Priority: Major Reporter: Tom Jones This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Daniel Beck commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Is there anything else logged? In the build log? The jenkins log? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-pipeline] (JENKINS-24975) Jenkins breaks when creating a new build pipeline view
Daniel Beck resolved JENKINS-24975 as Duplicate Jenkins breaks when creating a new build pipeline view Duplicates JENKINS-23749. Change By: Daniel Beck (02/Oct/14 8:10 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [scoverage] (JENKINS-24979) Wrong link in scoverage plugin
Dirceu Semighini Filho created JENKINS-24979 Wrong link in scoverage plugin Issue Type: Bug Assignee: Unassigned Components: scoverage Created: 02/Oct/14 7:41 PM Description: Scoverage trend graph link redirects to 127.0.0.1 instead of the report address Project: Jenkins Labels: plugin user-experience Priority: Minor Reporter: Dirceu Semighini Filho This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24978) Change entry repeated
dan tran created JENKINS-24978 Change entry repeated Issue Type: Bug Assignee: Unassigned Components: p4 Created: 02/Oct/14 7:36 PM Description: last change shows up in the next change list Here is a sample of display Changes #107 (Oct 2, 2014 12:25:51 PM) Configure spring-boot-maven-plugin, brought over from spring-boot's starter parent — trand8 / detail Configure maven-compiler-plugin — trand8 / detail #106 (Oct 2, 2014 12:14:37 PM) Configure maven-compiler-plugin — trand8 / detail Remove spring-boot as direct parent, used dependencyManagement with import scope instead — trand8 / detail #105 (Oct 2, 2014 11:58:44 AM) Remove spring-boot as direct parent, used dependencyManagement with import scope instead — trand8 / detail 201071: updated to use x-messages nwcpe rpm — xxx / detail Project: Jenkins Priority: Major Reporter: dan tran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24978) Change entry repeated
dan tran updated JENKINS-24978 Change entry repeated Change By: dan tran (02/Oct/14 7:37 PM) Description: last change shows up in the next change listHere is a sample of displayChanges#107 (Oct 2, 2014 12:25:51 PM)Configure spring-boot-maven-plugin, brought over from spring-boot's starter parent— trand8 / detailConfigure maven-compiler-plugin— trand8 / detail #106 (Oct 2, 2014 12:14:37 PM)Configure maven-compiler-plugin— trand8 / detailRemove spring-boot as direct parent, used dependencyManagement with import scope instead— trand8 / detail #105 (Oct 2, 2014 11:58:44 AM)Remove spring-boot as direct parent, used dependencyManagement with import scope instead— trand8 / detail201071: updated to use x-messagesnwcpe rpm— xxx / detail This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [cloverphp-plugin] (JENKINS-24977) Build name causes images to not be found
Andrew Vojak created JENKINS-24977 Build name causes images to not be found Issue Type: Bug Assignee: sogabe Components: cloverphp-plugin Created: 02/Oct/14 7:33 PM Description: Build names that include "expand" cause a 404 error for loading the collapse.gif image. It appears that the URL is being rewritten. Example: Site URL ending in ABCDEF--expandSomeFunctionality/site/clover/index.html will successfully locate ABCDEF--expandSomeFunctionality/site/clover/img/expand.gif however will attempt to locate ABCDEF--collapseSomeFunctionality/site/clover/img/expand.gif instead of the correct ABCDEF--expandSomeFunctionality/site/clover/img/collapse.gif Environment: Jenkins ver. 1.544 Clover ver. 3.1.12 Independent of OS and browser Project: Jenkins Labels: gui Priority: Minor Reporter: Andrew Vojak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xcode] (JENKINS-24874) Xcode plugin hangs when using xcode6
Reinhard Karbas reopened JENKINS-24874 Xcode plugin hangs when using xcode6 After protests from the community I am re-opening the issue to get some sort of timeout implemented for xcodebuild to find schemas and fail the build if it times out. Change By: Reinhard Karbas (02/Oct/14 7:29 PM) Resolution: Not A Defect Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [kpp-management] (JENKINS-24976) Original FileName should be used to determine equality, not Filename + GUID.
Tom Jones created JENKINS-24976 Original FileName should be used to determine equality, not Filename + GUID. Issue Type: Improvement Assignee: Unassigned Components: kpp-management Created: 02/Oct/14 7:13 PM Description: If I regenerate a provision profile and upload it to Jenkkins, jobs that used the original provisioning profile will break if I edit them and don't update the provisioning profile. The plugin appears to use filename and UUID to determine if the provisioning profile is a match, but should only use the filename. Project: Jenkins Labels: plugin provisioning Priority: Minor Reporter: Tom Jones This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24607) Need ability to build changes sequentially
Paul Allen commented on JENKINS-24607 Need ability to build changes sequentially I was thinking about adding a option for incremental changelist building under the 'Polling build filters'. This would allow you to set it per-project. I like Morne Joubert's idea of a binary bisect; not sure I could implement that in the plugin, but would be happy to review any shelved changes or pull requests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-pipeline] (JENKINS-24975) Jenkins breaks when creating a new build pipeline view
Lee Kang created JENKINS-24975 Jenkins breaks when creating a new build pipeline view Issue Type: Bug Assignee: Unassigned Attachments: error.txt Components: build-pipeline Created: 02/Oct/14 6:21 PM Description: I get the error given in the attachment when creating a new build pipeline view and then exiting the initial configuration page without clicking "accept" or "okay". We believe that this is due to the plugin creating incorrect xml for the view config that isn't completed unless "accept" or "okay" is clicked on the initial configuration page. Project: Jenkins Priority: Major Reporter: Lee Kang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [openid] (JENKINS-22368) Discovery fails when Jenkins is behind a proxy
Daniel Beck resolved JENKINS-22368 as Fixed Discovery fails when Jenkins is behind a proxy Bot seems to have forgotten to resolve this. Change By: Daniel Beck (02/Oct/14 6:17 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [fogbugz] (JENKINS-24972) FogBugz does not always use "CASE_ID", for example "BugzID" is used too (for svn integration).
Daniel Beck updated JENKINS-24972 FogBugz does not always use "CASE_ID", for example "BugzID" is used too (for svn integration). Change By: Daniel Beck (02/Oct/14 6:15 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-24966) Debian init script says: [OK] when failing on port check.
Daniel Beck updated JENKINS-24966 Debian init script says: [OK] when failing on port check. Change By: Daniel Beck (02/Oct/14 6:15 PM) Component/s: core Component/s: _test This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xcode] (JENKINS-24874) Xcode plugin hangs when using xcode6
Johanna Wolf commented on JENKINS-24874 Xcode plugin hangs when using xcode6 Well, I wouldn't mark it as Not A Defect so quickly - that xcodebuild -list command should be suffixed with a mandatory timeout to prevent this issue from being an issue, e.g.: xcodebuild -list blahblah & sleep 10 ; kill $! (as well as discard the return state as acceptable in such case) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [integrity-plugin] (JENKINS-24849) Problem in Thread handling for scm-polling jobs
Cletus D'Souza commented on JENKINS-24849 Problem in Thread handling for scm-polling jobs As for the polling thread behavior, this would need to be reviewed by someone on the core Jenkins team. There is nothing in the plugin that creates threads for supporting polling. The only threads created by the plugin are during the actual checkout process. However, the behavior you are seeing is much before the checkout is executed. As for the CmdRunner.release() call, have you tried to catch the exception to see if that resolves the issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [integrity-plugin] (JENKINS-24729) Check out Member Branch Tip from Integrity
Cletus D'Souza resolved JENKINS-24729 as Won't Fix Check out Member Branch Tip from Integrity Checking out from branch tip for individual files is not a normal mode of operation in Integrity. I would have to review your process as a whole as this type of activity is far from what we would recommend as "best practices". That said, if you insist on wanting the checkout from branch tip, then I strongly suggest you investigate the use of 'Development Paths' (project branches) to create a configuration (Update Member Revision - F7) that would include all your 'Branch Tips' in this special development path. Then you can pass in the 'configuration path' for this development path to the Jenkins plugin and you'll get the behavior you seek. Thanks! Cletus Change By: Cletus D'Souza (02/Oct/14 5:30 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [openid] (JENKINS-24974) OpenId with Google Apps stopped working in jenkins 1.565.3
Patrik Boström created JENKINS-24974 OpenId with Google Apps stopped working in jenkins 1.565.3 Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: openid Created: 02/Oct/14 5:23 PM Description: When upgrading to 1.565.3 from 1.565.2 openid stopped working. No error messages in log. Environment: Jenkins 1.565.3 Project: Jenkins Priority: Major Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ftppublisher] (JENKINS-24973) Enable ftp deployment to z/OS
Tim Wilson created JENKINS-24973 Enable ftp deployment to z/OS Issue Type: New Feature Assignee: benjaminjaton Components: ftppublisher Created: 02/Oct/14 5:20 PM Description: Error message when testing ftp server: Failed to connect or change directory jenkins.plugins.publish_over.BapPublisherException: PWD ['C111.'] did not return an absolute path... 'C111.' is valid when connecting to z/OS when the file path is to partitioned datasets on a mainframe. We transfer assembler source to z/OS PDS files to run the Assemble and Link jobs to create executables. Environment: Jenkins & git on linux, ftp to z/os IBM mainframe (not USS). Project: Jenkins Priority: Minor Reporter: Tim Wilson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-24972) FogBugz does not always use "CASE_ID", for example "BugzID" is used too (for svn integration).
J McG created JENKINS-24972 FogBugz does not always use "CASE_ID", for example "BugzID" is used too (for svn integration). Issue Type: Bug Assignee: Unassigned Components: core, fogbugz Created: 02/Oct/14 5:18 PM Description: In the "Build Environment" settings the "Copy custom fields from Fogbugz case retrieved by 'CASE_ID' environment variable into environment variables available to other build steps." specifies "CASE_ID" yet we use "BugzID" to ensure our subversion integration with FogBugz works. Can't this part of Jenkins be modified to use the "Bug ID Regex" from the "Fogbugz API communication settings"? Environment: CentOS v6.5 System Properties Name ↓ Value com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 50.0 java.endorsed.dirs /usr/java/jdk1.6.0_35/jre/lib/endorsed java.ext.dirs /usr/java/jdk1.6.0_35/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/java/jdk1.6.0_35/jre java.io.tmpdir /tmp java.library.path /usr/java/jdk1.6.0_35/jre/lib/amd64/server:/usr/java/jdk1.6.0_35/jre/lib/amd64:/usr/java/jdk1.6.0_35/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.6.0_35-b10 java.specification.name Java Platform API Specification java.specification.vendor Sun Microsystems Inc. java.specification.version 1.6 java.vendor Sun Microsystems Inc. java.vendor.url http://java.sun.com/ java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi java.version 1.6.0_35 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Sun Microsystems Inc. java.vm.specification.version 1.0 java.vm.vendor Sun Microsystems Inc. java.vm.version 20.10-b01 javamelody.About Monitoring https://wiki.jenkins-ci.org/display/JENKINS/Monitoring javamelody.analytics-id UA-1335263-7 javamelody.custom-reports Jenkins Info,About Monitoring javamelody.gzip-compression-disabled true javamelody.http-transform-pattern /\d+/|/site/.+|avadoc/.+|/ws/.+|obertura/.+|estReport/.+|iolations/file/.+|/user/.+|/static/\w+/|/adjuncts/\w+/|/bound/[\w\-]+ javamelody.Jenkins Info /systemInfo javamelody.no-database true javamelody.storage-directory //home/jenkins/monitoring javamelody.system-actions-enabled true JENKINS_HOME /home/jenkins jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 2.6.18-308.11.1.el5 path.separator : pid 17058 sun.arch.data.model 64 sun.boot.class.path /usr/java/jdk1.6.0_35/jre/lib/resources.jar:/usr/java/jdk1.6.0_35/jre/lib/rt.jar:/usr/java/jdk1.6.0_35/jre/lib/sunrsasign.jar:/usr/java/jdk1.6.0_35/jre/lib/jsse.jar:/usr/java/jdk1.6.0_35/jre/lib/jce.jar:/usr/java/jdk1.6.0_35/jre/lib/charsets.jar:/usr/java/jdk1.6.0_35/jre/lib/modules/jdk.boot.jar:/usr/java/jdk1.6.0_35/jre/classes sun.boot.library.path /usr/java/jdk1.6.0_35/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/lib/jenkins/jenkins.war --logfile=/home/jenkins/logs/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir / user.home /home/jenkins user.language en user.name jenkins user.timezone US/Eastern Environment Variables Name ↓ Value
[JIRA] [pmd] (JENKINS-24873) Wrong number of new warnings
Ulli Hafner resolved JENKINS-24873 as Fixed Wrong number of new warnings Can you please check if this works with the pull request that is part of new analysis-core 1.61 release? Change By: Ulli Hafner (02/Oct/14 5:18 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xcode] (JENKINS-24874) Xcode plugin hangs when using xcode6
Reinhard Karbas resolved JENKINS-24874 as Not A Defect Xcode plugin hangs when using xcode6 After creating the missing shared schemas for 2 of the xCode projects the build now works properly Change By: Reinhard Karbas (02/Oct/14 5:07 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xcode] (JENKINS-24874) Xcode plugin hangs when using xcode6
Reinhard Karbas closed JENKINS-24874 as Not A Defect Xcode plugin hangs when using xcode6 Change By: Reinhard Karbas (02/Oct/14 5:08 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [valgrind] (JENKINS-24971) valgrind not run if working directory set.
J McG created JENKINS-24971 valgrind not run if working directory set. Issue Type: Bug Assignee: Johannes Ohlemacher Components: valgrind Created: 02/Oct/14 5:06 PM Description: When I set the working directory and I attempt to build the prohject in Jenkins using the valgrind plugin to run valgrind (valgrind-3.8.1) all I get in the log is: [Valgrind] includes files: $ valgrind --version [Valgrind] detected valgrind version (valgrind): 3.8.1 [FINDBUGS] Collecting findbugs analysis files... If I delete the setting in the working directory and build again I see: (I have tried both "BasicStartExitSendOrders*" and "BasicStartExitSendOrdersTest" and get the same result.) [Valgrind] includes files: BasicStartExitSendOrdersTest $ valgrind --version [Valgrind] detected valgrind version (valgrind): 3.8.1 [Valgrind] working dir: /home/jenkins/workspace/NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender [NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender] $ valgrind --tool=memcheck --leak-check=full --show-reachable=no --undef-value-errors=no --track-origins=no --child-silent-after-fork=no --trace-children=no --xml=yes --xml-file=/home/jenkins/workspace/NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender/sender/reports/valgrind/BasicStartExitSendOrdersTest.%p.xml /home/jenkins/workspace/NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender/sender/build/cpp/src/Test/BasicStartExitSendOrdersTest [Valgrind] valgrind exit code: 201 [Valgrind] valgrind standard out: ERROR: Unable to initialize logger - configuration file is not specified. Please set environment variable LOG4CXX_CONFIG_FILE Running 8 test cases... unknown location(0): fatal error in "SenderCtor": std::runtime_error: Required parameter 'MSG_SIZE' has no specified value. unknown location(0): fatal error in "SenderInit": std::runtime_error: Required parameter 'MSG_SIZE' has no specified value. unknown location(0): fatal error in "SenderInitWithMITSim": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file. unknown location(0): fatal error in "SenderInitWithMITSimAndRunner": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file. unknown location(0): fatal error in "SenderProcessANewOrderMsg": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file. unknown location(0): fatal error in "SenderProcessACancelOrderMsg": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file. unknown location(0): fatal error in "SenderProcessAReplaceOrderMsg": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file. unknown location(0): fatal error in "SenderSoakTestNewOrderParallel": std::exception: Error loading NXTG configuration file [mit.xml]: Failed to open file. [Valgrind] valgrind error out: log4cxx: No appender could be found for logger (com.nomura.nxtdirect.nxt-direct-user.NxtDirectSender). log4cxx: Please initialize the log4cxx system properly. 8 failures detected in test suite "Master Test Suite" Build step 'Run Valgrind' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE Also please clarify the help text on the "Executable Include Pattern" edit box to indicate if it is relative to the entry in the "Working Directory" edit box. Thank you. Environment: CentOS v6.5 System Properties Name ↓ Value com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 50.0 java.endorsed.dirs /usr/java/jdk1.6.0_35/jre/lib/endorsed java.ext.dirs /usr/java/jdk1.6.0_35/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/java/jdk1.6.0_35/jre java.io.tmpdir /tmp java.library.path /usr/java/jdk1.6.0_35/jre/lib/amd64/server:/usr/java/
[JIRA] [active-directory] (JENKINS-24960) Active directory Logon Timeout
Daniel Beck commented on JENKINS-24960 Active directory Logon Timeout Right, as soon as you specify one of the options it switches to the LDAP (Unix) implementation; but on Windows doesn't offer you the same configuration options. This appears to be an oversight in the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [publish-over-ssh] (JENKINS-24969) Publish Over SSH Issue
Daniel Beck resolved JENKINS-24969 as Not A Defect Publish Over SSH Issue User error. Change By: Daniel Beck (02/Oct/14 5:00 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Daniel Beck resolved JENKINS-24970 as Duplicate Blank page when reapproving Duplicates JENKINS-22550 Change By: Daniel Beck (02/Oct/14 4:59 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [disk-usage] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["allJobsSize"] is not a number.
Justin Wagner commented on JENKINS-21259 Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["allJobsSize"] is not a number. I just reproduced this same error on 1.583 After upgrading I noticed that any save of the global config caused this Exception. Then after reading these comments I looked at what I had configured for "Warn if all jobs exceed some size", and it checked and the value was blank. I unchecked the box and the exception went away. Thanks for the good notes that helped me on this one. Clearly the plugin needs to handle this case better, as I don't recall turning that option on and leaving it blank. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [robot-plugin] (JENKINS-24688) Robot framework summary split in multiple rows in job list
Jussi Malinen updated JENKINS-24688 Robot framework summary split in multiple rows in job list Change By: Jussi Malinen (02/Oct/14 4:14 PM) Summary: Broken robot Robot framework summary split in multiple rows in job list This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [pmd] (JENKINS-24873) Wrong number of new warnings
SCM/JIRA link daemon commented on JENKINS-24873 Wrong number of new warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/BuildResultEvaluator.java http://jenkins-ci.org/commit/analysis-core-plugin/c873a76a22edd958c33578713fc317eec5a3df0e Log: JENKINS-24873 Fixed priority naming. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/b75554ea6be6...c873a76a22ed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [robot-plugin] (JENKINS-24792) Cleanup graph zooming
Jussi Malinen resolved JENKINS-24792 as Fixed Cleanup graph zooming Change By: Jussi Malinen (02/Oct/14 4:10 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22428) Random crash when the job is running on a slave
Sascha Retter reopened JENKINS-22428 Random crash when the job is running on a slave We are having the same issue here. Unfortunately it looks like the problem is persistent and doesn't occur only sometimes. We are on Jenkins 1.563 17:32:25 [WARNINGS] Parsing warnings in console log with parser MSBuild 17:32:39 ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception 17:32:39 java.io.IOException: remote file operation failed: at hudson.remoting.Channel@8da12db: 17:32:39 at hudson.FilePath.act(FilePath.java:916) 17:32:39 at hudson.FilePath.act(FilePath.java:893) 17:32:39 at hudson.plugins.warnings.WarningsPublisher.annotate(WarningsPublisher.java:461) 17:32:39 at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:407) 17:32:39 at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:322) 17:32:39 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333) 17:32:39 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 17:32:39 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) 17:32:39 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:709) 17:32:39 at hudson.model.Build$BuildExecution.post2(Build.java:182) 17:32:39 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:658) 17:32:39 at hudson.model.Run.execute(Run.java:1731) 17:32:39 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 17:32:39 at hudson.model.ResourceController.execute(ResourceController.java:88) 17:32:39 at hudson.model.Executor.run(Executor.java:231) 17:32:39 Caused by: java.io.IOException: Remote call on failed 17:32:39 at hudson.remoting.Channel.call(Channel.java:748) 17:32:39 at hudson.FilePath.act(FilePath.java:909) 17:32:39 ... 14 more 17:32:39 Caused by: java.lang.Error: Failed to deserialize the Callable object. 17:32:39 at hudson.remoting.UserRequest.perform(UserRequest.java:104) 17:32:39 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 17:32:39 at hudson.remoting.Request$2.run(Request.java:326) 17:32:39 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 17:32:39 at java.util.concurrent.FutureTask.run(Unknown Source) 17:32:39 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 17:32:39 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 17:32:39 at hudson.remoting.Engine$1$1.run(Engine.java:58) 17:32:39 at java.lang.Thread.run(Unknown Source) 17:32:39 Caused by: java.lang.ClassCastException: cannot assign instance of hudson.plugins.analysis.util.TreeString to field hudson.plugins.analysis.util.model.AbstractAnnotation.fileName of type hudson.plugins.analysis.util.TreeString in instance of hudson.plugins.warnings.parser.Warning 17:32:39 at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(Unknown Source) 17:32:39 at java.io.ObjectStreamClass.setObjFieldValues(Unknown Source) 17:32:39 at java.io.ObjectInputStream.defaultReadFields(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readSerialData(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readObject0(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readObject(Unknown Source) 17:32:39 at java.util.HashSet.readObject(Unknown Source) 17:32:39 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 17:32:39 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 17:32:39 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 17:32:39 at java.lang.reflect.Method.invoke(Unknown Source) 17:32:39 at java.io.ObjectStreamClass.invokeReadObject(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readSerialData(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readObject0(Unknown Source) 17:32:39 at java.io.ObjectInputStream.defaultReadFields(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readSerialData(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readObject0(Unknown Source) 17:32:39 at java.io.ObjectInputStream.defaultReadFields(Unknown Source) 17:32:39 at java.io.ObjectInputStream.readSerialData(Unknown Source) 17:32:39 at java.io.Objec
[JIRA] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier
updated JENKINS-24970
Blank page when reapproving
Change By:
Maxime Lemanissier
(02/Oct/14 4:00 PM)
Description:
Hi, i'm running with Jenkins 1.559 and promoted builds plugin 2.17.In a job with a promotion process defined with a manual approval, the first execution of the promotion on a build (by clicking 'approve' button) is successful, but the next ones (by clicking on 'Re-execute promotion' button) return a blank http page, and produces this exception in Jenkins log:
{code} Error while serving http://ci-server/jenkins/job/test_promotion_1/descriptorByName/org.jenkinsci.plugins.ghprb.GhprbTrigger/checkCronjava.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1135.invoke(Unknown Source)(snip) Caused by: java.lang.NoSuchMethodError: hudson.triggers.TimerTrigger$DescriptorImpl.doCheckSpec(Ljava/lang/String;)Lhudson/util/FormValidation; at org.jenkinsci.plugins.ghprb.GhprbTrigger$DescriptorImpl.doCheckCron(GhprbTrigger.java:349){code} The problem is not reproducible when i use an admin user.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier
updated JENKINS-24970
Blank page when reapproving
Change By:
Maxime Lemanissier
(02/Oct/14 4:00 PM)
Description:
Hi, i'm running with Jenkins 1.559 and promoted builds plugin 2.17.In a job with a promotion process defined with a manual
approbation
approval
, the first execution of the promotion on a build (by clicking 'approve' button) is successful, but the next ones (by clicking on 'Re-execute promotion' button) return a blank http page, and produces this exception in Jenkins log:{code} Error while serving http://ci-server/jenkins/job/test_promotion_1/descriptorByName/org.jenkinsci.plugins.ghprb.GhprbTrigger/checkCronjava.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1135.invoke(Unknown Source)(snip) Caused by: java.lang.NoSuchMethodError: hudson.triggers.TimerTrigger$DescriptorImpl.doCheckSpec(Ljava/lang/String;)Lhudson/util/FormValidation; at org.jenkinsci.plugins.ghprb.GhprbTrigger$DescriptorImpl.doCheckCron(GhprbTrigger.java:349){code} The problem is not reproducible when i use an admin user.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [publish-over-ssh] (JENKINS-24969) Publish Over SSH Issue
mohamed amin mengat commented on JENKINS-24969 Publish Over SSH Issue Ok Thank you very much. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-reviewbot] (JENKINS-19642) ReviewBot plugin fails after 'apply patch'
Yardena Meymann closed JENKINS-19642 as Not A Defect ReviewBot plugin fails after 'apply patch' Change By: Yardena Meymann (02/Oct/14 3:47 PM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-reviewbot] (JENKINS-19642) ReviewBot plugin fails after 'apply patch'
Yardena Meymann commented on JENKINS-19642 ReviewBot plugin fails after 'apply patch' Thanks Dan, I will close the bug then. What do you mean by "more implementations"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier created JENKINS-24970 Blank page when reapproving Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 02/Oct/14 3:43 PM Description: Hi, i'm running with Jenkins 1.559 and promoted builds plugin 2.17. In a job with a promotion process defined with a manual approbation, the first execution of the promotion on a build (by clicking 'approve' button) is successful, but the next ones (by clicking on 'Re-execute promotion' button) return a blank http page, and produces this exception in Jenkins log: Error while serving http://ci-server/jenkins/job/test_promotion_1/descriptorByName/org.jenkinsci.plugins.ghprb.GhprbTrigger/checkCron java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1135.invoke(Unknown Source) (snip) Caused by: java.lang.NoSuchMethodError: hudson.triggers.TimerTrigger$DescriptorImpl.doCheckSpec(Ljava/lang/String;)Lhudson/util/FormValidation; at org.jenkinsci.plugins.ghprb.GhprbTrigger$DescriptorImpl.doCheckCron(GhprbTrigger.java:349) The problem is not reproducible when i use an admin user. Project: Jenkins Priority: Minor Reporter: Maxime Lemanissier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Paul Allen
resolved JENKINS-24028 as Fixed
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Fixed in 1.0.15
Change By:
Paul Allen
(02/Oct/14 3:22 PM)
Status:
Reopened
Resolved
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [mantis] (JENKINS-23979) Array to string conversion error with existing Mantis project
Andreas Wacker closed JENKINS-23979 as Not A Defect Array to string conversion error with existing Mantis project Sorry, I forgot to publish that a re-install and re-configuration of mantis fixed the problem. Change By: Andreas Wacker (02/Oct/14 3:01 PM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-7976) Aggregate downstream test results does not work for Matrix projects
Jeremy Rampon commented on JENKINS-7976 Aggregate downstream test results does not work for Matrix projects Same here. Jenkins ver. 1.581 Matrix Project Plugin: 1.3 JUnit Plugin: 1.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Maxime Lemanissier commented on JENKINS-21750 Promoted Builds Plugin I don't know if this could help but Promoted build plugin v2.18 introduces a new REST API to manage promotions (fixes https://issues.jenkins-ci.org/browse/JENKINS-8963). Maybe DSL plugin could use it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [analysis-core] (JENKINS-24905) Tab and source layout broken after Jenkins UI improvements
SCM/JIRA link daemon commented on JENKINS-24905 Tab and source layout broken after Jenkins UI improvements Code changed in jenkins User: Ulli Hafner Path: .gitignore src/main/java/hudson/plugins/analysis/views/ConsoleDetail.java src/main/java/hudson/plugins/analysis/views/SourceDetail.java src/test/resources/hudson/plugins/analysis/views/ExpectedRendering-2-Ranges.html src/test/resources/hudson/plugins/analysis/views/ExpectedRendering-Line6-12.html src/test/resources/hudson/plugins/analysis/views/ExpectedRendering-Line6.html http://jenkins-ci.org/commit/analysis-core-plugin/3d2410ff40cc7bf931fcdf22b30c9627aa62cdca Log: Merge pull request #23 from yohanesgultom/master Replace bgcolor with background-color to comply html5. Fixes partly JENKINS-24905. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/1d1eb5b17cc4...3d2410ff40cc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-11543) UTF-8 encoding issue of build parameters as soon as including File parameter
Daniel Beck updated JENKINS-11543 UTF-8 encoding issue of build parameters as soon as including File parameter Change By: Daniel Beck (02/Oct/14 1:49 PM) Labels: 1.565.3-fixed lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory] (JENKINS-24960) Active directory Logon Timeout
Sven Schultschik commented on JENKINS-24960 Active directory Logon Timeout Added an screenshot to show how the advance option looks like This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory] (JENKINS-24960) Active directory Logon Timeout
Sven Schultschik updated JENKINS-24960 Active directory Logon Timeout Change By: Sven Schultschik (02/Oct/14 1:37 PM) Attachment: activeDirectoryPlugin.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory] (JENKINS-24960) Active directory Logon Timeout
Daniel Beck commented on JENKINS-24960 Active directory Logon Timeout Seems to be a separate bug in the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-24961) GCC output in console badly parsed/modified
Daniel Beck commented on JENKINS-24961 GCC output in console badly parsed/modified Seems to be the default on old CentOS. If it's an SSH slave, I use the Prefix Start Slave command export LANG=en_US.UTF-8 ; to set a sane value. It's an Advanced option in the slave configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [publish-over-ssh] (JENKINS-24969) Publish Over SSH Issue
Daniel Beck updated JENKINS-24969 Publish Over SSH Issue Change By: Daniel Beck (02/Oct/14 1:23 PM) Component/s: publish-over-ssh Component/s: ssh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ssh] (JENKINS-24969) Publish Over SSH Issue
Daniel Beck commented on JENKINS-24969 Publish Over SSH Issue I don't think this is a bug at all – you just managed to execute the one command that has no output when run without a PTY, which is one of the advanced options as explained on the wiki. Compare these two commands and their output: ssh user@host who -m ssh -t user@host who -m This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ssh] (JENKINS-24969) Publish Over SSH Issue
mohamed amin mengat created JENKINS-24969 Publish Over SSH Issue Issue Type: Bug Assignee: Unassigned Attachments: Jenkins.png, Putty.png Components: ssh Created: 02/Oct/14 12:46 PM Description: Hello; Im trying to execute a unix command over ssh via jenkins, but it doesn't work: Using Publish Over SSH Plugin. After Build Job is successful But the command Returns Nothing. Executing the same command in Putty returns the result. Command executed : Who -m *** Démarré par l'utilisateur Building in workspace d:\Profiles\admin10303\.jenkins\jobs\TFJ\workspace SSH: Connecting from host [***] SSH: Connecting with configuration [VM_Root_172.31.47.56] ... SSH: EXEC: STDOUT/STDERR from command [who -m] ... SSH: EXEC: completed after 401 ms SSH: Disconnecting configuration [VM_Root_172.31.47.56] ... SSH: Transferred 0 file(s) executing script: set -x who -m + who -m [SSH] exit-status: 0 Finished: SUCCESS Project: Jenkins Priority: Minor Reporter: mohamed amin mengat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-24961) GCC output in console badly parsed/modified
T K commented on JENKINS-24961 GCC output in console badly parsed/modified on the build node: file.encoding ANSI_X3.4-1968 seems strange, but how is this set? thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-24961) GCC output in console badly parsed/modified
T K updated JENKINS-24961 GCC output in console badly parsed/modified build node system info Change By: T K (02/Oct/14 12:38 PM) Attachment: centos-SystemInformation.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [analysis-collector] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Kevin Formsma commented on JENKINS-24940 New Warnings link in Static Analysis results shows all warnings I lost the run that had this and it doesn't seem to occur every time. I will get more details next time I see it. If I recall, it showed something like '1 new warnings' and my project has 3000+ warnings at any given time (yea, I know...). In one of the most current runs, some warnings were both fixed and created, and those links appear to be working fine ATM (I haven't changed anything on plugin/job/jenkins configuration). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory] (JENKINS-24960) Active directory Logon Timeout
Sven Schultschik commented on JENKINS-24960 Active directory Logon Timeout And where the option is to be changed when there is no UI-Option? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory] (JENKINS-24960) Active directory Logon Timeout
Daniel Beck commented on JENKINS-24960 Active directory Logon Timeout Right, but on Windows it still uses the Unix (LDAP-based) implementation if you set any of the options. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [robot-plugin] (JENKINS-24968) Show documentation on suite and test view
Jussi Malinen created JENKINS-24968 Show documentation on suite and test view Issue Type: Bug Assignee: Jussi Malinen Components: robot-plugin Created: 02/Oct/14 12:04 PM Description: The suite and test documentation could be shown on their result pages. Project: Jenkins Priority: Minor Reporter: Jussi Malinen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [robot-plugin] (JENKINS-24868) Add the ability for robot plugin graph to show only failed tests
Jussi Malinen commented on JENKINS-24868 Add the ability for robot plugin graph to show only failed tests Okay, I see your point. The next version will have a "zoom to changes" checkbox. There could be another "show only errors" or something like that... Unless someone is asking this from inside Nokia, it might take a while for us to implement. We are happy to take pull requests though! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [robot-plugin] (JENKINS-24916) Link to robot log from individual tests and suites
Jussi Malinen resolved JENKINS-24916 as Fixed Link to robot log from individual tests and suites Change By: Jussi Malinen (02/Oct/14 12:00 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
