Cannot create new release due to Jira integration error

paraic.oceallaigh · 14 December 2021 05:24

Hi David,
Thanks for reaching out.

We have a GitHub with a fix for this issue:

github.com/OctopusDeploy/Issues

Azure Devops Fatal Error when running task: OctopusCreateRelease@4 with a commit message referencing a Jira Work Item that doesn't exist

opened 11:55PM - 30 Nov 21 UTC

closed 12:09AM - 01 Dec 21 UTC

long-sean

kind/bug team/integrations

### Team - [X] I've assigned a team label to this issue ### Severity On…e Report ### Version Octopus Deploy 2021.3.8733 ADO/Octopus Marketplace Extension 4.2.492 ### Latest Version I could reproduce the problem in the latest build ### What happened? When using an Azure DevOps pipeline to create a Project Release if the 1. Release contains a Commit Message 2. the Octopus Instance has Jira Integration Enabled and Jira Release Notes Configured correctly If the Commit Message contains a WorkItem.Id that doesn't exist (JIR-317982) the Devops Pipeline will fail with the following message: Creating release... There was a problem with your request. ``` - Jira: Failed to retrieve Jira issues 'JIR-63124' from https://dfalvo.atlassian.net. Response Code: BadRequest (Reason: Bad Request) Error from Octopus Server (HTTP 400 BadRequest) Exit code: -7 ##[debug]Exit code 249 received from tool '/usr/bin/dotnet' ##[debug]STDIO streams have closed for tool '/usr/bin/dotnet' ##[error]Error: The process '/usr/bin/dotnet' failed with exit code 249 ``` If this commit message is parsed during any future deployments the Pipeline will continue to fail. This also means the Octopus Release doesn't proceed. ### Reproduction 1. Create a Project that deploys a package 2. Setup Jira Integration 3. Setup Jira Release Notes (Release Notes Template whether configured or not, does not affect the outcome) 4. Create an Azure Devops Pipeline to perform a release of the Project. The Repo can be an Azure DevOps repo (or GitHub) ``` - task: OctopusCreateRelease@4 inputs: OctoConnectedServiceName: 'Octopus DFCloud' Space: 'Spaces-1' ProjectName: 'Projects-285' ReleaseNumber: '$(Build.BuildNumber)' DeployToEnvironment: 'Development' ``` 5. Commit a change, and provide a commit message with the start of the commit message in the format "XXXX-XX". e.g JIR-21354, JIRA-523662, 2021-11 6. Run the pipeline ### Error and Stacktrace ```shell Azure Devops Error: Found project: Simply Deploy a Package (Projects-285) Automatically selecting the best channel for this release... Building a release plan for Channel 'Default'... Finding deployment process... Finding release template... The package version for some steps was not specified. Going to try and resolve those automatically... Finding latest package for step: Deploy a Package Selected 'MyDotNetCoreAppGITExample.Development' version '20211126.10' for 'Deploy a Package' Selected the release plan for Channel 'Default' - it is a perfect match Using version number provided on command-line: 20211126.10 Release plan for Simply Deploy a Package 20211126.10 Channel: 'Default' (this is the default channel) # Name Version Source Version rules --- ------------------ ------------- ------------------ ------------------- 1 Deploy a Package 20211126.10 Latest available Allow any version Creating release... There was a problem with your request. - Jira: Failed to retrieve Jira issues '2021-11' from https://dfalvo.atlassian.net. Response Code: BadRequest (Reason: Bad Request) Error from Octopus Server (HTTP 400 BadRequest) Exit code: -7 ##[debug]Exit code 249 received from tool '/usr/bin/dotnet' ##[debug]STDIO streams have closed for tool '/usr/bin/dotnet' ##[error]Error: The process '/usr/bin/dotnet' failed with exit code 249 ##[debug]Processed: ##vso[task.issue type=error;]Error: The process '/usr/bin/dotnet' failed with exit code 249 ##[debug]task result: Failed ##[error]Failed to deploy release The process '/usr/bin/dotnet' failed with exit code 249 ##[debug]Processed: ##vso[task.issue type=error;]Failed to deploy release The process '/usr/bin/dotnet' failed with exit code 249 ##[debug]Processed: ##vso[task.complete result=Failed;]Failed to deploy release The process '/usr/bin/dotnet' failed with exit code 249 Finishing: OctopusCreateRelease ``` ### More Information Original Ticket: https://help.octopus.com/t/jira-integration-prevents-release-creation-if-it-fails/27402/3 ### Workaround Disable Jira Integration in Octopus Deploy Do a release. Enable Jira Integration again.

