[JENKINS-73813] Show a notification when scheduling a build fails

[mawinter69]

When a build is triggered via the UI (either on the job page or via the buildbuttoncolumn in a view) and the crumb is no longer valid, the tooltip was shown that the build was scheduled, although nothing happened.
This change will show a notification when scheduling failed.

See JENKINS-73813.

Testing done

Manual testing

• setup jenkins with users
• create a job without parameters
• go to dashboard
• in a second window logout the user
• click on schedule build -> notification is shown

Proposed changelog entries

• Show a notification when scheduling a build fails

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[mawinter69]

I've chosen to use a notificationBar in case of an error as the hoverNotification doesn't allow to change color.
One idea might be to use a notification also for the success case.

[janfaracik]

I've chosen to use a notificationBar in case of an error as the hoverNotification doesn't allow to change color. One idea might be to use a notification also for the success case.

I think it'd make sense to standardise on one, +1 on the notification.

[janfaracik]

LGTM - thanks :)

[janfaracik]

Suggested change

	Task_schedule_failed=Failed to schedule build for {0}.
	Task_schedule_failed=Failed to schedule build for {0}

For consistency with the 'Build scheduled' content. Any thoughts?

[janfaracik]

Couple linting issues.

[daniel-beck]

This does not address the issue with Build Now from context menus (e.g., breadcrumb bar). Is that deliberate or just an oversight?

[mawinter69]

This does not address the issue with Build Now from context menus (e.g., breadcrumb bar). Is that deliberate or just an oversight?

ah yes, that I overlooked

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!