[jbosstools-issues] [JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv

Ondrej Dockal (Jira) issues at jboss.org
Mon Mar 4 09:12:00 EST 2019


    [ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702082#comment-13702082 ] 

Ondrej Dockal edited comment on JBIDE-25050 at 3/4/19 9:11 AM:
---------------------------------------------------------------

As we moved to Upshift, hyperv seems to be a go on windows 10. Thus I am creating new snapshot that should fulfill our needs. 

Specifics: 
* Setting env. variable: MINISHIFT_HYPERV_VIRTUAL_SWITCH = Default Switch
* Hudson user is added to Hyperv administrators groups 


was (Author: odockal):
As we moved to Upshift, hyperv seems to be a go on windows 10. Thus I am creating new snapshot that should fulfill our needs. 

Specifics: 
* I have added HYPERV_VS virtual switch
* Setting env. variable: MINISHIFT_HYPERV_VIRTUAL_SWITCH = Default Switch
* Hudson user is added to Hyperv administrators groups 

> Prepare windows image with hyperv
> ---------------------------------
>
>                 Key: JBIDE-25050
>                 URL: https://issues.jboss.org/browse/JBIDE-25050
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: integration-tests, qa
>    Affects Versions: 4.5.1.AM2
>            Reporter: Ondrej Dockal
>            Assignee: Ondrej Dockal
>            Priority: Major
>              Labels: jenkins
>             Fix For: 4.11.0.Final
>
>         Attachments: error.log
>
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Provision win10-x64-jbds (as some changes were made to jbds script)
> * Install manually HyperV in fresh windows image 
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jbosstools-issues mailing list