This will likely require an upgrade for you as the workaround is to disable JIRA integration which is not a great option.

Let me know if this fixes it for you.

Kind Regards,
Paraic

david.keaveny · 14 December 2021 10:50

Hi Paraic,

Thanks for your quick response. The problem is that the ticket referenced (SC-76) does exist. Are there permissions involved in the Jira <-> Octopus integration, and can we check those?

dane.falvo · 14 December 2021 13:50

Hi David,

I’m sorry to see that you are facing this issue. It’s good to see that the Jira Issue is being recognised in the Octopus logs and there is an attempt to match the issue up with Jira. This rules out a lot of potential problems.

Can I clarify what version of Octopus you are using?
Can you also clarify what version of the Octopus Deploy Marketplace extension you have installed on Jira?

Have you upgraded the marketplace app or reconfigured anything on either end (Jira or Octopus)? Sometimes, when there are issues with Jira integration, we get the user to uninstall the Marketplace app, remove the details from Octopus and then reconfigure the connection. This has worked a handful of times to fix issues when nothing seems to be incorrectly configured.

I can also see that the build information is being correctly pushed to Octopus.

Does the “Work Items” field populate with the correct link?

Also, is your Environment set with a Jira Environment type? You can check this via “Infrastructure” → “Environments” then select Edit from the burger menu next to the environment name.

There are a handful of other troubleshooting steps available here:

Please, let me know if this gets you any further, then we can dig a bit deeper.

Regards,

david.keaveny · 14 December 2021 23:00

We are on Octopus Cloud - Version 2021.3 (Build 8275); the Octopus plugin is 1.0.5-AC.

Build information is not showing the Work Items. Here’s what the build server logs show (this is using the Octopus Deploy pipe for BitBucket):

Digest: sha256:e23751377a0c7a8d9b321ad2e77e7822bb6c086fc8c2747bd9b7ded95c9b2994
Status: Downloaded newer image for octopipes/octopus-cli-run:0.26.0
INFO: Running: octo build-information --package-id=stp-api --server=$OCTOPUS_SERVER --apiKey=$OCTOPUS_APIKEY --file=octopus.buildinfo --space=Aussiepay --version=0.0.1.232 
Octopus CLI, version 7.4.3467
Detected automation environment: "BitBucket"
Found space: Aussiepay (Spaces-2)
Space name specified, process is now running in the context of space: Aussiepay
Handshaking with Octopus Server: $OCTOPUS_SERVER
Handshake successful. Octopus version: 2021.3.8275; API version: 3.0.0
Authenticated as: David Keaveny <david.keaveny@readytech.io> 
Pushing build information for package "stp-api" version "0.0.1.232"...
Push successful

Meanwhile, if I look at that release in Octopus and check the build information, then I can see the following:

Create AWS ECS task definition:stp-api(stp-api) version 0.0.1.232
Published: Tuesday, 14 December 2021 4:04 AM +00:00
Platform: linux amd64

Build Information

Build Environment	BitBucket
Build	232
Commits	819edbc Merged in feature/SC-76-fix-authentication-bug (pull request #13)
Work Items

Environments are correctly mapped (e.g. in Octopus, Development environment is mapped to development environment in Jira), and I can see deployments in Jira, and in Jira, those deployments are linked back to their tickets.

I have other projects which are successfully sending through Work Items. They are all using the same Octopus and Jira instances, but most of them are building with on-premise TeamCity and using its build information plugin, whereas this one is using Atlassian Bitbucket Pipelines - maybe that is a factor? And they are using different Jira projects (which is why I asked about permissions). That suggests at least that the Octopus Deploy plugin for Jira is working.

paraic.oceallaigh · 15 December 2021 01:58

Hi David,
Thanks for the additional info.

As you are a Cloud user the fix (Azure DevOps at least) has already been applied so there may be specific Bitbucket issues that were not addressed.

It does look like the key factor is the Bitbucket Pipeline. Has the build info ever appeared in JIRA when using the Bitbucket pipeline create-release? I am trying to establish if its a new issue or the integration is just not working.
I see one of our team has commented on the GH issue and I can note this ticket there. I will pass this along to our Dev team in the meantime to take another look.

Kind Regards,
Paraic

david.keaveny · 15 December 2021 03:17

Hi Paraic,

No, this is our first time using BitBucket Pipelines to integrate with Octopus Deploy and Jira. I am aware that the Octopus pipe is in beta at the moment, so it could well be a bug in the code there. I can try switching to use the more generic Octopus CLI tool and see if that makes a difference, or we can see if we can drive the bug out of the code through further investigations.

paraic.oceallaigh · 15 December 2021 04:52

Hi David,
Even though this issue has been fixed in the Cloud your instance is on an older version than the one the fix came in.
I am asking our Cloud team if you can be upgraded sooner rather than later to get the fix applied for your version. This can be done at the next available maintenance window.

Update to follow.

Kind regards,
Paraic

paraic.oceallaigh · 15 December 2021 04:56

Hi David,
I have confirmed that your instance can be upgraded to the latest version with that fix applied.

I will schedule this in for you tonight during your maintenance window and it should be ready for you by tomorrow.

If you can get a chance to test it and let us know that would be great.

Kind Regards,
Paraic

david.keaveny · 15 December 2021 04:56

Hi Paraic,

Thanks for your response; I look forward to your next update.

Regards,
David

dane.falvo · 15 December 2021 13:25

Hi David,

I wanted to quickly let you know that your instance has been successfully upgraded.
Please, let us know if your issue is fixed now.

Happy Deployments,

david.keaveny · 15 December 2021 23:29

Hi Dane,

Thank you for organising the update of our instance, I can see we are now running on build 9562.

The good news is that I’m not getting an error when I include a work item ID in my commit messages; the bad news is that there are no work items coming through in the build information step. I don’t know if you want to close this ticket, and open a new one, or just keep going here?

Regards,
David

John_Simons · 16 December 2021 01:52

Hi David,

This is John, I had a look at our logs and can see that some workitems cannot be found
examples

Makes me wonder if the account configured has access to see these workitems?
Has this functionality worked before the update?

Regards
John

david.keaveny · 16 December 2021 02:29

Hi John,

I’ve had a look at the identifier issues in Jira; in some cases, the ticket has been moved from one project to another and has therefore acquired a new key. For instance, EP-7302 (the first one you highlight) is now known in Jira as AI-588, so that sounds like it might be more of a Jira issue than an Octopus Deploy one. Some of the others are blatant typos - for instance, DES-92 should actually be DE-92. Others just don’t exist at all - maybe issues that were actually deleted. The accout definitely has access to all the tickets.

The issues I am particularly interested in are in the SC project - this is the only project that uses BitBucket Pipelines to build and deploy; all the others use our on-premise TeamCity server to build and deploy. I create a build this morning to verify that the new Octopus instance would indeed fix the issue and referenced SC-46 in the commit message (and that shows in the build information commit section) but doesn’t appear in the work item section. Would you be able to check for SC-46?

Are those logs visible anywhere for users like myself, or are they an internal-only feature for Octopus support?

Regards,
David

John_Simons · 16 December 2021 03:42

Hi David,

That is good to know that some issues have been renamed or mistyped.
Regarding SC-46, I can’t see anything in the logs regarding this one!
Do you give me authorisation to login to your instance and have a look? What is the package name?

Also, I noticed you are local, we can chat in our Slack community if you want? Join Octopus Deploy Community on Slack | Slack, just send me a dm.

rjunruh · 10 January 2022 23:54

Any update on this patch showing up on the downloads page? We have this issue but aren’t using cloud.

paraic.oceallaigh · 11 January 2022 00:46

Hi @rjunruh
Thanks for letting us know.
I am reaching out to our Dev team to see if the Server version is ready to be released, or maybe a version we can provide for you with the fix applied.

I’ll get back to you as soon as I get confirmation.

Kind Regards,
Paraic

paraic.oceallaigh · 11 January 2022 02:14

Hi @rjunruh
Our Dev team say the next drop of Octopus Server will be around 2 weeks from now - most likely version 2021.3.9562.

We could provide a custom build but to be honest that might be more trouble than its worth as it may vary enough from the next release so as to potentially cause upgrade issues. I would recommend waiting for the next official release and I’m pretty sure it should be out before the end of January at the latest.

Thanks for your patience on this one.

Kind Regards,
Paraic

paraic.oceallaigh · 14 January 2022 03:11

Hi @rjunruh
Our Dev team have completed testing on a version which may resolve your issue and have given me a download link for this version:
https://download.octopusdeploy.com/octopus/Octopus.2021.3.10526-x64.msi

This is not GA yet but if you don’t wish to wait 2-3 more weeks you can try this version and let us know if it resolves the issue for you.

Kind Regards,
Paraic

rjunruh · 19 January 2022 20:07

This worked, thanks!

system · 19 February 2022 22:00

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.