[JIRA] (JENKINS-40178) Use new QEMU2 Emulator engine

2017-01-16 Thread atho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Burton commented on  JENKINS-40178  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use new QEMU2 Emulator engine   
 

  
 
 
 
 

 
 Any update on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40178) Use new QEMU2 Emulator engine

2016-12-02 Thread atho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Burton commented on  JENKINS-40178  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use new QEMU2 Emulator engine   
 

  
 
 
 
 

 
 Hey Chris, I compiled a version disabling the check, and it worked great. This was using emulators that had been created via Android Studio though, and not the plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40178) Use new QEMU2 Emulator engine

2016-12-01 Thread ch...@orr.me.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Orr commented on  JENKINS-40178  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use new QEMU2 Emulator engine   
 

  
 
 
 
 

 
 Yeah, I think that a recent emulator release fixed the last of the issues, but I haven't confirmed. Last time I checked, using the new engine, I think I had problems starting emulators that had been created and were started with the old engine — something about not being able to find the correct kernel image. I'll try and check it out, and see what issues there are, if any. If you fancy trying it out, you can change the line of code that keeps us on the old engine and try out a build of the plugin. Or I can create a build of the plugin hardcoded to the new engine if you need for testing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40178) Use new QEMU2 Emulator engine

2016-12-01 Thread atho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Burton created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40178  
 
 
  Use new QEMU2 Emulator engine   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Christopher Orr  
 
 
Components: 
 android-emulator-plugin  
 
 
Created: 
 2016/Dec/02 12:26 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Burton  
 

  
 
 
 
 

 
 Emulators using the new QEMU2 engine are must faster, and more stable. I am currently unable to use the Android Emulator Jenkins plugin as my tests fail with the classic engine. I understand the reason the plugin uses the classic engine is because certain commands like `ports` were not supported. It appears that ports is now supported. Is there anything else stopping the plugin from using the new engine?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment