Changes between Initial Version and Version 1 of CI


Ignore:
Timestamp:
Oct 3, 2018, 4:56:49 PM (4 months ago)
Author:
ahf
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CI

    v1 v1  
     1{{{
     2CI session
     3==========
     4
     5- We should *only* merge code where the CI is not failing.
     6- We should consider having the test-network-all tests running as well as stem
     7  tests.
     8    - Sometimes consensus might fail because of the way we fire off timers eagerly.
     9    - Cascading failure modes for consensus, we might happen for the public
     10      network, but it's more unlikely.
     11    - Let's start by having it as allow to fail tests on Travis while we test it.
     12
     13- We should put high priority to always fixing CI failures.
     14- We should ensure CI passes before we merge more stuff.
     15- Should we have asn/dgoulet create PR's as part of the review ticket triage:
     16  yes, we do, but only for a test period where they note down how much time
     17  they spend.
     18- CI/coverity role creates a ticket when there is CI failure and tries to
     19  ensure that it gets assigned to the right people (subsystem maintainer).
     20- Create ticket when a test has been disabled due to CI failures. Review the
     21  list of tickets at the upcoming network-team meeting.
     22- AppVeyor is currently broken.
     23- If we don't watch AppVeyor we should watch jenkins for Windows' failures.
     24- For volunteers either put their code in a PR and/or put the ticket into needs_info
     25
     26- Rationales for CI:
     27    - When CI is broken on master, it's a lot of work to figure out if it's
     28      master or your own branch that is the problem.
     29}}}