Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release branches on ci.android.com not visible to non-googlers #1715

Closed
DanAlbert opened this issue May 11, 2022 · 7 comments
Closed

release branches on ci.android.com not visible to non-googlers #1715

DanAlbert opened this issue May 11, 2022 · 7 comments

Comments

@DanAlbert
Copy link
Member

The new link shows and empty list. I cannot see asop-ndk-release branch.

Screenshot 2022-05-11 at 21 22 45

Originally posted by @orifmilod in #1671 (comment)

@orifmilod
Copy link

I can see aosp-master-ndk branch although not the build #8568313 - maybe any other build number from there would solve our problem?

@DanAlbert
Copy link
Member Author

DanAlbert commented May 11, 2022

I'm not sure when this broke, but I'll start chasing it with the build team. We'd asked for all our release branches to always be publicly visible and I believe that was working until recently.

@orifmilod
Copy link

Got it! Thanks for the swift responses.

@DanAlbert
Copy link
Member Author

http://b/140114921 is the internal bug for this (I know you can't see it, that's just so I can find it again later). It seems like there isn't any actual wildcard pattern for our release branches which is what I'd wanted, they'd just added all the branches that existed at the time we made the request. We mostly only end up sharing links to the master branch, so that could be an explanation of why we haven't noticed the problem sooner...

@orifmilod
Copy link

@DanAlbert Any updates on this one?

@DanAlbert
Copy link
Member Author

No. The person I need to talk to was OOO.

@DanAlbert
Copy link
Member Author

DanAlbert commented Oct 19, 2022

r25 is visible now. We will probably forget to do this for future release branches, and unfortunately the tool does not support wildcards, so there's no way for me to fix this permanently. If we forget again, file a bug and I'll go bother people.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants