[JIRA] [core] (JENKINS-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Daniel Beck commented on JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions Changing the code of each plugin itself? Yes. what is running every few seconds that would be trying to export? (We run a very vanilla Jenkins installation and were surprised to see this.) The logged stack trace should have a call to a doApi method somewhere, which corresponds to the .../api/(xml|json) URLs. Someone's using the Jenkins REST API. This message is automatically generated by JIRA. 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] [groovy-postbuild] (JENKINS-15210) Add variable resolution to additional groovy class path
Sebastian Schuberth commented on JENKINS-15210 Add variable resolution to additional groovy class path BTW, as a work-around, it should be possible to use Groovy's evaluate() 1 instead of tampering with the classpath. 1 http://stackoverflow.com/a/9154553/1127485 This message is automatically generated by JIRA. 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] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete
Alex Earl commented on JENKINS-23660 Attached log in Jenkins email incomplete It will be in 2.39 This message is automatically generated by JIRA. 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-24575) The instance of extension class should not be kept
rin_ne updated JENKINS-24575 The instance of extension class should not be kept Change By: rin_ne (04/Sep/14 7:35 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/ 174 175 This message is automatically generated by JIRA. 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] [allure-jenkins] (JENKINS-24481) Could not deleting files/folder in workspace
Marat Mavlyutov resolved JENKINS-24481 as Duplicate Could not deleting files/folder in workspace duplicates JENKINS-15331 Change By: Marat Mavlyutov (04/Sep/14 9:29 AM) Status: Open Resolved Assignee: ArtemEroshenko MaratMavlyutov 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] [active-directory] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
Justinas Urbanavicius commented on JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException can't really remember but i think with angry jenkins, it looks familiar This message is automatically generated by JIRA. 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] [active-directory] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
Daniel Beck commented on JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException The problem is that, especially given how extensible Jenkins is, accounting for all possible failures is impossible. So some will show the angry Jenkins error page. Note also that this page is way more helpful to many users (and the developers handling the error report later) than a nice, but uninformative "an error occurred that we assume is vague related to authentication" page could ever be. I'm currently working on improving that page (e.g. actually link to the wiki page explaining how to report issues and how the Jenkins project uses Jira), and will incorporate a simpler error message in addition to the full stack trace. It would probably look like one of the following in your case: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: my.domainserver.xx:389 Root exception is java.net.ConnectException: Connection refused] Failed to retrieve user information for jusurb; nested exception is [Root exception is: my.domainserver.xx:389 Root exception is: Connection refused] While still not ideal, it's clear from either that it's a network connection issue involving your AD server, and the user jusurb. This message is automatically generated by JIRA. 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] [junit] (JENKINS-24580) Older and Newer buttons should be flipped
Rick Oosterholt updated JENKINS-24580 Older and Newer buttons should be flipped Change By: Rick Oosterholt (04/Sep/14 11:47 AM) Attachment: JENKINS-24580.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] [rqm] (JENKINS-24553) Missing summary section in plugin (our case 11935)
Yakup Kariksiz assigned JENKINS-24553 to Praqma Support Missing summary section in plugin (our case 11935) Change By: Yakup Kariksiz (04/Sep/14 12:17 PM) Assignee: YakupKariksiz PraqmaSupport This message is automatically generated by JIRA. 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] [jacoco] (JENKINS-24570) Jenkins Jacoco plugin - Coverage report goes missing after couple of hours
Kumar Pratik closed JENKINS-24570 as Duplicate Jenkins Jacoco plugin - Coverage report goes missing after couple of hours Change By: Kumar Pratik (04/Sep/14 10:40 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [s3] (JENKINS-24576) option to fail the build when selector didn't selected any file to deploy
Steven Christou commented on JENKINS-24576 option to fail the build when selector didnt selected any file to deploy This should be fixed as part of https://github.com/jenkinsci/support-core-plugin/commit/057dcdca67065aefada209bfb3ba21fab4316ee2. This message is automatically generated by JIRA. 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-24412) Do not save config for matrix configurations
Stefan Brausch resolved JENKINS-24412 as Fixed Do not save config for matrix configurations Version 2.9 is released now Change By: Stefan Brausch (04/Sep/14 7:14 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [view-job-filters] (JENKINS-24579) Filter based on Job Labels
Richard Zamponi created JENKINS-24579 Filter based on Job Labels Issue Type: New Feature Assignee: Jacob Robertson Components: view-job-filters Created: 04/Sep/14 11:29 AM Description: As Nodes have Lables it would be handy that Jobs have those too. That way it would be possible to define groups a Job belongs to and to filter against. Project: Jenkins Priority: Major Reporter: Richard Zamponi This message is automatically generated by JIRA. 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] [maven2] (JENKINS-3122) auto build of downstream projects doesn't workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore
Justin Wesley commented on JENKINS-3122 auto build of downstream projects doesnt workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore I'm with @Adam H on this one. I want the build to be yellow if I have test failures, but still want downstream jobs to run as well. This message is automatically generated by JIRA. 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] [rqm] (JENKINS-24553) Missing summary section in plugin (our case 11935)
Mads Nielsen resolved JENKINS-24553 as Fixed Missing summary section in plugin (our case 11935) Change By: Mads Nielsen (04/Sep/14 11:48 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [groovy-postbuild] (JENKINS-15210) Add variable resolution to additional groovy class path
Sebastian Schuberth commented on JENKINS-15210 Add variable resolution to additional groovy class path Looks like addressing this would possibly interfere with the pending pull request to integrate with the Script Security plugin 1. I've posted a comment / question to the PR to get some more details. 1 https://github.com/jenkinsci/groovy-postbuild-plugin/pull/11 This message is automatically generated by JIRA. 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] [s3] (JENKINS-24576) option to fail the build when selector didn't selected any file to deploy
Steven Christou edited a comment on JENKINS-24576 option to fail the build when selector didnt selected any file to deploy Ops, sorry wrong ticket comment. This message is automatically generated by JIRA. 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] [rqm] (JENKINS-24578) Too many test scripts found during discovery (case 11942)
Mads Nielsen created JENKINS-24578 Too many test scripts found during discovery (case 11942) Issue Type: Bug Assignee: Praqma Support Components: rqm Created: 04/Sep/14 11:14 AM Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Arpit Nagar commented on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive Any Update ?? This message is automatically generated by JIRA. 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-20879) SSH Credentials (private key with passphrase) do not work
Felix Nawroth commented on JENKINS-20879 SSH Credentials (private key with passphrase) do not work Can you estimate when this will be fixed? To use the SSH Agent plugin as workaround would cost us a lot of configuration effort, since we're building on Windows, too. I can confirm that the Credentials plugin with password-protected SSH keys works well in general, both with key on disc/password in Jenkins and key in Jenkins/password in Jenkins. For example we connect our SSH slaves this way. Only Git fails to use the password-protected keys. This message is automatically generated by JIRA. 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] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne resolved JENKINS-24445 as Fixed Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Change By: rin_ne (04/Sep/14 7:35 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [rqm] (JENKINS-24578) Too many test scripts found during discovery (case 11942)
Mads Nielsen resolved JENKINS-24578 as Fixed Too many test scripts found during discovery (case 11942) Change By: Mads Nielsen (04/Sep/14 11:47 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-24575) The instance of extension class should not be kept
rin_ne resolved JENKINS-24575 as Fixed The instance of extension class should not be kept Change By: rin_ne (04/Sep/14 7:23 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [support-core] (JENKINS-24567) java.lang.IllegalArgumentException: Invalid thread ID parameter: -1
Steven Christou commented on JENKINS-24567 java.lang.IllegalArgumentException: Invalid thread ID parameter: -1 This should be fixed in https://github.com/jenkinsci/support-core-plugin/commit/057dcdca67065aefada209bfb3ba21fab4316ee2. This message is automatically generated by JIRA. 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] [junit] (JENKINS-24580) Older and Newer buttons should be flipped
Rick Oosterholt created JENKINS-24580 Older and Newer buttons should be flipped Issue Type: Bug Assignee: Unassigned Attachments: JENKINS-24580.png Components: junit Created: 04/Sep/14 11:44 AM Description: When viewing the history of test results the "Newer" and "Older" buttons should be flipped. This order just doesn't make sense. Project: Jenkins Priority: Minor Reporter: Rick Oosterholt This message is automatically generated by JIRA. 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-24410) Job config change not saved for maven and matrix projects
Stefan Brausch resolved JENKINS-24410 as Fixed Job config change not saved for maven and matrix projects Version 2.9 is released now Change By: Stefan Brausch (04/Sep/14 7:15 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven] (JENKINS-24572) ClassNotFoundException: org.jvnet.hudson.maven3.listeners.MavenProjectInfo
Daniel Beck commented on JENKINS-24572 ClassNotFoundException: org.jvnet.hudson.maven3.listeners.MavenProjectInfo What's common to the builds that fail? Running on the same node? Is there anything else (like a failure to cache) logged in the system log, or slave 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] [rqm] (JENKINS-24577) Test case execution order not honored (case 11936)
Mads Nielsen created JENKINS-24577 Test case execution order not honored (case 11936) Issue Type: Bug Assignee: Praqma Support Components: rqm Created: 04/Sep/14 8:40 AM Description: We should always sort test-cases in ascending execution order. So that the one with the highest priority is at the top of the list, Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. 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-24575) The instance of extension class should not be kept
rin_ne updated JENKINS-24575 The instance of extension class should not be kept Change By: rin_ne (04/Sep/14 7:23 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/174 This message is automatically generated by JIRA. 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] [s3] (JENKINS-24576) option to fail the build when selector didn't selected any file to deploy
Nicolas De Loof created JENKINS-24576 option to fail the build when selector didnt selected any file to deploy Issue Type: New Feature Assignee: Michael Watt Components: s3 Created: 04/Sep/14 8:04 AM Description: When s3-plugin doesn't select any file, it logs a diagnostic warning but doesn't stop the build marking it as FAILED. For backward compatibility this has to be maintained, but a new option can offer a fail-fast strategy to fail the build when no S3 upload occurred due to a missing file. Project: Jenkins Priority: Minor Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-24582) With the latest version of Jenkins, 1.5.78, the GIT Plugin throws a stack trace for both jobs and configure system. Without the plugin the stack trace is not present
justin mellinger moved JENKINS-24582 With the latest version of Jenkins, 1.5.78, the GIT Plugin throws a stack trace for both jobs and configure system. Without the plugin the stack trace is not present Change By: justin mellinger (04/Sep/14 12:17 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 125 24582 Workflow: jira JNJira Component/s: git Component/s: ci This message is automatically generated by JIRA. 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] [jacoco] (JENKINS-24570) Jenkins Jacoco plugin - Coverage report goes missing after couple of hours
Kumar Pratik resolved JENKINS-24570 as Duplicate Jenkins Jacoco plugin - Coverage report goes missing after couple of hours This is actually duplicated of https://issues.jenkins-ci.org/browse/JENKINS-23708 Change By: Kumar Pratik (04/Sep/14 10:39 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] [gerrit-trigger] (JENKINS-24575) The instance of extension class should not be kept
rin_ne created JENKINS-24575 The instance of extension class should not be kept Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 04/Sep/14 2:54 AM Description: Some classes which is extended from Extension keeps one's instance into one's member. It might cause memory leak after restart. Environment: Jenkins 1.565.1 Gerrit Trigger 2.11.0-beta-4 Project: Jenkins Priority: Critical Reporter: rin_ne This message is automatically generated by JIRA. 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] [dashboard-view] (JENKINS-24583) Regular expression for selecting jobs in dashboard view breaks jenkins
Paulo Matos created JENKINS-24583 Regular _expression_ for selecting jobs in dashboard view breaks jenkins Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 04/Sep/14 1:10 PM Description: Jenkins ver. 1.565.1, dashboard view 2.9.1 Crashes when saving view with regular _expression_: (?rall.). Stack trace javax.servlet.ServletException: java.util.regex.PatternSyntaxException: Unknown inline modifier near index 2 (?rall.*).* ^ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) 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.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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.java:81) at
[JIRA] [gerrit-trigger] (JENKINS-24575) The instance of extension class should not be kept
SCM/JIRA link daemon commented on JENKINS-24575 The instance of extension class should not be kept Code changed in jenkins User: rinrinne Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/dependency/DependencyQueueTaskDispatcher.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/RetriggerAction.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/RetriggerAllAction.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/500bd4dc496a027bc1feac169fd71c304b4ebe32 Log: Don't keep Extension instances All instance of Extension extended class must be fully managed by Jenkins instance. So those must not be reused by other instances. This patch fixes such issue. Targets are: ToGerritRunListener DependencyQueueTaskDispatcher Fix for JENKINS-24575 Task-Url: https://issues.jenkins-ci.org/browse/JENKINS-24575 This message is automatically generated by JIRA. 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] [rqm] (JENKINS-24553) Missing summary section in plugin (our case 11935)
Yakup Kariksiz assigned JENKINS-24553 to Yakup Kariksiz Missing summary section in plugin (our case 11935) Change By: Yakup Kariksiz (04/Sep/14 12:14 PM) Assignee: PraqmaSupport YakupKariksiz This message is automatically generated by JIRA. 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] [rqm] (JENKINS-24577) Test case execution order not honored (case 11936)
Mads Nielsen resolved JENKINS-24577 as Fixed Test case execution order not honored (case 11936) Change By: Mads Nielsen (04/Sep/14 11:47 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-24581) tasks status icon not visible at overview of single task
podskalsky created JENKINS-24581 tasks status icon not visible at overview of single task Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Attachments: 2014-09-04 14_01_07-tagging + release [Jenkins].png Components: core, tasks-plugin Created: 04/Sep/14 12:12 PM Description: The tasks status icon is not visible at overview of single task. I think before the big design updates they where visible. Environment: jenkins 1.57 latest versions of core+plugins latest chrome/firefox/ie8 Project: Jenkins Priority: Major Reporter: podskalsky This message is automatically generated by JIRA. 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Arpit Nagar edited a comment on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive Any Update on 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] [core] (JENKINS-24407) missing weather icons (randomly?)
K P commented on JENKINS-24407 missing weather icons (randomly?) Note that simply reverting jenkins to 1.575 resolves the issue. So obviously someone has just broken something in 1.576. I don't think there were that may commits integrated in 1.576 ?? So there can't be that much source lines involved and it shouldn't be too hard to pinpoint the problem for someone knowing the jenkins code? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-20091) OpenId plugin (Version1.7) is not working, but 1.5 is working
junaid shaikh commented on JENKINS-20091 OpenId plugin (Version1.7) is not working, but 1.5 is working Stack trace javax.servlet.ServletException: org.openid4java.discovery.DiscoveryException: 0x706: Failed to discover OpenID: http://localhost:9090/cfgmgnt.cas.sso/login 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.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) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at
[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I uploaded a new Wireshark log and the Jenkins logcat log. These are matching now (the name of the file should be enough to match the files). At the last Wireshark log I didn't use logcat, so I needed to take a new log. Here the link. https://github.com/ITobiI/Android-Problem-Jenkins/tree/master/WiresharkAndJenkinsLogcat I found the CNXN passage at packet number 296 at the bad log (I didn't see any other CNXN) and number 829 at the good 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] [openid] (JENKINS-20091) OpenId plugin (Version1.7) is not working, but 1.5 is working
junaid shaikh edited a comment on JENKINS-20091 OpenId plugin (Version1.7) is not working, but 1.5 is working Stack trace I get the same error while using openID CAS implementation. Jenkins is able to validate the openID server URL fine and the validation jenkins version: latest 1.578 CAS version: 1.21.6-snapshot Sep 04, 2014 4:13:05 PM org.openid4java.discovery.Discovery discover INFO: Starting discovery on URL identifier: http://localhost:9090/cfgmgnt.cas.sso/login Sep 04, 2014 4:13:05 PM org.openid4java.discovery.yadis.YadisResolver discover INFO: Yadis discovered 0 endpoints from: http://localhost:9090/cfgmgnt.cas.sso/login Sep 04, 2014 4:13:05 PM org.openid4java.discovery.Discovery discover INFO: No OpenID service endpoints discovered through Yadis; attempting HTML discovery... Sep 04, 2014 4:13:05 PM org.openid4java.discovery.html.HtmlResolver discoverHtml INFO: HTML discovery completed on: http://localhost:9090/cfgmgnt.cas.sso/login Sep 04, 2014 4:13:05 PM org.openid4java.discovery.Discovery discover INFO: Discovered 0 OpenID endpoints. Sep 04, 2014 4:14:50 PM org.openid4java.discovery.Discovery discover INFO: Starting discovery on URL identifier: http://localhost:9090/cfgmgnt.cas.sso/login Sep 04, 2014 4:14:50 PM org.openid4java.discovery.yadis.YadisResolver discover INFO: Yadis discovered 0 endpoints from: http://localhost:9090/cfgmgnt.cas.sso/login Sep 04, 2014 4:14:50 PM org.openid4java.discovery.Discovery discover INFO: No OpenID service endpoints discovered through Yadis; attempting HTML discovery... Sep 04, 2014 4:14:50 PM org.openid4java.discovery.html.HtmlResolver discoverHtml INFO: HTML discovery completed on: http://localhost:9090/cfgmgnt.cas.sso/login Sep 04, 2014 4:14:50 PM org.openid4java.discovery.Discovery discover INFO: Discovered 0 OpenID endpoints. Sep 04, 2014 4:14:50 PM org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@1f6f1c28: display name [Root WebApplicationContext]; startup date [Thu Sep 04 16:14:50 CEST 2014]; root of context hierarchy Sep 04, 2014 4:14:50 PM org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@1f6f1c28]: org.springframework.beans.factory.support.DefaultListableBeanFactory@2cf823f Sep 04, 2014 4:14:50 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@2cf823f: defining beans [filter,legacy]; root of factory hierarchy Sep 04, 2014 4:15:35 PM org.openid4java.discovery.Discovery discover INFO: Starting discovery on URL identifier: http://localhost:9090/cfgmgnt.cas.sso/login Sep 04, 2014 4:15:35 PM org.openid4java.discovery.yadis.YadisResolver discover INFO: Yadis discovered 0 endpoints from: http://localhost:9090/cfgmgnt.cas.sso/login Sep 04, 2014 4:15:35 PM org.openid4java.discovery.Discovery discover INFO: No OpenID service endpoints discovered through Yadis; attempting HTML discovery... Sep 04, 2014 4:15:35 PM org.openid4java.discovery.html.HtmlResolver discoverHtml INFO: HTML discovery completed on: http://localhost:9090/cfgmgnt.cas.sso/login Sep 04, 2014 4:15:35 PM org.openid4java.discovery.Discovery discover INFO: Discovered 0 OpenID endpoints. Sep 04, 2014 4:15:36 PM org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@2dc43978: display name [Root WebApplicationContext]; startup date [Thu Sep 04 16:15:36 CEST 2014]; root of context hierarchy Sep 04, 2014 4:15:36 PM org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@2dc43978]: org.springframework.beans.factory.support.DefaultListableBeanFactory@7988661b Sep 04, 2014 4:15:36 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@7988661b: defining beans [filter,legacy]; root of factory hierarchy Sep 04, 2014 4:15:40 PM org.openid4java.server.RealmVerifier setEnforceRpId WARNING:
[JIRA] [git] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Mark Waite commented on JENKINS-20879 SSH Credentials (private key with passphrase) do not work Felix Nawroth I found that I can use a passphrase protected ssh key with the latest git plugin (2.2.5) and the latest git client plugin (1.10.1) if I use a git URL of the form ssh://username@hostname/repository. That form works as expected on both Windows and Linux, with the ssh passphrase entered into the "Advanced" section of the credentials panel. I don't have any estimate for when this will be fixed. I don't plan to work on fixing it, especially since I've found at least one URL form which works as expected with a passphrase protected ssh key. I have recently been able to add an authentication test case to the git client plugin automated tests, so there is progress towards allowing further testing of these types of cases, but I don't intend to work on this specific case, since I believe it is relatively uncommon, and has a work around. This message is automatically generated by JIRA. 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] [openid] (JENKINS-24288) Noclassdef found in openID plugin
junaid shaikh commented on JENKINS-24288 Noclassdef found in openID plugin still facing the same error but figured the workaround that I can add manually xml-apis-2.0.2.jar in $userhome\.jenkins\war\WEB-INF\lib and it works This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
Justinas Urbanavicius commented on JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException i totally agree with you. I've seen some applications that display a user friendly error and have a link or a button "more details" that then clicked, shows the stack trace and error code or more related information, that is helpful for developers. It's both user friendly and informative. This message is automatically generated by JIRA. 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] [dynamicparameter] (JENKINS-24584) 'View selected script option' in build configuration displays wrong scriptler script
Ioannis Moutsatsos created JENKINS-24584 View selected script option in build configuration displays wrong scriptler script Issue Type: Bug Assignee: Dominik Bartholdi Components: dynamicparameter, scriptler Created: 04/Sep/14 4:07 PM Description: When a project configuration contains a Dynamic Parameter (Scriptler) parameter and uses one or more Scriptler script build steps the 'View Selected Script' link displayed in the build steps, link to the wrong script. It appears that the script displayed is the previous one used in the configuration sequence. Since the Dynamic Parameter (Scriptler) does not have a 'View selected script' option (which it should have!) we are dealing with a 'one-off' type of error due to the introduction of a Dynamic Parameter Scriptlet whose link is not tracked. To clarify here is an example configuration file Parameters --Dynamic Parameter (Scriptler) uses Script_A Build --Scriptler Script: Step 1 Uses Script_B --'View' links to Script_A (instead of Script_B) --Scriptler Script: Step 2 Uses Script_C --'View' links to Script_B (instead of Script_C) Environment: Jenkins-CI 1.565.1, Scriptler 2.7, Windows Project: Jenkins Priority: Minor Reporter: Ioannis Moutsatsos This message is automatically generated by JIRA. 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] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete
Reinhard Karbas commented on JENKINS-23660 Attached log in Jenkins email incomplete What's the planned release date for 2.39? This message is automatically generated by JIRA. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Given the error symptoms it looks like we can enable to tracing in ADB to get it to tell more information about what is going on. Just set the environment variable ADB_TRACE to adb,transport for the job (or as a global environment variable in the jenkins configuration) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-24581) tasks status icon not visible at overview of single task
Daniel Beck updated JENKINS-24581 tasks status icon not visible at overview of single task Please specify the correct Jenkins version. Change By: Daniel Beck (04/Sep/14 4:17 PM) Assignee: UlliHafner Component/s: tasks-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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Given the error symptoms it looks like we can enable to tracing in ADB to get it to tell more information about what is going on. Just set the environment variable ADB_TRACE to adb,transport for the job (or as a global environment variable in the jenkins configuration). You might need the EnvInject plugin installed to do this. Now when the build runs it will log additional information in the console output. The ADB server will also log to /tmp/adb.log. That location is hardcoded and cannot be changed so you need to grab that after the build. Also make sure that you remove it before the next build or it will append the new log onto the end. If it is configured right you will see lots of messages similar to the following: system/core/adb/adb_client.c::_adb_connect():_adb_connect: return fd 3 system/core/adb/adb_client.c::adb_connect():adb_connect: return fd 3 system/core/adb/transport.c::readx():readx: fd=3 wanted=4 system/core/adb/transport.c::readx():readx: fd=3 wanted=4 got=4 30303237 0027 I don't really think you need to capture the "good" logs anymore we have enough examples of that so you might as well save some uploading time. This message is automatically generated by JIRA. 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] [dashboard-view] (JENKINS-24583) Regular expression for selecting jobs in dashboard view breaks jenkins
Daniel Beck resolved JENKINS-24583 as Not A Defect Regular _expression_ for selecting jobs in dashboard view breaks jenkins This regular _expression_ is invalid, and the error tells you where. Change By: Daniel Beck (04/Sep/14 4:22 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. 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] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete
Alex Earl commented on JENKINS-23660 Attached log in Jenkins email incomplete When I can find enough time to complete testing and do a release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23263) Move hudson.tasks.junit to a bundled plugin
Reinhard Karbas commented on JENKINS-23263 Move hudson.tasks.junit to a bundled plugin I don't think it is an email ext plugin problem, the token macro does not find the values: ERROR: Publisher hudson.plugins.emailext.ExtendedEmailPublisher aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at hudson.plugins.emailext.plugins.content.TestCountsContent.evaluate(TestCountsContent.java:50) at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:189) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:182) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:233) at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:71) at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:717) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:474) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:292) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:283) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:235) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1786) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) This message is automatically generated by JIRA. 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-24407) missing weather icons (randomly?)
Daniel Beck commented on JENKINS-24407 missing weather icons (randomly?) https://github.com/jenkinsci/jenkins/compare/jenkins-1.575...jenkins-1.576 Just 62 commits changing 263 files, nothing major Missed your earlier comment, will try to reproduce the problem later today. This message is automatically generated by JIRA. 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Daniel Serodio commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Thanks Steve, it does help. However, we'd have a hard time asking our security team to open a firewall rule allowing so many ports (1024-65535). I don't understand the details of Jenkins CLI networking, is it possible to narrow the range of ports, or are they this much dynamic? This message is automatically generated by JIRA. 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-24407) missing weather icons (randomly?)
Mike Hobbs commented on JENKINS-24407 missing weather icons (randomly?) For what it's worth, we're able to fix the weather icons by rebuilding the projects (which re-runs Cobertura). This message is automatically generated by JIRA. 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] [xcode] (JENKINS-15118) Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project
Sharon Bamani commented on JENKINS-15118 Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project I get the same error. When working with "Xcode Workspace File",which is not at the jenkins workspace (for example dirA/dirB ) without specifying the "Xcode Project Directory": $ /usr/bin/agvtool new-marketing-version 0.0.109 There are no Xcode project files in this directory. agvtool needs a project to operate. FATAL: Could not set CFBundleShortVersionString to: 0.0.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] [integrity-plugin] (JENKINS-23369) Unable to check-in using bypass mode
SCM/JIRA link daemon commented on JENKINS-23369 Unable to check-in using bypass mode Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/IntegrityCheckinTask.java http://jenkins-ci.org/commit/integrity-plugin/24b84592236495d63ba2139b66c594c5e5f85af8 Log: Resolved JENKINS-23369 Unable to check-in using bypass mode This message is automatically generated by JIRA. 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-23638) Error in Checkin not failing job
SCM/JIRA link daemon commented on JENKINS-23638 Error in Checkin not failing job Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/IntegrityCheckinAction.java http://jenkins-ci.org/commit/integrity-plugin/e29c66112b0d6fe5c89088bb3a7ef47db1b73413 Log: Resolved JENKINS-23638 Error in Checkin not failing job This message is automatically generated by JIRA. 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-24582) With the latest version of Jenkins, 1.5.78, the GIT Plugin throws a stack trace for both jobs and configure system. Without the plugin the stack trace is not present
Mark Waite
updated JENKINS-24582
With the latest version of Jenkins, 1.5.78, the GIT Plugin throws a stack trace for both jobs and configure system. Without the plugin the stack trace is not present
Change By:
Mark Waite
(04/Sep/14 5:31 PM)
Description:
LatestGITPlugin=2.2.5Stacktrace
{noformat}
javax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-1.578.jar!/lib/form/section.jelly:48:21:d:invokeBodyhudson/matrix/MatrixBuild atorg.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) atorg.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) atorg.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) atorg.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) atorg.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Daniel Beck commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Doesn't it just use the port configured on the Configure Global Security page? (needs security enabled) This message is automatically generated by JIRA. 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-24520) Recent changes is always empty
Mark Waite commented on JENKINS-24520 Recent changes is always empty Björn Kraus does the problem resolve itself for you if you switch to git plugin 2.2.4 and leave all other components unchanged? Can you provide more details so that the problem can be duplicated? Under which conditions do you see the problem? Under which conditions do you not see the problem? Is the multiple SCMs plugin required to show the problem, or can it be seen without the multiple SCM plugin? Is there any stack trace information in the log files or elsewhere which might hint why the list of changes is empty? This message is automatically generated by JIRA. 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-23638) Error in Checkin not failing job
Cletus DSouza resolved JENKINS-23638 as Fixed Error in Checkin not failing job Resolved in 1.26 version of the plugin Change By: Cletus DSouza (04/Sep/14 5:44 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-24532) Integrity Checkin Task takes optional changePackageID
Cletus DSouza resolved JENKINS-24532 as Fixed Integrity Checkin Task takes optional changePackageID Already supported with build parameter ItemID Change By: Cletus DSouza (04/Sep/14 5:43 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-23412) Way to configure description to check in action
Cletus DSouza resolved JENKINS-23412 as Wont Fix Way to configure description to check in action You can use Change Packages by passing in an ItemID using build parameters. This way your Build Item can have all the links you need. Change By: Cletus DSouza (04/Sep/14 5:45 PM) Status: Open Resolved Fix Version/s: current Resolution: WontFix This message is automatically generated by JIRA. 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-23369) Unable to check-in using bypass mode
Cletus DSouza resolved JENKINS-23369 as Fixed Unable to check-in using bypass mode Resolved in version 1.26 of the plugin. Simply add the :bypass keyword to the ItemID build parameter. Example: http://server/job/myjob/buildWithParameters?token=TOKENItemID=:bypass Change By: Cletus DSouza (04/Sep/14 5:46 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-21993) [Integrity] Add a label to existing checkpoint
Cletus DSouza resolved JENKINS-21993 as Fixed [Integrity] Add a label to existing checkpoint This is already possible today. Simply activate the checkpoint action in the post build and if a build project is encountered, it will get re-labeled. Change By: Cletus DSouza (04/Sep/14 5:47 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-21931) Uncaught Exception when using multiple checkout threads ( Checkout Thread Pool Size 1)
Cletus DSouza resolved JENKINS-21931 as Incomplete Uncaught Exception when using multiple checkout threads ( Checkout Thread Pool Size 1) Closing due to lack of response. Change By: Cletus DSouza (04/Sep/14 5:49 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. 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-14706) Integrity Plugin should create *.pj files, too
Cletus DSouza resolved JENKINS-14706 as Wont Fix Integrity Plugin should create *.pj files, too As mentioned earlier, the support for the client is not something that will be done in this plugin. You have two options the way I see it: 1. Write your extensions (CLI) using the JAVA API 2. Use the Maven Plugin to create/update the sandbox instead of the Jenkins plugin Thanks! Cletus Change By: Cletus DSouza (04/Sep/14 5:52 PM) Status: Reopened Resolved Resolution: WontFix This message is automatically generated by JIRA. 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-23317) PTC plugin causing memory leak
Cletus DSouza resolved JENKINS-23317 as Cannot Reproduce PTC plugin causing memory leak All memory leak issues as it relates to the API/APISession have been resolved. Without a specific reproducible case, I cannot fix something I can reproduce. Change By: Cletus DSouza (04/Sep/14 5:54 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. 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 DSouza commented on JENKINS-14703 PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin Martin, is the resolution to this problem in the Locale Plugin or did you do something in the Integrity plugin that makes it work for you? Thanks! Cletus This message is automatically generated by JIRA. 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-14675) Schema 'DBUSER' does not exist error in integrity plugin
Cletus DSouza commented on JENKINS-14675 Schema DBUSER does not exist error in integrity plugin Are there any new updates on a potential root cause for this error that I can chase down? This message is automatically generated by JIRA. 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-21968) A SQL Exception was caught! Schema 'DBUSER' does not exist
Cletus DSouza resolved JENKINS-21968 as Duplicate A SQL Exception was caught! Schema DBUSER does not exist This is a duplicate of JENKINS-14675 Change By: Cletus DSouza (04/Sep/14 5:58 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [rebuild] (JENKINS-24585) Change text on button to Rebuild Last Completed Build
André Söderlind created JENKINS-24585 Change text on button to Rebuild Last Completed Build Issue Type: Improvement Assignee: André Söderlind Components: rebuild Created: 04/Sep/14 6:10 PM Description: The text on the button is non-intuitive, since users does not understand that if the last build was for example aborted hitting "Rebuild Last" will not rebuild that one. Project: Jenkins Priority: Trivial Reporter: André Söderlind This message is automatically generated by JIRA. 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] [build-failure-analyzer] (JENKINS-23409) Crashing api at depth 0
milki mlk edited a comment on JENKINS-23409 Crashing api at depth 0 We use http://netmelody.org/ci-eye/ and with Jenkins 1.576 and 1.577, all calls from it are failing with the same error: Caused by: org.kohsuke.stapler.export.NotExportableException: class java.io.IOException doesn't have @ExportedBean so cannot write hudson.slaves.OfflineCause$ChannelTermination.cause Our logs are filling up because the errors are generating 0.5MB/sec. This message is automatically generated by JIRA. 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] [filesystem-list-parameter] (JENKINS-24586) NPE in at alex.jenkins.plugins.FileSystemListParameterDefinition.createAllObjectsMap(FileSystemListParameterDefinition.java:342)
Walter Kacynski created JENKINS-24586 NPE in at alex.jenkins.plugins.FileSystemListParameterDefinition.createAllObjectsMap(FileSystemListParameterDefinition.java:342) Issue Type: Bug Assignee: Unassigned Components: filesystem-list-parameter Created: 04/Sep/14 7:00 PM Description: Getting an NPE with this message: Caused by: java.lang.NullPointerException at alex.jenkins.plugins.FileSystemListParameterDefinition.createAllObjectsMap(FileSystemListParameterDefinition.java:342) at alex.jenkins.plugins.FileSystemListParameterDefinition.getFsObjectsList(FileSystemListParameterDefinition.java:210) Project: Jenkins Priority: Major Reporter: Walter Kacynski This message is automatically generated by JIRA. 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] [rebuild] (JENKINS-22836) Rebuild Last link out of date
André Söderlind commented on JENKINS-22836 Rebuild Last link out of date Pull request: https://github.com/jenkinsci/rebuild-plugin/pull/27 This message is automatically generated by JIRA. 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] [rebuild] (JENKINS-24585) Change text on button to Rebuild Last Completed Build
André Söderlind commented on JENKINS-24585 Change text on button to Rebuild Last Completed Build Pull request: https://github.com/jenkinsci/rebuild-plugin/pull/26 This message is automatically generated by JIRA. 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] [rebuild] (JENKINS-24585) Change text on button to Rebuild Last Completed Build
André Söderlind stopped work on JENKINS-24585 Change text on button to Rebuild Last Completed Build Change By: André Söderlind (04/Sep/14 7:01 PM) Status: InProgress 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] [rebuild] (JENKINS-24585) Change text on button to Rebuild Last Completed Build
André Söderlind started work on JENKINS-24585 Change text on button to Rebuild Last Completed Build Change By: André Söderlind (04/Sep/14 7:00 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [filesystem-list-parameter] (JENKINS-24586) NPE in at alex.jenkins.plugins.FileSystemListParameterDefinition.createAllObjectsMap(FileSystemListParameterDefinition.java:342)
Walter Kacynski assigned JENKINS-24586 to Alexander Endter NPE in at alex.jenkins.plugins.FileSystemListParameterDefinition.createAllObjectsMap(FileSystemListParameterDefinition.java:342) Change By: Walter Kacynski (04/Sep/14 7:01 PM) Assignee: AlexanderEndter This message is automatically generated by JIRA. 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] [rebuild] (JENKINS-24585) Change text on button to Rebuild Last Completed Build
André Söderlind assigned JENKINS-24585 to ragesh_nair Change text on button to Rebuild Last Completed Build Change By: André Söderlind (04/Sep/14 7:02 PM) Assignee: AndréSöderlind ragesh_nair This message is automatically generated by JIRA. 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-24407) missing weather icons (randomly?)
Daniel Beck commented on JENKINS-24407 missing weather icons (randomly?) Reproduced the issue with the data provided by K P: The 87% (worst health) HealthReport in question was serialized to disk from before the icon classname field existed (attached build.xml starting at line 581), and deserialization does not call the constructor, leaving the field null, hence no icon. There's no implementation of readResolve() in HealthReport that would be able to fix it. Any builds created after the Jenkins update should contain the field in serialized form, and therefore show up correctly (making reproducing it rather difficult!). I'm preparing a fix right now. A workaround for everyone affected and not willing to wait for a fix would be to script changes to affected build.xml files. For every line like this: iconUrlhealth-80plus.png/iconUrl Add a line below like this: iconClassNameicon-health-80plus/iconClassName Repeat for all other pairs of icon class name/icon URL defined here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/HealthReport.java#L50 Then reload configuration from disk. This message is automatically generated by JIRA. 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-24407) missing weather icons (randomly?)
Daniel Beck edited a comment on JENKINS-24407 missing weather icons (randomly?) Reproduced the issue with the data provided by K P: The 87% (worst health) HealthReport in question was serialized to disk from before the icon classname field existed (attached build.xml starting at line 581), and deserialization does not call the constructor, leaving the field null, hence no icon. There's no implementation of readResolve() in HealthReport, and ConverterImpl ignores this issue. Any builds created after the Jenkins update should contain the field in serialized form, and therefore show up correctly (making reproducing it rather difficult!). I'm preparing a fix right now. A workaround for everyone affected and not willing to wait for a fix would be to script changes to affected build.xml files. For every line like this: iconUrlhealth-80plus.png/iconUrl Add a line below like this: iconClassNameicon-health-80plus/iconClassName Repeat for all other pairs of icon class name/icon URL defined here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/HealthReport.java#L50 Then reload configuration from disk. This message is automatically generated by JIRA. 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-13128) Artifacts Permissions Stripped
Tony Panza commented on JENKINS-13128 Artifacts Permissions Stripped @Daniel This occurs on slave nodes as well. On a slave with Ubuntu 10.04.3 LTS (2.6.32-64-generic-pae #128-Ubuntu SMP Tue Jul 15 08:49:38 UTC 2014 i686 GNU/Linux), Jenkins v1.436. This message is automatically generated by JIRA. 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-24587) Remote triggering over POST request doesn't bring Jenkins page loaded
oleg hayevskyy created JENKINS-24587 Remote triggering over POST request doesnt bring Jenkins page loaded Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 04/Sep/14 7:31 PM Description: Hi, I was using Parameterized-trigger plugin for quite a long time to trigger my jobs remotely over POST request from my webpage. When I was triggering the job I used to have jenkins page loaded in a separate tab with the job being launched and running. But after recent updates I don't get the page loaded anymore, however new tab is opened but with no content and the job is being triggered and executed. Unfortunately I didn't notice which exact version affected this. Currently I'm using latest version - 1.578 and the issue still persists. Please suggest how I can resolve this. Thanks, Oleg Environment: Windows 7 64bit Project: Jenkins Priority: Minor Reporter: oleg hayevskyy This message is automatically generated by JIRA. 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-24407) missing weather icons (randomly?)
Daniel Beck commented on JENKINS-24407 missing weather icons (randomly?) Tom FENNELLY: The following change causes the HealthReport to inialize properly from old on-disk data: https://github.com/daniel-beck/jenkins/commit/3a18c6ba1092bee3a0b1903aa42e838b37a72a60 I'll create a PR for it if you don't merge this change by late Friday UTC so it has a chance to get in 1.580. This message is automatically generated by JIRA. 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] [github] (JENKINS-23995) Adding commit status context in github-plugin
Edward Rudd commented on JENKINS-23995 Adding commit status context in github-plugin Having the ability to set the context in the after-build task would be extremely useful.. For example I have two jenkins jobs setup for the same github repository. One is doing a linux build the other a windows build. (yes there are other ways of doing this too).. But the need is there to have the "status" set on github in separate contexts. e.g. build/windows build/linux build/osx. Read more on the github developer blog on other use-cases. https://developer.github.com/changes/2014-03-27-combined-status-api/ https://developer.github.com/changes/2014-07-09-status-contexts-are-official/ This message is automatically generated by JIRA. 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] [radargun] (JENKINS-24588) Pass -slaveIndex to slaves
vjuranek created JENKINS-24588 Pass -slaveIndex to slaves Issue Type: Bug Assignee: vjuranek Components: radargun Created: 04/Sep/14 7:44 PM Description: https://github.com/vjuranek/radargun-plugin/issues/3 Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. 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-24589) Build History - name and links overlap if build names are long
Joshua Strouse created JENKINS-24589 Build History - name and links overlap if build names are long Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: screencap.png Components: gui Created: 04/Sep/14 7:49 PM Description: The build names overlap the build links when the build names are long, using the 'build-name-setter' plugin. Environment: Server: Jenkins v1.576, build name setter plugin v1.3 Viewed On: Windows 7 SP1 x64, Chrome Version 36.0.1985.143 m Project: Jenkins Priority: Critical Reporter: Joshua Strouse This message is automatically generated by JIRA. 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-23806) Managed script files are not included in scm config
onekilo79 commented on JENKINS-23806 Managed script files are not included in scm config Just add a Manual synchronization includes: for buildstep-config-files.xml This will then save the managed scripts to your scm. This message is automatically generated by JIRA. 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] [radargun] (JENKINS-24588) Pass -slaveIndex to slaves
vjuranek resolved JENKINS-24588 as Fixed Pass -slaveIndex to slaves Done in https://github.com/jenkinsci/radargun-plugin/commit/665aabb34bdfd11fd40dd6427f5333404a5444ce Change By: vjuranek (04/Sep/14 8:33 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-24589) Build History - name and links overlap if build names are long
Daniel Beck updated JENKINS-24589 Build History - name and links overlap if build names are long Change By: Daniel Beck (04/Sep/14 8:47 PM) Labels: user-experience Priority: Critical 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] [core] (JENKINS-24582) With the latest version of Jenkins, 1.5.78, the GIT Plugin throws a stack trace for both jobs and configure system. Without the plugin the stack trace is not present
Daniel Beck resolved JENKINS-24582 as Not A Defect With the latest version of Jenkins, 1.5.78, the GIT Plugin throws a stack trace for both jobs and configure system. Without the plugin the stack trace is not present Install and/or enable the Matrix Project plugin. Change By: Daniel Beck (04/Sep/14 8:49 PM) Status: Open Resolved Assignee: R.TylerCroy Resolution: NotADefect This message is automatically generated by JIRA. 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-24587) Remote triggering over POST request doesn't bring Jenkins page loaded
Daniel Beck updated JENKINS-24587 Remote triggering over POST request doesnt bring Jenkins page loaded This has nothing to do with Parameterized Trigger plugin. Change By: Daniel Beck (04/Sep/14 8:55 PM) Assignee: huybrechts Affects Version/s: current Component/s: core Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [filesystem-list-parameter] (JENKINS-24586) NPE in at alex.jenkins.plugins.FileSystemListParameterDefinition.createAllObjectsMap(FileSystemListParameterDefinition.java:342)
Daniel Beck updated JENKINS-24586 NPE in at alex.jenkins.plugins.FileSystemListParameterDefinition.createAllObjectsMap(FileSystemListParameterDefinition.java:342) Jenkins generally allows you to enter invalid input and lets you suffer afterwards. In this case, because you did not enter a folder path despite the bold, red message telling you to. Change By: Daniel Beck (04/Sep/14 9:03 PM) 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] [core] (JENKINS-24587) Remote triggering over POST request doesn't bring Jenkins page loaded
oleg hayevskyy commented on JENKINS-24587 Remote triggering over POST request doesnt bring Jenkins page loaded Hi Daniel, Thank you for the response. Apologies for putting this into wrong section. Is there any way/workaround to get old behavior working again? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24587) Remote triggering over POST request doesn't bring Jenkins page loaded
Daniel Beck commented on JENKINS-24587 Remote triggering over POST request doesnt bring Jenkins page loaded Not that I know. Maybe try asking on the jenkinsci-users mailing list. This message is automatically generated by JIRA. 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-24589) Build History - name and links overlap if build names are long
Daniel Beck updated JENKINS-24589 Build History - name and links overlap if build names are long Change By: Daniel Beck (04/Sep/14 9:14 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.
