6.05 KB
Newer Older
PRUVOST Florent's avatar
PRUVOST Florent committed
* To contribute to the project, you need to do it through merge request
2 3 4
** Create a fork
   First you need to fork the repository into your own account. You can
   do that simply by clicking the fork button on the gitlab interface.

PRUVOST Florent's avatar
PRUVOST Florent committed

8 9 10 11 12 13 14 15 16 17 18
   Then, clone the repository on your laptop:
   #+begin_src sh
   git clone

   Once this is done, you can setup the chameleon repository as the
   upstream of your clone to simplify the update of your fork
   #+begin_src sh
   git remote add upstream
PRUVOST Florent's avatar
PRUVOST Florent committed

20 21 22 23 24 25 26 27
   To update your fork with the upstream chameleon's state:
   #+begin_src sh
   git pull upstream master
   git push -u origin master

** Create a "Feature" branch in your fork

PRUVOST Florent's avatar
PRUVOST Florent committed
28 29
   To add a new feature, fix a bug, and so on, you need to create a
   new branch from the last state of the master branch
30 31 32 33 34
   #+begin_src sh
   git branch your_branch_name
   git checkout your_branch_name

PRUVOST Florent's avatar
PRUVOST Florent committed
35 36
   Apply your modifications in that "Feature" branch. Then, you need
   to push this branch on your online repository
   #+begin_src sh
   git push origin your_branch_name
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55

** Merge request
   Once your branch is online, on the gitlab interface, go to the
   branches webpage, select the branch you want to push as a merge
   request, and push the button !!!

   *Be careful to check the 'close after merge' check box, and to push
   to the solverstack/chameleon repository*. By default the checkbox
   may not be checked, and the default repository is your fork.

   If the pull request is made to fix an issue, please name the branch
   "issueXX" so it is automatically linked to the issue. In addition,
   please add "fix issue #xx" in the comment of the pull request to
   automatically close the issue when the PR is merged.

** Rebase on top of 'master'
PRUVOST Florent's avatar
PRUVOST Florent committed
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73
   In some cases your "feature" branch you want to merge into "master"
   has a long life span so that your branch and the master branch
   could make some conflicts. To avoid having to handle the possible
   conflicts at *merge request* time, please rebase your "feature" on
   top of "master" before pushing the button *merge request*.

   To do that, just go at the HEAD of your "feature" branch and rebase
   #+begin_src sh
   git checkout feature
   git rebase master

   Then force to push on your origin
   #+begin_src sh
   git push --force origin feature

   Then push the button *merge request*.

75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142
* Configure a runner to test your branch
  To be effectively merged, your branch must be tested through the
  [[][gitlab-ci]] mechanism.

  In order to execute the tests the contributor should define his own
  /gitlab runner/, /e.g/. his laptop or any other remote machine. To avoid
  having to install the proper dependencies in every runners we use
  the [[][Docker]] image /hpclib/hiepacs/ whose recipe is defined
  [[][here]]. Consequently, to register a compatible runner the requirements
  on the system are :
  * OS must be Linux
  * Docker must be installed, e.g.
    #+begin_src sh
    sudo apt-get update && sudo apt-get install -y curl
    curl -fsSL | sudo apt-key add -
    sudo apt install -y software-properties-common
    sudo add-apt-repository "deb [arch=amd64] $(lsb_release -cs) stable"
    sudo apt-get update
    sudo apt install -y docker-ce
    sudo usermod -aG docker ${USER}
    newgrp docker

*** Register your runner
    Please read first the [[][Gitlab documentation]] for general information
    about runners registration.

    Three steps are required:
    1) install the gitlab-runner program
    2) register your runner to your project (your fork of Chameleon)
    3) start gitlab-runner as a service
    #+begin_src sh
    # install gitlab-runner
    sudo wget -O /usr/local/bin/gitlab-runner
    sudo chmod +x /usr/local/bin/gitlab-runner
    sudo useradd --comment 'GitLab Runner' --create-home gitlab-runner --shell /bin/bash

    # register runner to
    sudo gitlab-runner register # see just after for an example

    # install and run as a service
    sudo gitlab-runner install --user=gitlab-runner --working-directory=/home/gitlab-runner
    sudo gitlab-runner start

    Example of registering sequence:
    sudo gitlab-runner register
    Please enter the gitlab-ci coordinator URL (e.g.
    Please enter the gitlab-ci token for this runner:
    # copy/paste the project's secret token here
    Please enter the gitlab-ci description for this runner:
    Please enter the gitlab-ci tags for this runner (comma separated):
    linux, ubuntu
    Whether to run untagged builds [true/false]:
    [false]: true
    Whether to lock Runner to current project [true/false]:
    Registering runner... succeeded                     runner=4jknGvoz
    Please enter the executor: shell, ssh, docker+machine, docker-ssh+machine, kubernetes, docker, parallels, virtualbox, docker-ssh:
    Please enter the default Docker image (e.g. ruby:2.1):
    Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!

143 144 145 146 147 148 149 150 151 152 153 154
* To review locally a private pull request submitted by someone else

   Get the patch from the pull request (Need to update that !!!!
   Coming from bitbucket)
   #+begin_src sh
   curl > pr#PR.patch

   Then apply the patch on your local copy
   #+begin_src sh
   git apply pr#PR.patch