[JIRA] (JENKINS-10449) Excluded regions do not exclude commits from changelog
SCM/JIRA link daemon commented on JENKINS-10449 Excluded regions do not exclude commits from changelog Code changed in jenkins User: Brent Atkinson Path: src/main/java/hudson/scm/DirAwareSVNXMLLogHandler.java src/main/java/hudson/scm/SVNLogFilter.java src/main/java/hudson/scm/SubversionChangeLogBuilder.java src/main/java/hudson/scm/SubversionSCM.java http://jenkins-ci.org/commit/subversion-plugin/f71918fc997a38fab6b9133942b8ee68e70c999c Log: JENKINS-10449 Factored out svnlog filter to use with detection and changelogs 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-10449) Excluded regions do not exclude commits from changelog
SCM/JIRA link daemon commented on JENKINS-10449 Excluded regions do not exclude commits from changelog Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/scm/DefaultSVNLogFilter.java src/main/java/hudson/scm/DirAwareSVNXMLLogHandler.java src/main/java/hudson/scm/NullSVNLogFilter.java src/main/java/hudson/scm/SVNLogFilter.java src/main/java/hudson/scm/SubversionChangeLogBuilder.java src/main/java/hudson/scm/SubversionSCM.java src/main/resources/hudson/scm/SubversionSCM/config.jelly src/main/resources/hudson/scm/SubversionSCM/help-filterChangelog.html src/test/java/hudson/scm/DefaultSVNLogFilterTest.java src/test/java/hudson/scm/SubversionSCMTest.java src/test/java/hudson/scm/SubversionSCMUnitTest.java src/test/resources/hudson/scm/JENKINS-10449.zip http://jenkins-ci.org/commit/subversion-plugin/72be6320a61f79ec329e0f42b496dbac8fff1644 Log: Merge pull request #27 from batkinson/JENKINS-10449 Filter changelog based on the same inclusion/exclusion filters used to detect changes. [FIXED JENKINS-10449] Compare: https://github.com/jenkinsci/subversion-plugin/compare/ed8a1f80131f...72be6320a61f 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-10449) Excluded regions do not exclude commits from changelog
SCM/JIRA link daemon resolved JENKINS-10449 as Fixed Excluded regions do not exclude commits from changelog Change By: SCM/JIRA link daemon (29/Dec/12 9:20 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16210) CVS update not taking date
Michael Clarke closed JENKINS-16210 as Not A Defect CVS update not taking date This is by design. The '-r' option when not specifying HEAD or also specifying 'use head if not found' isn't compatible with the -D option. Change By: Michael Clarke (29/Dec/12 10:33 AM) Status: Open Closed Assignee: Michael Clarke Resolution: Not A Defect 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-14538) Separate "configure tools" page
domi commented on JENKINS-14538 Separate "configure tools" page nice change, but I would still prefer a separate page to global configuration is a mess on its own and dividing it into different pages would help 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-16222) Source code files for displaying warnings are empty in some cases
Markus Schneider
created JENKINS-16222
Source code files for displaying warnings are empty in some cases
Issue Type:
Bug
Affects Versions:
current
Assignee:
Ulli Hafner
Components:
warnings
Created:
29/Dec/12 10:54 AM
Description:
In some situations the source code files, displaying the warnings are empty.
Reason:
In some setups the default encoding was not set. This caused an exception in the class HealthAwareRecorder.java in
private void print(final FileOutputStream outputStream, final String message,
final Object... arguments) throws IOException {
IOUtils.write(String.format(message, arguments), outputStream, getDefaultEncoding());
}
The default encoding was an empty string and therefore the write function threw the IOException "Unknown Encoding".
This resulted in jumping out of the logging function to print the statement, that the path to the source file is wrong.
Fixed/Workaround by setting the Default Encoding in the configuration setting to "UTF-8"
Environment:
Jenkins: V1.493
Warnings-Plugin: V4.18
Static Analysis Utilities: V1.48
OS: Windows XP, Mac OS X
Project:
Jenkins
Priority:
Minor
Reporter:
Markus Schneider
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-15440) Emailing users at the end of a failed build very slow for big Jenkins instance using subversion
SCM/JIRA link daemon commented on JENKINS-15440 Emailing users at the end of a failed build very slow for big Jenkins instance using subversion Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/scm/SubversionMailAddressResolverImpl.java src/main/resources/hudson/scm/SubversionMailAddressResolverImpl/global.jelly http://jenkins-ci.org/commit/subversion-plugin/ad7882e97d026827a21d206e7731bfb61e746839 Log: Removed very old legacy svn repositories which where configured as defaults for mail address resolving, but are very unlikely to be of use to anyone[FIXED JENKINS-15440] Compare: https://github.com/jenkinsci/subversion-plugin/compare/1795b677b3fd...ad7882e97d02 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-15440) Emailing users at the end of a failed build very slow for big Jenkins instance using subversion
SCM/JIRA link daemon resolved JENKINS-15440 as Fixed Emailing users at the end of a failed build very slow for big Jenkins instance using subversion Change By: SCM/JIRA link daemon (29/Dec/12 11:41 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16223) Update periodicbackup-plugin dependency plexus-archiver to 2.2.
johno created JENKINS-16223 Update periodicbackup-plugin dependency plexus-archiver to 2.2. Issue Type: Patch Assignee: Unassigned Components: periodicbackup Created: 29/Dec/12 1:54 PM Description: Lots of bug fixes eg. http://jira.codehaus.org/browse/PLXCOMP-149 . Suspected cause for https://issues.jenkins-ci.org/browse/JENKINS-13617 . I built the plugin locally, works as per normal on my dev environment. Pull request @ https://github.com/jenkinsci/periodicbackup-plugin/pull/4 Project: Jenkins Priority: Major Reporter: johno 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space No need for jenkins.log at the moment. Heap dump looks okish, top instance count is java.lang.Class, I would recommend adding the switch -XX:+CMSClassUnloadingEnabled . Looking at the thread dump I see it OOMd in the PeriodicBackup ( https://wiki.jenkins-ci.org/display/JENKINS/PeriodicBackup+Plugin ) thread. Would you please try installing my snapshot with updated libraries ( https://issues.jenkins-ci.org/secure/attachment/23009/periodicbackup.hpi ) or disabling the plugin temporarily to see if it helps. "PeriodicBackup thread" prio=5 tid=3023 RUNNABLE at java.lang.OutOfMemoryError.(OutOfMemoryError.java:25) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) .. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno updated JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Change By: johno (29/Dec/12 3:17 PM) Attachment: periodicbackup.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space I have created a new build of the periodicbackup plugin ( https://issues.jenkins-ci.org/secure/attachment/23010/periodicbackup.hpi ) with the latest plexus-archiver, let me know if it helps! 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space No need for jenkins.log at the moment. Heap dump looks okish, top instance count is java.lang.Class, I would recommend adding the switch -XX:+CMSClassUnloadingEnabled . Looking at the thread dump I see it OOMd in the PeriodicBackup ( https://wiki.jenkins-ci.org/display/JENKINS/PeriodicBackup+Plugin ) thread. Would you please try installing my snapshot with updated libraries ( https://issues.jenkins-ci.org/secure/attachment/23010/periodicbackup.hpi ) or disabling the plugin temporarily to see if it helps. "PeriodicBackup thread" prio=5 tid=3023 RUNNABLE at java.lang.OutOfMemoryError.(OutOfMemoryError.java:25) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) .. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Updated periodbackup snapshot to include fix for http://jira.codehaus.org/browse/PLXCOMP-194 . 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
johno commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Would you be willing to create a small testcase project which demonstrates the bug? 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-16224) ProjectNamingStrategy/force existing: Does not prevent modifying existing job configurations
Harald Albers
created JENKINS-16224
ProjectNamingStrategy/force existing: Does not prevent modifying existing job configurations
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
29/Dec/12 5:49 PM
Description:
On Jenkins' main configuration, the Restrict project naming feature has a Pattern strategy with an force existing option. Checking this option should prevent users from updating an existing job configuration if the job name does not comply with the naming convention (unless they change the project name to a complying value as well).
This does not work as expected for existing jobs with non-compliant job names. After saving such a job configuration, an error page is displayed ('...' does not match the job name convention pattern ...). The changes are applied, though.
See https://github.com/jenkinsci/jenkins/commit/a2d9bac03da99d739ecf7ce0be9ba793b93d2c88 for a discussion with the feature's author about the meaning of the checkbox.
Project:
Jenkins
Priority:
Minor
Reporter:
Harald Albers
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-16225) JENKINS_URL, JOB_URL, BUILD_URL not set
Russell Bevers created JENKINS-16225 JENKINS_URL, JOB_URL, BUILD_URL not set Issue Type: Bug Affects Versions: current Assignee: Richard Sczepczenski Components: shell-script-scm Created: 29/Dec/12 6:53 PM Description: An Execute shell build step with simple command `env` shows that none of the *_URL environment variables are being imported to the shell. Scripts that access the Jenkins REST API rely on these vars to execute. E.g. output of `env` step on 1.495 BUILD_CAUSE_USERIDCAUSE=true HUDSON_SERVER_COOKIE=62a4ddfd88c783b78b6ae030cb9d0617 SHELL=/bin/bash TMPDIR=/var/folders/zv/6gwf54fj3c791gjxcddqp9t47c/T/ BUILD_TAG=jenkins-ios-app_master-17 WORKSPACE=/Users/Shared/Jenkins/Home/jobs/ios-app_master/workspace com.apple.java.jvmTask=CommandLine.java.java.java.java.java.java USER=jenkins __CF_USER_TEXT_ENCODING=0xEC:0:0 GIT_COMMIT=925e5ce56d7b6f0b67015131f8dd9d85e9c1168b JENKINS_HOME=/Users/Shared/Jenkins/Home PATH=/usr/bin:/bin:/usr/sbin:/sbin PWD=/Users/Shared/Jenkins/Home/jobs/ios-app_master/workspace JOB_NAME=ios-app_master JAVA_MAIN_CLASS_8793=Main com.apple.java.jvmMode=client BUILD_CAUSE=USERIDCAUSE BUILD_ID=2012-12-29_10-31-47 HOME=/Users/Shared/Jenkins SHLVL=1 GIT_BRANCH=origin/master JENKINS_SERVER_COOKIE=62a4ddfd88c783b78b6ae030cb9d0617 EXECUTOR_NUMBER=0 NODE_LABELS=master LOGNAME=jenkins HUDSON_HOME=/Users/Shared/Jenkins/Home NODE_NAME=master BUILD_NUMBER=17 HUDSON_COOKIE=fadc3c90-aca8-4b58-8850-5aded45d1348 JAVA_ARCH=x86_64 SECURITYSESSIONID=186d2 _=/usr/bin/env Environment: os.arch x86_64 os.name Mac OS X os.version 10.8.2 java.vendor Apple Inc. java.vendor.url http://www.apple.com/ java.version 1.6.0_37 Project: Jenkins Labels: jenkins Priority: Major Reporter: Russell Bevers 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-16226) Tools.jar is not included in classpath of maven project
studreamer studreamer created JENKINS-16226 Tools.jar is not included in classpath of maven project Issue Type: Bug Assignee: Unassigned Components: maven Created: 29/Dec/12 7:40 PM Description: The tools.jar is missing from the classpath which cause maven compile failure. I also tried to compile the same project in Eclipse, there is no compiling issue. I don't know where Jenkins only load the JARs from $JAVA_HOME/jre/lib into the classpath. The current wrong class path set by jenkins: sun.boot.class.path = /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/resources.jar /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/rt.jar /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/sunrsasign.jar /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/jsse.jar /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/jce.jar /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/charsets.jar /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/jfr.jar /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/classes Also please see the allsetting output in one build: Started by user anonymous Building in workspace /var/lib/jenkins/workspace/Google Test Updating https://192.168.1.7/svn/seleniumCook/SeleniumCook to revision '2012-12-30T03:27:36.988 +0800' At revision 11 no change for https://192.168.1.7/svn/seleniumCook/SeleniumCook since the previous build Starting xvnc [Google Test] $ vncserver :13 New 'Ubuntu1210:13 (jenkins)' desktop is Ubuntu1210:13 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/Ubuntu1210:13.log Parsing POMs [Google Test] $ /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/bin/java -XshowSettings -cp /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/usr/share/maven/boot/plexus-classworlds-2.x.jar org.jvnet.hudson.maven3.agent.Maven3Main /usr/share/maven /var/cache/jenkins/war/WEB-INF/lib/remoting-2.19.jar /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 43659 VM settings: Max. Heap Size (Estimated): 121.81M Ergonomics Machine Class: client Using VM: Java HotSpot(TM) Client VM Property settings: awt.toolkit = sun.awt.X11.XToolkit file.encoding = UTF-8 file.encoding.pkg = sun.io file.separator = / java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment java.awt.printerjob = sun.print.PSPrinterJob java.class.path = /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar /usr/share/maven/boot/plexus-classworlds-2.x.jar java.class.version = 51.0 java.endorsed.dirs = /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/endorsed java.ext.dirs = /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/ext /usr/java/packages/lib/ext java.home = /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre java.io.tmpdir = /tmp java.library.path = /usr/java/packages/lib/i386 /lib /usr/lib java.runtime.name = Java(TM) SE Runtime Environment java.runtime.version = 1.7.0_09-b05 java.specification.name = Java Platform API Specification java.specification.vendor = Oracle Corporation java.specification.version = 1.7 java.vendor = Oracle Corporation java.vendor.url = "" href="http://java.oracle.com/">http://java.oracle.com/ java.vendor.url.bug = http://bugreport.sun.com/bugreport/ java.version = 1.7.0_09 java.vm.info = mixed mode java.vm.name = Java HotSpot(TM) Client 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 = 23.5-b02 line.separator = \n os.arch = i386 os.name = Linux os.version = 3.5.0-21-generic path.separator = : sun.arch.data.model = 32 sun.boot.class.path = /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/resources.jar /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre/lib/rt.jar /var/
[JIRA] (JENKINS-16226) Tools.jar is not included in classpath of maven project
studreamer studreamer started work on JENKINS-16226 Tools.jar is not included in classpath of maven project Change By: studreamer studreamer (29/Dec/12 7:42 PM) Status: Open In Progress 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-16226) Tools.jar is not included in classpath of maven project
kutzi resolved JENKINS-16226 as Not A Defect Tools.jar is not included in classpath of maven project Change By: kutzi (29/Dec/12 9:10 PM) Status: In Progress Resolved Resolution: Not A Defect 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-16226) Tools.jar is not included in classpath of maven project
kutzi commented on JENKINS-16226 Tools.jar is not included in classpath of maven project According to your output JAVA_HOME seems to point to an JRE instead of a JDK: java.home = /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK/jre This seems more like a configuration problem than a bug. Please use the users mailing list for such issues. 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-16219) Version 1.77 injects all *environment* variables into ANT command line (-D)
thetaphi commented on JENKINS-16219 Version 1.77 injects all *environment* variables into ANT command line (-D) Hi, after the update to 1.78, all is fine again. Thanks for the quick help! Uwe 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-16226) Tools.jar is not included in classpath of maven project
studreamer studreamer closed JENKINS-16226 as Not A Defect Tools.jar is not included in classpath of maven project Change By: studreamer studreamer (30/Dec/12 4:17 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
