[JIRA] [core] (JENKINS-23492) UI improvements / refreshing

2014-07-16 Thread k...@inburke.com (JIRA)














































Kevin Burke
 commented on  JENKINS-23492


UI improvements / refreshing















Hi Ulli,
I'm having trouble reproducing the issues you raised.


	On which page do the buttons appear out of whack? The "Manage Jenkins" page?



I am also having trouble reproducing the FOUC on the "Manage Jenkins" page. Which browser are you using? Are you downloading assets over a network or from your local machine? May be a latency 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/d/optout.


[JIRA] [core] (JENKINS-23434) "None" option should be first in "Source Code Management" dropdown

2014-06-14 Thread k...@inburke.com (JIRA)














































Kevin Burke
 created  JENKINS-23434


"None" option should be first in "Source Code Management" dropdown















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


15/Jun/14 3:22 AM



Description:


The "None" option appears in the middle of the list of "Source Code Management" options which is sort of weird. It should be the top option, and the list of possible version control schemes should be listed below it.

I tried fixing this myself in the source code but it looks like there's just too much magic going on - I tried grepping the source code for "Projectset" which is a word that shows up on screen but couldn't find any files related to CVS or non-abstract SCM classes.




Project:


Jenkins



Priority:


Major



Reporter:


Kevin Burke

























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-16750) Job console output does not refresh when job is done

2014-06-11 Thread k...@inburke.com (JIRA)















































Kevin Burke
 assigned  JENKINS-16750 to Kevin Burke



Job console output does not refresh when job is done
















Change By:


Kevin Burke
(11/Jun/14 9:48 PM)




Assignee:


Kevin Burke



























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-16750) Job console output does not refresh when job is done

2014-06-11 Thread k...@inburke.com (JIRA)














































Kevin Burke
 commented on  JENKINS-16750


Job console output does not refresh when job is done















What action/update is needed to fix this? Does the success/failure handle just need to call redrawLayout or whatever?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [cli] (JENKINS-23364) Rename hudson-dev:run to jenkins-dev:run

2014-06-09 Thread k...@inburke.com (JIRA)














































Kevin Burke
 created  JENKINS-23364


Rename hudson-dev:run to jenkins-dev:run















Issue Type:


Task



Assignee:


Unassigned


Components:


cli, devstack



Created:


09/Jun/14 3:29 AM



Description:


To run Jenkins in development mode, you currently type:

mvn hudson-dev:run

This command should probably be updated to:

mvn jenkins-dev:run

See discussion here: https://groups.google.com/forum/#!topic/jenkinsci-dev/UNW6bWjcgF4




Project:


Jenkins



Priority:


Major



Reporter:


Kevin Burke

























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.