You can read verdicts and start runs without these options. Enabled options work for your account while this page is closed.
:
Details
All pages of the checker use it in every browser you log in from. PR comments and visas
stay in English.
TeamCity login:
⚠ TeamCity no longer accepts the token your options use, so they
are paused: log in again with a fresh token.
Details
Re-run failed suites of my runs — re-runs failures in your Ignite, Python, PHP, Node.js or Extensions runs at the top; ci2 may refuse priority.
Post my runs' verdicts in the PR — the checker's account
posts the verdicts of runs you start in any project as PR comments.
JIRA token: not saved
⚠ JIRA rejected your saved token, so Visa my runs in JIRA went
off: save a new token and switch it on again.
⚠ The checker's state was restored from a backup older than
2 days, which keeps no tokens. Visa my runs in JIRA is paused until you save your JIRA token again.
⚠ The checker does not use the JIRA token your browser kept.
Visas go to JIRA only while Visa my runs in JIRA is on: switch it on and paste the token.
Visa my runs in JIRA — posts the verdicts of runs you start in any project to the IGNITE ticket named in the PR title.
GitHub account: not linked
This checker has no Link GitHub: switch on Add my PR's tests that no
suite runs with a GitHub token for commits, which links your account.
Details
PR commands — /run-all in a PR comment queues RunAll under your ci2 account,
/run-all top queues it at the top, /top moves it there.
GitHub token for commits: not saved
⚠ GitHub rejected your saved token, so the options that commit
with it went off: save a new token and switch them on again.
⚠ The checker's state was restored from a backup older than
2 days, which keeps no tokens. The options that commit are paused until you save your GitHub token for
commits again.
Create a fine-grained token
for your fork of ignite with Contents: Read and write, that expires in 90 days. A PR from another
repository needs a classic token
with public_repo.
These options push commits to your own Ignite PRs.
Details
Fix checkstyle before my commanded runs — needs PR commands; on your own PR, pushes a
commit that fixes what it can before the run starts.
Add my PR's tests that no suite runs — puts each such test class into the suite of the
nearest class in its module, in one commit to your PR.
This checker has no GitHub account (GITHUB_TOKEN), so the
options that write to GitHub are off: its operator can add one.
The server stores these tokens encrypted, and only while an option that needs
them is on. How these work
Your logins:
Your options above are the same in every browser you log in from. Logging out does not
change them.
Journal:
The journal lists each change of your settings and the browser it came from. It also lists
each visa the checker posted or edited with your JIRA token. The browser name comes from the browser's
User-Agent.
See which tests your Apache Ignite PR actually broke, not the ones already failing or
flaky on master. Start a RunAll or re-run just the blockers, right from here.
Log in with your own TeamCity (ci2) access token. There is no
shared account: TeamCity records the runs you start or cancel here as yours. The server also uses your
token to read TeamCity for everyone's PRs, for up to an hour after your last request.
Your browser keeps it in an encrypted session cookie.
The server keeps it in memory for up to an hour after your last request, or until you log out.
The host's swap can write that memory to the disk.
After login, the ⚙ menu has options that work while this page is closed. While one is on, the
server stores the token encrypted, until you turn them all off. Copies stay in server backups
for 2 days. With any option other than PR commands on, the server also
keeps using the token to read from TeamCity, to check open PRs for everyone.
Log out ends your login in this browser. ⚙ lists your logins in other browsers and can end them.
A login left unused for 400 days ends too.
No ci2 account or token yet?
Register an account on ci2, the
TeamCity of Apache Ignite.
Create an access token there: Profile → Access Tokens (“Create a token” above opens it).
The token acts with your account's rights. Reading verdicts needs only view access. “Run” and
“Rerun” need the right to run builds. “Run at top” and “Rerun at top” also need the right to
reorder the build queue. Without it, TeamCity queues them at the end. “Cancel my runs” needs
the right to stop builds and remove them from the queue.
An open-source developer tool for
Apache Ignite contributors (source on
GitHub).
It reads test results from Ignite's CI server, TeamCity (ci2).
Pick a PR on the left, or type its number in the filter.
RunAll:
Verdict to JIRA:to PR:
⚠ Suites that never ran
Broken suites
Fewer tests than master
Tests that did not run cannot fail. Nothing to do if this PR removes tests on purpose. If
not, compare the test list with master and re-run.
BlockersGroup by:
Not confirmed yet: each of these failed its only run on this branch. Re-run
their suites: a second failure confirms a blocker, a pass removes it.
Not confirmed: 1 run
Each failed its only run on this branch. Re-run their suites: a second failure confirms a
blocker, a pass removes it.
Recently started failing
Not blockers yet: there are too few runs of this code to tell a break from a flake. Re-run their
suites: if they keep failing, they become blockers; if they pass, they drop out.
Could not be checked
These tests failed, but TeamCity errors stopped the check. They are not counted as blockers.
The checker tries again by itself.
This PR's tests
These are the tests of an earlier RunAll. The tests of this RunAll are still loading.
Crashed near the end of the run — results stand
None of their failures is blamed on this PR (see Not blamed on this PR), so the results of the
tests they ran stand. Nothing to do.
Not blamed on this PR
Nothing to do for this PR. Re-run only to double-check the flaky ones.