Pre-hack Prepare Your Development Environment


In order to save some time on Monday, we decided to add your public keys to our Git server and make a little test which runs on our Jenkins server (CI server).
To make sure that your development environment is fully functional before the session we made this "anchor_test.sh" file. The file is quite simple:
#!/bin/bash
exit 1
The "exit 1" causes the test to fail. What we want you to do is to clone your team repository edit the file to:
#!/bin/bash
exit 0
And push it to server and your team repository in Jenkins should show pass! That way we make sure that your key has worked and you are good to go!
 

Teams setup

Team name Git repository to clone Member(s) Company/Companies
Group 1  git clone git@developer.lindholmen.se:prehack-group1.git Rickard Nilsson
Golnaz Sabet Nejad
Golnaz Makhtoumi
HIQ(SICS)
Group 2 git clone git@developer.lindholmen.se:prehack-group2.git Johan Wessfeldt
Andreas Johansson
Combitech
Consat
Group 3 git clone git@developer.lindholmen.se:prehack-group3.git Johan Breisel Prevas
Group 4 git clone git@developer.lindholmen.se:prehack-group4.git Rickard Lundahl
Anders Widén
Cybercom Groups
Group 5 git clone git@developer.lindholmen.se:prehack-group5.git Magnus Grundberg
Jonas Thorsell
Volvo
Group 6 git clone git@developer.lindholmen.se:prehack-group6.git Håkan Johansson
Johan Olsson
Delphi
Group 7 git clone git@developer.lindholmen.se:prehack-group7.git Fredrik Malmin
Christoffer Hindelid
Emil Knabe
Semcon
Group 8 git clone git@developer.lindholmen.se:prehack-group8.git Oskar Hagberg
Nils Heuman
Interaktionsbyrån
Group 9 git clone git@developer.lindholmen.se:prehack-group9.git Håkan Burden GU
Group 10 git clone git@developer.lindholmen.se:prehack-group10.git    
Once you managed to get your repository test pass on Jenkins you may also want to go ahead and clone our other repositories. Please take a look at Software_components page for details about each component.