Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
tf-build
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Benedikt Wildenhain
tf-build
Commits
c79a0bfe
Commit
c79a0bfe
authored
2 years ago
by
Austin Anderson
Browse files
Options
Downloads
Patches
Plain Diff
Clarify cookies
parent
aa00983b
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
tf_oss_dashboard/help.md
+11
-7
11 additions, 7 deletions
tf_oss_dashboard/help.md
with
11 additions
and
7 deletions
tf_oss_dashboard/help.md
+
11
−
7
View file @
c79a0bfe
...
@@ -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
)
.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment