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

More control over bitbucket bit failure popup #244

Open
stuaxo opened this issue Aug 9, 2019 · 3 comments
Open

More control over bitbucket bit failure popup #244

stuaxo opened this issue Aug 9, 2019 · 3 comments

Comments

@stuaxo
Copy link

stuaxo commented Aug 9, 2019

Changing the build title as in #241 is definitely handy.

Is there any way to get control over the dialogue in bitbucket that comes up when you press (!) ?

It would be useful to change the text underneath the title would be handy, especially to include some sort of summary.

Or does this need new features in bitbucket ?

image

@scaytrase
Copy link
Member

scaytrase commented Aug 9, 2019

Yea, currently the text is taken from build description

protected String getBuildDescription(
final Run<?, ?> run,
final StashBuildState state) {
if (run.getDescription() != null
&& run.getDescription().trim().length() > 0) {
return run.getDescription();
} else {
switch (state) {
case INPROGRESS:
return "building on Jenkins @ "
+ getRootUrl();
default:
return "built by Jenkins @ "
+ getRootUrl();
}
}
}

So you can just set build description with other tools to make it more useful

@scaytrase
Copy link
Member

For the history and the future. We need to have a way to manipulate both description (for custom use cases) and configurable predefined messages (for classic UI), have custom case preferred over messages

@Subhajit009iitr
Copy link

Hey, I am interested in looking into this issue! Can you please explain once what kind of message needs to be shown? Is it the same type as is in #241 ?

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

3 participants