Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CAMP Installation stages ? #4

Open
fermenreq opened this issue Sep 25, 2019 · 4 comments
Open

CAMP Installation stages ? #4

fermenreq opened this issue Sep 25, 2019 · 4 comments
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@fermenreq
Copy link

fermenreq commented Sep 25, 2019

Hi @danzone ,

As I see in pipeline stages, you dont use an stage previously in order to install CAMP. Should it be previously installed on your host? If yes, which of the three installation methods offered by the developer do you use to install CAMP?

Best,
Fernando

@fermenreq fermenreq added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Sep 25, 2019
@danzone
Copy link
Contributor

danzone commented Sep 25, 2019

Dear @fermenreq, yes, CAMP should be previously installed in the host. I'm preparing documentation to cover this topic from zero to CAMP. This documentation will be available in this repository soon (for sure before Madrid meeting, but I'm planning to have it completed by the first half of next week)

@jesus-gorronogoitia
Copy link

Hi @danzone
As we cannot wait for you to prepare us a detailed documentation, don't you mind to share with us the approach you followed?
IMHO, I think we can:
1- create a Docker container for CAMP from the DockerHub image that we can use to execute camp commands
2- create scripts that invoke the Docker instance of CAMP from the Jenkins pipeline to execute concrete camp commands

What is, grosso modo, the approach you have followed to install CAMP and use it?
Grazie mille
Yosu

@fermenreq
Copy link
Author

fermenreq commented Sep 25, 2019

hi @danzone,

As @jesus-gorronogoitia said. I created a Jenkins pipeline job according Atos use case. I think is the best way to launch and integrate CAMP

node("master") {
stage('Pull Sut CityGo'){
git (credentialsId: 'git-credentials', url: 'https://gitlab.atosresearch.eu/ari/stamp_docker_citygoApp', branch: 'master')
}
stage('Install CAMP'){
sh 'docker pull fchauvel/camp:latest '
}
stage('Run CAMP'){
sh 'docker run -d --name camp -v /var/run/docker.sock:/var/run/docker.sock -v /var/jenkins_home/workspace/citygo_camp/stamp_docker_citygoApp:/stamp_docker_citygoApp/ -t fchauvel/camp:latest '
}
stage('CAMP generate'){
sh 'docker exec -i camp sh -c camp generate -d ./stamp_docker_citygoApp/camp.yml --all'
}
stage('CAMP realize'){
sh 'docker exec -i camp sh -c camp realize -d ./stamp_docker_citygoApp/camp.yml --all'
}
stage('CAMP execute'){
sh 'docker exec -i camp sh -c camp execute -d ./stamp_docker_citygoApp/camp.yml --all"'
}
stage('Stop CAMP'){
sh 'sudo docker stop camp && sudo docker rm camp'
}
}

@danzone
Copy link
Contributor

danzone commented Sep 25, 2019

Hi @fermenreq and @jesus-gorronogoitia, I would rather prefer to install CAMP, in order to use containers just to run test configurations and tests against them. Currently the method I followed is simply cloning the CAMP repo, and install it with pip (pip install . . Actually I used also the -e option - development mode - but it isn't necessary). The prerequisite is to have Python 3,Python 2 is no more supported (we, Franck and I, realized this during JMeter integration, and I will update documentation accordingly). Anyway, if you prefer to run CAMP as a Docker image and you aren't facing issues related to launch containers inside a container, I think it is a good choice. My choice was simply to reduce entropy during the development of JMeter support :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants