[JIRA] [buildgraph-view-plugin] (JENKINS-29779) Build dependency graph
Title: Message Title Radek Chromy created an issue Jenkins / JENKINS-29779 Build dependency graph Issue Type: Bug Assignee: Unassigned Components: buildgraph-view-plugin Created: 04/Aug/15 1:47 PM Environment: buildgraph-1.1.1 jenkins 1.509.4 Labels: plugin gui Priority: Minor Reporter: Radek Chromy When triggered build has removed history build, Build Graph plugin shows empty page. job1 #10 - job2 #20 when job1 #20 is removed, build graph on job1 #10 is empty In _javascript_ console is error: prototype.js:5798 Uncaught TypeError: element.dispatchEvent is not a function breadcrumbs.js:159 Uncaught TypeError: e.hasClassName is not a function
[JIRA] [ghprb] (JENKINS-22509) ghprb requires restart Jenkins when authTokens are changed in configuration
Radek Chromy created JENKINS-22509 ghprb requires restart Jenkins when authTokens are changed in configuration Issue Type: Bug Affects Versions: current Assignee: Honza Brázdil Components: ghprb Created: 04/Apr/14 4:53 PM Description: When github oauth tokens are regenerated and updated in jenkins configuration, ghprb plugin still uses the old configuration and does not tries to reconnect with new one. Jenkins has to be restarted to apply new settings. Project: Jenkins Labels: plugins Priority: Major Reporter: Radek Chromy This message is automatically generated by JIRA. 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-11962) Symlinking lastSuccessful build shouldn't fail with concurrent jobs
Radek Chromy updated JENKINS-11962 Symlinking lastSuccessful build shouldnt fail with concurrent jobs Change By: Radek Chromy (23/Apr/13 12:19 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-11962) Symlinking lastSuccessful build shouldn't fail with concurrent jobs
Radek Chromy updated JENKINS-11962 Symlinking lastSuccessful build shouldnt fail with concurrent jobs Change By: Radek Chromy (23/Apr/13 12:21 PM) Labels: artifactjenkins 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/groups/opt_out.
[JIRA] (JENKINS-17232) Jenkins mixes-up form fields when Back browser button is used
Radek Chromy created JENKINS-17232 Jenkins mixes-up form fields when Back browser button is used Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 15/Mar/13 2:55 PM Description: Do the following: Goto an parametrized job start page. Fill-out all paramteters fields Start the task Go to the task's console Use browser's Back button to return to the task start page. The form seems to be filled in, but the values are mixed between fields. E.g. The previous PARAM1 value is now in the PARAM2 field. This makes reusing the form very difficult and error-prone, as upon a first look the form seems to be filled correctly. Project: Jenkins Labels: jenkins Priority: Major Reporter: Radek Chromy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16516) Maked Passwords are shown as input parameters in Build pipeline plugin
Radek Chromy created JENKINS-16516 Maked Passwords are shown as input parameters in Build pipeline plugin Issue Type: Bug Affects Versions: current Assignee: Daniel Petisme Components: build-pipeline, mask-passwords Created: 29/Jan/13 9:51 AM Description: 1. I have configured global parameters for masking passwords. Plugin: Mask Passwords Plugin 2. I have created job and enable mask password 3. I have created build pipeline view. Plugin: Build Pipeline Plugin with the first job with masked passwords. The result was, that the input parameters contains masked password in plaintext in the pipeline view. Project: Jenkins Labels: plugins Priority: Critical Reporter: Radek Chromy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16242) Github pull request builder - branch to merged before build
Radek Chromy created JENKINS-16242 Github pull request builder - branch to merged before build Issue Type: Improvement Assignee: Honza Brázdil Components: github, plugin Created: 02/Jan/13 4:21 PM Description: Can the plugin be extended by merging to the branch where the pull is created to? Use Case: Assume git repository with 2 branches: master stable01 Create pull requests to merge to any of branch. Need to run build of the pull request with merge to the target branch. Project: Jenkins Labels: plugin Priority: Critical Reporter: Radek Chromy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15134) Different icons for offline and idle nodes
Radek Chromy created JENKINS-15134 Different icons for offline and idle nodes Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: slave-status Created: 12/Sep/12 12:05 PM Description: It would be nice to have different icons for offline nodes and idle nodes: idle slave (waits for job to run) offline slave (computer offline/unreachable) I use "http://my_jenkins/computer/" overview with more than 100 nodes - there is not possible to say, which node is offline because of computer down or because of slave is idle. Project: Jenkins Labels: jenkins Priority: Major Reporter: Radek Chromy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-850) search box should match non-casesensitively
[ https://issues.jenkins-ci.org/browse/JENKINS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162886#comment-162886 ] Radek Chromy commented on JENKINS-850: -- It seems to be platform/environment depended: Jenkins ver. 1.464 Linux Ubuntu 12.04, Chromium 18.0.1025.151, search is case *insensitive*. Mac OS X 10.7.3 a Chrome Version 19.0.1084.46, search is case *sensitive*. search box should match non-casesensitively --- Key: JENKINS-850 URL: https://issues.jenkins-ci.org/browse/JENKINS-850 Project: Jenkins Issue Type: Improvement Components: www Affects Versions: current Environment: Platform: All, OS: All Reporter: gradopado Assignee: dogfood The search box would be even more useful if it would match text non-casesensitively. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12920) LDAP autentication has incorrect credentials for user
Radek Chromy created JENKINS-12920:
--
Summary: LDAP autentication has incorrect credentials for user
Key: JENKINS-12920
URL: https://issues.jenkins-ci.org/browse/JENKINS-12920
Project: Jenkins
Issue Type: Bug
Components: security
Affects Versions: current
Environment: Jenkins ver. 1.451
Reporter: Radek Chromy
We have company LDAP server with all users, I have tried to configure Jenkins
to use this LDAP database, but user login fails with exception in jenkins.log
(see bellow)
Problem:
Our LDAP identify user by uid token, but in log file there is some
userDnuid, which is not supported. There is no possible to configure mapping
user to another token.
Jenkins configuration:
- User search filter: uid={0} ... this explicit setting does not help either
---
WARNING: Failed to bind to LDAP:
userDnuid=myname,ou=Account,dc=mycompany,dc=com username=myname
javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid
Credentials]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3032)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2978)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2780)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2694)
at com.sun.jndi.ldap.LdapCtx.init(LdapCtx.java:306)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
at
com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
at
com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
at
com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
...
INFO: Login attempt failed
org.acegisecurity.BadCredentialsException: Bad credentials
at
org.acegisecurity.providers.ldap.authenticator.BindAuthenticator.authenticate(BindAuthenticator.java:76)
at
org.acegisecurity.providers.ldap.authenticator.BindAuthenticator2.authenticate(BindAuthenticator2.java:49)
at
org.acegisecurity.providers.ldap.LdapAuthenticationProvider.retrieveUser(LdapAuthenticationProvider.java:233)
at
org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:119)
at
org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:195)
at
org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:45)
at
org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:71)
at
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
