You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Daniel Takamori (JIRA)" <ji...@apache.org> on 2016/09/05 20:50:20 UTC

[jira] [Resolved] (INFRA-11428) VM setup information for Jenkin slaves

     [ https://issues.apache.org/jira/browse/INFRA-11428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Takamori resolved INFRA-11428.
-------------------------------------
    Resolution: Fixed

> VM setup information for Jenkin slaves
> --------------------------------------
>
>                 Key: INFRA-11428
>                 URL: https://issues.apache.org/jira/browse/INFRA-11428
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: Jenkins
>            Reporter: Kevin Minder
>            Assignee: Daniel Takamori
>
> We recently ran into a situations were we had failing build/test only on a particular Jenkin slave (ie ubuntu3).  The only recourse we had to debug the issue was to add additional debugging to the product and new jobs.  It would have been much more efficient and much less disruptive to the other project members if I could have created a local replica VM by having say a Vagrant file that reproduced the setup of ubuntu3 and debugged the issue locally.  I don't know how the Jenkins slaves are currently setup but I figured I'd ask the question in the hopes that there was an easy solution for this.  Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)