Raymond Barbiero

I'm currently working around this by manually triggering jenkins to build. In the above example case, jenkins properly finds the new repository and builds the release candidate. It would be...

https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/blob/54fa2568bf113ab0a2fa3e06eeb90990abfe0252/src/main/java/com/nerdwin15/stash/webhook/RepositoryChangeListener.java seems to indicate that RepositoryRefsChangedEvent is notified for RepositoryPushEvent and i believe RepositoryPushEvent has the RefChange.getType()

+1 would love for this to get some attention

Hey there. Had this same issue. Looks like the problem goes away when I switch the basePingQuery to use https. https://github.com/uber/makisu/blob/2312b399473f4d588e6c797e9b43b6492a7a5b83/lib/registry/security/basicauth.go#L30 I suspect that some registries used to respond using...

@evelynl94 following is my registry config: ``` "docker.mycompany.com": ".*": security: tls: ca: cert: path: /etc/pki/tls/cert.pem basic: username: user password: apikey ``` @evelynl94 i confirm i already have your patch from...

@yiranwang52 correct

I suspect there is something else missing from the code which is not handling the 302 FOUND Location: https://docker.mycompany.com/v2/ redirection ``` < HTTP/1.1 302 Found < Cache-Control: no-cache < Content-length:...

Also, do we want to handle backwards compatibility to older Sentry 7.x?

Also hitting this with nixos-anywhere and disko - commenting out impermanence allows nixos-anywhere to correctly provision. with impermanence enabled, doing a clean nixos-anywhere flake based install to a remote host...

@talyz i tracked down the MVP of the nixos-anywhere provisioning issue - seems to be related to /etc/ssh keys not existing until the first boot... this issue lists similar keys...