You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Steve Varnau (JIRA)" <ji...@apache.org> on 2015/10/08 00:01:26 UTC

[jira] [Closed] (TRAFODION-105) LP Blueprint: infra-test-infra - infra - Need automated test of infra code for slave set-up

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

Steve Varnau closed TRAFODION-105.
----------------------------------
    Resolution: Won't Fix

Infra changes have many test scenarios depending on whether the changes are in Jenkins, Build, or Test configs.  Hence the testing needs to be customized to the particular change. 

> LP Blueprint: infra-test-infra - infra - Need automated test of infra code for slave set-up
> -------------------------------------------------------------------------------------------
>
>                 Key: TRAFODION-105
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-105
>             Project: Apache Trafodion
>          Issue Type: New Feature
>          Components: Build Infrastructure
>            Reporter: Steve Varnau
>            Priority: Minor
>
> Many infra changes infra repo (buildtest module, cloudera module,...) can impact test results, but infra test jobs do not test viability of slave test environment.
> We need dev/test nodes for slaves, and perhaps zuul and jenkins to properly test infra before impacting the production environment. Like install testing, this has restrictions, since puppet runs as root. So this can not be run in unsupervised check testing.
> Also these test machines can not be updated from "production" puppet configuration with time-based runs, but must be tested with puppet apply instead.
> Should be implemented after infra-upgrade-puppet is implemented.



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