[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured

2014-12-04 Thread robert.dahlst...@ongame.com (JIRA)












































  
Robert Dahlström
 edited a comment on  JENKINS-10191


JDK selection is hidden even when a JDK is configured 
















Just ran into this as well and a bit of googling led me here. However, my wants are slightly different: I'd also like an option to tell Jenkins to explicitly use the System provided JDK. Mainly because the Jenkins I currently maintain should use the same JDK/JRE we have in production and we maintain the JDK/JRE with puppet, outside of the Jenkins eco-system.

I do agree that the current way to work with JDK's in Jenkins is a bit confusing and it does not tie all plugins together (maven job with sonar's 'inherit from job' when the job's JDK is 'Default' is one such example).



























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-10191) JDK selection is hidden even when a JDK is configured

2014-12-04 Thread robert.dahlst...@ongame.com (JIRA)














































Robert Dahlström
 commented on  JENKINS-10191


JDK selection is hidden even when a JDK is configured 















Just ran into this as well and a bit googling made me end up here. However, my wants are slightly different: I'd also like an option to tell Jenkins to explicitly use the System JDK. Mainly because the Jenkins I currently maintain should use the same JDK/JRE we have in production and we maintain the JDK/JRE with puppet, outside of the Jenkins eco-system.

I do agree that the current way to work with JDK's in Jenkins is a bit confusing and it does not tie all plugins together (maven job with sonar's 'inherit from job' when the job's JDK is 'Default' is one such example).



























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] (JENKINS-16886) 500 Error when type the git url during creating new job

2013-02-20 Thread robert.dahlst...@ongame.com (JIRA)














































Robert Dahlström
 commented on  JENKINS-16886


500 Error when type the git url during creating new job















Downgrading from 1.1.29 to 1.1.26 solved it for me.
I have jenkins git client plugin 1.0.2 installed.

Have not tried with the latest 1.2.0 release yet.



























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.