[JIRA] [subversion-plugin] (JENKINS-32892) SVN_REVISION(_1) gets set to an unexpected value, seems to be "Last Changed Rev" from previous build.
Title: Message Title Tim-Christian Bloss created an issue Jenkins / JENKINS-32892 SVN_REVISION(_1) gets set to an unexpected value, seems to be "Last Changed Rev" from previous build. Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 11/Feb/16 12:46 PM Environment: AMD64 Debian GNU/Linux 8 Jenkins LTS 1.609.3 Tomcat 7.0.54 Oracle JDK 8 Subversion Plugin 1.5.7 LANG=de_DE.UTF-8 Labels: subversion variable variables Priority: Major Reporter: Tim-Christian Bloss SVN_REVISION(_1) gets set to an unexpected value, seems to be "last modified" from previous build. For a regular job (here maven, but seems to happen also on freestyle) using subversion plugin for checkout, we get the following behaviour: Job overview states Revision: 55304 Checking out http://svn-[.]/trunk at revision '2016-02-11T13:04:54.819 +0100' At revision 55305
[JIRA] [subversion-plugin] (JENKINS-32892) SVN_REVISION(_1) gets set to an unexpected value, seems to be "Last Changed Rev" from previous build.
Title: Message Title Tim-Christian Bloss updated an issue Jenkins / JENKINS-32892 SVN_REVISION(_1) gets set to an unexpected value, seems to be "Last Changed Rev" from previous build. Change By: Tim-Christian Bloss SVN_REVISION(_1) gets set to an unexpected value, seems to be "last modified" from previous build.For a regular job (here maven, but seems to happen also on freestyle) using subversion plugin for checkout, we get the following behaviour:Job overview statesRevision: 55304Checking out http://svn-[.]/trunk at revision '2016-02-11T13:04:54.819 +0100'At revision 55305variables set in this build by subversion plugin:SVN_REVISION_1=55291SVN_REVISION=55291svn info from prebuild-step shell command states:Revision: 55305Last Changed Rev: 55304When running another build of this job:Job overview statesRevision: 55304Checking out http://svn-[...]/trunk at revision '2016-02-11T13:10:41.523 +0100'At revision 55315variables set in this build by subversion plugin:SVN_REVISION_1=55304SVN_REVISION=55304svn info from prebuild-step shell command states:Revision: 55315Last changed Rev: 55304We expected SVN_REVISION(_1) to be set to the value of svn info "Last Changed Rev" of the current build, but it seems like it gets set to the value of svn info "Last Changed Rev" which was seen in the previous build.When we start a checkout, abort the job immediately after checkout, and start again, we get the SVN_REVISION(_1) set as expected, but only if nobody has checked in new changes before starting a new build.This behaviour is reproducible for us for all jobs using subversion plugin for checkout. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [subversion-plugin] (JENKINS-27137) Connection Aborted since 2.5 on Win64
Title: Message Title Tim-Christian Bloss commented on JENKINS-27137 Re: Connection Aborted since 2.5 on Win64 We had no issues using 2.4.5 in Jenkins 1.596.3 , neither on Windows nor Linux. Using 2.5 we got some other errors and issues, both on Linux and Windows. Using 2.5.4 no error occured when using Jenkins 1.596.3 Also no error using 2.5.4 with Jenkins 1.609.3 , neither on Linux nor Windows. Summed up: subversion plugin 2.4.5 and 2.5.4 both work with Jenkins 1.596.3 and 1.609.3 on Linux and Windows using Oracle JRE 1.8.0u66(master) and 1.80u25/31/66(slaves). Therefore I would suspect our problems using 2.5 results from some specialities, maybe combination of 2.5 and our svn repository version have some incompatibility that was fixed on the way to 2.5.4. So I think this case can be closed. 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] [subversion-plugin] (JENKINS-27137) Connection Aborted since 2.5 on Win64
Title: Message Title Tim-Christian Bloss closed an issue as Fixed Hi, problem seems to be solved some way between 2.5 and 2.5.4 , though I can't determine what exactly did solve this. Maybe some other plugins which got updated in the meantime had side effects, but that can't be investigated anymore. After all this issue is no longer of any relevance to us. Thank you for having observed it! Best regards Jenkins / JENKINS-27137 Connection Aborted since 2.5 on Win64 Change By: Tim-Christian Bloss Status: Open Closed Resolution: Fixed 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
[JIRA] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Title: Message Title Tim-Christian Bloss commented on JENKINS-26545 Re: Persist build(s) log(s) in MySQL (or similar) Hi, maybe I'm not fully aware of the structure builds are stored in, but I think can understand a little bit what's the intention to store builds including build log in databases. For me it looks like Jenkins reads jobs (jobs/*/config.xml) as well as some parts of the builds of each job everytime the Jenkins master gets started. Same goes for file system based config-history. At least our splitted file system shows such activity every time the Jenkins master gets started (splitting listed later on). From what I see on our file systems, each build of most of our jobs jobs contains something like "build.xml" "log" "revision.txt" "InjectedEnvVars.txt" "changelog.xml" Maybe build/log doesn't get read permanently, but I would suspect the build.xml might contain valuable information, possibly even the txt files.. We splitted jenkins to different disks to hunt down some massive performance issues we ran into, namely /dev/sdb1 30G 1,2G 27G 5% /opt/jenkins /dev/sdg1 40G 7,0G 31G 19% /opt/jenkins/jenkins_jobs_builds ---> defined using tmpfs 4,0G 732K 4,0G 1% /opt/jenkins/temp tmpfs 4,0G 0 4,0G 0% /opt/jenkins/fingerprints /dev/sdd1 197G 6,0G 181G 4% /opt/jenkins/jobs /dev/sdc1 50G 4,2G 43G 10% /opt/jenkins/config-history When starting Jenkins master, disk activity "breaks any scale" on our monitoring on disks containing /opt/jenkins/jenkins_jobs_builds /opt/jenkins/jobs /opt/jenkins/config-history We've already cut down job history to only two builds in history for each job, otherwise we sometimes got startup times far beyond half an hour (even more than one hour as we were running Jenkins master on Windows previously). In all maven builds we disabled fingerprinting as it became possible to do so, as we needed to flush the tmpfs /opt/jenkins/fingerprints nearly once per minute before. Maybe we're an example of a company excessively using jenkins or simply "building too large projects too often" as some might think. Regarding our experiences, it would really be useful to store as much data as possible in some database, limiting data reads to just the used fields (maybe who started a build and when it happened, what were the test results and so on) instead of reading build.xml for more than 200 maven modules per single build run per job. Also regarding portability for test systems (on site integration testing before upgrading production systems) as well as high availability it would be easier to store configuration and job data in a (replicated) database rather than using a file
[JIRA] [subversion-plugin] (JENKINS-27137) Connection Aborted since 2.5 on Win64
Title: Message Title Tim-Christian Bloss commented on JENKINS-27137 Re: Connection Aborted since 2.5 on Win64 We'll evaluate 2.5.4 next week (2015/11/16+) within our scheduled maintenance, running our system integration tests to verify stability. We'll also test 2.5 as an intermedia upgrade step, so we can see if this error still occurs on win64. That's just to verify if it's an issue regarding our win64 setups (2008r2) or something fixed between 2.5 and 2.5.4, in case 2.5.4 works flawlessy as I hope. Best regards 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] [subversion-plugin] (JENKINS-27137) Connection Aborted since 2.5 on Win64
Title: Message Title Tim-Christian Bloss commented on JENKINS-27137 Re: Connection Aborted since 2.5 on Win64 Thanks for the hint to the link (didn't see it), but I think our problems were different, as they were completely gone after downgrading from 2.5 to 2.4.5 I'll try to test out 2.5 next week to dig into this again, but currently it's not possible for me at the moment to do so. Best regards 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] [subversion-plugin] (JENKINS-27137) Connection Aborted since 2.5 on Win64
Title: Message Title Tim-Christian Bloss commented on JENKINS-27137 Re: Connection Aborted since 2.5 on Win64 Hi, currently we're staying at 2.4.5 without any issues using jenkins 1.596.3 / Debian 8 / Oracle JRE 1.8.0_51 (x86_64). With regards to current work load, I hope I can try to reproduce this issue between 2015/11/16 and 2015/11/28. When I'm done I'll report back in either case, including all information I can gather in case this error happens again. Best regards 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] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Tim-Christian Bloss commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves Same issue here. We have one Linux master running multiple slaves, some windows, some Linux. Linux slaves (VMWare VM) get a revert to snapshot using vmware plugin, which is not possible for windows slaves in our current environment. To handle hanging processes and locked files, we disconnect each windows slave after 1 single build, shutdown and power on the vm. Our problem are ever growing workspace folders, allocating far more than 80gig of disk space within about two weeks, as the async cleanup can not run and remove old workspaces due to premature disconnect and termination of the java vm. In our case the workspace cleanup plugin can rename old workspaces successfully (* -> *ws-cleanup[1234567890]+) , but does not delete those old folders after successfully reconnecting the windows slaves. We get no errors logged using ws-cleanup plugin version 0.28 in our build logs. 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] [core] (JENKINS-29954) views lost due to error parsing config.xml after copying jenkins to another system
Title: Message Title Tim-Christian Bloss created an issue Jenkins / JENKINS-29954 views lost due to error parsing config.xml after copying jenkins to another system Issue Type: Bug Assignee: Peter Hayes Components: core, dashboard-view-plugin, nested-view-plugin, sectioned-view-plugin Created: 14/Aug/15 12:04 PM Environment: Debian GNU/Linux 8 (amd64) OpenJDK 8 (level 8u51) and/or Oracle JRE 8u51 Tomcat 8 Jenkins LTS 1.596.3 SectionedViewPlugin 1.18 NestedViewPlugin 1.14 DashboardView 2.9.4 ViewJobFilters 1.26 LANG=de_DE.UTF-8 Labels: dashboard nested sectioned-view view views xml robustness exception error xstream config.xml config Priority: Critical Reporter: Tim-Christian Bloss We tried to create a pre production instance of jenkins on another system. The system was a cloned vmware vm. At this vanilla state jenkins could be started (at least 3-4 times) without a glitch and everything was displayed as expected. Later we rsync'ed every file to reflect the actual state of the production system using the following bash commands:
[JIRA] [nested-view-plugin] (JENKINS-29766) views not displayed - NullPointerException on SectionedView.getItems within NestedView
Title: Message Title Tim-Christian Bloss created an issue Jenkins / JENKINS-29766 views not displayed - NullPointerException on SectionedView.getItems within NestedView Issue Type: Bug Assignee: Timothy Bingaman Components: nested-view-plugin, sectioned-view-plugin Created: 03/Aug/15 9:19 PM Environment: Debian GNU/Linux 8 (amd64) OpenJDK 8 (level 8u51) Tomcat 8 Jenkins LTS 1.596.3 SectionedViewPlugin 1.18 NestedViewPlugin 1.14 DashboardView 2.9.4 ViewJobFilters 1.26 LANG=de_DE.UTF-8 Labels: sectioned-view nullpointer exception view views config.xml xml nested Priority: Critical Reporter: Tim-Christian Bloss We tried to copy config (jobs and views) from production to test environment, but many views (SectionedView, ListView and NestedView) do not get listed for an unknown reason. Within one view [NestedView-SectionedView-ListViewSection] we got only one (empty) ListViewSection displayed when there should be six. Even on highest log levels we can't get any hint
[JIRA] [reverse-proxy-auth-plugin] (JENKINS-29330) nested groups not looked up
Title: Message Title Tim-Christian Bloss created an issue Jenkins / JENKINS-29330 nested groups not looked up Issue Type: Improvement Assignee: Oleg Nenashev Components: reverse-proxy-auth-plugin, role-strategy-plugin Created: 10/Jul/15 7:39 AM Environment: Debian GNU/Linux 8 / AMD64 LANG=de_DE.UTF-8 Apache Tomcat/7.0.54 Oracle JDK 1.8.0_45 / AMD64 -Duser.language=de -Duser.country=DE -Dfile.encoding=UTF-8 Jenkins LTS 1.596.3 Apache httpd 2.4 / mod_jk as frontend using kerberos authentication Windows 2008 R2 Domain user database in Active Directory Labels: auth authentication authorization ldap group Priority: Major Reporter: Tim-Christian Bloss We're using reverse-proxy-auth plugin for authentication and role-strategy-plugin for authorization. The users connect to apache httpd 2.4 which authenticates against Windows 2008 R2 active directory and passes user authentication to Tomcat/Jenkins. In Jenkins the reverse-proxy-auth-plugin accesses active directory
[JIRA] [reverse-proxy-auth-plugin] (JENKINS-29331) groups displayed as user in role-strategy-plugin screen assign roles
Title: Message Title Tim-Christian Bloss created an issue Jenkins / JENKINS-29331 groups displayed as user in role-strategy-plugin screen assign roles Issue Type: Improvement Assignee: Oleg Nenashev Components: reverse-proxy-auth-plugin, role-strategy-plugin Created: 10/Jul/15 7:47 AM Environment: Debian GNU/Linux 8 / AMD64 LANG=de_DE.UTF-8 Apache Tomcat/7.0.54 Oracle JDK 1.8.0_45 / AMD64 -Duser.language=de -Duser.country=DE -Dfile.encoding=UTF-8 Jenkins LTS 1.596.3 Apache httpd 2.4 / mod_jk as frontend using kerberos authentication Windows 2008 R2 Domain user database in Active Directory Priority: Minor Reporter: Tim-Christian Bloss We're using reverse-proxy-auth plugin for authentication and role-strategy-plugin for authorization. The users connect to apache httpd 2.4 which authenticates against Windows 2008 R2 active directory and passes user authentication to Tomcat/Jenkins. In Jenkins the reverse-proxy-auth-plugin accesses active directory using its LDAP configuration to lookup a users groups. We're using the role-strategy-plugin with active directory groups for authorization. If I'm right, the lookup of users and groups by role-strategy-plugin for displaying correctness of groups and users also gets handled using the ldap functionallity of reverse-proxy-auth-plugin,
[JIRA] [reverse-proxy-auth-plugin] (JENKINS-29330) nested groups not looked up
Title: Message Title Tim-Christian Bloss updated an issue Jenkins / JENKINS-29330 nested groups not looked up Change By: Tim-Christian Bloss Issue Type: Improvement Bug 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] [envinject-plugin] (JENKINS-27665) NPE after updating EnvInject Plugin from 1.90 to 1.91.1
Title: Message Title Tim-Christian Bloss commented on JENKINS-27665 Re: NPE after updating EnvInject Plugin from 1.90 to 1.91.1 Same here. Debian GNU/Linux 8 / AMD64 LANG=de_DE.UTF-8 Apache Tomcat/7.0.54 Oracle JDK 1.8.0_45 / AMD64 -Duser.language=de -Duser.country=DE -Dfile.encoding=UTF-8 Jenkins LTS 1.596.3 EnvInject Plugin 1.91.3 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] [thinBackup] (JENKINS-20395) Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server
Title: Message Title Tim-Christian Bloss commented on JENKINS-20395 Re: Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server That error happend to us some time ago, but not recently, Last time this occured we were using Oracle JRE 1.8.0_25 as it seems.. ls -l /opt/jenkins_backup insgesamt 229336 rw-r r - 1 tomcat tomcat 204881920 Feb 14 12:13 BACKUPSET_2015-02-13_12-00_.zip rw-r r - 1 tomcat tomcat 4915558 Jun 30 12:01 BACKUPSET_2015-06-29_12-00_.zip rw-r r - 1 tomcat tomcat 4952374 Jul 1 12:01 BACKUPSET_2015-06-30_12-00_.zip rw-r r - 1 tomcat tomcat 4990141 Jul 2 12:02 BACKUPSET_2015-07-01_12-00_.zip rw-r r - 1 tomcat tomcat 5002866 Jul 3 12:02 BACKUPSET_2015-07-02_12-00_.zip rw-r r - 1 tomcat tomcat 5025237 Jul 5 17:33 BACKUPSET_2015-07-03_12-00_.zip rw-r r - 1 tomcat tomcat 5027377 Jul 6 12:02 BACKUPSET_2015-07-05_12-00_.zip drwxr-xr-x 5 tomcat tomcat 4096 Jul 6 12:01 FULL-2015-07-06_12-00 for I in $(ls /opt/jenkins_backup/*.zip); do unzip -q -t $I; done [/opt/jenkins_backup/BACKUPSET_2015-02-13_12-00_.zip] End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of /opt/jenkins_backup/BACKUPSET_2015-02-13_12-00_.zip or /opt/jenkins_backup/BACKUPSET_2015-02-13_12-00_.zip.zip, and cannot find /opt/jenkins_backup/BACKUPSET_2015-02-13_12-00_.zip.ZIP, period. No errors detected in compressed data of /opt/jenkins_backup/BACKUPSET_2015-06-29_12-00_.zip. No errors detected in compressed data of /opt/jenkins_backup/BACKUPSET_2015-06-30_12-00_.zip. No errors detected in compressed data of /opt/jenkins_backup/BACKUPSET_2015-07-01_12-00_.zip. No errors detected in compressed data of
[JIRA] [cluster-stats-plugin] (JENKINS-29246) ConcurrentModificationException on serialization
Title: Message Title Tim-Christian Bloss created an issue Jenkins / JENKINS-29246 ConcurrentModificationException on serialization Issue Type: Bug Assignee: Unassigned Components: cluster-stats-plugin Created: 06/Jul/15 1:40 PM Environment: Debian GNU/Linux 8 / AMD64 LANG=de_DE.UTF-8 Apache Tomcat/7.0.54 Oracle JDK 1.8.0_45 / AMD64 -Duser.language=de -Duser.country=DE -Dfile.encoding=UTF-8 Jenkins LTS 1.596.3 cluster-stats-plugin 0.4.6 Labels: exception Priority: Minor Reporter: Tim-Christian Bloss Not fully thread safe as it seems. Not nice, but not yet causing severe problems. Jul 06, 2015 11:03:40 AM hudson.model.listeners.RunListener report WARNUNG: RunListener failed java.lang.RuntimeException: Failed to serialize org.zeroturnaround.stats.ClusterStatisticsPlugin#statsData for class org.zeroturnaround.stats.ClusterStatisticsPlugin at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:214) at
[JIRA] [email-ext-plugin] (JENKINS-29249) NullPointerException when calling addRecipients
Title: Message Title Tim-Christian Bloss created an issue Jenkins / JENKINS-29249 NullPointerException when calling addRecipients Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 06/Jul/15 1:46 PM Environment: Debian GNU/Linux 8 / AMD64 LANG=de_DE.UTF-8 Apache Tomcat/7.0.54 Oracle JDK 1.8.0_45 / AMD64 -Duser.language=de -Duser.country=DE -Dfile.encoding=UTF-8 Jenkins LTS 1.596.3 email-ext-plugin 2.40.5 Labels: exception Priority: Minor Reporter: Tim-Christian Bloss Jul 05, 2015 8:08:05 PM hudson.plugins.emailext.ExtendedEmailPublisher sendMail WARNUNG: Could not send email. java.lang.NullPointerException at hudson.plugins.emailext.plugins.recipients.RequesterRecipientProvider.addRecipients(RequesterRecipientProvider.java:46) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:590) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:331) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:322) at
[JIRA] [nested-view-plugin] (JENKINS-28923) Nested View causes StackOverflowError
Title: Message Title Tim-Christian Bloss updated an issue Jenkins / JENKINS-28923 Nested View causes StackOverflowError Change By: Tim-Christian Bloss Attachment: jenkins_stacktrace.txt Attachment: 2015-06-1616_22_22-01.Entwicklung[Jenkins].png Attachment: 2015-06-1616_21_43-01.Entwicklung[Jenkins].png 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] [subversion-plugin] (JENKINS-27137) Connection Aborted since 2.5 on Win64
Tim-Christian Bloss created JENKINS-27137 Connection Aborted since 2.5 on Win64 Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 26/Feb/15 12:34 AM Description: Since upgrade from 2.3 to 2.5 builds on windows slaves crash during (or shortly after) svn checkout. Messages are mostly about connection abort between master and slave. The problem arises when upgrading subversion plugin to 2.5. The problem never occured using version 2.3 (used for nearly a year). The problem did not (yet) arise using version 2.4.5 either (used one day so far). Linux slaves (workspace on tmpfs, same os/jre/svn as master) are not affected by this problem. The problem (when summing up different stack traces as shown below) seems to be reproducible by 100%. CASE 1 : After svn check out , slave dit not get shut down nor disconnected at network layer (remote desktop active all the time!) ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:295) at hudson.remoting.Channel.terminate(Channel.java:814) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) at ..remote call to WindowsJev2(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.Request.call(Request.java:171) at hudson.remoting.Channel.call(Channel.java:751) at hudson.FilePath.act(FilePath.java:969) at hudson.FilePath.act(FilePath.java:958) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:959) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1745) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:189) at java.net.SocketInputStream.read(SocketInputStream.java:121) at java.io.FilterInputStream.read(FilterInputStream.java:133) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read(BufferedInputStream.java:265) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) CASE 2 : After svn check out , despite message slave did NOT go down nor got disconnected on network layer! (remote desktop active all the time!) ERROR: POMs konnten nicht geparst werden java.io.IOException: remote file operation failed: d:\jws\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.0.4\hudson1843729123396716916.sh at hudson.remoting.Channel@69e40890:WindowsHMJev4: hudson.remoting.ChannelClosedException: channel is already closed at hudson.FilePath.act(FilePath.java:976) at hudson.FilePath.act(FilePath.java:958) at hudson.FilePath.delete(FilePath.java:1412) at hudson.tools.AbstractCommandInstaller.performInstallation(AbstractCommandInstaller.java:82) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:205) at hudson.tasks.Maven$MavenInstallation.forNode(Maven.java:609) at
[JIRA] [scripted-cloud-plugin] (JENKINS-26750) please implement limited builds feature
Tim-Christian Bloss created JENKINS-26750 please implement limited builds feature Issue Type: Improvement Assignee: Unassigned Components: scripted-cloud-plugin Created: 03/Feb/15 10:44 AM Description: We are using several very different build environments, which we revert to snapshot before starting a new build. From "vSphere Plugin", we know the features "shutdown and revert" and "disconnect after limited builds", which give us the flexibility we need. We would really appreciate such a feature to be available for scripted-cloud-plugin, as triggering a shutdown/revert using a triggered shutdown-the-system build after regular build completes may be superseeded by another build job that gets triggered before the shutdown job gets triggered/started, leaving a dirty build environment behind. Environment: Jenkins 1.565.3 , Linux Master Project: Jenkins Priority: Major Reporter: Tim-Christian Bloss This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Tim-Christian Bloss commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. Interesting aspect. Java 7 seems to have some issues since those SSL-Updates of last days/weeks. In some cases regarding SNI and SSL, especially when combined, Java 8 may be an option to try for master and slaves. Another problem may be Windows updates, as some parts like smb/ad protocols get updated now and then and therefore some apache httpd modules might need an update for proper authentication/authorization against security realm/domain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-14541) Option to checkout with --quiet (or equivalent)
Tim-Christian Bloss commented on JENKINS-14541 Option to checkout with --quiet (or equivalent) Same here. svn checkout logs fill between 50% and 90% of our build logs. Would be great if SVN-CheckOut could be quiet by default, only showing messages if starting/finishing checkout (status info) an error occured: print everything a warning occured: print warning a new option like "printAllSvnMessages" is set to true This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logaction] (JENKINS-8233) Job restarted with Centralized Job(Re)Action plugin don't keep parameters from the original build
Tim-Christian Bloss commented on JENKINS-8233 Job restarted with Centralized Job(Re)Action plugin dont keep parameters from the original build The problem exists in "Centralized Job(Re)Action plugin" 1.2 and there's no release of a fixed version available/released yet. Even if "Naginator Plugin" may be a more modern/flexible plugin, which we're already using, the "Centralized Job(Re)Action plugin" has the advantage of being a "global" trigger, processing the log output of each and every job, while the "Naginator Plugin" requires individual configuration. Environment: Jenkins 1.565.3, Centralized Job(Re)Action plugin 1.2, Tomcat 7.0.54, JRE1.7.0_71, Debian GNU/Linux 7, amd64, de_DE.UTF-8 Besides this problem, the plugin works as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-tag] (JENKINS-25359) Give Option to prevent deletion of old svn tags
Tim-Christian Bloss created JENKINS-25359 Give Option to prevent deletion of old svn tags Issue Type: Bug Assignee: k2nakamura Components: svn-tag Created: 29/Oct/14 3:21 PM Description: When a build was successfull and there was already a matching svn tag, the previous tag gets deleted. That should not happen, as this massively breaks traceability of releases. When talking about a "tested, quality approved release 2.2" , nobody knows if "the old 2.2" or "the new 2.2" was working as specified in quality assurance, while the other did not. Therefore a global option to prevent removal of svn tags would be really appreciated. In case there a situations where deletion of old svn tags is desired, there could also a be job-based override option for this, but an option to prevent those tag deletions by accident really would help maintaining traceability of release versions. Environment: Jenkins 1.565.3 Tomcat 7.0.54, amd64 Oracle JRE 1.7.0u71, amd64 Debian GNU/Linux, amd64, de_DE.UTF-8 Project: Jenkins Priority: Critical Reporter: Tim-Christian Bloss This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [text-finder] (JENKINS-3612) Allow text-finder plugin to carry out multiple searches.
Tim-Christian Bloss commented on JENKINS-3612 Allow text-finder plugin to carry out multiple searches. This would also be very helpfull for our complex automated remote deployment tasks. Should be possible to trigger different behaviour based on console output: deployment successfull but application not working - unstable, developers have to fix this deployment failed - fail the build, admins have to track down 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] [plugin] (JENKINS-24862) Allow Textfinder to optionally change failed builds to unstable
Tim-Christian Bloss created JENKINS-24862 Allow Textfinder to optionally change failed builds to unstable Issue Type: Improvement Assignee: drlewis Components: plugin, text-finder Created: 25/Sep/14 8:22 AM Description: Background: We have many very complex automated deployment tasks which get started using "Send Files or execute commands over SSH", calling some bash shell scripts on one target system connecting to other systems (database, loadbalancer...). We use the "Editable Email Notification" to get informed about success and failulre of the builds/deployments. Our problem: We must use the option "Fail the build if an error occurs" for the SSH remote access, in order to catch up all errors. In certain condition, when exectly one text message (echo) gets printed when the build fails, we know for sure it is no deployment/admin failure but definately an application/development issue. If the message occurs during "successfull" builds, the developrs can get an automated email, informing them about the not successfully starting up application. If the message occurs during a build that "failed" due to some application startup issues, the developers do not get immediately informed about the issue, and the system administrators have to dig into the logs, just to find out deployment failed due to some regression. What would solve this for us: It would be very nice to have an additional option (separate checkbox, unchecked by default to retain current plugin behaviour) to change even a "failed" build to "unstable" if a specific text pattern occurs in the logs. Environment: Jenkins 1.554.3, Debian GNU/Linux 7, AMD64, Tomcat 7, Oracle JRE 7u67 Project: Jenkins Labels: plugin Priority: Major Reporter: Tim-Christian Bloss This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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] (JENKINS-24862) Allow Textfinder to optionally change failed builds to unstable
Tim-Christian Bloss updated JENKINS-24862 Allow Textfinder to optionally change failed builds to unstable Change By: Tim-Christian Bloss (25/Sep/14 8:28 AM) Description: Background:WehavemanyverycomplexautomateddeploymenttaskswhichgetstartedusingSendFilesorexecutecommandsoverSSH,callingsomebashshellscriptsononetargetsystemconnectingtoothersystems(database,loadbalancer...).WeusetheEditableEmailNotificationtogetinformedaboutsuccessand failulre failure ofthebuilds/deployments.Ourproblem:WemustusetheoptionFailthebuildifanerroroccursfortheSSHremoteaccess,inordertocatchupallerrors.Incertaincondition,whenexectlyonetextmessage(echo)getsprintedwhenthebuildfails,weknowforsureitisnodeployment/adminfailurebutdefinatelyanapplication/developmentissue.Ifthemessageoccursduringsuccessfullbuilds,thedeveloprscangetanautomatedemail,informingthemaboutthenotsuccessfullystartingupapplication.Ifthemessageoccursduringabuildthatfailedduetosomeapplicationstartupissues,thedevelopersdonotgetimmediatelyinformedabouttheissue,andthesystemadministratorshavetodigintothelogs,justtofindoutdeploymentfailedduetosomeregression.Whatwouldsolvethisforus:Itwouldbeverynicetohaveanadditionaloption(separatecheckbox,uncheckedbydefaulttoretaincurrentpluginbehaviour)tochangeevenafailedbuildtounstableifaspecifictextpatternoccursinthelogs. EDIT:Spellingcorrected This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-24863) Please add support for the text-finder plugin
Tim-Christian Bloss created JENKINS-24863 Please add support for the text-finder plugin Issue Type: Improvement Assignee: mdonohue Components: configurationslicing Created: 25/Sep/14 9:05 AM Description: Hi, would be nice if you could add support for the text-finder plugin. https://wiki.jenkins-ci.org/display/JENKINS/Text-finder+Plugin Would definately help us to modify our checks after builds, without using bash scripts (wrapping cat,grep,find,sed) as we do by now. Environment: all Project: Jenkins Priority: Minor Reporter: Tim-Christian Bloss This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Tim-Christian Bloss reopened JENKINS-18455 all modules of all maven projects are listed separately Hi, the problem seems to persist when using slicing to set JDK per maven project. When reconfiguring projects for new JDK versions, I see al modules of all projects listed. Environment: Debian 7.6 amd64 Oracle JRE7 1.7.0_60 Tomcat 7.0.54 Jenkins 1.554.3 Locale/Charset: de_DE.UTF-8 Change By: Tim-Christian Bloss (28/Aug/14 11:09 AM) Resolution: Fixed Status: Resolved 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] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Tim-Christian Bloss edited a comment on JENKINS-18455 all modules of all maven projects are listed separately Hi, the problem seems to persist when using slicing to set JDK per maven project. When reconfiguring projects for new JDK versions, I see al modules of all projects listed. Environment: Debian 7.6 amd64 Oracle JRE7 1.7.0_60 Tomcat 7.0.54 Jenkins 1.554.3 Locale/Charset: de_DE.UTF-8 EDIT 20140829@1310 : Configuration Sclicing Plugin 1.38.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] [gui] (JENKINS-23744) Using blanks in names that get parsed to URIs cause URISyntaxException
Tim-Christian Bloss updated JENKINS-23744 Using blanks in names that get parsed to URIs cause URISyntaxException Change By: Tim-Christian Bloss (27/Aug/14 10:29 AM) Environment: DebianGNU/Linux7.5(x64)OracleJRE1.7.0_60Tomcat7.0.54 ADDED2014/08/27:Jenkins1.532.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] [gui] (JENKINS-23744) Using blanks in names that get parsed to URIs cause URISyntaxException
Tim-Christian Bloss commented on JENKINS-23744 Using blanks in names that get parsed to URIs cause URISyntaxException Sorry, could only select "current version" from dropdown and forgot to mention correct version explicitly. Error occured using Jenkins 1.532.3 (LTS). environment: export LANG=de_DE.UTF-8 Java system.properties set by jsvc invocation: -Duser.language=de -Duser.country=DE -Dfile.encoding=UTF-8 The management/configuration pages said no warnings at all. And there were no errors or warnings visible in the browser while watching those pages which caused these messages. The messages only showed up in the log files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23742) slave complaining about log4j-configuration , namely FileNotFoundException referencing /logs/.catalina.log
Tim-Christian Bloss created JENKINS-23742 slave complaining about log4j-configuration , namely FileNotFoundException referencing /logs/.catalina.log Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: core, logging, maven Created: 10/Jul/14 12:47 PM Description: Tomcat has been configured to use log4j as logging-implementation, using tomcat/lib/log4j.xml relying on environment variables for path and file resolution We get the following StackTrace in the build logs of some of our Maven3 projects. This happens on Windows and Linux, regardless of release or snapshot build. We suspect this to be caused by the Tomcat configuration, forcing Tomcat to use log4j instead of Juli. The master seems to push its log4j.xml to the slave to provide log4j.xml as configuration media. The master's log4j.xml in tomcat/lib/log4j.xml is absolutely identical to the slave's log4j.xml in /tmp/jenkins-remoting88201907393997867/log4j.xml The (Linux-)slaves get reverted to a blank vmware-snapshot containing only the JRE 1.7.0_17 and afterwards powered on before the master connects. Therefore we're absolutely sure there never was any log4j.xml on the slaves before the master connects. log message containing StackTrace: maven3-agent.jar already up to date maven3-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date common $ /work/tools/hudson.model.JDK/lnx64ora7u51/bin/java -Dlog4j.debug -Djava.awt.headless=true -cp /work/maven3-agent.jar:/work/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /work/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.4 /work/slave.jar /work/maven3-interceptor.jar /work/maven3-interceptor-commons.jar 39496 ===JENKINS REMOTING CAPACITY===channel started log4j: Trying to find log4j.xml using context classloader sun.misc.Launcher$AppClassLoader@713c817. log4j: Trying to find log4j.xml using hudson.remoting.RemoteClassLoader@48bfba23 class loader. log4j: Using URL file:/tmp/jenkins-remoting88201907393997867/log4j.xml for automatic log4j configuration. log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator log4j: System property is :null log4j: Standard DocumentBuilderFactory search succeded. log4j: DocumentBuilderFactory is: com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl log4j: debug attribute= "null". log4j: Ignoring debug attribute. log4j: Threshold ="null". log4j: Level value for root is INFO. log4j: root level set to INFO log4j: Class name: org.apache.log4j.DailyRollingFileAppender log4j: Setting property file to /logs/.catalina.log. log4j: Setting property append to true. log4j: Setting property encoding to UTF-8. log4j: Setting property datePattern to .-MM-dd. log4j: Parsing layout of class: "org.apache.log4j.PatternLayout" log4j: Setting property conversionPattern to [%d %-5p %t %m%n]. log4j: setFile called: /logs/.catalina.log, true log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /logs/.catalina.log (Datei oder Verzeichnis nicht gefunden) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:221) at java.io.FileOutputStream.init(FileOutputStream.java:142) at org.apache.log4j.FileAppender.setFile(FileAppender.java:273) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:152) at org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:206) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247) at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:210) at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:140) at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:153) at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:415) at
[JIRA] [gui] (JENKINS-23744) Using blanks in names that get parsed to URIs cause URISyntaxException
Tim-Christian Bloss updated JENKINS-23744 Using blanks in names that get parsed to URIs cause URISyntaxException Change By: Tim-Christian Bloss (10/Jul/14 1:40 PM) Description: WegottheseexceptionsinourTomcatlog(Tomcathasbeenconfiguredtouselog4jaslogging-implementation)wheneveraURIgotbuildbyparsinguser-namedelementsofJenkins(view,nestedview,jobname,dashboardviewnames).TheexceptionoccursforexamplewhenclickingthearrownexttoajobtoopenthecntextMenuwheneverthenameofthecurrentviewcontainsablank.Maybethishappensalsoinothersituations,butexactlythiscausedourlogstogettotallyfloodedbysuchmessages. Intermediatesolution:Renameallviewsandjobssotheynolongercontainblanks. Jul03,20149:56:06AMhudson.ExpressionFactory2$JexlExpressionevaluateWARNUNG:Caughtexceptionevaluating:taskTags!=nullandattrs.contextMenu!=false?taskTags.add(href,icon,title,post==true,requiresConfirmation==true):nullin/jenkins/view/3.Anwendungen/view/LOC-TRUNK(SNAPSHOT)/job/prjxxx-tr/contextMenu.Reason:java.lang.IllegalArgumentException:BadURIfrom/jenkins/view/3.Anwendungen/view/LOC-TRUNK(SNAPSHOT)/job/prjxxx-tr/contextMenuvs./jenkins/view/3.Anwendungen/view/LOC-TRUNK(SNAPSHOT)/job/prjxxx-tr/changesjava.lang.IllegalArgumentException:BadURIfrom/jenkins/view/3.Anwendungen/view/LOC-TRUNK(SNAPSHOT)/job/prjxxx-tr/contextMenuvs./jenkins/view/3.Anwendungen/view/LOC-TRUNK(SNAPSHOT)/job/prjxxx-tr/changes atjenkins.model.ModelObjectWithContextMenu$MenuItem.withUrl(ModelObjectWithContextMenu.java:279) atjenkins.model.ModelObjectWithContextMenu$MenuItem.init(ModelObjectWithContextMenu.java:269) atjenkins.model.ModelObjectWithContextMenu$ContextMenu.add(ModelObjectWithContextMenu.java:123) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) atorg.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) atorg.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) atorg.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) atorg.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) atorg.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) atorg.apache.commons.jexl.parser.ASTTernaryNode.value(ASTTernaryNode.java:41) atorg.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) atorg.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56) atorg.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) athudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) atorg.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) atorg.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) atorg.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) atorg.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) atorg.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
[JIRA] [gui] (JENKINS-23744) Using blanks in names that get parsed to URIs cause URISyntaxException
Tim-Christian Bloss created JENKINS-23744 Using blanks in names that get parsed to URIs cause URISyntaxException Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: gui, nested-view Created: 10/Jul/14 1:39 PM Description: We got these exceptions in our Tomcat log (Tomcat has been configured to use log4j as logging-implementation) whenever a URI got build by parsing user-named elements of Jenkins (view, nested view, jobname, dashboard view names). The exception occurs for example when clicking the arrow next to a job to open the cntextMenu whenever the name of the current view contains a blank. May be this happens also in other situations, but exactly this caused our logs to get totally flooded by such messages. Jul 03, 2014 9:56:06 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNUNG: Caught exception evaluating: taskTags!=null and attrs.contextMenu!='false' ? taskTags.add(href, icon, title, post == 'true', requiresConfirmation == 'true') : null in /jenkins/view/3. Anwendungen/view/LOC - TRUNK (SNAPSHOT)/job/prjxxx-tr/contextMenu. Reason: java.lang.IllegalArgumentException: Bad URI from /jenkins/view/3. Anwendungen/view/LOC - TRUNK (SNAPSHOT)/job/prjxxx-tr/contextMenu vs. /jenkins/view/3. Anwendungen/view/LOC - TRUNK (SNAPSHOT)/job/prjxxx-tr/changes java.lang.IllegalArgumentException: Bad URI from /jenkins/view/3. Anwendungen/view/LOC - TRUNK (SNAPSHOT)/job/prjxxx-tr/contextMenu vs. /jenkins/view/3. Anwendungen/view/LOC - TRUNK (SNAPSHOT)/job/prjxxx-tr/changes at jenkins.model.ModelObjectWithContextMenu$MenuItem.withUrl(ModelObjectWithContextMenu.java:279) at jenkins.model.ModelObjectWithContextMenu$MenuItem.init(ModelObjectWithContextMenu.java:269) at jenkins.model.ModelObjectWithContextMenu$ContextMenu.add(ModelObjectWithContextMenu.java:123) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTTernaryNode.value(ASTTernaryNode.java:41) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
Tim-Christian Bloss edited a comment on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Problem also occurring on Jenkins LTS 1.532.3 SVN-Tag-Plugin 1.16 SVN-Plugin 2.3 Debian GNU/Linux 7 Tomcat 7.0.52 JRE 1.7.0_55 We'd need that new version for 1.532.3, too This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-tag] (JENKINS-14133) build marked as failure by subversion tagging plugin still succeeds
Tim-Christian Bloss edited a comment on JENKINS-14133 build marked as failure by subversion tagging plugin still succeeds Problem also occurring on Jenkins LTS 1.532.3 SVN-Tag-Plugin 1.16 SVN-Plugin 2.3 Debian GNU/Linux 7 Tomcat 7.0.52 JRE 1.7.0_55 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-tag] (JENKINS-14133) build marked as failure by subversion tagging plugin still succeeds
Tim-Christian Bloss commented on JENKINS-14133 build marked as failure by subversion tagging plugin still succeeds Problem also occurring on Jenkins LTS 1.532.3 SVN-Plugin 2.3 Debian GNU/Linux 7 Tomcat 7.0.52 JRE 1.7.0_55 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
Tim-Christian Bloss commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Problem also occurring on Jenkins LTS 1.532.3 SVN-Plugin 2.3 Debian GNU/Linux 7 Tomcat 7.0.52 JRE 1.7.0_55 We'd need that new version for 1.532.3, too This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-21235) Artifactory plugin is configured to run post-build, but actually runs pre-Post-Steps
Tim-Christian Bloss commented on JENKINS-21235 Artifactory plugin is configured to run post-build, but actually runs pre-Post-Steps Same here: Jenkins LTS 1.532.3, Artifactory Plugin 2.2.1, Debian GNU/Linux 7, JRE1.7.0_55 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
