Skip to content
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

Replace default message pattern in notify in Freestyle job #784

Open
marselsultanov opened this issue Jan 24, 2022 · 1 comment
Open

Replace default message pattern in notify in Freestyle job #784

marselsultanov opened this issue Jan 24, 2022 · 1 comment

Comments

@marselsultanov
Copy link

marselsultanov commented Jan 24, 2022

What feature do you want to see added?

At now in Freestyle job, i have only default messages, which will be send to channel for options:
Notify Build Start as [{Job name} - #{Build number} Started by user {user} ({link Open to job})]
Notify Success as [{Job name} - #{Build number} Success after 0.43 sec (link Open to job)]
etc...
And option Custom Message, which adds the message to default pattern in notifications, but not replace him.

What about to add "Default message - Success" ("Default message - Build Aborted", etc) option, with any user pattern, which replace default message? Or maybe other way, as example, when i checkup Notify Build Start/Notify Success/etc, additional windows appear, where i can replace default pattern (pic attached). Maybe some other design, what will be better?

For example, we don't use pipelines, but need Notify Success only with message like this (without default message):
$BUILD_NUMBER successfully deployed

Thanks.

image

Upstream changes

No response

@timja
Copy link
Member

timja commented Jan 24, 2022

Makes sense I think there's a few related issues.

The UI here is a bit out of hand with the advanced properties, would be good if it could be made sane

e.g.
#489 (comment)

(Personally I don't use freestyle builds at all so rely on contributions here, unlikely I will make any changes in this area without someone else picking it up, PRs will be reviewed though)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants