jenkinsci / jenkinsci/postbuild-task-plugin

[JENKINS-71347] Missing headers for post-build actions

Open
#66 0 comments 0 reactions 0 assignees View on GitHub
component:postbuild-task-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
8
Forks
19
Avg merge
38m
Merged PRs (30d)
1

Description

Jenkins 2.403

In our jobs we see some post-build actions that have no headers and no content. I think the fact they don't have content is because there's no settings for those steps, but since they also don't have a header, it looks very strange and it is difficult to know what they are.

This has been for some versions, not sure when it was introduced. The steps shown here are 'Allow broken build claiming', 'Continuous Integration game' and 'Emotional Jenkins'.

---
Originally reported by jjvdgeer, imported from: Missing headers for post-build actions


  • status: Open
  • priority: Minor
  • component(s): postbuild-task-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 20251223-222157

Raw content of original issue

Jenkins 2.403

In our jobs we see some post-build actions that have no headers and no content. I think the fact they don't have content is because there's no settings for those steps, but since they also don't have a header, it looks very strange and it is difficult to know what they are.

This has been for some versions, not sure when it was introduced. The steps shown here are 'Allow broken build claiming', 'Continuous Integration game' and 'Emotional Jenkins'.

  • environment: Windows

1 attachment

- [image-2023-05-26-09-10-31-039.png](https://issues.jenkins.io/secure/attachment/60501/image-2023-05-26-09-10-31-039.png)
> ![image-2023-05-26-09-10-31-039.png](https://issues.jenkins.io/secure/attachment/60501/image-2023-05-26-09-10-31-039.png)

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in Jenkins 2.403 using the post-build actions “Allow broken build claiming,” “Continuous Integration game,” and “Emotional Jenkins.” Inspect how these actions are rendered when they have no settings; done means each action displays an identifying header even when its content is empty.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.