Skip to content

Accept "try-jobs:" as alternative to "try-job:" #860

Closed

Description

@RalfJung

As part of the bors command, both try job=foo and try jobs=foo work. However, I just found out the hard way that when specifying the jobs via the PR description, only "try-job:" works, not "try-jobs:".

Would be great to make this consistent and reduce some potential confusion. :)

Activity

  1. changed the title [-]Accept "try-jobs:" as alternatie to "try-job:"[/-] [+]Accept "try-jobs:" as alternative to "try-job:"[/+] on Sep 26, 2026
  2. Kobzol commented on Sep 27, 2026

    @Kobzol
    Member

    I only added try job= because people were writing it by accident instead of try jobs= 😆 I guess what you describe is the same situation though..

  3. RalfJung commented on Sep 27, 2026

    @RalfJung
    MemberAuthor
  4. Kobzol commented on Sep 27, 2026

    @Kobzol
    Member

    As far as I'm concerned, the two things aren't actually related that much.

    try-job: is a special marker syntax interpreted by Rust's CI, and existed before bors was even used as the merge bot for rust-lang/rust. This syntax does not accept commas, multiple markers have to be entered on separate lines.

    Originally, it was used like this:

    try-job: job-1
    try-job: job-2
    

    etc. But later we also added glob support, so you can now also say things like try-job: test-*, which makes using multiple markers a bit less common.

    @bors try jobs= is the syntax of a bors command that will just generate the try-job: markers for you. Most people use the bors command nowadays, without modifying the PR description (though it can be useful if you do a lot of try builds and don't want to type the jobs repeatedly).

    But those are two separate systems, where bors conforms to the syntax expected by the rust-lang/rust CI. Of course that doesn't mean that we can't change the CI markers to also accept try-jobs:.

  5. RalfJung commented on Sep 27, 2026

    @RalfJung
    MemberAuthor

    I understand they are implemented entirely separately, but as a user they feel like two entry points to the same thing.

  6. Kobzol commented on Sep 28, 2026

    @Kobzol
    Member

    rust-lang/rust#163433 + #863 implements this.

  7. added 2 commits that reference this issue on Sep 28, 2026
  8. added a commit that references this issue on Sep 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions