[JIRA] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Title: Message Title bbonn commented on JENKINS-22853 Re: SEVERE: Trying to unexport an object that's already unexported HI There, We are still seeing this on Jenkins ver. 2.7.1. Is there additional things we can do to troubleshoot. We have also been crashing with permgen errors since upgrade, not sure if related. Please advise if i should reopen this issue. Thanks! SEVERE: Trying to unexport an object that's already unexported java.lang.IllegalStateException: Invalid object ID 412 iota=773 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:409) at hudson.remoting.Channel.unexport(Channel.java:641) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$1.handle(Channel.java:501) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: java.lang.Exception: Object was recently deallocated #412 (ref.0) : object=null type=hudson.remoting.FastPipedOutputStream interfaces=[java.lang.Object] Created at Thu Feb 02 09:24:16 EST 2017 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:629) at hudson.remoting.Pipe.writeObject(Pipe.java:158) at sun.reflect.GeneratedMethodAccessor1141.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at java.io.ObjectStreamClass.invokeWriteObject(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.writeObject(Unknown Source) at hudson.remoting.UserRequest._serialize(UserRequest.java:189) at hudson.remoting.UserRequest.serialize(UserRequest.java:198) at hudson.remoting.UserRequest.(UserRequest.java:64) at hudson.remoting.Channel.callAsync(Channel.java:807) at hudson.FilePath.actAsync(FilePath.java:1087) at hudson.FilePath.read(FilePath.java:1782) at hudson.plugins.groovy.FileScriptSource.getScriptStream(FileScriptSource.java:52) at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:93) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Released at Thu Feb 02 09:24:16 EST 2017 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:414) at hudson.remoting.Channel.unexport(Channel.java:641) at hudson.remoting.ProxyOutputStream$EOF$1.run(ProxyOutputStream.jav
[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled
Title: Message Title bbonn updated an issue Jenkins / JENKINS-29130 RTC Polling broken when Proxy enabled Change By: bbonn Hi,We have an issue with RTC polling when we have the proxy set in Jenkins. We need to set http and https proxy settings on the master for many other apps. So we do this in the Jenkins.xml file on the master. But this seems to break polling on RTC jobs. Jobs can still pull files out of source control but polling does not work. What is the difference between these 2 operations? Gives the below stack trace in the polling log:Any ideas, this one is killing us ! :) Any help would be greatly appreciated!!FATAL: RTC : checking for changes failure: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver. paychex company .com:9443/ccm2/versionCompatibility?clientVersion=5.0. Error details: Remote host closed connection during handshake.com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver. paychex company .com:9443/ccm2/versionCompatibility? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled
Title: Message Title bbonn created an issue Jenkins / JENKINS-29130 RTC Polling broken when Proxy enabled Issue Type: Bug Assignee: Unassigned Components: teamconcert-plugin Created: 29/Jun/15 3:44 PM Environment: windows 2008 Priority: Critical Reporter: bbonn Hi, We have an issue with RTC polling when we have the proxy set in Jenkins. We need to set http and https proxy settings on the master for many other apps. So we do this in the Jenkins.xml file on the master. But this seems to break polling on RTC jobs. Jobs can still pull files out of source control but polling does not work. What is the difference between these 2 operations? Gives the below stack trace in the polling log: Any ideas, this one is killing us ! Any help would be greatly appreciated!! FATAL: RTC : checking for changes failure: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.paychex.com:9443/ccm2/versionCompatibility?clientVersion=5.0. Error details: Remote host closed connection during handshake. com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.paychex.com:9443/ccm2/versionCompatibility?
[JIRA] [teamconcert-plugin] (JENKINS-25762) Build Engine going inactive due to no credentials
bbonn edited a comment on JENKINS-25762 Build Engine going inactive due to no credentials Thanks Heather! This seems to be having a good effect. We will continue to monitor. Thanks again, Bernie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-25762) Build Engine going inactive due to no credentials
bbonn commented on JENKINS-25762 Build Engine going inactive due to no credentials Thanks Heather! This seeme to be having a good effect. We will continue to monitor. Thanks again, Bernie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-git-plugin] (JENKINS-25762) Build Engine going inactive due to no credentials
bbonn created JENKINS-25762 Build Engine going inactive due to no credentials Issue Type: Bug Assignee: Krishna Kishore Components: teamconcert-git-plugin Created: 24/Nov/14 3:38 PM Description: Hi there, We were recently required by our security group to disable anonymous access in Jenkins. This has had a negative effect on our RTC integration. We have never required folks to put in credentials into the build engine. Not many folks have taken to kicking off builds from the Eclipse, and it is one more place to forget to change your password. When we made the change we had a bunch of build engines shut down, i.e. go inactive. Is there any way around this, we don't want to ask developers to put credentials in unless they want the 2 way interaction (kicking off builds from Eclipse). Thanks! Environment: Windows Server 2008 & 12 Project: Jenkins Labels: teamconcert RTC, Priority: Major Reporter: bbonn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
bbonn commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart Hi Heather, Yes we use Oracles JVM on all of our masters and slaves. We have thought about loading the toolkit but it would be a pain to maintain for all of our slaves (approx 100). If we could install it automatically like the jdk and ant that would be great, but I feel like I tried that and it didn't work. Are you saying for a future version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
bbonn commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart Hi there, Just wanted to add a question one of my peers came up with. This is still a big problem for us, we have massive failure after any master restart(we think) we are starting to wonder if it is completely related to master restarts or something else. A manula restart of the slave always seems to fix the issue, but this is not practical. Please let us know if there is anything else we can try to help trouble shoot. ~Thanks! It appears they are replacing the default java (remote) classloader with their own: 10:17:06 Original class loader: hudson.remoting.RemoteClassLoader@1d90cec 10:17:06 Found hjplugin-rtc jar /C:/Users/_HUDSO~1/AppData/Local/Temp/jenkins-remoting4111565012137500452/com.ibm.team.build.hjplugin-rtc-1.0.0.jar 10:17:06 System class loader sun.misc.Launcher$AppClassLoader@601bb1 10:17:06 new classloader: com.ibm.team.build.internal.hjplugin.RTCFacadeClassLoader@9304ba but it doesn't handle controller socket disconnect very well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
bbonn commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart Thanks Heather, I'll share with the team. We run our slaves as windows services, so they start with this: java -Xrs -Xmx1024m -XX:MaxPermSize=128m -jar -Djava.library.path="\\hcntpnv02\tools\RTC\natives" "%BASE%\slave.jar" -jnlpUrl http:///computer/someSlave/slave-agent.jnlp -secret someSecret This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
bbonn commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart Hi Heather, Just wanted to give you some more information on this. A team member had done some looking and had this to add: "It is possible that the failure in RTC plugin is because the classpath becomes so long that part of it is cutting off. We have seen BuildClient (in the HPI), ScmPackage (in the toolkit), and now OperationCanceledException (in the toolkit) all having a NoClassDefFoundError. The RTC toolkit is pulling in over 100 jar files which by itself doesn’t seem like it would be too many but maybe it has something to do with the problem. We did a test where we created a share which had a shorter path than what the agent was using previously. This resolved the problem in almost all cases. But sometimes the error still appears." Does this make sense as a possible cause to what we are seeing? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
bbonn created JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart Issue Type: Bug Assignee: Unassigned Components: teamconcert Created: 10/Mar/14 7:41 PM Description: Hi, We have jobs that use the Team Concert plugin error out after the master is restarted. If we restart the Jenkins Slave service it repairs itself. In our configuration we have the Build Toolkit living on a share, and all of our slaves access it via a unc path (\\server\... etc.) Which is configured in the Global Jenkins config. The error we see in the Jenkins job console when attempting a transaction with RTC is: 00:00:00.012 RTC : checkout... 00:00:00.560 FATAL: RTC : checkout failure: Could not initialize class com.ibm.team.build.internal.hjplugin.rtc.BuildClient 00:00:00.561 java.lang.NoClassDefFoundError: Could not initialize class com.ibm.team.build.internal.hjplugin.rtc.BuildClient 00:00:00.562 at com.ibm.team.build.internal.hjplugin.rtc.RTCFacade.getBuildClient(RTCFacade.java:51) 00:00:00.562 at com.ibm.team.build.internal.hjplugin.rtc.RTCFacade.checkout(RTCFacade.java:404) 00:00:00.563 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 00:00:00.563 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 00:00:00.563 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 00:00:00.564 at java.lang.reflect.Method.invoke(Unknown Source) 00:00:00.564 at com.ibm.team.build.internal.hjplugin.RTCFacadeFactory$RTCFacadeWrapper.invoke(RTCFacadeFactory.java:96) 00:00:00.564 at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:110) 00:00:00.565 at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:31) 00:00:00.565 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2394) 00:00:00.565 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 00:00:00.565 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 00:00:00.566 at hudson.remoting.Request$2.run(Request.java:326) 00:00:00.566 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 00:00:00.566 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 00:00:00.566 at java.util.concurrent.FutureTask.run(Unknown Source) 00:00:00.567 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 00:00:00.567 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 00:00:00.567 at hudson.remoting.Engine$1$1.run(Engine.java:63) 00:00:00.567 at java.lang.Thread.run(Unknown Source) 00:00:00.568 ERROR: RTC : checkout failure: Could not initialize class com.ibm.team.build.internal.hjplugin.rtc.BuildClient We have over 70 slaves so restarting them before jobs jump on there is a little problematic. Any ideas, would be great not to have to worry about his going forward. Thanks! Environment: Master - Windows 2008 Server Slaves - Windows 2008 Server Team Concert Plugin v 1.0.11 Project: Jenkins Priority: Major Reporter: bbonn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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] (JENKINS-21767) Add alert configuration for identified causes
bbonn created JENKINS-21767 Add alert configuration for identified causes Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer Created: 11/Feb/14 6:45 PM Description: Hi, It would be cool if you could configure this plugin to e-mail a group when a certain error line is recognized. We have a recent use case where we want to know whenever a certain failure occurs in our build environment. We have a pretty big Jenkins environment so an automated solution would be great. Let me know if this doesn't make sense. Thanks for the consideration! Environment: Windows Server 2008 Project: Jenkins Priority: Minor Reporter: bbonn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21537) Option to use Global User and Password when RTC url is overidden
bbonn created JENKINS-21537 Option to use Global User and Password when RTC url is overidden Issue Type: Improvement Assignee: Unassigned Components: teamconcert Created: 28/Jan/14 8:46 PM Description: Hi there, We are rolling out the plugin in a large environment. One big nuisance for us is the need to enter a user name and password when the "Override global RTC repository connection" box is checked. We use a generic build user and we don't like to give out the password for it. Other SCM plugins will default to the global user and password if the fields are left blank. This would be optimum. Let me know if you need any clarification. Thanks! Environment: Jenkins Master - Windows Server 2008 Slaves - Windows & Linux Project: Jenkins Priority: Major Reporter: bbonn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18293) Team Concert plugin cannot cope with symbolic links
bbonn commented on JENKINS-18293 Team Concert plugin cannot cope with symbolic links Hi There, Is there a work item for a more formal fix to this issue. We have a Jenkins farm with over 70 slaves. Which means I would have to do this workaround for all of them, then maintain it per RTC version. Let me know if I should create request on in RTC for Jazz dev. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
bbonn commented on JENKINS-15156 Builds disappear from build history after completion Hi all, I have found a way to reproduce in our environment. Not sure if this will be the same for all of you, but maybe it is a start for debugging. I noticed recently that while un-shelving a job (plugin we use quite frequently) a job that was running displayed a strange 404 error in the console. See below 15:27:09 [WARNINGS] Parsing warnings in console log... 15:27:09 Archiving artifacts Status Code: 404 Exception: Stacktrace: (none) I then went back job page and refreshed and the build had disappeared. A reload from disk brought it back as usual. I have recreated a couple of times now, so not sure if the Shelve plugin is the culprit or some other underlying piece that interacts with plugins. Also, I don't always get the 404 in the console, sometimes after starting a un-shelving job, the link for the build console goes right tot a generic 404 error page. Jenkins 1.480.1 Windows Server 2008 R2 (Master and Slave) Can anyone else recreate this way? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7481) ClearCase polling change degrades performance for large VOBs
bbonn commented on JENKINS-7481 ClearCase polling change degrades performance for large VOBs Sounds good. Any idea when they will do another pull? In the meantime do you have a version I could test with from your branch? I was wondering if there was any new config we have to do to force the -r in stead of -all. Thanks 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
[JIRA] (JENKINS-7481) ClearCase polling change degrades performance for large VOBs
bbonn commented on JENKINS-7481 ClearCase polling change degrades performance for large VOBs Hi, Just upgraded to 1.3.11, thinking I would see lshistory -r instead of -all in the console log. But I haven't seen a difference. I have tested on some builds that have not built in a while hoping the lshistory portion would be shortened, but no-go. Am I missing some config, or did I misread this bug? I appreciate any guidance. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15323) Allow user to define X and Y axis
bbonn updated JENKINS-15323 Allow user to define X and Y axis Change By: bbonn (26/Sep/12 5:27 PM) Description: It would be great if the plot plugin accepted both axis if fed a file , not force the X axis as builds . I would like to produce reports form a file where I provide both data points and the plugin just produces the chart of my choice. Kind of like you could do with Excel. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15323) Allow user to define X and Y axis
bbonn created JENKINS-15323 Allow user to define X and Y axis Issue Type: New Feature Assignee: nidaley Components: plot Created: 26/Sep/12 5:26 PM Description: It would be great if the plot plugin accepted both axis if fed a file. I would like to produce reports form a file where I provide both data points and the plugin just produces the chart of my choice. Kind of like you could do with Excel. Environment: Windows Server 2008 Project: Jenkins Labels: reporting plot Priority: Minor Reporter: bbonn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
bbonn created JENKINS-15156 Builds Disappear from Build History after Completion Issue Type: Bug Assignee: Unassigned Components: other Created: 13/Sep/12 2:20 PM Description: We have recently noticed builds disappearing from the "Build History" listing on the project page. Developer was watching a build, waiting for it to complete and said it disappeared after it finished. Nothing was noted in any of the logs concerning that build. The data was still present on the disk and doing a reload from disk brought the build back. We have other automated jobs that deploy these builds based on build number, so it is pretty big issue in our environment. We are not able to reproduce at this point, but I still wanted to document what was happening. I have seen other JIRA issues that look similar, but in those jobs were disappearing after a restart, or upgrade. That is not the case for us. The build disappears after completion, success or failure. Environment: Jenkins 1.477.2 Master and Slaves Windows Server 2008 r2 Project: Jenkins Priority: Major Reporter: bbonn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12695) Upload fails when using Fortify 3.30
bbonn created JENKINS-12695: --- Summary: Upload fails when using Fortify 3.30 Key: JENKINS-12695 URL: https://issues.jenkins-ci.org/browse/JENKINS-12695 Project: Jenkins Issue Type: Bug Components: fortify360 Environment: Windows Server 2008 Jenkins ver. 1.409.2 Fortify ver. 3.30 Reporter: bbonn Assignee: samngms Hi, We have been using the Fortify360 plugin for a while, works like a charm. But we have recently upgraded to Fortify 3.30. We noticed that if 3.30 is on the system Path the plugin will look there for the 4 files it needs to do the upload (i.e. wsclient.jar,wsobjects.jar, common.jar,common13.jar). Problem is they are not there (in core/lib/) in 3.30, at least they are not named the same. So, if we leave the Version field blank in the global Jenkins config, or we enter 3.30 we get an error that the plugin can't find the .jars it needs. We can get around it by using 3.30 to do the scans but entering 2.65 for the Jars Path for the upload. But still seems like it should be fixed going forward. Here is an example of the error: Error uploading to F360 Server: http://ourfortifyserver/f360 java.lang.RuntimeException: Invalid JarsPath: N:\Program Files (x86)\Fortify Software\HP Fortify v3.30\Core\lib, can't locate common.jar or common13.jar Let me know if you need any more info or need me to try anything. I am glad to help. Thanks! Bernie Bonn -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
