[JIRA] [core] (JENKINS-21092) Adaptable UI for Mobile Devices
Bruno Meneguello created JENKINS-21092 Adaptable UI for Mobile Devices Issue Type: New Feature Assignee: Unassigned Attachments: proto.png Components: core Created: 19/Dec/13 12:50 PM Description: Jenkins interface is targeted for desktop browsers, with large screens and mouse pointers. Frequently I use Jenkins via mobile devices with 4" screens and I need to zoom in and out to be able to read and click. I suggest to tune the UI to adapt to small/medium/large screens. The layout changes needn't to be radical. Just being able to flow the screen vertically and allow the elements to be shrinked horizontally to fit on small device screens help a lot. Environment: mobile Project: Jenkins Priority: Major Reporter: Bruno Meneguello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20734) NPE on some operations after restart
Bruno Meneguello created JENKINS-20734 NPE on some operations after restart Issue Type: Bug Affects Versions: current Assignee: Bruno Meneguello Components: ec2 Created: 22/Nov/13 8:58 PM Description: After restart Jenkins, the ec2 slaves forgets is cloud (the cloud attribute becames null) and then, when any operation needs to connect to the cloud, throws a NPE Project: Jenkins Priority: Critical Reporter: Bruno Meneguello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20352) computer/*/configure view doesn't render completely and displays exception
Bruno Meneguello commented on JENKINS-20352 computer/*/configure view doesnt render completely and displays exception Fixed at pull requests #68 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20352) computer/*/configure view doesn't render completely and displays exception
Bruno Meneguello edited a comment on JENKINS-20352 computer/*/configure view doesnt render completely and displays exception Fixed at pull requests #68 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-13416) On demand slave provisioning is starting all available slaves
[ https://issues.jenkins-ci.org/browse/JENKINS-13416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Meneguello updated JENKINS-13416: --- Attachment: jenkins-1.459.diff Description: I'm using on demand slaves (on amazon) started by a shell script. When starting a job with all slaves disconnected, all my slaves are started together. When in debug, I'd noticed that RetentionStrategy Demand is testing Computer.getDemandStartMilliseconds() to connect the slave, but all slaves (that 'll take some time to wake up) pass in test. Shouldn't this strategy take in account if there are executor enough and nodes starting? I,ve made a change in RetentionStrategy that solves the problem. Anyone see any problem with this solution? was: I'm using on demand slaves (on amazon) started by a shell script. When starting a job with all slaves disconnected, all my slaves are started together. When in debug, I'd noticed that RetentionStrategy Demand is testing Computer.getDemandStartMilliseconds() to connect the slave, but all slaves (that 'll take some time to wake up) pass in test. Shouldn't this strategy take in account if there are executor enough and nodes starting? On demand slave provisioning is starting all available slaves - Key: JENKINS-13416 URL: https://issues.jenkins-ci.org/browse/JENKINS-13416 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Reporter: Bruno Meneguello Assignee: Kohsuke Kawaguchi Priority: Minor Attachments: jenkins-1.459.diff I'm using on demand slaves (on amazon) started by a shell script. When starting a job with all slaves disconnected, all my slaves are started together. When in debug, I'd noticed that RetentionStrategy Demand is testing Computer.getDemandStartMilliseconds() to connect the slave, but all slaves (that 'll take some time to wake up) pass in test. Shouldn't this strategy take in account if there are executor enough and nodes starting? I,ve made a change in RetentionStrategy that solves the problem. Anyone see any problem with this solution? -- 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-13416) On demand slave provisioning is starting all available slaves
Bruno Meneguello created JENKINS-13416: -- Summary: On demand slave provisioning is starting all available slaves Key: JENKINS-13416 URL: https://issues.jenkins-ci.org/browse/JENKINS-13416 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Reporter: Bruno Meneguello Assignee: Kohsuke Kawaguchi Priority: Minor I'm using on demand slaves (on amazon) started by a shell script. When starting a job with all slaves disconnected, all my slaves are started together. When in debug, I'd noticed that RetentionStrategy Demand is testing Computer.getDemandStartMilliseconds() to connect the slave, but all slaves (that 'll take some time to wake up) pass in test. Shouldn't this strategy take in account if there are executor enough and nodes starting? -- 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
