infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17517) Install and configure the Jenkins JIRA Trigger Plugin
Date Sat, 19 Jan 2019 00:20:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-17517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746846#comment-16746846
] 

Allen Wittenauer commented on INFRA-17517:
------------------------------------------

They need data that I'm not sure I have access to provide.  They seem to think that filtering
on attachments should work, but need to see the JSON coming from JIRA to the webhook.

> Install and configure the Jenkins JIRA Trigger Plugin
> -----------------------------------------------------
>
>                 Key: INFRA-17517
>                 URL: https://issues.apache.org/jira/browse/INFRA-17517
>             Project: Infrastructure
>          Issue Type: New Feature
>          Components: Jenkins, JIRA
>            Reporter: Allen Wittenauer
>            Assignee: Gavin
>            Priority: Major
>
> Jenkins doesn't (easily) support freestyle job -> pipeline job triggers.  As a result,
precommit-admin can't really trigger pipeline jobs and many people are starting to use those
on the ASF Jenkins instance.  About 3 years ago, it would appear that the Jenkins community
caught up to where the ASF was almost 11 years ago and released a plug-in that has similar
functionality to what precommit-admin does: JIRA Trigger Plugin.  So rather than rework precommit-admin
to support this use case, it's easier to just switch to the plugin.
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message