Learn more about these different git repos.
Other Git URLs
A new feature needs tests.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.14.0 owner: somebody => pbrezina
priority: major => minor
1.14.0 should be released no later than Wednesday next week, this ticket should not block the 1.14.0 release.
milestone: SSSD 1.14.0 => SSSD 1.14.1
rhbz: => 0
We need to release 1.14.1 soon, therefore moving to 1.14.2.
milestone: SSSD 1.14.1 => SSSD 1.14.2
owner: pbrezina => pcech
We should transition the 1.14 branch to the maintenance mode, moving to triage to discuss which milestone to fix this ticket at.
milestone: SSSD 1.14.2 => NEEDS_TRIAGE
Temporarily moving to the CI milestone, Dan might be able to help with this ticket during his work on covering sssctl with tests.
milestone: NEEDS_TRIAGE => SSSD Continuous integration
Metadata Update from @jhrozek: - Issue assigned to pcech - Issue set to the milestone: SSSD Continuous integration
Just one update here:
Currently sssctl has a small test coverage as part of our integration tests, just covering the part that does not involve any communication with InfoPipe.
sssctl
Recently InfoPipe tests have been added (please, see: https://pagure.io/SSSD/sssd/issue/2823) and now we can improve our test coverage also writing tests for the part that does communicate with InfoPipe.
We still lack infra to run tests related to subdomains and so on, but that should not block us to extend (as much as we can) tests for sssctl.
Metadata Update from @fidencio: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4091
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.