-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
CI: Set job names. #59055
CI: Set job names. #59055
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
This changes the job name for a few jobs for consistency, such as |
@rustbot modify labels to I-nominated and T-infra. We should discuss this at the next meeting and if there are no concerns raised r=me on the implementation. Cc @alexcrichton, @pietroalbini, and @kennytm in particular |
I'm leaning towards not changing the CI job names since I don't see the appeal of having a "consistent" As for the PR itself, why some jobs are named |
Having clearer names on the overview of builds, e.g. https://travis-ci.com/rust-lang/rust/builds/103795945, would be useful when doing rollups. For example, what each macOS builder does is really cryptic... @kennytm What's are the drawbacks to this change? |
@Centril I'm +1 with adding the |
@kennytm Oh... I'm fine with whatever on that front. |
I'm sorry, I somehow had it in my mind that "check" and "test" were different. I have reverted the name changes, so every job name should now be the same as before. If you want a preview of what it looks like, here are some samples: |
👍 This is way clearer when looking for a job, and it shouldn't affect anything else. |
@bors: r+ Looks like since the renamings are backed out this is otherwise equivalent, and definitely much nicer to read on the travis side of things |
📌 Commit 8371377 has been approved by |
Removing the nomination since the team already approved the PR. |
CI: Set job names. This should make it easier to identify what each job is doing when looking at the Travis or Appveyor UI. - Set `name` for each job in Travis. - Move `CI_JOB_NAME` to the front in Appveyor so that it appears first in the UI.
CI: Set job names. This should make it easier to identify what each job is doing when looking at the Travis or Appveyor UI. - Set `name` for each job in Travis. - Move `CI_JOB_NAME` to the front in Appveyor so that it appears first in the UI.
☔ The latest upstream changes (presumably #59226) made this pull request unmergeable. Please resolve the merge conflicts. |
This should make it easier to identify what each job is doing when looking at the Travis or Appveyor UI. - Set `name` for each job in Travis. - Move `CI_JOB_NAME` to the front in Appveyor so that it appears first in the UI.
@bors r=alexcrichton |
📌 Commit 2070414 has been approved by |
CI: Set job names. This should make it easier to identify what each job is doing when looking at the Travis or Appveyor UI. - Set `name` for each job in Travis. - Move `CI_JOB_NAME` to the front in Appveyor so that it appears first in the UI.
Rollup of 5 pull requests (all of which changes `src/ci/docker`) Successful merges: - #58986 ([CI] Update binutils for powerpc64 and powerpc64le) - #59038 (Track embedded-book in the toolstate) - #59055 (CI: Set job names.) - #59253 (Calculate Docker cache hash precisely from Dockerfile's dependencies) - #59257 (Update CI configuration for building Redox libraries) Failed merges: r? @ghost
This should make it easier to identify what each job is doing when looking at the Travis or Appveyor UI.
name
for each job in Travis.CI_JOB_NAME
to the front in Appveyor so that it appears first in the UI.