jenkinsci / jenkinsci/postbuild-task-plugin

[JENKINS-23952] Postbuild task plugin doesn't work with Flexible Publish plugin

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

Description

Steps to Reproduce:

1. Create a Post-build Action of type Flexible publish



  • Run? Always

  • Action Post build task

  • Script: echo "I am script A"

    So far so good. This works just fine. Now add a second one:

    2. Create a Post-build Action of type Flexible publish

  • Run? Always

  • Action Post build task

  • Script: echo "I am script B"

Save the project and run.

Notice it runs Script A twice and Script B twice.

Also notice that if you click "configure" on this project, things have gone bonkers (that's a technical term):

There are 2 conditional steps, but they both have 2 script executions for the same condition.

It gets more complicated if you have different conditions to run these scripts: It merges them into one condition, making it pretty much useless.

---
Originally reported by grayaii, imported from: Postbuild task plugin doesn't work with Flexible Publish plugin


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

Raw content of original issue

Steps to Reproduce:
1. Create a Post-build Action of type Flexible publish



  • Run? Always

  • Action Post build task

  • Script: echo "I am script A"
    So far so good. This works just fine. Now add a second one:
    2. Create a Post-build Action of type Flexible publish

  • Run? Always

  • Action Post build task

  • Script: echo "I am script B"

Save the project and run.
Notice it runs Script A twice and Script B twice.
Also notice that if you click "configure" on this project, things have gone bonkers (that's a technical term):
There are 2 conditional steps, but they both have 2 script executions for the same condition.

It gets more complicated if you have different conditions to run these scripts: It merges them into one condition, making it pretty much useless.

2 attachments

- [bad.xml](https://issues.jenkins.io/secure/attachment/26430/bad.xml)
- [good.xml](https://issues.jenkins.io/secure/attachment/26431/good.xml)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.