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
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
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
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.
"""
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
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.
"""
