Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,557,742
Community Members
 
Community Events
184
Community Groups

Importing cucumber json reports into Jira using xray plugin from Jenkins :getting 404 error

CrazyAs5assin
CrazyAs5assin Jul 16, 2020

Hi , I am trying to import my execution results to Jira using the xray plugin.

 

Upon running the pipeline getting below error

 

Error unable to confirm results of upload upload failed status 404 resposen<?xml version=“1.0” encoding=“UTF-8” standalone=“yes”?>404null for uri: https://companyName.atlassian.net/rest/raven/1.0/import/execution/cucumber/multipart

Jenkins is configured with xray configurations by my orgs Jenkins admin .

Am I missing anything ? Here please help!. However if i try to upload manually and it works .

 

Answer
Watch
Like Be the first to like this
553 views

1 answer

1 accepted

0 votes
Answer accepted
CrazyAs5assin
CrazyAs5assin Jul 16, 2020

I got the issue resolved . The reason for the error is that my jira instance is cloud . I had used server instead of cloud in jira

View More Comments
rohan_nirola
rohan_nirola Apr 27, 2023

I am facing the same issue. What link or api link did you use?

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira Software
Jira Software
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events

See all events