[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Smouch Smouch commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Yep - more nonsense from SVNKit and the crappy subversion plugin. Yet another reason to simply remove the subversion plugin from Jenkins and let configuration set the path to svn binary. 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-36990) Jenkins API conitnues to make use of "Hudson" namespace
Title: Message Title Smouch Smouch created an issue Jenkins / JENKINS-36990 Jenkins API conitnues to make use of "Hudson" namespace Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/27 1:03 PM Environment: ANY Priority: Minor Reporter: Smouch Smouch Understanding how to use the Jenkins API is made especially complex by the fact that much of the useful functionality is only available within the "Hudson" namespace - or at least this is how the documentation appears to present it. This is just plain dumb. It is totally unclear under what circumstances a developer should look in "Hudson" or in "Jenkins" to find the API of interest. As a (very) experienced software developer I am at a complete loss as to how to script what - to my initial impression - should be a trivial script to discover the "culprits" of a build break. Add Comment
[JIRA] (JENKINS-36844) Regex match fails - "Mentioned somewhere in commit message"
Title: Message Title
Smouch Smouch edited a comment on JENKINS-36844
Re: Regex match fails - "Mentioned somewhere in commit message"
I have finally managed to get some additional log information out of this plugin I added a few lines of logging within MentionedInCommitStrategy.java as follows:{quote}this._logger.log(Level.FINE,"Message text BEGIN:");this._logger.log(Level.FINE,msg);this._logger.log(Level.FINE,":Message text END");this._logger.log(Level.FINE,"JiraPrefix BEGIN:");this._logger.log(Level.FINE,validJiraPrefix);this._logger.log(Level.FINE,":JiraPrefix END");{quote}Trying to understand why the regex match string search would failHere is the resulting log message for a single test issue:{quote}Jul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategyMessage text BEGIN:Jul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategyJira key: EXITEVODEV-1309 Comments: Test Jira updaterJul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategy:Message text ENDJul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategyJiraPrefix BEGIN:Jul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategyEXITEVODEVJul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategy:JiraPrefix END{quote}So, there seems to be some kind of fundamental issue with the way the regex matcher string search is being used. Clearly the message text contains the regex being searched for, yet the matcher search is failing.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36844) Regex match fails - "Mentioned somewhere in commit message"
Title: Message Title Smouch Smouch commented on JENKINS-36844 Re: Regex match fails - "Mentioned somewhere in commit message" I have finally managed to get some additional log information out of this plugin I added a few lines of logging within MentionedInCommitStrategy.java as follows: this._logger.log(Level.FINE,"Message text BEGIN:"); this._logger.log(Level.FINE,msg); this._logger.log(Level.FINE,":Message text END"); this._logger.log(Level.FINE,"JiraPrefix BEGIN:"); this._logger.log(Level.FINE,validJiraPrefix); this._logger.log(Level.FINE,":JiraPrefix END"); Trying to understand why the regex match would fail Here is the resulting log message for a single test issue: Jul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategy Message text BEGIN: Jul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategy Jira key: EXITEVODEV-1309 Comments: Test Jira updater Jul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategy :Message text END Jul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategy JiraPrefix BEGIN: Jul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategy EXITEVODEV Jul 26, 2016 10:53:00 AM FINE org.jenkinsci.plugins.jiraext.view.MentionedInCommitStrategy :JiraPrefix END So, there seems to be some kind of fundamental issue with the way the regex matcher is being used. Clearly the message text contains the regex being searched for, yet the matcher is failing. Add Comment
[JIRA] (JENKINS-36844) Regex match fails - "Mentioned somewhere in commit message"
Title: Message Title Smouch Smouch created an issue Jenkins / JENKINS-36844 Regex match fails - "Mentioned somewhere in commit message" Issue Type: Bug Assignee: Dan Alvizu Components: jira-ext-plugin Created: 2016/Jul/21 10:40 AM Environment: System Information: awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-1.b14.el7_2.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-1.b14.el7_2.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-1.b14.el7_2.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_91-b14 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_91 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.91-b14 JENKINS_HOME /var/lib/jenkins jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/dyninst:/usr/lib64/mysql:/usr/lib64/iscsi jnidispatch.path /tmp/jna--1712433994/jna2497847408718895242.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.10.0-327.22.2.el7.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path
[JIRA] [subversion-plugin] (JENKINS-28251) Subversion plugin consistent source of problems - allow native subversion client
Title: Message Title Smouch Smouch created an issue Jenkins / JENKINS-28251 Subversion plugin consistent source of problems - allow native subversion client Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 06/May/15 8:02 AM Priority: Critical Reporter: Smouch Smouch As can be clearly seen by the huge number of jira bug reports, forum questions, and plug-in wiki comments, the subversion plug-in is a failed implementation. The reason for this is quite simply that it is not possible to rely upon svnkit (TMate software) to maintain timely compatibility with subversion (Apache). Incompatibilities across default Jenkins svnkit version and host machine version cause confusion and error. Availability of additional plug-in (not default bundled version) is equally confusing. Proposed solution is to allow Jenkins to to use the host (master and slave) machine subversion client.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Smouch Smouch commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Does this: Version 2.5 (Jan 2, 2015) Replace custom svnkit library in exchange for using the default binaries. issue #18935 Upgrade to svn 1.8. issue #25241 Upgrade trilead-ssh. mean that there is a way to use the hosts version of subversion instead of the Jenkins built-in (plug-in whatever) version ? I find the whole topic of subversion support within Jenkins quite confusing. I don't understand why Jenkins would ever ship with a plug-in installed by default in such a way that's it's not really a plug-in. I also don't understand why there is a separate plug-in that can be a different version from the one shipped by default. I also don't understand why Jenkins would have a subversion plug-in at all. Jenkins is a front end to cron, and of course needs to display results. That there are so many - some conflicting - plug-ins may be considered a strength, but it also means there are simply too many options for failure. Jenkins should be should be able to communicate with anything, but not require a "plug-in" or built-in functionality to reproduce (usually incorrectly) or mimic that behavior. 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-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch updated JENKINS-26866 jenkins java.io.ioexception remote file operation failed Change By: Smouch Smouch (17/Feb/15 8:24 AM) Environment: Jenkins versioniswhateverthelatestversionisasof09 ver . FEB 1 . 2015 598Furtherenvironmentdetailslistedbelow. 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-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch commented on JENKINS-26866 jenkins java.io.ioexception remote file operation failed Hello, Thanks again. I am back from holiday. Here is the version information: Jenkins ver. 1.598 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-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch commented on JENKINS-26866 jenkins java.io.ioexception remote file operation failed Thanks Daniel. Sorry, I am doing my best to get this resolved, because I have left our build system in an unknown state - even though the jobs are all running successfully - while I am away on holiday, during a fairly important milestone for our project. Needless to say, for any conscientious person, that makes me feel ill. Anyway, apparently I haven't managed to provide the Jenkins version. My initial installation of Jenkins on this server was via the download link for Fedora on the Jenkins site here: http://pkg.jenkins-ci.org/redhat/ Then I have updated via the web interface to the running Master server. I am fairly confident that means I am running 1.598. Please tell me how I check. 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-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch edited a comment on JENKINS-26866 jenkins java.io.ioexception remote file operation failed Please note: I am on holiday and have no access to this server other than by an e-mail chain with a colleague. Please forgive me if this takes some back and forth to get the necessary info. Jenkins master configuration # awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_75-mockbuild_2015_01_21_08_43-b00 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_75 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.75-b04 JENKINS_HOME /var/lib/jenkins jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna2593038690531263893.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.18.5-101.fc20.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/classes sun.boot.library.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone Europe/Berlin Environment Variables Name ↓ Value HOME /var/lib/jenkins LANG en_US.UTF-8 LOGNAME jenkins NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat PATH /sbin:/usr/sbin:/bin:/usr/bin PWD / SHELL /bin/bash SHLVL 2 USER jenkins XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt Plugins Name ↓ Version Enabled Pinned ant 1.2 false false antisamy-markup-formatter 1.1 false false build-monitor-plugin 1.6+build.138 true false credentials 1.18 true false cvs 2.11 false false email-ext 2.39 true false external-monitor-job 1.4 false false hudson-wsclean-plugin 1.0.4 true false javadoc 1.1 false false jenkinswalldisplay 0.6.27 true false junit 1.2-beta-4 true false ldap 1.8 false true mailer 1.15 true true matrix-auth 1.1 true false matrix-project 1.3 true false maven-plugin 2.7.1 false false multi-slave-config-plugin 1.0.0 true false pam-auth 1.1 false false
[JIRA] [core] (JENKINS-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch reopened JENKINS-26866 jenkins java.io.ioexception remote file operation failed Jenkins master configuration # awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_75-mockbuild_2015_01_21_08_43-b00 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_75 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.75-b04 JENKINS_HOME /var/lib/jenkins jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna2593038690531263893.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.18.5-101.fc20.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/classes sun.boot.library.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone Europe/Berlin Environment Variables Name ↓ Value HOME /var/lib/jenkins LANG en_US.UTF-8 LOGNAME jenkins NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat PATH /sbin:/usr/sbin:/bin:/usr/bin PWD / SHELL /bin/bash SHLVL 2 USER jenkins XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt Plugins Name ↓ Version Enabled Pinned ant 1.2 false false antisamy-markup-formatter 1.1 false false build-monitor-plugin 1.6+build.138 true false credentials 1.18 true false cvs 2.11 false false email-ext 2.39 true false external-monitor-job 1.4 false false hudson-wsclean-plugin 1.0.4 true false javadoc 1.1 false false jenkinswalldisplay 0.6.27 true false junit 1.2-beta-4 true false ldap 1.8 false true mailer 1.15 true true matrix-auth 1.1 true false matrix-project 1.3 true false maven-plugin 2.7.1 false false multi-slave-config-plugin 1.0.0 true false pam-auth 1.1 false false parameterized-trigger 2.25 true false scm-api 0.2 true false script-security 1.10 true false ssh-credentials 1.10 true false ssh-slaves 1.9 false false subversion 2.2 true true token-macro 1.10 true
[JIRA] [core] (JENKINS-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch created JENKINS-26866 jenkins java.io.ioexception remote file operation failed Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Feb/15 8:52 PM Description: Jenkins jobs assigned to java web-start slaves. The jobs in question were all working fine. Suddenly I get: jenkins java.io.ioexception remote file operation failed The call stack is essentially useless, and points to an exception handler in some Java class without indicating what exactly was attempted. Unfortunately this occurred just as I was preparing for a holiday. I do not have exact call stack now (I'm on a train). I fixed the problem by making the script explicitly perform a svn checkout/update rather than the normal method where one provides the URL and credentials in the fields for the "configure" page. That should be a good indication of where the issue lies. I really would like some kind of feedback on this issue, even though I will be away for a week. I would like to have the "normal" functionality and am willing to help investigate. Environment is: Fedora 21 x86_64 - all updates current as of 09.Feb.2015 Master and slaves are identical. I appreciate any help. Environment: Jenkins version is whatever the latest version is as of 09.FEB.2015 Project: Jenkins Labels: exception slave subversion Priority: Critical Reporter: Smouch Smouch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25883) email-ext plugin missing feature to suppress mail if downstream trigger skipped.
Smouch Smouch created JENKINS-25883 email-ext plugin missing feature to suppress mail if downstream trigger skipped. Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 03/Dec/14 10:57 AM Description: User wishes to suppress email even on success if downstream job is not triggered. User has multiple jobs which are used to conditionally trigger downstream jobs. These jobs report success if the downstream job is not triggered, because the parent job runs successfully. BUT, the notification e-mail for this job (on success) makes little sense or is undesirable unless the downstream job is triggered. The downstream job is highly parameterized, and quite generic. Triggering e-mails from it is not desirable. Feature request is to suppress success notification if downstream trigger is not satisfied Project: Jenkins Priority: Minor Reporter: Smouch Smouch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25883) email-ext plugin missing feature to suppress mail if downstream trigger skipped.
Smouch Smouch updated JENKINS-25883 email-ext plugin missing feature to suppress mail if downstream trigger skipped. Change By: Smouch Smouch (03/Dec/14 10:58 AM) Issue Type: Bug NewFeature 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.
