[JIRA] [tap-plugin] (JENKINS-26080) In 'Tap Extended Test Result' page, the link to tap output file is wrong
Title: Message Title Herbert Vojčík commented on JENKINS-26080 Re: In 'Tap Extended Test Result' page, the link to tap output file is wrong It is very useful feature indeed. It is wrong to put it away, unless you allow other easy way to look at the surroundings / output / stacktrace of the failed test (that's what raw tap file was really useful). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-26080) In 'Tap Extended Test Result' page, the link to tap output file is wrong
Herbert Vojčík created JENKINS-26080 In Tap Extended Test Result page, the link to tap output file is wrong Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap-plugin Created: 16/Dec/14 11:33 AM Description: In 'Tap Extended Test Result' page on a build, there is the link to the raw output file just above the table with results. This link points to latest output from workspace, not the actual output of that build. This way, one can see old tap tests in a table, but not as a raw file. Project: Jenkins Priority: Minor Reporter: Herbert Vojčík This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Herbert Vojčík commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) What can be done, is not to install any executors by default, allow users to install master executors by hand, but with visible not that this is not recommended and link to "add a node" screen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online It happens to me as well. Problem is the private key with password. I think it does not use the password to unlock the key. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík edited a comment on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online It happens to me as well (masterslave CentOS). Problem is the private key with password. I think it does not use the password to unlock the key. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Deleting all credentials and creating them anew solved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online @Yoram No need to downgrade for me. Just delete all credentials, restart Jenkins and set them back, and it works with 0.23. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online @HemangL My setup is: no security connecting to slave with password-protected private key. After delete, restart and create it worked fine (I should mention that backed up data, reinstalled whole jenkins (I have it under OpenVZ machine that is created and populated by script, so no big hassle for me) and returned data back, only then I did the delete-restart-recreate). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15919) Broken link for 1.492 on http://pkg.jenkins-ci.org/debian/
Herbert Vojčík commented on JENKINS-15919 Broken link for 1.492 on http://pkg.jenkins-ci.org/debian/ Same for http://pkg.jenkins-ci.org/redhat/. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1555) Remote triggering of builds requires anonymous user Read permission
[ https://issues.jenkins-ci.org/browse/JENKINS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remote triggering of builds requires anonymous user Read permission --- Key: JENKINS-1555 URL: https://issues.jenkins-ci.org/browse/JENKINS-1555 Project: Jenkins Issue Type: Bug Components: security Affects Versions: current Environment: Platform: All, OS: All Reporter: subbaer Priority: Minor Attachments: hudson-active-dir-build-anonymous.jpg I stepwise tried to harden my local hudson installation. Security realm is set to Active Directory. From the Anonymous user I removed all Authorization rights. This broke triggering hudson builds using URL with token. To make it work again I had to assign the Overall - read right to the Anonymous user. Actually, I didn't wanted to have Anonymous users see project details. Could the current behavior be changed by checking the Job - Build right prior to triggered builds? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1555) Remote triggering of builds requires anonymous user Read permission
[ https://issues.jenkins-ci.org/browse/JENKINS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-1555 stopped by Herbert Vojčík. Remote triggering of builds requires anonymous user Read permission --- Key: JENKINS-1555 URL: https://issues.jenkins-ci.org/browse/JENKINS-1555 Project: Jenkins Issue Type: Bug Components: security Affects Versions: current Environment: Platform: All, OS: All Reporter: subbaer Priority: Minor Attachments: hudson-active-dir-build-anonymous.jpg I stepwise tried to harden my local hudson installation. Security realm is set to Active Directory. From the Anonymous user I removed all Authorization rights. This broke triggering hudson builds using URL with token. To make it work again I had to assign the Overall - read right to the Anonymous user. Actually, I didn't wanted to have Anonymous users see project details. Could the current behavior be changed by checking the Job - Build right prior to triggered builds? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1555) Remote triggering of builds requires anonymous user Read permission
[ https://issues.jenkins-ci.org/browse/JENKINS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161596#comment-161596 ] Herbert Vojčík commented on JENKINS-1555: - Hi, it does not work for me, too (1.458, freebsd). Strange is, IIRC it worked on 1.454 or so, I did not give anonymous any access and it worked. Now, it is problem unless I goive anonymous overall read as well as job read. Remote triggering of builds requires anonymous user Read permission --- Key: JENKINS-1555 URL: https://issues.jenkins-ci.org/browse/JENKINS-1555 Project: Jenkins Issue Type: Bug Components: security Affects Versions: current Environment: Platform: All, OS: All Reporter: subbaer Priority: Minor Attachments: hudson-active-dir-build-anonymous.jpg I stepwise tried to harden my local hudson installation. Security realm is set to Active Directory. From the Anonymous user I removed all Authorization rights. This broke triggering hudson builds using URL with token. To make it work again I had to assign the Overall - read right to the Anonymous user. Actually, I didn't wanted to have Anonymous users see project details. Could the current behavior be changed by checking the Job - Build right prior to triggered builds? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
