[JIRA] [multijob-plugin] (JENKINS-25452) Change implementation of "Build Only If SCMChanges" to be check just if it's configure
SCM/JIRA link daemon commented on JENKINS-25452 Change implementation of "Build Only If SCMChanges" to be check just if it's configure Code changed in jenkins User: itaior Path: src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuilder.java http://jenkins-ci.org/commit/tikal-multijob-plugin/8dfb1639caa08563b59b377cb6807cf24ae81117 Log: Merge pull request #57 from itaior/master Fixed issue JENKINS-25452 Compare: https://github.com/jenkinsci/tikal-multijob-plugin/compare/b7ae48bef990...8dfb1639caa0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-25452) Change implementation of "Build Only If SCMChanges" to be check just if it's configure
SCM/JIRA link daemon commented on JENKINS-25452 Change implementation of "Build Only If SCMChanges" to be check just if it's configure Code changed in jenkins User: itaior Path: src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuilder.java http://jenkins-ci.org/commit/tikal-multijob-plugin/85b6a61558458af2daaa3aaa11ec482f139bca76 Log: Fixed issue JENKINS-25452 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-failure-analyzer-plugin] (JENKINS-24171) BFA is blindly adding text to gzipped log
Jan Feindt commented on JENKINS-24171 BFA is blindly adding text to gzipped log Possibly I ran into the same problem: using "Compress Build Log Plugin" everything is fine until I choose to rescan the Builds with BFA. So I think one solution is to "not change the old build log" in this use case using a NullOutputStream instead of a FileOutputStream with the old build log. In com.sonyericsson.jenkins.plugins.bfa.sod.ScanOnDemandTask.scanBuild(AbstractBuild) change line fos = new FileOutputStream(abstractBuild.getLogFile(), true); to fos = new NullOutputStream(); Another solution is to check if file is gzipped and then use NullOutputStream or decompress first, change logfile, compress after BFA is done. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-25464) Unable to Run HP LoadRunner from Jenkins in a Master/Slave Configuration
Randy Stevenson created JENKINS-25464 Unable to Run HP LoadRunner from Jenkins in a Master/Slave Configuration Issue Type: Task Assignee: Unassigned Attachments: Jenkins Console Output - Test Failure, Jenkins Environment Variables.pdf, Jenkins Project Configuration.pdf Components: hp-application-automation-tools-plugin Created: 06/Nov/14 6:51 AM Description: Trying to set up running HP LoadRunner Controller Scenario to run in a Jenkins Master/Slave configuration for Continuous Integration (CI) proof of concept work. The Controller Scenario runs correctly in a Local Jenkins/LoadRunner installation (i.e. both Jenkins and HP LoadRunner installed on the same machine). When trying to do a "Build Now" from Jenkins in the Master/Slave setup, the test ends with one word: Error. If there is additional logged information besides the word "Error", I have not yet found it. Environment: Jenkins Master v1.580.1 Jenkins slave running on Windows 7 Enterprise SP1 machine, Xeon Processor W3520@2.67Ghz, 16Gb RAM, 64-bit O/S. HP-Application-Automation-Tools-Plugin HP LoadRunner 12.01 installed on Slave machine. Jenkins Slave Service set to run with Administrator rights. Project: Jenkins Labels: LoadRunner, CI Master/Slave Priority: Major Reporter: Randy Stevenson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 For all those people eagerly awaiting an outcome on this task, I can report that a commit was pushed to the main github repo about 24 hours ago which removes the customised svnkit and replaces it with the standard library. This was the main stumbling block that prevented svnkit from being upgraded (and in fact was the reason why it was such a huge task to move forward every time svnkit was upgraded). Now I think it is just about testing and then upgrading svnkit to 1.8 and more testing, so hopefully this will happen soon. Steve Christou, you have the thanks of everyone here! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14223) accessing Jenkins through https produces browser warning about mixed https/http content
Kohsuke Kawaguchi resolved JENKINS-14223 as Incomplete accessing Jenkins through https produces browser warning about mixed https/http content Marking as incomplete as Daniel Beck recommended. Change By: Kohsuke Kawaguchi (06/Nov/14 6:00 AM) Status: Reopened Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-1833) Have to be able to provide user and pass for proxy in update center
Kohsuke Kawaguchi resolved JENKINS-1833 as Fixed Have to be able to provide user and pass for proxy in update center This is an old ticket, and UC currently has the proxy configuration. I'm assuming this is working now, and closing this ticket. Change By: Kohsuke Kawaguchi (06/Nov/14 5:55 AM) Status: Reopened Resolved Assignee: Kohsuke Kawaguchi 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] [parameterized-remote-trigger-plugin] (JENKINS-24872) Job fails when using a blocking parameterized remote trigger with a job name containing a token
SCM/JIRA link daemon commented on JENKINS-24872 Job fails when using a blocking parameterized remote trigger with a job name containing a token Code changed in jenkins User: Maurice Williams Path: src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/RemoteBuildConfiguration.java http://jenkins-ci.org/commit/parameterized-remote-trigger-plugin/5988ef15d0ea284fceabdf3153d2fbccfe84c94b Log: Merge pull request #6 from wgreven-ibr/JENKINS-24872 Make sure that tokens are replaced in the job name that is used to construct the job url. Compare: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/compare/a8c7aa6a4821...5988ef15d0ea This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-24872) Job fails when using a blocking parameterized remote trigger with a job name containing a token
SCM/JIRA link daemon commented on JENKINS-24872 Job fails when using a blocking parameterized remote trigger with a job name containing a token Code changed in jenkins User: Wilco Greven Path: src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/RemoteBuildConfiguration.java http://jenkins-ci.org/commit/parameterized-remote-trigger-plugin/0ddb3bf91202bf1f76877f0eb8d0fbde2364822b Log: JENKINS-24872 Make sure that tokens are replaced in the job name that is used to construct the job url. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit-plugin] (JENKINS-25295) Do not fail when no Nunit test reports found
Bruno P. Kinoshita commented on JENKINS-25295 Do not fail when no Nunit test reports found Done, but I couldn't extensively test it. Thus, I'll wait till someone else can `mvn clean hpi:run` and test it, or `mvn clean package` and manually install the plug-in in some test instance and give some positive feedback. Then we can cut a new release with this fix. Thanks! Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit-plugin] (JENKINS-25295) Do not fail when no Nunit test reports found
SCM/JIRA link daemon resolved JENKINS-25295 as Fixed Do not fail when no Nunit test reports found Change By: SCM/JIRA link daemon (06/Nov/14 2:37 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit-plugin] (JENKINS-25295) Do not fail when no Nunit test reports found
SCM/JIRA link daemon commented on JENKINS-25295 Do not fail when no Nunit test reports found Code changed in jenkins User: Bruno P. Kinoshita Path: .gitignore src/main/java/hudson/plugins/nunit/NUnitArchiver.java src/main/java/hudson/plugins/nunit/NUnitPublisher.java src/main/resources/hudson/plugins/nunit/NUnitPublisher/config.jelly src/test/java/hudson/plugins/nunit/NUnitArchiverTest.java src/test/java/hudson/plugins/nunit/NUnitPublisherTest.java http://jenkins-ci.org/commit/nunit-plugin/e6e5f01c60476b6949b823e14522d4a0c15ea780 Log: [FIXED JENKINS-25295] Do not fail when no Nunit test reports found This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [radiatorview-plugin] (JENKINS-25463) 404 When Clicking on a Job
Kayhan Sefat
created JENKINS-25463
404 When Clicking on a Job
Issue Type:
Bug
Assignee:
howama
Components:
radiatorview-plugin, radiatorviewplugin
Created:
06/Nov/14 12:56 AM
Description:
When the radiator view is open, (for example):
http://{host}/view/radiator-master/
and you click on a job, instead of taking you to:
http://{host}/view/radiator-master/job/Checkout-M1_CI/lastBuild
it duplicates part of the URL:
http://{host}/view/radiator-master/view/radiator-master/job/Checkout-M1_CI/lastBuild
...and you get a 404
Environment:
Plugin 1.20, Jenkins 1.588
Project:
Jenkins
Labels:
radiator
Priority:
Major
Reporter:
Kayhan Sefat
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [radiatorview-plugin] (JENKINS-25463) 404 When Clicking on a Job
Kayhan Sefat
updated JENKINS-25463
404 When Clicking on a Job
Change By:
Kayhan Sefat
(06/Nov/14 12:57 AM)
Description:
When the radiator view is open, (for example):http://{host}/view/radiator-master/and you click on a job, instead of taking you to:http://{host}/view/radiator-master/job/
Checkout-M1_CI
MY_JOB
/lastBuildit duplicates part of the URL:http://{host}/view/radiator-master/view/radiator-master/job/
Checkout-M1_CI
MY_JOB
/lastBuild...and you get a 404
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-25458) Version 1.14 forces a git checkout? unknown reasons
Leeam Dagan updated JENKINS-25458 Version 1.14 forces a git checkout? unknown reasons Change By: Leeam Dagan (06/Nov/14 12:05 AM) Description: I have my multi job setup to not need any source code management (none radio button)It would always start off and then begin the first multi job phaseafter upgrading to 1.14 it now forces a git checkout? no idea where its getting the proper info from to even try a git fetch but it is (my job steps were the only ones doing checkouts before). Downgrading to 1.13 (on test jenkins) restored desired behavior as well as downgrading to 1.10 on live. However now I cant seem to download 1.13 for my live implementationLooking forward to a fix :) The view console is all messed up in 1.10 Edit: found 1.13 archive and installed that for now This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clone-workspace-scm-plugin] (JENKINS-25462) Failed to extract workspace.tar.gz when cloning workspace
Alice Goldfuss created JENKINS-25462 Failed to extract workspace.tar.gz when cloning workspace Issue Type: Bug Assignee: Unassigned Components: clone-workspace-scm-plugin, core Created: 05/Nov/14 11:58 PM Description: We are seeing intermittent errors on jobs using the Clone Workspace SCM Plugin. Job A kicks off dependent/downstream builds Job B, C, and D, and many times one of the dependent builds will fail with the following stack trace: Started by upstream project "synthetics-01-build_test_findbugs" build number 853 originally caused by: Started by remote host GitHub via SQS with note: SQS poll initiated on Nov 5, 2014 12:23:01 PM [EnvInject] - Loading node environment variables. Building remotely on synthetics-test-01 (synthetics-build) in workspace /home/jenkins/workspace/synthetics-02-docker-build-scheduler Restoring workspace from build #853 of project synthetics-01-build_test_findbugs java.io.IOException: remote file operation failed: /home/jenkins/workspace/synthetics-02-docker-build-scheduler at hudson.remoting.Channel@17aba278:synthetics-test-01: java.io.IOException: Failed to extract workspace.tar.gz at hudson.FilePath.act(FilePath.java:976) at hudson.FilePath.act(FilePath.java:958) at hudson.FilePath.untar(FilePath.java:518) at hudson.plugins.cloneworkspace.CloneWorkspacePublisher$WorkspaceSnapshotTar.restoreTo(CloneWorkspacePublisher.java:243) at hudson.plugins.cloneworkspace.CloneWorkspaceSCM$Snapshot.restoreTo(CloneWorkspaceSCM.java:396) at hudson.plugins.cloneworkspace.CloneWorkspaceSCM.checkout(CloneWorkspaceSCM.java:152) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.io.IOException: Failed to extract workspace.tar.gz at hudson.FilePath.readFromTar(FilePath.java:2198) at hudson.FilePath.access$400(FilePath.java:190) at hudson.FilePath$4.invoke(FilePath.java:520) at hudson.FilePath$4.invoke(FilePath.java:518) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2577) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to synthetics-test-01(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.FilePath.act(FilePath.java:969) ... 13 more Caused by: java.io.IOException: incorrect header check at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:112) at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257) at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223) at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228) at hudson.FilePath.readFromTar(FilePath.java:2175) at hudson.FilePath.access$400(FilePath.java:190) at hudson.FilePath$4.invoke(FilePath.java:520) at hudson.FilePath$4.invoke(FilePath.java:518) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2577) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.Inte
[JIRA] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Matt Philmon created JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins Issue Type: Bug Assignee: Gregory Boissinot Components: artifactdeployer-plugin Created: 05/Nov/14 11:49 PM Description: When the ArtifactDeployer kicks off after the build we're getting this: ERROR: Publisher org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher aborted due to exception java.lang.AbstractMethodError Environment: Windows Server 2008 R2 running as a service. The bug was noticed under 1.588, but the previous version that worked was 1.585 (we skipped the releases between these). Latest version of Java (JRE) 7. Project: Jenkins Labels: plugin jenkins exception Priority: Blocker Reporter: Matt Philmon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
Jacob Keller commented on JENKINS-12523 Could not initialize class org.libvirt.Connect I also have this problem. Is the only current work-around to downgrade 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] [dashboard-view-plugin] (JENKINS-25220) Dashboard "Status of build" images missing after upgrade to 1.584
Michael Merrell commented on JENKINS-25220 Dashboard "Status of build" images missing after upgrade to 1.584 Closed that pull request and opened another with a smaller change. https://github.com/jenkinsci/jenkins/pull/1455 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25460) Clicking on the console icon to open the console dialog a screen with a "Server not found" error is displayed
Simon
updated JENKINS-25460
Clicking on the console icon to open the console dialog a screen with a "Server not found" error is displayed
Change By:
Simon
(05/Nov/14 11:08 PM)
Environment:
Jenkins version 1.580.1Standalone (i.e. not run in container)jdk1.7.0_07build pipeline
view
plugin version 1.4.4 server is redhatclient is windows firefox
Description:
This issue started happening after upgrading from version 1.4.3 to 1.4.4 of the build-pipeline-view plugin
In the pipeline view, when I click on the console icon on one of the builds the dialog displays a "Server not found" error.In pictures: clicking on the console button:!
attached
build
-
image
pipeline-view
.
gif
png
!gives:!
attached
build
-
image
pipeline-view-console-dialog
.
gif
png
!I debugged the issue and discovered the cause was a '/' added to the href. This is done in line 105 of build-pipeline.js:{code} fillDialog : function(href, title) { jQuery.fancybox({ type: 'iframe', title: title, titlePosition: 'outside', href: '/' + href, transitionIn : 'elastic', transitionOut : 'elastic', width: '90%', height: '80%' }); },{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25460) Clicking on the console icon to open the console dialog a screen with a "Server not found" error is displayed
Simon
created JENKINS-25460
Clicking on the console icon to open the console dialog a screen with a "Server not found" error is displayed
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
build-pipeline-view-console-dialog.png, build-pipeline-view.png
Components:
build-pipeline-plugin
Created:
05/Nov/14 11:05 PM
Description:
In the pipeline view, when I click on the console icon on one of the builds the dialog displays a "Server not found" error.
In pictures: clicking on the console button:
Unable to render embedded object: File (attached-image.gif) not found.
gives:
Unable to render embedded object: File (attached-image.gif) not found.
I debugged the issue and discovered the cause was a '/' added to the href. This is done in line 105 of build-pipeline.js:
fillDialog : function(href, title) {
jQuery.fancybox({
type: 'iframe',
title: title,
titlePosition: 'outside',
href: '/' + href,
transitionIn : 'elastic',
transitionOut : 'elastic',
width: '90%',
height: '80%'
});
},
Environment:
Jenkins version 1.580.1
Standalone (i.e. not run in container)
jdk1.7.0_07
build pipeline plugin version 1.4.4
server is redhat
client is windows firefox
Project:
Jenkins
Priority:
Major
Reporter:
Simon
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build
Ulli Hafner commented on JENKINS-13458 Add switch to set reference build always as the latest build Well, this feature seems not very useful in my projects (you just need to press build again to get rid of the unstable status). (However I'm willing to integrate a pull request that adds that feature, so if you are interested please go ahead. It should not be that complicated.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build
Ivan Andrus commented on JENKINS-13458 Add switch to set reference build always as the latest build Any thoughts on this? I would really like 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] [parameterized-remote-trigger-plugin] (JENKINS-22231) Allow parameterized remote trigger to be a post-build action
Rick Liu commented on JENKINS-22231 Allow parameterized remote trigger to be a post-build action any progress on 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] [build-pipeline-plugin] (JENKINS-25427) Build Pipleline Plugin no longer allows starting build with parameters
Jeremy Orem commented on JENKINS-25427 Build Pipleline Plugin no longer allows starting build with parameters I'm also experiencing this issue. Downgrading back to 1.4.3 fixes the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipleline Plugin no longer allows starting build with parameters
Jeremy Orem edited a comment on JENKINS-25427 Build Pipleline Plugin no longer allows starting build with parameters I'm also experiencing this. Downgrading back to 1.4.3 fixes the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-25459) Authorization by "Github Commiter" strategy broken.
adrian kalaveshi
created JENKINS-25459
Authorization by "Github Commiter" strategy broken.
Issue Type:
Bug
Assignee:
Sam Kottler
Components:
github-oauth-plugin
Created:
05/Nov/14 9:44 PM
Description:
Suddenly, when using the "Github Commiter" authorization strategy, we're getting an exception. >From the log:
WARNING: Caught exception evaluating: it.items in /. Reason: java.lang.reflect.InvocationTargetException
...
Caused by: java.util.concurrent.ExecutionException: java.io.FileNotFoundException: https://api.github.com/repos/[redacted]/collaborators
...
The API endpoint returns:
{
"message": "Not Found",
"documentation_url": "https://developer.github.com/v3"
}
Environment:
github-oauth-plugin version 1.59
Project:
Jenkins
Priority:
Major
Reporter:
adrian kalaveshi
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-25364) Unable to update workspace error
Naveen Gogineni commented on JENKINS-25364 Unable to update workspace error Paul I am confused about your mentioning a "proxy". What is that in this context ? The builds were working fine with force sync but suddenly now it stopped working again with following error ERROR: Unable to update workspace: com.perforce.p4java.exception.ConnectionException: java.net.SocketException: Connection reset Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-25458) Version 1.14 forces a git checkout? unknown reasons
Leeam Dagan created JENKINS-25458 Version 1.14 forces a git checkout? unknown reasons Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 05/Nov/14 8:34 PM Description: I have my multi job setup to not need any source code management (none radio button) It would always start off and then begin the first multi job phase after upgrading to 1.14 it now forces a git checkout? no idea where its getting the proper info from to even try a git fetch but it is (my job steps were the only ones doing checkouts before). Downgrading to 1.13 (on test jenkins) restored desired behavior as well as downgrading to 1.10 on live. However now I cant seem to download 1.13 for my live implementation Looking forward to a fix The view console is all messed up in 1.10 Project: Jenkins Priority: Blocker Reporter: Leeam Dagan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather
Scott Busche commented on JENKINS-24006 Customize number of Junit test failures that affect weather I've created a PR that fixes the issue Mark is seeing - https://github.com/jenkinsci/junit-plugin/pull/4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25379) Manual trigger execution causes TriggerException using a 32bits jdk
Maximiliano Leonardo García Santanna updated JENKINS-25379 Manual trigger execution causes TriggerException using a 32bits jdk Change By: Maximiliano Leonardo García Santanna (05/Nov/14 7:54 PM) Description: Running Jenkins on windows with a 32bits jdk, clicking the icon in the Delivery Pipeline Plugin to run a manual step in a pipeline yields a "Cannot trigger build!" error. Running the manual step in Build Pipeline Plugin is successful. Steps to reproduce:Run jenkins on windows with a 32bits jdkCreate a pipeline with a manual stepRun the pipe up to the manual stepClick the icon to the the right of the manual step This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25362) Cannot start parametrized freestyle job from workflow plugin
Marcin Gawenda closed JENKINS-25362 as Cannot Reproduce Cannot start parametrized freestyle job from workflow plugin Confirming, works fine with job as the parameter name for the job name. Thanks! Change By: Marcin Gawenda (05/Nov/14 7:26 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25362) Cannot start parametrized freestyle job from workflow plugin
Jesse Glick commented on JENKINS-25362 Cannot start parametrized freestyle job from workflow plugin Sorry, my mistake: job is the parameter name for the job name. https://trello.com/c/kXyfSioF/133-code-snippet-generation-for-buildtriggerstep-parameters would make this more apparent from the UI. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-25456) POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml'
Jake Carlson commented on JENKINS-25456 POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml' I'm seeing this in the Jenkins system logs after the failed API call to edit a job's configuration. Nov 05, 2014 12:19:39 PM WARNING hudson.plugins.jobConfigHistory.FileHistoryDao hasDuplicateHistory unable to check for duplicate previous history file: /data/jenkins/config-history/jobs/jobs/2014-11-05_12-12-22/config.xml java.io.FileNotFoundException: /data/jenkins/jobs/jobs/config.xml (No such file or directory) Nov 05, 2014 12:19:39 PM WARNING hudson.model.listeners.SaveableListener fireOnChange null java.lang.RuntimeException: Unable to copy /data/jenkins/jobs/jobs/config.xml at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntryAndCopyConfig(FileHistoryDao.java:252) at hudson.plugins.jobConfigHistory.FileHistoryDao.saveItem(FileHistoryDao.java:264) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:29) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:80) at hudson.model.AbstractItem.updateByXml(AbstractItem.java:669) at hudson.model.AbstractItem.doConfigDotXml(AbstractItem.java:613) at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.success(BasicHeaderProcessor.java:95) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:75) at hudson.security.ChainedServletFi
[JIRA] [delivery-pipeline-plugin] (JENKINS-25457) Server error when viewing pipeline with NOT_BUILT result job.
Taiki Sugawara
updated JENKINS-25457
Server error when viewing pipeline with NOT_BUILT result job.
Change By:
Taiki Sugawara
(05/Nov/14 6:12 PM)
Description:
Server error was occurred when I've view pipeline that is configured with NOT_BUILT result job.Summary of stacktrace log
if
is
following:{noformat}11 06, 2014 2:07:59 午前 org.eclipse.jetty.util.log.JavaUtilLog warn警告: Error while serving http://debabocho.ariel-networks.com:8080/view/Pipeline/api/jsonjava.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor194.invoke(Unknown Source)...Caused by: java.io.IOException: Failed to write pipelines at org.kohsuke.stapler.export.Property.writeTo(Property.java:122) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeTo(Model.java:164) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doJson(Api.java:205) ... 76 moreCaused by: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.export.MethodProperty.getValue(MethodProperty.java:66) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) ... 80 moreCaused by: java.lang.IllegalStateException: Result NOT_BUILT not recognized. at se.diabol.jenkins.pipeline.domain.status.SimpleStatus.resolveStatus(SimpleStatus.java:144) at se.diabol.jenkins.pipeline.domain.Task.getLatestTask(Task.java:142) at se.diabol.jenkins.pipeline.domain.Stage.createLatestStage(Stage.java:188) at se.diabol.jenkins.pipeline.domain.Pipeline.createPipelineLatest(Pipeline.java:149) at se.diabol.jenkins.pipeline.DeliveryPipelineView.getComponent(DeliveryPipelineView.java:324) at se.diabol.jenkins.pipeline.DeliveryPipelineView.getPipelines(DeliveryPipelineView.java:292) ... 85 more{noformat}And I attached full stacktrace log as [^error.txt].
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25457) Server error when viewing pipeline with NOT_BUILT result job.
Taiki Sugawara created JENKINS-25457 Server error when viewing pipeline with NOT_BUILT result job. Issue Type: Bug Assignee: Patrik Boström Attachments: error.txt Components: delivery-pipeline-plugin Created: 05/Nov/14 6:12 PM Description: Server error was occurred when I've view pipeline that is configured with NOT_BUILT result job. Summary of stacktrace log if following: 11 06, 2014 2:07:59 午前 org.eclipse.jetty.util.log.JavaUtilLog warn 警告: Error while serving http://debabocho.ariel-networks.com:8080/view/Pipeline/api/json java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor194.invoke(Unknown Source) ... Caused by: java.io.IOException: Failed to write pipelines at org.kohsuke.stapler.export.Property.writeTo(Property.java:122) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeTo(Model.java:164) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doJson(Api.java:205) ... 76 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.export.MethodProperty.getValue(MethodProperty.java:66) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) ... 80 more Caused by: java.lang.IllegalStateException: Result NOT_BUILT not recognized. at se.diabol.jenkins.pipeline.domain.status.SimpleStatus.resolveStatus(SimpleStatus.java:144) at se.diabol.jenkins.pipeline.domain.Task.getLatestTask(Task.java:142) at se.diabol.jenkins.pipeline.domain.Stage.createLatestStage(Stage.java:188) at se.diabol.jenkins.pipeline.domain.Pipeline.createPipelineLatest(Pipeline.java:149) at se.diabol.jenkins.pipeline.DeliveryPipelineView.getComponent(DeliveryPipelineView.java:324) at se.diabol.jenkins.pipeline.DeliveryPipelineView.getPipelines(DeliveryPipelineView.java:292) ... 85 more And I attached full stacktrace log as error.txt. Environment: Jenkins: 1.588 delivery-pipeline-plugin: 0.8.6 Project: Jenkins Priority: Minor Reporter: Taiki Sugawara This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25362) Cannot start parametrized freestyle job from workflow plugin
Marcin Gawenda commented on JENKINS-25362 Cannot start parametrized freestyle job from workflow plugin Yes, the job 'Grep ENV' exists, can be executed separately. If you mean the plugin 'CB Folders' - was not installed. I have installed it in version 4.7. Moved both jobs to new folder. Finally got the same issue as described. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job).
Martin Hohl updated JENKINS-25450 Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job). Change By: Martin Hohl (05/Nov/14 6:02 PM) Description: Unexpected behavior of Integrity plugin after message "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist.":The Integrity - CM Polling Log says"Started on Nov 5, 2014 7:00:00 AMPreparing to execute si projectinfo for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pjPreparing to execute si viewproject for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pjA SQL Exception was caught!Table/View 'CM_PROJECT' does not exist.Done. Took 7.8 secNo changes"and the job status of the build job is not FAILED , but "Finished: SUCCESS" .Normally, if the plugin says "Failed to establish an API connection to the Integrity Server!" it fails the build job (as expected).I would not expect that a Jenkins job can have status OK, if the workspace cannot be populated or updated with the SCM configured for that job.The issue occurred the first time after an upgrade of the Integrity plugin (previous version was 1.24, current version is 1.28). Without administrator intervention the "pseudo-good" builds with outdated workspace contents were consistenly occurring since that moment... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds-jenkins] (JENKINS-19935) Instances on EC2 don't get random suffix
John Engelman commented on JENKINS-19935 Instances on EC2 don't get random suffix The problem is here: https://github.com/jenkinsci/jclouds-plugin/blob/master/jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlave.java#L83 That sets the Node name to be the metadata.getName() which is just the template name. I've fixed for myself by using a custom build that changes that line to use: metaData.getName() + "-" + metaData.getProviderId() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-25456) POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml'
Jake Carlson created JENKINS-25456 POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml' Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory-plugin Created: 05/Nov/14 5:33 PM Description: When POSTing to an already existing job's config.xml to edit the job's configuration, I'm getting the following error: java.io.IOException: Failed to persist config.xml at hudson.model.AbstractItem.updateByXml(AbstractItem.java:648) at hudson.model.AbstractItem.doConfigDotXml(AbstractItem.java:613) at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.success(BasicHeaderProcessor.java:95) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:75) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.comp
[JIRA] [deploy-plugin] (JENKINS-24675) Deploy plugin does not store hostname for Glassfish 2 container
Harald Koch commented on JENKINS-24675 Deploy plugin does not store hostname for Glassfish 2 container I just discovered this bug also. Last plugin update was July 2014. Is anyone still maintaining 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-25455) Code input field is too small
Daniel Beck commented on JENKINS-25455 Code input field is too small Clearly a bug. Also, after resize, the gutter (where the line numbers are) is broken until something is typed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25444) CliGit implementation of fetch/deleteBranch does remove open changes, JGit does not
Stephan Pauxberger commented on JENKINS-25444 CliGit implementation of fetch/deleteBranch does remove open changes, JGit does not Just for the sake of completeness: JGit.CheckoutCommand.setForce() is not equivalent to CLI "checkout -f" but "checkout -B", i.e. to force the resetting of a branch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-9665) Variables used as node labes are not expanded in parameterized builds
Daniel Beck resolved JENKINS-9665 as Fixed Variables used as node labes are not expanded in parameterized builds Node Label Parameter Plugin and Parameterized Trigger Plugin resolve this issue. If you can't get them to work together, please file a new issue against these plugins, preferably after having asked for help on the jenkinsci-users mailing list and having read https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Change By: Daniel Beck (05/Nov/14 4:40 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] [scm-sync-configuration-plugin] (JENKINS-25453) Jobs with spaces in name lead to crash in plugin
Daniel Beck resolved JENKINS-25453 as Duplicate Jobs with spaces in name lead to crash in plugin Duplicates JENKINS-24686. Change By: Daniel Beck (05/Nov/14 4:41 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] [git-plugin] (JENKINS-24133) GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Rowan Beentje commented on JENKINS-24133 GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL Also saw this when updating to the Stash jenkins webhook 2.6.0. Supporting calling notifyCommit with the branch and SHA would be incredibly useful - it enables a "Trigger build" button in the Stash UI, for example, which triggers a build of a specific revision for testing. However this currently causes the detached GIT_BRANCH issue above, so we've had to roll the webhook back 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] [jclouds-jenkins] (JENKINS-19935) Instances on EC2 don't get random suffix
John Engelman commented on JENKINS-19935 Instances on EC2 don't get random suffix Trying this with Jclouds-Jenkins-2.9-SNAPSHOT (running with jclouds-1.8) and this still doesn't work. The instance is created with the name of the EC2 template. Subsequent slaves are started and seemed to be configured, but never join into Jenkins as slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25455) Code input field is too small
Dmitrijs Sahlovs created JENKINS-25455 Code input field is too small Issue Type: Bug Assignee: vjuranek Attachments: jenkins-groovy.png Components: core, groovy-plugin Created: 05/Nov/14 4:09 PM Description: Not sure if this is a bug or desired behavior(see screenshot). When I add groovy script as a build step I can't add anything to it, because text field is too small. Of course I can easily make it bigger and write some code there, but in my opinion input field should not be so small by default. Environment: Jenkins 1.586 on Windows Groovy-plugin 1.23 Google Chrome 38.0.2125 /IE 9 Project: Jenkins Priority: Minor Reporter: Dmitrijs Sahlovs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job).
Martin Hohl commented on JENKINS-25450 Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job). Occurs with older versions of Jenkins Integrity plugin too, whenever an SQL Exception occurs due to outdated DB schema (after upgrading). A required condition for the behavior to appear is that the "Clean workspace" option is disabled for the particular build queue (which is not really to be considered as "best practice" for quality assurance of production builds, but might be used by some people for development builds to save some extra time for fetching the complete SCM archive). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25454) Jobs with spaces in name lead to crash in plugin
Frédéric Camblor closed JENKINS-25454 as Duplicate Jobs with spaces in name lead to crash in plugin Dupe Change By: Frédéric Camblor (05/Nov/14 4:02 PM) Status: Open Closed 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] [scm-sync-configuration-plugin] (JENKINS-25454) Jobs with spaces in name lead to crash in plugin
Dirk Eichel created JENKINS-25454 Jobs with spaces in name lead to crash in plugin Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 05/Nov/14 3:47 PM Description: If any job has a name with spaces, nothing is pushed to SCM any more. To remove spaces from names is no solution in current days. Error log of one job named 'Build STAR' (below named 'Build%20STAR'): Nov 03, 2014 12:09:45 PM FINER org.apache.maven.scm.manager.ScmManager checkIn THROW org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(AbstractGitScmProvider.java:291) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.checkin(AbstractGitScmProvider.java:217) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:415) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:397) at org.apache.maven.scm.manager.AbstractScmManager.checkIn(AbstractScmManager.java:423) at hudson.plugins.scm_sync_configuration.SCMManipulator.checkinFiles(SCMManipulator.java:242) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.processCommitsQueue(ScmSyncConfigurationBusiness.java:208) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.access$000(ScmSyncConfigurationBusiness.java:29) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:143) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:141) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.apache.maven.scm.ScmException: Error while executing command. at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:122) at org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.executeCheckInCommand(GitCheckInCommand.java:129) at org.apache.maven.scm.command.checkin.AbstractCheckInCommand.executeCommand(AbstractCheckInCommand.java:54) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) ... 14 more Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error inside systemOut parser at org.codehaus.plexus.util.cli.CommandLineUtils$1.call(CommandLineUtils.java:188) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:107) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:74) at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:118) ... 17 more Caused by: java.lang.IllegalArgumentException: Illegal character in path at index 0: "jobs/Build%20STAR/config.xml" at java.net.URI.create(URI.java:859) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolveURI(GitStatusConsumer.java:251) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolvePath(GitStatusConsumer.java:232) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.consumeLine(GitStatusConsumer.java:138) at org.codehaus.plexus.util.cli.StreamPumper.consumeLine(StreamPumper.java:190) at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:135) Caused by: java.net.URISyntaxException: Illegal character in path at index 0: "jobs/Build%20STAR/config.xml" at java.net.URI$Parser.fail(URI.java:2829) at java.net.URI$Parser.checkChars(URI.java:3002) at java.net.URI$Parser.parseHierarchical(URI.java:3086) at java.net.URI$Parser.parse(URI.java:3044) at java.net.URI.(URI.java:595) at java.net.URI.create(URI.java:857) ... 5 more Nov 03, 2014 12:09:45 PM SEVERE hudson.plug
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25453) Jobs with spaces in name lead to crash in plugin
Dirk Eichel created JENKINS-25453 Jobs with spaces in name lead to crash in plugin Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 05/Nov/14 3:45 PM Description: If any job has a name with spaces, nothing is pushed to SCM any more. To remove spaces from names is no solution in current days. Error log of one job named 'Build STAR' (below named 'Build%20STAR'): Nov 03, 2014 12:09:45 PM FINER org.apache.maven.scm.manager.ScmManager checkIn THROW org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(AbstractGitScmProvider.java:291) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.checkin(AbstractGitScmProvider.java:217) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:415) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:397) at org.apache.maven.scm.manager.AbstractScmManager.checkIn(AbstractScmManager.java:423) at hudson.plugins.scm_sync_configuration.SCMManipulator.checkinFiles(SCMManipulator.java:242) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.processCommitsQueue(ScmSyncConfigurationBusiness.java:208) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.access$000(ScmSyncConfigurationBusiness.java:29) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:143) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:141) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.apache.maven.scm.ScmException: Error while executing command. at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:122) at org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.executeCheckInCommand(GitCheckInCommand.java:129) at org.apache.maven.scm.command.checkin.AbstractCheckInCommand.executeCommand(AbstractCheckInCommand.java:54) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) ... 14 more Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error inside systemOut parser at org.codehaus.plexus.util.cli.CommandLineUtils$1.call(CommandLineUtils.java:188) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:107) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:74) at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:118) ... 17 more Caused by: java.lang.IllegalArgumentException: Illegal character in path at index 0: "jobs/Build%20STAR/config.xml" at java.net.URI.create(URI.java:859) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolveURI(GitStatusConsumer.java:251) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolvePath(GitStatusConsumer.java:232) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.consumeLine(GitStatusConsumer.java:138) at org.codehaus.plexus.util.cli.StreamPumper.consumeLine(StreamPumper.java:190) at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:135) Caused by: java.net.URISyntaxException: Illegal character in path at index 0: "jobs/Build%20STAR/config.xml" at java.net.URI$Parser.fail(URI.java:2829) at java.net.URI$Parser.checkChars(URI.java:3002) at java.net.URI$Parser.parseHierarchical(URI.java:3086) at java.net.URI$Parser.parse(URI.java:3044) at java.net.URI.(URI.java:595) at java.net.URI.create(URI.java:857) ... 5 more Nov 03, 2014 12:09:45 PM SEVERE hudson.plug
[JIRA] [junit-plugin] (JENKINS-12815) Add an option to select Build status when no Test is found
Klaus Azesberger edited a comment on JENKINS-12815 Add an option to select Build status when no Test is found if you run an incremental maven build (as part of a free style project) and try to publish surefire-reports there is a real possibility that there were no modules within the project list to build, that had led to testexecution and thus surefire-reports to publish. so that's a real pain in the a... when you are forced to write dummy reports in order to have a green build after a green build that didnt need to execute tests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-12815) Add an option to select Build status when no Test is found
Klaus Azesberger commented on JENKINS-12815 Add an option to select Build status when no Test is found if you run an incremental maven build and try to publish surefire-reports there is a real possibility that there were no modules within the project list to build, that had led to testexecution and thus surefire-reports to publish. so that's a real pain in the a... when you are forced to write dummy reports in order to have a green build after a green build that didnt need to execute tests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-16126) CLI Basic authentiation does not work
Andrei Neculau edited a comment on JENKINS-16126 CLI Basic authentiation does not work I am getting the same with 1.588 NOTE: I am also having a reverse-proxy (nginx, not apache) in front of the jenkins instance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-16126) CLI Basic authentiation does not work
Andrei Neculau commented on JENKINS-16126 CLI Basic authentiation does not work i am getting the same with 1.588 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-9665) Variables used as node labes are not expanded in parameterized builds
ggi reopened JENKINS-9665 Variables used as node labes are not expanded in parameterized builds Hi, I think that the proposals are workarounds for specific situations, but I think the issue is still not resolved, since can not be used variables in label parameters. In my case I don't found the way to with those workarounds, I have to send the job to a label (not node) depending of the parameters which are called the job. I have solved it with another workaround: using the "Parameterized Trigger Plugin" inside this call, using the option of pass parameters from a properties file and inside this option, use the option "Don't trigger if any files are missing" So depending the the properties files that I create or delete in a previous shell script, I control which jobs runs, and each job has a fixed label. Still all of these are complex workarounds because can not be used variables in label parameters. So if this can be fixed would the good solution. Regards, Gorka Change By: ggi (05/Nov/14 3:25 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit-plugin] (JENKINS-25295) Do not fail when no Nunit test reports found
Bruno P. Kinoshita commented on JENKINS-25295 Do not fail when no Nunit test reports found Hello Dale. Doesn't sound so hard to implement this new feature. IIRC I had to do something similar in TAP Plug-in, since I mimicked Jenkins JUnit reports behaviour there. I'll try to tackle this issue next Sunday, but drop a note here if you have a pull request before that. I can merge it and cut a release right away too. Thanks Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25445) Incorrect workspace selection when checkout to subfolder (case 12252)
Mads Nielsen resolved JENKINS-25445 as Fixed Incorrect workspace selection when checkout to subfolder (case 12252) Change By: Mads Nielsen (05/Nov/14 3:16 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] [multijob-plugin] (JENKINS-25452) Change implementation of "Build Only If SCMChanges" to be check just if it's configure
itai Or created JENKINS-25452 Change implementation of "Build Only If SCMChanges" to be check just if it's configure Issue Type: Bug Assignee: itai Or Components: multijob-plugin Created: 05/Nov/14 3:15 PM Description: hudson.scm.SCM.calcRevisionsFromBuild(Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/model/TaskListener;)Lhudson/scm/SCMRevisionState; java.lang.AbstractMethodError: hudson.scm.SCM.calcRevisionsFromBuild(Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/model/TaskListener;)Lhudson/scm/SCMRevisionState; at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.getScmChange(MultiJobBuilder.java:117) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:181) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) at hudson.model.Run.execute(Run.java:1706) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Project: Jenkins Priority: Major Reporter: itai Or This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25364) Unable to update workspace error
Paul Allen commented on JENKINS-25364 Unable to update workspace error I was just thinking about your proxy, were you able to sync files using P4 or P4V? The behaviour was inline with the proxy running out of disk space or poor network connection (the Proxy logs might have more details). Are you happy if I close the issue? It seems to be more related to the environment than the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job).
Martin Hohl commented on JENKINS-25450 Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job). If during comparing the current workspace (stored locally on the Jenkins site in a SQL database) with the current content of the SCM archive it becomes obvious, that the database scheme of that local database needs DB schema versioning, the SCM plugin should either try to automatically perform DB schema versioning for that job or if that can't be done, it would be a good idea to fall back to "Clean workspace" operation mode and start over with the local database (instead of compiling old workspace content and rating it "OK"). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job).
Martin Hohl updated JENKINS-25450 Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job). Change By: Martin Hohl (05/Nov/14 2:55 PM) Summary: Unexpected behavior of Jenkins Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist inside plugin (no error returned to build job) . " Description: Unexpected behavior of Integrity plugin after message "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist.": The Integrity - CM Polling Log says"Started on Nov 5, 2014 7:00:00 AMPreparing to execute si projectinfo for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pjPreparing to execute si viewproject for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pjA SQL Exception was caught!Table/View 'CM_PROJECT' does not exist.Done. Took 7.8 secNo changes"and the job status of the build job is not FAILED.Normally, if the plugin says "Failed to establish an API connection to the Integrity Server!" it fails the build job (as expected).I would not expect that a Jenkins job can have status OK, if the workspace cannot be populated or updated with the SCM configured for that job.The issue occurred the first time after an upgrade of the Integrity plugin (previous version was 1.24, current version is 1.28). Without administrator intervention the "pseudo-good" builds with outdated workspace contents were consistenly occurring since that moment... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist."
Martin Hohl updated JENKINS-25450 Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist." Change By: Martin Hohl (05/Nov/14 2:53 PM) Environment: Jenkins 1.586 - PTC Integrity CM - Jenkins Plugin 1.28 running on WIndows Windows 7 SP1 - x64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist."
Martin Hohl updated JENKINS-25450 Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist." Change By: Martin Hohl (05/Nov/14 2:52 PM) Environment: Jenkins 1.586 - PTC Integrity CM - Jenkins Plugin 1.28 running on WIndows 7 SP1 - x64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist."
Martin Hohl updated JENKINS-25450 Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist." Change By: Martin Hohl (05/Nov/14 2:52 PM) Description: The Integrity - CM Polling Log says"Started on Nov 5, 2014 7:00:00 AMPreparing to execute si projectinfo for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pjPreparing to execute si viewproject for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pjA SQL Exception was caught!Table/View 'CM_PROJECT' does not exist.Done. Took 7.8 secNo changes"and the job status of the build job is not FAILED.Normally, if the plugin says "Failed to establish an API connection to the Integrity Server!" it fails the build job (as expected).I would not expect that a Jenkins job can have status OK, if the workspace cannot be populated or updated with the SCM configured for that job.The issue occurred the first time after an upgrade of the Integrity plugin (previous version was 1.24, current version is 1.28). Without administrator intervention the "pseudo-good" builds with outdated workspace contents were consistenly occurring since that moment... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25451) "build after other projects"
Andrei Neculau created JENKINS-25451 "build after other projects" Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 05/Nov/14 2:37 PM Description: I have created a job X that "depends" on a job Y in a delivery-pipeline (build) and triggers whenever Y succeeds. At that point, I fetch the PIPELINE_VERSION and use it in the environment. I noticed that job X then starts appearing the in the delivery-pipeline view, which is not correct I think. It is not a subproject, nor a downstream job by my definition. Project: Jenkins Priority: Minor Reporter: Andrei Neculau This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23013) AtomNode should capture CPS call stack
SCM/JIRA link daemon commented on JENKINS-23013 AtomNode should capture CPS call stack Code changed in jenkins User: Jesse Glick Path: api/src/main/java/org/jenkinsci/plugins/workflow/actions/SourceLocationAction.java http://jenkins-ci.org/commit/workflow-plugin/bf48f97641c12aebf8d742e11b289f1f94c4b0d1 Log: JENKINS-23013 Deleting unused SourceLocationAction. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23080) standalone "println" should work like "echo" step
Jesse Glick commented on JENKINS-23080 standalone "println" should work like "echo" step Are you planning on doing this in the 1.0 timeframe? After that, getConsole is locked into the API. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-failure-analyzer-plugin] (JENKINS-25436) Report failures by analyzing jenkins test report
Jan Feindt closed JENKINS-25436 as Duplicate Report failures by analyzing jenkins test report duplicate to 25437 Change By: Jan Feindt (05/Nov/14 2:23 PM) Status: Open Closed 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-25362) Cannot start parametrized freestyle job from workflow plugin
Jesse Glick resolved JENKINS-25362 as Cannot Reproduce Cannot start parametrized freestyle job from workflow plugin Started a job with parameters is a tested use case. value should no longer be used. Use name to specify the job name. Are you sure a job of that exact name exists? Are you using folders? Change By: Jesse Glick (05/Nov/14 2:20 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25362) Cannot start parametrized freestyle job from workflow plugin
Jesse Glick assigned JENKINS-25362 to Jesse Glick Cannot start parametrized freestyle job from workflow plugin Change By: Jesse Glick (05/Nov/14 2:17 PM) Assignee: Kohsuke Kawaguchi Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24673) Build wrappers in Workflow plugin
Jesse Glick assigned JENKINS-24673 to Jesse Glick Build wrappers in Workflow plugin Change By: Jesse Glick (05/Nov/14 2:17 PM) Assignee: Kohsuke Kawaguchi Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24672) GitSCM in Workflow runs git.exe if master is run on Windows and slave is a Linux
Jesse Glick commented on JENKINS-24672 GitSCM in Workflow runs git.exe if master is run on Windows and slave is a Linux Still reproducible using newest plugins? GitSCM does not deal with anything this low-level, so it is unlikely there is any bug there, but it is possible there is a broader bug in how a Launcher is constructed by ExecutorStep. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24672) GitSCM in Workflow runs git.exe if master is run on Windows and slave is a Linux
Jesse Glick assigned JENKINS-24672 to Jesse Glick GitSCM in Workflow runs git.exe if master is run on Windows and slave is a Linux Change By: Jesse Glick (05/Nov/14 2:13 PM) Assignee: Kohsuke Kawaguchi Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25337) Jenkins fails to start
Jesse Glick commented on JENKINS-25337 Jenkins fails to start Ah, right, sorry. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25337) Jenkins fails to start
Daniel Beck commented on JENKINS-25337 Jenkins fails to start The correct wiki link would be this one: https://wiki.jenkins-ci.org/display/JENKINS/IBM+WebSphere This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25337) Jenkins fails to start
Jesse Glick commented on JENKINS-25337 Jenkins fails to start When you figure this out please update: https://wiki.jenkins-ci.org/display/JENKINS/IBM+WebSphere+Configuration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25337) Jenkins fails to start
Jesse Glick updated JENKINS-25337 Jenkins fails to start Change By: Jesse Glick (05/Nov/14 1:51 PM) Labels: cookie security websphere This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist."
Martin Hohl updated JENKINS-25450 Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist." Change By: Martin Hohl (05/Nov/14 1:28 PM) Description: The Integrity - CM Polling Log says"Started on Nov 5, 2014 7:00:00 AMPreparing to execute si projectinfo for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pjPreparing to execute si viewproject for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pjA SQL Exception was caught!Table/View 'CM_PROJECT' does not exist.Done. Took 7.8 secNo changes"and the job status of the build job is not FAILED.Normally, if the plugin says "Failed to establish an API connection to the Integrity Server!" it fails the build job (as expected).I would not expect that a Jenkins job can have status OK, if the workspace cannot be populated or updated with the SCM configured for that job. The issue occurred the first time after an upgrade of the Integrity plugin (previous version was 1.24, current version is 1.28). Without administrator intervention the "pseudo-good" builds were consistenly occurring since that moment... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit-plugin] (JENKINS-25295) Do not fail when no Nunit test reports found
Dale Hards assigned JENKINS-25295 to Bruno P. Kinoshita Do not fail when no Nunit test reports found Reassigning back to Bruno Kinoshita who I notice is the lead on the nunit-plugin Change By: Dale Hards (05/Nov/14 1:26 PM) Assignee: redsolo Bruno P. Kinoshita This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-25449) Add form validation for label expression axis
Oliver Gondža updated JENKINS-25449 Add form validation for label _expression_ axis Change By: Oliver Gondža (05/Nov/14 1:25 PM) Assignee: Kohsuke Kawaguchi 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] [svnmerge-plugin] (JENKINS-24735) Add support for build parameters in Subversion URLs.
SCM/JIRA link daemon commented on JENKINS-24735 Add support for build parameters in Subversion URLs. Code changed in jenkins User: Alex Ouzounis Path: src/main/java/jenkins/plugins/svnmerge/IntegrateAction.java http://jenkins-ci.org/commit/svnmerge-plugin/14eeb009758a87889a0e5c5964d41a7cdfe655b0 Log: JENKINS-24735 - Add support for build parameters in Subversion URLs Update IntegrateAction to expand SVN URLs (fixed typo) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-24735) Add support for build parameters in Subversion URLs.
SCM/JIRA link daemon commented on JENKINS-24735 Add support for build parameters in Subversion URLs. Code changed in jenkins User: Hugues Chabot Path: src/main/java/jenkins/plugins/svnmerge/IntegrateAction.java http://jenkins-ci.org/commit/svnmerge-plugin/d4f365865c7741dea46697d06e8abde0c433a8aa Log: Merge pull request #19 from alexouzounis/JENKINS-24735 JENKINS-24735 - Add support for build parameters in Subversion URLs Compare: https://github.com/jenkinsci/svnmerge-plugin/compare/344a848c5d48...d4f365865c77 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-24735) Add support for build parameters in Subversion URLs.
SCM/JIRA link daemon commented on JENKINS-24735 Add support for build parameters in Subversion URLs. Code changed in jenkins User: Alexandros Ouzounis Path: src/main/java/jenkins/plugins/svnmerge/IntegrateAction.java http://jenkins-ci.org/commit/svnmerge-plugin/c1c54c962b9dc39b2d865119ca343343779c1c96 Log: JENKINS-24735 - Add support for build parameters in Subversion URLs Update IntegrateAction to expand SVN URLs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [radiatorview-plugin] (JENKINS-23096) radiatorviewplugin has incorrect links for jobs in folders
SCM/JIRA link daemon commented on JENKINS-23096 radiatorviewplugin has incorrect links for jobs in folders Code changed in jenkins User: Baptiste Mathus Path: src/main/resources/hudson/model/RadiatorView/job.jelly http://jenkins-ci.org/commit/radiatorview-plugin/60e37149d77ba77fdfb31648498b651543fc5ce8 Log: [FIXED JENKINS-23096] incorrect links for jobs The behaviour of the job.getUrl() seems to have changed around Jenkins 1.568. It now returns a relative path instead of an absolute one. So replacing the relative url by an absolute one fixes it for the radiatorplugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [radiatorview-plugin] (JENKINS-23096) radiatorviewplugin has incorrect links for jobs in folders
SCM/JIRA link daemon resolved JENKINS-23096 as Fixed radiatorviewplugin has incorrect links for jobs in folders Change By: SCM/JIRA link daemon (05/Nov/14 1:20 PM) Status: In Progress 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] [git-client-plugin] (JENKINS-25444) CliGit implementation of fetch/deleteBranch does remove open changes, JGit does not
Stephan Pauxberger commented on JENKINS-25444 CliGit implementation of fetch/deleteBranch does remove open changes, JGit does not Created pull request 153 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist."
Martin Hohl assigned JENKINS-25450 to Cletus D'Souza Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist." Change By: Martin Hohl (05/Nov/14 1:11 PM) Assignee: Cletus D'Souza This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist."
Martin Hohl created JENKINS-25450 Unexpected behavior of Integrity plugin after "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist." Issue Type: Bug Assignee: Unassigned Components: integrity-plugin Created: 05/Nov/14 1:10 PM Description: The Integrity - CM Polling Log says "Started on Nov 5, 2014 7:00:00 AM Preparing to execute si projectinfo for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pj Preparing to execute si viewproject for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pj A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist. Done. Took 7.8 sec No changes" and the job status of the build job is not FAILED. Normally, if the plugin says "Failed to establish an API connection to the Integrity Server!" it fails the build job (as expected). I would not expect that a Jenkins job can have status OK, if the workspace cannot be populated or updated with the SCM configured for that job. Environment: Jenkins 1.586 - PTC Integrity CM - Jenkins Plugin 1.28 Project: Jenkins Priority: Critical Reporter: Martin Hohl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-25415) Develop and implement a "Continuous Integration Experience Index"
Torsten Schlabach updated JENKINS-25415 Develop and implement a "Continuous Integration Experience Index" Change By: Torsten Schlabach (05/Nov/14 1:03 PM) Assignee: Manuel Carrasco This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25444) CliGit implementation of fetch/deleteBranch does remove open changes, JGit does not
Mark Waite commented on JENKINS-25444 CliGit implementation of fetch/deleteBranch does remove open changes, JGit does not Thanks for detecting that inconsistency. I think the CliGit implementation should be considered the reference implementation and the JGit implementation should eventually be modified to match the behavior of CliGit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-14332) Repeated channel/timeout errors from Jenkins slave
Poul Henriksen commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave I had the same issue. Downgrading the Jenkins master kernel from 3.14.19-17.43.amzn1.x86_64 to 3.4.62-53.42.amzn1.x86_64 solved 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] [matrix-project-plugin] (JENKINS-25449) Add form validation for label expression axis
Oliver Gondža created JENKINS-25449 Add form validation for label _expression_ axis Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 05/Nov/14 12:29 PM Project: Jenkins Priority: Minor 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] [matrix-project-plugin] (JENKINS-25448) NPE on job save when no expressions provided for label expression axis
Oliver Gondža created JENKINS-25448 NPE on job save when no expressions provided for label _expression_ axis Issue Type: Bug Assignee: Oliver Gondža Components: matrix-project-plugin Created: 05/Nov/14 12:28 PM Description: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:628) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) Caused by: java.lang.NullPointerException at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187) at com.google.common.collect.SingletonImmutableSet.(SingletonImmutableSet.java:47) at com.google.common.collect.ImmutableSet.of(ImmutableSet.java:88) at com.google.common.collect.ImmutableSet.copyFromCollection(ImmutableSet.java:341) at com.google.common.collect.ImmutableSet.copyOf(ImmutableSet.java:329) at com.google.common.collect.Sets$CartesianSet$Axis.(Sets.java:1086) at com.google.common.collect.Sets$CartesianSet.(Sets.java:998) at com.google.common.collect.Sets.cartesianProduct(Sets.java:935) at hudson.matrix.AxisList.list(AxisList.java:82) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:630) at hudson.matri
[JIRA] [analysis-core-plugin] (JENKINS-25447) ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception
Daniel Beck resolved JENKINS-25447 as Duplicate ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception Duplicates ... some other issue I can't be bothered to search right now Solution: Update Analysis Core to 1.65. (Plugin Manager » Advanced » Check Now to force a refresh of the data) Change By: Daniel Beck (05/Nov/14 12:09 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] [flaky-test-handler-plugin] (JENKINS-25446) ERROR: Publisher com.google.jenkins.flakyTestHandler.plugin.JUnitFlakyResultArchiver aborted due to exception
Daniel Beck updated JENKINS-25446 ERROR: Publisher com.google.jenkins.flakyTestHandler.plugin.JUnitFlakyResultArchiver aborted due to exception Added the component. Of course, I doubt it'll help getting this resolved if the authors haven't bothered to set up a component to begin with. Change By: Daniel Beck (05/Nov/14 12:05 PM) Component/s: flaky-test-handler-plugin Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25447) ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception
Jonas Bang Christensen commented on JENKINS-25447 ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception Just to make it perfectly clear: It works now with "warnings-plugin" 4.43 and "analysis-core" 1.61 on Jenkins 1.565.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25447) ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception
Jonas Bang Christensen created JENKINS-25447 ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin, warnings-plugin Created: 05/Nov/14 11:53 AM Description: After updating "warnings-plugin" from 4.42 to 4.43 (and "analysis-core" from 1.61 to 1.64) then ALL my jobs fail no matter which parser is used (see logs below). I tried to downgrade "warnings-plugin" to 4.42, still they fail. I tried to uninstall "warnings-plugin" and install it again, still they fail. I tried to disable "warnings-plugin" in the individual job (they pass, obviously) and enable it again, still they fail. Then I tried to downgrade "analysis-core" to 1.61, and they pass again. So, seems to be an issue with "analysis-core" 1.64. Log example 1: 00:02:46.430 [WARNINGS] Parsing warnings in console log with parser IAR Compiler (C/C++) 00:02:46.491 ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception 00:02:46.494 java.lang.NoSuchMethodError: hudson.plugins.analysis.core.ParserResult.addAnnotations(Ljava/util/Collection;)V 00:02:46.495 at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:405) 00:02:46.495 at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:321) 00:02:46.495 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:319) 00:02:46.495 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 00:02:46.495 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) 00:02:46.495 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) 00:02:46.495 at hudson.model.Build$BuildExecution.post2(Build.java:182) 00:02:46.495 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) 00:02:46.495 at hudson.model.Run.execute(Run.java:1731) 00:02:46.495 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 00:02:46.495 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:02:46.495 at hudson.model.Executor.run(Executor.java:232) Log example 2: 00:03:34.271 [WARNINGS] Parsing warnings in console log with parser Texas Instruments Code Composer Studio (C/C++) 00:03:34.286 ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception 00:03:34.286 java.lang.NoSuchMethodError: hudson.plugins.analysis.core.ParserResult.addAnnotations(Ljava/util/Collection;)V 00:03:34.286 at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:405) 00:03:34.286 at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:321) 00:03:34.286 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:319) 00:03:34.286 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 00:03:34.286 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) 00:03:34.286 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) 00:03:34.287 at hudson.model.Build$BuildExecution.post2(Build.java:182) 00:03:34.287 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) 00:03:34.287 at hudson.model.Run.execute(Run.java:1731) 00:03:34.287 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 00:03:34.287 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:03:34.287 at hudson.model.Executor.run(Executor.java:232) Log example 3: 00:01:56.629 [WARNINGS] Parsing warnings in console log with parser MSBuild 00:01:56.644 ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception 00:01:56.645 java.lang.NoSuchMethodError: hudson.plugins.analysis.core.ParserResult.addAnnotations(Ljava/util/Collection;)V 00:01:56.645 at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:405) 00:01:56.645 at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPubl
[JIRA] [git-server-plugin] (JENKINS-25264) Scriptler add script fails with java.io.IOException: failed to update git repo
Manish Singh commented on JENKINS-25264 Scriptler add script fails with java.io.IOException: failed to update git repo You will also need to downgrade the Scriptler plugin to 2.6.1 version. Download it from: https://updates.jenkins-ci.org/download/plugins/scriptler/2.6.1/scriptler.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.
