Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX Jenkins 39809 404 pages appear only in pipeline page children #622

Merged

Conversation

scherler
Copy link
Collaborator

@scherler scherler commented Nov 23, 2016

Description

See JENKINS-39809.

I left a FIXME note for @imeredith since I am not yet familiar with the mobx stuff and we need to return some object that indicates that we have to show the 404.

AT PR: jenkinsci/blueocean-acceptance-test#71
Passing ATH: https://ci.blueocean.io/blue/organizations/jenkins/ATH-Jenkinsfile/detail/JENKINS-39809_404_pages_appear_only_in_pipelinePage_children/4

Submitter checklist

  • Link to JIRA ticket in description, if appropriate.
  • Change is code complete and matches issue description
  • Appropriate unit or acceptance tests or explanation to why this change has no tests
  • Reviewer's manual test instructions provided in PR description. See Reviewer's first task below.
  • Ran Acceptance Test Harness against PR changes.

Reviewer checklist

  • Run the changes and verified the change matches the issue description
  • Reviewed the code
  • Verified that the appropriate tests have been written or valid explanation given

@jenkinsci/code-reviewers @reviewbybees

@scherler scherler changed the title Jenkins 39809 404 pages appear only in pipeline page children FIX Jenkins 39809 404 pages appear only in pipeline page children Nov 24, 2016
@ghost
Copy link

ghost commented Nov 24, 2016

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

… shrinkCrap so much. I have lost so many hours on that crap tool. Unbelievable
@michaelneale
Copy link
Member

michaelneale commented Nov 25, 2016

Some things I tried:

Activity screen with non existing pipeline name: works
Dashboard with nonsense path: works
Result screen with non existent pipeline name or run: doesn't work, although API shows up 404 - and 🐜 unless you mean this is what you need Ivan to look at?

So if the scope of this is narrowed to be those - then 🐝 from be (and thanks for ATH too!)

Can you make a follow on ticket for Ivan or something to deal with the results screen not showing 404 @scherler ?

@@ -90,6 +90,9 @@ export class ActivityService extends BunkerService {
run.result = 'UNKNOWN';
}
return this.setItem(run);
})
.catch(err => {
console.log('There had been an error while trying to get the data.', err); // FIXME: Ivan what is the way to return an "error" opbject so underlying component are aware of the problem and can react
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"There has" - as past tense doesn't make sense here 🐜

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and this is where it knows it is a 404, eg on results screen:

blueocean.js:1688 GET http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/keitha/branches/fdsfd/runs/3/ 404 (Not Found)request @ blueocean.js:1688dedupe @ blueocean.js:4475dedupe @ blueocean.js:4498rawFetchJSON @ blueocean.js:1699fetchJSON @ blueocean.js:1765fetchActivity @ blueocean.js:2694_fetchRun @ jenkins-js-extension.js:33974componentWillMount @ jenkins-js-extension.js:33948target.(anonymous function) @ jenkins-js-extension.js:9126performInitialMount @ blueocean.js:79317mountComponent @ blueocean.js:79224mountComponent @ blueocean.js:86237updateChildren @ blueocean.js:77502_reconcilerUpdateChildren @ blueocean.js:85090_updateChildren @ blueocean.js:85189updateChildren @ blueocean.js:85176_updateDOMChildren @ blueocean.js:80934updateComponent @ blueocean.js:80752receiveComponent @ blueocean.js:80710receiveComponent @ blueocean.js:86316_updateRenderedComponent @ blueocean.js:79718_performComponentUpdate @ blueocean.js:79688updateComponent @ blueocean.js:79609receiveComponent @ blueocean.js:79511receiveComponent @ blueocean.js:86316_updateRenderedComponent @ blueocean.js:79718_performComponentUpdate @ blueocean.js:79688updateComponent @ blueocean.js:79609performUpdateIfNecessary @ blueocean.js:79525performUpdateIfNecessary @ blueocean.js:86348runBatchedUpdates @ blueocean.js:87387perform @ blueocean.js:89435perform @ blueocean.js:89435perform @ blueocean.js:87326flushBatchedUpdates @ blueocean.js:87409closeAll @ blueocean.js:89501perform @ blueocean.js:89448batchedUpdates @ blueocean.js:83118enqueueUpdate @ blueocean.js:87437enqueueUpdate @ blueocean.js:87045enqueueForceUpdate @ blueocean.js:87178ReactComponent.forceUpdate @ blueocean.js:78557(anonymous function) @ jenkins-js-extension.js:9158Reaction.runReaction @ jenkins-js-extension.js:11108runReactions @ blueocean.js:59540transactionEnd @ blueocean.js:59612executeAction @ blueocean.js:58863res @ blueocean.js:58831(anonymous function) @ blueocean.js:3874
blueocean.js:2706 There had been an error while trying to get the data. Error: Not Found(…)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I talked to @imeredith and he wanted to extend the pager to return an object such as:

{ data, error, state }

That will hopefully go away anyway but will fix the working.

@@ -15,7 +15,7 @@
},
"devDependencies": {
"@jenkins-cd/eslint-config-jenkins": "0.0.2",
"@jenkins-cd/js-builder": "0.0.47",
"@jenkins-cd/js-builder": "0.0.49-beta6",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder what goodness this brings

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is fixing a bug that we discovered when I moved the NotFound to core and had to introduce react-router as dep. Without that version that leads to an exception for the bundle. Kudos to @tfennelly

@scherler
Copy link
Collaborator Author

@michaelneale if you want we keep this PR open.

however I personally try to get PRs quickly in (still remembering the endless i18n branch which costs extra time to keep it in sync with master.

@scherler
Copy link
Collaborator Author

@scherler scherler merged commit b9ee860 into master Nov 25, 2016
@scherler scherler deleted the JENKINS-39809_404_pages_appear_only_in_pipelinePage_children branch November 25, 2016 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants