[JIRA] [tfs-plugin] (JENKINS-21460) TFS plugin throws NumberFormatException
Andreas Hetz commented on JENKINS-21460 TFS plugin throws NumberFormatException I have the same problem please fix it. Thank you. 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] [tfs-plugin] (JENKINS-21460) TFS plugin throws NumberFormatException
Andreas Hetz edited a comment on JENKINS-21460 TFS plugin throws NumberFormatException I have the same problem, please fix it. Thank you. If you need any kind of help, please ping me. 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] [git-client-plugin] (JENKINS-25639) Multiple builds can be triggered for same commit
Wannes Sels created JENKINS-25639 Multiple builds can be triggered for same commit Issue Type: Bug Assignee: Wannes Sels Components: git-client-plugin, git-plugin Created: 17/Nov/14 9:21 AM Description: If the same commit is detected more than once (for example in 2 repositories) multiple builds for that same commit are triggered. Environment: git-plugin 2.2.8 Project: Jenkins Priority: Minor Reporter: Wannes Sels 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Bug still existing at Jenkins 1.590 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky updated JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Change By: podskalsky (17/Nov/14 9:32 AM) Environment: Jenkinsver.1.589 ,1.590 LatestPluginsSolaris10Firefox+ChromeMavenBuildJob 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-25640) use relative paths in update-center.json to allow for local mirroring
Christoph Obexer created JENKINS-25640 use relative paths in update-center.json to allow for local mirroring Issue Type: Improvement Assignee: Unassigned Components: core Created: 17/Nov/14 9:33 AM Description: 1) using relative paths in the update-center.json allows to locally mirror the jenkins update site so that a jenkins installation that is behind a corporate firewall can still be updated comfortably. 2) also a file named .json should contain json - not jsonp. jsonp should be served with the content type application/_javascript_ and named .js thus in case the requested change can't be made without breaking older jenkins version I suggest to add a new json file for use with newer jenkins version that could also fix part 2. Project: Jenkins Priority: Major Reporter: Christoph Obexer 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration changes at config.xml after only pressing "Save/Apply": $ diff config.xml config.ok 57c57,58 canRoamtrue/canRoam assignedNodemaster/assignedNode canRoamfalse/canRoam 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky edited a comment on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration The "newline" of my config.xml is removed and alse the parameters assignedNode + canRoam ... $ diff config.xml config.ok Warning: missing newline at end of file config.xml 57c57,58 canRoamtrue/canRoam assignedNodemaster/assignedNode canRoamfalse/canRoam 197c198 /maven2-moduleset /maven2-moduleset 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] [m2release-plugin] (JENKINS-25487) Exception not verbose with m2release plugin
soufien BOUZAOUIA updated JENKINS-25487 Exception not verbose with m2release plugin Change By: soufien BOUZAOUIA (17/Nov/14 9:57 AM) Labels: plugins 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] [m2release-plugin] (JENKINS-25487) Exception not verbose with m2release plugin
soufien BOUZAOUIA updated JENKINS-25487 Exception not verbose with m2release plugin Change By: soufien BOUZAOUIA (17/Nov/14 10:00 AM) Attachment: logFile.txt 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Steven Christou resolved JENKINS-18935 as Fixed Make Subversion plugin support Subversion 1.8 Merged pull request to add 1.8 support. Should be available in next release. Change By: Steven Christou (17/Nov/14 10:02 AM) Status: InProgress 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-25641) Need to share variables between jobs without using globale variables
Anis benAli created JENKINS-25641 Need to share variables between jobs without using globale variables Issue Type: Improvement Assignee: Anis benAli Components: core Created: 17/Nov/14 10:06 AM Description: Hello, It's possible to share variables between many jobs without using globale variable? we avoid giving administrative access to project leaders whom hosted their projects on our servers. Environment: last version Project: Jenkins Labels: job Priority: Minor Reporter: Anis benAli 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] [ec2-plugin] (JENKINS-25385) Jenkins EC2 plugin is not able to launch Windows Slaves in AWS
Thorsten Möllers updated JENKINS-25385 Jenkins EC2 plugin is not able to launch Windows Slaves in AWS tcpdump output Change By: Thorsten Möllers (17/Nov/14 10:30 AM) Attachment: win-agent.txt 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] [ec2-plugin] (JENKINS-25385) Jenkins EC2 plugin is not able to launch Windows Slaves in AWS
Thorsten Möllers commented on JENKINS-25385 Jenkins EC2 plugin is not able to launch Windows Slaves in AWS I see the same problem. Tried to debug it with tcpdump, and have the following findings: 1. The TCP connection is set up, so there are no firewall issues 2. The initial http request jenkins-server == raised windows-node does not have any username/password for authentication 3. The windows-node replies with HTTP/1.1 401 (authentication failed) The node logfile logs like this to me: Node Windows build machine (i-7665db97)(i-7665db97) is still stopping, waiting 5s above line repeated while node boots up Node Windows build machine (i-7665db97)(i-7665db97) is ready Windows build machine (i-7665db97) booted at 1415975164000 Connecting to ip-10-124-9-246.release.in.here.com(10.124.9.246) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. above two lines repeated indefinitely 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] [ec2-plugin] (JENKINS-25385) Jenkins EC2 plugin is not able to launch Windows Slaves in AWS
Thorsten Möllers edited a comment on JENKINS-25385 Jenkins EC2 plugin is not able to launch Windows Slaves in AWS I see the same problem. Tried to debug it with tcpdump (see attached file, win-dump.txt), and have the following findings: 1. The TCP connection is set up, so there are no firewall issues 2. The initial http request jenkins-server == raised windows-node does not have any username/password for authentication 3. The windows-node replies with HTTP/1.1 401 (authentication failed) The node logfile logs like this to me: Node Windows build machine (i-7665db97)(i-7665db97) is still stopping, waiting 5s above line repeated while node boots up Node Windows build machine (i-7665db97)(i-7665db97) is ready Windows build machine (i-7665db97) booted at 1415975164000 Connecting to ip-10-124-9-246.release.in.here.com(10.124.9.246) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. above two lines repeated indefinitely 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
pjdarton commented on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive "Been there, done that" In my experience, disabling Windows Search and anti-virus merely reduces the problem, e.g. down from a 5% failure rate to a 0.5% failure rate. On all my windows build slaves, I've configured Windows Search to only search the start-menu, then disabled the search service entirely, I've configured the anti-virus to exclude the Jenkins build area from its scans and on-access checking, and I was still seeing builds fail every week due to transient file-locking problems. After implementing the fix for this (https://github.com/jenkinsci/jenkins/pull/1209) and applying it to my local Jenkins server, I haven't seen a single build fail due to these transient file-locking problems. 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] [security] (JENKINS-25642) Bad link to /configureSecurity/asynchPeople
Diego Municio created JENKINS-25642 Bad link to /configureSecurity/asynchPeople Issue Type: Bug Assignee: Unassigned Components: security Created: 17/Nov/14 11:39 AM Description: In Manage Jenkins Configure Global Security (/configureSecurity) With "enable security" checked, in "Jenkins’ own user database" field, in help text (showed when question-mark-icon is clicked): the link "Jenkins's own user list" has href="" (relative), that way it points to /configureSecurity/asynchPeople which is not correct. I think it should be href="" (absolute) Project: Jenkins Priority: Minor Reporter: Diego Municio 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] [gradle-jpi-plugin] (JENKINS-25643) Not able to use example build.gradle file with Java 8
Hallvard Nygård created JENKINS-25643 Not able to use example build.gradle file with Java 8 Issue Type: Bug Assignee: Daniel Spilker Components: gradle-jpi-plugin Created: 17/Nov/14 11:43 AM Description: Downloaded the repository from https://github.com/jenkinsci/gradle-jpi-plugin and tried to use the build.gradle file in the "doc" folder (https://github.com/jenkinsci/gradle-jpi-plugin/tree/master/doc). $ ../gradlew build.gradle Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 FAILURE: Build failed with an exception. * Where: Script 'https://raw.github.com/jenkinsci/gradle-jpi-plugin/master/install' line: 22 * What went wrong: A problem occurred evaluating script. Failed to apply plugin [id 'org.jenkins-ci.jpi'] Plugin with id 'org.jenkins-ci.jpi' not found. * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total time: 4.355 secs Using Java 1.8.0_25 on Windows 7. Also tried to copy the build.gradle file from README.md (https://github.com/jenkinsci/gradle-jpi-plugin/blob/master/README.md) With the gradle wrapper from gradle-jpi-plugin: $ ../gradle-jpi-plugin-master/gradlew build Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 :localizer :stapler :compileJava UP-TO-DATE :compileGroovy UP-TO-DATE :processResources UP-TO-DATE :classes UP-TO-DATE :javadoc UP-TO-DATE :javadocJar :jpi FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':jpi'. java/util/HashMap$Entry * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total time: 1 mins 13.436 secs Gradle wrapper version of the gradle-jpi-plugin: $ ../gradle-jpi-plugin-master/gradlew -version Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Gradle 2.1 Build time: 2014-09-08 10:40:39 UTC Build number: none Revision: e6cf70745ac11fa943e19294d19a2c527a669a53 Groovy: 2.3.6 Ant: Apache Ant(TM) version 1.9.3 compiled on December 23 2013 JVM: 1.8.0_05 (Oracle Corporation 25.5-b02) OS: Windows 7 6.1 amd64 Project: Jenkins Priority: Major Reporter: Hallvard Nygård 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] [gradle-jpi-plugin] (JENKINS-25643) Not able to use example build.gradle file with Java 8
Hallvard Nygård
commented on JENKINS-25643
Not able to use example build.gradle file with Java 8
Tried changing the Gradle wrapper version to latest 2.3 build (in a fresh download from gradle-jpi-plugin repo):
task wrapper(type: Wrapper) {
gradleVersion = '2.3'
distributionUrl = 'http://downloads.gradle.org/distributions-snapshots/gradle-2.3-20141026230040%20-bin.zip'
}
Running gradle in main project:
$ ./gradlew wrapper
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
:wrapper
BUILD SUCCESSFUL
Total time: 4.809 secs
$ ./gradlew build
Downloading http://downloads.gradle.org/distributions-snapshots/gradle-2.3-20141026230040%20-bin.zip
.
.
.
Unzipping C:\Users\hnygard\.gradle\wrapper\dists\gradle-2.3-20141026230040 -bin\6fbv8gucgle3a8ve1h8epjf2bi\gradle-2.3-20141026230040 -bin.zip to C:\Users\hnygard\.gradle\wrapper\dists\gradle-2.3-2014102623
:compileJava
warning: [options] bootstrap class path not set in conjunction with -source 1.6
:compileGroovy
:processResources
:classes
:jar
:signArchives SKIPPED
:assemble
:codenarcMain
Download https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/1.7.5/groovy-all-1.7.5.pom
Download https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/1.7.5/groovy-all-1.7.5.jar
:codenarcTest
:compileTestJava UP-TO-DATE
:compileTestGroovy
:processTestResources
:testClasses
:test
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec basics FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:32
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec plugin class FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:54
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec dependency FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:89
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec dependencies FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:112
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec optional dependency FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:134
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec optional dependencies FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:157
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec complex dependencies FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:182
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec compatible since version FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:202
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec mask classes FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:222
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec plugin first class loader FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:242
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec sandbox status FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:262
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec plugin developer FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:288
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec plugin developers FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:317
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec support dynamic loading yes FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:341
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec support dynamic loading maybe FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:341
org.jenkinsci.gradle.plugins.jpi.JpiManifestSpec support dynamic loading no FAILED
org.spockframework.runtime.SpockComparisonFailure at JpiManifestSpec.groovy:341
Java HotSpot(TM)
[JIRA] [core] (JENKINS-25641) Need to share variables between jobs without using globale variables
Anis benAli updated JENKINS-25641 Need to share variables between jobs without using globale variables Change By: Anis benAli (17/Nov/14 11:55 AM) Environment: lastversion jenkins1.565.3 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-19728) Much needed dependency management between jobs
James Ascroft-Leigh commented on JENKINS-19728 Much needed dependency management between jobs I have a graph like this on my dashboard: Is is based on each job having three types of dependency: Zero or more Mercurial repositories from Bitbucket. It uses the Bitbucket REST API to determine the changeset of the head of the branch that the job is configured to use. Zero or more artifacts from other jobs. It uses the fingerprints from the build.xml for the last successful build of the upstream job and compares that to the fingerprints from the build.xml of the last completed build of the downstream job. The Jenkins config.xml for the job itself. Periodically I store the sha1sum of this XML file so that changes can be detected. If any of these change then the job is considered to be pending and scheduled (in dependency order) to run. I also re-run any job that is: Failing and hasn't run for 24 hours. This means I retry failed jobs frequently. Passing and hasn't run for 1 month. This means that I can be fairly confident that I detect jobs that break due to external influences. The only time I configure Jenkins to trigger a job is if I want it to run on a timer such as hourly or daily. 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] [workflow-plugin] (JENKINS-25632) workflow cps-global-lib workflowLibs.git issues
valentina armenise commented on JENKINS-25632 workflow cps-global-lib workflowLibs.git issues tested: All the issues are resolved. 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] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Is this still an 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] [ssh-slaves-plugin] (JENKINS-23419) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF
Daniel Grunwald commented on JENKINS-23419 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF To anyone else with this problem: this error indicates that the slave process died unexpected. See https://wiki.jenkins-ci.org/display/JENKINS/Remoting+issue In my case, the slave JVM terminates because the slave machine ran out of memory; and I get an error log file in the slave's FS root. 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] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Tom Ghyselinck edited a comment on JENKINS-21861 option to include attachment with console.txt from failed slaves Hi Alex, I have been watching this issue. We're also very interested in the collection of console logs from matrix Jobs. We also have very large multi-configuration Jobs, building for several configurations. We are only interested in a single e-mail, saying the build failed (or was unstable or fixed) Since otherwise our mail-box gets bloated with e-mail from our build servers. But since we still want to know why the builds failed, we need the specific console log from every configuration. (or at least every failed or every unstable Job). 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] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Tom Ghyselinck commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Hi Alex, I have been watching this issue. We-re also very interested in the collection of console logs from matrix Jobs. We also have very large multi-configuration Jobs, building for several configurations. We are only interested in a single e-mail, saying the build failed (or was unstable or fixed) Since otherwise our mail-box gets bloated with e-mail from our build servers. But since we still want to know why the builds failed, we need the specific console log from every configuration. (or at least every failed or every unstable Job). 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] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
G. Kr. commented on JENKINS-12523 Could not initialize class org.libvirt.Connect AFAIK downgrade is the only solution atm is anyone working on 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] [remoting] (JENKINS-23852) slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed
Michael M commented on JENKINS-23852 slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed Just wanted to follow up. We see this issue a few times a week, and are confident that there isn't technically a network outage at all as other nodes and jobs stay connected through this error. It most frequently happens for us at the end of a job, once as far as I'm concerned everything is complete. Can attach more logs of the error if that is helpful. Running Jenkins 1.583 on Windows 7. 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] [log-parser-plugin] (JENKINS-25644) log parser image urls don't respect the jenkins base url
martin sarsale updated JENKINS-25644 log parser image urls dont respect the jenkins base url Change By: martin sarsale (17/Nov/14 1:59 PM) Summary: logparser imageurlsdontrespectthejenkinsbaseurl 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] [log-parser-plugin] (JENKINS-25644) image urls don't respect the jenkins base url
martin sarsale created JENKINS-25644 image urls dont respect the jenkins base url Issue Type: Bug Assignee: rgoren Components: log-parser-plugin Created: 17/Nov/14 1:59 PM Description: My jenkins is configured in http://jenkins.local:8091/jenkins/ but the URLs images linked from the log-parser-plugin don't include the '/jenkins/' part: eh: http://jenkins.local:8091///plugin/log-parser/images/red.gif Project: Jenkins Priority: Minor Reporter: martin sarsale 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] [gradle-jpi-plugin] (JENKINS-25643) Not able to use example build.gradle file with Java 8
Hallvard Nygård commented on JENKINS-25643 Not able to use example build.gradle file with Java 8 Seems to be an issue with Gradle user home being a network share (corporate setup). The example in "doc" does not work. 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] [parameterized-trigger-plugin] (JENKINS-25645) Plugin writes out Triggerin projects: myproject even if no project succeeds to be triggered.
Tomas Westling created JENKINS-25645 Plugin writes out Triggerin projects: myproject even if no project succeeds to be triggered. Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 17/Nov/14 2:13 PM Description: If I setup a nonblocking project to trigger as a build step and get a failure to trigger this project (in my case due to a missing property file). I get the printouts: parameterizedtrigger Properties file $SOMETHING did not exist. Not triggering due to missing file Triggering projects: myproject When myproject in fact is never triggered. Environment: Jenkins 1.554.2, parameterized trigger plugin 2.25 Project: Jenkins Priority: Minor Reporter: Tomas Westling 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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Joshua Strouse commented on JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source Would it be preferable to create a new issue regarding the new error that Shane and I have seen when changing to JDK 7? 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] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated Test Result Trend charts
Jason Davis commented on JENKINS-25527 xUnit reports yield duplicated Test Result Trend charts Experiencing the same problem after upgrading to v1.92 (I only performed plugin upgrades) - however, I noticed the issue with existing reports. The duplicate chart appeared right after restarting Jenkins and before any builds occurred. I'm generating mstest results in a freestyle project on a windows host and slave. jenkins version is 1.585. Downgrading to v1.91 didn't help resolve the duplicate test result charts 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] [clearcase-ucm-plugin] (JENKINS-25647) LoadRules not properly added in certain situations (case 12301)
Mads Nielsen created JENKINS-25647 LoadRules not properly added in certain situations (case 12301) Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm-plugin Created: 17/Nov/14 2:34 PM Project: Jenkins Priority: Major Reporter: Mads Nielsen 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-25641) Need to share variables between jobs without using globale variables
Anis benAli updated JENKINS-25641 Need to share variables between jobs without using globale variables Change By: Anis benAli (17/Nov/14 2:36 PM) Priority: Minor Blocker 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-plugin] (JENKINS-25648) P4_CHANGELIST variable points to unshelved cl , not synced CL
Morne Joubert created JENKINS-25648 P4_CHANGELIST variable points to unshelved cl , not synced CL Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 17/Nov/14 2:39 PM Description: I would like to extract the CL that s jobs was synced to and the CL of the shelved job that was un-shelved. It is unclear how these values are available to the job (there is nothing in the documentation) The variable P4_CHANGELIST seems to point to the last CL action. So for a normal sync to CL 1000 the value maps to P4_CHANGELIST =1000 If i now test a shelved CL 1050 the value maps to P4_CHANGELIST =1050 This is problematic since the code didn't sync to 1050, it just unshelved 1050. Since the job passes in the shelved CL number , i do have access to it but i need the P4_CHANGELIST to point to the CL that was synced. Project: Jenkins Priority: Minor Reporter: Morne Joubert 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 updated JENKINS-25535 Exception if email trigger enabled but no recipient specified Change By: davida2009 (17/Nov/14 2:38 PM) Attachment: Jenkins_screenshot.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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified Sorry for my slow reply. I've attached a screenshot to show conditions that trigger the exception. 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 edited a comment on JENKINS-25535 Exception if email trigger enabled but no recipient specified Sorry for my slow reply. I've attached a screenshot to show conditions that trigger the exception. The job succeeded. 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] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated Test Result Trend charts
Jason Davis edited a comment on JENKINS-25527 xUnit reports yield duplicated Test Result Trend charts Experiencing the same problem after upgrading to v1.92 (I only performed plugin upgrades) - however, I noticed the issue with existing reports. The duplicate chart appeared right after restarting Jenkins and before any builds occurred. I'm generating mstest results in a freestyle project on a windows host and slave. jenkins version is 1.585. Downgrading to v1.91 didn't help resolve the duplicate test result charts issue. - False alarm - just noticed the problem in another project not using xUnit and reverting the Junit plugin (which I had also upgraded) to the previous version resolved the problem. 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-25641) Need to share variables between jobs without using globale variables
Anis benAli assigned JENKINS-25641 to Unassigned Need to share variables between jobs without using globale variables Change By: Anis benAli (17/Nov/14 2:43 PM) Assignee: AnisbenAli 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] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Matt Philmon commented on JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins Is there a workaround I can try? I can't move Jenkins forward without 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] [junit-plugin] (JENKINS-25649) Duplicate Test Reports in Projects
Jason Davis created JENKINS-25649 Duplicate Test Reports in Projects Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 17/Nov/14 2:51 PM Description: Duplicate Test Results chart after upgrading to version 1.2. Reverting back to 1.1 resolved the issue. I'm seeing this in Test results generated in projects using the xUnit plugin and the HP Application Automation Tools plugin. Environment: Windows 2008 R2 - Jenkins 1.585 Project: Jenkins Priority: Minor Reporter: Jason Davis 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] [m2release-plugin] (JENKINS-25487) Exception not verbose with m2release plugin
teilo commented on JENKINS-25487 Exception not verbose with m2release plugin I'm not entirely sure what you are expecting in this exception - it is coming from maven and is not under Jenkins control. 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] [m2release-plugin] (JENKINS-11509) maven release plugin does not allow to set the pom file used
teilo resolved JENKINS-11509 as Incomplete maven release plugin does not allow to set the pom file used Change By: teilo (17/Nov/14 3:11 PM) Status: Reopened Resolved Resolution: Incomplete 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] [m2release-plugin] (JENKINS-15983) Possibility to define a custom SCM tag in project config
teilo stopped work on JENKINS-15983 Possibility to define a custom SCM tag in project config Change By: teilo (17/Nov/14 3:12 PM) Status: InProgress Open 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] [m2release-plugin] (JENKINS-20131) M2 Release Plugin Build Failure message
teilo resolved JENKINS-20131 as Incomplete M2 Release Plugin Build Failure message no response to request for more info. Change By: teilo (17/Nov/14 3:16 PM) Status: Open Resolved Resolution: Incomplete 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] [m2release-plugin] (JENKINS-16091) Aborted builds are repeated within subsequent builds
teilo commented on JENKINS-16091 Aborted builds are repeated within subsequent builds @danielbeck - what wierd things? the arguments interceptor changes the goals - but only if the build was triggered via the UI and has a M2ReleaseAction attached. If we are getting one of those attached for non release builds then Jenkins itself is erronously attaching old actions. 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-with-parameters-plugin] (JENKINS-25650) java.lang.NoClassDefFoundError when attempting to build parameterized job
Jean Gressmann created JENKINS-25650 java.lang.NoClassDefFoundError when attempting to build parameterized job Issue Type: Bug Assignee: Unassigned Components: build-with-parameters-plugin Created: 17/Nov/14 3:18 PM Description: When starting a build on a parameterized job this exception happens: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-1.590.jar!/hudson/model/ParametersDefinitionProperty/index.jelly:50:78: st:include java.lang.NoClassDefFoundError: hudson/tasks/test/AggregatedTestResultAction at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:60) at jenkins.model.ParameterizedJobMixIn.doBuild(ParameterizedJobMixIn.java:162) at hudson.model.AbstractProject.doBuild(AbstractProject.java:1733) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at
[JIRA] [m2release-plugin] (JENKINS-16091) Aborted builds are repeated within subsequent builds
teilo commented on JENKINS-16091 Aborted builds are repeated within subsequent builds can someone explain how the Server can abort a build. and can someone please attach logs and 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-11962) Symlinking lastSuccessful build shouldn't fail with concurrent jobs
Rebecca Drabenstott commented on JENKINS-11962 Symlinking lastSuccessful build shouldnt fail with concurrent jobs Thanks for the suggestions Daniel. We plan to move to Java 7 in the near future. Possibly that will fix the issue. Good point about the parallel runs being unnecessary. However, the other job we have that runs for much longer (and stalls for much longer) does require parallel runs. 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] [m2release-plugin] (JENKINS-19547) Release build fails on jenkins-slave for MultiModuleMavenProjects
teilo assigned JENKINS-19547 to Unassigned Release build fails on jenkins-slave for MultiModuleMavenProjects Change By: teilo (17/Nov/14 3:21 PM) Assignee: teilo 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-with-parameters-plugin] (JENKINS-25650) java.lang.NoClassDefFoundError when attempting to build parameterized job
Jean Gressmann updated JENKINS-25650 java.lang.NoClassDefFoundError when attempting to build parameterized job It appears this was due to an unused matrix configuration parameter. Once I removed the param this exception disappeared. Change By: Jean Gressmann (17/Nov/14 3:22 PM) 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] [m2release-plugin] (JENKINS-10104) Make releases visible to the release plugin
teilo commented on JENKINS-10104 Make releases visible to the release plugin portlet support for releases has been available for a fair while - along with a permalink to the latest release. houskeeping and closign this - and keeping open Jenkins-7487 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] [cucumber-testresult-plugin] (JENKINS-21835) Cucumber Test Result Plugin crashes on malformed output in Scenario Outline results produced by some tools
teilo updated JENKINS-21835 Cucumber Test Result Plugin crashes on malformed output in Scenario Outline results produced by some tools Change By: teilo (17/Nov/14 3:32 PM) Summary: CucumberTestResultPlugin doesnotcorrectlyparse crashesonmalformedoutputin ScenarioOutlineresults producedbysometools 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] [cucumber-testresult-plugin] (JENKINS-21703) Cucumber Test results plugin
teilo updated JENKINS-21703 Cucumber Test results plugin Change By: teilo (17/Nov/14 3:33 PM) Component/s: cucumber-testresult-plugin Component/s: cucumber-reports-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] [cucumber-testresult-plugin] (JENKINS-21703) Cucumber Test results plugin
teilo resolved JENKINS-21703 as Duplicate Cucumber Test results plugin JENKINS-21835 Change By: teilo (17/Nov/14 3:33 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] [cucumber-testresult-plugin] (JENKINS-23991) Step error_message is not quoted in the scenario view, but IS quoted in the message error view
teilo updated JENKINS-23991 Step error_message is not quoted in the scenario view, but IS quoted in the message error view fix component. Change By: teilo (17/Nov/14 3:34 PM) Component/s: cucumber-testresult-plugin Component/s: cucumber-reports-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] [m2release-plugin] (JENKINS-25487) Exception not verbose with m2release plugin
soufien BOUZAOUIA commented on JENKINS-25487 Exception not verbose with m2release plugin I don't have the same problem when I do the release in command line on the other side i have this not verbose exception when i try to execute the release with m2release plugin (Jenkins). 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] [ghprb-plugin] (JENKINS-25646) Global configuration enforces job configuration without tri-state
Kanstantsin Shautsou commented on JENKINS-25646 Global configuration enforces job configuration without tri-state For example "Close failed pull request automatically?" has no help description and you can't unset it without admin permissions. 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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Daniel Beck commented on JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source Jenkins is notoriously bad to build on Windows. When I'm forced to do that I just -DskipTests=true and outsource testing to Linux boxes. That said, there appears to be something wrong, so filing an issue is the right action to take. (I'd just not hold my breath on getting a 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified Strange, I setup something the same way as you have and I don't get an exception. I'll continue trying to replicate. 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified Can you also attach your job's config.xml? 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] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Hi Tom, Did you try changing the "Trigger for matrix projects" setting in the job configuration along with the attach build log? Thanks, Alex 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-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I'm looking at a job splash page right now. SA = 0 Dup code = 15 Comp warn = 0 Open Task = ~137 SA was supposed to collect (warnings, duplicates, tasks) but it looks like (trend graph) its currently only collecting comp warnings (of which there are zero at present), when there were non-zero comp warnings, it looks like it collected the other two (duplicates, open tasks) but not compiler warnings e.g. builds 712-119 had dup code = 15 all builds open task = 137 all builds comp warnings = ~5 for all builds sa = ~155 all builds comp warnings were fixed in build 720 but the open tasks, duplicates remained stead state sa = 0 warnings dup = 15 tasks = 140 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-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff edited a comment on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I'm looking at a job splash page right now. SA = 0 Dup code = 15 Comp warn = 0 Open Task = ~137 SA was supposed to collect (warnings, duplicates, tasks) but it looks like (trend graph) its currently only collecting comp warnings (of which there are zero at present), when there were non-zero comp warnings, it looks like it collected the other two (duplicates, open tasks) but not compiler warnings e.g. builds 712-119 had dup code = 15 all builds open task = 137 all builds comp warnings = ~5 for all builds sa = ~155 all builds comp warnings were fixed in build 720 but the open tasks, duplicates remained stead state sa = 0 warnings dup = 15 tasks = 140 since the # of comp warnings was low (3-5) it may be including then correctly (when there are non-zero of them) its just hard to see (since there are 155 other counts) 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-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff edited a comment on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I'm looking at a job splash page right now. SA = 0 Dup code = 15 Comp warn = 0 Open Task = ~137 SA was supposed to collect (warnings, duplicates, tasks) but it looks like (trend graph) its currently only collecting comp warnings (of which there are zero at present), when there were non-zero comp warnings, it looks like it collected the other two (duplicates, open tasks) but not compiler warnings e.g. builds 712-119 had dup code = 15 all builds open task = 137 all builds comp warnings = ~5 for all builds sa = ~155 all builds comp warnings were fixed in build 720 but the open tasks, duplicates remained stead state sa = 0 warnings dup = 15 tasks = 140 since the # of comp warnings was low (3-5) it may be including then correctly (when there are non-zero of them) its just hard to see (since there are 155 other counts) I changed the graph to 'distr by type' and it looks like comp warnings are on the x-axis 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] [email-ext-plugin] (JENKINS-22713) '+' char in content encoded as #43;
Alex Earl commented on JENKINS-22713 + char in content encoded as #43; Using a test, the generated HTML with inlined images looks fine and renders if I open it. I'll sending an email to see if that changes it somehow. 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 updated JENKINS-25535 Exception if email trigger enabled but no recipient specified config.xml as requested, saved via Job Config History screen. Change By: davida2009 (17/Nov/14 4:56 PM) Attachment: config.xml 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-25573) Junit plugin always produces 100% health report
Mark Sinclair commented on JENKINS-25573 Junit plugin always produces 100% health report I think this is the issue: The health score is calculated in this file: junit-plugin / src / main / java / hudson / tasks / test / AbstractTestResultAction.java On Line 160-162, the health score is calculated. The lines are shown below: int score = (totalCount == 0) ? 100 : (int) (100.0 * Math.max(1.0, Math.min(0.0, 1.0 - (scaleFactor * failCount) / totalCount))); The problem is the Math.max has a first argument of 1.0, which makes the second argument irrelevant as it is always less than 1. The first argument should be 0.0, as the intention is to never report negative health. Corrected code is below (just changed to 1.0 to 0.0 in the first arg of Math.max: int score = (totalCount == 0) ? 100 : (int) (100.0 * Math.max(0.0, Math.min(0.0, 1.0 - (scaleFactor * failCount) / totalCount))); I'm pretty sure the above would fix the problem. This nested max, min functions seem redundant so the code could be further simplified - I think the following is more concise: int score = (totalCount == 0) ? 100 : (int) (100.0 * Math.max(0.0, 1.0 - (scaleFactor * failCount) / totalCount)); 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] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Hi ALex, yes - this is still an issue for "Matrix projects". works as advertised on "freestyle" projects. I tried to change "send log for all slaves" and for "master only" - it did not help. Currently, as a work-around we have some ugly script to fetch consoles and attach to the outgoing email. We could have screen sharing session if needed to demo the problem - but it is the same as in screenshot. 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] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather
Mark Sinclair commented on JENKINS-24006 Customize number of Junit test failures that affect weather The always 100% health report issue is tracked by the following: https://issues.jenkins-ci.org/browse/JENKINS-25573 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl edited a comment on JENKINS-25535 Exception if email trigger enabled but no recipient specified This will be super helpful, thanks. If you need a fast workaround, opening the job and resaving should fix the issue for you. Let me know if it does not. One question though, why have a trigger with no recipients defined? 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified This will be super helpful, thanks. If you need a fast workaround, opening the job and resaving should fix the issue for you. Let me know if it does not. 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified why have a trigger with no recipients defined? That's clearly an error on my part. But I just thought it shouldn't result in an exception. 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] [email-ext-plugin] (JENKINS-24506) NPE when sending an email in post build
Alex Earl commented on JENKINS-24506 NPE when sending an email in post build I believe I have a pretty simple fix for this. Is anyone willing to try a "debug" build based on 2.39? 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified I agree, just wondering if there was a use case I wasn't thinking of. I can create a version of 2.38.x that has what I think is the fix for this, or you can try upgrading to 2.39, it has the change I would make already. Let me know which you would like to do. 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-25488) New UI wastes horizontal space
Tom FENNELLY commented on JENKINS-25488 New UI wastes horizontal space What resolution are you working with here? It looks very small. The width of the left panel changes depending on the overall width of the browser window. It adjusts the number of "columns" given to the left panel based on the overall width of the window. This is not easy to get working in a way that is "perfect" for every situation. When doing it I experimented with different screen widths and settled on what I thought was the best balance, but of course there will be situations where it is not perfect. I suppose I leaned in favour of screens with higher resolutions, so you may be suffering from that if your screen is lower res. Changing the responsive grid css (which we got from twitter bootstrap) is not really a fix. It may fix it for the the exact scenario you are talking about here, but will most probably cause something else to look messed up. 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-25651) Admins should be able to force queued items to be executed
Bruno Meneguello created JENKINS-25651 Admins should be able to force queued items to be executed Issue Type: Improvement Assignee: Unassigned Components: core Created: 17/Nov/14 6:03 PM Description: When jobs are queued, or when the system is in shutdown mode, as admin, I want to be able to force (heavily suggest) one queued item to be executed. It happens because when I put the server to shutdown (I prefer maintenance mode), sometimes I need to run admin tasks without leaving the maintenance mode. I think the logic that tests for shutdown is spread in inadequate places, like LoadBalancer.sanitize anonymous class, and since the Task interface is much core, alter it is not a good idea. Project: Jenkins Priority: Minor Reporter: Bruno Meneguello 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-25381) Build history widget verbosity
Tom FENNELLY commented on JENKINS-25381 Build history widget verbosity Doing a no-wrap and overflow can also make it look terrible. 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] [email-ext-plugin] (JENKINS-24506) NPE when sending an email in post build
Alex Earl resolved JENKINS-24506 as Fixed NPE when sending an email in post build This is fixed in 2.39. I was previously only creating the recipient provider list if one of the options was selected (send to recipients, etc). In 2.39 this was changed so that if the list is null, it always gets created. Change By: Alex Earl (17/Nov/14 6:03 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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Shane Gannon commented on JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source -DskipTests=true did the trick. 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Daniel Beck commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration podskalsky: Jenkins does not add trailing newlines to XML files, I assume those are yours? (JENKINS-25628) 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-25642) Bad link to /configureSecurity/asynchPeople
Daniel Beck updated JENKINS-25642 Bad link to /configureSecurity/asynchPeople Change By: Daniel Beck (17/Nov/14 7:27 PM) Priority: Minor Trivial Assignee: DanielBeck Component/s: core Component/s: security 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified FYI, please see JENKINS-24506 for further discussion on 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-25652) Relaunch slave agent fails after node changes IP address
Matthew Bells created JENKINS-25652 Relaunch slave agent fails after node changes IP address Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Nov/14 7:33 PM Description: Steps to reproduce Setup Jenkins (computer "jenkins") with a node "foo" on separate computers. Browse to the page: http://jenkins:8080/computer/foo/ Ensure the node is running and Idle. Turn off the node foo computer (without first bringing the Jenkins node offline). Restart the node and have it reconnect to the network with DHCP. Make sure its IP address changed. Refresh the page, note the node is offline. The state may be "This node is being launched.", but the log is empty. Press the "Relaunch slave agent" button. This takes you to the log, which remains empty. Other info The stack trace from Jenkins shows: "Channel reader thread: foo" Id=360 Group=main WAITING on com.trilead.ssh2.channel.Channel@66a77259 at java.lang.Object.wait(Native Method) - waiting on com.trilead.ssh2.channel.Channel@66a77259 at java.lang.Object.wait(Object.java:503) at com.trilead.ssh2.channel.FifoBuffer.read(FifoBuffer.java:212) at com.trilead.ssh2.channel.Channel$Output.read(Channel.java:127) at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:946) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) at com.trilead.ssh2.SFTPv3Client.readBytes(SFTPv3Client.java:215) at com.trilead.ssh2.SFTPv3Client.receiveMessage(SFTPv3Client.java:240) at com.trilead.ssh2.SFTPv3Client.init(SFTPv3Client.java:864) at com.trilead.ssh2.SFTPv3Client.init(SFTPv3Client.java:108) at com.trilead.ssh2.SFTPv3Client.init(SFTPv3Client.java:119) at hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:1160) - locked hudson.plugins.sshslaves.SSHLauncher@1cb4fc57 at hudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:443) at hudson.remoting.Channel.terminate(Channel.java:799) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Workaround Configure the node, add a dummy value (e.g. "relaunch-1" to the description). Save the new configuration. It will now launch. There may be a way to script this too... Environment: Jenkins ver. 1.554.3 Ubuntu 14.04 Project: Jenkins Labels: slave Priority: Minor Reporter: Matthew Bells 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] [workflow-plugin] (JENKINS-25653) TimeoutStepTest.killingParallel() in aggregator failing on MacOS
Tom FENNELLY updated JENKINS-25653 TimeoutStepTest.killingParallel() in aggregator failing on MacOS Change By: Tom FENNELLY (17/Nov/14 7:48 PM) Assignee: JesseGlick KohsukeKawaguchi 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] [workflow-plugin] (JENKINS-25653) TimeoutStepTest.killingParallel() in aggregator failing on MacOS
Tom FENNELLY created JENKINS-25653 TimeoutStepTest.killingParallel() in aggregator failing on MacOS Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 17/Nov/14 7:47 PM Description: This test (introduced in f7c0db4) fails every time on Darwin/MacOS (at least for me). It runs fine if you run the test on its own (i.e. do not run TimeoutStepTest.basic()). It times out waiting for the build to fail (line 51). It seemed like it might be something to do with not being able to kill all related child processes running in the parallel step, but I'm not sure about that now after adding some logging to the ProcessTree class. Initially it seemed as though it was trying to kill the same process multiple times (I thought maybe that might cause things to hang) but that's not the case either since I've seen it hang even when all the PIDs are unique, so not sure now. Environment: MacOS Project: Jenkins Priority: Major Reporter: Tom FENNELLY 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] [jobconfighistory-plugin] (JENKINS-25654) Restore Project option for Job Config History gets Oops! page
george trubisky created JENKINS-25654 Restore Project option for Job Config History gets Oops! page Issue Type: Bug Assignee: Mirko Friedenhagen Attachments: JobConfigHistory_2014-11-17_11-39-41.jpg, JobConfigHistory_stacktrace.txt Components: jobconfighistory-plugin Created: 17/Nov/14 7:57 PM Description: When attempting to restore projects, get the "devil jenkins" oops page. Projects in question were disabled prior to delete and Job Config History plugin was not installed prior to the project being disabled. Environment: Jenkins ver. 1.565.1, jobconfighistory plugin 2.9 Project: Jenkins Labels: user-experience Priority: Major Reporter: george trubisky 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-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I.e., only the job graph shows a wrong result, the SA result is correct in the build details view? 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-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff updated JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I picture of what I said earlier Change By: Greg Moncreaff (17/Nov/14 8:08 PM) Attachment: JENKINS-22394.JPG 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-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff edited a comment on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I picture of what I said earlier. I don't know what you mean by 'build details view'? 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] [nodelabelparameter-plugin] (JENKINS-24280) Environment variables get corrupted when using Node parameter
Richard Hendricks commented on JENKINS-24280 Environment variables get corrupted when using Node parameter I see the same problem with our Jenkins setup. We are not using env-inject. 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-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff edited a comment on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I picture of what I said earlier. It's wrong in 'build details' also... Static Analysis Warnings: 0 warnings. No warnings since build 719. New zero warnings highscore: no warnings for 2 days! 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] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Daniel Beck commented on JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins To clarify, you cannot upgrade beyond 1.585 without a fix? Or what else is the problem here? 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] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves A screen sharing session would be useful, I'm just not sure when during the day I could do it. What timezone are you in? 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-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner reopened JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results Change By: Ulli Hafner (17/Nov/14 8:48 PM) 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] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results Can you please show the log messages of the analysis plugins from your console log of the latest build? There should be messages starting with WARNINGS DRY, etc. 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-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results And are you using the latest versions of the plugins/jenkins? 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.
