Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to hit jira api from jenkins

getting 

No JIRA site configured with <URL_HERE> name.

when running 

jiraAddComment site: '<URL_HERE>', idOrKey: 'ticketId', input: "test comment"

 

1 answer

0 votes
Hana Kučerová Community Leader Nov 13, 2019

Hi @Gereth Dittrick,

is it correct, that you are using JIRA Pipeline Steps plugin?

 

Do you have the possibility to check authentication configuration in Jenkins?

https://jenkinsci.github.io/jira-steps-plugin/getting-started/config/authentication/

You can also perform the connection check from the configuration site (using Test connection button).

 

The parameter site is optional - is it neccessary to override global JIRA_SITE variable? Did you try to skip it?

Hello Hana, yes this is the Jira Steps Plugin. The test connect button shows a successful connection but when trying to invoke the plugin with a job i get the above error. I did try omitting the site variable but the JIRA_SITE env variable is empty/null with the specific error

ERROR: No JIRA site configured with null name.
Hana Kučerová Community Leader Nov 14, 2019

Hi @Gereth Dittrick ,

I would recommend you to contact the vendor of the Jira Steps Plugin, described behaviour looks like a bug to me.

If the problem is still relevant, try using the following script in Jenkinspipeline to contact JIRA and make comment to Issue TSP-26:

script {
  withEnv(['JIRA_SITE=JIRA-Test']) {
  def comment = [ body: 'Test comment from Jenkins' ]
  jiraAddComment idOrKey: 'TSP-26', input: comment
}

where JIRA_SITE=JIRA-Test is predefined Jira site in Jenkins system settings:

2021-02-02_073428.png

Like Ivan Ricotti likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you