[JIRA] [timestamper] (JENKINS-19778) http://jenkins/job/jobname/1/timestamps return twice as big values compared to what it should
stevengbrown assigned JENKINS-19778 to stevengbrown http://jenkins/job/jobname/1/timestamps return twice as big values compared to what it should Change By: stevengbrown (27/Nov/13 8:05 AM) Assignee: aleksas stevengbrown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20779) Jenkins 1.541 crashes JVM on startup
Sergej Kleva commented on JENKINS-20779 Jenkins 1.541 crashes JVM on startup The same thing happen from 1.539 to 1.540 or 1.541! java version "1.7.0_40" Java(TM) SE Runtime Environment (build 1.7.0_40-b43) Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode) Windows 7 x64 Brgds, S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17314) Rebuild Job using GET method
Wolfgang Hauser commented on JENKINS-17314 Rebuild Job using GET method Using dashboard 2.9.2 with 1.541, the "Unstable Job" portlet was working well. But Job Grid portlet still has the GET method problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-20025) Dashboard View Plugin: Starting jobs returns error 'Form post required'
Wolfgang Hauser commented on JENKINS-20025 Dashboard View Plugin: Starting jobs returns error 'Form post required' Using dashboard view 2.9.2 on Jenkins 1.541, the job grid portlet still reports the POST /GET issue. I file a bug for dashboard view. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-20780) Job Grid portet reports GET / POST issue for "Build job"
Wolfgang Hauser created JENKINS-20780 Job Grid portet reports GET / POST issue for "Build job" Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Components: dashboard-view Created: 27/Nov/13 9:38 AM Description: Job Grid reports You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin. See also JENKINS-20025 Environment: Jenkins 1.541 dashboard view 2.9.2 debian lennny Fix Versions: current Project: Jenkins Priority: Minor Reporter: Wolfgang Hauser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-15631) When custom tool installation is on SCM checkout fails
Oleg Nenashev assigned JENKINS-15631 to Oleg Nenashev When custom tool installation is on SCM checkout fails Change By: Oleg Nenashev (27/Nov/13 10:49 AM) Assignee: recampbell Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-15631) When custom tool installation is on SCM checkout fails
Oleg Nenashev resolved JENKINS-15631 as Duplicate When custom tool installation is on SCM checkout fails Change By: Oleg Nenashev (27/Nov/13 10:51 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/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20781) "Specific Users Strategy" does not validate authentication of the selected user
Oleg Nenashev created JENKINS-20781 "Specific Users Strategy" does not validate authentication of the selected user Issue Type: Bug Assignee: Unassigned Components: authorize-project Created: 27/Nov/13 10:54 AM Description: The real authentication checking code is commented, so the validation will be passed for every user (see SpecificUserAuthorizationStrategy.java:375 ) Project: Jenkins Labels: security Priority: Blocker Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20781) "Specific Users Strategy" does not validate authentication of the selected user
Oleg Nenashev assigned JENKINS-20781 to ikedam "Specific Users Strategy" does not validate authentication of the selected user Change By: Oleg Nenashev (27/Nov/13 10:55 AM) Assignee: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20782) CLONE - "Specific Users Strategy" verifies authentication multiple times
Oleg Nenashev created JENKINS-20782 CLONE - "Specific Users Strategy" verifies authentication multiple times Issue Type: Bug Assignee: ikedam Components: authorize-project Created: 27/Nov/13 10:58 AM Description: The real authentication checking code is commented, so the validation will be passed for every user (see SpecificUserAuthorizationStrategy.java:375 ) Project: Jenkins Labels: security Priority: Blocker Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20782) "Specific Users Strategy" verifies authentication multiple times
Oleg Nenashev updated JENKINS-20782 "Specific Users Strategy" verifies authentication multiple times Change By: Oleg Nenashev (27/Nov/13 10:58 AM) Summary: CLONE - "Specific Users Strategy" verifies authentication multiple times Priority: Blocker Critical Description: The real authentication checking code is commented, so In "Specific Users Strategy" you check the validation will be passed for every user (see SpecificUserAuthorizationStrategy password multiple times after the each change of the input field . java:375 ) It may lead to locking of user's account due to limited number of authentication attempts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [drmemory] (JENKINS-20222) Allowing drmemory to run even if the command return a failure ( Praqma case 10247 )
Mads Nielsen resolved JENKINS-20222 as Fixed Allowing drmemory to run even if the command return a failure ( Praqma case 10247 ) Fixed in 1.1 Change By: Mads Nielsen (27/Nov/13 11:07 AM) Status: Open Resolved Assignee: Jens Brejner Praqma Support Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20783) Improper invocation of doCheckPassword() in Authoriza project
Oleg Nenashev created JENKINS-20783 Improper invocation of doCheckPassword() in Authoriza project Issue Type: Bug Assignee: Unassigned Components: authorize-project Created: 27/Nov/13 11:10 AM Description: doCheckPassword() from "Specific User Strategy" is being triggered even if "Configure Build Authorization" is unchecked Project: Jenkins Labels: security Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20784) Authorize project plugin causes creation of new users in Jenkins
Oleg Nenashev created JENKINS-20784 Authorize project plugin causes creation of new users in Jenkins Issue Type: Bug Assignee: Unassigned Components: authorize-project Created: 27/Nov/13 11:11 AM Description: The plugin uses User.get(String) to retrieve users. This method creates new users on-demand, so your null checks won't work in any case. In addition, this function may lead to creation of new users if admin uses "Specific User" strategy Project: Jenkins Priority: Critical Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20785) Authorize Project does not handle configurations of MatrixProject
Oleg Nenashev created JENKINS-20785 Authorize Project does not handle configurations of MatrixProject Issue Type: Bug Assignee: Unassigned Components: authorize-project Created: 27/Nov/13 11:15 AM Description: Matrix Projects are not handled. The plugin should check the class of the project and then retrieve its parent for Matrix Configurations Project: Jenkins Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20786) Replace radioBloks by dropdownDescriptorSelector.
Oleg Nenashev created JENKINS-20786 Replace radioBloks by dropdownDescriptorSelector. Issue Type: Improvement Assignee: Unassigned Components: authorize-project Created: 27/Nov/13 11:17 AM Description: hetero-radio selector overloads web UI in the case of big number of strategies. I suppose that dropdownDescriptoSelector would be preferable Project: Jenkins Labels: ui Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-user-vars] (JENKINS-19187) User variables are not set to Maven3 build
Anders Hammar commented on JENKINS-19187 User variables are not set to Maven3 build I've run into the same problem for Maven build projects. I solved it by adding yet another plugin and have it injecting the environment variables. Not a pretty solution though. If the suggested solution for this plugin is correct, it would be great to have a new release out! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-user-vars] (JENKINS-20787) BUILD_USER_ID is not set in Maven build execution triggered by release:perform
Anders Hammar
created JENKINS-20787
BUILD_USER_ID is not set in Maven build execution triggered by release:perform
Issue Type:
Bug
Assignee:
Unassigned
Components:
build-user-vars
Created:
27/Nov/13 11:58 AM
Description:
When doing a release for a Maven build project (using the m2release plugin), the build user vars gets screwed up in the Maven build during the Maven build execution triggered by release:perform.
BUILD_USER is set to the user id ('kaha14' for example). BUILD_USER_ID is not set. BUILD_USER_FIRST_NAME is set to the same as BUILD_USER and BUILD_USER_LAST_NAME is not set (probably because BUILD_USER is just one word).
Environment:
Windows 2008 Server, Oracle JDK 1.7.0, Jenkins 1.509.4 LTS, plugin v1.1
Project:
Jenkins
Priority:
Major
Reporter:
Anders Hammar
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-20166) Promoted Build NullPointer when not manual promotion
Adam H commented on JENKINS-20166 Promoted Build NullPointer when not manual promotion Seeing the same thing. Jenkins 1.522 with version 2.14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials The only alternatives I've discovered have required that I switch the URL to something other than an ssh URL. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-20166) Promoted Build NullPointer when not manual promotion
Adam H edited a comment on JENKINS-20166 Promoted Build NullPointer when not manual promotion Seeing the same thing. Jenkins 1.522 with version 2.14. Downgrading to 2.13 seem to solve the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-20788) pom.xml should be updated to LTS release
chanti vlad created JENKINS-20788 pom.xml should be updated to LTS release Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core Created: 27/Nov/13 1:16 PM Description: The analysis-pom/pom.xml file should be upgraded to: org.jenkins-ci.plugins plugin 1.509.4 Project: Jenkins Priority: Trivial Reporter: chanti vlad This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Roland Whitley commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Thanks, unfortunately I have not been very successful with gitlab and http. Commits have usually exceeded size limitations. There were a couple of mentions that this was a recent change. Is there a version that I can roll back to that would bypass this until this fix is released. I only want to consider forking the branch as a final option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Roland Whitley edited a comment on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Thanks, unfortunately I have not been very successful with gitlab and http. Commits have usually exceeded size limitations. Did you mention that this was a recent change and prior releases did not behave like this. Is there a version that I can roll back to that would bypass this until this fix is released. I only want to consider forking the branch as a final option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials I believe Git plugin 1.5 worked just fine in this case, as did earlier versions of the plugin, though none of those earlier versions supported the Jenkins credentials store. You'll need to manage the credentials yourself in the job definition, without the convenience of the Jenkins credentials system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Ean Rollings commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails so my odd error is around the password. when the password contains a dollar sign ($), it seems to be sending the value as "%24" instead of a $ (maybe desired behavior for other parts of the URI but not for the password). In my case, the password began with a dollar sign. the important bit of the error message I was getting is: stderr: error: The requested URL returned error: 401 while accessing https://USERNAME:%24-the-rest-of-the-passw...@git.url/... NOTE: this was when I was running credentials 1.9.1. after updating to 1.9.3 of that plugin, it seems that semi-revealing error message has been reduced to: Failed to connect to repository : Failed to connect to https://git.url/git/git_repo using credentials USERNAME password (status = 401) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-3925) Clear workspace before build
Anders Hammar commented on JENKINS-3925 Clear workspace before build Support for deleting the m2 local repository in the workspace would be good. That's the recommended fashion to ensure a good release environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-20789) EC2: manage new computeCurrentGen (c3.*) instances
Julien Carsique created JENKINS-20789 EC2: manage new computeCurrentGen (c3.*) instances Issue Type: New Feature Assignee: Julien Carsique Components: ec2 Created: 27/Nov/13 1:47 PM Description: Align on com.amazonaws:aws-java-sdk:1.6.7 to manage new "computeCurrentGen" (aka "c3.*") instances. Project: Jenkins Priority: Major Reporter: Julien Carsique This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-20790) Warning text about several upstream jobs shown even though there is only one upstream job
André Söderlind created JENKINS-20790 Warning text about several upstream jobs shown even though there is only one upstream job Issue Type: Bug Assignee: André Söderlind Attachments: jenkins_multijob_warning.png Components: jenkins-multijob-plugin Created: 27/Nov/13 1:50 PM Description: Below text is shown even it the job only has one upstream job. "There are other upstream projects for this job. It's possible, although very low probability, that multijob will be unable to execute concurrently the same job, due to Jenkins limitation. In such cases, recommended to clone the job." Project: Jenkins Priority: Minor 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/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Ean Rollings edited a comment on JENKINS-20533 Git2 plugin and HTTP-authentication fails so my odd error is around the password. when the password contains a dollar sign ($), it seems to be sending the value as "%24" instead of a $ (maybe desired behavior for other parts of the URI but not for the password). In my case, the password began with a dollar sign. the important bit of the error message I was getting is: stderr: error: The requested URL returned error: 401 while accessing https://USERNAME:%24-the-rest-of-the-passw...@git.url/... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-20526) Allow timouts to be set via parameter
Martin Wiklundh commented on JENKINS-20526 Allow timouts to be set via parameter There has been a number of requests regarding this. Please implement. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-20789) EC2: manage new computeCurrentGen (c3.*) instances
Julien Carsique started work on JENKINS-20789 EC2: manage new computeCurrentGen (c3.*) instances Change By: Julien Carsique (27/Nov/13 2:00 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-20790) Warning text about several upstream jobs shown even though there is only one upstream job
André Söderlind commented on JENKINS-20790 Warning text about several upstream jobs shown even though there is only one upstream job Bugfix implemented: Check if "upstreamProjects.size()" is larger than 1 rather than 0. @Plugin owners: please review code modification (only 1 line of code ) Bugfix committed to the branch: https://github.com/andresoderlind/tikal-multijob-plugin/tree/ISSUE-J-20790 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-user-vars] (JENKINS-20787) BUILD_USER_ID is not set in Maven build execution triggered by release:perform
Anders Hammar commented on JENKINS-20787 BUILD_USER_ID is not set in Maven build execution triggered by release:perform Doing some digging, the problem is that the m2release plugin has created a ReleaseClause that extends UserCause. And it overrides getUserName(). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20205) JSONException saving periodicreincarnation.JobLocalConfiguration
Yordan Boev commented on JENKINS-20205 JSONException saving periodicreincarnation.JobLocalConfiguration Fixed, will be included in the next version. This helped a lot to make the optionalBlock thing work: http://stackoverflow.com/questions/13024929/how-to-use-optionalblock-in-build-steps-config-jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-20791) ReleaseCause should extend UserIdCause
Anders Hammar created JENKINS-20791 ReleaseCause should extend UserIdCause Issue Type: Bug Assignee: teilo Components: m2release Created: 27/Nov/13 2:12 PM Description: hudson.model.Cause.UserCause is deprecated and class ReleaseCause should extend hudson.model.Cause.UserIdCause instead. Also, it should not override methods like getUserName() as it will cause issues for other plugins like build-user-vars (see JENKINS-20787)! Environment: n/a Project: Jenkins Priority: Major Reporter: Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20785) Authorize Project does not handle configurations of MatrixProject
ikedam assigned JENKINS-20785 to ikedam Authorize Project does not handle configurations of MatrixProject Change By: ikedam (27/Nov/13 2:37 PM) Assignee: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20784) Authorize project plugin causes creation of new users in Jenkins
ikedam assigned JENKINS-20784 to ikedam Authorize project plugin causes creation of new users in Jenkins Change By: ikedam (27/Nov/13 2:38 PM) Assignee: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-20660) xshell: java.lang.NullPointerException from regex after updating to version 0.9
Mark Waite commented on JENKINS-20660 xshell: java.lang.NullPointerException from regex after updating to version 0.9 I encountered the same problem. The work around I used was to open the job definition, then save that job definition. It appears that the latest changes to the XShell plugin do not handle updates from a previously defined job as smoothly as they should. The same problem does not occur for a newly defined job, only for a job which was defined with an earlier version of the XShell plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-20660) xshell: java.lang.NullPointerException from regex after updating to version 0.9
Mark Waite updated JENKINS-20660 xshell: java.lang.NullPointerException from regex after updating to version 0.9 Change By: Mark Waite (27/Nov/13 2:45 PM) Environment: OS X 10.8.5 and Debian Wheezy and Windows, XShell 0.9, Jenkins 1.509.4 and Jenkins 1.532.1 and Jenkins 1.540 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-20788) pom.xml should be updated to LTS release
Ulli Hafner commented on JENKINS-20788 pom.xml should be updated to LTS release Why? Is there something missing in 1.424 that you would like to use? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20784) Authorize project plugin causes creation of new users in Jenkins
SCM/JIRA link daemon commented on JENKINS-20784 Authorize project plugin causes creation of new users in Jenkins Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategyTest.java http://jenkins-ci.org/commit/authorize-project-plugin/108872b08e97731f58b10816dd4087fdae828cd7 Log: [FIX JENKINS-20784] Specifying an unknwon user should result in anonymous authorization. This also avoids unintended createtion of new users. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20785) Authorize Project does not handle configurations of MatrixProject
SCM/JIRA link daemon resolved JENKINS-20785 as Fixed Authorize Project does not handle configurations of MatrixProject Change By: SCM/JIRA link daemon (27/Nov/13 2: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/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20785) Authorize Project does not handle configurations of MatrixProject
SCM/JIRA link daemon commented on JENKINS-20785 Authorize Project does not handle configurations of MatrixProject Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticator.java http://jenkins-ci.org/commit/authorize-project-plugin/ce58c76dbc26ea87773c09af32833a1498ffc382 Log: [FIXED JENKINS-20785] Now works also for MatrixProject. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20785) Authorize Project does not handle configurations of MatrixProject
SCM/JIRA link daemon commented on JENKINS-20785 Authorize Project does not handle configurations of MatrixProject Code changed in jenkins User: ikedam Path: src/test/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticatorTest.java http://jenkins-ci.org/commit/authorize-project-plugin/f76835226924ea20546650b3fb7d3ada18963ea5 Log: JENKINS-20785 Added tests for MatrixProject. They fails now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-20786) Replace radioBlocks by dropdownDescriptorSelector.
Oleg Nenashev updated JENKINS-20786 Replace radioBlocks by dropdownDescriptorSelector. Change By: Oleg Nenashev (27/Nov/13 3:32 PM) Summary: Replace radioBloks radioBlocks by dropdownDescriptorSelector. 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/groups/opt_out.
[JIRA] [parameters] (JENKINS-17221) "You must use POST method to trigger builds" warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/b
Kevin Thieling commented on JENKINS-17221 "You must use POST method to trigger builds" warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParameters?PARAMETER=Value What about when clicking on the "Build Now" link and this occurs? Is that a core issue, a plugin issue, or maybe a configuration issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20517) Show SCM changes in pipeline view
Patrik Boström closed JENKINS-20517 as Fixed Show SCM changes in pipeline view Change By: Patrik Boström (27/Nov/13 3:34 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-10967) Commit message doesn't appear whereas file is commited
evernat resolved JENKINS-10967 as Incomplete Commit message doesn't appear whereas file is commited No response from the reporter, so resolving as incomplete. Please reopen if needed. Change By: evernat (27/Nov/13 3:35 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/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20099) Cant use SVN_REVISION as pipeline version
Patrik Boström closed JENKINS-20099 as Fixed Cant use SVN_REVISION as pipeline version Change By: Patrik Boström (27/Nov/13 3:35 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20015) Placeholder for a logo
Patrik Boström closed JENKINS-20015 as Fixed Placeholder for a logo Change By: Patrik Boström (27/Nov/13 3:42 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-19972) Update helptexts
Patrik Boström closed JENKINS-19972 as Fixed Update helptexts Change By: Patrik Boström (27/Nov/13 3:42 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20441) Backport code to run on Java 1.6
Patrik Boström closed JENKINS-20441 as Fixed Backport code to run on Java 1.6 Change By: Patrik Boström (27/Nov/13 3:43 PM) Status: Resolved Closed Assignee: Rickard von Essen Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20388) Configurable update interval
Patrik Boström closed JENKINS-20388 as Fixed Configurable update interval Change By: Patrik Boström (27/Nov/13 3:43 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20588) consider "Trigger/call builds on other projects" from the Build configuration
Patrik Boström closed JENKINS-20588 as Fixed consider "Trigger/call builds on other projects" from the Build configuration Change By: Patrik Boström (27/Nov/13 3:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20539) various pipelines have no color
Patrik Boström closed JENKINS-20539 as Fixed various pipelines have no color Change By: Patrik Boström (27/Nov/13 3:43 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20721) Triggered by includes culprits
Patrik Boström closed JENKINS-20721 as Fixed Triggered by includes culprits Change By: Patrik Boström (27/Nov/13 3:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-20792) since 1.3.4 we can't use remote api to create pipeline
li wei created JENKINS-20792 since 1.3.4 we can't use remote api to create pipeline Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 27/Nov/13 4:05 PM Description: on 1.3.3, we can use remote api to create pipeline, by posting the following data to createView url: $jsonvalue = array ( "name" => $jobName, "mode" => "au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView", "filterExecutors" => "false", "filterQueue" => "false", "selectedJob" => $jobName, "noOfDisplayedBuilds" => "10", "buildViewTitle" => $description, "refreshFrequency" => "3", "description" => $description, // does not work "showPipelineDefinitionHeader" => "true" ); $parameters = array ( "name" => $jobName, "mode" => "au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView", "description" => $description, "_.showPipelineDefinitionHeader" => "true", "json" => json_encode ( $jsonvalue ) ); But after 1.3.4, it did not work. I guess the reason is "gridBuilder" does not be constructed, since "readResolve()" did not work. Due Date: 27/Nov/13 12:00 AM Project: Jenkins Priority: Blocker Reporter: li wei This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-20789) EC2: manage new computeCurrentGen (c3.*) instances
Julien Carsique commented on JENKINS-20789 EC2: manage new computeCurrentGen (c3.*) instances https://github.com/jenkinsci/ec2-plugin/pull/71 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-20789) EC2: manage new computeCurrentGen (c3.*) instances
Julien Carsique stopped work on JENKINS-20789 EC2: manage new computeCurrentGen (c3.*) instances Change By: Julien Carsique (27/Nov/13 4:28 PM) Status: In Progress 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/groups/opt_out.
[JIRA] [tap] (JENKINS-20212) TAP Plugin Uses High CPU/IO When Projects Have Lots of Tests
Ralph Bolton commented on JENKINS-20212 TAP Plugin Uses High CPU/IO When Projects Have Lots of Tests If junit is the only way to go, then maybe we'll go ahead and generate junit results instead of TAP (although the converter may find its way into our Perl unit testing). It would be a shame though, as TAP is all we really need, and very console-friendly. For now, we've restricted the problematic (massive) project to keeping only 5 previous builds - it seems to behave itself much better now, but it's not really a great solution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command
Ian Will commented on JENKINS-20387 Timeout (10min) on git clone command Same answer as above, but with more hand-holding for ubuntu servers. sudo /etc/init.d/jenkins stop sudo vi /etc/init.d/jenkins (insert this directly below DAEMON_ARGS) #Timeout is in minutes, 120 = 2 hours JAVA_ARGS="-Dorg.jenkinsci.plugins.gitclient.Git.timeOut=120" sudo /etc/init.d/jenkins start This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command
Ian Will edited a comment on JENKINS-20387 Timeout (10min) on git clone command I can confirm that updating the timeout resolved the issue for our very large repository. Here's a bit more hand-holding for ubuntu servers. sudo /etc/init.d/jenkins stop sudo vi /etc/init.d/jenkins (insert this directly below DAEMON_ARGS) #Timeout is in minutes, 120 = 2 hours JAVA_ARGS="-Dorg.jenkinsci.plugins.gitclient.Git.timeOut=120" sudo /etc/init.d/jenkins start This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Dale King commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Is this going to be fixed anytime soon? Jenkins is pretty much unusable in this state, e.g. you cannot submit changes to configuration. I am very close to switching to Hudson. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-20793) add "delete snapshot" build step
cforce updated JENKINS-20793 add "delete snapshot" build step Change By: cforce (27/Nov/13 5:07 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-20793) add "delete snapshot" build step
cforce created JENKINS-20793 add "delete snapshot" build step Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud Created: 27/Nov/13 5:07 PM Description: We wann make a snapshost, do some critical opertion, If fails wen wanna revert and if sucess we wanna delete the snapshot. We can do all except "delete the snapshost" we created just before. This will lead to massive creation of stacked snapshost by time and make system ressource cirtical. Please add new task "delete snapshot" and "consolidate" Project: Jenkins Priority: Major Reporter: cforce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Cannot connect to Jenkins from another PC
Hello, I'n a newbie to Jenkins and configured it on a Windows 7 64 bit system. I've configured email to be sent once build completes. In the email there is a link such as: Check console output at http://mysever:8080/job/MyBuildProj/41/ to view the results. If I click the link I get an error in the browser: Could not connect to ... I've opened port 8080 on myserver; there is no other webserver running on myserver; I thought Jenkins would do all the setup for me. I can open the same link if done locally. I launch Jenkins from within a dos box, as admin. There are no errors in it when I attempt to connect. I'm guessing there is a Windows setup issue on myserver, but I'm not sure what. Any suggestion appreciated. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Cannot-connect-to-Jenkins-from-another-PC-tp4682678.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
Elan Ruusamäe commented on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Here, downgrade to 1.3 from 1.4.1 solved similar problem for me http://mirrors.jenkins-ci.org/plugins/ssh-agent/1.3/ Started by user anonymous Building remotely on lumpy in workspace /home/glen/jenkins/workspace/pld32-chef [ssh-agent] Using credentials tomcat [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] FATAL: Could not find a suitable ssh-agent provider [ssh-agent] Diagnostic report [ssh-agent] * Java/JNR ssh-agent [ssh-agent] java.io.IOException: Remote call on lumpy failed [ssh-agent] at hudson.remoting.Channel.call(Channel.java:723) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentFactory.start(JNRRemoteAgentFactory.java:61) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.(SSHAgentBuildWrapper.java:211) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:123) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:93) [ssh-agent] at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:78) [ssh-agent] at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:559) [ssh-agent] at hudson.model.Run.execute(Run.java:1592) [ssh-agent] at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) [ssh-agent] at hudson.model.ResourceController.execute(ResourceController.java:88) [ssh-agent] at hudson.model.Executor.run(Executor.java:237) [ssh-agent] Caused by: java.lang.UnsatisfiedLinkError: /lib/libc.so.6: wrong ELF class: ELFCLASS32 [ssh-agent] at jnr.ffi.provider.jffi.NativeLibrary.loadNativeLibraries(NativeLibrary.java:87) [ssh-agent] at jnr.ffi.provider.jffi.NativeLibrary.getNativeLibraries(NativeLibrary.java:70) [ssh-agent] at jnr.ffi.provider.jffi.NativeLibrary.getSymbolAddress(NativeLibrary.java:49) [ssh-agent] at jnr.ffi.provider.jffi.NativeLibrary.findSymbolAddress(NativeLibrary.java:59) [ssh-agent] at jnr.ffi.provider.jffi.AsmLibraryLoader.generateInterfaceImpl(AsmLibraryLoader.java:125) [ssh-agent] at jnr.ffi.provider.jffi.AsmLibraryLoader.loadLibrary(AsmLibraryLoader.java:63) [ssh-agent] at jnr.ffi.provider.jffi.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:43) [ssh-agent] at jnr.ffi.LibraryLoader.load(LibraryLoader.java:228) [ssh-agent] at jnr.ffi.Library.loadLibrary(Library.java:123) [ssh-agent] at jnr.ffi.Library.loadLibrary(Library.java:80) [ssh-agent] at jnr.unixsocket.Native$LibC.(Native.java:40) [ssh-agent] at jnr.unixsocket.Native.libsocket(Native.java:60) [ssh-agent] at jnr.unixsocket.Native.socket(Native.java:68) [ssh-agent] at jnr.unixsocket.UnixServerSocketChannel.(UnixServerSocketChannel.java:38) [ssh-agent] at jnr.unixsocket.UnixServerSocket.(UnixServerSocket.java:29) [ssh-agent] at jnr.unixsocket.UnixServerSocketChannel.open(UnixServerSocketChannel.java:48) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.start(AgentServer.java:67) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.(JNRRemoteAgent.java:64) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:54) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:35) [ssh-agent] at hudson.remoting.UserRequest.perform(UserRequest.java:118) [ssh-agent] at hudson.remoting.UserRequest.perform(UserRequest.java:48) [ssh-agent] at hudson.remoting.Request$2.run(Request.java:326) [ssh-agent] at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) [ssh-agent] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [ssh-agent] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [ssh-agent] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [ssh-agent] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [ssh-agent] at java.lang.Thread.run(Thread.java:662) FATAL: [ssh-agent] Unable to start agent hudson.util.IOException2: [ssh-agent] Unable to start agent at com.cloud
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
Elan Ruusamäe edited a comment on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Here, downgrade to 1.3 from 1.4.1 solved similar problem for me http://mirrors.jenkins-ci.org/plugins/ssh-agent/1.3/ Started by user anonymous Building remotely on lumpy in workspace /home/glen/jenkins/workspace/pld32-chef [ssh-agent] Using credentials tomcat [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] FATAL: Could not find a suitable ssh-agent provider [ssh-agent] Diagnostic report [ssh-agent] * Java/JNR ssh-agent [ssh-agent] java.io.IOException: Remote call on lumpy failed [ssh-agent] at hudson.remoting.Channel.call(Channel.java:723) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentFactory.start(JNRRemoteAgentFactory.java:61) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.(SSHAgentBuildWrapper.java:211) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:123) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:93) [ssh-agent] at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:78) [ssh-agent] at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:559) [ssh-agent] at hudson.model.Run.execute(Run.java:1592) [ssh-agent] at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) [ssh-agent] at hudson.model.ResourceController.execute(ResourceController.java:88) [ssh-agent] at hudson.model.Executor.run(Executor.java:237) [ssh-agent] Caused by: java.lang.UnsatisfiedLinkError: /lib/libc.so.6: wrong ELF class: ELFCLASS32 [ssh-agent] at jnr.ffi.provider.jffi.NativeLibrary.loadNativeLibraries(NativeLibrary.java:87) [ssh-agent] at jnr.ffi.provider.jffi.NativeLibrary.getNativeLibraries(NativeLibrary.java:70) [ssh-agent] at jnr.ffi.provider.jffi.NativeLibrary.getSymbolAddress(NativeLibrary.java:49) [ssh-agent] at jnr.ffi.provider.jffi.NativeLibrary.findSymbolAddress(NativeLibrary.java:59) [ssh-agent] at jnr.ffi.provider.jffi.AsmLibraryLoader.generateInterfaceImpl(AsmLibraryLoader.java:125) [ssh-agent] at jnr.ffi.provider.jffi.AsmLibraryLoader.loadLibrary(AsmLibraryLoader.java:63) [ssh-agent] at jnr.ffi.provider.jffi.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:43) [ssh-agent] at jnr.ffi.LibraryLoader.load(LibraryLoader.java:228) [ssh-agent] at jnr.ffi.Library.loadLibrary(Library.java:123) [ssh-agent] at jnr.ffi.Library.loadLibrary(Library.java:80) [ssh-agent] at jnr.unixsocket.Native$LibC.(Native.java:40) [ssh-agent] at jnr.unixsocket.Native.libsocket(Native.java:60) [ssh-agent] at jnr.unixsocket.Native.socket(Native.java:68) [ssh-agent] at jnr.unixsocket.UnixServerSocketChannel.(UnixServerSocketChannel.java:38) [ssh-agent] at jnr.unixsocket.UnixServerSocket.(UnixServerSocket.java:29) [ssh-agent] at jnr.unixsocket.UnixServerSocketChannel.open(UnixServerSocketChannel.java:48) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.start(AgentServer.java:67) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.(JNRRemoteAgent.java:64) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:54) [ssh-agent] at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:35) [ssh-agent] at hudson.remoting.UserRequest.perform(UserRequest.java:118) [ssh-agent] at hudson.remoting.UserRequest.perform(UserRequest.java:48) [ssh-agent] at hudson.remoting.Request$2.run(Request.java:326) [ssh-agent] at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) [ssh-agent] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [ssh-agent] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [ssh-agent] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [ssh-agent] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [ssh-agent] at java.lang.Thread.run(Thread.java:662) FATAL: [ssh-agent] Unable to start agent hudson.util.IOException2: [ssh-agent] Unable to start agent at com.
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
Elan Ruusamäe commented on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Also someone from irc said that you should use jsch-agentproxy in your code, so such problems would not occour. 18:46:09 nDuff> glen: ...I'd argue that that plugin is arguably doing the Wrong Thing if it isn't using the jsch-agentproxy implementation, which should work just fine without native components. 18:57:25 msabramo> kinow: weird 18:58:03 msabramo> that would suck if people have to recreate their projects to use the plugin 18:59:07 glen> msabramo: well. i have ssh slaves plugin pinned to some dead old version due that, 0.27 (1.5 is current) 18:59:10 +kinow> msabramo: indeed. But there should be a way to avoid it. 18:59:32 glen> msabramo: so it's kind of possible to have it autopinned or whatever SSH Slaves plugin did there to pin here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cvs] (JENKINS-20794) Jenkins doesn't detect CVS changes (polling)
Chris Shearer Cooper created JENKINS-20794 Jenkins doesn't detect CVS changes (polling) Issue Type: Bug Assignee: Unassigned Components: cvs Created: 27/Nov/13 5:53 PM Description: Jenkins has stopped launching jobs when the CVS repository changes (unfortunately we are still stuck polling for now). In the "CVS Polling Log" for the job I see: CVS Polling Log Started on Nov 27, 2013 10:42:17 AM cvs rlog -S -d27 Nov 2013 08:26:12 -0700<27 Nov 2013 10:32:17 -0700 PROJECT cvs rlog: Logging PROJECT (snip) Done. Took 2.2 sec No changes And when I type the same command into the command line I get different results: cvs rlog -S -d"27 Nov 2013 08:26:12 -0700<27 Nov 2013 10:32:17 -0700" PROJECT cvs rlog: Logging PROJECT (snip) RCS file: CVS/PROJECT/FILE.txt,v head: 1.4 branch: locks: strict access list: keyword substitution: o total revisions: 4; selected revisions: 1 description: revision 1.4 date: 2013-11-27 10:32:05 -0700; author: ME; state: Exp; lines: +0 -1; commitid: dNRJCnHf3vUMmWex; COMMENT = Project: Jenkins Priority: Major Reporter: Chris Shearer Cooper This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Scott MacDonald commented on JENKINS-18736 PAM authertication over NIS server does not work I am seeing them same problem after everything was working properly for months. We starting seeing this issue yesterday immediately following a reboot to install EnvInject PLugin(which is now uninstalled, without fixing the error) We originally had "Unix user/group database" configured with "Service sshd" and "jenkins" user was NOT part of linux group "shadow". We have tried changing "service" to "ssh"(no back to "sshd") and have added jenkins user to linux group "shadow" Nothing has had any affect. The linux credentials are indeed valid, and we can ssh directly to the box without any problem. OS is Ubuntu 12.04.2 LTS We really need authentication working, so any help is GREATLY appreciated. Nov 27, 2013 5:32:27 PM hudson.security.AuthenticationProcessingFilter2 onUnsuccessfulAuthentication INFO: Login attempt failed org.acegisecurity.BadCredentialsException: pam_authenticate failed : Authentication failure; nested exception is org.jvnet.libpam.PAMException: pam_authenticate failed : Authentication failure at hudson.security.PAMSecurityRealm.authenticate(PAMSecurityRealm.java:78) at hudson.security.AbstractPasswordBasedSecurityRealm$Authenticator.retrieveUser(AbstractPasswordBasedSecurityRealm.java:135) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java: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 org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.h
[JIRA] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Scott MacDonald edited a comment on JENKINS-18736 PAM authertication over NIS server does not work I am seeing them same problem after everything was working properly for months. We starting seeing this issue yesterday immediately following a reboot to install EnvInject PLugin(which is now uninstalled, without fixing the error) We originally had "Unix user/group database" configured with "Service sshd" and "jenkins" user was NOT part of linux group "shadow". We have tried changing "service" to "ssh"(now back to "sshd") and have added jenkins user to linux group "shadow" Nothing has had any affect. The linux credentials are indeed valid, and we can ssh directly to the box without any problem. OS is Ubuntu 12.04.2 LTS We really need authentication working, so any help is GREATLY appreciated. Nov 27, 2013 5:32:27 PM hudson.security.AuthenticationProcessingFilter2 onUnsuccessfulAuthentication INFO: Login attempt failed org.acegisecurity.BadCredentialsException: pam_authenticate failed : Authentication failure; nested exception is org.jvnet.libpam.PAMException: pam_authenticate failed : Authentication failure at hudson.security.PAMSecurityRealm.authenticate(PAMSecurityRealm.java:78) at hudson.security.AbstractPasswordBasedSecurityRealm$Authenticator.retrieveUser(AbstractPasswordBasedSecurityRealm.java:135) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java: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 org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.j
[JIRA] [cvs] (JENKINS-20794) Jenkins doesn't detect CVS changes (polling)
Chris Shearer Cooper commented on JENKINS-20794 Jenkins doesn't detect CVS changes (polling) Jenkins 1.537, CVS Plug-in 2.11, OSX 10.7.5, latest release of CVS (which isn't saying much) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Jenkins not detecting CVS changes (polling)
Jenkins is no longer detecting when CVS changes (we're stuck doing polling for now). When I look in the "CVS Polling Log" for my job I see it run the "cvs rlog" command and conclude "No changes", when I run the same rlog command from the command line (with double-quotes around the date range to keep bash happy) it shows the changed file. Jenkins 1.537, CVS Plug-in 2.11, OSX 10.7.5, latest release of CVS (which isn't saying much). I've added this as issue JENKINS-20794. Has anyone else seen this behavior? Thanks, Chris -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Jenkins-not-detecting-CVS-changes-polling-tp4682688.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-9792) OpenID Javascript does not load - 403
SCM/JIRA link daemon commented on JENKINS-9792 OpenID _javascript_ does not load - 403 Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/plugins/openid/StaticResourceServer.java src/main/resources/hudson/plugins/openid/OpenIdLoginService/_openid-form-body.jelly src/main/resources/hudson/plugins/openid/OpenIdLoginService/loginFragment.jelly src/test/java/hudson/plugins/openid/OpenIdLoginServiceTest.java http://jenkins-ci.org/commit/openid-plugin/64ec740cd394e39e67129313dd4903e262bf2d41 Log: [FIXED JENKINS-9792] OpenID plugin shouldn'd require global read access for authenticating users This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-9792) OpenID Javascript does not load - 403
SCM/JIRA link daemon resolved JENKINS-9792 as Fixed OpenID _javascript_ does not load - 403 Change By: SCM/JIRA link daemon (27/Nov/13 6:41 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-20660) xshell: java.lang.NullPointerException from regex after updating to version 0.9
Mark Waite commented on JENKINS-20660 xshell: java.lang.NullPointerException from regex after updating to version 0.9 I submitted a pull request to fix this - https://github.com/jenkinsci/xshell-plugin/pull/10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-11746) OpenID plugin gives NPE in OpenId Plugin at OpenIdSsoSecurityRealm.doFinishLogin(OpenIdSsoSecurityRealm.java:159)
Kohsuke Kawaguchi resolved JENKINS-11746 as Not A Defect OpenID plugin gives NPE in OpenId Plugin at OpenIdSsoSecurityRealm.doFinishLogin(OpenIdSsoSecurityRealm.java:159) This is normally the result of host name mismatch — you access the login page under one host name, then OpenID server redirecting you back to Jenkins on another host name. As far as the browser is concerned, those two host names are two different sites, not session cookies get sent, and Jenkins fails to find it. Check your Jenkins URL configuration. Change By: Kohsuke Kawaguchi (27/Nov/13 6:43 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Hallvard Nygård updated JENKINS-20630 Jenkins fails to start Change By: Hallvard Nygård (27/Nov/13 6:45 PM) Environment: Microsoft Windows Server 2003 R2Microsoft Windows 2008 server w/TomcatMicrosoft Windows XP SP3Microsoft Windows 7 x64 SP1 Microsoft Windows Server 2012 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [github-oauth] (JENKINS-16350) "logout" link doesn't work
Kohsuke Kawaguchi resolved JENKINS-16350 as Won't Fix "logout" link doesn't work I don't see how to fix this. As kylecordes wrote, what's really happening is: Jenkins logs you out, redirects you back to the Jenkins page you were in. Jenkins sees a new you, now anoanymous. It decides to authenticate you. Jenkins sends you to OpenID server OpenID server is configured to automatically log you in (aka "remember this website") Jenkins logs you right back in. This happens if (1) you use OpenID in SSO mode, (2) you do not grant anonymous read access, and (3) your OpenID server remembers you. You have to log out by going to your OpenID server. We can't really get rid of the logout link, because if you do allow anonyomus read access then this feature would work as expected. If you see this problem where the above 3 assumptions do not hold, please describe your setup in details and reopen this ticket. Change By: Kohsuke Kawaguchi (27/Nov/13 6:55 PM) Status: Open Resolved Assignee: Michael O'Cleirigh Kohsuke Kawaguchi Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-14843) OpenID SSO should use POST to submit details to google apps endpoint
SCM/JIRA link daemon commented on JENKINS-14843 OpenID SSO should use POST to submit details to google apps endpoint Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/plugins/openid/impl/TeamsExtension.java http://jenkins-ci.org/commit/openid-plugin/e5bf3e92ca99e095565510ea8504b3c0debba99f Log: JENKINS-14843 We can't merge the proposed patch as is, and we should switch to POST if that's what has to happen. In the mean time, at least provide an escape hatch to allow people to bypass the team extension. Run Jenkins with -Dhudson.plugins.openid.impl.TeamsExtension.disable=true to disable the team extension. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-9978) yadis exception seen on openID SSO on gmail
SCM/JIRA link daemon commented on JENKINS-9978 yadis exception seen on openID SSO on gmail Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/plugins/openid/OpenIdLoginService.java http://jenkins-ci.org/commit/openid-plugin/62485113a49b79e8fb9a66809b4b0cb92ad6535c Log: JENKINS-9978 Improve the error diagnosis When YADIS discovery fails, openid4java does not report the URL it is hitting, making error diagnosis difficult. Compare: https://github.com/jenkinsci/openid-plugin/compare/48a59a543d88...62485113a49b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-9978) yadis exception seen on openID SSO on gmail
Kohsuke Kawaguchi commented on JENKINS-9978 yadis exception seen on openID SSO on gmail I've improved error diagnosis toward 1.8 to report which URL is failing. Let's see which endpoint is failing to respond in time. Also, please can you tell us what OpenID was typed in? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9740) Access to static content is denied when jenkins works in private mode (anonymous access is disabled)
Kohsuke Kawaguchi resolved JENKINS-9740 as Duplicate Access to static content is denied when jenkins works in private mode (anonymous access is disabled) Change By: Kohsuke Kawaguchi (27/Nov/13 7:06 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/groups/opt_out.
[JIRA] [openid] (JENKINS-16612) Openid plugin does not work because of invalid return_to
Kohsuke Kawaguchi commented on JENKINS-16612 Openid plugin does not work because of invalid return_to It appears to have something to do with parameter decoding, but I'm not sure how this happens. Which OpenID server did you talk to? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-10321) Can't use JNLP-based slave in OpenID SSO mode
Kohsuke Kawaguchi resolved JENKINS-10321 as Fixed Can't use JNLP-based slave in OpenID SSO mode This has been resolved since 1.503 as a part of SECURITY-54 fix. Change By: Kohsuke Kawaguchi (27/Nov/13 7:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-14760) Failed to instantiate class hudson.plugins.openid.GoogleAppSsoSecurityRealm
SCM/JIRA link daemon commented on JENKINS-14760 Failed to instantiate class hudson.plugins.openid.GoogleAppSsoSecurityRealm Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/plugins/openid/OpenIdLoginService.java src/main/java/hudson/plugins/openid/OpenIdSsoSecurityRealm.java src/main/java/hudson/plugins/openid/YadisResolver2.java http://jenkins-ci.org/commit/openid-plugin/ca6531e56496744ad583bcb8dd619f87050c628c Log: Using an improved version in SSO mode as well. This would help diagnose issues like JENKINS-14760. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-14760) Failed to instantiate class hudson.plugins.openid.GoogleAppSsoSecurityRealm
Kohsuke Kawaguchi resolved JENKINS-14760 as Not A Defect Failed to instantiate class hudson.plugins.openid.GoogleAppSsoSecurityRealm openid plugin 1.8 will contain an improvement in error diagnosis that tells you which URL had caused the problem. But the root cause of the problem is that your endpoint is in SSL, and the certificate fails to validate. Check the validity of the certificate, and make sure the root CA is in Java's root certificate list. If you'd rather get stuff working without figuring out all the gory details, you can also opt for [bypassing the SSL check entirely](https://wiki.jenkins-ci.org/display/JENKINS/Skip+Certificate+Check+plugin). This has the same effect of having your server running over plain HTTP, which has security impliations. Change By: Kohsuke Kawaguchi (27/Nov/13 7:21 PM) Status: Reopened Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-16162) Make OpenID plugin work even when anonymous user hasn't any permissions
Kohsuke Kawaguchi resolved JENKINS-16162 as Duplicate Make OpenID plugin work even when anonymous user hasn't any permissions Change By: Kohsuke Kawaguchi (27/Nov/13 7:21 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/groups/opt_out.
[JIRA] [openid] (JENKINS-16463) OpenID plugin does not work when Jenkins run behind apache2 + SSL
Kohsuke Kawaguchi resolved JENKINS-16463 as Not A Defect OpenID plugin does not work when Jenkins run behind apache2 + SSL The problem is that you didn't set the Jenkins root URL correctly. Jenkins needs to know the URL people access it with, or else things like this will not work. Change By: Kohsuke Kawaguchi (27/Nov/13 7:24 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20795) Jenkins hangs/unrepsonsive occasionally (with one core at100%)
Klaus Schniedergers created JENKINS-20795 Jenkins hangs/unrepsonsive occasionally (with one core at100%) Issue Type: Bug Assignee: Unassigned Attachments: dump20131126-0826.txt Components: core Created: 27/Nov/13 7:24 PM Description: About once every 1-2 weeks, our Jenkins service stops responding, i.e. the web page is not responding. The symptoms are "top" showing 100% for a Java process (on a many-cores box, so it looks like only one core is stuck at 100%). There are not obvious issues/errors in the log that are leasing up to this issue. A thread dump is attached. Environment: Jenkins 1.539 on Ubuntu 12.04 LTS Project: Jenkins Priority: Major Reporter: Klaus Schniedergers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20795) Jenkins hangs/unresponsive occasionally (with one core at100%)
Klaus Schniedergers updated JENKINS-20795 Jenkins hangs/unresponsive occasionally (with one core at100%) Change By: Klaus Schniedergers (27/Nov/13 7:25 PM) Summary: Jenkins hangs/ unrepsonsive unresponsive occasionally (with one core at100%) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-20091) OpenId plugin (Version1.7) is not working, but 1.5 is working
Kohsuke Kawaguchi commented on JENKINS-20091 OpenId plugin (Version1.7) is not working, but 1.5 is working 1.8 will improve the error message so that we can tell which endpoint it is hitting. That would help us diagnose the problem further. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Scott MacDonald commented on JENKINS-18736 PAM authertication over NIS server does not work Still scowering the net for a solutiojn..not much out there.Found this old, failry definiative blog post from 2009.. Jon Schewe wrote: > Yes, this is the case if you have shadow passwords, which most people > do. You can either run hudson as root or give access to /etc/shadow to a > group, perhaps called 'shadow', and then add the hudson user to that > group. Then it'll work. > > Kohsuke Kawaguchi wrote: >> I've heard from some users that PAM auth can only authenticate the user >> that Hudson is running as, unless Hudson is run as root. >> ## So if I change jenkins to run as root, authentication does indeed work (although I see other breakages launching slaves due which I would now have to sort out) Considering that I have been running for 6 months as jenkins without any problems, I having a hard time buying that running as root is a hard requirement PAM auth. At least it has not been true for us for about 6 months. There's got to be something else going on. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-19949) logout doesn't work when using openid with google apps auth
Kohsuke Kawaguchi resolved JENKINS-19949 as Won't Fix logout doesn't work when using openid with google apps auth Basically what kylecordes said. SSO means you have to log out from SSO server, not from Jenkins, and Jenkins doesn't know where to send you for causing logout. Change By: Kohsuke Kawaguchi (27/Nov/13 7:28 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-11866) OpenID plugin does not work with SSL-only Jenkins
Kohsuke Kawaguchi resolved JENKINS-11866 as Not A Defect OpenID plugin does not work with SSL-only Jenkins This is because Jenkins root URL is not set correctly. Change By: Kohsuke Kawaguchi (27/Nov/13 7:30 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [github-oauth] (JENKINS-16350) "logout" link doesn't work
Kohsuke Kawaguchi reopened JENKINS-16350 "logout" link doesn't work Oops, somehow I thought this was a ticket to the OpenID plugin. Turns out this is about github-oauth plugin! Since this plugin only needs to work with GitHub, there might be a way to do this, including sending the user to the GitHub logout link. Change By: Kohsuke Kawaguchi (27/Nov/13 7:30 PM) Resolution: Won't Fix Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-20599) Handle several testpoints TAP result file
SCM/JIRA link daemon commented on JENKINS-20599 Handle several testpoints TAP result file Code changed in jenkins User: witokondoria Path: src/main/java/hudson/plugins/testlink/result/AbstractTAPResultSeeker.java src/main/java/hudson/plugins/testlink/result/TAPFileNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/TAPMultiTestpointsFileNameResultSeeker.java src/main/resources/hudson/plugins/testlink/result/TAPMultiTestpointsFileNameResultSeeker/config.jelly http://jenkins-ci.org/commit/testlink-plugin/e51fd1bc6d8e1bda852a5f747d572d5c1ece952b Log: [FIXED JENKINS-20599] New result seeker implemented, resulting in one testlink execution for each TAP testpoint This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-20599) Handle several testpoints TAP result file
SCM/JIRA link daemon commented on JENKINS-20599 Handle several testpoints TAP result file Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/hudson/plugins/testlink/result/AbstractTAPFileNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/AbstractTAPResultSeeker.java src/main/java/hudson/plugins/testlink/result/TAPFileNameMultiTestPointsResultSeeker.java src/main/java/hudson/plugins/testlink/result/TAPFileNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/TAPMultiTestpointsFileNameResultSeeker.java src/main/resources/hudson/plugins/testlink/result/TAPFileNameMultiTestPointsResultSeeker/config.jelly src/main/resources/hudson/plugins/testlink/result/TAPMultiTestpointsFileNameResultSeeker/config.jelly http://jenkins-ci.org/commit/testlink-plugin/11c768d64c11e6bf0283b2280d97e107dc7c9f67 Log: JENKINS-20599 Compare: https://github.com/jenkinsci/testlink-plugin/compare/e51fd1bc6d8e^...11c768d64c11 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
