[JIRA] [ghprb] (JENKINS-22404) Allow job configuration per target branch
Thomas Diesler updated JENKINS-22404 Allow job configuration per target branch Change By: Thomas Diesler (08/Sep/14 7:16 AM) Summary: Allow job configuration per target container branch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Martin Hohl commented on JENKINS-14703 PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin To avoid use of IETF BCP 47 language tags as language setting for the locale plugin is a sufficient workaround for this problem. The real problem IMHO is that a totally misleading SQL exception appears, maybe it could be fixed by introducing a more specific exception handling (e.g. catching the exception for the invalid language setting before the SQL exception can occur). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24454) Windows GIT SCM Polling hung
sharon xia commented on JENKINS-24454 Windows GIT SCM Polling hung We are using Git-1.8.4-preview20130916 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24454) Windows GIT SCM Polling hung
sharon xia edited a comment on JENKINS-24454 Windows GIT SCM Polling hung We are using Git-1.8.4-preview20130916 (msysgit) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12569) Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes
Steven Murphy commented on JENKINS-12569 Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes It would be good to have the ability to truly disable these checks. My HP slaves have issues with the Free Swap Space check (java exception 'top' unavailable) and these errors clutter the log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-24620) Informational labels for OnDemand plugin
apgray created JENKINS-24620 Informational labels for OnDemand plugin Issue Type: Improvement Affects Versions: current Assignee: Kohsuke Kawaguchi Components: sauce-ondemand Created: 08/Sep/14 7:33 AM Description: A suggested useful improvement would be to display an dynamic label below the Sauce OnDemand multiSelect boxes on the job configuration page that simply said: "1 platform selected." Or "59 platforms selected." Due Date: 30/Sep/14 12:00 AM Environment: Windows Fix Versions: current Project: Jenkins Priority: Minor Reporter: apgray This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12569) Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes
Daniel Beck commented on JENKINS-12569 Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes At least for custom log recorders in, you can reduce logging levels for more specific loggers since 1.549 (undocumented, unfortunately). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chrome-frame] (JENKINS-24621) Footer shadows save button on job config
Thomas Diesler created JENKINS-24621 Footer shadows save button on job config Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Screen Shot 2014-09-08 at 09.52.45.png Components: chrome-frame Created: 08/Sep/14 7:52 AM Description: Information added to the footer seems to expand upwards with the result that it shadows controls/information on the main page Environment: Chrome: 37.0.2062.94 Darwin macbook 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014 Project: Jenkins Priority: Major Reporter: Thomas Diesler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chrome-frame] (JENKINS-24621) Footer shadows save button on job config
Thomas Diesler updated JENKINS-24621 Footer shadows save button on job config Change By: Thomas Diesler (08/Sep/14 7:53 AM) Attachment: Screen Shot 2014-09-08 at 09.52.45.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-24620) Informational labels for OnDemand plugin
apgray updated JENKINS-24620 Informational labels for OnDemand plugin Change By: apgray (08/Sep/14 7:55 AM) Due Date: 30/Sep/14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Stephan Krull commented on JENKINS-19142 Don't add jobs to a view Oleg Nenashev's workaround works perfect for me. This keeps me from insisting to the following detail: By closing JENKINS-19596 this issue is no longer treated as a bug but as an improvement. I disagree because in my understandig there should be differantiation between job and view. A view has to show objects that have been configured for that view. If there is a regex or a manually checked lists of jobs that belong to that view than no algorithm or automatic process should slip in this configuration (as is by creating a new job in that view). A newly created job should be included only in views whose configurations is appropriate. This definition makes this issue a 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-24562) Publish Valgrind results and ClearCase
Knut Petter S commented on JENKINS-24562 Publish Valgrind results and ClearCase The executable contains the source path used at compile time. I suppose this is how the "Publish Valgrind results" step finds the source files to copy into .jenkins/jobs/../valgrind-plugin/source-files/source_x.tmp. However, the source file path in the executable is not available during the post build step (since it is not running in view context). So what I need is a way to specify a prefix to where the source code is located (when not running in view context as it was duing build time). An example: Program myApp is compiled from source /vobs/comp1/src/main.cpp and /vobs/comp2/src/file1.cpp. But when publish valgrind results is running the source is avaiable from /view/my_view/vobs/comp1/src/main.cpp and /view/my_view/vobs/comp2/src/file1.cpp. By adding a way to specify a "prefix path" or "source substitute path" this would solve the problem. In the example would be "/view/my_view". Does this make sense? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
SCM/JIRA link daemon commented on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list Code changed in jenkins User: Ulli Hafner Path: src/test/java/hudson/plugins/warnings/parser/ParserRegistryIntegrationTest.java src/test/resources/hudson/plugins/warnings/parser/issue24611.txt http://jenkins-ci.org/commit/warnings-plugin/70e7048ef9ecc3d09be4b5c676e617c987e3b5a6 Log: JENKINS-24611 Added testcase. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Ulli Hafner edited a comment on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list You can't directly select the ant javac parser. It is part of the sub-set of the javac parsers. I added a test case that correctly parses your log file, seems there is something else broken. Which versions are you using? Did you select the Javac parser. What messages are in the console log? (There should be some messages from the WARNINGS plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Ulli Hafner edited a comment on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list You can't directly select the ant parser. It is part of the sub-set of the javac parsers. I added a test case that correctly parsers your log file, seems there is something else broken. Which versions are you using? Did you select the Javac parser. What messages are in the console log? (There should be some messages from the WARNINGS plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Ulli Hafner commented on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list You can't select the ant parser. It is part of the sub-set of the javac parsers. I added a test case that correctly parsers your log file, seems there is something else broken. Which versions are you using? Did you select the Javac parser. What messages are in the console log? (There should be some messages from the WARNINGS plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Ulli Hafner edited a comment on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list You can't directly select the ant javac parser. It is part of the sub-set of the javac parsers. I added a test case that correctly parses your log file, seems there is something else broken. Which versions are you using? Did you select the Javac parser? What messages are in the console log? (There should be some messages from the WARNINGS plugin.) Can you please attach the log output as plain text file, maybe there is an encoding problem... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-24622) Upstream jobs have disapeared from job main page
Sylvain C. created JENKINS-24622 Upstream jobs have disapeared from job main page Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 08/Sep/14 8:51 AM Description: Since the version 2.17 upstream jobs have disappeared from job main page when paramterized-trigger plugin is used in a build step. Project: Jenkins Priority: Major Reporter: Sylvain C. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-24619) Job history overlaps content in main window
davida2009 commented on JENKINS-24619 Job history overlaps content in main window I see a similar effect for job history with IE11 and Jenkins 1.579. Also the job list on the dashboard overlaps the main window - will attached screenshot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metrics] (JENKINS-23933) Expose build successful/unstable/failed metrics
SCM/JIRA link daemon commented on JENKINS-23933 Expose build successful/unstable/failed metrics Code changed in jenkins User: Mirko Friedenhagen Path: src/main/java/jenkins/metrics/impl/JenkinsMetricProviderImpl.java http://jenkins-ci.org/commit/metrics-plugin/e40935251265732178ce1f605a481cec8d038a41 Log: JENKINS-23933: Expose build successful/unstable/failed metrics. We are running a couple of Jenkins masters. We have run into problems because nodes are not able to access vital systems like our internal Maven repository or our SCM, sometimes because the hosts were down or because of new VLAN settings or firewalls between nodes or even because of configuration changes. In these cases the number of failing builds is increasing immediately. It would be nice if the metrics plugin could provide metrics of successful, unstable and failed builds, so we can react more promptly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metrics] (JENKINS-23933) Expose build successful/unstable/failed metrics
SCM/JIRA link daemon commented on JENKINS-23933 Expose build successful/unstable/failed metrics Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/metrics/impl/JenkinsMetricProviderImpl.java http://jenkins-ci.org/commit/metrics-plugin/264a210d6e4b6575ebf0f37f00385ac71315cfd2 Log: Merge pull request #3 from mfriedenhagen/JENKINS-23933 JENKINS-23933: Expose build successful/unstable/failed metrics. Compare: https://github.com/jenkinsci/metrics-plugin/compare/79d151a18216...264a210d6e4b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-5318) Allow default view at user level
Dennis F. commented on JENKINS-5318 Allow default view at user level I think it would be handy to have per user configuration of default view. It would be great to see your view directly after logon without navigating to My views menu... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24623) LDAP AcceptSecurityContext error
Alex Vesely
created JENKINS-24623
LDAP AcceptSecurityContext error
Issue Type:
Bug
Affects Versions:
current
Assignee:
Kohsuke Kawaguchi
Components:
ldap
Created:
08/Sep/14 9:01 AM
Description:
Running Jenkins 1.565.1, LDAP plugin 1.10.2.
I found multiple topics on this subject, but none of them seem to solve my problem.
I am trying to set up LDAP authentication on my Jenkins in my corporate network. Jenkins is running on Linux.
Here are my LDAP settings:
Server: ldap://my_server.abc.corp.company.com
root DN: dc=abc,dc=corp,dc=company,dc=com
manager DN: my_n...@abc.corp.company.com
manager password: set
Other settings are blank/default.
When I try to login to Jenkins, even using the same "manager" login, I get a failure, and see the following error in the Jenkins log:
org.acegisecurity.providers.ldap.authenticator.BindAuthenticator2 handleBindException
WARNING: Failed to bind to LDAP: userDnCN=my_name,OU=UserPersonalities,OU=ims,OU=UNIX,OU=A Name With Spaces,OU=Resources,dc=abc,dc=corp,dc=company,dc=com username=my_name
javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A8, comment: AcceptSecurityContext error, data 52e, v1db1]
I found a Groovy script that was supposed to help me debug the issue:
String[] names = ["my_name","another_name"];
for (name in names) {
println("Checking the name '" + name + "'...")
try {
println(" It is a USER: " + Jenkins.instance.securityRealm.loadUserByUsername(name))
} catch (Exception e) {
println(" It is NOT a user, reason: " + e.getMessage())
}
println("");
}
However, it can find the username successfully:
Checking the name 'my_name'...
It is a USER: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@5a26cfb7
Checking the name 'another_name'...
It is a USER: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@143fee62
Moreover, I can successfully authenticate using the Active Directory plugin, but its performance is very low (it takes 1-2 minutes to authorize a user), and I don't see any setting to tweak that.
Environment:
Linux
Project:
Jenkins
Labels:
ldap
Priority:
Critical
Reporter:
Alex Vesely
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24623) LDAP AcceptSecurityContext error
Alex Vesely
updated JENKINS-24623
LDAP AcceptSecurityContext error
Change By:
Alex Vesely
(08/Sep/14 9:02 AM)
Description:
Running Jenkins 1.565.1, LDAP plugin 1.10.2.I found multiple topics on this subject, but none of them seem to solve my problem.I am trying to set up LDAP authentication on my Jenkins in my corporate network. Jenkins is running on Linux. Here are my LDAP settings:Server: ldap://my_server.abc.corp.company.comroot DN: dc=abc,dc=corp,dc=company,dc=commanager DN: my_n...@abc.corp.company.commanager password: *set*Other settings are blank/default.When I try to login to Jenkins, even using the same "manager" login, I get a failure, and see the following error in the Jenkins log:org.acegisecurity.providers.ldap.authenticator.BindAuthenticator2 handleBindExceptionWARNING: Failed to bind to LDAP: userDnCN=my_name,OU=UserPersonalities,OU=
ims
site
,OU=UNIX,OU=A Name With Spaces,OU=Resources,dc=abc,dc=corp,dc=company,dc=com username=my_namejavax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A8, comment: AcceptSecurityContext error, data 52e, v1db1] I found a Groovy script that was supposed to help me debug the issue:String[] names = ["my_name","another_name"];for (name in names) { println("Checking the name '" + name + "'...") try {println(" It is a USER: " + Jenkins.instance.securityRealm.loadUserByUsername(name)) } catch (Exception e) {println(" It is NOT a user, reason: " + e.getMessage()) } println("");} However, it can find the username successfully:Checking the name 'my_name'... It is a USER: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@5a26cfb7Checking the name 'another_name'... It is a USER: org.acegisecurity.userdetails.ldap.LdapUserDetailsImpl@143fee62Moreover, I can successfully authenticate using the Active Directory plugin, but its performance is very low (it takes 1-2 minutes to authorize a user), and I don't see any setting to tweak that.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-24619) Job history overlaps content in main window
davida2009 updated JENKINS-24619 Job history overlaps content in main window Attached file containing screenshot of overlapping job title on main dashboard in IE11. Change By: davida2009 (08/Sep/14 9:09 AM) Attachment: dashboard.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24624) Support for shared workspaces
Morne Joubert created JENKINS-24624 Support for shared workspaces Issue Type: New Feature Assignee: Unassigned Components: p4 Created: 08/Sep/14 9:45 AM Description: I have recently joined a company that is using Jenkins (i used to manage TeamCity in an enterprise environment for 250 engineers) and am having problems seeing how Jenkins scales using Perforce. My problem is as follows: Setup: 1 Slave with 1 executor 10 different builds all using the same stream Current Jenkins behavior (to allow the Workspace browser to work) is to sync 10 different workspaces (all with the same code) and create 10 different client specs in perforce. Now take a slave with 16 executors. We now have 16*10 copies of exactly the same stream source code on the slave and 16*10 client specs in perforce. Now scale it up to 50 different builds using 3 different streams with many slaves and the whole system just doesn't scale well from an IT storage and perforce access point of view What i was hoping to achieve (and this is how TeamCity and ElectricCommander does it) it to be able to share workspaces between builds. If we created workspaces/clientspecs PER EXECUTOR then 2 builds can't use the source code at the same time. So if a slave had 16 executors then there would only be 16 clientspecs and 16 workspaces for each stream and the builds won't clash since each executor can only do one thing at a time. I am happy to loose the Workspace browser (that we never use) since this won't be valid anymore. For this to work i would expect the change history tracking can't be stored on the perforce server side since the workspace/client spec is now shared so am not sure if this can actually be solved. Any suggestions on how this can be achieved ? This would be a big opportunity for Perforce to get themselves into Jenkins use for enterprise use. (that TeamCity and ElectricCommander has already done) Project: Jenkins Priority: Major Reporter: Morne Joubert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24591) Unable to run perforce commands within build steps
Morne Joubert commented on JENKINS-24591 Unable to run perforce commands within build steps The best way would be for P4TICKETS to be used. That way the P4USER and P4PASSWORDS are not made visible in scripts,steps etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24625) style.css should define background color for input fields
Ceesjan Luiten created JENKINS-24625 style.css should define background color for input fields Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: 2014-08-09_114643_7858.png Components: core Created: 08/Sep/14 9:50 AM Description: Currently style.css sets the foreground color but doesn't set the background color; this renders all input fields unreadable for people with certain color schemes. https://github.com/jenkinsci/jenkins/blob/7cdb85d09c0a709c59694de7b009cb2d0117578b/war/src/main/webapp/css/style.css#L115 To reproduce on Windows: Switch the Windows theme to High Contract and open a job configuration page. To reproduce on Linux: Switch your theme to one where you have dark backgrounds and light text. To solve this, add 'background-color: #fff' to the same definition. Project: Jenkins Labels: css Priority: Minor Reporter: Ceesjan Luiten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura] (JENKINS-6684) Cobertura plugin should autoconfigure for Maven projects
Dennis Lundberg commented on JENKINS-6684 Cobertura plugin should autoconfigure for Maven projects I've created a pull request with a fix for this issue: https://github.com/jenkinsci/cobertura-plugin/pull/35 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24607) Need ability to build changes sequentially
Morne Joubert commented on JENKINS-24607 Need ability to build changes sequentially A potential extra angle to this that i have used before (in TeamCity) is to do binary chopping of the changes for builds that take very long. So take the case of a build taking 1 hours and 20 changes go in. The overnight build fail with the last change. I then scripted code to go back 20/2=10 changes back and do a build. If that passed then go back 10/2=5 builds etc until i found the actual problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [distfork] (JENKINS-16200) Duration parameter doesn't work
Alex Vesely commented on JENKINS-16200 Duration parameter doesn't work Same with 1.565.1. Is anybody supporting dist-fork? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19760) Long hyperlinks in build description not displayed correctly on project page when using Markdown syntax
Sami Salonen
commented on JENKINS-19760
Long hyperlinks in build description not displayed correctly on project page when using Markdown syntax
This issue is about build descriptions only. I have not tested setting project descriptions. Build descriptions are visible on project page (Build History table) and naturally on the build page itself. Displaying build descriptions in Build History table (project page) seems to be the problem here.
Here is a sample shell script that sets the build description during the build.
jcli="ssh -p "
function get_first_link()
{
local text="first"
local url="" class="code-quote">"http://x.x.x.x/x/x/x/x?zzz=yyy&aaa=bbb&ccc=ddd&eee=123"
# this does not work:
echo "[$text]($url)"
# this works:
# echo "$url\">$text"
}
function get_second_link()
{
}
first=$( get_first_link )
second=$( get_second_link )
desc="$first\ $second"
$jcli set-build-description "$JOB_NAME" "$BUILD_NUMBER" "$desc"
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24625) style.css should define background color for input fields
Daniel Beck updated JENKINS-24625 style.css should define background color for input fields Change By: Daniel Beck (08/Sep/14 11:36 AM) Labels: css user-experience Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24623) LDAP AcceptSecurityContext error
Daniel Beck resolved JENKINS-24623 as Not A Defect LDAP AcceptSecurityContext error This report does not show that the observed behavior is in fact a bug, therefore resolving as Not A Defect. Please direct requests for assistance (e.g. in configuring Jenkins) to the jenkinsci-users mailing list, or #jenkins on Freenode. Change By: Daniel Beck (08/Sep/14 11:39 AM) Status: Open Resolved Assignee: Kohsuke Kawaguchi Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24619) Job history overlaps content in main window
Daniel Beck resolved JENKINS-24619 as Duplicate Job history overlaps content in main window Duplicates JENKINS-24589. Change By: Daniel Beck (08/Sep/14 11:42 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-24621) Footer shadows save button on job config
Daniel Beck updated JENKINS-24621 Footer shadows save button on job config Should probably be fixed in SCM Sync Plugin, and only if no reasonable solution is possible reassign to core to change the layout to account for this. Change By: Daniel Beck (08/Sep/14 11:41 AM) Labels: user-experience Affects Version/s: current Priority: Major Minor Component/s: scm-sync-configuration Component/s: chrome-frame This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24619) Job history overlaps content in main window
Daniel Beck updated JENKINS-24619 Job history overlaps content in main window Change By: Daniel Beck (08/Sep/14 11:42 AM) Affects Version/s: current Component/s: core Component/s: jenkins-tracker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24626) Unable to CopyArtifact from builds using older CopyArtifact plugin
Tom Ghyselinck created JENKINS-24626 Unable to CopyArtifact from builds using older CopyArtifact plugin Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 08/Sep/14 11:59 AM Description: Hi, We have a problem when passing Build selector for Copy Artifact as a parameter filter for an older job/build. Suppose 3 Jobs: Job 1: DepJob Job 2: SubJob Build selector for Copy Artifact Parameter: SELECT_ME Default selector : Specific build Build number : 123 Build step: Copy artifacts from another project: Project Name : DepJob Which build : Specified by a build parameter Parameter Name : SELECT_ME Job 3: MainJob Build selector for Copy Artifact Parameter: SELECT_DEPJOB Default selector : Specific build Build number : 123 Build step: Copy artifacts from another project: Project Name : SubJob Which build : Latest successful build Parameter filters : SELECT_ME=$SELECT_DEPJOB Quick issue description When last successful build of SubJob has been built with an older version of the Copy Artifact Plugin, then MainJob cannot find the artifacts although they exist! Details DepJob has a build 123. SubJob performs some builds with Copy Artifact Plugin version 1.26: Build selector for Copy Artifact Parameter: SELECT_ME: Specific build -> 123 Update Copy Artifact Plugin MainJob performs build with Copy Artifact Plugin version 1.31: Build selector for Copy Artifact Parameter: SELECT_DEPJOB: Specific build -> 123 MainJob build fails since it cannot find atifacts with SELECT_ME: Specific build -> 123 in the old builds of SubJob! This is a blocker for us since we have a very large project which uses this kind of constructions for packaging all sub-projects (aka sub jobs). We recently updated the Copy Artifact Plugin, but we still need lots of artifacts the old(er) sub-projects (for which currently no rebuilt is needed). Environment: Jenkins 1.565.1 LTS Copy Artifact Plugin 1.31 Project: Jenkins Labels: copyartifact parameter filter Priority: Blocker Reporter: Tom Ghyselinck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24626) Unable to CopyArtifact from builds using older CopyArtifact plugin
Tom Ghyselinck updated JENKINS-24626 Unable to CopyArtifact from builds using older CopyArtifact plugin Change By: Tom Ghyselinck (08/Sep/14 12:01 PM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter] (JENKINS-24618) Absolute priority not working
Tomas Westling commented on JENKINS-24618 Absolute priority not working After running some more tests, I see that sometimes the priorities work and sometimes they don't. I haven't been able to deduce what causes them to stop working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24623) LDAP AcceptSecurityContext error
Alex Vesely commented on JENKINS-24623 LDAP AcceptSecurityContext error Why is it not a bug? The configuration seems to be correct, but authentication fails with a nonsensical stack-trace. Authentication is successful from the settings, but the same credentials fail from the Login 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24623) LDAP AcceptSecurityContext error
Alex Vesely edited a comment on JENKINS-24623 LDAP AcceptSecurityContext error Why is it not a bug? The configuration seems to be correct, but authentication fails with a nonsensical stack-trace. Authentication is successful from the settings, but the same credentials fail on the Login 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24623) LDAP AcceptSecurityContext error
Alex Vesely edited a comment on JENKINS-24623 LDAP AcceptSecurityContext error Why is it not a bug? The configuration seems to be correct (tested with the Active Directory plugin), but authentication fails with a nonsensical stack-trace. Authentication is successful from the settings, but the same credentials fail on the Login 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24560) Customize time fromat for columns in task lists
Maciej Jaros closed JENKINS-24560 as Won't Fix Customize time fromat for columns in task lists Change By: Maciej Jaros (08/Sep/14 12:43 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24560) Customize time fromat for columns in task lists
Maciej Jaros commented on JENKINS-24560 Customize time fromat for columns in task lists Hi. Just wanted to thank you. The column "Compact Column: All Statuses w/ Options" with format "Date/time Date prefered" is exactly what I wanted . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-20056) When deleting the entire workspace, perform it asynchronously
Oliver Gondža assigned JENKINS-20056 to Oliver Gondža When deleting the entire workspace, perform it asynchronously Change By: Oliver Gondža (08/Sep/14 1:05 PM) Assignee: Lucie Votypkova Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-18961) LDAP plugin does not support nested groups
Bruce Coveny commented on JENKINS-18961 LDAP plugin does not support nested groups There has been some chat on the springsource ticket and wondering if this could be investigated to what they said to allow nested groups. My firm only uses nested groups so instead of one or two groups we now have to add 50 different groups to Jenkins security console and maintain them all. Jean-Pierre Bergamin added a comment - 17/Jun/14 1:31 AM I use this class here: https://gist.github.com/ractive/258dd06c99d2939781c0 Put it in the package org.springframework.security.ldap.authentication.ad and you should be ready to go... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24623) LDAP AcceptSecurityContext error
Alex Vesely reopened JENKINS-24623 LDAP AcceptSecurityContext error Change By: Alex Vesely (08/Sep/14 1:14 PM) Resolution: Not A Defect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-24627) ConcurrentModificationException with DiskUsage
Krzysztof Malinowski
created JENKINS-24627
ConcurrentModificationException with DiskUsage
Issue Type:
Bug
Assignee:
Lucie Votypkova
Components:
disk-usage
Created:
08/Sep/14 1:56 PM
Description:
It happens that opening job page hangs for a long time, while Jenkins log gets full of ConcurrentModificationException. Disabling disk-usage plugin eliminates the issue.
The exception starts in various ways, but always related to disk usage, i.e.:
WARNING: Caught exception evaluating: from.getSizeInString(from.getBuildsDiskUsage().get('all')) in /job/project/. Reason: java.util.ConcurrentModificationException
WARNING: Caught exception evaluating: from.getSizeInString(from.getJobRootDirDiskUsage()) in /view/view1/job/project/. Reason: java.util.ConcurrentModificationException
Full stack trace:
Sep 08, 2014 3:43:20 PM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: from.getSizeInString(from.getJobRootDirDiskUsage()) in /view/view1/job/project/. Reason: java.util.
ConcurrentModificationException
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429)
at java.util.HashMap$KeyIterator.next(HashMap.java:1453)
at hudson.plugins.disk_usage.ProjectDiskUsageAction.getBuildsDiskUsage(ProjectDiskUsageAction.java:232)
at hudson.plugins.disk_usage.ProjectDiskUsageAction.getBuildsDiskUsage(ProjectDiskUsageAction.java:203)
at hudson.plugins.disk_usage.ProjectDiskUsageAction.getJobRootDirDiskUsage(ProjectDiskUsageAction.java:134)
at sun.reflect.GeneratedMethodAccessor2745.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54)
at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:81)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
[JIRA] [core] (JENKINS-23665) Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password
Torsten Schlabach assigned JENKINS-23665 to Account App Run by Kohsuke Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password Change By: Torsten Schlabach (08/Sep/14 2:26 PM) Assignee: Account App Run by Kohsuke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23665) Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password
Torsten Schlabach updated JENKINS-23665 Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password Change By: Torsten Schlabach (08/Sep/14 2:23 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot] (JENKINS-24628) IRC bot forgets aliases at each restart.
David Britton created JENKINS-24628 IRC bot forgets aliases at each restart. Issue Type: Bug Assignee: kutzi Components: ircbot Created: 08/Sep/14 2:38 PM Description: When the bot re-joins channel (for instance on a configuration change), it forgets all the aliases you have defined. It would be very benefitial if you could hardcode these aliases somewhere, or if it would automatically save them. As you have the ability to list and delete them, it seems the only thing missing is persistence. Environment: Linux, Ubuntu 14.04 Project: Jenkins Priority: Major Reporter: David Britton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot] (JENKINS-24628) IRC bot forgets aliases at each restart.
kutzi updated JENKINS-24628 IRC bot forgets aliases at each restart. Change By: kutzi (08/Sep/14 2:44 PM) Issue Type: Bug New Feature 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [grails] (JENKINS-24629) Incorrect quoting of environment variables
Aron Sedlack created JENKINS-24629 Incorrect quoting of environment variables Issue Type: Bug Affects Versions: current Assignee: jeffg2one Components: grails Created: 08/Sep/14 3:03 PM Description: To reproduce: Add a build parameter with a value that contains a space. The plugin will pass: "-Dvar=value" The quoting for that statement results in Grails parsing anything after the space incorrectly. Possible fix: "-Dvar=\"value\"" Project: Jenkins Priority: Trivial Reporter: Aron Sedlack This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12543) CliAuthenticator (username/password) called too late to parse arguments (like job names)
Christophe LACOMBE commented on JENKINS-12543 CliAuthenticator (username/password) called too late to parse arguments (like job names) Hope we will have soon a fix for this old bug Having all jobs that need to be run from Jenkins-cli.jar to have read access for anonymous, is not a good thing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19760) Long hyperlinks in build description not displayed correctly in history widget when using Markdown syntax
Daniel Beck assigned JENKINS-19760 to Daniel Beck Long hyperlinks in build description not displayed correctly in history widget when using Markdown syntax Change By: Daniel Beck (08/Sep/14 3:35 PM) Assignee: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19760) Long hyperlinks in build description not displayed correctly in history widget when using Markdown syntax
Daniel Beck updated JENKINS-19760 Long hyperlinks in build description not displayed correctly in history widget when using Markdown syntax Change By: Daniel Beck (08/Sep/14 3:35 PM) Summary: Long hyperlinks in build description not displayed correctly on project page in history widget when using Markdown syntax Labels: build markup - description html markdown pegdown formatter Assignee: bap Component/s: www Component/s: pegdown-formatter-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19760) Long hyperlinks in build description not displayed correctly on project page when using Markdown syntax
Daniel Beck commented on JENKINS-19760 Long hyperlinks in build description not displayed correctly on project page when using Markdown syntax Thanks, now it's clear that it's about the automatic truncating of build descriptions in the history widget. hudson/widgets/HistoryWidget/entry.jelly calls app.markupFormatter.translate(build.truncatedDescription) and Run.getTruncatedDescription operates on the raw text when determining where to truncate, so the markup formatter receives an incomplete format string. Should probably add MarkupFormatter.translateAndTruncate(String markup, Writer output, int maxLength) for this case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-24630) Exception when opening JobConfigurationHistory that have changed operation
Christophe LACOMBE created JENKINS-24630 Exception when opening JobConfigurationHistory that have changed operation Issue Type: Bug Affects Versions: current Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 08/Sep/14 3:44 PM Description: When I open the jobConfigurationHistory of a job that have changed operation I have the following exception: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.579.jar!/lib/layout/main-panel.jelly:36:21: hudson/maven/MavenModule at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81
[JIRA] [ldap] (JENKINS-24623) LDAP AcceptSecurityContext error
Daniel Beck commented on JENKINS-24623 LDAP AcceptSecurityContext error A simple web search for the error reveals that error 59, data 0x52e indicates invalid credentials (e.g. this or this), and based on the documentation for manager DN you're entering the value in a wrong format. Don't know about you, but that looks like a configuration error to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-22885) Creation of Inheritance Project throws Exception
Vladimir Kralik commented on JENKINS-22885 Creation of Inheritance Project throws Exception I've two Jenkins servers on Linux Machine, both are 1.579. Inheritance plugin has version 1.5.3 on both machines. One was upgrade from 1.5.1, second was fresh installation. This bug appears only on one of that machine , that with fresh installation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-22885) Creation of Inheritance Project throws Exception
Vladimir Kralik
commented on JENKINS-22885
Creation of Inheritance Project throws Exception
Workaround ?
http://${HOST}/configureSecurity/
set Markup Formatter = "Safe 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
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Cletus D'Souza resolved JENKINS-14703 as Cannot Reproduce PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin Change By: Cletus D'Souza (08/Sep/14 4:22 PM) Status: Open Resolved Fix Version/s: current Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Cletus D'Souza commented on JENKINS-14703 PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin Thanks for the update Martin! While I agree the SQL exception could be better parsed, as you can see there is not much in the exception itself. Unless someone has a code they can contribute to better diagnosing the exception, I'm going to close this issue as I don't have a way to reproduce this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-24631) Credentials store API cannot browse into domains
Johannes Wienke created JENKINS-24631 Credentials store API cannot browse into domains Issue Type: Bug Assignee: stephenconnolly Components: credentials Created: 08/Sep/14 4:22 PM Description: When using the API for the credentials store it is not possible to directly browse into all domains via the depth request parameter. Accessing https://example.com/credential-store/api/xml results in the follwing useless document: And giving any depth parameter like https://example.com/credential-store/api/xml?depth=1 results in an exception: javax.servlet.ServletException: java.lang.IllegalArgumentException: wrong number of arguments at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.j
[JIRA] [credentials] (JENKINS-24632) Include username and descriptions in API output for credential pairs
Johannes Wienke created JENKINS-24632 Include username and descriptions in API output for credential pairs Issue Type: Improvement Assignee: stephenconnolly Components: credentials Created: 08/Sep/14 4:26 PM Description: Currently, when listing credentials inside a domain using the XML API you receive something like this: credential-store/Domain Name/b935f3cc-8a17-4f62-b567-b4e7b7a1d76e Username with password ... Please include the username and description in the output for each pair, comparable to what is visible for normal users when they are selecting the credentials to use in their jobs. Otherwise, it is hard to automatically do configuration updates for jobs that require authentication. Project: Jenkins Priority: Major Reporter: Johannes Wienke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23299) Project building from tag builds at each polling interval
Daniel Wille commented on JENKINS-23299 Project building from tag builds at each polling interval I still see Jenkins using the "-h" in polling. I'm using git-client 1.10.1 and git 2.2.5 at the moment. It does appear to strip the "-h" when I prefix with refs/tags. Is it intentional that the "-h" is only removed there and not globally? That aside, you're right about that tag issue. I'd initially only considered lightweight (i.e. not annotated) tags, which don't have their own object. Adding a suffix of "~0" or "^0" when using a tag will de-reference the tag and get the commit it refers to for many git operations, but that doesn't appear to work with "git ls-remote". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rbenv] (JENKINS-24633) Rbenv plugin sometimes does not release lock correctly
Joseph Hughes created JENKINS-24633 Rbenv plugin sometimes does not release lock correctly Issue Type: Bug Assignee: Unassigned Components: rbenv Created: 08/Sep/14 4:51 PM Description: In cases where a build throws an exception, a gem does not install correctly, or rbenv does not install correctly, or sometimes just randomly the .rbenv_lock file is left in the home directory of the build executer. To fix this issue the teardown mechanism should be used to ensure if a build created the lock, the build releases the lock for other projects to continue to use rbenv on the executer. Project: Jenkins Priority: Minor Reporter: Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24626) Unable to CopyArtifact from builds using older CopyArtifact plugin
Daniel Beck commented on JENKINS-24626 Unable to CopyArtifact from builds using older CopyArtifact plugin Regarding the blocker priority, can't you just downgrade the plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-24631) Credentials store API cannot browse into domains
Daniel Beck commented on JENKINS-24631 Credentials store API cannot browse into domains Confirmed on Jenkins 1.565.2 with Credentials 1.16.1, SSH Credentials 1.19. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [distfork] (JENKINS-16200) Duration parameter doesn't work
Daniel Beck assigned JENKINS-16200 to Daniel Beck Duration parameter doesn't work Change By: Daniel Beck (08/Sep/14 5:36 PM) Assignee: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [distfork] (JENKINS-16200) Duration parameter doesn't work
Daniel Beck started work on JENKINS-16200 Duration parameter doesn't work Change By: Daniel Beck (08/Sep/14 5:36 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [distfork] (JENKINS-16200) Duration parameter doesn't work
Daniel Beck commented on JENKINS-16200 Duration parameter doesn't work Download the HPI file with the fix from here while it's hot: https://jenkins.ci.cloudbees.com/job/plugins/job/distfork-plugin/2/org.jenkins-ci.plugins$distfork/artifact/org.jenkins-ci.plugins/distfork/1.4-SNAPSHOT/ Who knows when this will be merged and a new version released, if ever. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket] (JENKINS-23681) Error on parsing POST requests
Jeffrey Mendez commented on JENKINS-23681 Error on parsing POST requests I'm seeing a similar error when using wget to POST a config.xml change. It's the same java.lang.reflect.InvocationTargetException exception, but caused by a different exception: Caused by: java.lang.IllegalStateException: STREAMED at org.eclipse.jetty.server.Request.getReader(Request.java:898) at javax.servlet.ServletRequestWrapper.getReader(ServletRequestWrapper.java:256) at javax.servlet.ServletRequestWrapper.getReader(ServletRequestWrapper.java:256) at hudson.model.AbstractItem.doConfigDotXml(AbstractItem.java:598) ... 81 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23299) Project building from tag builds at each polling interval
Mark Waite
commented on JENKINS-23299
Project building from tag builds at each polling interval
It is intentional that the "-h" is only dropped when the "refs/tags/tag_name" syntax is used, since that syntax was a new addition and we were not confident we could predict all the side effects if we removed the "-h" from the general case.
There is a suffix we can add which does resolve with ls-remote. It is
git ls-remote tag_name^{}
I haven't yet looked to see if that is safe for both annotated and lightweight tags. If not, then it might require two calls to "git ls-remote" in the refs/tags case, once for annotated tags and once for lightweight tags.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24607) Need ability to build changes sequentially
Michael Rose commented on JENKINS-24607 Need ability to build changes sequentially I like your idea Morne Joubert, but that still seems more reactive. The nightly build has already failed, and now users that needed that build are on standby waiting while analysis is being done to figure out which change caused the problem. In the approach I described above there are two separate Jenkins projects; one that triggers each time a change is submitted (an incremental build) and one that triggers nightly (a full build). The old Perforce plugin had an environment variable (P4ONECHANGELIST) that when set to true tells Jenkins to use the next changes after the one that was last built (as opposed to the head revision). This was set to true for the incremental builds and ensures that each build is just for one change so there is less ambiguity when the build fails (it's either the fault of the author of the change or the fault of the build system). We are not worried about the extra build time required to do it this way b/c right now we have a lot of idle build servers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Toru Takahashi commented on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list > You can't directly select the ant javac parser. It is part of the sub-set of the javac parsers. I see the proper settings for ant javac is to select 'Java Compiler (javac)' parser. Then, I have tried to use warnings plugin the following cases. 1) Linux, Jenkins 1.568, Warnings plugin 4.41, compiler option "-Xlint" 2) Linux, Jenkins 1.568, Warnings plugin 4.41, compiler option "-Xlint -J-Duser.language=en" 3) Windows, Jenkins 1.578, Warnings plugin 4.41, compiler option "-Xlint" 4) Windows, Jenkins 1.578, Warnings plugin 4.41, compiler option "-Xlint -J-Duser.language=en" Notes: My environment is japanese(user.language=ja), and javac output message is internationalized, especially 'warning' is '警告'. The results are as follows: 1) Good 2) Good 3) Bad 4) Good This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24591) Unable to run perforce commands within build steps
Michael Rose commented on JENKINS-24591 Unable to run perforce commands within build steps I could live with just the P4USER and P4PORT being exposed in the build environment and you could even use a separate variable name similar to what you're doing with P4CLIENT (e.g. P4_USER, P4_PORT). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Toru Takahashi edited a comment on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list > You can't directly select the ant javac parser. It is part of the sub-set of the javac parsers. I see the proper settings for ant javac is to select 'Java Compiler (javac)' parser. Then, I have tried to use warnings plugin the following cases. 1) Linux, Jenkins 1.568, Warnings plugin 4.41, compiler option "-Xlint" 2) Linux, Jenkins 1.568, Warnings plugin 4.41, compiler option "-Xlint -J-Duser.language=en" 3) Windows, Jenkins 1.578, Warnings plugin 4.41, compiler option "-Xlint" 4) Windows, Jenkins 1.578, Warnings plugin 4.41, compiler option "-Xlint -J-Duser.language=en" Notes: My environment is japanese(user.language=ja), and javac output message is internationalized, especially 'warning' is '警告'. The results and row log file name attached are as follows: 1) Good, 24611_case1.log 2) Good, 24611_case2.log 3) Bad, 24611_case3.log 4) Good, 24611_case4.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24607) Need ability to build changes sequentially
Morne Joubert commented on JENKINS-24607 Need ability to build changes sequentially I am all for both methods, in fact the best setup would be to use both as you suggested. If you can build very quickly and there is a lot of changes , then yes the sequential builds is needed. and that is why i voted for it. But if the build takes an hour then sequential builds can take too long. That is why i use to do an overnight test (say midnight) to build with a lot of changes and then do the binary chopping. So by 1am the system knows that somewhere in forexample 20 changes there is an error. It would take using binary chop (20/10/5/2) 4 hours for the system to nail the culprit! So by 6 am the morning everyone knows who broke the longs builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Toru Takahashi updated JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list Change By: Toru Takahashi (08/Sep/14 6:56 PM) Attachment: 24611_case1.log Attachment: 24611_case2.log Attachment: 24611_case3.log Attachment: 24611_case4.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Toru Takahashi edited a comment on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list > You can't directly select the ant javac parser. It is part of the sub-set of the javac parsers. I see the proper settings for ant javac is to select 'Java Compiler (javac)' parser. Then, I have tried to use warnings plugin the following cases. 1) Linux, Jenkins 1.568, Warnings plugin 4.41, compiler option "-Xlint" 2) Linux, Jenkins 1.568, Warnings plugin 4.41, compiler option "-Xlint -J-Duser.language=en" 3) Windows, Jenkins 1.578, Warnings plugin 4.41, compiler option "-Xlint" 4) Windows, Jenkins 1.578, Warnings plugin 4.41, compiler option "-Xlint -J-Duser.language=en" Notes: My environment is japanese(user.language=ja), and javac output message is internationalized, especially 'warning' is '警告'. The results and row log file name attached are as follows: 1) Good, 24611_case1.log 2) Good, 24611_case2.log 3) Bad, 24611_case3.log 4) Good, 24611_case4.log For OS encoding, Linux default encoding is UTF-8. Windows default encoding is not UTF-8 but windows-31j (CP932). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Michael Rose
commented on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Hi [~pallen], have you had a chance to look more into this?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Michael Rose
edited a comment on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Hi Paul Allen, have you had a chance to look more into this?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-20056) When deleting the entire workspace, perform it asynchronously
Oliver Gondža commented on JENKINS-20056 When deleting the entire workspace, perform it asynchronously https://github.com/jenkinsci/ws-cleanup-plugin/pull/20 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-18137) null value for project workspace location
Oliver Gondža
commented on JENKINS-18137
null value for project workspace location
The {null} values has nothing to do with workspace, the logic[1] that prints exceptions is wrong. Fixed as a side-effect of https://github.com/jenkinsci/ws-cleanup-plugin/pull/20/files.
I am tempted to close this issue as the cause of exceptions is unknown and can even be different in each case.
[1] https://github.com/jenkinsci/ws-cleanup-plugin/blob/master/src/main/java/hudson/plugins/ws_cleanup/PreBuildCleanup.java#L106-109
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-24634) Multi-Level Single Select does not set variables for all dropdown items
Michael Dobrindt created JENKINS-24634 Multi-Level Single Select does not set variables for all dropdown items Issue Type: Bug Affects Versions: current Assignee: vimil Components: extended-choice-parameter Created: 08/Sep/14 8:31 PM Description: When setting up a Multi-Level Single Select there is first the name of the Parameter. Let's call this PARAM_NAME. Then there is the Value. Here you can fill in multiple values and for each one listed a drop down menu will appear. Lets call these VALUE1,VALUE2. When the job is launched the only Environment Variable that is set is PARAM_NAME and it is set to the the value of whatever VALUE2 was selected. There should be a variable set (excluding PARAM_NAME) for each Value listed. So that when you run your job you would see the following environment variables: PARAM_NAME = VALUE1 = VALUE2 = ... Project: Jenkins Priority: Major Reporter: Michael Dobrindt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24546) Git plugin doesn't use environment variables when running git for polling
eguess74 commented on JENKINS-24546 Git plugin doesn't use environment variables when running git for polling Alright, i got to the end of it: the probelm as i see it was in the fact that in .bashrc for the user under which the Jenkins and the slaves are operating i had the LD_LIBRARY_PATH specified incorrectly (it was missing the folder from which git executable was linking the libraries). In this case nothing can be done in Jenkins GUI on the configuration side in order to override this varaible on the slave. It is always last thing to run before the execution of the command. So effectively i had a situation when if the job is rebuit on master node where the LD_LIBRARY_PATH was correct then the next poll of this project was successful. Now the interesting part is that as soon as the job was rebuilt on a slave with incorrrect LD_LIBRARY_PATH, then the next poll was failing! So as far as i understand this behaviour contradicts to what is claimed - git polling seems to pick up latest known environment, but not the one from master node. In order to check where the libraries are found by git executable you can run "ldd /path/to/git" It will show the list wof libraries used and where are they taken from, then if you will ovverride LD_LIBRARY_PATH and exclude one of the folders from the list it shoudl start failing with the error finding the libs. hope that helps This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket] (JENKINS-23681) Error on parsing POST requests
Jeffrey Mendez edited a comment on JENKINS-23681 Error on parsing POST requests I'm seeing a similar error when using wget to POST a config.xml change. I'm trying to modify a build job in a shell script by retrieving the config.xml using wget, modifying the config.xml, and then posting the modified config.xml using wget. This was working in the beginning of August, but now I'm getting HTTP 500 server error. In the Jenkins log, I'm getting the same java.lang.reflect.InvocationTargetException exception, but caused by a different exception: java.lang.reflect.InvocationTargetException Caused by: java.lang.IllegalStateException: STREAMED at org.eclipse.jetty.server.Request.getReader(Request.java:898) at javax.servlet.ServletRequestWrapper.getReader(ServletRequestWrapper.java:256) at javax.servlet.ServletRequestWrapper.getReader(ServletRequestWrapper.java:256) at hudson.model.AbstractItem.doConfigDotXml(AbstractItem.java:598) ... 81 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24546) Git plugin doesn't use environment variables when running git for polling
Mark Waite commented on JENKINS-24546 Git plugin doesn't use environment variables when running git for polling I haven't checked the source code to be sure, but it is possible that the plugin chooses an existing repository if one is available for polling. Can we close this as "Not a defect"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-24635) doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Nikolai Colton
created JENKINS-24635
doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
jenkinswalldisplay
Created:
08/Sep/14 9:34 PM
Description:
When the wall display is active, stack traces spam the logs at ridiculously high speeds.
JENKINS-24458 has details on the behavior.
From doing a test, I've narrowed it down to the code block shown below:
walldisplay.js:632
$.ajax({
url: jenkinsUrl + "/view/" + viewName + "/api/json",
dataType: 'json',
data: {
"depth": 1
},
The reference on GitHub walldisplay.js#L632
When this call is made (http://…/view//api/json?depth=1) then the logs are hammered by tracebacks, in some cases using hundreds of megabytes in a matter of a few minutes.
Project:
Jenkins
Priority:
Critical
Reporter:
Nikolai Colton
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-9741) Copy artifact loses file permissions
Tom Sackett commented on JENKINS-9741 Copy artifact loses file permissions There is still a problem to fix. I'm still seeing the problem of artifacts losing their executable permissions. I also notice that the current release notes include this under "Known Issues": "Filesystem permissions of artifacts are only preserved in the copy when using the "flatten" option". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-24590) Set the pull request number as an environment variable
Everett Toews commented on JENKINS-24590 Set the pull request number as an environment variable Confirmed. Thanks! There's a ton of useful information in there. echo "ghprbPullId=$ghprbPullId" echo "sha1=$sha1" echo "ghprbActualCommit=$ghprbActualCommit" echo "ghprbTargetBranch=$ghprbTargetBranch" echo "ghprbSourceBranch=$ghprbSourceBranch" echo "ghprbPullAuthorEmail=$ghprbPullAuthorEmail" echo "ghprbPullDescription=$ghprbPullDescription" echo "ghprbPullTitle=$ghprbPullTitle" echo "ghprbPullLink=$ghprbPullLink" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-24590) Set the pull request number as an environment variable
Everett Toews resolved JENKINS-24590 as Not A Defect Set the pull request number as an environment variable These are already there. Documented in the Environment Variables section. Change By: Everett Toews (08/Sep/14 11:20 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-9741) Copy artifact loses file permissions
ikedam commented on JENKINS-9741 Copy artifact loses file permissions Could you report more details of your problem? Especially, I want to know your OS and whether you use distributed build (master / slave). Copyartifact completely changed the copying mechanism in 1.21. Almost all comments in this page are already outdated, and I want to know problems with the latest version. I'll try to add automated tests for file permissions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-9741) Copy artifact loses file permissions
ikedam commented on JENKINS-9741 Copy artifact loses file permissions That known issue was added in 1.17, and may be outdated. https://wiki.jenkins-ci.org/pages/diffpagesbyversion.action?pageId=42470728&selectedPageVersions=33&selectedPageVersions=32 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-3002) TFS Support to get labels
Vinicius Kopcheski commented on JENKINS-3002 TFS Support to get labels Hi, Victor. Sorry, but I don't have this information. You should ask to the maintainers. Please check their e-mail in here: https://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24394) Gerrit trigger plugin doesnt update Gerrit with review comments using the latest Gerrit code base
rin_ne resolved JENKINS-24394 as Won't Fix Gerrit trigger plugin doesnt update Gerrit with review comments using the latest Gerrit code base It's known issue and solution is already given. https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-NotetoGerrit2.6Users Change By: rin_ne (09/Sep/14 5:42 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameters] (JENKINS-24636) upload file via CLI build a job with file parameter fail, if the file is large and the server is a windows machine
Jerry WANG created JENKINS-24636 upload file via CLI build a job with file parameter fail, if the file is large and the server is a windows machine Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: parameters Created: 09/Sep/14 6:03 AM Description: In Jenkins server, replica_data configured in a job as a file parameter. From clinet node, use command java -jar jenkins-cli.jar -s http://server:8080/ build retrive_data -p replica_data=dummy.txt It will be success if the dummy.txt is 2M. When it is 64M, the above command will fail as: SEVERE: I/O error in channel Chunked connection to http://server:8080/cli java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown Source) at java.io.ObjectInputStream.readStreamHeader(Unknown Source) at java.io.ObjectInputStream.(Unknown Source) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Sep 09, 2014 3:12:02 PM hudson.remoting.Request$2 run SEVERE: Failed to send back a reply java.io.IOException: Error writing request body to server at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(Unknown Source) at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:85) at hudson.remoting.ChunkedOutputStream.sendBreak(ChunkedOutputStream.java:66) at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:45) at hudson.remoting.Channel.send(Channel.java:545) at hudson.remoting.Request$2.run(Request.java:342) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Exception in thread "main" hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy3.main(Unknown Source) at hudson.cli.CLI.execute(CLI.java:331) at hudson.cli.CLI._main(CLI.java:489) at hudson.cli.CLI.main(CLI.java:382) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown
[JIRA] [copyartifact] (JENKINS-24626) Unable to CopyArtifact from builds using older CopyArtifact plugin
Tom Ghyselinck commented on JENKINS-24626 Unable to CopyArtifact from builds using older CopyArtifact plugin Hi Daniel, Thank you for the quick reply. Yes, we could do so, but meanwhile we also have a lot of builds which used the newer Copy Artifact Plugin. We also need some bug fixes and features from the new version. Maybe it's quite easy to disable the version check or to add some backward compatibility? Thank you in advance! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
