[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve()
dogfood commented on JENKINS-21631 java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve() Integrated in jenkins_main_trunk #3464 JENKINS-21631 - Don't fail with NPE if the PeepholePermalink cache contains the non-numeric value. (Revision 5df3f74b4e7700d5f51243ced4c97fdc209c6fb2) FIXED JENKINS-21631 Noting #1275. (Revision 2b89f9d09e3426de8d2d311e059f24cb1c0b0b10) Result = SUCCESS o.v.nenashev : 5df3f74b4e7700d5f51243ced4c97fdc209c6fb2 Files : core/src/main/java/jenkins/model/PeepholePermalink.java Jesse Glick : 2b89f9d09e3426de8d2d311e059f24cb1c0b0b10 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23417) AccessRestriction on SecurityListener methods
dogfood commented on JENKINS-23417 AccessRestriction on SecurityListener methods Integrated in jenkins_main_trunk #3464 FIXED JENKINS-23417 Noting merge of #1277. (Revision 6dd071eaa8dd20ac6734d1b54e05d0a4adb7599f) Result = SUCCESS Jesse Glick : 6dd071eaa8dd20ac6734d1b54e05d0a4adb7599f Files : core/src/main/java/jenkins/security/SecurityListener.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Frank Lee
updated JENKINS-23415
2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Change By:
Frank Lee
(13/Jun/14 7:09 AM)
Description:
Problem:Ajobkeepstriggeringwhenitshouldnot.Background:2separatejobsareconfiguredtobetriggeredonthesameGithubrepositorydependingonbranchthatpushedto.Whenpushingtothe1stbranch,origin/test/branch1,the1stjobistriggered.Good.Whenpushingtothe2ndbranch,origin/test/branch2,the2ndjobtriggers.Good.Butthe1stjobistriggeredagain.Bad.Theresonlybeen2pushes.Therepositoryisverylarge,sothegitclonetakesafewminutesforbothjobs.Theproblemconsistentlyoccurswhenpushingtothe1stbranch,THENimmediatelypushingtothe2ndbranch.The1stjobistriggeredandgitcloning.Andthe2ndjobistriggeredandqueued.BUTanother1stjobistriggeredandqueued.Seemstohappenwhenitsstilldownloadingduringtheclone.Thatextratriggeredjobiscausingusgrief,becauseitsusedfordeployments.Thisisreproducibleconsistentlywiththisscript:#!/bin/bashpushdmydirectorygitcheckoutdevelopecho${1}dd.txtgitadd.gitcommit-m${1}dgitpushgitcheckouttest/branch1gitpull--no-editupstreamdevelopgitpushgitcheckouttest/branch2gitpull--no-editupstreamtest/branch1gitpushpopdAndrunitas:#./script1#./script2etc...Jenkinsv1.558GitClientv1.9.0Gitpluginv2.2.1GitHubAPIv1.44GithubOAuthv0.14GitHubPullRequestBuilder1.12
GitHubpluginv1.8
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-20086) Allow disabling use of default exclude patterns (.git, .svn, etc.)
Nicolas Labrot commented on JENKINS-20086 Allow disabling use of default exclude patterns (.git, .svn, etc.) As a workaround I have remove ".svn" from the defaultExcludes with an init.groovy hook. Per job option seems to me the right way. And maybe per copy/archive task (a checkbox to include defaultExcludes). 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] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Frank Lee commented on JENKINS-23415 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading I edited the original post to add one more plugin: "GitHub plugin v1.8". I'm guessing the GitHub payloads are triggered with that plugin. If there's anything else I can do to move this issue forward, let me know. 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] [ansicolor] (JENKINS-23420) The AnsiColor 0.4.0 version no longer works
Alexander Obuhovich created JENKINS-23420 The AnsiColor 0.4.0 version no longer works Issue Type: Bug Assignee: Unassigned Components: ansicolor Created: 13/Jun/14 7:45 AM Description: After upgrading to AnsiColor 0.4.0 the escape sequences in the console output are no longer being highlighted. Reverting to AnsiColor 0.3.1 version solved the problem. I'm using Jenkins 1.567 Project: Jenkins Labels: plugin Priority: Major Reporter: Alexander Obuhovich 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] [gerrit-trigger] (JENKINS-23421) Parameter value should be always displayed as human-readable
rin_ne created JENKINS-23421 Parameter value should be always displayed as human-readable Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 13/Jun/14 8:38 AM Description: When an option to encode value of GERRIT_CHANGE_COMMIT_MESSAGE is enabled, its parameter provides encoded string to UI. But it should be human-readable. Environment: Jenkins 1.509.3 Gerrit Trigger 2.12.0-beta3 Project: Jenkins Priority: Minor Reporter: rin_ne 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] [gerrit-trigger] (JENKINS-23421) Parameter value should be always displayed as human-readable
rin_ne started work on JENKINS-23421 Parameter value should be always displayed as human-readable Change By: rin_ne (13/Jun/14 8:42 AM) Status: Open InProgress 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] [gerrit-trigger] (JENKINS-23421) Parameter value should be always displayed as human-readable
rin_ne updated JENKINS-23421 Parameter value should be always displayed as human-readable Change By: rin_ne (13/Jun/14 8:42 AM) Assignee: rsandell rin_ne 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] [sonar] (JENKINS-23422) Sonar runner plugin blocks jenkins web UI
Georgi Georgiev created JENKINS-23422 Sonar runner plugin blocks jenkins web UI Issue Type: Bug Affects Versions: current Assignee: Sonar Team Components: sonar Created: 13/Jun/14 8:58 AM Description: When post-build sonar task is running, then Jenkins becomes unresponsive until sonar runner finish. Environment: Ubuntu 12.04 - x64, Jenkins 1.567, Sonar plugin 2.1 Project: Jenkins Labels: sonar plugin Priority: Major Reporter: Georgi Georgiev 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] [docker] (JENKINS-23423) docker plugin depends on jclouds plugin and java/openjdk =7
Michael Prokop created JENKINS-23423 docker plugin depends on jclouds plugin and java/openjdk =7 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: docker Created: 13/Jun/14 9:05 AM Description: The docker plugin fails on systems using openjdk-6 with: 1) Error injecting constructor, java.lang.UnsupportedClassVersionError: com/nirima/docker/client/DockerException : Unsupported major.minor version 51.0 at com.nirima.jenkins.plugins.docker.builder.DockerBuilderControl$DescriptorImpl.init(Unknown Source) Updating to openjdk-7-jre-headless solves this problem. Also the docker plugin can't be used/configured until you install the jclouds-jenkins plugin, please consider updating the dependency accordingly. Thanks for the docker plugin! Environment: Jenkins 1.567 on Debian/wheezy, docker plugin v0.5 Project: Jenkins Priority: Major Reporter: Michael Prokop 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] (JENKINS-23233) Libvirt does not shut down slaves after last upgrade of plugin
Johan Cronje commented on JENKINS-23233 Libvirt does not shut down slaves after last upgrade of plugin From the logs, it seems the problem is when trying to shut down the machine: Jun 13, 2014 10:43:46 AM SEVERE hudson.remoting.Channel$2 handle Failed to execute command close (channel devel-win64-node1) java.lang.NullPointerException at java.util.regex.Matcher.getTextLength(Matcher.java:1234) at java.util.regex.Matcher.reset(Matcher.java:308) at java.util.regex.Matcher.init(Matcher.java:228) at java.util.regex.Pattern.matcher(Pattern.java:1088) at java.util.Formatter.parse(Formatter.java:2515) at java.util.Formatter.format(Formatter.java:2469) at java.util.Formatter.format(Formatter.java:2423) at java.lang.String.format(String.java:2797) at hudson.util.StreamTaskListener.fatalError(StreamTaskListener.java:153) at hudson.plugins.libvirt.VirtualMachineLauncher.afterDisconnect(VirtualMachineLauncher.java:192) at hudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:443) at hudson.remoting.Channel.terminate(Channel.java:819) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:951) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Jun 13, 2014 10:43:46 AM SEVERE hudson.remoting.Channel$2 handle This command is created here Command close created at at hudson.remoting.Command.init(Command.java:56) at hudson.remoting.Channel$CloseCommand.init(Channel.java:945) at hudson.remoting.Channel$CloseCommand.init(Channel.java:943) at hudson.remoting.Channel.close(Channel.java:1026) at hudson.remoting.Channel.close(Channel.java:1009) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:950) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) 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] (JENKINS-23424) Existing working directory is not updated
chrisabit created JENKINS-23424 Existing working directory is not updated Issue Type: Bug Assignee: Nicolas De Loof Components: git, git-client Created: 13/Jun/14 9:25 AM Description: Existing working dirs are not updated after a build is started. The git fetch works,moreover the correct commit hashcode is used (visible in console log) A manual (commandline!) "git reset --hard" updates the working dir. Our workaround: Force delete jenkins working dir. Environment: Jenkins 1.566 git plugin 2.2.1 git client plugin 1.9.1 JGit Tomcat 7 Java 1.7.0_60 RHEL6 gitblit Repos / http Project: Jenkins Priority: Critical Reporter: chrisabit 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-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Daniel Beck commented on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history rin_ne: Re my newest comment to the Github core PR: I checked the Jenkins instance with jobs with several parameters. The current implementation really isn't that easy to use (and looks worse) even with jobs that are not Gerrit-triggered (and in fact have quite short parameter values on average). So I'm OK with a 'hide by default' change to the widget. 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] [gerrit-trigger] (JENKINS-23421) Parameter value should be always displayed as human-readable
rin_ne stopped work on JENKINS-23421 Parameter value should be always displayed as human-readable Change By: rin_ne (13/Jun/14 10:47 AM) 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] [gerrit-trigger] (JENKINS-23421) Parameter value should be always displayed as human-readable
rin_ne commented on JENKINS-23421 Parameter value should be always displayed as human-readable PR: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/160 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-19250) Want to know which user started a build that is sitting in the queue
Shannon Kerr commented on JENKINS-19250 Want to know which user started a build that is sitting in the queue OK on 1. For 2, I see something structured like (I'm numbering the lines): 1. Started by Shannon Kerr 2. Jenkins is about to shutdown 3. The rest of the parameters for that build (e.g. svn branch etc) I thought that 1 would have been kept with 3 and 2 would have been above them both. I considered the person who started the build part of the build parameters, but now that I think about it I could see how others may not think that way. I'll leave it up to you. I really appreciate your responsiveness during the work on this ticket. Thanks very much. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19250) Want to know which user started a build that is sitting in the queue
Shannon Kerr commented on JENKINS-19250 Want to know which user started a build that is sitting in the queue btw, the Jenkins Trac plugin that we use in our issue tracker (in the "timeline") is able to list those who triggered the build if the build was triggered by a commit. So, it looks like there may be code out there that could be reused to list anyone responsible for triggering a build. Of course, that list could be large. I think you pointed this out earlier. 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-23425) View or using REST api (json,xml) on a job building war do not delete temp file in tomcat7 temp
adoudev viaccess-orca created JENKINS-23425 View or using REST api (json,xml) on a job building war do not delete temp file in tomcat7 temp Issue Type: Bug Assignee: Christian Pelster Components: core, walldisplay Created: 13/Jun/14 12:45 PM Description: We faced to a problem with our Jenkins 1.537 into tomcat7; the tomcat7-tmp is full of war file. The problem have been put under the light when we started using wall display plug-in. We found out that it wasn't walldisplay that was causing this; but calls to the REST json api every 20 seconds. Calls are make on JENKINS_URL/job/JOB_NAME/api/json as you can see line 390 of this file : https://github.com/jenkinsci/walldisplay-plugin/blob/master/src/main/webapp/walldisplay.js The job also publish jar file but only war file is fulling the tomcat temp. We also see that not only REST api produce this temp war file! View the project page do this too. What we do not understand is why it's not happening to all job that publish war artifact... the job using: remove old build security based on project launch on a windows slave using Subversion publish Checkstyle analysis publish PMD analysis save artifacts (jar and war using *) If it's not a bug from Jenkins it may be a tomcat7 configuration error? Environment: Jenkins 1.537, tomcat7, Ubuntu 12.04.3 LTS Project: Jenkins Priority: Critical Reporter: adoudev viaccess-orca 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-23232) SEVERE: I/O error in channel Chunked connection
Peter Kline commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection By setting -Dhudson.diyChunking=false in /etc/sysconfig/jenkins and restarting I am now able to run remote build calls. Not sure if this fixes the remote slave issue but it certainly solves my issue when running the jenkins-cli.jar problems with Chunking 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-23223) Jenkins CLI to start a build no longer working in 1.564
Peter Kline commented on JENKINS-23223 Jenkins CLI to start a build no longer working in 1.564 By setting -Dhudson.diyChunking=false in /etc/sysconfig/jenkins and restarting I am now able to run remote build calls. Leaving ticket open as while this solves my problem not sure if this is a long term viable 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] [core] (JENKINS-23425) View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp
adoudev viaccess-orca updated JENKINS-23425 View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp Change By: adoudev viaccess-orca (13/Jun/14 12:50 PM) Summary: VieworusingRESTapi (json,xml) onajob buildingwar publishingartifact donotdelete war tempfileintomcat7temp 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-23425) View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp
adoudev viaccess-orca commented on JENKINS-23425 View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp We just tried to : copy the job remove artifact publish launch the job = not more war file in tomcat temp enable archiving artifact but NOT the war file launch the job = war file in tomcat temp! 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-23425) View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp
adoudev viaccess-orca edited a comment on JENKINS-23425 View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp We just tried to : copy the job remove artifact publish launch the job view job page = not more war file in tomcat temp enable archiving artifact but NOT the war file launch the job view job page = war file in tomcat temp! 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] [jacoco] (JENKINS-23426) Crash publishing jacoco report across all projects with 1.0.15
James Green created JENKINS-23426 Crash publishing jacoco report across all projects with 1.0.15 Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco Created: 13/Jun/14 1:05 PM Description: Using Jenkins 1.567 on Linux. Each project is Maven 3 based and publishes jacoco coverage reports. Since upgrading plugins yesterday we're seeing a crash whenever the plugin tries to run. Here's one example: JaCoCo plugin Collecting JaCoCo coverage data... JaCoCo plugin */.exec;/classes;*/src/main/java; locations are configured JaCoCo plugin Number of found exec files: 3 JaCoCo plugin Saving matched execfiles: /var/lib/jenkins/jobs/mjls-parent/workspace/automated-readers/target/jacoco.exec /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-core/target/jacoco.exec /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-web/target/jacoco.exec JaCoCo plugin Saving matched class directories: /var/lib/jenkins/jobs/mjls-parent/workspace/automated-readers/target/classes /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-core/target/classes /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-web/target/classes /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-web/target/mjls/WEB-INF/classes JaCoCo plugin Saving matched source directories: /var/lib/jenkins/jobs/mjls-parent/workspace/automated-readers/src/main/java /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-core/src/main/java /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-web/src/main/java JaCoCo plugin Loading inclusions files.. JaCoCo plugin inclusions: [] JaCoCo plugin exclusions: [] ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception java.io.IOException: Error while analyzing class /var/lib/jenkins/jobs/mjls-parent/builds/2014-06-13_12-58-21/jacoco/classes/com/mjog/mjls/attachment/DeletedAttachmentToSaas.class. at org.jacoco.core.analysis.Analyzer.analyzerError(Analyzer.java:150) at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:144) at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:175) at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:208) at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:130) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:137) at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:102) at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:291) at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:273) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:371) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1040) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1735) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: java.lang.IllegalArgumentException at org.objectweb.asm.ClassVisitor.init(Unknown Source) at org.jacoco.core.internal.flow.ClassProbesVisitor.init(ClassProbesVisitor.java:37) at org.jacoco.core.internal.flow.ClassProbesVisitor.init(ClassProbesVisitor.java:27) at org.jacoco.core.internal.analysis.ClassAnalyzer.init(ClassAnalyzer.java:47) at org.jacoco.core.analysis.Analyzer$1.init(Analyzer.java:90) at org.jacoco.core.analysis.Analyzer.createAnalyzingVisitor(Analyzer.java:87) at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:105) at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:142) ... 17 more Finished: FAILURE Similar stacktraces can be found across our other projects. I've updated the jacoco plugin within the project to the latest 0.7.1 with no change. The build itself is
[JIRA] [jacoco] (JENKINS-23426) Crash publishing jacoco report across all projects with 1.0.15
James Green commented on JENKINS-23426 Crash publishing jacoco report across all projects with 1.0.15 Downgraded to 1.0.14 and it works fine: JaCoCo plugin Collecting JaCoCo coverage data... JaCoCo plugin */.exec;/classes;*/src/main/java; locations are configured JaCoCo plugin Number of found exec files: 3 JaCoCo plugin Saving matched execfiles: /var/lib/jenkins/jobs/mjls-parent/workspace/automated-readers/target/jacoco.exec /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-core/target/jacoco.exec /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-web/target/jacoco.exec JaCoCo plugin Saving matched class directories: /var/lib/jenkins/jobs/mjls-parent/workspace/automated-readers/target/classes /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-core/target/classes /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-web/target/classes /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-web/target/mjls/WEB-INF/classes JaCoCo plugin Saving matched source directories: /var/lib/jenkins/jobs/mjls-parent/workspace/automated-readers/src/main/java /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-core/src/main/java /var/lib/jenkins/jobs/mjls-parent/workspace/mjls-web/src/main/java JaCoCo plugin Loading inclusions files.. JaCoCo plugin inclusions: [] JaCoCo plugin exclusions: [] JaCoCo plugin Thresholds: JacocoHealthReportThresholds minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0 JaCoCo plugin Publishing the results.. JaCoCo plugin Loading packages.. JaCoCo plugin Done. Finished: SUCCESS 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] [blamesubversion] (JENKINS-23427) Performance of Blame svn plugin is very poor
Ireneusz Makowski created JENKINS-23427 Performance of Blame svn plugin is very poor Issue Type: Bug Assignee: Unassigned Components: blamesubversion Created: 13/Jun/14 1:19 PM Description: See this issue for details: https://issues.jenkins-ci.org/browse/JENKINS-20078 Blame svn plugin calls hudson.model.User.getProjects(User.java:479) for all User projects but should call only for upstream projects of a given job. This cause serious performance issue at java.lang.Character.toUpperCase(Unknown Source) at java.lang.Character.toUpperCase(Unknown Source) at java.lang.String$CaseInsensitiveComparator.compare(Unknown Source) at java.lang.String$CaseInsensitiveComparator.compare(Unknown Source) at java.lang.String.compareToIgnoreCase(Unknown Source) at hudson.model.User$1.compare(User.java:415) at hudson.model.User$1.compare(User.java:413) at java.util.TimSort.mergeHi(Unknown Source) at java.util.TimSort.mergeAt(Unknown Source) at java.util.TimSort.mergeForceCollapse(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at java.util.Collections.sort(Unknown Source) at hudson.model.User.getAll(User.java:413) at hudson.model.User$FullNameIdResolver.resolveCanonicalId(User.java:768) at hudson.model.User.get(User.java:327) at hudson.model.User.get(User.java:300) at hudson.model.User.get(User.java:369) at hudson.scm.SubversionChangeLogSet$LogEntry.setUser(SubversionChangeLogSet.java:267) at sun.reflect.GeneratedMethodAccessor56595.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.beanutils.PropertyUtilsBean.invokeMethod(PropertyUtilsBean.java:2170) at org.apache.commons.beanutils.PropertyUtilsBean.setSimpleProperty(PropertyUtilsBean.java:2151) at org.apache.commons.beanutils.PropertyUtilsBean.setNestedProperty(PropertyUtilsBean.java:1957) at org.apache.commons.beanutils.PropertyUtilsBean.setProperty(PropertyUtilsBean.java:2064) at org.apache.commons.beanutils.BeanUtilsBean.setProperty(BeanUtilsBean.java:1017) at org.apache.commons.beanutils.BeanUtils.setProperty(BeanUtils.java:456) at org.apache.commons.digester.BeanPropertySetterRule.end(BeanPropertySetterRule.java:202) at org.apache.commons.digester.Digester.endElement(Digester.java:1345) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1871) at hudson.scm.SubversionChangeLogParser.parse(SubversionChangeLogParser.java:76) at hudson.scm.SubversionChangeLogParser.parse(SubversionChangeLogParser.java:43) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:922) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:896) at
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Daniel Beck updated JENKINS-23232 SEVERE: I/O error in channel Chunked connection slave-setup is a plugin, removing that component. Change By: Daniel Beck (13/Jun/14 1:22 PM) Component/s: slave-setup 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-23223) Jenkins CLI to start a build no longer working in 1.564
Daniel Beck resolved JENKINS-23223 as Duplicate Jenkins CLI to start a build no longer working in 1.564 Seems to be a duplicate of JENKINS-23232. Change By: Daniel Beck (13/Jun/14 1:22 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] [prioritysorter] (JENKINS-23428) Jobs in NestedView (ViewGroup) are not correctly found
Magnus Sandberg created JENKINS-23428 Jobs in NestedView (ViewGroup) are not correctly found Issue Type: Bug Assignee: Magnus Sandberg Components: prioritysorter Created: 13/Jun/14 1:42 PM Description: NestedView in nested-view-plugin returns "false" when asked if a Job is present in the view. This might also be true for other implementations of ViewGroup. https://github.com/jenkinsci/nested-view-plugin/blob/master/src/main/java/hudson/plugins/nested_view/NestedView.java http://javadoc.jenkins-ci.org/hudson/model/ViewGroup.html Project: Jenkins Priority: Major Reporter: Magnus Sandberg 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] (JENKINS-9589) SSH sessions kept open by Subversion checkout
Todd Rhoades commented on JENKINS-9589 SSH sessions kept open by Subversion checkout Possibly related? http://issues.tmatesoft.com/issue/SVNKIT-467 Also, I haven't fully confirmed this, but it appears to happen when the post commit hook triggers and "No jobs found matching the modified files." 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] (JENKINS-9589) SSH sessions kept open by Subversion checkout
Todd Rhoades edited a comment on JENKINS-9589 SSH sessions kept open by Subversion checkout Possibly related? http://issues.tmatesoft.com/issue/SVNKIT-467 Also, I haven't fully confirmed this, but it appears to happen when the post commit hook triggers and "No jobs found matching the modified files." Running Jenkins 1.532.2 subversion plugin 1.45 svnserve 1.6.15 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] [prioritysorter] (JENKINS-23428) Jobs in NestedView (ViewGroup) are not correctly found
SCM/JIRA link daemon commented on JENKINS-23428 Jobs in NestedView (ViewGroup) are not correctly found Code changed in jenkins User: emsa23 Path: src/main/java/jenkins/advancedqueue/PriorityConfiguration.java http://jenkins-ci.org/commit/priority-sorter-plugin/81d763473a814d65fa8c97741f9dac4bc221f355 Log: JENKINS-23428 Better support for ViewGroup 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-23305) NPE on running some slaves of a matrix build - failure with no explanation
trejkaz
edited a comment on JENKINS-23305
NPE on running some slaves of a matrix build - failure with no explanation
My guess would be that despite isUnix being set in a synchronized{} block, isUnix() is not synchronised, so a second thread getting the value might be getting an out of date value.
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-23305) NPE on running some slaves of a matrix build - failure with no explanation
trejkaz
commented on JENKINS-23305
NPE on running some slaves of a matrix build - failure with no explanation
My guess would be that despite isUnix being set in a synchronized{} block, when isUnix() is not synchronised, so a second thread getting the value might be getting an out of date value.
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] [ivytrigger] (JENKINS-23429) System properties that contain a quote will cause a parsing error
Robert Clark created JENKINS-23429 System properties that contain a quote will cause a parsing error Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: ivytrigger Created: 13/Jun/14 2:20 PM Description: In the properties file we provide to the trigger, we have property that contains a double quote. Even though this specific property is not used in the Ivy file, the plugin generates an temporary XML file that is not valid because of it. For example: build.properties contains: a.property.name=This is "A" test results in: [ERROR] - XTrigger exception: java.text.ParseException: failed to load settings from file:/C:/Users/x/AppData/Local/Temp/file9178016074964912659.tmp: Element type "property" must be followed by either attribute specifications, "" or "/". Because the generated file contains: property name="a.property.name" value="This is "A" test"/ Characters that are not XML safe will need to be encoded when the file is written out. Environment: Version 0.32 of the plugin Project: Jenkins Priority: Major Reporter: Robert Clark 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] [ivytrigger] (JENKINS-23429) System properties that contain a quote will cause a parsing error in the IvyTrigger plugin
Robert Clark updated JENKINS-23429 System properties that contain a quote will cause a parsing error in the IvyTrigger plugin Change By: Robert Clark (13/Jun/14 2:20 PM) Summary: Systempropertiesthatcontainaquotewillcauseaparsingerror intheIvyTriggerplugin 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] (JENKINS-19994) Unable to delete workspace
Thiago Zanetti commented on JENKINS-19994 Unable to delete workspace I tried to configure the command line git and found it a bit hard to accomplish with the limited time I had in that moment. I'll give another try. Therefore, I'll create a linux machine to support my CI services but still have to maintain a Windows node for the projects that are Windows only. Thank you for your time. Best regards, Thiago Zanetti 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-20086) Allow disabling use of default exclude patterns (.git, .svn, etc.)
Daniel Beck commented on JENKINS-20086 Allow disabling use of default exclude patterns (.git, .svn, etc.) Right, I meant per post-build step. As there's usually only one, it's effectively "per job". I don't know whether the same behavior applies to Copy Artifact plugin. I'd consider that a separate issue though, as it's a different component. 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] (JENKINS-9589) SSH sessions kept open by Subversion checkout
Daniel Beck commented on JENKINS-9589 SSH sessions kept open by Subversion checkout Needs to be reproduced in Subversion Plugin 2.x. 1.45 was released 17 months ago. 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-19134) Disallow Users to set a custom workspace
Daniel Beck commented on JENKINS-19134 Disallow Users to set a custom workspace Steffen Breitbach Right, Cloudbees Template plugin is Jenkins Enterprise only. (Note that it's the same program, just a licensing plugin that other enterprise plugins depend on. So no additional config changes necessary after you hand them a bucket full of money.) 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-21693) JSONException: There is a cycle in the hierarchy!
Jesse Glick commented on JENKINS-21693 JSONException: There is a cycle in the hierarchy! In 1.561. 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-21693) JSONException: There is a cycle in the hierarchy!
Jesse Glick updated JENKINS-21693 JSONException: There is a cycle in the hierarchy! Change By: Jesse Glick (13/Jun/14 4:23 PM) Labels: _javascript_json stapler 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-22373) IE 9 regular mode: Enter does not work to submit forms
Tom FENNELLY commented on JENKINS-22373 IE 9 regular mode: Enter does not work to submit forms I parked trying to sort out JENKINS-23405(https://issues.jenkins-ci.org/browse/JENKINS-23405) for now - issues replicating the same release structure as was used to create the 2.9.0 YUI resources (which Jenkins depends on). Pull request: https://github.com/jenkinsci/jenkins/pull/1278 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-22373) IE 9 regular mode: Enter does not work to submit forms
Tom FENNELLY edited a comment on JENKINS-22373 IE 9 regular mode: Enter does not work to submit forms I parked trying to sort out JENKINS-23405 for now - issues replicating the same release structure as was used to create the 2.9.0 YUI resources (which Jenkins depends on). Pull request: https://github.com/jenkinsci/jenkins/pull/1278 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-23405) Proper incorporation of YUI
Tom FENNELLY commented on JENKINS-23405 Proper incorporation of YUI I spent more time trying to produce a YUI2 "release" consistent with whatever produced the 2.9.0 release. Still lots of little picky diffs. Will wait and see if I can get someone from the YUI community to point me to where the YUI2 release scripts are. 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] [description-setter] (JENKINS-23097) Set description during build as a build step
SCM/JIRA link daemon commented on JENKINS-23097 Set description during build as a build step Code changed in jenkins User: Marco Miller Path: pom.xml src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterBuilder.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterHelper.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisher.java src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/config.jelly src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/config_ja.properties src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description_ja.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-regexp.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-regexp_ja.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help_ja.html src/test/java/hudson/plugins/descriptionsetter/DescriptionSetterBuilderTest.java src/test/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisherTest.java src/test/java/hudson/plugins/descriptionsetter/TestBuilder.java http://jenkins-ci.org/commit/description-setter-plugin/9f47d84e0c126a49ffed9990763237360629540c Log: Merge pull request #3 from jonaskaveby/description-setter-builder FIXED JENKINS-23097 Set description during build as a build step. Compare: https://github.com/jenkinsci/description-setter-plugin/compare/823db6bcd975...9f47d84e0c12 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] [description-setter] (JENKINS-23097) Set description during build as a build step
SCM/JIRA link daemon resolved JENKINS-23097 as Fixed Set description during build as a build step Change By: SCM/JIRA link daemon (13/Jun/14 4:51 PM) 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] [description-setter] (JENKINS-23097) Set description during build as a build step
SCM/JIRA link daemon commented on JENKINS-23097 Set description during build as a build step Code changed in jenkins User: Jonas Kåveby Path: pom.xml src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterBuilder.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterHelper.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisher.java src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/config.jelly src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/config_ja.properties src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description_ja.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-regexp.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-regexp_ja.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help_ja.html src/test/java/hudson/plugins/descriptionsetter/DescriptionSetterBuilderTest.java src/test/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisherTest.java src/test/java/hudson/plugins/descriptionsetter/TestBuilder.java http://jenkins-ci.org/commit/description-setter-plugin/43a98d9f6d1a7f0df3505769931654da654827f3 Log: FIXED JENKINS-23097 Set description during build as a build step. This change allows the description of a build to be set as a part of building. Setting the description early is useful if you have time consuming builds. Common description setter functionality is extracted to a helper class in order to avoid code copy when implementing the new builder. The common helper class also properly closes a reader after parsing a log file. The test builder is moved to a separate class in order to avoid code copy when implementing more test classes. The test builder is now compatible with jenkins-core 1.414 or later by defining a Descriptor, mandatory since JENKINS-9687. The parent version is bumped to 1.480.3 in order to compile against Java 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] [core] (JENKINS-9687) Log which build step changed the build result
SCM/JIRA link daemon commented on JENKINS-9687 Log which build step changed the build result Code changed in jenkins User: Jonas Kåveby Path: pom.xml src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterBuilder.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterHelper.java src/main/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisher.java src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/config.jelly src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/config_ja.properties src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-description_ja.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-regexp.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help-regexp_ja.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help.html src/main/resources/hudson/plugins/descriptionsetter/DescriptionSetterBuilder/help_ja.html src/test/java/hudson/plugins/descriptionsetter/DescriptionSetterBuilderTest.java src/test/java/hudson/plugins/descriptionsetter/DescriptionSetterPublisherTest.java src/test/java/hudson/plugins/descriptionsetter/TestBuilder.java http://jenkins-ci.org/commit/description-setter-plugin/43a98d9f6d1a7f0df3505769931654da654827f3 Log: FIXED JENKINS-23097 Set description during build as a build step. This change allows the description of a build to be set as a part of building. Setting the description early is useful if you have time consuming builds. Common description setter functionality is extracted to a helper class in order to avoid code copy when implementing the new builder. The common helper class also properly closes a reader after parsing a log file. The test builder is moved to a separate class in order to avoid code copy when implementing more test classes. The test builder is now compatible with jenkins-core 1.414 or later by defining a Descriptor, mandatory since JENKINS-9687. The parent version is bumped to 1.480.3 in order to compile against Java 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] [grails] (JENKINS-23430) Make grailsw executable
Becca Gaspard created JENKINS-23430 Make grailsw executable Issue Type: Bug Assignee: jeffg2one Components: grails Created: 13/Jun/14 5:16 PM Description: Provide option to make grailsw file excutable when using grails wrapper. See https://issues.jenkins-ci.org/browse/JENKINS-14780 Project: Jenkins Priority: Major Reporter: Becca Gaspard 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-22373) IE 9 regular mode: Enter does not work to submit forms
SCM/JIRA link daemon commented on JENKINS-22373 IE 9 regular mode: Enter does not work to submit forms Code changed in jenkins User: tfennelly Path: changelog.html war/src/main/webapp/scripts/yui/button/button-debug.js war/src/main/webapp/scripts/yui/button/button-min.js http://jenkins-ci.org/commit/jenkins/aa8f5955cd478d4a473f49126dad1a0efecc0e2a Log: JENKINS-22373 Submit on Enter key bug on IE9 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] [grails] (JENKINS-23430) Make grailsw executable
Becca Gaspard commented on JENKINS-23430 Make grailsw executable https://github.com/jenkinsci/grails-plugin/pull/11 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-23431) Google is phasing out OpenID endpoint. Need to move on to G+ sign-in
Kohsuke Kawaguchi created JENKINS-23431 Google is phasing out OpenID endpoint. Need to move on to G+ sign-in Issue Type: Task Assignee: Kohsuke Kawaguchi Components: openid Created: 13/Jun/14 5:42 PM Description: Google is going to shutdown its OpenID endpoint in April 2015. As the base protocol appears to have nothing to do with OpenID, such a new feature probably needs to be implemented in a separate plugin, and OpenID plugin would have to be updated to direct users to the new plugin. This needs to be done sooner because if an user fails to update their plugin by then, they'd lose the ability to login, which makes the update very difficult. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-23431) Google is phasing out OpenID endpoint. Need to move on to G+ sign-in
Kohsuke Kawaguchi commented on JENKINS-23431 Google is phasing out OpenID endpoint. Need to move on to G+ sign-in I looked at the doc a bit, and the new scheme seems to require a client ID and secret. I wonder if it means every Jenkins instance needs to be registered separately. 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] (JENKINS-9589) SSH sessions kept open by Subversion checkout
Todd Rhoades edited a comment on JENKINS-9589 SSH sessions kept open by Subversion checkout Possibly related? http://issues.tmatesoft.com/issue/SVNKIT-467 Also, I haven't fully confirmed this, but it appears to happen when the post commit hook triggers and "No jobs found matching the modified files." Confirmed this was not the case. It happened on a check-in of a single file that was found in an existing job. Running Jenkins 1.532.2 subversion plugin 1.45 svnserve 1.6.15 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] [s3] (JENKINS-23432) S3 publisher fails with String index out of range error
Curtis Kline created JENKINS-23432 S3 publisher fails with String index out of range error Issue Type: Bug Assignee: Michael Watt Components: s3 Created: 13/Jun/14 6:01 PM Description: Just updated Jenkins to latest LTS release and updated S3 plugin to 0.6. All S3 uploads fail with this error message in the console log: ERROR: Publisher hudson.plugins.s3.S3BucketPublisher aborted due to exception java.lang.StringIndexOutOfBoundsException: String index out of range: -25 at java.lang.String.substring(String.java:1937) at java.lang.String.substring(String.java:1904) at hudson.plugins.s3.S3Profile.upload(S3Profile.java:123) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:174) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) at hudson.model.Run.execute(Run.java:1709) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: Jenkins 1.554.2 S3 Plugin 0.6 Project: Jenkins Priority: Major Reporter: Curtis Kline 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-22373) IE 9 regular mode: Enter does not work to submit forms
Tom FENNELLY resolved JENKINS-22373 as Fixed IE 9 regular mode: Enter does not work to submit forms Change By: Tom FENNELLY (13/Jun/14 6:03 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22373) IE 9 regular mode: Enter does not work to submit forms
dogfood commented on JENKINS-22373 IE 9 regular mode: Enter does not work to submit forms Integrated in jenkins_main_trunk #3465 JENKINS-22373 Submit on Enter key bug on IE9 (Revision aa8f5955cd478d4a473f49126dad1a0efecc0e2a) Result = SUCCESS tom.fennelly : aa8f5955cd478d4a473f49126dad1a0efecc0e2a Files : changelog.html war/src/main/webapp/scripts/yui/button/button-min.js war/src/main/webapp/scripts/yui/button/button-debug.js 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-remote-trigger] (JENKINS-22325) Parameterized Remote Trigger Plugin fails with 'FATAL: Invalid JSON String' after triggering the remote build
Jason Swager commented on JENKINS-22325 Parameterized Remote Trigger Plugin fails with FATAL: Invalid JSON String after triggering the remote build I'm having this same problem. It looks like an update is supposed to be rolling out - but no trace of an update being available. 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-23425) View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp
Daniel Beck commented on JENKINS-23425 View or using REST api on a job publishing artifact do not delete war temp file in tomcat7 temp Are you able to reproduce this issue on a vanilla installation of Jenkins 1.567? If so, please provide the exact + complete steps to reproduce 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] [parameterized-remote-trigger] (JENKINS-22325) Parameterized Remote Trigger Plugin fails with 'FATAL: Invalid JSON String' after triggering the remote build
Daniel Beck commented on JENKINS-22325 Parameterized Remote Trigger Plugin fails with FATAL: Invalid JSON String after triggering the remote build Maurice W.: Looks like you hit a bug in maven release plugin when releasing (search the Jenkins mailing list for a fix). You uploaded a snapshot build instead of a proper release. There is no 2.1.2 release available for download. Release builds: http://repo.jenkins-ci.org/simple/releases/org/jenkins-ci/plugins/Parameterized-Remote-Trigger/ Snapshot builds: http://repo.jenkins-ci.org/simple/snapshots/org/jenkins-ci/plugins/Parameterized-Remote-Trigger/ 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] [sauce-ondemand] (JENKINS-23433) NPE in SauceOnDemandReportPublisher.processBuildOutput
John Shuping created JENKINS-23433 NPE in SauceOnDemandReportPublisher.processBuildOutput Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand Created: 13/Jun/14 8:43 PM Description: Hi, in version 1.89 (with jenkins 1.567) we are seeing an NPE that we are not sure what to do about, or what might be wrong. I am kinda just the messenger here, but would be happy to provide any detail I can. We have downgraded to back to 1.53 to avoid this issue for now. Archiving artifacts Recording test results ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception java.lang.NullPointerException at hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher.processBuildOutput(SauceOnDemandReportPublisher.java:90) at hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher.getTestData(SauceOnDemandReportPublisher.java:71) at hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher.getTestData(SauceOnDemandReportPublisher.java:57) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:147) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:182) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1735) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Recording fingerprints Project: Jenkins Priority: Major Reporter: John Shuping 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] (JENKINS-23424) Existing working directory is not updated
Mark Waite commented on JENKINS-23424 Existing working directory is not updated Please provide more details about the conditions around the bug you're reporting. If that type of bug is happening in common configurations, I'd expect many reports from users of the git plugin. Have you configured the "Branch to build" as a branch which is not changing? I attempted to duplicate your report by creating a job which performs a checkout, then appends text to one of the tracked files. Each time I run the job, it correctly resets the workspace to the state of the git repository, then appends a single line to the tracked file and completes successfully. If the repository were not being reset, the append would have caused those lines to accumulate, but there is always only one line visible at the end of the file. 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] (JENKINS-23424) Existing working directory is not updated
Mark Waite updated JENKINS-23424 Existing working directory is not updated Change By: Mark Waite (13/Jun/14 11:22 PM) Component/s: git-client 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] [tasks-plugin] (JENKINS-22744) cp1251 encoding issue when viewing Details tab
Martin Ende commented on JENKINS-22744 cp1251 encoding issue when viewing Details tab I would like to support the investigation of that issue by creating a test case in the scope of the acceptance test harness project which helps to reproduce the issue. Unfortunately, I had some problems with the Java file attached to this issue. When I download it with Firefox running under Ubuntu, it seems to be automatically saved as ISO-8859-1 and I cannot convert it into windows-1251. I'll try to download it under Windows tomorrow. I hope that this will preserve the original encoding as the cp1251 is a windows proprietary encoding. 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.
