Skip to content
Snippets Groups Projects
Commit c79a0bfe authored by Austin Anderson's avatar Austin Anderson
Browse files

Clarify cookies

parent aa00983b
Branches
No related tags found
No related merge requests found
...@@ -2,9 +2,6 @@ This is TensorFlow's open-source build status dashboard. It tracks all ...@@ -2,9 +2,6 @@ This is TensorFlow's open-source build status dashboard. It tracks all
GitHub statuses for the TensorFlow repository that are published to GitHub. GitHub statuses for the TensorFlow repository that are published to GitHub.
The source for the dashboard is on [TensorFlow SIG Build](https://github.com/tensorflow/build/tree/master/tf_oss_dashboard). The source for the dashboard is on [TensorFlow SIG Build](https://github.com/tensorflow/build/tree/master/tf_oss_dashboard).
We use Google Analytics to help figure out how many people are using the
dashboard, but we don't track anything else.
Many of these jobs use Google's internal continuous integration systems, and may Many of these jobs use Google's internal continuous integration systems, and may
not report their results publicly. We're trying to make more of our important not report their results publicly. We're trying to make more of our important
jobs visible to external developers, but security concerns make this a slow jobs visible to external developers, but security concerns make this a slow
...@@ -71,7 +68,14 @@ Here are some tips and notes about the dashboard: ...@@ -71,7 +68,14 @@ Here are some tips and notes about the dashboard:
- Kokoro, Google's CI system that powers most of these jobs, does not report - Kokoro, Google's CI system that powers most of these jobs, does not report
"in progress" jobs, so there is no way to see how many Kokoro jobs are "in progress" jobs, so there is no way to see how many Kokoro jobs are
pending. pending.
- The "kokoro" job is actually multiple jobs that are all called "kokoro." These - The "kokoro" job (at the very bottom) is actually multiple jobs that are all
statuses overlap and are effectively useless, because each dot points to a called "kokoro." These statuses overlap and are effectively useless, because
different job. If your (Google) team owns one of these, you need to change the each dot points to a different job. If your (Google) team owns one of these,
`commit_status_context` github_scm config value to a real name. you need to change the `commit_status_context` github_scm config value to a
real name.
#### Cookies
We use Google Analytics to help figure out how many people are using the
dashboard, and that's it. [Learn more about Cookies
here](https://policies.google.com/technologies/cookies).
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment