Within the comment, we are using a Codefresh native variable CF_BUILD_URL, which will reference your pipeline build and will allow you to search for your pipeline.Īll variables use the Codefresh specific variable notation $ `.JIRA_ISSUE_SOURCE_FIELD: This is the tag that identifies your issue e.g.Then we added these arguments for our specific step: The official Atlassian documentation details how it can be created. JIRA_API_KEY: Note that you will have to create this key.JIRA_USERNAME: This is usually the e-mail that you are logged in with at Jira.JIRA_BASE_URL: This is the url of your organisation e.g.These arguments are required to use the step: Everything up to the arguments is similar to other Codefresh steps. ![]() JiraCommentCreate : title : " Add Jira Comment" type : " jira-issue-manager" stage : " deploy" arguments : JIRA_BASE_URL : ' $' JIRA_USERNAME : ' $' JIRA_API_KEY : ' $' JIRA_ISSUE_SOURCE_FIELD : ' $' ACTION : " comment_create" COMMENT_BODY : " Build number $ finished in Codefresh" In case that you are using the example, the codefresh.yml file is already added. Next, add the following step to your Codefresh pipeline. However, this is not explained in this example. does not matter.) Alternatively, you can also create an issue first with the Jira step. (Note that the project type and who is creating the issue etc. If you do not have one yet, please create an issue. You need an issue in your Jira account that you want to link to your Codefresh pipeline. ![]() You can either use the example provided to try out the Jira integration or follow along with your own application. This documentation is using the following example. ![]() One of those steps is the Jira Issue Manager. The plugin marketplace offers several freestyle steps that can be used in your Codefresh pipeline through steps. Improve this page on GitHub Sending the notification to Jira
0 Comments
Leave a Reply. |