Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Attendees:


Agenda

  1. Amy Mullins  (moved from 5/15 meeting) QRB discussed moving away from the internal EMC Code repo to a private github repo to address ease of use concerns (no longer required to require an account)
    • This would move private lab configs and proprietary skupacks
  2. Amy Mullins  Plans and process to ramp developers and expand merge capabilities across the teams
  3. Former user (Deleted)  RAC-5196:  I would like to better understand the behavior for a workflow that fails but needs to do some clean-up
  4. Former user (Deleted)  Moving PR gates to an external Jenkins instance.  Should we bump this up in priority?  Could help our latest issues on production Jenkins.
  5. Former user (Deleted)  To Vagrant Box or not to Vagrant Box?  Do we know if anyone is using the Vagrant Boxes that we publish?   It seems like more people are building their own for development.
  6. Former user (Deleted)   Are tests part of our release?   Make sure we are all on the same page.   Setting AffectsCommunity for test PRs.
  7. Former user (Deleted)   Timing of the tests in Jenkins.   Should we decrease the frequency of ContinuousFunctionTest?  Currently running every hour but competing for resources.
  8. Former user (Deleted)   I see a lot more on-http Travis failures after the merge goes in but it runs successfully in the PR gates.  Is this a known issue or one that needs to be investigated further.
  9. Former user (Deleted)  Can we get more slaves for the Hopkinton Sandbox Jenkins instance?   A lot of use in this Sandbox now  (Yay!) but it is getting very VM constrained.
  10. Amy Mullins  Deprecated hound checks have been removed last sprint (https://rackhd.atlassian.net/browse/RAC-5147).   
    1. anything left to be considered before making hound checks a merge gate?
  11. Amy Mullins Post package deployment testing
      If tests are passing FIT, need to clarify the expectations/guidelines for post package testing
  12. QRB discussion/suggestions for alleviating resource concerns on the production environment:
        1.  Run MasterCI at a non working time.  It was recently moved to 9am SH time.  Suggest that it be moved to 6am to minimize resource allocation competing with the PR quality gates
        2.  Turn off Docker CIT and OVA CIT in the post test.  CIT is just about all converted with the exception of a few api test.  Erika will be turning them on in the next 1-2 sprints.  This will frees up 2 instances.
        3.  Consolidate the 3 Docker OS Install to a single RackHD Slave instance where Post Package OS Install is executed on a single RackHD Slave instance in parallel.  This will free up 2 slave instances.
        4.  Consolidate the 3 OVA OS Install to a single RackHD Slave instance where Post Package OS Install is executed on a single RackHD Slave instance in parallel.  This will free up 2 slave instances.
        5.  This will drop the RackHD slave instances from 13 to 7.

    QRB question and AI for Alan to check with Peter: What is the purpose of the Vagrant post test?  Who is using the vagrant deployment and does it really need to be in the nightly build? What is currently running for this suite of tests. 

        
  • No labels