DRAFT FOR COMMENT FROM THE WORKING TEAM

Introduction

The LFN Technical Community is critically dependent on its software development tool chain for success. The standard tool chain today is Gerrit for Source Code Management (SCM) , Jenkins for Continuous Integration / Continuous Deliver (CI/CD)  and Nexus for artifact repositories.

...

This recommendation is provided to the Technology Advisory Council for communication to the projects within Linux Foundation Networking. No specific implementation plans are included, just recommendations.

The default preferred path for new generic software projects that do not have a dependency on non-standard hardware resources and/or gerrit for legacy code is to use a pull model based SCM.

For all hosted solutions we recommend:

   Github  ->  Circleci  ->  packagecloud

Some projects may need premises versions for compatibility with corporate build environments

    GITLAB  > GITLABci  -> packagecloud

If non-standard hardware resources are required in addition:
   Github  ->  Circleci (for normal jobs)   ->  packet.net ( several possible launching methods including terraform)  -> packagecloud

If even more specialized hardware is needed:
     GitHub -> circleci                                                                                -> packagecloud
                 ->  drone.io server launching on nomadproject.io cluster    ^DRAFT FOR DISCUSSION AT THE INFRASTRUCTURE WORKING GROUP -DOES NOT REPRESENT CONSENSUS

Should the TAC recommend to member projects that they move off Gerrit/Jenkins/Nexus and onto a new tool chain ?

...