Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21345

Filter action list on matrix jobs

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not A Defect
    • flexible-publish-plugin
    • None
    • Jenkins LTS 1.532.1
      Flexible publisher plugin 0.12
      Jenkins Subversion Tagging Plugin 1.16

    Description

      For a matrix job you can add flexible publisher as post build action. Afeter that you can choose the wanted action of the flexible publisher.

      Unfortunately all existing post build actions are listed there, including those which don't support matrix jobs, e.g. "Perform subversion tagging on successful build" of the Subversion tagging plugin.

      Improvement: For matrix jobs filter out actions in flexible publishers action list, that don't support matrix builds.

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-14494 Need to be able to use Flexible Publish in matrix job post-build actions

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-9683 Support matrix projects

          • Major - Major loss of function.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            ikedam ikedam added a comment -

            I think you misunderstand the problem.

            A publisher in a matrix project can work in following two phases:

            • For each child build, after finishing builders of each child.
            • For the parent build, after finishing all child builds.

            The latter phase is supported by publishers designed for matrix projects.
            Publishers that does not designed for matrix projects works only in former phases.

            So, even publishers does not support matrix projects, you can use them in matrix projects and combine with Flexible Publisher.
            It is not necessary to filter them out.

            ikedam ikedam added a comment - I think you misunderstand the problem. A publisher in a matrix project can work in following two phases: For each child build, after finishing builders of each child. For the parent build, after finishing all child builds. The latter phase is supported by publishers designed for matrix projects. Publishers that does not designed for matrix projects works only in former phases. So, even publishers does not support matrix projects, you can use them in matrix projects and combine with Flexible Publisher. It is not necessary to filter them out.
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: ikedam
            Path:
            src/main/java/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisher.java
            src/main/resources/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher/help-configuredAggregation.html
            http://jenkins-ci.org/commit/flexible-publish-plugin/7c0d2dfc1cb9f707a24cf6ac202ee2cbc11981b0
            Log:
            JENKINS-21345 improved explanation for the aggregation condition.

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: ikedam Path: src/main/java/org/jenkins_ci/plugins/flexible_publish/FlexiblePublisher.java src/main/resources/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher/help-configuredAggregation.html http://jenkins-ci.org/commit/flexible-publish-plugin/7c0d2dfc1cb9f707a24cf6ac202ee2cbc11981b0 Log: JENKINS-21345 improved explanation for the aggregation condition.
            ikedam ikedam added a comment -

            As commented before, there is no need to filter publishers without multi-configuration supports.
            And there is no way to dynamically switch display of "Condition for Aggregation" depending on which publisher is selected.

            I improved some messages in helps, and display warnings at build time if "Condition for Aggregation" is configured for publishers without multi-configuration supports.

            ikedam ikedam added a comment - As commented before, there is no need to filter publishers without multi-configuration supports. And there is no way to dynamically switch display of "Condition for Aggregation" depending on which publisher is selected. I improved some messages in helps, and display warnings at build time if "Condition for Aggregation" is configured for publishers without multi-configuration supports.
            ikedam ikedam added a comment -

            Fixed in 0.13.
            It will be available in a day.
            Please try that.

            ikedam ikedam added a comment - Fixed in 0.13. It will be available in a day. Please try that.

            People

              ikedam ikedam
              wh WH
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: