My project key is invalid on jenkins even though the project key is correct.

[Divyani]

when I am trying to integrate JiraTestResultReporter module in Jenkins , It says the project key is invalid even though it is correct.

[Dario B · Accepted solution]

Hello @Divyani ,

Welcome to the Atlassian Community!

Usually if a project exist but you cannot see it something went wrong with the authentication. 

Can you kindly let us know which steps are you following to integrate Jira with Jenkins and where (which step) do you get the error? 

Cheers,
Dario

[lokeshkambhoji]

Hi @Dario B 

I've followed the instructions from below link for integrating Jenkins with JIRA server & getting the error as "Invalid Project key" from the 'post build actions'-> Additional test report features-> JiraTestResultReporter.

I've provided the valid project key only but still it's giving the error. 

Link: https://github.com/jenkinsci/JiraTestResultReporter-plugin

Any suggestions will be really helpful. Thank you!

[Dario B]

Hello @lokeshkambhoji , 

I am not sure if you are working with @Divyani  on the same project or if this is a different scenario. Can you please clarify?

Also, is this for Jira Server or Cloud?

I am asking because, as already mentioned, if the project key is not found even if it actually exists in Jira there are chances that the authentication failed. And, looking at the instructions you are following, I can see that they authenticate using username and password but this is not going to work in Jira Cloud.

Indeed, as you can read in below link, basic authentication with username and password has been deprecated long time ago in Jira Cloud and you should use basic authentication with email address and API Tonken instead.

For details please see:

• Deprecation of basic authentication with passwords for Jira and Confluence APIs
• Deprecation notice - Basic authentication with passwords and cookie-based authentication

Cheers,
Dario

[lokeshkambhoji]

Hi @Dario B ,

Thank you for your quick response, I am not working with Divyani.

I am using the JIRA cloud only and followed the below steps for authentication.

1. Provided the JIRA URL, username(provided the email address) & password(provided the API token generated from https://id.atlassian.com/manage/api-tokens)

2. Validated the settings from the configure systems in Jenkins and it's showing as 'jira'.

But from the post build actions i am getting the error message as 'Invalid project key'.please let me know how to get resolve this error.

[Dario B]

@Divyani  and @lokeshkambhoji ,

After a bit of research I have found that this is a known issue that has already been fixed and waiting for release:

• https://issues.jenkins-ci.org/browse/JENKINS-61171 (JiraTestReporterPlugin no longer works)
  

  The plugin stopped working in jobs over the weekend and will no longer validate the Jira Project Key and allow further config and use.

As you can see:

• The status is:
  

  FIXED BUT UNRELEASED This change has been implemented and merged, but not yet released. 

• The root-cause is the change discussed in below thread:
  • https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944

Please follow the Jenkins bug ticket and set yourself as a watcher so that you will be updated as soon as the fix is released.

Cheers,
Dario

[lokeshkambhoji]

Hi @Dario B ,

Thank you for the update, it really helped me a lot.

Have a good weekend!

[Dario B]

You are very welcome @lokeshkambhoji :) 

I am accepting my answer so that this thread will be marked as resolved. 

Have a nice weekend too!

[lokeshkambhoji]

@Dario B  Just a quick question related to the Jenkins bug ticket - https://issues.jenkins-ci.org/browse/JENKINS-61171

In the above ticket 'JiraTestResultReporter' plugin version is mentioned as 2.0.7. I've downgraded the plugin version from 2.0.7 to 2.0.6 in Jenkins, still i am getting the same error.

Also downgraded the Jenkins version to 2.190.1.

Any suggestions will be really helpful! Thank you.

[Dario B]

@lokeshkambhoji 

As already mentioned, that plugin is still using usernames that have been deprecated since 2018 (due to GDPR) and that we finally switched off completely this February:

• https://confluence.atlassian.com/cloud/blog/2018/06/say-goodbye-to-usernames-in-atlassian-cloud
• https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/
• https://community.developer.atlassian.com/t/announcement-reminder-on-removal-of-user-names

Therefore, downgrading to previous version is not gonna fix the issue. You have to wait for the new version (not using usernames) to be released.

Cheers,
Dario

[Moeed Chohan]

Is their any other plugin for this