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

Feature Request: Improve task title #90

Open
gauntface opened this issue Sep 26, 2022 · 1 comment
Open

Feature Request: Improve task title #90

gauntface opened this issue Sep 26, 2022 · 1 comment

Comments

@gauntface
Copy link

gauntface commented Sep 26, 2022

When I look at the output from gocd the output doesn't carry any meaningful info about what the script ran because the logs are collapsed by default:

Screen Shot 2022-09-26 at 9 55 25 AM

It would be great if the output included the start of the executed script OR the ability to add a name/brief description for the script.

Script example:

[go] Task: Plugin with ID: script-executortook [git clone --branch ...] : 1.472s
[go] Task: Plugin with ID: script-executortook [npm run build]: 0.488s
[go] Task: Plugin with ID: script-executortook [./bin/deploy-releas...]: 0.392s

Another option:

[go] Task: Check API service [script-executor]: 1.472s
[go] Task: Build Project [script-executor]: 0.488s
[go] Task: Deploy Release [script-executor]: 0.392s
@chadlwilson
Copy link
Contributor

chadlwilson commented Sep 27, 2022

Yeah, I agree this is annoying.

I looked at this a long time ago from a plugin author's perspective and IIRC unfortunately I don't think the plugin model for GoCD allows this to be done (either set dynamically by the plugin) or able to be set by the user.

This means it'd require a change to the plugin API first and then opt-in via plugins. (or to consider something like displaying the success message returned by plugins and allowing plugins to opt-in for that behaviour)

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

No branches or pull requests

2 participants