[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Manuel Coenen commented on JENKINS-16810 CLI: java.io.EOFException After a few days of working without problems the problem no occurs again with Jenkins 1.506 and AD plugin 1.30. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Manuel Coenen edited a comment on JENKINS-16810 CLI: java.io.EOFException After a few days of working without problems the problem no occurs again with Jenkins 1.506 and AD plugin 1.30. Interestingly when downgrading Jenkins to 1.499 it always works no matter of the AD plugin version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15932) Slave hangs
dmatag commented on JENKINS-15932 Slave hangs It continues happening with 2G to launch the slave, version 1.503 of Jenkins and slave 2.22. The projects are multi-module and very large. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15932) Slave hangs
dmatag updated JENKINS-15932 Slave hangs ThreadDump update Change By: dmatag (26/Mar/13 7:42 AM) Attachment: threadDump.2.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17350) Provision via JClouds fails, possibly because of upgrading SSH Slaves plugin
sakkew created JENKINS-17350 Provision via JClouds fails, possibly because of upgrading SSH Slaves plugin Issue Type: Bug Affects Versions: current Assignee: abayer Components: jclouds Created: 26/Mar/13 8:00 AM Description: Unable to create new slave, possibly after upgrading SSH Slaves plugin from 0.22 to 0.23. I assume JClouds plugin depend on this plugin, even if it is not mentioned at https://wiki.jenkins-ci.org/display/JENKINS/JClouds+Plugin. Note that when the plugin is updated, it downloads dependency "SSH Credentials Plugin". This dependency seems new according to release notes. Pressing "Test Connection" from http:///configure works fine. Pressing "Provision via JClouds" fomr http://bweppas1:8080/computer/ fails with the error: Status Code: 500 Exception: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.RuntimeException: Method is not annotated as either http or provider method: public abstract com.google.common.util.concurrent.ListenableFuture org.jclouds.rackspace.cloudidentity.v2_0.CloudIdentityAuthenticationAsyncApi.authenticateWithTenantNameAndCredentials(java.lang.String,org.jclouds.rackspace.cloudidentity.v2_0.domain.ApiKeyCredentials) Stacktrace: javax.servlet.ServletException: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.RuntimeException: Method is not annotated as either http or provider method: public abstract com.google.common.util.concurrent.ListenableFuture org.jclouds.rackspace.cloudidentity.v2_0.CloudIdentityAuthenticationAsyncApi.authenticateWithTenantNameAndCredentials(java.lang.String,org.jclouds.rackspace.cloudidentity.v2_0.domain.ApiKeyCredentials) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMePr
[JIRA] (JENKINS-5408) Quoting Issue with JDK Installer with Windows Slave
Halvor Platou commented on JENKINS-5408 Quoting Issue with JDK Installer with Windows Slave Please... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)
Emil Styrke commented on JENKINS-16533 Jobs checked out from svn with pinned externals continuously run (with no changes in svn) This is kind of critical, our builds are running rampant, and since we upgraded our working copies to 1.7, going back to 1.39 is not an option for us (I think). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Geoff Cummings commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Also seeing this after upgrade from 1.506 to 1.508 and Jenkins promoted builds plugin 2.9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Björn Peemöller commented on JENKINS-17337 Failed to load job on Matrix jobs @Bob: Looking at your stack trace, it seems to another issue, namely #17341. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Björn Peemöller edited a comment on JENKINS-17337 Failed to load job on Matrix jobs @Bob: Looking at your stack trace, it seems to be caused by another issue, namely #17341. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Bao Xiaopan(Bob) commented on JENKINS-17337 Failed to load job on Matrix jobs @Björn Peemöller thanks, I got it... the ticket will be 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Bao Xiaopan(Bob) resolved JENKINS-17337 as Fixed Failed to load job on Matrix jobs see another issue: https://issues.jenkins-ci.org/browse/JENKINS-17341 Change By: Bao Xiaopan(Bob) (26/Mar/13 8:43 AM) Status: Reopened 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Bao Xiaopan(Bob) commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 look forward to the update of the plugin... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17351) Archiving artifacts does not work at all
Bernhard Hiller
created JENKINS-17351
Archiving artifacts does not work at all
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
26/Mar/13 8:45 AM
Description:
On the slave machine, the installation of a setup package is done via command line ("Windows batch command"). The installation is logged to C:\Freigabe\Installation\LOGS\LicenseServerSetup.log.
The installation starts the freshly installed servcie. That service creates a log file: C:\Freigabe\Installation\LOGS\LicenseServerServiceTrace.log
Both files do exist.
I want to archive the files instead of TYPE them to the console (that is a very bad workaround!).
In the section "Archive the artifacts", I entered C:\Freigabe\Installation\LOGS\License*.log
Jenkins insists that the files do not exist, "even C: does not exist" - obviously wrong. Consequently, no artifacts are archived at all.
Environment:
Both Jenkins Master and Slave run on virtual machines (VMWare) with Windows XP SP3, Java SDK 1.6.42; on the Master, Jenkins runs as a service, on the slave in the context of an administrative user.
Project:
Jenkins
Labels:
artifact
jenkins
windows
Priority:
Major
Reporter:
Bernhard Hiller
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17027) Ratio red/green bar wrong
Laurent Schoelens commented on JENKINS-17027 Ratio red/green bar wrong Hello everyone, I think the best solution would be to add an option for the plugin to set the graphical representation length of uncovered lines / covered lines. By default we would keep this representation, and another option would be to set the length of graphical representation of M/C lines according to the M/(M+C) and C/(M+C) percentage. Greetings, Laurent This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
Laurent ERNES commented on JENKINS-17307 1st Failure Trigger triggers for successful builds I have the exact same issue after upgrade from 2.24.1 to 2.27.1 Using Jenkins 1.504 on master. I only configured mail for these triggers : 1st failure Still failing Fixed But I receive e-mail each time the job is successfull. The e-mail subject says "Successfull", but the log says "1st failure" trigger. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16786) Please make the "N/A" white, not black. :-)
Laurent Schoelens commented on JENKINS-16786 Please make the "N/A" white, not black. :-) I'm also in favor of choosing whether or not display the additionnal column because in my case, only a few builds are relative to code coverage report and I don't want it to appear on dashboard. I managed to do it by deleting the embedded "JaCoCo Coverage Column plugin" which is installed by default with the JaCoCo plugin. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius created JENKINS-17353 problem with summary encoding Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Attachments: Capture.PNG Components: mercurial Created: 26/Mar/13 9:59 AM Description: When displaying summary of changes unicode characters are displayed incorrectly. Browser encoding is set o Unicode. Environment: Windows Server 2008 R2 x64 Project: Jenkins Labels: mercurial encoding unicode Priority: Minor Reporter: justinas Urbanavicius This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
Daniel de Wildt commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" It Looks like this patch is the reason for the regression JENKINS-17343 https://issues.jenkins-ci.org/browse/JENKINS-17343 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We are observing this issue with Jenkins 1.480.3 on RedHat Enterprise Linux Server and SUSE Linux Enterprise Server running on a Mainframe (s390x) using current IBM JDK 7 SR4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Phil Ostler commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available Same here as well running Windows Server 2003 SE SP2 Tried upgraded from 1.505 to 1.507 & 1.508, both with the same problem. SEVERE: Failed Loading job Flexmojos java.lang.UnsatisfiedLinkError: Error looking up function 'CreateSymbolicLinkW': The specified procedure could not be found. at com.sun.jna.Function.(Function.java:179) at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:347) at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:327) at com.sun.jna.Library$Handler.invoke(Library.java:203) at $Proxy22.CreateSymbolicLinkW(Unknown Source) at hudson.util.jna.Kernel32Utils.createSymbolicLink(Kernel32Utils.java:85) at hudson.Util.createSymlink(Util.java:1048) at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:145) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:118) at hudson.model.Job.getLastSuccessfulBuild(Job.java:802) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:185) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:448) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:712) at hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:444) at hudson.model.AbstractProject.onLoad(AbstractProject.java:311) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:746) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2552) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:887) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17354) Label expression kills slave executors
Mikko Tapaninen
created JENKINS-17354
Label _expression_ kills slave executors
Issue Type:
Bug
Assignee:
kbertelson
Components:
matrixtieparent
Created:
26/Mar/13 11:44 AM
Description:
We noticed problems with using label _expression_ as "Node". In our case we used value "build&&machine (group of machine_1,...)". Once the build started, Jenkins started to loose the slave executors. They failed with:
SEVERE: Timer task hudson.model.Queue$MaintainTask@15db104e failed
java.lang.ClassCastException: hudson.model.labels.LabelExpression$And cannot be cast to hudson.model.labels.LabelAtom
at jenkins.model.Jenkins.getLabelAtom(Jenkins.java:1571)
at hudson.model.labels.LabelAtom.get(LabelAtom.java:224)
at hudson.model.labels.LabelExpressionParser.term6(LabelExpressionParser.java:208)
at hudson.model.labels.LabelExpressionParser.term5(LabelExpressionParser.java:164)
at hudson.model.labels.LabelExpressionParser.term4(LabelExpressionParser.java:136)
at hudson.model.labels.LabelExpressionParser.term3(LabelExpressionParser.java:113)
at hudson.model.labels.LabelExpressionParser.term2(LabelExpressionParser.java:83)
at hudson.model.labels.LabelExpressionParser.term1(LabelExpressionParser.java:60)
at hudson.model.labels.LabelExpressionParser.expr(LabelExpressionParser.java:50)
at hudson.model.Label.parseExpression(Label.java:509)
at jenkins.model.Jenkins.getLabel(Jenkins.java:1553)
at hudson.model.AbstractProject.getAssignedLabel(AbstractProject.java:356)
at hudson.model.queue.MappingWorksheet$WorkChunk.getAssignedLabel(MappingWorksheet.java:202)
at hudson.model.queue.MappingWorksheet$WorkChunk.(MappingWorksheet.java:185)
at hudson.model.queue.MappingWorksheet$WorkChunk.(MappingWorksheet.java:157)
at hudson.model.queue.MappingWorksheet.(MappingWorksheet.java:375)
at hudson.model.queue.MappingWorksheet.(MappingWorksheet.java:303)
at hudson.model.Queue.maintain(Queue.java:1033)
at hudson.model.Queue$MaintainTask.doRun(Queue.java:1759)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Mar 26, 2013 1:12:52 PM hudson.triggers.SafeTimerTask run
I checked that running the following groovy script from console fails to our matrix project with the "matrix tie parent" plugin config above:
import jenkins.model.*;
for(item in Jenkins.instance.items) {
println("JOB: '" + item.name + "'");
if (item.getAssignedLabel() != null) {
println("LABEL: '" + item.getAssignedLabel() + "'");
}
}
The outcome is that all executors die (https://wiki.jenkins-ci.org/display/JENKINS/Dead+Executor) and we cannot restart those threads through the UI. Only after I changed the "Node" to "master" I was able to restart the executors. So this really kills the whole Jenkins instance.
Environment:
Jenkins 1.454
matrixtieparent 1.1
Project:
Jenkins
Priority:
Major
Reporter:
Mikko Tapaninen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17355) LogRotator does not delete Maven Artifacts
Geoff Cummings
created JENKINS-17355
LogRotator does not delete Maven Artifacts
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
26/Mar/13 11:45 AM
Description:
For our maven jobs we deploy the artifacts to a Nexus Maven repository.
This requires that I do not select the "Disable automatic artifact archiving" option.
I have configured the LogRotator Discard old builds to keep the last 30 builds, but only keep 1 build with artifacts.
In multimodule maven builds the following directory is deleted:
${jenkins_home}/jobs/${jobname}/archive
The following directories are not deleted:
${jenkins_home}/jobs/${jobname}/modules/${moduleName}/builds/65/archive
Is there another way to deploy the artifacts to nexus and retain a build history without having to keep all the module artifacts?
Project:
Jenkins
Priority:
Major
Reporter:
Geoff Cummings
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11379) "Local module directory" not copied from trunk project when creating a feature branch
Andreas Kleist Svendsen commented on JENKINS-11379 "Local module directory" not copied from trunk project when creating a feature branch I just ran into this issue. There's a fix for it by ain322 here https://github.com/ain322/svnmerge-plugin/commit/39180697dee473ad766c28a16ebc57fb89b7d32d. It just needs to be pulled into master and released. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft edited a comment on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We are observing this issue with Jenkins 1.480.3 on RedHat Enterprise Linux Server and SUSE Linux Enterprise Server running on a Mainframe (s390x) using current IBM JDK 7 SR4. A very interesting observation is that on AIX - which also doesn't have an Oracle JDK - a message appears: "Failed to load native POSIX impl; falling back on Java impl. Unsupported OS." - and everything seems to work out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft edited a comment on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We are observing this issue with Jenkins 1.480.3 on RedHat Enterprise Linux Server and SUSE Linux Enterprise Server running on a Mainframe (s390x) using current IBM JDK 7 SR4. A very interesting observation is that on AIX and HP-UX - which also don't have an Oracle JDK - a message appears: "Failed to load native POSIX impl; falling back on Java impl. Unsupported OS." - and everything seems to work out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15319) Failure starting slave nodes
Francis Upton commented on JENKINS-15319 Failure starting slave nodes Hi John, I will do a release in the next couple of days which will include this fix. Sorry for the delay. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17340) Environment variables fail to get translated when encountered as part of a command execution.
Nipin Joshy closed JENKINS-17340 as Fixed Environment variables fail to get translated when encountered as part of a command execution. This issue is resolved by improrting the user .profiles Change By: Nipin Joshy (26/Mar/13 12:38 PM) Status: Open Closed 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error A possible solution might be lined out in these comments: http://jira.codehaus.org/browse/JRUBY-6712 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14351) Outdated JRuby libs
Matthias Kraft updated JENKINS-14351 Outdated JRuby libs Raised to blocker, see related links. Change By: Matthias Kraft (26/Mar/13 1:09 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Vincent Carluer updated JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available Change By: Vincent Carluer (26/Mar/13 1:44 PM) Environment: windows XP Windows Server 2003 Enterprise Edition SP2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
Alex Earl commented on JENKINS-17307 1st Failure Trigger triggers for successful builds Has there been any failure in recent builds? Can you give me the sequence of build results, or does it always trigger on first failure for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17349) CPU on master node keeps increasing and never come down
evernat updated JENKINS-17349 CPU on master node keeps increasing and never come down CPU 1 month Change By: evernat (26/Mar/13 1:54 PM) Attachment: CPU.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16854) svn:externals with fixed revision causes continuous builds
Diego Garcia commented on JENKINS-16854 svn:externals with fixed revision causes continuous builds Please fix this. This bug make unusable Jenkins for me... Thanks in advance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17356) Help for Tokens not rendering correctly
David Ishee created JENKINS-17356 Help for Tokens not rendering correctly Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 26/Mar/13 1:56 PM Description: When I click on the help icon for the token reference when configuring a Job, it displays the raw HTML. Environment: email-ext v2.27.1 Jenkins 1.480.3 Project: Jenkins Priority: Minor Reporter: David Ishee This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17357) Random Crashes From Active Directory Plugin
Michael Fowler created JENKINS-17357 Random Crashes From Active Directory Plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: active-directory Created: 26/Mar/13 2:06 PM Description: Server has crashed with no active logins with the following message: WARNING: Untrapped Error in Servlet java.lang.NullPointerException at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:88) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:119) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:195) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:45) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:138) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Project: Jenkins Labels: plugin Priority: Major Reporter: Michael Fowler 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/grou
[JIRA] (JENKINS-17358) Allow a TopLevelItemDescriptor to specify permissions needed to create an item
Jesse Glick created JENKINS-17358 Allow a TopLevelItemDescriptor to specify permissions needed to create an item Issue Type: Improvement Assignee: Jesse Glick Components: core Created: 26/Mar/13 2:07 PM Description: While many job types could reasonably be created by any user with Item.CREATE, some types inherently require more specialized permissions to create, configure, and run: backup jobs, Groovy script jobs, etc. While it is possible to check these other permissions "later", it would be much better to just forbid general users from creating such jobs to begin with—do not even show the option. Proposal: add a method to TopLevelItemDescriptor, say boolean canCreate(ItemGroup parent, AccessControlled acl), checking whether the current user is allowed to create an instance of this job type in the selected folder. The default implementation would return true, but a subclass could perform an access check on the target folder. ItemGroupMixIn would be responsible for calling the new method to prevent crafted form submissions from being accepted, but the main usage would be from e.g. View/newJob.jelly calling Items.all() and using . Project: Jenkins Labels: permissions api Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Vincent Carluer commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available It may be related with this commit: https://github.com/jenkinsci/jenkins/commit/d97b0834c8dc14d9d7ecd6634455f829d3644005 and the new method createSymbolicLink This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17359) Git plugin: clean must be performed _before_ checkout, not after
Ferry Huberts created JENKINS-17359 Git plugin: clean must be performed _before_ checkout, not after Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 26/Mar/13 2:14 PM Description: I have cgit builds, 1 that uses the git submodule and 1 that uses a fast snapshot download of git to build cgit. Because the snapshot download is untarred into the same (submodule) directory, a checkout of a new fails. This seems to have changed somewhere right at or after the 1.500 release because before it worked fine. log: Started by an SCM change Building in workspace /var/lib/jenkins/workspace/cgit_upstream_get-git_master Checkout:cgit_upstream_get-git_master / /var/lib/jenkins/workspace/cgit_upstream_get-git_master - hudson.remoting.LocalChannel@77ed71cb Using strategy: Default Last Built Revision: Revision e1e0e038fd0fee3fe10524d7466deab03e78deb5 (origin/master) Fetching changes from 1 remote Git repository Pruning obsolete local branches Commencing build of Revision b60e6bff75719a5fb0df970bac3be6b2726cf73a (origin/master) Checking out Revision b60e6bff75719a5fb0df970bac3be6b2726cf73a (origin/master) Cleaning workspace FATAL: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: git/.depend hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: git/.depend at org.jenkinsci.plugins.gitclient.JGitAPIImpl.clean(JGitAPIImpl.java:310) at hudson.plugins.git.GitAPI.clean(GitAPI.java:248) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1213) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1196) at hudson.model.AbstractProject.checkout(AbstractProject.java:1364) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:670) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:575) at hudson.model.Run.execute(Run.java:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: git/.depend at org.eclipse.jgit.api.ResetCommand.checkoutIndex(ResetCommand.java:361) at org.eclipse.jgit.api.ResetCommand.call(ResetCommand.java:204) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.clean(JGitAPIImpl.java:304) ... 14 more Caused by: org.eclipse.jgit.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: git/.depend at org.eclipse.jgit.dircache.DirCacheCheckout.cleanUpConflicts(DirCacheCheckout.java:873) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:413) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:391) at org.eclipse.jgit.api.ResetCommand.checkoutIndex(ResetCommand.java:359) ... 16 more Project: Jenkins Priority: Major Reporter: Ferry Huberts 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 r
[JIRA] (JENKINS-17349) CPU on master node keeps increasing and never come down
evernat updated JENKINS-17349 CPU on master node keeps increasing and never come down Change By: evernat (26/Mar/13 2:17 PM) Attachment: percent http errors.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
Laurent ERNES commented on JENKINS-17307 1st Failure Trigger triggers for successful builds No recent failure. The build is successful for more than ten times now... It always triggers the 1st failure when successful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17356) Help for Tokens not rendering correctly
Alex Earl started work on JENKINS-17356 Help for Tokens not rendering correctly Change By: Alex Earl (26/Mar/13 2:26 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17359) Git plugin: clean must be performed _before_ checkout, not after
Ferry Huberts commented on JENKINS-17359 Git plugin: clean must be performed _before_ checkout, not after There also is something fishy going on with the clean. I've now worked around this specific problem by deleting the git directory after the build. But now the clean fails to remove the 'dist' directory is use in a make DESTDIR="$(pwd)/dist" install It shouldn't fail this. And actually if I start a build right after, it successfully removes the dist directory log 1: Started by user Ferry Huberts Building in workspace /var/lib/jenkins/workspace/cgit_upstream_get-git_master Checkout:cgit_upstream_get-git_master / /var/lib/jenkins/workspace/cgit_upstream_get-git_master - hudson.remoting.LocalChannel@77ed71cb Using strategy: Default Last Built Revision: Revision e1e0e038fd0fee3fe10524d7466deab03e78deb5 (origin/master) Fetching changes from 1 remote Git repository Pruning obsolete local branches Commencing build of Revision b60e6bff75719a5fb0df970bac3be6b2726cf73a (origin/master) Checking out Revision b60e6bff75719a5fb0df970bac3be6b2726cf73a (origin/master) Cleaning workspace FATAL: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: git/.depend hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: git/.depend at org.jenkinsci.plugins.gitclient.JGitAPIImpl.clean(JGitAPIImpl.java:310) at hudson.plugins.git.GitAPI.clean(GitAPI.java:248) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1213) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1196) at hudson.model.AbstractProject.checkout(AbstractProject.java:1364) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:670) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:575) at hudson.model.Run.execute(Run.java:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: git/.depend at org.eclipse.jgit.api.ResetCommand.checkoutIndex(ResetCommand.java:361) at org.eclipse.jgit.api.ResetCommand.call(ResetCommand.java:204) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.clean(JGitAPIImpl.java:304) ... 14 more Caused by: org.eclipse.jgit.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: git/.depend at org.eclipse.jgit.dircache.DirCacheCheckout.cleanUpConflicts(DirCacheCheckout.java:873) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:413) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:391) at org.eclipse.jgit.api.ResetCommand.checkoutIndex(ResetCommand.java:359) ... 16 more log 2: normal successful build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17360) Two "Attach Build Log" checkboxes available
Mario Mader created JENKINS-17360 Two "Attach Build Log" checkboxes available Issue Type: Bug Assignee: Unassigned Attachments: attach_build_log.PNG Components: notification Created: 26/Mar/13 2:34 PM Description: There are two "Attach Build Log" checkboxes available but only one works. If I activate the above checkbox (please see the attached screenshot), the setting won't be stored. Environment: Windows 7 Enterprise 64 Bit Project: Jenkins Labels: plugin Priority: Minor Reporter: Mario Mader This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17349) CPU on master node keeps increasing and never come down
evernat edited a comment on JENKINS-17349 CPU on master node keeps increasing and never come down I have joined 2 interesting graphics from the PDF: % CPU for 1 month and % http errors for 1 month. It is strange to me that % CPU increases suddenly, about each week. And in the second graph, it seems that you have many http errors lately. From the joined PDF: It can be seen in the http statistics, that you have some downloads of very large artifacts (100 to 400 Mb) taking a long time. And most importantly, in the "Detailed system information" from the PDF, it says: Perm gen memory : 80 Mb / 82 MB, which is quite full. I suggest first to add a jvm parameter, probably in JENKINS_HOME/jenkins.xml: -XX:MaxPermSize=256m And restart Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17349) CPU on master node keeps increasing and never come down
evernat edited a comment on JENKINS-17349 CPU on master node keeps increasing and never come down I have joined 2 interesting graphics from the PDF: % CPU for 1 month and % http errors for 1 month. It is strange to me that % CPU increases suddenly, about each week. And in the second graph, it seems that you have many http errors lately. From the joined PDF: It can be seen in the http statistics, that you have some downloads of very large artifacts (100 to 400 Mb) taking a long time. And most importantly, in the "Detailed system information" from the PDF, it says: Perm gen memory : 80 Mb / 82 Mb, which is quite full. I suggest first to add a jvm parameter, probably in JENKINS_HOME/jenkins.xml: -XX:MaxPermSize=256m And restart Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17361) incremental build error when use gerrit-trigger choosing strategy
Haijing Wei
created JENKINS-17361
incremental build error when use gerrit-trigger choosing strategy
Issue Type:
Bug
Affects Versions:
current
Assignee:
rsandell
Components:
gerrit-trigger
Created:
26/Mar/13 2:36 PM
Description:
We have problem by incremental build jenkins 1.506 and gerrit-trigger 2.8.0. if we push for example 3 commit at once, only the last commit will be built.
The problem ist in com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.prevBuildForChangelog(). This methods return parent commit as last commit, which let git-plugin build a wrong changelog.xml. and jenkins use this changelog.xml for incremental build.
Patch for this problem:
GerritTriggerBuildChooser.java
--- a/gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerBuildChooser.java
+++ b/gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerBuildChooser.java
@@ -112,6 +112,14 @@
// Now we cheat and add the parent as the last build on the branch, so we can
// get the changelog working properly-ish.
ObjectId parentSha1 = getFirstParent(sha1, git);
+
+if(data != null) {
+ Build b = data.getLastBuildOfBranch(singleBranch);
+ if(b != null) {
+parentSha1 = b.getSHA1();
+ }
+}
+
Revision parentRev = new Revision(parentSha1);
parentRev.getBranches().add(new Branch(singleBranch, parentSha1));
Project:
Jenkins
Priority:
Major
Reporter:
Haijing Wei
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17349) CPU on master node keeps increasing and never come down
evernat edited a comment on JENKINS-17349 CPU on master node keeps increasing and never come down I have joined 2 interesting graphics from the PDF: % CPU for 1 month and % http errors for 1 month. It is strange to me that % CPU increases suddenly, about each week. (Note: this graphic is the %CPU of the Jenkins process, and not of the OS.) And in the second graph, it seems that you have many http errors lately. From the joined PDF: It can be seen in the http statistics, that you have some downloads of very large artifacts (100 to 400 Mb) taking a long time. And most importantly, in the "Detailed system information" from the PDF, it says: Perm gen memory : 80 Mb / 82 Mb, which is quite full. I suggest first to add a jvm parameter, probably in JENKINS_HOME/jenkins.xml: -XX:MaxPermSize=256m And restart Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17362) Maven build cannot find JDK when project uses default
Philip Kerrigan created JENKINS-17362 Maven build cannot find JDK when project uses default Issue Type: Bug Assignee: Unassigned Components: maven Created: 26/Mar/13 2:38 PM Description: I recently installed JDK 6.0.43, and after removing the old versions of Java my projects with a default JDK no longer build, with an error from maven that it can't find tools.jar. Jenkins is running in Tomcat with the war renamed to Hudson for historical reasons, and Tomcat is running with JDK 6.0.43. JDK7 is installed on the server and configured in Jenkins, but JAVA_HOME is also set to JDK 6.0.43, so I don't know where the jre7 is getting set. This is a problem because I have about 170 projects. Setting the specific JDK for each would be BAD, changing it for jdk7 later would be worse. [ERROR] BUILD ERROR [INFO] [INFO] Fatal error compiling Embedded error: tools.jar not found: D:\Applicazioni\Java\jre7\..\lib\tools.jar [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Fatal error compiling at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) Due Date: 30/Apr/13 12:00 AM Environment: Windows 2003 server and Tomcat 7.0.23 Project: Jenkins Priority: Major Reporter: Philip Kerrigan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17363) Ludicrously slow load time [with lazyloading]
Renaud Lepage created JENKINS-17363 Ludicrously slow load time [with lazyloading] Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: cppcheck Created: 26/Mar/13 2:38 PM Description: CPPcheck might be taking over 3,823,295ms loading a 500-job project on account of, possibly, one erroneous file. Or something. Long story short, I used the JavaMelody monitoring in Jenkins and saw that cppCheckResult was taking a HELL of a long time with one method call, and other attempts to find other ways to do this or ways around the bug have given, at best, nothing. Handling GET /job/---/cppcheckResult/graph : RequestHandlerThread24 /job/---/cppcheckResult/graph? GET 3 823 295 0 0 com.thoughtworks.xstream.converters.reflection.FieldDictionary.fieldOrNull(FieldDictionary.java:113) It's a "replicatable" problem on our servers, but since it's internal stuff I can't link you to it. Environment: Latest Jenkins, Linux ecamolx0800.mo.ca.am.ericsson.se 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux, SuSe most probably. Project: Jenkins Labels: ridiculous Priority: Major Reporter: Renaud Lepage This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17361) incremental build error when use gerrit-trigger choosing strategy
Haijing Wei
updated JENKINS-17361
incremental build error when use gerrit-trigger choosing strategy
Change By:
Haijing Wei
(26/Mar/13 2:39 PM)
Description:
We have problem by incremental build jenkins 1.506 and gerrit-trigger 2.8.0. if we push for example 3 commit at once, only the last commit will be built.The problem ist in com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.prevBuildForChangelog().
{color:red}
This methods return parent commit as last commit
{color}
, which let git-plugin build a wrong changelog.xml. and jenkins use this changelog.xml for incremental build.Patch for this problem:{code:title=GerritTriggerBuildChooser.java|borderStyle=solid}--- a/gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerBuildChooser.java+++ b/gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerBuildChooser.java@@ -112,6 +112,14 @@ // Now we cheat and add the parent as the last build on the branch, so we can // get the changelog working properly-ish. ObjectId parentSha1 = getFirstParent(sha1, git);++if(data != null) {+ Build b = data.getLastBuildOfBranch(singleBranch);+ if(b != null) {+parentSha1 = b.getSHA1();+ }+}+ Revision parentRev = new Revision(parentSha1); parentRev.getBranches().add(new Branch(singleBranch, parentSha1)); {code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16201) Join plugin - join job does not run
Geoff Greene commented on JENKINS-16201 Join plugin - join job does not run I'm having the same issue with Jenkins 1.500. join job not running. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17349) CPU on master node keeps increasing and never come down
sharon xia commented on JENKINS-17349 CPU on master node keeps increasing and never come down Good catch! Today I found another thing: There is a slave node(used to do our daily build), in which we have many branch build jobs connected to it. I found the sudden increases were caused when a branch build started, and the CPU didn't decreased even if the branch build finished. However, during this week we might have >20 branch builds and only 1 of 2 builds caused the cpu sudden increase. If I disconnected the slave build node, then the cup will decrease from the plug-in, althought from task manager the java.exe still keeps high. And after I reconnect the slave build node back, the cpu went back to high. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17364) Latest version injects ssh credentials on each restart
Björn Pedersen created JENKINS-17364 Latest version injects ssh credentials on each restart Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 26/Mar/13 2:47 PM Description: With the latest ssh-lsaves plugin, the ssh credentials from existing slaves are injected on each restart. The credentials should only get injected if no corresponding credetials entry is there already. Environment: FreeBSD Project: Jenkins Priority: Major Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17349) CPU on master node keeps increasing and never come down
sharon xia commented on JENKINS-17349 CPU on master node keeps increasing and never come down Perm gen memory : 80 Mb / 82 Mb, which is quite full. This should not be the direct reason that CPU incresed, correct? I checked it will changes from 80Mb to 81Mb, 82Mb and turned to be 80Mb again... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17364) Latest version injects ssh credentials on each restart
Björn Pedersen updated JENKINS-17364 Latest version injects ssh credentials on each restart Change By: Björn Pedersen (26/Mar/13 2:48 PM) Description: With the latest ssh- lsaves slaves plugin, the ssh credentials from existing slaves are injected on each restart. The credentials should only get injected if no corresponding credetials entry is there already. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17365) copyartifact 1.26 does not expand label expressions in parameter field, copies all of them
Julian Taylor created JENKINS-17365 copyartifact 1.26 does not expand label expressions in parameter field, copies all of them Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 26/Mar/13 3:04 PM Environment: since version 1.26 copyartifact does not expand variables in the parameter filter. Previously I had such a setup: job-name/os=$os,arch=$arch where os and arch are either label expressions or environment variables of the nodes themselves (for non matrix jobs). So each job copied the one correct artifact from the other matrix jobs. with the latest update now the plugin does not properly handle this. The Parameter filter was created automatically like this: os=$os,arch=$arch but this has the effect that *all* artifacts of the parent matrix job are copied. They also land in variable qualified subfolders instead of the top level so it breaks all of my jobs. Project: Jenkins Priority: Major Reporter: Julian Taylor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17365) copyartifact 1.26 does not expand label expressions in parameter field, copies all of them
Julian Taylor updated JENKINS-17365 copyartifact 1.26 does not expand label expressions in parameter field, copies all of them since version 1.26 copyartifact does not expand variables in the parameter filter. Previously I had such a setup: job-name/os=$os,arch=$arch where os and arch are either label expressions or environment variables of the nodes themselves (for non matrix jobs). So each job copied the one correct artifact from the other matrix jobs. with the latest update now the plugin does not properly handle this. The Parameter filter was created automatically like this: os=$os,arch=$arch but this has the effect that all artifacts of the parent matrix job are copied. They also land in variable qualified subfolders instead of the top level so it breaks all of my jobs. Change By: Julian Taylor (26/Mar/13 3:05 PM) Environment: since version linux jenkins 1. 26 copyartifact does not expand variables in the parameter filter.Previously I had such a setup:job-name/os=$os,arch=$archwhere os and arch are either label expressions or environment variables of the nodes themselves (for non matrix jobs).So each job copied the one correct artifact from the other matrix jobs.with the latest update now the plugin does not properly handle this. The Parameter filter was created automatically like this:os=$os,arch=$archbut this has the effect that *all* artifacts of the parent matrix job are copied.They also land in variable qualified subfolders instead of the top level so it breaks all of my jobs. 508 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17349) CPU on master node keeps increasing and never come down
evernat commented on JENKINS-17349 CPU on master node keeps increasing and never come down The limited perm gen may cause some cascading problems, for example in GC and in class loading, and perhaps introduce an overhead in CPU. If your large artifacts are copied between node and master or sent from master to browsers, this may also be a cause of high cpu usage. In fact, there are some other Jenkins issues, with some threads currently executing "java.util.zip.Deflater.deflateBytes", like your threads. The recent fix of JENKINS-7813, in the future Jenkins v1.509, may help perhaps for communication between node and master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
Laurent ERNES commented on JENKINS-17307 1st Failure Trigger triggers for successful builds After inspection of the config.xml file, I noticed that not all the "FirstFailureTrigger" have a "failureCount", typically the ones that generate this issue. This indicates a serialization problem, possibly due to the recent upgrade since the former version did not have this property. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
wbauer commented on JENKINS-17265 Builds disappearing from history Same issue for me, had it with the 1.4xxx builds and now still with 1.505 - really annoying! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
Alex Earl commented on JENKINS-17307 1st Failure Trigger triggers for successful builds This is a great clue, thanks! I'll have a version to try (if you are willing) that should fix this 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/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Richard Mortimer commented on JENKINS-17265 Builds disappearing from history We need to try and identify what may/may not be causing the problems. Quite a few fixes went into 1.505 and earlier but there are obviously still a few gremlins in there. Here's a few questions that those of you seeing the problem can try to answer: are there any relevant messages in any of the Jenkins logs. Any exceptions, notices about failure to load are useful. what job types do problem occur on? maven, freestyle, other. are you running Jenkins direct from the war file or within tomcat/similar environment. what OS are your masters/slaves running? Answers to those will help to point towards the right person to fix/investigate further. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
Alex Earl updated JENKINS-17307 1st Failure Trigger triggers for successful builds Try this snapshot and see if it resolves the issue. Change By: Alex Earl (26/Mar/13 3:45 PM) Attachment: email-ext.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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17362) Maven build cannot find JDK when project uses default
Philip Kerrigan commented on JENKINS-17362 Maven build cannot find JDK when project uses default I tried disinstalling all JDKs except the one I wanted, and deleting the JDK configurations from Jenkins, reinstalling Jenkins and restarting the server, but there was no difference in the error. I deleted the folder that Maven was searching and Maven/Jenkins then used the remaining public JRE, Embedded error: tools.jar not found: C:\Program Files\Java\jre6\..\lib\tools.jar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
Laurent ERNES commented on JENKINS-17307 1st Failure Trigger triggers for successful builds Sorry, but I really have no time left for this issue. Anyway, I confirm that if I reconfigure (delete/save/add/save) the 1st trigger in a job, then everything is OK, and the "failureCount" property is stored in the config.xml I did not try direct modification of the config.xml, as I wanted to check for serialization of the current version (that seems OK), but that should do the trick as well. Note that this can be used as a workaround for 2.27.1. In conclusion, I would say that the upgrade to 2.27.1 did not handle correctly the conversion (rename) of the triggers; it did not add the "failureCount" property to existing triggers that are now extending NthFailureTrigger. Hence, "failureCount" is set to 0, that leads to immediate trigger for successful build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
Rainer Weinhold created JENKINS-17366 ssh slave login via keyfile not working in 0.23 Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 26/Mar/13 3:59 PM Description: I updated to 1.480.3 (from 1.480.2) so i also updated all plugins -> so ssh-slaves was updated from 0.22 to 0.23 The upgrade process seems to have created all needed entries for the ssh-credentials plugin. But they are not working (keyfile + pwd type)! [TRACE] The same effect appears when i create the new entry manually. Which does NOT work when: using "Enter directly" using "From a file on Jenkins master " with relative or absolute path using "From the Jenkins master ~/.ssh" using not the keyfile password but the password of the user There also no changes in the error message when typing in a wrong username, or a wrong password. It only works when loging in with username password combination. So i would say the keyfile authentication is completely broken. PS: via plain ssh i can login with that keyfile. TRACE: [03/26/13 16:51:01] [SSH] Opening SSH connection to 192.168.0.24:22. [03/26/13 16:51:01] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:907) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:462) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:224) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) [03/26/13 16:51:01] [SSH] Connection closed. Environment: Ubuntu Project: Jenkins Priority: Critical Reporter: Rainer Weinhold This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
Alex Earl commented on JENKINS-17307 1st Failure Trigger triggers for successful builds You are correct. That seems to be 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/groups/opt_out.
[JIRA] (JENKINS-17367) Why is the jira project call 'credentials' when the plugin is called SSH-Credentials?
Rainer Weinhold created JENKINS-17367 Why is the jira project call 'credentials' when the plugin is called SSH-Credentials? Issue Type: Task Assignee: stephenconnolly Components: credentials Created: 26/Mar/13 4:04 PM Description: This component should be called "ssh-credentials" or the plugin should be renamend to "credentials" Project: Jenkins Priority: Major Reporter: Rainer Weinhold This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17356) Help for Tokens not rendering correctly
Alex Earl resolved JENKINS-17356 as Fixed Help for Tokens not rendering correctly Matched the way the global config is doing this. Change By: Alex Earl (26/Mar/13 4:05 PM) Status: In Progress 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17368) Manage Credentials view should show description by default
Rainer Weinhold created JENKINS-17368 Manage Credentials view should show description by default Issue Type: New Feature Assignee: stephenconnolly Components: credentials Created: 26/Mar/13 4:11 PM Description: In the "Manage Credentials" the "description" is only visible when clicking on "Advanced". When having more than one ssh-credentials entry with the same username, this does not allow you to find the key you're searching for, without clicking n-times on "advanced". I suggest that the Description should be visible by default. On the other hand "password" or "Private Key" are not necessary by default. Even scope does not help to narrow a search down this also should only be visible after pressing advanced. Environment: ssh-credentials 0.2 Project: Jenkins Priority: Major Reporter: Rainer Weinhold This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16099) Not able to enter correct SVN credentials
Pim Do commented on JENKINS-16099 Not able to enter correct SVN credentials Hi everybody, Is there any progress on this? I noticed at SVNKit bugtracker that 1.6.7 has bugs with respect to the authentication. I have not found a workaround yet while our jenkins is now unavailable because of the proxy authentication problem. No matter what I do (clean the cache in the user home, or the entries in the hudson xml) the authentication fails. With the previous releases this month we already had these issues but where able to get it running by cleaning up all credentials. Now this doesn't even help anymore. Downgrading to 1.39 (the only option in jenkins) didn't help either. We are stuck!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17369) SVNKit 1.6.7 has authentication bugs
Pim Do created JENKINS-17369 SVNKit 1.6.7 has authentication bugs Issue Type: Patch Affects Versions: current Assignee: Unassigned Components: subversion Created: 26/Mar/13 4:33 PM Description: SVNKit has bugs in release 1.6.7: http://issues.tmatesoft.com/issue/SVNKIT-342 That is currently embedded in the subversion plugin. In our case Jenkins is no longer able to access subversion!!! Please note that in my opinion this plugin and its quality is not performing as it should given its importance in the workflow. In the job configuration page we always see the connection failure (even when svn communication worked) Setting the credentials through the enter credentials page fails with: FAILED: svn: E175002: OPTIONS /project-context-pad failed org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /project-context-pad failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:628) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:103) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1018) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:1939) at hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:1884) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.
[JIRA] (JENKINS-16099) Not able to enter correct SVN credentials
domi commented on JENKINS-16099 Not able to enter correct SVN credentials @Pim as noted in my previous comment, we have identified our issue: the wrong return code of the custom auth module in our apache in front of the SVN server. After we fixed that, everything is working as expected. To identify your issue, you have to be a bit more concrete and try to clearly identify what goes wrong. Do you have any logs? what kind of security you have in place (cert, basic,...)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16099) Not able to enter correct SVN credentials
Pim Do commented on JENKINS-16099 Not able to enter correct SVN credentials @domi Hi Domi, I think my issue might be different so I have created JENKINS-17369. I will answer your question there This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
Jesse Glick commented on JENKINS-17353 problem with summary encoding Unfortunately Mercurial does not define any encoding (for file contents, filenames, or metadata such as user names and comments), so it is impossible for Jenkins to know what encoding was “meant” by the people committing changes, or indeed if they all agree on what encoding to use. My only advice is to use UTF-8 everywhere. Not sure if this is fixable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Jesse Glick commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error @makr: newer versions of Jenkins on Java 7+ will not exhibit this error because they use a different code path. By the way anyone using proprietary or unusual platforms should not expect that Jenkins core developers will be able to reproduce their problems. Debug it yourself and file a pull request if you want a prompt fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17369) SVNKit 1.6.7 has authentication bugs
Pim Do commented on JENKINS-17369 SVNKit 1.6.7 has authentication bugs @domi System setup is uberSvn with httpd. httpd is setup to require BasicAuthentication over http. Svn checkout with the same credentials work from several pc's including the server hosting jenkins. Never the less the subversion plugin in Jenkins can not connect (see previous post). Jenkins version is now 1.508. We have succesfully used version 1.504 and 1.505 with some minor bugs on the job configuration pages (saying no access, but jenkins could checkout) and the known subversion cache problems. Now we upgraded to 1.508 and it is now longer working (already spend 6 hours to fix it and am getting nowhere). Downgrading didn't help either and now I am concidering never to use this subversion plugin again and switch to a maven scm solution. With 1.504 I also encountered problems with this plugin which took me days to get the credentials set properly by Jenkins. Please note this my problem is mostlikely caused by a bug in SVN kit self and came along with a Jenkins update that selected the buggy SVN Kit release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14351) Outdated JRuby libs
Jesse Glick commented on JENKINS-14351 Outdated JRuby libs 1.0.3 is the last version of jna-posix. For jnr-posix, 2.0 changes package names so would be quite incompatible; even diff --git a/core/pom.xml b/core/pom.xml index 6d1495b..5d046d5 100644 --- a/core/pom.xml +++ b/core/pom.xml @@ -114,8 +114,8 @@ THE SOFTWARE. org.jruby.ext.posix - jna-posix - 1.0.3 + jnr-posix + 1.1.9 org.kohsuke fails to compile due to some apparently incompatible API changes. May not be practical to update this library; rather, any symptoms caused by use of the older library on some platforms should be addressed by falling back to use of some other library, or plain Java code. (Generally all of these functions are considered optional, so it is a matter of making sure the fallback code works.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17296) Can no longer attach build log
Alex Earl resolved JENKINS-17296 as Fixed Can no longer attach build log Fixed the updated optionalBlock to use the inline attribute so that the project_attach_buildlog item is passed through the JSON on submit. Change By: Alex Earl (26/Mar/13 6:25 PM) Status: In Progress Resolved Fix Version/s: current 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
Alex Earl resolved JENKINS-17307 as Fixed 1st Failure Trigger triggers for successful builds Added readResolve for FirstFailureTrigger that sets the failureCount to 1 if it is not found in the xml. Change By: Alex Earl (26/Mar/13 6:25 PM) Status: In Progress 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius commented on JENKINS-17353 problem with summary encoding i commit through netbeans IDE and not sure what encoding it does use, i presume it uses utf-8, as it would be a wise choice and mercurial's rhodecode UI displays these messages correctly so i think the problem is on Jenkins side and you should definitely use UTF-8 by default. also mercurial does define encoding it defaults to UTF-8: UTF-8 strings are used to store most repository metadata. Unlike repository contents, repository metadata is 'owned and managed' by Mercurial and can be made to conform to its rules. In particular, this includes: commit messages stored in the changelog user names tags branches The following files are stored in UTF-8: .hgtags .hg/branch .hg/branchheads.cache .hg/tags.cache .hg/bookmarks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15464) Matrix-based security -Job cancel privilege not working
Adham Hassan commented on JENKINS-15464 Matrix-based security -Job cancel privilege not working I'm experiencing this issue as well. I have a subversion checkout, and I'd like to let users start a build if they just committed code and don't want to wait for the next SVN polling. However if they cancel the build in the middle of the SVN update, it screws up the entire source tree, and I then have to choose to wipe the work space to fix it. Otherwise all builds after that fail in an SVN error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17370) Support escaping HTML whitespace with '+'
Karl Kell created JENKINS-17370 Support escaping HTML whitespace with '+' Issue Type: New Feature Assignee: Gregory Boissinot Components: urltrigger Created: 26/Mar/13 6:43 PM Description: Jenkins does not support urls that escape whitespace using '+', it only allows '%20' When attempting to visit a url using '+' instead of '%20' it returns a 400 error. Environment: CentOS 6, Jenkins 1.503, Java 7 Project: Jenkins Labels: html whitespace escaping Priority: Trivial Reporter: Karl Kell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
Jesse Glick commented on JENKINS-17353 problem with summary encoding The current system seems to date to https://github.com/jenkinsci/mercurial-plugin/commit/a0ff0f7 started by http://jenkins.361315.n4.nabble.com/Mercurial-plugin-MalformedByteSequenceException-while-parsing-changelog-xml-td367631.html but I am not sure what it was intended to do. Dealing with Unicode characters in filenames correctly in all cases is probably impossible, but sounds like it should be possible to handle Unicode in user names and commit messages. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
Jesse Glick commented on JENKINS-17353 problem with summary encoding Using NetBeans in (US-English) Windows XP I made a commit using Czech characters. They were not preserved in hg log on Ubuntu or even on the same XP machine. So I doubt I can reproduce your setup. I can only run the hg log command under the assumption that everything it produces is UTF-8. Probably this will cause problems for someone else, but too bad. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius commented on JENKINS-17353 problem with summary encoding sound good, will wait for a fix file-names are not my main concern as all file-names in my repository have only latin alphabet chars. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
SCM/JIRA link daemon commented on JENKINS-17353 problem with summary encoding Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/mercurial/MercurialSCM.java http://jenkins-ci.org/commit/mercurial-plugin/20116c4e40be73e4146af27931c54c5ef57be4e2 Log: [FIXED JENKINS-17353] Assume UTF-8 encoding for metadata in changelog.xml. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
justinas Urbanavicius commented on JENKINS-17353 problem with summary encoding hmm, that's strange, as i said, mercurial rhodecode reads commit messages just fine, and displays them correctly, and it runs on Linux Debian. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17353) problem with summary encoding
Jesse Glick updated JENKINS-17353 problem with summary encoding See if the attached update works for you. Change By: Jesse Glick (26/Mar/13 7:38 PM) Attachment: mercurial.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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17371) CAS Plugin causes infinite redirects in Chrome after Jenkins 1.508 upgrade
Eli Richmond created JENKINS-17371 CAS Plugin causes infinite redirects in Chrome after Jenkins 1.508 upgrade Issue Type: Bug Assignee: Unassigned Components: cas1 Created: 26/Mar/13 8:36 PM Description: The CAS plugin was working in Google Chrome for Jenkins 1.507, but after I upgraded to Jenkins 1.508 Chrome now gets stuck in an infinite loop. The CAS plugin seems to work fine with Firefox. If I change the security to anyone Chrome works fine. If I change the security back to matrix it works the first time I login, but any subsequent logins get stuck in the infinite redirect. Environment: Chrome 26 on Windows 7 Jenkins 1.508 on CentOS 64 Project: Jenkins Labels: plugin security Priority: Minor Reporter: Eli Richmond This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17371) CAS Plugin causes infinite redirects after Jenkins 1.508 upgrade
Eli Richmond updated JENKINS-17371 CAS Plugin causes infinite redirects after Jenkins 1.508 upgrade Change By: Eli Richmond (26/Mar/13 8:44 PM) Summary: CAS Plugin causes infinite redirects in Chrome after Jenkins 1.508 upgrade Environment: Chrome 26 or Internet Explorer 9 on Windows 7Jenkins 1.508 on CentOS 64 Description: The CAS plugin was working in Google Chrome for Jenkins 1.507, but after I upgraded to Jenkins 1.508 , Chrome now gets and IE both get stuck in an infinite loop . The CAS plugin seems to work fine with Firefox. If if I change the security go to anyone Chrome "/jenkins" without the trailing slash. It works fine if I add the trailing slash (eg "/jenkins/") or if I use Firefox 17 . If I change the security back to matrix anyone it also works the first time I login, but any subsequent logins get stuck in the infinite redirect . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17348) Git Plugin: Fast-Remote Polling Does not Filter Branch Name
Andrew Schurman updated JENKINS-17348 Git Plugin: Fast-Remote Polling Does not Filter Branch Name Attached 2 different approaches: use build parameters from the last build use default build parameters (1) is consistent with the way the scm url are retrieved, but its debatable whether to use the last build parameters when polling. Change By: Andrew Schurman (26/Mar/13 8:46 PM) Attachment: 0001-17348-Use-last-build-parameters-with-branch-specifie.patch Attachment: 0001-17348-Use-default-build-parameters-as-branch-specifi.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17296) Can no longer attach build log
SCM/JIRA link daemon commented on JENKINS-17296 Can no longer attach build log Code changed in jenkins User: Alex Earl Path: src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy http://jenkins-ci.org/commit/email-ext-plugin/d47c561f221e6f3f74286e8593f1a4c9dcb27fad Log: Fix JENKINS-17296 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17234) email-ext gives a misleading message when there is an error in a template
SCM/JIRA link daemon commented on JENKINS-17234 email-ext gives a misleading message when there is an error in a template Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java http://jenkins-ci.org/commit/email-ext-plugin/f43d8c0991abc9f7b5dd7984577924904b3583cb Log: Fix JENKINS-17234 Changed the error message for a GroovyRuntimeException This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17307) 1st Failure Trigger triggers for successful builds
SCM/JIRA link daemon commented on JENKINS-17307 1st Failure Trigger triggers for successful builds Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/NthFailureTrigger.java src/test/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTriggerTest.java src/test/resources/hudson/plugins/emailext/plugins/trigger/oldformat.xml http://jenkins-ci.org/commit/email-ext-plugin/5e3e92af367d76600e87a712af7285b13fa194ab Log: Fix JENKINS-17307 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17234) email-ext gives a misleading message when there is an error in a template
SCM/JIRA link daemon commented on JENKINS-17234 email-ext gives a misleading message when there is an error in a template Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java http://jenkins-ci.org/commit/email-ext-plugin/a24861f3fb3ecf8d438c0957ef17918046a21808 Log: Fix JENKINS-17234 Added catch of GroovyRuntimeException to output a different message so the user doesn't think its an issue with the plugin. Compare: https://github.com/jenkinsci/email-ext-plugin/compare/3bb33fcb54e9...a24861f3fb3e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17234) email-ext gives a misleading message when there is an error in a template
Alex Earl resolved JENKINS-17234 as Fixed email-ext gives a misleading message when there is an error in a template Change By: Alex Earl (26/Mar/13 8:47 PM) 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
vinz r commented on JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject I still encountered this error on 1.507. Thanks, Vinz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Richard Mortimer commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 I tested Gabriel's pull request and can confirm that it fixes the problem for me. Would be nice if we could have a new plugin release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
