[JIRA] (JENKINS-51178) NullPointer while resolving already deployed apps
Title: Message Title Daniel Fischer closed an issue as Fixed Although nobody commented on my issue: this issue seems to be fixed in websphere-deployer-plugin version 1.6.1. I no longer get that NullPointerException with v1.6.1. Jenkins / JENKINS-51178 NullPointer while resolving already deployed apps Change By: Daniel Fischer Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-51178) NullPointer while resolving already deployed apps
Title: Message Title Daniel Fischer updated an issue Jenkins / JENKINS-51178 NullPointer while resolving already deployed apps Change By: Daniel Fischer Summary: NullPointer while resolving already deployed apps Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51178) NullPointer
Title: Message Title Daniel Fischer created an issue Jenkins / JENKINS-51178 NullPointer Issue Type: Bug Assignee: Unassigned Components: websphere-deployer-plugin Created: 2018-05-07 11:41 Environment: websphere-deployer-plugin 1.6.0 on local Jenkins master: Jenkins LTS v2.107.2 on Tomcat 8 Debian Linux 8 Oracle JDK 1.8.0_161 Remote WebSphere Application Server 8.5.5.6 on SLES 11 SP4 Priority: Major Reporter: Daniel Fischer I am using version 1.6.0 of the websphere-deployer-plugin and can not get it to work. I want to deploy a WAR file to a WAS 8.5 single server instance (no liberty profile). The "test connection" button on the job config page reports a successfull connection. The WAR should be installed/updated. The name of the existing deployed WAR application is configured. That deployment should be updated by that job. However I am getting a Nullpointer at the time the plugin checks for existing applications on the was instance: Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- /var/lib/jenkins/workspace/job-deploy-web-ui-HEAD/hyperdoc-web-ui.war Last modified on Mai 07, 2018 10:58:17 --- Generating EAR For Artifact: hyperdoc-web-ui_war Artifact is being deployed to virtual host: default_host Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Could not determine if artifact 'hyperdoc-web-ui_war' is installed: General Exception: null at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.isArtifactInstalled(WebSphereDeploymentService.java:477) at
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Daniel Fischer edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Is it It is {noformat} _MSPDBSRV_ENDPOINT_ {noformat} (with underlines) or is it not MSPDBSRV_ENDPOINT ? .Just realized it myself that it's a formatting issue. If you enclose the word in underlines it will get italicised and the underlines disappear. ;)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Daniel Fischer commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Is it MSPDBSRV_ENDPOINT (with underlines) or is it MSPDBSRV_ENDPOINT ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [viewVC-plugin] (JENKINS-25563) ViewVC links for classic CVS integration are not generated
Daniel Fischer created JENKINS-25563 ViewVC links for classic CVS integration are not generated Issue Type: Bug Assignee: Unassigned Components: viewVC-plugin Created: 12/Nov/14 11:31 AM Description: The ViewVC integration is not working if I configure it under advanced repository properties on the classic "CVS" integration. If I configure the ViewVC repository browser on the "CVS Projectset" the links are shown correctly. I am using Jenkins 1.580.1 LTS on tomcat 6 and CVS Plugin v2.12 and ViewVC Plugin v1.7. Environment: OS: SLES 11 SP3, Jenkins 1.580.1 LTS on tomcat 6 Project: Jenkins Labels: plugin viewvc cvs viewcvs Priority: Major Reporter: Daniel Fischer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-18337) Fingerprint throws exceptions on 1.518
Daniel Fischer updated JENKINS-18337 Fingerprint throws exceptions on 1.518 We are getting a similar exception now with one job at fingerprinting. I think it is caused by an unmasked special character in the XML file. We have an ampersand character in the fileName tag. This causes the following exception: Zeichne Fingerabrücke auf ERROR: Aufzeichnen der Fingerabdrücke fehlgeschlagen hudson.util.IOException2: Unable to read /var/lib/jenkins/fingerprints/ad/e6/834fc0dc20875dcc2c88635d6b37.xml at hudson.XmlFile.read(XmlFile.java:147) at hudson.model.Fingerprint.load(Fingerprint.java:981) at hudson.model.Fingerprint.load(Fingerprint.java:969) at hudson.model.FingerprintMap.load(FingerprintMap.java:94) at hudson.model.FingerprintMap.load(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.get(KeyedDataStorage.java:154) at hudson.model.FingerprintMap.get(FingerprintMap.java:79) at hudson.model.FingerprintMap.get(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.getOrCreate(KeyedDataStorage.java:108) at hudson.model.FingerprintMap.getOrCreate(FingerprintMap.java:65) at hudson.tasks.Fingerprinter$1Record.addRecord(Fingerprinter.java:210) at hudson.tasks.Fingerprinter.record(Fingerprinter.java:254) at hudson.tasks.Fingerprinter.perform(Fingerprinter.java:121) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Caused by: com.thoughtworks.xstream.converters.ConversionException: : entity reference name can not contain character ' (position: START_TAG seen ...fileNameREC1RE.DAT... @5:25) : : entity reference name can not contain character ' (position: START_TAG seen ...fileNameREC1RE.DAT... @5:25) Debugging information message : : entity reference name can not contain character ' (position: START_TAG seen ...fileNameREC1RE.DAT... @5:25) cause-exception : com.thoughtworks.xstream.io.StreamException cause-message : : entity reference name can not contain character ' (position: START_TAG seen ...fileNameREC1RE.DAT... @5:25) class : java.lang.String required-type : java.lang.String converter-type : com.thoughtworks.xstream.converters.SingleValueConverterWrapper wrapped-converter : com.thoughtworks.xstream.converters.basic.StringConverter path: /fingerprint/fileName line number : 5 class1: hudson.model.Fingerprint converter-type1 : hudson.util.RobustReflectionConverter version : null --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925) at
[JIRA] [core] (JENKINS-18337) Fingerprint throws exceptions on 1.518
Daniel Fischer commented on JENKINS-18337 Fingerprint throws exceptions on 1.518 The issue with the special characters in the filename or other tags could be fixed analogical to JENKINS-10241 (keyword CDATA). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15416) The CVS changes detector does not exclude changes outside of HEAD if SCM Location Head is selected
Daniel Fischer closed JENKINS-15416 as Fixed The CVS changes detector does not exclude changes outside of HEAD if SCM Location Head is selected Fix verified with Jenkins CVS Plug-in version 2.7. Change By: Daniel Fischer (21/Nov/12 8:28 AM) 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
[JIRA] (JENKINS-15416) The CVS changes detector always does no filtering on selected branch or tag
Daniel Fischer updated JENKINS-15416 The CVS changes detector always does no filtering on selected branch or tag Please see attached file JENKINS-15416.zip . As you can see in included file hyperdoc-buildresources-HEAD\config.xml the HEAD is selected. The pollingLog file mentions a sourcecode change. The changes.htm shows one changed file /iqdoq/product/hyp4x/build/versno.properties with revision no 1.1307.2.18.2.41 . To verify that this revision was not checked in to the Head (branch) please see the screenshot file viewvc_screenshot_shows_commit_is_on_branch_hyp-5-3-1-branch_and_not_HEAD.png . The commit was done in branch hyp-5-3-1-branch (not HEAD). Also in jenkins.log I am getting numerous warnings like "#65188 warning C/S protocol error (section 5.10). It's regurarly observed with cvs 1.12.xx servers.". Change By: Daniel Fischer (09/Oct/12 8:24 AM) Attachment: JENKINS-15416.zip This message is automatically generated by JIRA. 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-15416) The CVS changes detector always does no filtering on selected branch or tag
Daniel Fischer commented on JENKINS-15416 The CVS changes detector always does no filtering on selected branch or tag I have copied the job hyperdoc-buildresources-HEAD for the build of another branch (hyp-5-4-0-branch). I have named the job hyperdoc-buildresources-5-4-0 If a commit is done out of that hyp-5-4-0-branch, the job hyperdoc-buildresources-5-4-0 detects no scm changes. This leads me to the assumption that the scm changes detector only has problems if the job uses the CVS Head. Perhaps the logic has to be changed that when Head is selected the changes detector has to filter out all branches rather than include a specific 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
[JIRA] (JENKINS-15416) The CVS changes detector always does no filtering on selected branch or tag
Daniel Fischer updated JENKINS-15416 The CVS changes detector always does no filtering on selected branch or tag Please see attached file cvs_rlog_out_hyperdoc-buildresources-HEAD-3.txt . I have simply 'replayed' the CVS rlog output command like that on the linux jenkins master command line: cvs rlog -S -d"05 Oct 2012 11:00:41 +020005 Oct 2012 16:00:53 +0200" iqdoq/product/hyp4x/build 21 cvs_rlog_out_hyperdoc-buildresources-HEAD-3.txt Change By: Daniel Fischer (09/Oct/12 9:28 AM) Attachment: cvs_rlog_out_hyperdoc-buildresources-HEAD-3.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
[JIRA] (JENKINS-15416) The CVS changes detector always does no filtering on selected branch or tag
Daniel Fischer commented on JENKINS-15416 The CVS changes detector always does no filtering on selected branch or tag The comment on the changes page is: Änderungen Zusammenfassung Autobuild: Release build hyp-5-3-1-28_442 autobuild: Autobuild: Release build hyp-5-3-1-28_442 The file was modified 1.1307.2.18.2.41 /iqdoq/product/hyp4x/build/versno.properties This message is automatically generated by JIRA. 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-15416) The CVS changes detector does not exclude changes outside of HEAD if SCM Location Head is selected
Daniel Fischer updated JENKINS-15416 The CVS changes detector does not exclude changes outside of HEAD if SCM Location Head is selected Change By: Daniel Fischer (09/Oct/12 10:14 AM) Summary: TheCVSchangesdetector always does nofilteringon notexcludechangesoutsideofHEADifSCMLocationHeadis selected branchortag This message is automatically generated by JIRA. 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-15416) The CVS changes detector always does no filtering on selected branch or tag
Daniel Fischer created JENKINS-15416 The CVS changes detector always does no filtering on selected branch or tag Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs Created: 05/Oct/12 9:25 AM Description: Bug found using the Jenkins CVS-Plugin version 2.6: The detection for changes for a CVS SCM is actually made with the cvs rlog command. The cvs rlog command does not set the revision option (-r) when polling HEAD or any other branches. If no -r option is applied all changes of all branches are detected! The cvs rlog option -rbranch has always to be appended. If the Head is configured cvs rlog command has to use -rHEAD. Environment: SUSE Linux Enterprise Server 11 SP2 on x86-64 Fix Versions: current Project: Jenkins Labels: plugin scm cvs Priority: Major Reporter: Daniel Fischer This message is automatically generated by JIRA. 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-14238) Use Local module directory instead Use custom workspace
Daniel Fischer commented on JENKINS-14238 Use Local module directory instead Use custom workspace I have a similar problem. The Cobertura Plugin uses the checked out directory as its search root for the resulting xml files. I need the search root set to the working directory and not to any subdirectory in the working directory. The Artifacts publisher and the JUnit results plugin are using the workspace root directory. The Cobertura Publisher plugin should use the same. This message is automatically generated by JIRA. 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-3862) Allow configuration of base directory for Cobertura report XML files
Daniel Fischer commented on JENKINS-3862 Allow configuration of base directory for Cobertura report XML files See also related issue JENKINS-14238. This message is automatically generated by JIRA. 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-14238) Use Local module directory instead Use custom workspace
Daniel Fischer commented on JENKINS-14238 Use Local module directory instead Use custom workspace See also related issue JENKINS-3862. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
