[JIRA] (JENKINS-42925) Error fetching page: Not found at checkstatus

2017-03-20 Thread jdu...@cloudbees.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42925  
 
 
  Error fetching page: Not found at checkstatus   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 * Go to [http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/blue/organizations/jenkins/cloudbees/] * You'll be redirected to [http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/blue/organizations/jenkins/cloudbees/activity] * Nothing will be showed in the activity and you'll get the JS errors in the screenshot attached \ {code}  GET http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/blue/rest/organizations/jenkins/pipelines/cloudbees/activities/?start=0=26 404 (Not Found)request @ blueocean.js:2551dedupe @ blueocean.js:7854dedupe @ blueocean.js:7877rawFetchJSON @ blueocean.js:2569fetchJSON @ blueocean.js:2650fetchNextPage @ blueocean.js:6128executeAction @ blueocean.js:63201res @ blueocean.js:63173Pager @ blueocean.js:6108lazyPager @ blueocean.js:5244getPager @ blueocean.js:6341activityPager @ blueocean.js:5238componentWillMount @ jenkins-js-extension.js:46475target.(anonymous function) @ jenkins-js-extension.js:11126performInitialMount @ blueocean.js:83535mountComponent @ blueocean.js:83442mountComponent @ blueocean.js:90455updateChildren @ blueocean.js:81720_reconcilerUpdateChildren @ blueocean.js:89308_updateChildren @ blueocean.js:89407updateChildren @ blueocean.js:89394_updateDOMChildren @ blueocean.js:85152updateComponent @ blueocean.js:84970receiveComponent @ blueocean.js:84928receiveComponent @ blueocean.js:90534_updateRenderedComponent @ blueocean.js:83936_performComponentUpdate @ blueocean.js:83906updateComponent @ blueocean.js:83827receiveComponent @ blueocean.js:83729receiveComponent @ blueocean.js:90534_updateRenderedComponent @ blueocean.js:83936_performComponentUpdate @ blueocean.js:83906updateComponent @ blueocean.js:83827performUpdateIfNecessary @ blueocean.js:83743performUpdateIfNecessary @ blueocean.js:90566runBatchedUpdates @ blueocean.js:91605perform @ blueocean.js:93653perform @ blueocean.js:93653perform @ blueocean.js:91544flushBatchedUpdates @ blueocean.js:91627closeAll @ blueocean.js:93719perform @ blueocean.js:93666batchedUpdates @ blueocean.js:87336enqueueUpdate @ blueocean.js:91655enqueueUpdate @ blueocean.js:91263enqueueForceUpdate @ blueocean.js:91396ReactComponent.forceUpdate @ blueocean.js:82775(anonymous) @ jenkins-js-extension.js:11158Reaction.runReaction @ jenkins-js-extension.js:13730runReactions @ blueocean.js:63882transactionEnd @ blueocean.js:63954executeAction @ blueocean.js:63205res @ blueocean.js:63173(anonymous) @ blueocean.js:6616tryCatch @ blueocean.js:38858invokeCallback @ blueocean.js:38873publish @ blueocean.js:38841flush @ blueocean.js:38569blueocean.js:6146 Error fetching page Error: Not Found at checkStatus (blueocean.js:2417)(anonymous) @ blueocean.js:6146 \ {code}

[JIRA] (JENKINS-42925) Error fetching page: Not found at checkstatus

2017-03-20 Thread cmey...@cloudbees.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-42925  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error fetching page: Not found at checkstatus   
 

  
 
 
 
 

 
 James Dumay we need to decide what we should do if the user visits a URL that corresponds to an organization folder. And for that matter, a folder as well. There may be handling for the latter already, in which case perhaps we should do the same for the former?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42925) Error fetching page: Not found at checkstatus

2017-03-20 Thread m.vilaci...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Isa Vilacides created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42925  
 
 
  Error fetching page: Not found at checkstatus   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screen Shot 2017-03-17 at 12.15.44.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Mar/20 9:56 AM  
 
 
Environment: 
 1.0.0-rc1 · Core 2.32.3 · 9ac3256 · (no branch)  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Isa Vilacides  
 

  
 
 
 
 

 
 
 
Go to http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/blue/organizations/jenkins/cloudbees/ 
You'll be redirected to http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/blue/organizations/jenkins/cloudbees/activity 
Nothing will be showed in the activity and you'll get the JS errors in the screenshot attached 
 {code} GET http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/blue/rest/organizations/jenkins/pipelines/cloudbees/activities/?start=0=26 404 (Not Found) request @ blueocean.js:2551 dedupe @ blueocean.js:7854 dedupe @ blueocean.js:7877 rawFetchJSON @ blueocean.js:2569 fetchJSON @ blueocean.js:2650 fetchNextPage @ blueocean.js:6128 executeAction @ blueocean.js:63201 res @ blueocean.js:63173 Pager @ blueocean.js:6108 lazyPager @ blueocean.js:5244 getPager @ blueocean.js:6341 activityPager @ blueocean.js:5238 componentWillMount @ jenkins-js-extension.js:46475 target.(anonymous function) @