简体   繁体   English

Jira Jenkins整合| 问题编号

[英]Jira Jenkins Integration | Issue Id

I was trying to get an SVN, Jenkins and Jira integration going. 我试图将SVN,Jenkins和Jira集成在一起。 The aim being to change the status of a ticket/issue to 'Fixed' when it is referred to in an SCM comment. 目的是将SCM注释中提及的票证/问题的状态更改为“已修复”。 The process being orchestrated by Jenkins. 詹金斯(Jenkins)精心策划了这个过程。 The flow details are 流程详细信息是

  • developer puts in the Jira ticket number (MDP-1) on an SVN commit message. 开发人员在SVN提交消息上输入Jira票证编号(MDP-1)。
  • The build is kicked off in JenkinsJenkins (using the Jira plugin) can figure out the Jira ticket referred to it in the SVN commit message. Jenkins启用了构建,Jenkins(使用Jira插件)可以弄清楚SVN提交消息中引用的Jira票证。 It updates the Jira ticket by putting in a Jira comment. 它通过添加Jira注释来更新Jira票证。
  • So far, this is working great! 到目前为止,效果很好!
  • Now, I also want to change the status of the ticket to 'fixed'. 现在,我还想将票证的状态更改为“固定”。 I am trying to use the Jenkins step (Progress jenkins issues by workflow action). 我正在尝试使用Jenkins步骤(通过工作流操作进展jenkins问题)。 I am unable to access the Jira issue ID/ticket number. 我无法访问Jira问题ID /机票号。

I know, under the hood, the Jira plugin has access to this. 我知道,Jira插件可以访问此文件。 Thats why it is able to put in a comment to the Jira ticket in the first case. 这就是为什么它能够在第一种情况下对Jira票证发表评论的原因。 Question is how/what variable do I use to get access to this Jira ticket# in Jenkins 问题是我如何/使用什么变量来访问詹金斯的这张吉拉门票#

在此处输入图片说明

I actually got this working with another Jenkins plugin ( https://wiki.jenkins-ci.org/display/JENKINS/Jira-Ext+Plugin ). 我实际上是通过另一个Jenkins插件( https://wiki.jenkins-ci.org/display/JENKINS/Jira-Ext+Plugin )来工作的。

This captures the Jira issue_id(s) captured in the SCM commit message and exposes them in an environment variable. 这将捕获SCM提交消息中捕获的Jira issue_id,并将其公开到环境变量中。

Just what I was looking for! 正是我想要的!

在此处输入图片说明

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM