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

As an unprivileged user, I can write to prow on the server side. #246

Closed
Tracked by #295 ...
jgao1025 opened this issue Aug 20, 2024 · 2 comments
Closed
Tracked by #295 ...

As an unprivileged user, I can write to prow on the server side. #246

jgao1025 opened this issue Aug 20, 2024 · 2 comments

Comments

@jgao1025
Copy link

Not sure if this is an expected behaviour, but it looks werid to me?

So I opened this CI build history, and click any error builds. The build log can highlight error lines in color, which is helpful. However, once I clicked the 'Analyzed' button, everything changed, and I can't find a way to revert it. Additionally, this seems to affect the server side as well.

@BenTheElder
Copy link
Member

That's just running an analysis tool, which we're no longer deploying. It was called halogen. kubernetes/test-infra#33353

/close

@k8s-ci-robot
Copy link
Contributor

@BenTheElder: Closing this issue.

In response to this:

That's just running an analysis tool, which we're no longer deploying. It was called halogen. kubernetes/test-infra#33353

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

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

3 participants