Hello Sahil, Thanks for your interest in this Jenkins GSoC project.
The best way to get acquainted with the Jenkins ATH is to actually try it out by yourself. There are instructions <https://github.com/jenkinsci/acceptance-test-harness/blob/master/docs/DOCKER.md> to run it inside a docker container. The ATH is used mostly for integration tests of plugins. If you look under https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/, you will see tests for many plugins. For example, the External Workspace Manager plugin tests are here <https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/ExternalWorkspaceManagerPluginTest.java>. The tests are written as a jenkins pipeline script. This is really powerful because using this model, users can write tests for their pipeline build scripts and test them using the ATH. Pipeline library code can be tested the same way. The ATH is one of the better ways to test user build script and user pipeline libraries, because it runs in a live in-memory Jenkins instance. Users can select the jenkins core version and the plugin versions. But it can be slow to run. Another drawback is that tests will download plugins from the update center, which can fail sometimes when the update center is busy or not available. The good thing is that it is actively maintained and has lot of documentation. To get started, I suggest you try to run the tests of a plugin that you know. You could also use the ATH to test your own build script or your own pipeline library. Then you can start thinking on how the ATH performance or usability could be improved, and you can create a project proposal based your observations. Best Regards, Martin d'Anjou On Monday, March 12, 2018 at 4:25:14 PM UTC-4, Sahil Khan wrote: > > Hello > I am Sahil Khan, I am pursuing my 3rd year engineering from Lakshmi Narain > College of Technology and Science Bhopal.I am really passionate about > Linux.I have been a keen evangelist for Dockers. I have been using and > playing around with Dockers for 2 years and also taken various sessions in > my Local City(https://www.null.co.in/profile/5878-sahil-khan).I have also > worked on some Docker-based project one of them is Documented on my Blog > which can be seen here.( http://sahilkhan.me/Dockers-Virtual-Hosting/ ). > I have also contributed and worked on some Open Source Projects on Github ( > https://github.com/docker-scripts/privoxy). > I am interested to work on the project "*Improvements to the Jenkins > Acceptance Test Harness*". > The reason I am Interested in that project is that I contribute to Open > Source projects and once I was contributing to OWASP ZAP Proxy where I > wanted that the Jenkins plugin to be able to use the ZAP docker images.So > this built up my interest in Jenkins and Docker Integrations. > Looking forward to your response. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bc14be3b-d61c-4d4a-aaf4-86badbea8945%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
