On Thu, Jun 19, 2025 at 10:51 AM Valentin Delaye (jonesbusy) < [email protected]> wrote:
> …when a branch is deleted (for example via UI when it's disabled). > > By checking logs the onDeleted() is just not called. > > Is it expected behavior? > No, I do not think so. I'm not sure about other implementation (But I guess it should be on > branch-api?) > Yes, that is what should be calling `Job.delete` and thus firing notifications. FWIW `artifact-manager-s3` deliberately declines to ever delete artifacts (only permits this via a system property), because - A key advantage of using an external artifact management system is that you can freely configure job/build retention strategies in Jenkins to aggressively reclaim space in `$JENKINS_HOME` without worrying about losing actual data. - Granting the controller permissions to delete things is a security risk from the perspective of auditability. Instead it expects that you have configured some sort of expiry policy at the S3 level. Perhaps the same can be configured in Artifactory. -- 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MjnPVkft-o98vYsV7reYNLA2Hap8E4%2B3OArO3fWX2sw%40mail.gmail.com.
