[JIRA] [config-rotator-plugin] (JENKINS-26623) Error when component without dep. baseline (our case 12441)
Mads Nielsen resolved JENKINS-26623 as Fixed Error when component without dep. baseline (our case 12441) Change By: Mads Nielsen (29/Jan/15 4:30 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] [warnings-plugin] (JENKINS-26682) Can't parse jslint-formatted XML file
DEMEY Emmanuel updated JENKINS-26682 Cant parse jslint-formatted XML file Change By: DEMEY Emmanuel (29/Jan/15 4:32 PM) Attachment: jenkins.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] [workflow-plugin] (JENKINS-26692) RFE: workflow-plugin: specify job delay when running a build job
Jesse Glick updated JENKINS-26692 RFE: workflow-plugin: specify job delay when running a build job Change By: Jesse Glick (29/Jan/15 4:43 PM) Labels: delayjenkinspluginpluginsworkflowworkflow-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] [build-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon commented on JENKINS-26693 Build token root can not start Workflow plugin jobs Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/b93a873874989b73644b42857422e6df79cfa2ea Log: JENKINS-26693 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26675) JVM-versions for autoinstall is not being updated
dennis Hoer commented on JENKINS-26675 JVM-versions for autoinstall is not being updated I'm talking about the dropdown list under Manage Jenkins - Configure System - JDK Installation section. This list is not showing the latest 8u31 and 7u75 versions. If I remember correctly, this list automatically gets updated and doesn't require a Jenkins outage to refresh the list. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26675) JVM-versions for autoinstall is not being updated
dennis Hoer edited a comment on JENKINS-26675 JVM-versions for autoinstall is not being updated I'm talking about the dropdown list under Manage Jenkins - Configure System - JDK Installation section. This list is not showing the latest 8u31 and 7u75 versions. If I understand correctly, this list is automatically updated via http://mirror.xmission.com/jenkins/updates/updates/hudson.tools.JDKInstaller.json. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26692) RFE: workflow-plugin: specify job delay when running a build job
Raymond Barbiero
created JENKINS-26692
RFE: workflow-plugin: specify job delay when running a build job
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
29/Jan/15 4:28 PM
Description:
When I start a job, e.g.:
build job: ‘start-job', parameters: [new hudson.model.StringParameterValue('name',aha)]
The default delay is used. Can the DSL provide a verb to specify the delay? Or specify no delay? Similar to the build URL parameter delay=0sec
Project:
Jenkins
Labels:
workflow-plugin
workflow
jenkins
plugin
plugins
delay
Priority:
Minor
Reporter:
Raymond Barbiero
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-26682) Can't parse jslint-formatted XML file
DEMEY Emmanuel commented on JENKINS-26682 Cant parse jslint-formatted XML file It looks like we have some problem with our Jenkins. Because I have created a job, fetching your github repository. And I have configure the Warning plugin, in order to parse the single.xml file you have in your src/test package and I have the same error. :s I tried another solution, with my own parser, configured in the Admin part of Jenkins. Here is the structure of the error message : app/_javascript_/test.js: line 2, col 8, Error - 'angular' is not defined. (no-undef) You will find in the attached file the configuration of new parser. When I execute my job, I have a similar issue : Commencing build of Revision d1de912ac99d897ca5c4ce97331f431cbe6a9c95 (origin/HEAD, origin/master) Checking out Revision d1de912ac99d897ca5c4ce97331f431cbe6a9c95 (origin/HEAD, origin/master) Warning : There are multiple branch changesets here [testworkflowgrunt-ci-1] $ /bin/bash -xe /tmp/hudson1893862861617495453.sh + npm install npm WARN package.json tutoGruntWorkflow@1.0.0 No repository field. + ./node_modules/grunt-cli/bin/grunt eslint:app [4mRunning "eslint:app" (eslint) task [24m app/_javascript_/test.js: line 2, col 8, Error - 'angular' is not defined. (no-undef) 1 problem [33mWarning: Task "eslint:app" failed. Use --force to continue. [39m [31mAborted due to warnings. [39m + true [WARNINGS] Parsing warnings in console log with parser ESLint ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.lang.IllegalStateException: java.io.IOException: Underlying input stream returned zero bytes at org.apache.commons.io.LineIterator.hasNext(LineIterator.java:107) at hudson.plugins.warnings.parser.RegexpLineParser.parse(RegexpLineParser.java:93) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:315) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:294) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:398) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:320) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:780) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:752) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1617) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Finished: FAILURE any ideas ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
Raymond Barbiero created JENKINS-26693 Build token root can not start Workflow plugin jobs Issue Type: Bug Assignee: Jesse Glick Components: build-token-root-plugin Created: 29/Jan/15 4:34 PM Description: Workflow jobs do not start when kicked off from a build-token-root URL. Project: Jenkins Labels: workflow workflow-plugin plugin plugins Priority: Minor Reporter: Raymond Barbiero This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
Jesse Glick updated JENKINS-26693 Build token root can not start Workflow plugin jobs Change By: Jesse Glick (29/Jan/15 4:42 PM) Labels: pluginplugins workflow workflow-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] [build-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon commented on JENKINS-26693 Build token root can not start Workflow plugin jobs Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/c1b7f6761b9c0a86be9f1d2106b61341eaf1ff71 Log: Noting JENKINS-26693 in a more appropriate section. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick updated JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Yes one workaround would be delete all numeric SYMLINKD, though I am not sure if there is an easy batch command to do that. Still intend to try to reproduce this and offer a proper fix. Change By: Jesse Glick (29/Jan/15 4:51 PM) Summary: Buildrecordsnotmigrateddueto“failedtorename”onWindows esp.onJava6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26659) file permissions aren't protected after archive/unarchive
Jesse Glick commented on JENKINS-26659 file permissions arent protected after archive/unarchive Yes, of course it is best to avoid relying on it (and for example tar up any files locally whose exact permissions you want to preserve), but insofar as the archive step (using StandardArtifactManager) preserves permissions and symlinks, unarchive should as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24512) Add option to lock the created workspace to a host
Paul Allen commented on JENKINS-24512 Add option to lock the created workspace to a host Ok, so this works for slaves, but I totally forgot if you don't use slaves then NODE_NAME returns 'master'. Unless you're Jenkins server's hostname is 'master' this isn't much use. I have added some helper function to access the real hostname from the Computer object, but this gives a FQDN; is that an issue or should I look to shorten it to just the machine alias? e.g. foo.domain.com -- foo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-26655) - error 'JSONObject[smtpServer] not found.'
Tom FENNELLY commented on JENKINS-26655 - error JSONObject[smtpServer] not found. Hi Dani. Thanks for letting us know. I'll keep an eye out for it when fixing the other 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] [warnings-plugin] (JENKINS-26682) Can't parse jslint-formatted XML file
DEMEY Emmanuel commented on JENKINS-26682 Cant parse jslint-formatted XML file I have tested the generated jslint report with the unit test of the plugin, it looks everything is OK. :s This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26617) Old Misleading Email Notifications being Sent
Sundeep Dhunna resolved JENKINS-26617 as Not A Defect Old Misleading Email Notifications being Sent Looking again closely at the email header showed a different server sent the email. It turns out that IT cloned the build server. That copy was attempting to run the builds, failing and sending the emails. We have corrected this and the emails stopped. Thanks for your support. Change By: Sundeep Dhunna (29/Jan/15 5:07 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26681) Improve Performance of S3 Entry upload which contain a *lot* of files
Ray H created JENKINS-26681 Improve Performance of S3 Entry upload which contain a *lot* of files Issue Type: Bug Assignee: Unassigned Components: s3-plugin Created: 29/Jan/15 8:34 AM Description: This can be a little frustrating when you're trying to upload alot of files to S3, i.e. updating a static site. This is more of an implementation issue where the current approach (while clever), tries to flatten all the upload requests and uploads them one at a time. The better approach would be to use a TransferManager and batch upload all the Entries together. I want to take this on but there's some code I'd like to refactor to get there. Project: Jenkins Priority: Minor Reporter: Ray H This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-23432) S3 publisher fails with String index out of range error
Ray H commented on JENKINS-23432 S3 publisher fails with String index out of range error So it sounds like the problem is related to people's expectation is that the S3 plugin should take a comma separated list b/c the ANT path specifier usually allows that. I think it'd be reasonable to actually support comma separated values. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-23432) S3 publisher fails with String index out of range error
Ray H edited a comment on JENKINS-23432 S3 publisher fails with String index out of range error So it sounds like the problem is related to people's expectation is that the S3 plugin should take a comma separated list b/c the ANT path specifier usually allows that. I think it'd be reasonable to actually support comma separated values. However is this reimplementing the idea of having multiple entries. Hm? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-16025) Allow full path when uploading a file
Ray H commented on JENKINS-16025 Allow full path when uploading a file IMO it seems that if we want to make this less 'magical', we should allow the user to specify a prefix path, i.e. if I have a file at foo/bar/baz/qux.zip. Then I'd specify: prefixPath = foo/bar search=baz/* so that when I upload to `myBucket`, it should uploaded to s3://myBucket/baz/qux.zip` whereas the current behavior: of specifying sourceFile = `foo/bar/baz/*` would upload it to the root directory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-19934) Add Job Create permission to project roles
podskalsky commented on JENKINS-19934 Add Job Create permission to project roles I have the same problem: the project role "Job create" with using the Restrict project naming "Role-Based Strategy" (defined pattern) is not running as mentioned. only the global role "Job create" is allowed to create Jobs, but without defined patterns Here is the Help text ... Help for feature: Role-Based Strategy Restricts Job creation according to role based settings. Global role allows create with any name, project role according to defined pattern This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-19934) Add Job Create permission to project roles
Oleg Nenashev commented on JENKINS-19934 Add Job Create permission to project roles Seems Kanstantsin Shautsou is too busy to handle this issue. I'll try to reproduce it according to the comments above. There's an issue in the code with Folders plugin. regexp filters for such jobs won't be applied correctly The message is not completely sensible, of course: the users is already logged in! There can be an impersonation issue within the code The user then reported that the tabbed views at the top of the Jenkins page had disappaeared! This was shown to me. REMOVING the global "Discover" permission restored the view tabs. I cannot imagine what would cause that, I'm half doubting the evidence of my eyes, but it seemed to be as reported. No idea. I suppose it is not related to this issue. Please file a new one to role-strategy (or Jenkins core) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-19934) Add Job Create permission to project roles
Oleg Nenashev assigned JENKINS-19934 to Oleg Nenashev Add Job Create permission to project roles Change By: Oleg Nenashev (29/Jan/15 9:10 AM) Assignee: KanstantsinShautsou OlegNenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-6268) Make checking for modification time of junit results be configurable and off by default
Rolf Geuenich commented on JENKINS-6268 Make checking for modification time of junit results be configurable and off by default Hi, I want to run "JUnit Result Archiver" belated on a nightly build to test different options and need the option to configure the amount of time for difference, which is ok. Or an option to disable this check at all. This case is 5 years old and no one will fix it? I hope someone will fix it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Another excerpt with newest build: Jan 29, 2015 8:50:35 AM WARNUNG jenkins.model.RunIdMigrator doMigrate failed to process d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\2014-10-16_10-32-01 java.io.IOException: d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\68 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5995 Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5996 Jan 29, 2015 8:50:35 AM WARNUNG jenkins.model.RunIdMigrator doMigrate failed to process d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\2014-11-05_16-13-26 java.io.IOException: d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\69 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5997 Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5998 Jan 29, 2015 8:50:35 AM INFO jenkins.model.RunIdMigrator migrate Migrating build records in d:\NightlyBuilds\Jenkins\jobs\KomalogWin - 14.01-dev\builds Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 124 Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 128 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-26682) Can't parse jslint-formatted XML file
DEMEY Emmanuel created JENKINS-26682 Cant parse jslint-formatted XML file Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 29/Jan/15 9:24 AM Description: Hi everyone, I spent few hours on that issue yesterday afternoon and this morning, without any solutions . I have a freestyle job that will generate a JSLint XML report thanks to the ESLint Quality tool. (pwd and ls are just debugging ) npm install ./node_modules/bower/bin/bower install node ./node_modules/eslint/bin/eslint --config config/eslint.json --rulesdir config/rules --format jslint-xml -o lint.xml --quiet app/_javascript_ || true pwd ls I have configured the Warning Plugin to parse the lint.xml file with the JSLint parser. When I run my Job, here is the output : [testworkflowgrunt-ci-1] $ /bin/bash -xe /tmp/hudson3519419950863763056.sh + npm install npm WARN package.json tutoGruntWorkflow@1.0.0 No repository field. + ./node_modules/bower/bin/bower install + node ./node_modules/eslint/bin/eslint --config config/eslint.json --rulesdir config/rules --format jslint-xml -o lint.xml --quiet app/_javascript_ + true + pwd /DATA/jenkins/workspace/testworkflowgrunt-ci-1 + ls app bower.json checkstyle.xml config grunt Gruntfile.js jslint.xml lint.xml node_modules package.json README.md [WARNINGS] Parsing warnings in files 'lint.xml' with parser JSLint [WARNINGS] Finding all files that match the pattern lint.xml [WARNINGS] Parsing 1 files in /DATA/jenkins/workspace/testworkflowgrunt-ci-1 [WARNINGS] Parsing of file /DATA/jenkins/workspace/testworkflowgrunt-ci-1/lint.xml failed due to an exception: java.io.IOException: Underlying input stream returned zero bytes at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:287) at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) at java.io.InputStreamReader.read(InputStreamReader.java:184) at java.io.Reader.read(Reader.java:140) at org.apache.tools.ant.util.ReaderInputStream.read(ReaderInputStream.java:117) at org.apache.xerces.impl.XMLEntityManager$RewindableInputStream.read(Unknown Source) at org.apache.xerces.impl.io.UTF8Reader.read(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.skipSpaces(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(SAXParser.java:195) at hudson.plugins.warnings.parser.LintParser.parse(LintParser.java:49) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:315) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:294) at hudson.plugins.warnings.parser.FileWarningsParser.parse(FileWarningsParser.java:53) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:306) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:264) at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:215) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:184) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2394) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at
[JIRA] [core] (JENKINS-26679) BUILD_ID not containing build timestamp after 1.597 due to JENKINS-24380
Daniel Beck resolved JENKINS-26679 as Duplicate BUILD_ID not containing build timestamp after 1.597 due to JENKINS-24380 JENKINS-26520 Change By: Daniel Beck (29/Jan/15 10:33 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26606) Unable send email
qa Xperthis commented on JENKINS-26606 Unable send email Exactly the same issue for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26606) Unable send email
Tom FENNELLY commented on JENKINS-26606 Unable send email oops sorry ... I thought there were some basic unit tests in there testing this. Will fix it ASAP. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25465) ${GIT_BRANCH} macro expands full branch name + remotes instead of short name
Horst Krause
commented on JENKINS-25465
${GIT_BRANCH} macro expands full branch name + remotes instead of short name
Contrary to the comment from 24. Nov in the build name setter plugin ${GIT_BRANCH} will result in "master" and not in "origin/master".
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-plugin] (JENKINS-25465) ${GIT_BRANCH} macro expands full branch name + remotes instead of short name
Horst Krause
edited a comment on JENKINS-25465
${GIT_BRANCH} macro expands full branch name + remotes instead of short name
Contrary to the comment from 24. Nov in the build name setter plugin ${GIT_BRANCH} will result in "master" and not in "origin/master" or "remotes/origin/master".
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26686) Jenkins ignores javaagent failure in test cases
Wisen Tanasa created JENKINS-26686 Jenkins ignores javaagent failure in test cases Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 29/Jan/15 11:54 AM Description: When we have a failure of test cases due to javaagent failure, Jenkins are ignoring the test result and mark the build status as SUCCESS. Log: ... ... FATAL ERROR in native method: processing of -javaagent failed /bin/sh: line 1: 16902 Aborted /opt/build/jdk/jdk1.6.0_45/jre/bin/java -javaagent:/data/hudson/jobs/foo/workspace/.repository/fixme/jmockit/1.0/jmockit-1.0.jar -jar /tmp/surefirebooter3725770228654412047.jar /tmp/surefire2623483402548392725tmp /tmp/surefire6196487644916225973tmp Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323) at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338) Caused by: java.lang.NoSuchMethodError: mockit.internal.RedefinitionEngine.setUpMock(Ljava/lang/Class;)V at mockit.internal.ToolLoader.setUpExternalMock(ToolLoader.java:104) at mockit.internal.ToolLoader.visitEnd(ToolLoader.java:92) at org.objectweb.asm2.ClassReader.accept(ClassReader.java:1147) at org.objectweb.asm2.ClassReader.accept(ClassReader.java:300) at mockit.internal.Startup.loadExternalTool(Startup.java:156) at mockit.internal.Startup.initialize(Startup.java:114) at mockit.internal.Startup.premain(Startup.java:96) ... 6 more FATAL ERROR in native method: processing of -javaagent failed /bin/sh: line 1: 16925 Aborted /opt/build/jdk/jdk1.6.0_45/jre/bin/java -javaagent:/data/hudson/jobs/foo/workspace/.repository/fixme/jmockit/1.0/jmockit-1.0.jar -jar /tmp/surefirebooter4869326884051725104.jar /tmp/surefire9113749607916052890tmp /tmp/surefire4100425927814768287tmp [ERROR] There are test failures. ... ... Finished: SUCCESS Environment: maven-plugin 2.1 jenkins 1.553 Project: Jenkins Priority: Major Reporter: Wisen Tanasa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26612) svn: absolutely unacceptably SLOW
Steven Christou updated JENKINS-26612 svn: absolutely unacceptably SLOW Change By: Steven Christou (29/Jan/15 9:45 AM) Description: Ihavenocluehowbrokensvnpluginis,butittakeswaytomuchtodosvnupdateonmysvnrepo.Lookslikeitusessomethingelse(e.g.svnclientimplementationmadeinpurejava?!)insteadofrealsvn-client.Mysvnrepois4GB,76,220Files,4,371Folders.IfIsimplycdintothetopdiranddosvnupdatefromcommandpromptittakes7seconds.Whenjenkinsrunsthesvnupdateittakesafewminutes(Ididnteventrytomeasure,buteverytimeItakealooktheconsoleprogressisstuckonUpdating...step.Pleaseprovideawaytomakeitusenormalsvn-clientinstead,otherwiseitsjustunusablethatway.ForthesamereasonIactuallyhadtousesimpleupdateoption,updateandrevertwasexceptionally assproken broken optionthatIthinkwastakinglikehalfanhourtocomplete.IhadtowritemyownbatchscriptthatmakesthebuildandIdosvnrevert-Rmanuallyfrommyownbuildscriptinstead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [customtools-plugin] (JENKINS-26683) Get rid of dependency on Extended Choice Parameter plugin
stanislav bashkirtsev created JENKINS-26683 Get rid of dependency on Extended Choice Parameter plugin Issue Type: Improvement Assignee: Oleg Nenashev Components: customtools-plugin Created: 29/Jan/15 10:11 AM Description: Is there a real need to depend on Extended Choice Parameter? I'd like to use Custom Tools, but don't want to install an extra plugin like Extended Choice (my team hates it ). So if Custom Tools can work without additional dependency, that would be fantastic. I've noticed that Extended Choice is used only for tools versioning (which throws exceptions anyway), would be great to simply specify the version as a plain string. Project: Jenkins Priority: Major Reporter: stanislav bashkirtsev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Build #3957 Log extract... 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-10_17-23-06 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\273 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\GEMTEST_Page_84\builds\2014-12-23_14-42-31 java.io.IOException: C:\Jenkins\jobs\GEMTEST_Page_84\builds\1420 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-26_13-03-35 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\288 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Jenkins is running on Running on a Virtual Machine with - Windows Server 2008 R2 Standard with Service Pack 1 Java version is - Java Standard Edition Version 8 Update 31 NOTE: Tried experiment if I manually delete the shortcut directories in a job directory then migration is okay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are
[JIRA] [core] (JENKINS-26685) No empty value for a build's buildOn data
Sebastian Feldmann created JENKINS-26685 No empty value for a builds buildOn data Issue Type: Improvement Assignee: Unassigned Components: core Created: 29/Jan/15 11:06 AM Description: The buildOn property for a build should not be empty. Set to "master" or if set to the master's label by default would be great. "builtOn": "", "buildOn": "my master label" Project: Jenkins Labels: api build Priority: Minor Reporter: Sebastian Feldmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-26655) - error 'JSONObject[smtpServer] not found.'
dani spahieva commented on JENKINS-26655 - error JSONObject[smtpServer] not found. The installed Mailer plugin is v 1.13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26606) Unable send email
Daniel Beck updated JENKINS-26606 Unable send email Assigning to Tom FENNELLY as he seems to have broken it: https://github.com/jenkinsci/mailer-plugin/compare/mailer-1.12...mailer-1.13 Possibly due to missing space after comma. Change By: Daniel Beck (29/Jan/15 11:08 AM) Assignee: TomFENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26612) svn: absolutely unacceptably SLOW
Steven Christou commented on JENKINS-26612 svn: absolutely unacceptably SLOW Could you take several thread dumps while the checkout is happening (kill -3 $PID, or jstack $PID)? This would help with debugging and understanding where some slow points are happening, and any places in the code threads are stuck at. While doing initial testing before I released I was able to perform checkouts (svn 1.8) with speeds with little (to sometime no) difference than through command line. I will look into setting up an environment to perform svn checkouts with several GB. Pablob P I have tried to make several attempts at using a native api (javahl, svnkit + native libraries, etc.), however I do not believe they are safe to use. Debugging issues increases the complexity because each native library has a different libsvn implementation (default *nix libsvn libraries, vendor libsvn implementations, etc). SVNKIT offers a pure java implementation which is easier to debug. Another issue is we would need to be careful and make sure to guard against native code potentially crashing the JVM. We could try something similar to what the git plugin does (define the svn executable or pick svnkit), but that would require a major rework. Pablob P I understand your frustration, but please do not use bad language. I am really sorry about the issue you are experiencing, and I am making efforts to resolve any performance issues users are experiencing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [customtools-plugin] (JENKINS-26683) Get rid of dependency on Extended Choice Parameter plugin
stanislav bashkirtsev commented on JENKINS-26683 Get rid of dependency on Extended Choice Parameter plugin That's still a good news since this is planned to be done. 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] [other] (JENKINS-26655) - error 'JSONObject[smtpServer] not found.'
Daniel Beck commented on JENKINS-26655 - error JSONObject[smtpServer] not found. What version of the mailer plugin is 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] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains a whitespace
Janno Jõgeva commented on JENKINS-24686 scm-sync-configuration fails if job name contains a whitespace I do not experience this issue on an Ubuntu 14.04 when using external repo but have the problem on CentOS 7 when using local repo. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [customtools-plugin] (JENKINS-26683) Get rid of dependency on Extended Choice Parameter plugin
Oleg Nenashev commented on JENKINS-26683 Get rid of dependency on Extended Choice Parameter plugin The hardcoded usage of Extended Choice plugin was a bad architectural decision in any case. It was quite OK till 0.29, but current versions are horribly unstable. The code is not good as well. I'm going to add ToolVersionProvider extension point and then decouple the ExtendedChoice integration into a separate plugin. See JENKINS-24114 for more info. Unfortunately, I still cannot find a time to implement the feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26661) View tabs does move depending on the selected view
Daniel Beck resolved JENKINS-26661 as Duplicate View tabs does move depending on the selected view JENKINS-25953 Change By: Daniel Beck (29/Jan/15 10:35 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26684) Maven build step fail to launch mvn process when special chars are present in build variables
Oliver Gondža created JENKINS-26684 Maven build step fail to launch mvn process when special chars are present in build variables Issue Type: Bug Assignee: Oliver Gondža Components: core Created: 29/Jan/15 10:54 AM Description: Maven build step put all build variables on command line as properties. This causes problems when special characters are used. This happens often when non-trivial label expressions are used: -Dlabel_exp=w2k8x86. Project: Jenkins Priority: Major Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26685) No empty value for a build's buildOn data
Daniel Beck commented on JENKINS-26685 No empty value for a builds buildOn data The node name of the Jenkins master is the empty string (Jenkins.instance.nodeName), possibly to distinguish from slave nodes with any specific name. Not sure this should be changed as it would introduce ambiguity for users with particularly stupid slave node names. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-26655) - error 'JSONObject[smtpServer] not found.'
Daniel Beck updated JENKINS-26655 - error JSONObject[smtpServer] not found. Assigning to Tom FENNELLY as this may be related to the mailer 1.13 release as well. Change By: Daniel Beck (29/Jan/15 12:20 PM) Assignee: TomFENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-21536) GIT_BRANCH should not change after merge
Ingo Mohr commented on JENKINS-21536 GIT_BRANCH should not change after merge Same problem here. We locally merge a feature branch (or bugfix branch) to master in order to check whether the branch can be merged later with a pull request. And for this, we need the "actual" feature branch name. But on Jenkins, the name of the $GIT_BRANCH is always "master" once we've locally merged. Maybe, an all-new variable should be added since the GIT_BRANCH name actually is "master. It's just: we need the name of the branch merged before building. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26687) [Downloadable Tool Installer] Improve error message for invalid JSON file X509 signature
Cyrille Le Clerc commented on JENKINS-26687 [Downloadable Tool Installer] Improve error message for invalid JSON file X509 signature See https://github.com/jenkinsci/jenkins/pull/1552 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26658) NPE when launching JNLP slave with blank in name in recent JRE
Michael Keppler commented on JENKINS-26658 NPE when launching JNLP slave with blank in name in recent JRE When collecting your requested data, I found there is a totally different root cause. We have that command in a batch file, and Windows interprets the %2 from the escaped blank as batch parameter, replacing it with an empty string. Escaping with another percent sign in the batch file (i.e. blank%%20name) fixes everything. So basically there is no bug in Jenkins. However, everyone just copying the command line of a slave with a blank in the name will easily run into the same trouble. Maybe a note could be added to the slave page? I'm fine if you just close the bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26688) [Tool Installer] Downloadable Tool Installers broken because X509 cert is expired [CN=Community Update Center, O=Jenkins Project, ST=California, C=US]
Cyrille Le Clerc created JENKINS-26688 [Tool Installer] Downloadable Tool Installers broken because X509 cert is expired [CN=Community Update Center, O=Jenkins Project, ST=California, C=US] Issue Type: Improvement Assignee: Unassigned Components: core Created: 29/Jan/15 12:31 PM Description: Stack trace collected using https://github.com/jenkinsci/jenkins/pull/1552 X509 Certificate "CN=Community Update Center, O=Jenkins Project, ST=California, C=US" is rejected with "CertificateExpiredException: NotAfter: Tue Jan 27 22:04:07 CET 2015" Certificate validation failed with certs [CN=Community Update Center, O=Jenkins Project, ST=California, C=US] in downloadable #039;hudson.tools.JDKInstaller#039; a href='' class='showDetails'(show details)/apre style='display:none'java.security.cert.CertPathValidatorException: timestamp check failed at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:129) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:212) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140) at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79) at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292) at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:79) at hudson.model.DownloadService$Downloadable.load(DownloadService.java:305) at hudson.model.DownloadService$Downloadable.doPostBack(DownloadService.java:293) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) 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.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) 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:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) 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
[JIRA] [mailer-plugin] (JENKINS-26606) Unable send email
Tom FENNELLY commented on JENKINS-26606 Unable send email @Horst can you provide the full stacktrace please? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26687) [Downloadable Tool Installer] Improve error message for invalid JSON file X509 signature
Cyrille Le Clerc created JENKINS-26687 [Downloadable Tool Installer] Improve error message for invalid JSON file X509 signature Issue Type: Improvement Assignee: Cyrille Le Clerc Components: core Created: 29/Jan/15 12:09 PM Description: Add details of the X509 certificates when the verification of the signature of the JSON file fails. Current message: Signature verification failed in downloadable hudson.tools.JDKInstaller ... java.security.cert.CertPathValidatorException: timestamp check failed at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:129) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:212) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140) at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79) at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292) at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:92) at hudson.model.DownloadService$Downloadable.load(DownloadService.java:305) at hudson.model.DownloadService$Downloadable.doPostBack(DownloadService.java:293) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) 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:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) 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:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) 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 com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter._doFilter(OfflineSecurityRealmFilter.java:67) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter.doFilter(OfflineSecurityRealmFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.opscenter.security.ClusterSessionFilter._doFilter(ClusterSessionFilter.java:69) at com.cloudbees.opscenter.security.ClusterSessionFilter.doFilter(ClusterSessionFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] [downstream-ext-plugin] (JENKINS-26674) Unable to delete project.
Daniel Beck updated JENKINS-26674 Unable to delete project. Change By: Daniel Beck (29/Jan/15 12:22 PM) Assignee: kutzi Component/s: downstream-ext-plugin Component/s: jenkins-tracker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Horst Krause commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH I linked some issue also struggeling with GIT-Sonar integration. Seems to be a quite common problem and would be very nice to get a solution. Especially as it seems to be quite simple for you. I would have provided the pull request, but the tests don't pass even before doing any change. Do I need any special setup on windows? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unreliable-slave-plugin] (JENKINS-23568) Unreliable slave Plugin will offline the slave or not? what’s the meaning of “try slave reconnect of put offline”? how to use the plugin?
SCM/JIRA link daemon resolved JENKINS-23568 as Fixed Unreliable slave Plugin will offline the slave or not? what’s the meaning of “try slave reconnect of put offline”? how to use the plugin? Change By: SCM/JIRA link daemon (29/Jan/15 12:11 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-22811) Folder loading can be broken by a NPE in a build wrapper in one job
SCM/JIRA link daemon commented on JENKINS-22811 Folder loading can be broken by a NPE in a build wrapper in one job Code changed in jenkins User: christ66 Path: core/src/main/java/hudson/model/ItemGroupMixIn.java test/src/test/java/hudson/model/ItemGroupMixInTest.java test/src/test/resources/hudson/model/ItemGroupMixInTest/xmlFileReadExceptionOnLoad.zip http://jenkins-ci.org/commit/jenkins/3520042b1b4cdd11f07c4f4d5a80aeafa1a09377 Log: JENKINS-22811 Folder loading can break when an item inside the folder fails to load or throws an Exception. (cherry picked from commit 3e29bd7eff12d73a9b49c1d6039dc6d0699db15a) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unreliable-slave-plugin] (JENKINS-23568) Unreliable slave Plugin will offline the slave or not? what’s the meaning of “try slave reconnect of put offline”? how to use the plugin?
SCM/JIRA link daemon commented on JENKINS-23568 Unreliable slave Plugin will offline the slave or not? what’s the meaning of “try slave reconnect of put offline”? how to use the plugin? Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractProject.java http://jenkins-ci.org/commit/jenkins/16ee133b480787101edc039d94c4f6ff055d4ff7 Log: FIXED JENKINS-23568 Be sure to release WorkspaceList.Lease deterministically in a finally block. (cherry picked from commit 47fa17ba61dac99052304b5a9bb44878ed5898c6) Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/e471b8b0e21e...16ee133b4807 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-26655) - error 'JSONObject[smtpServer] not found.'
Tom FENNELLY commented on JENKINS-26655 - error JSONObject[smtpServer] not found. Can you try 1.12 too please? At first glance, it doesn't appear to be related to the changes I made. Not that that really matters anyway since I'll try fix it either way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26685) No empty value for a build's buildOn data
Sebastian Feldmann commented on JENKINS-26685 No empty value for a builds buildOn data This has led to problems in the past JENKINS-9671 I think it would be more consitent to set buildOn to "master" if it was build there even if some naming ambiguities could occure for some users with "stupid" slave node names. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26689) javax.mail.internet.AddressException when more than one recipient should receive job status email
Robert Oschwald created JENKINS-26689 javax.mail.internet.AddressException when more than one recipient should receive job status email Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 29/Jan/15 1:40 PM Description: In project, when "Send separate e-mails to individuals who broke the build" is enabled and more than one recipient should receive a job status email, we get: stacktrace Sonar analysis completed: SUCCESS ERROR: Unable to send to address: develop...@sample.ex,develop...@sample.ex javax.mail.internet.AddressException: Illegal address in string ``develop...@sample.ex,develop...@sample.ex'' at javax.mail.internet.InternetAddress.init(InternetAddress.java:114) at hudson.tasks.Mailer.StringToAddress(Mailer.java:180) at jenkins.plugins.mailer.tasks.MimeMessageBuilder.toNormalizedAddress(MimeMessageBuilder.java:254) at jenkins.plugins.mailer.tasks.MimeMessageBuilder.addRecipients(MimeMessageBuilder.java:137) at jenkins.plugins.mailer.tasks.MimeMessageBuilder.addRecipients(MimeMessageBuilder.java:129) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:380) at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:201) at hudson.tasks.MailSender.createMail(MailSender.java:194) at hudson.tasks.MailSender.run(MailSender.java:107) at hudson.tasks.Mailer.perform(Mailer.java:141) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1743) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Sending e-mails to: dev-iss...@sample.ex This happens if you got a failed job and 2 or more developers committed to the project during the fail state. In this case, the build problem was fixed, so 2 developers need to get the email. Seems the formatting of the recipients is wrong. I'm not sure if this problem was also in former versions of the plugin. Environment: CentOS6.6, Jenkins ver. 1.598, email-ext plugin v. 2.39 Project: Jenkins Priority: Minor Reporter: Robert Oschwald This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-26690) Build stats throws illegal argument exception on dashboard view
Davide Bolognini created JENKINS-26690 Build stats throws illegal argument exception on dashboard view Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view-plugin Created: 29/Jan/15 1:49 PM Description: Dear all, on jenkins 1.597 (and also 1.598) the build stats on Dashboard view (version 2.9.4) doesn't work because of: Caught exception evaluating: it.getBuildStat(jobs) in /ci/. Reason: java.lang.IllegalArgumentException: fromKey toKey java.lang.IllegalArgumentException: fromKey toKey at java.util.TreeMap$NavigableSubMap.init(TreeMap.java:1261) at java.util.TreeMap$AscendingSubMap.init(TreeMap.java:1699) at java.util.TreeMap.subMap(TreeMap.java:877) at java.util.TreeMap.subMap(TreeMap.java:918) at jenkins.model.lazy.AbstractLazyLoadRunMap.subMap(AbstractLazyLoadRunMap.java:250) at jenkins.model.lazy.AbstractLazyLoadRunMap.headMap(AbstractLazyLoadRunMap.java:254) at jenkins.model.lazy.AbstractLazyLoadRunMap.headMap(AbstractLazyLoadRunMap.java:88) at java.util.Collections$UnmodifiableSortedMap.headMap(Collections.java:1543) at hudson.plugins.view.dashboard.stats.StatBuilds.getBuildStat(StatBuilds.java:48) etc. Please let me know if you need more info. Regards Davide Project: Jenkins Priority: Critical Reporter: Davide Bolognini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-24980) Keychain Management issue.
lacostej commented on JENKINS-24980 Keychain Management issue. Timothy thanks for your input. I am using OTHER_CODE_SIGN_FLAGS with the plugin. It works for me in combination of using the developer profile. What problems are you having with it ? My main issue is that it makes it more cumbersome for job configuration. Note: the OTHER_CODE_SIGN_FLAGS only work if the keychain as also been added to the search list! From the codesign documentation SIGNING IDENTITIES To be used for code signing, a digital identity must be stored in a keychain that is on the calling user's keychain search list. See http://prod.lists.apple.com/archives/xcode-users/2014/Dec/msg00041.html WRT atomicity, see http://lists.apple.com/archives/xcode-users/2014/Dec/msg00040.html to which someone answered to me offlist with 'man lockfile'for an idea on how to implement adding this in an atomic way See also https://github.com/jenkinsci/xcode-plugin/pull/56 for a pull request that I received with similar intent, and closed because I didn't like the implementation. To summarise, we could add things atomically (using my patch in comment of pr #56, or using lockfile command) we right now lack the ability to remove after usage (see below) there's still the issue of deciding how long the keychain should be opened for use (needs to be somewhat configurable) there's still the issue of making this keychain available at the same time for other processes I don't know yet how to solve it cleanly, and I don't know which use cases are the most important for the people. See also https://groups.google.com/d/msg/jenkinsci-dev/JrHvfNc3cQI/a4rAY1L8Ug0J for my request for input, so far without feedback. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26688) [Tool Installer] Downloadable Tool Installers broken because X509 cert is expired [CN=Community Update Center, O=Jenkins Project, ST=California, C=US]
Jesse Glick resolved JENKINS-26688 as Duplicate [Tool Installer] Downloadable Tool Installers broken because X509 cert is expired [CN=Community Update Center, O=Jenkins Project, ST=California, C=US] Change By: Jesse Glick (29/Jan/15 1:21 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] [other] (JENKINS-26655) - error 'JSONObject[smtpServer] not found.'
dani spahieva commented on JENKINS-26655 - error JSONObject[smtpServer] not found. Hi Tom, I've tried with 1.12. It works well. After that i've upgraded to 1.13 - it's ok too. I saw the bug once and after restarting Jenkins I can't reproduce it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-26695) Causing dead executor threads due to a ConcurrentModificationException being thrown when calling ThrottleJobProperty$DescriptorImpl.getCatego
Vito Paine created JENKINS-26695 Causing dead executor threads due to a ConcurrentModificationException being thrown when calling ThrottleJobProperty$DescriptorImpl.getCategoryByName Issue Type: Bug Assignee: Oleg Nenashev Components: throttle-concurrent-builds-plugin Created: 29/Jan/15 6:15 PM Description: Dead executor (Multiple times) java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) at java.util.AbstractList$Itr.next(AbstractList.java:343) at hudson.plugins.throttleconcurrents.ThrottleJobProperty$DescriptorImpl.getCategoryByName(ThrottleJobProperty.java:170) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canRun(ThrottleQueueTaskDispatcher.java:118) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canRun(ThrottleQueueTaskDispatcher.java:88) at hudson.model.Queue.isBuildBlocked(Queue.java:943) at hudson.model.Queue.maintain(Queue.java:984) at hudson.model.Queue.pop(Queue.java:863) at hudson.model.Executor.grabJob(Executor.java:285) at hudson.model.Executor.run(Executor.java:206) Environment: version 1.7.2 of the plugin Project: Jenkins Priority: Minor Reporter: Vito Paine This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26696) On Windows, P4 plugin pulls down wrong encoding for UTF-16
Ken Morse created JENKINS-26696 On Windows, P4 plugin pulls down wrong encoding for UTF-16 Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 29/Jan/15 6:21 PM Description: When using the new P4 Plugin to populate a workspace, we noticed that if a file of type UTF-16 is pulled down by the plugin, it will be encoded in Big-endian format instead of the Little-endian format more appropriate for Windows. Syncing this same file with either the p4 command line utility or P4V will bring down the file with the proper encoding. Environment: Jenkins 1.580.3 running on 64-bit Windows 8.1, P4 Plugin 1.1.2 Project: Jenkins Priority: Major Reporter: Ken Morse This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26694) Workflow build Parameters are not exposed to CopyArtifact
Jesse Glick updated JENKINS-26694 Workflow build Parameters are not exposed to CopyArtifact The problem is in ParametersBuildFilter. (Why this is a filter as opposed to just a BuildSelector, I have no idea. Weird design.) It uses Run.getEnvironment(TaskListener), which does something with parameters in an AbstractBuild because ParametersAction happens to be an EnvironmentContributingAction. A WorkflowRun does not override getEnvironment, since it has nothing special to add, and parameters in a workflow are passed as Groovy variables, not environment variables. (Anyway EnvironmentContributingAction is currently limited to use on AbstractBuild.) So that trick does not work. Anyway there is no apparent reason why ParametersBuildFilter needs to use getEnvironment, which is a very roundabout way of looking for parameters. It can just look for ParametersAction and check them directly. (Relying on StringParameterValue.equals would be intuitive but is not quite right, since the current code in ParametersBuildFilter assumes that it can match against a non-string ParameterValue whose textual expansion is the expected string. So you would need to call ParameterValue.buildEnvironment. Basically what ParametersAction.buildEnvVars does, without the gratuitous restriction to AbstractBuild.) Change By: Jesse Glick (29/Jan/15 6:22 PM) Labels: copyartifact workflow -plugin Assignee: JesseGlick TomFENNELLY Component/s: workflow-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] [copyartifact-plugin] (JENKINS-26694) Workflow build Parameters are not exposed to CopyArtifact
James VL created JENKINS-26694 Workflow build Parameters are not exposed to CopyArtifact Issue Type: Bug Assignee: Jesse Glick Components: copyartifact-plugin, workflow-plugin Created: 29/Jan/15 5:54 PM Description: If I use the CopyArtifact plugin with a workflow step(), it correctly pulls the latest successful build's artifacts when pointed to a project of type Workflow. However, if I specify parameters for that same project, it will always throw an AbortException saying no build with those parameters could be found, regardless of what I entered in. If I change the CopyArtifact to point to a freestyle project, the parameters correctly work as intended, pulling in most recent build that had those parameters. Since the CopyArtifact is behaving as it should, I'm assuming there's a flaw in how the Workflow plugin is exposing its build Parameters. Sample code: step ([$class: 'CopyArtifact', projectName: 'Test Run Composer', target: 'composer_run', parameters: "PRODUCT=test,BRANCH_NAME=$branch_name" ]); Environment: Jenkins 1.598 on Linux Workflow:Aggregator plugin 1.2 CopyArtifact plugin: 1.34 Project: Jenkins Labels: workflow-plugin copyartifact Priority: Minor Reporter: James VL This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Bryce Schober commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x I now have this problem on the 1.580.3 LTS package on Ubuntu 10.04: Preparing to replace jenkins 1.580.2 (using .../jenkins_1.580.3_all.deb) ... * Stopping Jenkins Continuous Integration Server jenkins[ OK ] Unpacking replacement jenkins ... dpkg-deb: file `/var/cache/apt/archives/jenkins_1.580.3_all.deb' contains ununderstood data member data.tar.xz , giving up dpkg: error processing /var/cache/apt/archives/jenkins_1.580.3_all.deb (--unpack): subprocess dpkg-deb --fsys-tarfile returned error exit status 2 * Starting Jenkins Continuous Integration Server jenkins[ OK ] Errors were encountered while processing: /var/cache/apt/archives/jenkins_1.580.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I'm guessing that dpkg's default behavior on the build machine switched to packing at least some members as tar.xz, which isn't supported in the dpkg-1.15.5.x on Ubuntu 10.04. At least that seems to be what's suggested by this SO post in which one solution was to additionally specify gzip compression to dpkg. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-9287) Configuration is not saven when two git repositories are added
Eric Beauchamp edited a comment on JENKINS-9287 Configuration is not saven when two git repositories are added Same issue with RepoSCM. Would be great if this issue is resolved...it is very annoying when setting up a new project. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-9287) Configuration is not saven when two git repositories are added
Eric Beauchamp edited a comment on JENKINS-9287 Configuration is not saven when two git repositories are added Same issue with RepoSCM. Would be great if this issue is resolved...it is very annoying when setting up a new project. I have opened a separated bug for it: https://issues.jenkins-ci.org/browse/JENKINS-26645 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-9287) Configuration is not saven when two git repositories are added
Eric Beauchamp edited a comment on JENKINS-9287 Configuration is not saven when two git repositories are added Same issue with RepoSCM. Would be great if this issue is resolved...it is very annoying when setting up a new project. I have opened a separated bug for it: https://issues.jenkins-ci.org/browse/JENKINS-26645 Seems that Kevin Bell has been inactive for a while...can someone else look a this issue? 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] [multiple-scms-plugin] (JENKINS-9287) Configuration is not saven when two git repositories are added
Eric Beauchamp commented on JENKINS-9287 Configuration is not saven when two git repositories are added Same issue with RepoSCM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Torsten Krah commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. Same here with Subversion 2.5, Working Copy 1.7 and Jenkins 1.598. svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. Going back to 2.4.5 and it worked again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-calendar-plugin] (JENKINS-26691) Google Calendar Plugin cannot connect to Google account
Yannis Mark created JENKINS-26691 Google Calendar Plugin cannot connect to Google account Issue Type: Bug Assignee: al_xipe Components: google-calendar-plugin Created: 29/Jan/15 2:01 PM Description: The plugin cannot publish events in a Google calendar because it cannot connect with Google. The logs contain the following: com.google.gdata.util.ServiceForbiddenException: Forbidden HTML HEAD TITLEForbidden/TITLE /HEAD BODY BGCOLOR="#FF" TEXT="#00" H1Forbidden/H1 H2Error 403/H2 Environment: Jenkins Ver 1.591 Google Calendar Plugin Ver 0.4 Project: Jenkins Priority: Major Reporter: Yannis Mark This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-calendar-plugin] (JENKINS-26691) Google Calendar Plugin cannot connect to Google account
Yannis Mark commented on JENKINS-26691 Google Calendar Plugin cannot connect to Google account I found out this https://developers.google.com/google-apps/calendar/v2/developers_guide_protocol which denotes that Google Calendar API is deprecated and is no longer 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] [ssh-plugin] (JENKINS-17440) SSH Plugin throws auth cancel
Paul P commented on JENKINS-17440 SSH Plugin throws auth cancel Hi Team, Could you please update us on this issue.seems like its an known/common 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth edited a comment on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Build #3957 Log extract... 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-10_17-23-06 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\273 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\GEMTEST_Page_84\builds\2014-12-23_14-42-31 java.io.IOException: C:\Jenkins\jobs\GEMTEST_Page_84\builds\1420 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-26_13-03-35 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\288 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Jenkins is running on a Virtual Machine with - Windows Server 2008 R2 Standard with Service Pack 1 Java version is - Java Standard Edition Version 8 Update 31 NOTE: Tried experiment... if I manually delete the shortcut directories in a job directory then migration is okay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed
[JIRA] [subversion-plugin] (JENKINS-26640) svn: E175002: handshake alert: unrecognized_name
Alex Simpson resolved JENKINS-26640 as Fixed svn: E175002: handshake alert: unrecognized_name We have now resolved this. Anyone wishing to know, this is what we did to resolve it: 1) Uninstall any Java version higher than 7. 2) Downloaded and installed JDK or JRE version 6u10. 3) Opened Jenkins.XML with Notepad ++. 4) Changed the following parameter from executable%BASE%\jre\bin\java/executable to executableC:\Program Files\Java\jre6\bin\java/executable If you navigate to %BASE%\jre\bin\java and see what the file version is (java.exe) you will notice its version 7, which is what has caused this issue for us. So it looks like Java JRE 7 is bundled with the Jenkins(Windows) installation, and by changing the above parameter you're basically telling Jenkins to use the version you just installed, which works. Might come in handy if anyone else experiences this issue. Kind regards, Alex Change By: Alex Simpson (29/Jan/15 3:53 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-26675) JVM-versions for autoinstall is not being updated
Daniel Beck commented on JENKINS-26675 JVM-versions for autoinstall is not being updated Jenkins uses these to compile only, not to run Java applications. Or are the security fixes preventing attacks against javac? That the tool installer directories are ancient duplicates INFRA-225. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26606) Unable send email
Tom FENNELLY commented on JENKINS-26606 Unable send email Guys, could you please try this fix and let me know if it work: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/mailer/1.14-SNAPSHOT/mailer-1.14-20150129.154638-1.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26689) javax.mail.internet.AddressException when more than one recipient should receive job status email
Alex Earl updated JENKINS-26689 javax.mail.internet.AddressException when more than one recipient should receive job status email The stack trace is not from email-ext, it's from the Mailer plugin. You aren't using email-ext in your project. Change By: Alex Earl (29/Jan/15 4:08 PM) Assignee: AlexEarl Component/s: mailer-plugin Component/s: email-ext-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] [mailer-plugin] (JENKINS-26689) javax.mail.internet.AddressException when more than one recipient should receive job status email
Daniel Beck resolved JENKINS-26689 as Duplicate javax.mail.internet.AddressException when more than one recipient should receive job status email Duplicates JENKINS-26606. Change By: Daniel Beck (29/Jan/15 4:11 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] [workflow-plugin] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Daniel Beck commented on JENKINS-26659 file permissions arent protected after archive/unarchive Assuming workflow archives on the master (like regular Archive Artifacts) I wouldn't rely on this anyway might be a Windows machine which would lose that information anyway. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Could not reproduce by starting Jenkins 1.596 on Windows 2012 as Administrator under JDK 7u21, creating a project, running a few builds, then stopping and starting a trunk build: builds got correctly migrated. So perhaps only arises under specific circumstances. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Also I checked in jrunscript under these circumstances that the code called by Util.resolveSymlink would work, as would the call to Util.deleteFile. In the case of tdtappe, running Java 6, resolveSymlink would be expected to fail, explaining the skipping deletion of directory … message. This I could fix by just trying deleteFile anyway—if it is really a symlink to a directory, that will work, but if it is really a directory, it should fail because the directory is not empty. It makes me a little nervous because isDirectory would also be true for a real directory created by 1.597+ (or a partly successful earlier migration), and relying on File.delete to fail in this case seems dangerous. In the case of Steve Haworth, running Java 8, I am puzzled. I see no FINE-level messages here so I assume you did not turn on the custom logger, which might have some crucial information. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows loading jobs..
SCM/JIRA link daemon commented on JENKINS-23620 The periodic refresh shows loading jobs.. Code changed in jenkins User: Pelle Pelster Path: src/main/webapp/walldisplay.css src/main/webapp/walldisplay.html src/main/webapp/walldisplay.js http://jenkins-ci.org/commit/walldisplay-plugin/a2874733c0771ee8a661a71d5671b3a9288ca562 Log: Merge pull request #38 from pvelder/master JENKINS-23620 Screen repaint without disturbing glitches Compare: https://github.com/jenkinsci/walldisplay-plugin/compare/569cdfe069ab...a2874733c077 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick edited a comment on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Also I checked in jrunscript under these circumstances that the code called by Util.resolveSymlink would work, as would the call to Util.deleteFile. In the case of tdtappe, running Java 6, resolveSymlink would be expected to fail, explaining the skipping deletion of directory … message, followed by the failure of the migrator. (Which as I mentioned before would not be expected to matter for most people because symlinks should not have been created to begin with; need to confirm this.) This I could fix by just trying deleteFile anyway—if it is really a symlink to a directory, that will work, but if it is really a directory, it should fail because the directory is not empty. It makes me a little nervous because isDirectory would also be true for a real directory created by 1.597+ (or a partly successful earlier migration), and relying on File.delete to fail in this case seems dangerous. In the case of Steve Haworth, running Java 8, I am puzzled. I see no FINE-level messages here so I assume you did not turn on the custom logger, which might have some crucial information. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows loading jobs..
SCM/JIRA link daemon commented on JENKINS-23620 The periodic refresh shows loading jobs.. Code changed in jenkins User: dvelderp Path: src/main/webapp/walldisplay.css src/main/webapp/walldisplay.html src/main/webapp/walldisplay.js http://jenkins-ci.org/commit/walldisplay-plugin/915214c9d5109c82d3782f627ba81c021c07e1c4 Log: JENKINS-23620 Screen repaint without disturbing glitches This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Ah, I was wrong, 1.596- on Windows Java 6 did attempt to create symlinks, using JNA, and this does produce the described error. So that is something I can and will 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-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Confusingly, for Windows on Java 6, 1, 2, etc. were created as true symlinks; the text files with build numbers were only used for permalinks like lastStableBuild, meaning my attempted fix in 056b446 was pointless and can probably just be reverted. (One of the unusual cases where “reopening” a bug is really correct.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-24852) Jenkins-HipChat plugin does not send message to internal hosted HipChat server
Bill Warner commented on JENKINS-24852 Jenkins-HipChat plugin does not send message to internal hosted HipChat server Having the same issue. Get this in the logs: Error posting to HipChat java.net.UnknownHostException: https at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618) at sun.security.ssl.SSLSocketImpl.init(SSLSocketImpl.java:407) at sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:88) at hudson.util.NoClientBindSSLProtocolSocketFactory.createSocket(NoClientBindSSLProtocolSocketFactory.java:135) at hudson.util.NoClientBindSSLProtocolSocketFactory.createSocket(NoClientBindSSLProtocolSocketFactory.java:117) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) at jenkins.plugins.hipchat.StandardHipChatService.publish(StandardHipChatService.java:50) at jenkins.plugins.hipchat.ActiveNotifier.completed(ActiveNotifier.java:71) at jenkins.plugins.hipchat.HipChatListener.onCompleted(HipChatListener.java:26) at jenkins.plugins.hipchat.HipChatListener.onCompleted(HipChatListener.java:14) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.model.Run.execute(Run.java:1810) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26517) Unable to download docker-java 0.10.5-SNAPSHOT
Wei Z commented on JENKINS-26517 Unable to download docker-java 0.10.5-SNAPSHOT I am wondering when this can be fixed. I am trying to use this plugin, but there is always a failure when it tries to launch a docker slave. However, I am not able to investigate further where it went wrong because I can't do a "mvn hpi:run" of this plugin due to this docker-java dependency problem, which means I can't debug what/where is wrong. I think this will be a blocking issue for many users who want to use this plugin, and it also prevents open source community to contribute to this plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/model/RunIdMigrator.java core/src/test/java/jenkins/model/RunIdMigratorTest.java http://jenkins-ci.org/commit/jenkins/388c4b5e6ba52037cae117c5c69f9f4156d41401 Log: FIXED JENKINS-26519 Build record migration failed on Windows using Java 6. In this environment, Util.createSymlink and .isSymlink are implemented, but resolveSymlink is 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] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon resolved JENKINS-26519 as Fixed Build records not migrated due to “failed to rename” on Windows Change By: SCM/JIRA link daemon (29/Jan/15 8:41 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] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
dogfood commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Integrated in jenkins_main_trunk #3958 FIXED JENKINS-26519 Build record migration failed on Windows using Java 6. (Revision 388c4b5e6ba52037cae117c5c69f9f4156d41401) Result = SUCCESS jesse glick : 388c4b5e6ba52037cae117c5c69f9f4156d41401 Files : changelog.html core/src/test/java/jenkins/model/RunIdMigratorTest.java core/src/main/java/jenkins/model/RunIdMigrator.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-12205) Test result trend not displayed in matrix project configuration top page
lam le commented on JENKINS-12205 Test result trend not displayed in matrix project configuration top page Any update? Mine is showing no data. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows tdtappe I think your problem is now fixed in this build, toward 1.600. If you confirm I will try to backport it to the 1.599 release candidate branch so it gets out earlier. Steve Haworth My latest fix might help in your case, but since you say you are running Java 8, you should not have been hitting it to begin with. Your symptoms are similar; the root cause may or may not be related. I would suggest trying once again with my newest build, assuming you still have the original build directories to reproduce against. First be sure to enable fine logging on this 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.
