[JIRA] (JENKINS-14584) More information on conditions in the output
domi updated JENKINS-14584 More information on conditions in the output Logging of each run condition is currently done in each condition implementation, we might have to think about how to do this in a more generic way. Change By: domi (28/Jul/12 11:21 AM) Component/s: run-condition This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not
Ulli Hafner commented on JENKINS-13892 Analysis collector marks some warnings as fixed even though they are not Nick Jones: Nick I think your case is different. Here the original warnings computation is working correctly (warnigns and findbugs). Just the aggregation is broken. In your case the warnings computation already is broken. The reason might be that the conflicting files could not be found. Can you please create a separate 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
[JIRA] (JENKINS-14615) Warnings plugin does not maintain order of parsers on the project page
Andrew Gvozdev created JENKINS-14615 Warnings plugin does not maintain order of parsers on the project page Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 28/Jul/12 12:40 PM Description: I have a bunch of parsers which I carefully added to my project in particular order. However, on the project page all of them reshuffled without any sorting criteria I can see. Project: Jenkins Priority: Major Reporter: Andrew Gvozdev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not
Ulli Hafner edited a comment on JENKINS-13892 Analysis collector marks some warnings as fixed even though they are not @Nick Jones: Nick I think your case is different. Here the original warnings computation is working correctly (warnigns and findbugs). Just the aggregation is broken. In your case the warnings computation already is broken. The reason might be that the conflicting files could not be found. Can you please create a separate 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
[JIRA] (JENKINS-14614) Custom parsers in Warnings plugin extremely slow down Jenkins Web interface
Andrew Gvozdev
created JENKINS-14614
Custom parsers in Warnings plugin extremely slow down Jenkins Web interface
Issue Type:
Bug
Affects Versions:
current
Assignee:
Ulli Hafner
Components:
warnings
Created:
28/Jul/12 12:20 PM
Description:
I created a dozen of custom parsers using Warnings plugin. After that Jenkins Web interface got extremely slow. It takes about 30 sec just to open my project from the Dashboard. "Configure project" takes about a minute to load.
My regular expressions are for IBM XLC compiler and regular expressions are like that - "^\s*"?(^)"?, line (\d).: (.) (.) (.*)$"
The Groovy scripts are like:
groovy start
import hudson.plugins.warnings.parser.Warning
import hudson.plugins.analysis.util.model.Priority
Priority priority = Priority.NORMAL
String fileName = matcher.group(1)
String lineNumber = matcher.group(2)
String category = matcher.group(3)
String severity = matcher.group(4)
if (severity == "U" || severity == "S" || severity == "E")
priority = Priority.HIGH
else if (severity == "W")
priority = Priority.NORMAL
else if (severity == "I")
priority = Priority.LOW
String message = matcher.group(5)
category = category + " " + message
.replaceAll("extern \"C\"", "extern C")
.replaceAll("\^\*\", "X")
.replaceAll(" d+ ", " N ")
.replaceAll(" \\d+.", " N.")
final int MAX_LEN = 128
if (category.length() MAX_LEN)
category = category.substring(0, MAX_LEN-1)
return new Warning(fileName, Integer.parseInt(lineNumber), "XLC Compiler", category, message, priority);
groovy end
Environment:
Jenkins ver. 1.475, Warnings 4.13
Project:
Jenkins
Priority:
Major
Reporter:
Andrew Gvozdev
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14616) Corrupted plugin updates leads to plugin uninstall and lost job configuration
Fredrik Orderud created JENKINS-14616 Corrupted plugin updates leads to plugin uninstall and lost job configuration Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: error_log.txt Components: plugin, update-center Created: 28/Jul/12 3:44 PM Description: From mailing-list entry "Verify downloaded jpi-files": https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/2v8csoO0cxE Jenkins does not seem to verify the integrity of downloaded plugins right after the download has completed. Rather, the verification is only done when attempting to install/upgrade the plugin. This concequence of this is that corrupted plugin updates will trigger a plugin uninstall instead of upgrade. Any job-configuration related to the accidentally uninstalled plugin is then also deleted, which is pretty serious. Steps to reproduce: 1: Create a job with a subversion working-copy workspace. 2: Configure plugin manager with invalid PROXY settings, so that non-intranet HTTP-requests returns a HTML error webpage (instead of connection refused). 3: Upgrade the subversion plugin. 4: Jenkins will download a corrupted subversion.jpi file containing HTML content without any error message. 5: Restart Jenkins. 6: Loading of subversion.jpi will fail (error log attached). 7: The subversion plugin will be uninstalled. 8. Subversion-related configuration in all jobs will be deleted! Environment: Windows 7 x64. Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode). Project: Jenkins Priority: Critical Reporter: Fredrik Orderud This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13872) Counter Parameter Factory
cjo9900 commented on JENKINS-13872 Counter Parameter Factory The problem here is that checking of the from,to and step values are not validated in the config stage, it just checks that the input for each item is a valid number or a macro. So at run time the checking of the from, to and step is done. these checks are done so that there is no cases where an infinite amount of jobs are started. So this requires that START and END is an inclusive group when the step is applied examples: 1. FROM=10 and TO=0 can be valid if STEP=-1(-ive) i.e Go in a negative direction. 2. FROM=100 and TO=110 can be valid if STEP=1 (+ive) i.e Go in a negative direction. Invalid cases 1. FROM=10 and TO=0 can be invalid if STEP=2 (+ive) i.e would never reach the value of 0 as would hit maximum value first and have an exception at this point. 2. FROM=100 and TO=110 can be invalid if STEP=-1 (-ive) i.e would never reach the value of 110 as would hit minimum value first and have an exception at this point. The code that checks this just throws a Runtime Exception if these checks fail. There is a possibility that the factory could be modified with an option to not trigger these projects if the validation of the stepping fails. However that only covers one case, as it may also be required that the parameters are not used and not passed on in the failing cases. i.e. return no parameters. So I propose having an option that allows the three behaviours on stepping validation: Fail the build - RuntimeExecption (default current behaviour) Skip the triggering - DontTriggerException - no jobs triggered in this trigger(other project might be triggered is they have different configuration) Do not add parameters - return no parameters - projects still triggered without counter factory values. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14530) Allow to upgrade/downgrade to any plugin version
Jeremy Young commented on JENKINS-14530 Allow to upgrade/downgrade to any plugin version It would be nice to have the plugin screen just show the latest compatible version of each plugin. That way, the default action is to simply bring them all up to date in a compatible way. This would help all installations, not just LTS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14604) Fix view display of nested MultiJob's / upstream of MultiJob
hagzag resolved JENKINS-14604 as Duplicate Fix view display of nested MultiJobs / upstream of MultiJob Duplicate of: https://issues.jenkins-ci.org/browse/JENKINS-13078 Change By: hagzag (29/Jul/12 5:03 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14491) HTML Publisher Plugin Add button broken after 1.474 upgrade
Jesse Jacob
commented on JENKINS-14491
HTML Publisher Plugin Add button broken after 1.474 upgrade
Same issue for me: when I click add nothing happens and no script errors on FF12 and IE9, but when I click save I get a 500 and the following stack trace:
Status Code: 500
Exception: java.lang.RuntimeException: Failed to instantiate class htmlpublisher.HtmlPublisher from {"kind":"htmlpublisher.HtmlPublisher","stapler-class":"htmlpublisher.HtmlPublisher"}
Stacktrace:
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class htmlpublisher.HtmlPublisher from {"kind":"htmlpublisher.HtmlPublisher","stapler-class":"htmlpublisher.HtmlPublisher"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
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:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
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 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 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.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:215)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
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)
Caused by: java.lang.RuntimeException: Failed to instantiate class htmlpublisher.HtmlPublisher from {"kind":"htmlpublisher.HtmlPublisher","stapler-class":"htmlpublisher.HtmlPublisher"}
at hudson.model.Descriptor.newInstance(Descriptor.java:575)
at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:912)
at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:899)
at hudson.util.DescribableList.rebuildHetero(DescribableList.java:203)
at hudson.model.Project.submit(Project.java:203)
at hudson.model.Job.doConfigSubmit(Job.java:990)
at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:688)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
[JIRA] (JENKINS-11759) Allow single user with multiple usernames, therefore allowing same person to be identified
Daniel Khodaparast started work on JENKINS-11759 Allow single user with multiple usernames, therefore allowing same person to be identified Change By: Daniel Khodaparast (29/Jul/12 6:18 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14617) libvirt-slave builds broken connection URI
Fritz Elfert created JENKINS-14617 libvirt-slave builds broken connection URI Issue Type: Bug Affects Versions: current Assignee: mmornati Attachments: libvirt-slave-uri-querystring.patch Components: libvirt-slave, libvirtslave Created: 29/Jul/12 3:05 AM Description: When building the connection URI in Hypervisor.java, the query parameter "?no_tty=1" is always appended. This does not take into account, that users might already have added their own parameters in the advanced settings already. E.g: In order to use a different SSH-key location and disable host-key verification, I use the following Hypervisor-System-URL: system?keyfile=/etc/jenkins/id_dsa_remotingno_verify=1 The attached patch fixes this by using '' resp. '?' conditionally. Please note, that the patch also contains an update in the (rather old) plugin's pom.xml to make it build with current jenkins (and JDK 1.7). Environment: any Project: Jenkins Labels: patch Priority: Minor Reporter: Fritz Elfert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14618) ignore the checkout on the master
morlajb created JENKINS-14618 ignore the checkout on the master Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: matrix Created: 29/Jul/12 11:11 AM Description: in a Matrix job , we need to ability to ignore the checkout on the Master. Environment: all Project: Jenkins Priority: Major Reporter: morlajb This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14602) Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config
kutzi commented on JENKINS-14602 Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config No, that's definitely no 'rubbish'. Actually, it's quite a feature that individual users may not disable their notifications. In this this plugon works similar to e.g. the email 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
[JIRA] (JENKINS-11759) Allow single user with multiple usernames, therefore allowing same person to be identified
Daniel Khodaparast assigned JENKINS-11759 to Daniel Khodaparast Allow single user with multiple usernames, therefore allowing same person to be identified Change By: Daniel Khodaparast (29/Jul/12 6:18 AM) Assignee: DanielKhodaparast This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14602) Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config
kutzi updated JENKINS-14602 Jenkins keeps jabbering me even though I have removed my Jabber ID from my user config Change By: kutzi (29/Jul/12 10:31 AM) Issue Type: Bug NewFeature Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14619) Matrix problem with Parameterized Build
morlajb created JENKINS-14619 Matrix problem with Parameterized Build Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 29/Jul/12 12:26 PM Description: The main project use the correct SVN revision, but all the configurations use the latest version , this can cause incompatibility with complex jobs. Project: Jenkins Priority: Critical Reporter: morlajb This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13872) Counter Parameter Factory
cjo9900 assigned JENKINS-13872 to cjo9900 Counter Parameter Factory Change By: cjo9900 (29/Jul/12 5:05 PM) Assignee: huybrechts cjo9900 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14619) Matrix problem with Parameterized Build
cjo9900 commented on JENKINS-14619 Matrix problem with Parameterized Build Can you describe the issue in more detail please. How is the trigger configured? What type of job is being triggered? Can you give config file examples showing this? (create test project(s) with a public OSS repo if needed). 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
[JIRA] (JENKINS-14251) Parent injected env properties not propagated to child build jobs
cjo9900 assigned JENKINS-14251 to cjo9900 Parent injected env properties not propagated to child build jobs Change By: cjo9900 (29/Jul/12 5:05 PM) Assignee: GregoryBoissinot cjo9900 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
cjo9900
commented on JENKINS-14495
Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
It looks like some of the changes in the core of 1.474 have changed how the json is created, as taking a similar case for 1.473 and 2.15 of the plugin gives the json for that case
{
"configs":
{
"projects": "1_test",
"block":
{
"buildStepFailureThreshold": "FAILURE",
"failureThreshold": "FAILURE",
"unstableThreshold": "UNSTABLE"
},
},
"stapler-class": "hudson.plugins.parameterizedtrigger.TriggerBuilder",
"kind": "hudson.plugins.parameterizedtrigger.TriggerBuilder"
},
and for the 1.474 with 2.15
{
"configs":
{
"block":true,
"buildStepFailureThreshold":"FAILURE",
"failureThreshold":"FAILURE",
"projects":"SlaveJob1",
"unstableThreshold":"UNSTABLE"
},
"kind":"hudson.plugins.parameterizedtrigger.TriggerBuilder",
"stapler-class":"hudson.plugins.parameterizedtrigger.TriggerBuilder"
}
you can see that block encloses three elements in 1.473, but in 1.474 these are at the same level, so it looks as if the optional block behaviour has changed.
Which is used in the BlockableBuildTriggerConfig jelly that is used for the configs.
f:optionalBlock field="block" title="${%Block until the triggered projects finish their builds}" checked="${instance.block!=null}"
j:set var="descriptor" value="${app.getDescriptorOrDie(descriptor.getPropertyType(field).clazz)}" /
j:set var="instance" value="${instance[field]}"/
st:include from="${descriptor}" page="${descriptor.configPage}" /
/f:optionalBlock
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11556) Project list is not updated between builds
cjo9900 assigned JENKINS-11556 to cjo9900 Project list is not updated between builds Change By: cjo9900 (29/Jul/12 5:32 PM) Assignee: cjo9900 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14542) Issue ID Pattern no longer working
sogabe started work on JENKINS-14542 Issue ID Pattern no longer working Change By: sogabe (30/Jul/12 5:00 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14278) A parameterized buildstep in a matrix project causes IllegalArgumentException
cjo9900 commented on JENKINS-14278 A parameterized buildstep in a matrix project causes IllegalArgumentException Pull request created. https://github.com/jenkinsci/parameterized-trigger-plugin/pull/22 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14451) Parsing junitResult.xml takes long time in some case
OHTAKE Tomohiro assigned JENKINS-14451 to OHTAKE Tomohiro Parsing junitResult.xml takes long time in some case Change By: OHTAKE Tomohiro (30/Jul/12 6:57 AM) Assignee: OHTAKETomohiro This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14159) 404 when trying to see coverage on java code
Dennys Hsieh commented on JENKINS-14159 404 when trying to see coverage on java code Me too This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Milos Svasek edited a comment on JENKINS-13790 Subversion externals fail Update to use SVNKit version 1.7.5 may help with the externals issue, because there are some fixies about the svn:externals. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14542) Issue ID Pattern no longer working
sogabe edited a comment on JENKINS-14542 Issue ID Pattern no longer working It seems that JSONlib library has a bug. I'll patch to it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14451) Parsing junitResult.xml takes long time in some case
SCM/JIRA link daemon commented on JENKINS-14451 Parsing junitResult.xml takes long time in some case Code changed in jenkins User: OHTAKE Tomohiro Path: core/src/main/resources/hudson/tasks/test/MetaTabulatedResult/body.jelly http://jenkins-ci.org/commit/jenkins/d531f75f4e5d60e0690a90b0a862c285032c22df Log: FIXED JENKINS-14451 Do not read junitResult.xml many times This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14451) Parsing junitResult.xml takes long time in some case
SCM/JIRA link daemon resolved JENKINS-14451 as Fixed Parsing junitResult.xml takes long time in some case Change By: SCM/JIRA link daemon (30/Jul/12 7:52 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14622) Windows slave service credentials are not updated
Krzysztof Malinowski created JENKINS-14622 Windows slave service credentials are not updated Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jul/12 9:04 AM Description: I have a Windows slave set up to be run by WMI. It uses the same credentials to start the service as they are used to connect to host. Some time ago password has expired so I updated connection credentials in the slave setup. Jenkins did connect however it could not start the service. Investigating slave's Event Viewer showed that the service could not log on, since apparently its password has not been updated. I recommend that service's credentials should be updated on every slave connection to avoid such situations. Environment: Jenkins 1.475 on RHEL5 x86_64, Windows XP slave Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14621) When connecting Windows slave error is not seen in the log
Krzysztof Malinowski created JENKINS-14621 When connecting Windows slave error is not seen in the log Issue Type: Improvement Assignee: Unassigned Components: core Created: 30/Jul/12 8:59 AM Description: I try to connect Windows slave through WMI infrastructure. The log goes up to this: Connecting to computer-name Checking if Java exists java full version "1.7.0_05-b05" Copying jenkins-slave.xml Copying slave.jar Starting the service The spinning wheel goes on and on. When I go back to list of nodes the starting node has a red X, so I go in and see that launching the slave has failed. When I see the log it still shows up the same "Starting the service" message. It would be good to log some message at this node startup log that the startup has failed, otherwise one may waste quite a long time waiting for the service. Environment: Jenkins 1.475 on RHEL5 x86_64, Windows XP slave Project: Jenkins Priority: Minor Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14623) EnvInject ignores changes in system configuration
Krzysztof Malinowski created JENKINS-14623 EnvInject ignores changes in system configuration Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 30/Jul/12 9:22 AM Description: I check 'Prepare an environment for the run' and provide the following script content: echo %PATH% I saw that PATH had additional Unix paths I provided at global configuration (my mistake). However, after removing PATH configuration from the global settings, all following builds still show these Unix paths appended. It looks like the plugin did not notice new global configuration and still injects old PATH settings. Environment: Jenkins 1.475 on RHEL5 x86_64, Windows XP slave Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14451) Parsing junitResult.xml takes long time in some case
dogfood commented on JENKINS-14451 Parsing junitResult.xml takes long time in some case Integrated in jenkins_main_trunk #1824 FIXED JENKINS-14451 Do not read junitResult.xml many times (Revision d531f75f4e5d60e0690a90b0a862c285032c22df) Result = SUCCESS ohtake.tomohiro : d531f75f4e5d60e0690a90b0a862c285032c22df Files : core/src/main/resources/hudson/tasks/test/MetaTabulatedResult/body.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4017) Failed to parse form data. Please report this problem as a bug
Eyal Edri commented on JENKINS-4017 Failed to parse form data. Please report this problem as a bug also happened to me when trying to update a shell section in job config: Failed to parse form data. Please report this problem as a bug .. net.sf.json.JSONException: JSONObjectthresholdMode is not a number. at net.sf.json.JSONObject.getInt(JSONObject.java:1722) at org.jenkinsci.plugins.xunit.XUnitPublisher$XUnitDescriptorPublisher.newInstance(XUnitPublisher.java:438) at org.jenkinsci.plugins.xunit.XUnitPublisher$XUnitDescriptorPublisher.newInstance(XUnitPublisher.java:393) at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:912) at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:899) at hudson.util.DescribableList.rebuildHetero(DescribableList.java:203) at hudson.model.Project.submit(Project.java:203) at hudson.model.Job.doConfigSubmit(Job.java:990) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:688) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) 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:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) 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:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) 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:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) 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:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) 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:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:175) 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.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) 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:85) 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
[JIRA] (JENKINS-14569) PATH is not being injected correctly
Krzysztof Malinowski
commented on JENKINS-14569
PATH is not being injected correctly
Additional side effect: on a Windows slave there is predefined environment variable named Path. When setting PATH=C:\Program Files\7-Zip;${PATH} as EnvInject setup, it results in both PATH and Path injected variables, where Path is original (without 7-Zip) and PATH contains 7-Zip. Anyway, the build later fails since apparently Windows checks Path and not PATH (or probably these two count as one and it depends on what order they are set).
As a workaround I have corrected EnvInject setup to set Path not PATH and it works. However, standard environment setup feature from Jenkins did not work this way, i.e. correctly expanded Path with the same setup as above (PATH=C:\Program Files\7-Zip;${PATH})
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Ruben Perez
commented on JENKINS-10628
SCM build trigger not working correctly with variables in SVN URL
Ok, I'm completely updated and I'm still having problems with variables in the SVN url... The interface is not recognizing that I entered a variable and is always showing problem and I can't enter my username and password (I have to specify it on the URL). Also, I'm having an exception like:
INFO: Failed to access subversion repository ${SVNPATH}
org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${SVNPATH}'
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.SVNURL.init(SVNURL.java:221)
at org.tmatesoft.svn.core.SVNURL.parseURIDecoded(SVNURL.java:113)
at hudson.scm.SubversionSCM$DescriptorImpl.doCheckRevisionPropertiesSupported(SubversionSCM.java:2201)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
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:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
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:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
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:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
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:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
This is basic stuff for managing different branches and so on Please fix it
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14624) TFS update command needs overwrite option for writable files on workspace
Sagayaraj David created JENKINS-14624 TFS update command needs overwrite option for writable files on workspace Issue Type: Improvement Assignee: redsolo Components: tfs Created: 30/Jul/12 10:30 AM Description: When TFS command is set to update files on existing workspace, and if for some reason a file is writable on the workspace, TFS update command does not update it. It would be good if you can add overwrite checkbox just like update checkbox. Due Date: 30/Aug/12 12:00 AM Project: Jenkins Priority: Minor Reporter: Sagayaraj David This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Ruben Perez
edited a comment on JENKINS-10628
SCM build trigger not working correctly with variables in SVN URL
Ok, I'm completely updated and I'm still having problems with variables in the SVN url... The interface is not recognizing that I entered a variable and is always showing problem and I can't enter my username and password (I have to specify it on the URL). Also, I'm having an exception like:
INFO: Failed to access subversion repository ${SVNPATH}
org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${SVNPATH}'
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.SVNURL.init(SVNURL.java:221)
at org.tmatesoft.svn.core.SVNURL.parseURIDecoded(SVNURL.java:113)
at hudson.scm.SubversionSCM$DescriptorImpl.doCheckRevisionPropertiesSupported(SubversionSCM.java:2201)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
This is basic stuff for managing different branches and so on Please fix it
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14625) Exception no page found
Peter Florijn created JENKINS-14625 Exception no page found Issue Type: Bug Affects Versions: current Assignee: mcrooney Components: htmlpublisher Created: 30/Jul/12 11:58 AM Description: After upgrading to OSX Mountain Lion (and had to install JVM again) my Jenkins jobs have a problem in showing the HTML reports. Before upgrade plugin was working OK. I downgraded plugin but this did not solve the problem. Extract from console output: Exception: org.apache.commons.jelly.JellyTagException: jar:file:/Users/peter/.jenkins/war/WEB-INF/lib/jenkins-core-1.475.jar!/hudson/model/DirectoryBrowserSupport/dir.jelly:29:58: st:include No page found 'sidepanel.jelly' for class htmlpublisher.HtmlPublisherTarget$HTMLBuildAction Due Date: 31/Jul/12 12:00 AM Environment: OSX Mountain Lion Project: Jenkins Labels: exception plugin Priority: Major Reporter: Peter Florijn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14343) URL for ViewVC/ViewCVS contains portion of CVSROOT
Michael Clarke updated JENKINS-14343 URL for ViewVC/ViewCVS contains portion of CVSROOT Change By: Michael Clarke (30/Jul/12 11:40 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14626) Specify file name generated to deploy
Raphael CHAUMIER created JENKINS-14626 Specify file name generated to deploy Issue Type: Improvement Assignee: Raphael CHAUMIER Components: weblogic-deployer Created: 30/Jul/12 3:21 PM Environment: Add a field which specify what file to deploy throught a regex value. If more than one found. It displays a warning message and deploy the first Project: Jenkins Priority: Major Reporter: Raphael CHAUMIER This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3761) When login j_acegi_security_check return a 404 error
ssbarnea commented on JENKINS-3761 When login j_acegi_security_check return a 404 error AD works and I can confirm that disabling Matrix authentication solves the problem. It seems that this bug appears only with AD+matrix auth. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14491) HTML Publisher Plugin Add button broken after 1.474 upgrade
SCM/JIRA link daemon commented on JENKINS-14491 HTML Publisher Plugin Add button broken after 1.474 upgrade Code changed in jenkins User: Jesse Glick Path: src/main/java/htmlpublisher/HtmlPublisher.java http://jenkins-ci.org/commit/htmlpublisher-plugin/d3d24157587d9e25fb634280b1787bbbf61bb38c Log: JENKINS-14491 NPE reported by Jesse Jacob. Form binding apparently neglects to pass empty lists to data-bound constructors, so check for null. Reproducible even in 1.473 just by configuring publisher with no rows, i.e. not actually the real problem reported in this bug (though made more apparent by it). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14616) Corrupted plugin updates leads to plugin uninstall and lost job configuration
jglick commented on JENKINS-14616 Corrupted plugin updates leads to plugin uninstall and lost job configuration More: https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/ueaAOGrtVDI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14381) Html publish plugin doesn't show any fields in Jenkins 1.474
jglick resolved JENKINS-14381 as Duplicate Html publish plugin doesnt show any fields in Jenkins 1.474 Change By: jglick (30/Jul/12 4:42 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14514) Repeatable jelly tag appears to be broken in 1.474+
jglick started work on JENKINS-14514 Repeatable jelly tag appears to be broken in 1.474+ Change By: jglick (30/Jul/12 4:44 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14514) Repeatable jelly tag appears to be broken in 1.474+
jglick commented on JENKINS-14514 Repeatable jelly tag appears to be broken in 1.474+ Confirmed that https://github.com/jenkinsci/jenkins/commit/96442cd9cd7b432a19d05dd945502a854541cae7 introduced this bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14514) Repeatable jelly tag appears to be broken in 1.474+
jglick updated JENKINS-14514 Repeatable jelly tag appears to be broken in 1.474+ Change By: jglick (30/Jul/12 4:44 PM) Component/s: htmlpublisher Component/s: gui This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14278) A parameterized buildstep in a matrix project causes IllegalArgumentException
cjo9900 started work on JENKINS-14278 A parameterized buildstep in a matrix project causes IllegalArgumentException Change By: cjo9900 (30/Jul/12 4:50 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13872) Counter Parameter Factory
cjo9900 commented on JENKINS-13872 Counter Parameter Factory Pull request created https://github.com/jenkinsci/parameterized-trigger-plugin/pull/24 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14394) The version 1.1.21 breaks
Bryan Jacobs updated JENKINS-14394 The version 1.1.21 breaks I've created another patch, based off 2283620895c888f5f02f06fcac2fb33f1def0691 . Apparently, the problem is the use of a build parameter in the "branch to build" field. I have a series of jobs which should all run on the same target revision; the first one is kicked off by an automated system, and it passes the "revision to test" into the later ones as a parameter. This change punts along the environment and uses it to expand variables where necessary. I am unsure why matching a pattern against an exactly equal string seems to fail, but I put in a direct .equals() check to handle that case. If you can figure out why it's necessary and fix it better, I'd appreciate it. With this patch I have no further issues with the git-scm plugin. Change By: Bryan Jacobs (30/Jul/12 5:44 PM) Attachment: 0001-Bug-14394-repair-branch-choice-logic.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
[JIRA] (JENKINS-12423) Password masked by Mask Passwords are visible when using envinject plugin
Walter Kacynski reopened JENKINS-12423 Password masked by Mask Passwords are visible when using envinject plugin Running EnvInject 1.62 and Jenkins 1.473 and I'm still having an issue trying to get this to work. It seems that when using a parametrized build, the "password" type filed is not being masked. If I use the masked password plugin the console output is correctly masked, but the unencrypted password ALWAYS shows on the Injected environment variables screen. Change By: Walter Kacynski (30/Jul/12 6:24 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14628) Fatal error on JSON parsing
Eyal Edri commented on JENKINS-14628 Fatal error on JSON parsing fixed for me by downgrading xUnit plugin to 1.45. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Martin dAnjou commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds At the very least, do not let the administrator reload the configuration from disk without a warning saying that in-flight jobs will be lost. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12423) Password masked by Mask Passwords are visible when using envinject plugin
Walter Kacynski edited a comment on JENKINS-12423 Password masked by Mask Passwords are visible when using envinject plugin Running EnvInject 1.62 and Jenkins 1.473 and I'm still having an issue trying to get this to work. It seems that when using a parametrized build, the "password" type field is not being masked. If I use the masked password plugin the console output is correctly masked, but the unencrypted password ALWAYS shows on the Injected environment variables screen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14569) PATH is not being injected correctly
Gregory Boissinot commented on JENKINS-14569 PATH is not being injected correctly If I understand, there is an issue on Windows. EnvInject plugin make a difference between PATH and Path, where it is the same thing on windows. Is it all? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14623) EnvInject ignores changes in system configuration
Gregory Boissinot commented on JENKINS-14623 EnvInject ignores changes in system configuration Global configuration is only taken in account when the Jenkins instance is restarted? Did you restart after changing your global configuration? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14569) PATH is not being injected correctly
Gregory Boissinot started work on JENKINS-14569 PATH is not being injected correctly Change By: Gregory Boissinot (30/Jul/12 7:45 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14623) EnvInject ignores changes in system configuration
Gregory Boissinot started work on JENKINS-14623 EnvInject ignores changes in system configuration Change By: Gregory Boissinot (30/Jul/12 7:34 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12201) NullPointerException during SVN update
SCM/JIRA link daemon commented on JENKINS-12201 NullPointerException during SVN update Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/scm/SubversionSCM.java src/main/java/hudson/scm/subversion/UpdateUpdater.java http://jenkins-ci.org/commit/subversion-plugin/09f17089fdbbfa202735bbd4fc4f0aa241045e64 Log: FIXED JENKINS-14629 return null to notify about checkout failure relates to JENKINS-12201 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14629) plugin don't fail the build when checkout failed
Nicolas De Loof created JENKINS-14629 plugin dont fail the build when checkout failed Issue Type: Bug Assignee: Unassigned Components: subversion Created: 30/Jul/12 7:42 PM Description: after a checkout failure, hudson.scm.SubversionSCM#checkout should return false to notify jenkins about the error, but never does Project: Jenkins Priority: Minor Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14371) NullPointerException in EnvInjectBuilderContributionAction.buildEnvVars during SCM poll
Gregory Boissinot resolved JENKINS-14371 as Fixed NullPointerException in EnvInjectBuilderContributionAction.buildEnvVars during SCM poll Change By: Gregory Boissinot (30/Jul/12 8:11 PM) 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
[JIRA] (JENKINS-14628) Fatal error on JSON parsing
NA NA
created JENKINS-14628
Fatal error on JSON parsing
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
gui
Created:
30/Jul/12 6:31 PM
Description:
Error
Failed to parse form data. Please report this problem as a bug
JSON={"":"embed height=\"300\" src="" type=\"image/svg+xml\" width=\"500\"\/embed\nembed height=\"300\" src="" type=\"image/svg+xml\" width=\"500\"\/embed","builder":{"antOpts":"","buildFile":"","kind":"hudson.tasks.Ant","properties":"","stapler-class":"hudson.tasks.Ant","targets":"build-parallel"},"core:apply":"","description":"embed height=\"300\" src="" type=\"image/svg+xml\" width=\"500\"\/embed\nembed height=\"300\" src="" type=\"image/svg+xml\" width=\"500\"\/embed","disable":{},"displayNameOrNull":"","hudson-triggers-SCMTrigger":{"scmpoll_spec":"* * * * *"},"logrotate":{"logrotate_artifact_days":"","logrotate_artifact_nums":"","logrotate_days":"","logrotate_nums":"200"},"name":"project-internal","properties":{"hudson-model-ParametersDefinitionProperty":{},"stapler-class-bag":"true"},"publisher":[{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","kind":"hudson.plugins.checkstyle.CheckStylePublisher","pattern":"build/logs/checkstyle.xml","shouldDetectModules":false,"stapler-class":"hudson.plugins.checkstyle.CheckStylePublisher","thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","kind":"hudson.plugins.pmd.PmdPublisher","pattern":"build/logs/pmd.xml","shouldDetectModules":false,"stapler-class":"hudson.plugins.pmd.PmdPublisher","thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},{"canComputeNew":{"failedNewAll":"","failedNewHigh":"","failedNewLow":"","failedNewNormal":"","unstableNewAll":"","unstableNewHigh":"","unstableNewLow":"","unstableNewNormal":"","useDeltaValues":false},"canRunOnFailed":true,"defaultEncoding":"","failedTotalAll":"","failedTotalHigh":"","failedTotalLow":"","failedTotalNormal":"","healthy":"","highThreshold":"50","kind":"hudson.plugins.dry.DryPublisher","normalThreshold":"25","pattern":"build/logs/pmd-cpd.xml","shouldDetectModules":false,"stapler-class":"hudson.plugins.dry.DryPublisher","thresholdLimit":"low","unHealthy":"","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalLow":"","unstableTotalNormal":""},{"kind":"hudson.plugins.plot.PlotPublisher","plots":{csvFileName:123.csv,group:phploc,numBuilds:100,series:{file:build/logs/phploc.csv,fileType:{displayTableFlag:false,exclusionValues:Lines of Code (LOC),Comment Lines of Code (CLOC),Non-Comment Lines of Code (NCLOC),inclusionFlag:INCLUDE_BY_STRING,url:,value:csv}},style:line,title:A - Lines of code,useDescr:false,yaxis:Lines of Code},{csvFileName:1107599928.csv,group:phploc,numBuilds:100,series:{file:build/logs/phploc.csv,fileType:{displayTableFlag:false,exclusionValues:Directories,Files,Namespaces,Interfaces,Classes,Methods,Functions,Anonymous Functions,Constants,inclusionFlag:INCLUDE_BY_STRING,url:,value:csv}},style:line,title:B - Structures,useDescr:false,yaxis:Count},{csvFileName:523405415.csv,group:phploc,numBuilds:100,series:{file:build/logs/phploc.csv,fileType:{displayTableFlag:false,exclusionValues:Average Class Length (NCLOC),Average Method Length (NCLOC),inclusionFlag:INCLUDE_BY_STRING,url:,value:csv}},style:line,title:G - Average Length,useDescr:false,yaxis:Average
[JIRA] (JENKINS-14550) Checksum mismatch while updating with Subversion Plugin 1.42
SCM/JIRA link daemon commented on JENKINS-14550 Checksum mismatch while updating with Subversion Plugin 1.42 Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/scm/subversion/UpdateUpdater.java http://jenkins-ci.org/commit/subversion-plugin/a7d6b393b785bb44328302e8778d85fd7c278052 Log: JENKINS-14550 switch to checkoutUpdater on corrupted workspace detection This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14467) Server login set by default to PircBotx
charles-erid dessart commented on JENKINS-14467 Server login set by default to PircBotx I'm sorry for the delay. Basically, each user in the company uses its ssh key to access to the servers (irc, github, etc.). As all the machines are monitored by puppet, it's not in the policy to tweak a server with a new user named PircBotx. Makes sense? Thanks for your help! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14459) Failed to record SCM polling with envinject plugin
Gregory Boissinot resolved JENKINS-14459 as Fixed Failed to record SCM polling with envinject plugin Change By: Gregory Boissinot (30/Jul/12 8:11 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
[JIRA] (JENKINS-14472) Columns cannot be deleted from configure view page
jglick resolved JENKINS-14472 as Duplicate Columns cannot be deleted from configure view page Change By: jglick (30/Jul/12 10:51 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14434) Delete buttons in view configuration not working
jglick assigned JENKINS-14434 to jglick Delete buttons in view configuration not working Change By: jglick (30/Jul/12 10:55 PM) Assignee: jglick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14434) Delete buttons in view configuration not working
jglick started work on JENKINS-14434 Delete buttons in view configuration not working Change By: jglick (30/Jul/12 10:55 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14505) Delete button broken (and many more)
jglick resolved JENKINS-14505 as Duplicate Delete button broken (and many more) Change By: jglick (30/Jul/12 10:54 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14434) Delete buttons in view configuration not working
SCM/JIRA link daemon resolved JENKINS-14434 as Fixed Delete buttons in view configuration not working Change By: SCM/JIRA link daemon (30/Jul/12 11:04 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13119) How can I set an environment variable based on value of user passed parameter?
Gregory Boissinot resolved JENKINS-13119 as Fixed How can I set an environment variable based on value of user passed parameter? Change By: Gregory Boissinot (30/Jul/12 8:17 PM) 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
[JIRA] (JENKINS-14514) Repeatable jelly tag appears to be broken in 1.474+
SCM/JIRA link daemon resolved JENKINS-14514 as Fixed Repeatable jelly tag appears to be broken in 1.474+ Change By: SCM/JIRA link daemon (30/Jul/12 11:04 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14514) Repeatable jelly tag appears to be broken in 1.474+
SCM/JIRA link daemon commented on JENKINS-14514 Repeatable jelly tag appears to be broken in 1.474+ Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/35af5960eadf193a7502807a9f901cc5b1186f4d Log: JENKINS-14434 JENKINS-14514 Noting. Compare: https://github.com/jenkinsci/jenkins/compare/d531f75f4e5d...35af5960eadf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14434) Delete buttons in view configuration not working
SCM/JIRA link daemon commented on JENKINS-14434 Delete buttons in view configuration not working Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/35af5960eadf193a7502807a9f901cc5b1186f4d Log: JENKINS-14434 JENKINS-14514 Noting. Compare: https://github.com/jenkinsci/jenkins/compare/d531f75f4e5d...35af5960eadf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2920) Allow groovy scripts to be saved
Martin dAnjou commented on JENKINS-2920 Allow groovy scripts to be saved For those of us who do not make a living coding in Java and all the contemporary programming languages, we need to invest a lot of time to come up with a Groovy script (the learning curve, the syntax, etc.), and having the ability to save them for future use would be great. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14434) Delete buttons in view configuration not working
dogfood commented on JENKINS-14434 Delete buttons in view configuration not working Integrated in jenkins_main_trunk #1825 FIXED JENKINS-14434 96442cd broke "Delete" buttons in some cases. (Revision 0c2a80928bb720c0ea6794f0d0bd8a6a5f1ea3f0) JENKINS-14434 JENKINS-14514 Noting. (Revision 35af5960eadf193a7502807a9f901cc5b1186f4d) Result = SUCCESS Jesse Glick : 0c2a80928bb720c0ea6794f0d0bd8a6a5f1ea3f0 Files : core/src/main/resources/lib/form/repeatableDeleteButton.jelly Jesse Glick : 35af5960eadf193a7502807a9f901cc5b1186f4d Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14630) Artifact archiving blocks other builds
Michael Dorval created JENKINS-14630 Artifact archiving blocks other builds Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: master-slave Created: 30/Jul/12 11:19 PM Description: Here's what we see happen in our Jenkins instance every once in a while: A build (let's call A) will get stuck on the "Archiving Artifacts" step. (The artifacts are no bigger than maybe 10MBs total). Each other build of that same job will be blocked waiting for that build A to finish archiving its artifacts. If I cancel the 'stuck' build the other builds finish archiving their artifacts almost immediately. We're not building anything, this instance is solely for running Squish tests. The artifacts are the results of those tests. All tests call a single paramaterized job for their build. This build is concurrently running on separate slaves. These jobs are all running on Windows slaves. The master is a linux box. I'm not able to find any logs that have Archiving Artifact output other than the main console logs. Let me know if there's something I can attach. Project: Jenkins Priority: Major Reporter: Michael Dorval This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14514) Repeatable jelly tag appears to be broken in 1.474+
dogfood commented on JENKINS-14514 Repeatable jelly tag appears to be broken in 1.474+ Integrated in jenkins_main_trunk #1825 FIXED JENKINS-14514 96442cd broke "Add Something" buttons for many plugins. (Revision acf394f4f65b6bb77d3737dff2159f0d336129dc) JENKINS-14434 JENKINS-14514 Noting. (Revision 35af5960eadf193a7502807a9f901cc5b1186f4d) Result = SUCCESS Jesse Glick : acf394f4f65b6bb77d3737dff2159f0d336129dc Files : core/src/main/resources/lib/form/repeatable/repeatable.js Jesse Glick : 35af5960eadf193a7502807a9f901cc5b1186f4d Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13336) Invalid JSON is produced during remote api operations when a changeSet contains duplicate keys.
Gerald Bortis commented on JENKINS-13336 Invalid JSON is produced during remote api operations when a changeSet contains duplicate keys. We're running into the same issue with a duplicate 'msg' in the JSON API response. Confirmed the problem exists in versions 1.466.1, 1.467, and 1.475. The oldest version that doesn't have the problem that we can confirm is 1.456. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14631) Do not install ALL the tools
Patrick Renaud created JENKINS-14631 Do not install ALL the tools Issue Type: Improvement Assignee: Gregory Boissinot Components: shared-objects Created: 30/Jul/12 11:30 PM Description: When using the Populate Tools Installations option the SharedObjects plugin goes and tries to install ALL the tools defined globally. The result is that a proliferation of mavens, or JDKs, or Git, get installed on the slave where the job runs. In some cases, and depending on the way some tools are installed, the practice of installing several versions of the same tool may lead to undesirable effects making this plugin harmful in this context and hence banned (unfortunately). Instead of installing ALL versions of ALL tools, the plugin should install only the tools/versions specified by the job. When selected, the Populate Tools Installations toggle should be expanded with the list of all tools/versions available, with a selection box for each. See the Tool Environment plugin for a good example of the desired functionality (http://wiki.hudson-ci.org/display/HUDSON/Tool+Environment+Plugin). Project: Jenkins Priority: Critical Reporter: Patrick Renaud This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
owenmehegan commented on JENKINS-14495 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder Argh, this is hitting me too, and I use Parameterized Trigger all over the place This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14633) Ruby Plugin causes jobs to fail to load
Darryl Pogue
created JENKINS-14633
Ruby Plugin causes jobs to fail to load
Issue Type:
Bug
Affects Versions:
current
Assignee:
Jørgen Tjernø
Components:
ruby-plugin-runtime
Created:
31/Jul/12 4:53 AM
Description:
Adding an action to a build using a Ruby plugin causes the build to fail to load when Jenkins is restarted.
The error looks like this
{{SEVERE: Failed Loading job cool
java.lang.ClassCastException: org.jruby.RubyObject cannot be cast to hudson.model.Action
at hudson.model.Run.onLoad(Run.java:293)
at hudson.model.RunMap.load(RunMap.java:234)
at hudson.model.AbstractProject.onLoad(AbstractProject.java:254)
at hudson.model.Project.onLoad(Project.java:88)
at hudson.model.Items.load(Items.java:115)
at jenkins.model.Jenkins$14.run(Jenkins.java:2360)
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$5.runTask(Jenkins.java:800)
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(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)}}
The bug was originally mentioned in IRC on April 11th by dragonkh_: http://echelog.com/logs/browse/jenkins/1334095200
Relevant parts of the IRC conversattion:
cowboyd dragonkh_: do you get an exception on startup?
dragonkh_ cowboyd - it happens when I start up jenkins
dragonkh_ cowboyd - http://pastie.org/3768530
dragonkh_ cowboyd - thats the exception I get on starting up jenkins - the job fails to load
dragonkh_ is it in the ruby-runtime somewhere?
cowboyd can you send me the xml for the job?
cowboyd It's the persistence that is getting confused.
dragonkh_ cowboyd - isnt this the config? http://pastie.org/3768541
dragonkh_ cowboyd - check my code here: https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin
cowboyd dragonkh: can I see the xml for the build?
dragonkh_ cowboyd - http://pastie.org/3768765
cowboyd yes, that's it. kohsuke: ^^ any idea why jruby-xstream would be handing the ruby object and not the jruby proxy?
dragonkh cowboyd - got any idea where I can have a look ?
cowboyd yes, it's in the deserialization code. https://github.com/jenkinsci/jruby-xstream
dragonkh is that part of the main jenkins release?
cowboyd all ruby plugins depend on it
dragonkh or is it part of the ruby-runtime ?
cowboyd jenkins.rb/java-runtime depends on it
Project:
Jenkins
Priority:
Major
Reporter:
Darryl Pogue
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14632) Hetero lists broken in Jenkins 1.455+ by introduction of resource adjuncts
Timothy Bingaman created JENKINS-14632 Hetero lists broken in Jenkins 1.455+ by introduction of resource adjuncts Issue Type: Bug Assignee: Unassigned Components: core Created: 31/Jul/12 2:23 AM Description: The use of f:section elements inside newly-added items in a hetero list are broken. This appears to be caused by the introduction of resource adjuncts in Jenkins 1.455. The generated html of a f:section entry changed in v1.455 to include these extra elements: link rel="stylesheet" href="" class="code-quote">"/adjuncts/29830985/lib/form/section_.css" type="text/css" script src="" class="code-quote">"/adjuncts/29830985/lib/form/section_.js" type="text/_javascript_"/script I believe it is the link element causing the problems because if I wrap the f:section in an f:advanced tag, then edit the DOM to remove the link ... href="" element, then the hetero list entry loads successfully when the advanced section is expanded. An example of this is the Sectioned View Plugin. If you add a new List View Section to a Sectioned View then the Advanced section (which contains a f:section tag) is empty when expanded in Jenkins 1.455+. If you edit the DOM immediately after adding the List View Section (before clicking the Advanced button) to remove that extra link ... element, then the Advanced section will work properly. Environment: Jenkins v1.455 Project: Jenkins Priority: Major Reporter: Timothy Bingaman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14580) Configuration of Buildresult-Trigger remains unchanged, when saved.
Ramakrishna Bejawar commented on JENKINS-14580 Configuration of Buildresult-Trigger remains unchanged, when saved. Hi..Any Update on this 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
[JIRA] (JENKINS-14592) Plugin is parsing session id output from standard error but not standard output
SCM/JIRA link daemon commented on JENKINS-14592 Plugin is parsing session id output from standard error but not standard output Code changed in jenkins User: Ross Rowe Path: src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandReportFactory.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/fb50a93a5d7a7e87d57b0e3288831cb27d3df630 Log: JENKINS-14592 Removed code which parsed build output during generation of test-specific results This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14327) Add setter for the label string on a node
SCM/JIRA link daemon commented on JENKINS-14327 Add setter for the label string on a node Code changed in jenkins User: Andrew Bayer Path: changelog.html core/src/main/java/hudson/model/Node.java core/src/main/java/hudson/model/Slave.java core/src/main/java/jenkins/model/Jenkins.java core/src/test/java/hudson/slaves/NodeListTest.java test/src/test/java/hudson/model/labels/LabelExpressionTest.java http://jenkins-ci.org/commit/jenkins/aa603603e98a9e15556afd98a9951a27c2eaec8f Log: FIXED JENKINS-14327 Added setter for labelString to Node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14327) Add setter for the label string on a node
SCM/JIRA link daemon resolved JENKINS-14327 as Fixed Add setter for the label string on a node Change By: SCM/JIRA link daemon (31/Jul/12 7:32 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14478) 1.474 breaks adding a list-view to sectioned-view plugin
Thorsten Löber commented on JENKINS-14478 1.474 breaks adding a list-view to sectioned-view plugin We are facing the same problem with 1.475 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14633) Ruby Plugin causes jobs to fail to load
Darryl Pogue
updated JENKINS-14633
Ruby Plugin causes jobs to fail to load
Change By:
Darryl Pogue
(31/Jul/12 4:55 AM)
Description:
AddinganactiontoabuildusingaRubyplugincausesthebuildtofailtoloadwhenJenkinsisrestarted.Theerrorlookslikethis
:
{
{
code}
SEVERE:FailedLoadingjobcooljava.lang.ClassCastException:org.jruby.RubyObjectcannotbecasttohudson.model.Action athudson.model.Run.onLoad(Run.java:293) athudson.model.RunMap.load(RunMap.java:234) athudson.model.AbstractProject.onLoad(AbstractProject.java:254) athudson.model.Project.onLoad(Project.java:88) athudson.model.Items.load(Items.java:115) atjenkins.model.Jenkins$14.run(Jenkins.java:2360) atorg.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) atjenkins.model.Jenkins$5.runTask(Jenkins.java:800) atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) atjava.lang.Thread.run(Thread.java:680)
{code
}
}
ThebugwasoriginallymentionedinIRConApril11thbydragonkh_:http://echelog.com/logs/browse/jenkins/1334095200RelevantpartsoftheIRCconversattion:{quote}cowboyddragonkh_:doyougetanexceptiononstartup?dragonkh_cowboyd-ithappenswhenIstartupjenkinsdragonkh_cowboyd-http://pastie.org/3768530dragonkh_cowboyd-thatstheexceptionIgetonstartingupjenkins-thejobfailstoloaddragonkh_isitintheruby-runtimesomewhere?cowboydcanyousendmethexmlforthejob?cowboydItsthepersistencethatisgettingconfused.dragonkh_cowboyd-isntthistheconfig?http://pastie.org/3768541dragonkh_cowboyd-checkmycodehere:https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugincowboyddragonkh:canIseethexmlforthebuild?dragonkh_cowboyd-http://pastie.org/3768765cowboydyes,thatsit.kohsuke:^^anyideawhyjruby-xstreamwouldbehandingtherubyobjectandnotthejrubyproxy?dragonkhcowboyd-gotanyideawhereIcanhavealook?cowboydyes,itsinthedeserializationcode.https://github.com/jenkinsci/jruby-xstreamdragonkhisthatpartofthemainjenkinsrelease?cowboydallrubypluginsdependonitdragonkhorisitpartoftheruby-runtime?cowboydjenkins.rb/java-runtimedependsonit{quote}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14578) The plugin Copy To Slave Plugin can't work!
MS FLY commented on JENKINS-14578 The plugin Copy To Slave Plugin cant work! It has been one week since I reported the bug,but it doesn't have any updates, Who can solve this bug? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14633) Ruby Plugin causes jobs to fail to load
Darryl Pogue
updated JENKINS-14633
Ruby Plugin causes jobs to fail to load
Change By:
Darryl Pogue
(31/Jul/12 4:54 AM)
Description:
AddinganactiontoabuildusingaRubyplugincausesthebuildtofailtoloadwhenJenkinsisrestarted.Theerrorlookslikethis{{
SEVERE:FailedLoadingjobcooljava.lang.ClassCastException:org.jruby.RubyObjectcannotbecasttohudson.model.Action athudson.model.Run.onLoad(Run.java:293) athudson.model.RunMap.load(RunMap.java:234) athudson.model.AbstractProject.onLoad(AbstractProject.java:254) athudson.model.Project.onLoad(Project.java:88) athudson.model.Items.load(Items.java:115) atjenkins.model.Jenkins$14.run(Jenkins.java:2360) atorg.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) atjenkins.model.Jenkins$5.runTask(Jenkins.java:800) atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) atjava.lang.Thread.run(Thread.java:680)
}}ThebugwasoriginallymentionedinIRConApril11thbydragonkh_:http://echelog.com/logs/browse/jenkins/1334095200RelevantpartsoftheIRCconversattion:{quote}cowboyddragonkh_:doyougetanexceptiononstartup?dragonkh_cowboyd-ithappenswhenIstartupjenkinsdragonkh_cowboyd-http://pastie.org/3768530dragonkh_cowboyd-thatstheexceptionIgetonstartingupjenkins-thejobfailstoloaddragonkh_isitintheruby-runtimesomewhere?cowboydcanyousendmethexmlforthejob?cowboydItsthepersistencethatisgettingconfused.dragonkh_cowboyd-isntthistheconfig?http://pastie.org/3768541dragonkh_cowboyd-checkmycodehere:https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugincowboyddragonkh:canIseethexmlforthebuild?dragonkh_cowboyd-http://pastie.org/3768765cowboydyes,thatsit.kohsuke:^^anyideawhyjruby-xstreamwouldbehandingtherubyobjectandnotthejrubyproxy?dragonkhcowboyd-gotanyideawhereIcanhavealook?cowboydyes,itsinthedeserializationcode.https://github.com/jenkinsci/jruby-xstreamdragonkhisthatpartofthemainjenkinsrelease?cowboydallrubypluginsdependonitdragonkhorisitpartoftheruby-runtime?cowboydjenkins.rb/java-runtimedependsonit{quote}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14636) Create Artifacts From an Wrong Build
rocky wang created JENKINS-14636 Create Artifacts From an Wrong Build Issue Type: Bug Assignee: Alan Harder Attachments: copy_artifacts_from_error_build.png Components: copyartifact Created: 31/Jul/12 8:40 AM Description: 2 Projects "A" and "B", "A" is parent, "B" is child. "A" trigger "B". "A" run very fast, but "B" is very slow, so one build of "B" is triggered by more than one build from "A". The problem is, when 'B' copy artifacts from 'A', it copy artifacts from the first trigger build number, but what I want is the last trigger build number artifacts. Attached the console output for example project. Environment: OS: Windows 7 Jenkins ver. 1.462 Copy Artifact Plugin 1.22 Project: Jenkins Priority: Critical Reporter: rocky wang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
SCM/JIRA link daemon commented on JENKINS-13916 Multiline text parameter displays as single line Code changed in jenkins User: Rafa de la Torre Path: changelog.html core/src/main/java/hudson/model/TextParameterDefinition.java core/src/main/java/hudson/model/TextParameterValue.java core/src/main/resources/hudson/model/TextParameterDefinition/config.jelly core/src/main/resources/hudson/model/TextParameterValue/value.jelly core/src/main/resources/lib/form/textarea.jelly http://jenkins-ci.org/commit/jenkins/d0dbd3b8525287cf1fce51c7639b50a4f55520b0 Log: FIXED JENKINS-13916 Text parameters are now defined and shown in a textarea instead of a one line textbox. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14635) Run EnvInject after building on message
Krzysztof Malinowski
created JENKINS-14635
Run EnvInject after building on message
Issue Type:
Improvement
Assignee:
Gregory Boissinot
Components:
envinject
Created:
31/Jul/12 8:28 AM
Description:
It would be nice if EnvInject could run after echoing 'building on' message. This way two important information ('build started by' and 'building on' messages) would be side by side. Environment cleanup plugin acts after this message but before scm as well, so it should be possible.
Current output
Started by user user
EnvInject - Loading node environment variables.
EnvInject - Preparing an environment for the build.
EnvInject - Keeping Jenkins system variables.
EnvInject - Keeping Jenkins build variables.
EnvInject - Adding build parameters as variables.
EnvInject - Executing and processing the following script content:
cleartool mount \vobtag || exit 0
Jenkins $ cmd /c call D:\Profiles\user\LOCALS~1\Temp\hudson2922408064470202936.bat
D:\Jenkinscleartool mount \vobtag || exit 0
\vobtag is already mounted.
EnvInject - Script executed successfully.
EnvInject - Injecting contributions.
Building remotely on node in workspace workspace
Deleting project workspace... done
projectname $ cleartool lsview viewname
...
Expected output
Started by user user
Building remotely on node in workspace workspace
EnvInject - Loading node environment variables.
EnvInject - Preparing an environment for the build.
EnvInject - Keeping Jenkins system variables.
EnvInject - Keeping Jenkins build variables.
EnvInject - Adding build parameters as variables.
EnvInject - Executing and processing the following script content:
cleartool mount \vobtag || exit 0
Jenkins $ cmd /c call D:\Profiles\user\LOCALS~1\Temp\hudson2922408064470202936.bat
D:\Jenkinscleartool mount \vobtag || exit 0
\vobtag is already mounted.
EnvInject - Script executed successfully.
EnvInject - Injecting contributions.
Deleting project workspace... done
projectname $ cleartool lsview viewname
...
Environment:
Jenkins 1.475 on RHEL5 x86_64, envinject 1.63
Project:
Jenkins
Priority:
Minor
Reporter:
Krzysztof Malinowski
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
dogfood commented on JENKINS-13916 Multiline text parameter displays as single line Integrated in jenkins_main_trunk #1826 FIXED JENKINS-13916 Text parameters are now defined and shown in a textarea instead of a one line textbox. (Revision d0dbd3b8525287cf1fce51c7639b50a4f55520b0) Result = SUCCESS Kohsuke Kawaguchi : d0dbd3b8525287cf1fce51c7639b50a4f55520b0 Files : changelog.html core/src/main/resources/hudson/model/TextParameterValue/value.jelly core/src/main/resources/hudson/model/TextParameterDefinition/config.jelly core/src/main/java/hudson/model/TextParameterValue.java core/src/main/java/hudson/model/TextParameterDefinition.java core/src/main/resources/lib/form/textarea.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14327) Add setter for the label string on a node
dogfood commented on JENKINS-14327 Add setter for the label string on a node Integrated in jenkins_main_trunk #1826 FIXED JENKINS-14327 Added setter for labelString to Node. (Revision aa603603e98a9e15556afd98a9951a27c2eaec8f) Result = SUCCESS Kohsuke Kawaguchi : aa603603e98a9e15556afd98a9951a27c2eaec8f Files : core/src/main/java/jenkins/model/Jenkins.java core/src/main/java/hudson/model/Slave.java core/src/main/java/hudson/model/Node.java test/src/test/java/hudson/model/labels/LabelExpressionTest.java core/src/test/java/hudson/slaves/NodeListTest.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
SCM/JIRA link daemon resolved JENKINS-13916 as Fixed Multiline text parameter displays as single line Change By: SCM/JIRA link daemon (31/Jul/12 7:32 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14634) Add support for customized username to email-address inference
Sebastien Arod created JENKINS-14634 Add support for customized username to email-address inference Issue Type: Improvement Assignee: Slide-O-Mix Components: email-ext Created: 31/Jul/12 8:20 AM Description: email-ext currently infer the email address from commiter or requester user names by adding a suffix to the username if there is no @domain in the user name. This works well in most cases but in some cases it's not working: In our company the email addresses are of type firstname.lastname@company.com whereas users are firstname-lastname. It would be nice to allow advanced customization.: Using a groovy _expression_ that take the username as input and return the email addresses could allow the best flexibility. Using an explicit username to address 1-1 mapping would be nice for projects with few users. Project: Jenkins Priority: Minor Reporter: Sebastien Arod 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
