On Fri, Aug 2, 2019 at 5:27 PM Julian Rüth <julian.ru...@fsfe.org> wrote: > > Hi Erik, > > I think this is not a problem on GitLab anymore. I can restart protected jobs at least, so probably also entire pipelines.
I just noticed that as well. That's good news. I tried to find some upstream issue about it just out of curiosity as to exactly what changed but I couldn't find it. Nevertheless, it seems as long as you have push permissions to a branch you can also retry a pipeline on that branch, which I'd have assumed all along would seem reasonable... > On Friday, August 2, 2019 at 11:14:24 AM UTC+2, E. Madison Bray wrote: >> >> Wow--do I understand you correctly that, if a branch is marked >> "unprotected" , GitLab won't receive the secrets credentials? And yet >> the only way to manually restart a pipeline is to "unprotect" the >> branch (which I did, as you say, in order to restart)? > > -- > You received this message because you are subscribed to the Google Groups "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/b845cefb-67a8-4c01-be7b-ce0e4b3b0227%40googlegroups.com . -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOTD34aaJv5pq%3Df1gXUGQKo-mUU5QVU%3DduGrQ085N3MC0XYZzA%40mail.gmail.com.
