[Git][cip-project/cip-testing/testing][master] 2 commits: remove 0001.patch


Agustin Benito Bethencourt
 

Agustin Benito Bethencourt pushed to branch master at cip-project / cip-testing / testing

Commits:

  • ddbe6ede
    by Don Brown at 2017-01-20T12:34:08-05:00
    remove 0001.patch
    
  • 40d4405b
    by Don Brown at 2017-02-22T18:43:47+00:00
    Update README.md

2 changed files:

Changes:

  • 0001.patch deleted
    1
    - integration-scripts/install_backend.sh      |  8 +++++++-
    
    2
    - integration-scripts/install_build_script.sh |  9 ++++++++-
    
    3
    - integration-scripts/install_frontend.sh     |  8 +++++++-
    
    4
    - scripts/setup-dev-env.sh                    | 11 +++++++++++
    
    5
    - 4 files changed, 33 insertions(+), 3 deletions(-)
    
    6
    - create mode 100644 scripts/setup-dev-env.sh
    
    7
    -
    
    8
    -diff --git a/integration-scripts/install_backend.sh b/integration-scripts/install_backend.sh
    
    9
    -index 72a974033a3c..157e7184e349 100755
    
    10
    ---- a/integration-scripts/install_backend.sh
    
    11
    -+++ b/integration-scripts/install_backend.sh
    
    12
    -@@ -4,7 +4,13 @@
    
    13
    - # Install kernelci backend
    
    14
    -
    
    15
    - cd $HOME && mkdir git-repos && cd git-repos
    
    16
    --git clone https://github.com/kernelci/kernelci-backend-config.git kernelci-backend
    
    17
    -+
    
    18
    -+GIT_SRC="https://github.com/kernelci/kernelci-backend-config.git"
    
    19
    -+if [ -d /vagrant/kernelci-backend-config ]; then
    
    20
    -+    GIT_SRC=/vagrant/kernelci-backend-config
    
    21
    -+fi
    
    22
    -+git clone $GIT_SRC kernelci-backend
    
    23
    -+
    
    24
    - cp /vagrant/config/secrets-backend.yml kernelci-backend/secrets.yml
    
    25
    -
    
    26
    - # Fixme: Don't let ansible try to create the file in the first place.
    
    27
    -diff --git a/integration-scripts/install_build_script.sh b/integration-scripts/install_build_script.sh
    
    28
    -index 322619317af6..879aaed01792 100755
    
    29
    ---- a/integration-scripts/install_build_script.sh
    
    30
    -+++ b/integration-scripts/install_build_script.sh
    
    31
    -@@ -3,7 +3,14 @@
    
    32
    - # Copyright (C) 2016, Siemens AG, Wolfgang Mauerer <wolfgang.mauerer@...>
    
    33
    - # SPDX-License-Identifier:     Apache-2.0
    
    34
    -
    
    35
    --cd $HOME && git clone https://github.com/kernelci/kernelci-build.git
    
    36
    -+cd $HOME
    
    37
    -+
    
    38
    -+GIT_SRC="https://github.com/kernelci/kernelci-build.git"
    
    39
    -+if [ -d /vagrant/kernelci-build ]; then
    
    40
    -+    GIT_SRC=/vagrant/kernelci-build
    
    41
    -+fi
    
    42
    -+git clone $GIT_SRC
    
    43
    -+
    
    44
    - cd kernelci-build
    
    45
    -
    
    46
    - MASTER_KEY=`cat $HOME/backend-admin-token.txt`
    
    47
    -diff --git a/integration-scripts/install_frontend.sh b/integration-scripts/install_frontend.sh
    
    48
    -index 48ab91ab83ce..251ef89d28f3 100755
    
    49
    ---- a/integration-scripts/install_frontend.sh
    
    50
    -+++ b/integration-scripts/install_frontend.sh
    
    51
    -@@ -4,7 +4,13 @@
    
    52
    - # Install kernelci frontend
    
    53
    -
    
    54
    - cd $HOME/git-repos
    
    55
    --git clone https://github.com/kernelci/kernelci-frontend-config.git kernelci-frontend
    
    56
    -+
    
    57
    -+GIT_SRC="https://github.com/kernelci/kernelci-frontend-config.git"
    
    58
    -+if [ -d /vagrant/kernelci-frontend-config ]; then
    
    59
    -+    GIT_SRC=/vagrant/kernelci-frontend-config
    
    60
    -+fi
    
    61
    -+git clone $GIT_SRC kernelci-frontend
    
    62
    -+
    
    63
    - sed -i kernelci-frontend/roles/install-app/tasks/main.yml \
    
    64
    -     -e 's/kernelci\/kernelci-frontend.git/siemens\/kernelci-frontend.git/'
    
    65
    -
    
    66
    -diff --git a/scripts/setup-dev-env.sh b/scripts/setup-dev-env.sh
    
    67
    -new file mode 100644
    
    68
    -index 000000000000..59c13b233065
    
    69
    ---- /dev/null
    
    70
    -+++ b/scripts/setup-dev-env.sh
    
    71
    -@@ -0,0 +1,11 @@
    
    72
    -+#!/bin/sh
    
    73
    -+
    
    74
    -+if [ ! -f "Vagrantfile" ]; then
    
    75
    -+    echo "script is supposed to be run from the top folder where"
    
    76
    -+    echo "the Vagrantfile is."
    
    77
    -+    exit 1
    
    78
    -+fi
    
    79
    -+
    
    80
    -+git clone https://github.com/kernelci/kernelci-backend-config.git
    
    81
    -+git clone https://github.com/kernelci/kernelci-build.git
    
    82
    -+git clone https://github.com/kernelci/kernelci-frontend-config.git
    
    83
    -

  • README.md
    1
    -# Kernel CI for the Civil Infrastructure Platform #
    
    1
    +# Board at desk - single dev description  #
    
    2 2
     
    
    3
    -This repository provides vagrant infrastructure that allows users/labs
    
    4
    -to easily set up a kernel CI front- end backend tailored to the needs
    
    5
    -of the civil infrastructure platform (http://www.cip-platform.org).
    
    3
    +Board at desk - single dev is an effort to ease the deployment of KernelCI and LAVAv2 allowing
    
    4
    +a developer with a board connected to its machine test kernels. 
    
    5
    +In order to do so, a VM has been created with all the tools and configurations required. 
    
    6
    +The current technology used to create that VM is Vagrant. 
    
    6 7
     
    
    7
    -KernelCI Virtual Machine Setup & Configuration
    
    8
    +# Interesting links #
    
    8 9
     
    
    9
    -The current setup requires (2) Virtual Machines; one for KernelCI and the other for LAVA v2
    
    10
    +* Board at desk - single dev [feature page](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevfeaturepage)
    
    11
    +* [Download](https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipdownload) Board at desk - single dev.
    
    12
    +* Instructions to [download and set up Board at desk - single dev](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevsetup).
    
    13
    +* [Connect and configure Beaglebone Black](https://wiki.linuxfoundation.org/civilinfrastructureplatform/beagleboneblackboard) to test the kernel on the board.
    
    14
    +* [CIP testing project home page](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting)
    
    10 15
     
    
    11
    -Edit
    
    12
    -Setting up KernelCI VM
    
    16
    +# Contribute to the CIP testing project: #
    
    17
    +* Please read the Testing at [CIP FAQ](https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingfaq) to learn more about this action.
    
    18
    +* Join the technical mailing list ( [cip-dev](https://lists.cip-project.org/mailman/listinfo/cip-dev) ) to follow this effort.
    
    19
    +* Report a [bug](https://gitlab.com/cip-project/testing/boards). 
    
    13 20
     
    14
    -1. Install Vagrant
    
    15
    -
    
    16
    -[user@host ~] $ sudo apt-get install vagrant
    
    17
    -
    
    18
    -2. Install Oracle Virtualbox
    
    19
    -
    
    20
    -[user@host ~] $ sudo apt-get install virtualbox
    
    21
    -
    
    22
    -OR, if you downloaded Virtualbox from the Oracle website
    
    23
    -Note: This assumes you are running Ubuntu Xenial(16.04) 64-bit
    
    24
    -[user@host ~] $ cd Downloads
    
    25
    -[user@host Downloads] $ sudo dpkg -i virtualbox-5.1_5.1.8-111374-Ubuntu-xenial_amd64.deb
    
    26
    -
    
    27
    -3. Get the CIP KernelCI Project
    
    28
    -
    
    29
    -[user@host ~/git] $ git clone https://gitlab.com/cip-project/testing.git
    
    30
    -
    
    31
    -4. Change to the testing directory
    
    32
    -
    
    33
    -[user@host ~/git] $ cd testing
    
    34
    -
    
    35
    -5. Launch the KernelCI Virtual Machine
    
    36
    -
    
    37
    -[user@host ~/git/testing] $ vagrant up
    
    38
    -
    
    39
    -Note: Please ignore any warnings such as “GetPassWarning: Can not control echo on the terminal.” or “Warning: Password input may be echoed.” - These do not affect the operation of the KernelCI VM.
    
    40
    -
    
    41
    -6. Connect to the KernelCI VM through ssh using vagrant
    
    42
    -
    
    43
    -[user@host ~] $ vagrant ssh
    
    44
    -
    
    45
    -Edit
    
    46
    -Get CIP Kernel using git
    
    47
    -
    
    48
    -7. Change to the git-repos directory
    
    49
    -
    
    50
    -vagrant@guest:~$ cd git-repos
    
    51
    -
    
    52
    -8. Clone the Linux Kernel
    
    53
    -
    
    54
    -vagrant@guest:~/git-repos$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
    
    55
    -
    
    56
    -9. Find the branch of the kernel version you want (i.e. 4.4.27)
    
    57
    -
    
    58
    -vagrant@guest:~/git-repos$ cd linux-stable
    
    59
    -
    
    60
    -vagrant@guest:~/git-repos/linux-stable$ git tag -l | grep 4.4.y
    
    61
    -
    
    62
    -10. Create a new branch using that tag.
    
    63
    -
    
    64
    -vagrant@guest:~/git-repos/linux-stable$ git checkout -b cip_v4.4.27 v4.4.27
    
    65
    -
    
    66
    -Edit
    
    67
    -Compile CIP Kernel
    
    68
    -
    
    69
    -11. Set the environment variables
    
    70
    -
    
    71
    -vagrant@guest:~/git-repos/linux-stable$ export TREE_NAME=cip-test
    
    72
    -
    
    73
    -vagrant@guest:~/git-repos/linux-stable$ export ARCH=arm
    
    74
    -
    
    75
    -vagrant@guest:~/git-repos/linux$ export CROSS_COMPILE=arm-linux-gnueabi-
    
    76
    -
    
    77
    -Note: Don't forget the dash (-) at the end of the CROSS_COMPILE line!
    
    78
    -
    
    79
    -12. Execute the build.py command
    
    80
    -
    
    81
    -vagrant@guest:~/git-repos/linux-stable$ ~/kernelci-build/build.py -c tinyconfig -p CIP-KernelCI
    
    82
    -
    
    83
    -13. The Web Server is already running in the background. when you navigate from page to page the logs are written to the screen. To get back to the command line, simply press Enter
    
    84
    -
    
    85
    -14. On your host machine, open a web browser and enter the following in the address box:
    
    86
    -
    
    87
    -http://localhost:5000
    
    88
    -
    
    89
    -15. You will see the KernelCI Website home page from which, you can navigate to the different builds and trees that you've created
    
    90
    - 

  • Join cip-dev@lists.cip-project.org to automatically receive all group messages.