URL: https://github.com/SSSD/sssd/pull/701 Author: pbrezina Title: #701: ci: add ability to run tests in jenkins Action: opened
PR body: """ Jenkins master polls github for new branches and pull requests. When it discovers new pull request or branch or changes to existing pull request or branch it will allocate a jenkins agent and executes pipeline defined in `./Jenkinsfile` (in SSSD source) on this agent.
The pipeline executes `./contrib/test-suite/run.sh` and archives logs when testing is finished. Script `./contrib/test-suite/run.sh` prepares sssd-test-suite, starts the vagrant machines and copy SSSD source code to the client machine. Then it calls `./contrib/test-suite/run-client.sh` on the client machine which runs continuous integration tests.
### Extending current tests To extend current testing capabilities, modify `./contrib/test-suite/run.sh` and `./contrib/test-suite/run-client.sh` to new requirements. These files can be modified by anyone but are considered untrusted from contributor that is not an administrator of SSSD repository. This means that if a public contributor submits a pull request that changes those files, Jenkins will refuse to run tests.
### Adding additional distribution to test on You need to modify `./Jenkinsfile`. Simply copy, paste and amend existing Fedora 28 stage. This file is also considered untrusted so only administrators can modify it within a pull request.
You also need to extend `sssd-test-suite` and prepare vagrant boxes for this distro. """
To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/701/head:pr701 git checkout pr701
URL: https://github.com/SSSD/sssd/pull/701 Title: #701: ci: add ability to run tests in jenkins
pbrezina commented: """ CI tests are now finished. You can see `sssd-ci` and `sssd-ci/fedora28` labels. The details tab for `sssd-ci` points to our internal jenkins instance that is not publicly accessible (sorry folks). But each distribution that we test on produces logs that we store in amazon cloud and these logs are publicly accesible (click the details button).
Tests can be aborted or re-run in Jenkins. Currently it takes about an hour to run them all. Jenkins polls github every 5 minutes, there is 5000/hour request limit on github api but I think we are safe here. If it will not be sufficient we can increase the timeout. """
See the full comment at https://github.com/SSSD/sssd/pull/701#issuecomment-441364123
URL: https://github.com/SSSD/sssd/pull/701 Title: #701: ci: add ability to run tests in jenkins
pbrezina commented: """ I just realized that Jenkins will fire new testing even if the target branch changes which is nice. So when you push something to master pull request will be re-tested. """
See the full comment at https://github.com/SSSD/sssd/pull/701#issuecomment-441578697
URL: https://github.com/SSSD/sssd/pull/701 Title: #701: ci: add ability to run tests in jenkins
pbrezina commented: """ Yes, you can re-run it from Jenkins: https://sssd-jenkins.duckdns.org/blue/pipelines
Sometimes, it yields 404. I do not know why, but refreshing the page works. """
See the full comment at https://github.com/SSSD/sssd/pull/701#issuecomment-442752331
URL: https://github.com/SSSD/sssd/pull/701 Author: pbrezina Title: #701: ci: add ability to run tests in jenkins Action: synchronized
To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/701/head:pr701 git checkout pr701
URL: https://github.com/SSSD/sssd/pull/701 Title: #701: ci: add ability to run tests in jenkins
pbrezina commented: """ After a discussion with Jakub, we decided to keep `sssd-ci` status and point it to SSSD homepage (for now), later we will prepare a document that will explain this CI. """
See the full comment at https://github.com/SSSD/sssd/pull/701#issuecomment-444455237
URL: https://github.com/SSSD/sssd/pull/701 Title: #701: ci: add ability to run tests in jenkins
pbrezina commented: """ The `sssd-ci` status is important for time when we will test on multiple distros as it will keep the overall status as 'pending' until all test on all distributions are finished. """
See the full comment at https://github.com/SSSD/sssd/pull/701#issuecomment-444455538
URL: https://github.com/SSSD/sssd/pull/701 Title: #701: ci: add ability to run tests in jenkins
jhrozek commented: """ I'll push the patch if the builds succeed here. What we need next is some documentation.. """
See the full comment at https://github.com/SSSD/sssd/pull/701#issuecomment-444465354
URL: https://github.com/SSSD/sssd/pull/701 Title: #701: ci: add ability to run tests in jenkins
Label: +Accepted
URL: https://github.com/SSSD/sssd/pull/701 Title: #701: ci: add ability to run tests in jenkins
jhrozek commented: """ * master: 36255b893a8a55588309a7c5729560c48a30018d """
See the full comment at https://github.com/SSSD/sssd/pull/701#issuecomment-444625732
URL: https://github.com/SSSD/sssd/pull/701 Author: pbrezina Title: #701: ci: add ability to run tests in jenkins Action: closed
To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/701/head:pr701 git checkout pr701
URL: https://github.com/SSSD/sssd/pull/701 Title: #701: ci: add ability to run tests in jenkins
Label: +Pushed
sssd-devel@lists.fedorahosted.org
-
jhrozek -
pbrezina