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

Version 1 Next »


Background

    1. Long term proposal from the LFN TAC is to replace Gerrit and Jenkins with a more modern tool chain and use an “As A Service” approach rather than dedicted instances.
    2. General plan is to move to a large cloud hosted solution like GitLab/GitLab-CI
    3. We believe reliability will be better
    4. We calculate that costs will be lower
    5. We believe that more modern SCM will reduce the learning curve for new developers

Approach

    1. Prototype with one or two projects to work out the kinks in Frankfurt
    2. Plan to move at the start of G release if approved by TSC in time.
    3. No project moves unless we are ready

FAQ

  1. Common Login

    1.  Common Login will be based on github accounts not linux foudation accounts

  2. Contributer License Agreements

  3. SCM Reviews

    1.  pull request and branches vs gerrit branches

      1. high level change in flow with git pull vs gerrit

    2. As a Contributer I will use xxx instead of git review -s/git review ....

    3. As a PTL I will see pull requests .....

    4. GUI Differences

      1. Cherry Pick

      2. Abandon

      3. Create Branch

      4. Create Tag

      5. Magic Words


  5. CI Jobs

    1. Instead of jjb on jenkins.onap.org my jobs will be .....

    2. Magic Words

    3. Seeing the job queue

    4. Restarting a job

    5. Seeing build errors

    6. Seeing build status

  6. Support.linuxfoundation.org and AsAService LF supported applciations

    1. How to get help through LF for SCM/CI in As A Service

    2. Escalations

  • No labels