Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40116

Crash on login when using blueocean plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • blueocean-plugin
    • None
    • Jenkins ver. 2.19.3
      BlueOcean beta 1.0.0-b12
      Kernel release: 3.16.0-4-amd64
      Kernel version: #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19)
      OS: Debian GNU/Linux 8.6 (jessie)
      (bitnami deployment)
    • tasman, frank

      After using the blueocean plugin for a few days suddenly stops. I restart it and when I try to login I get either a stack trace or a resource not found tomcat error I believe (forgot to screenshot this).

      I also get a jsessionid in the url all the time. Clearing cookies and trying t login again does not work. Using chromium as my default browser.

      Then switched to firefox and tried loggin in: succes. I then deactivated all blueocean related plugins, the problem disappeared and I could then login again at chromium.

        1. jenkins_bug
          5 kB

          [JENKINS-40116] Crash on login when using blueocean plugin

          Tom FENNELLY added a comment -

          We need an NPE check in ResourceCacheControl for when the request path is empty.

          Tom FENNELLY added a comment - We need an NPE check in ResourceCacheControl for when the request path is empty.

          James Dumay added a comment -

          dhensen sorry about that - this is an easy fix we can apply in the next release.

          James Dumay added a comment - dhensen sorry about that - this is an easy fix we can apply in the next release.

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Mark Waite
          Path:
          src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
          src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplAuthTest.java
          http://jenkins-ci.org/commit/git-client-plugin/f7b7cb995f5aaf22dcc49ccc48b980e5d1ce7ecc
          Log:
          Test JENKINS-40116, JENKINS-38194, JENKINS-38179 & JENKINS-38138

          Confirm that characters which Windows requires be escaped in a batch
          file can be used as characters in a git password (as used through https
          with a username / password combination).

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplAuthTest.java http://jenkins-ci.org/commit/git-client-plugin/f7b7cb995f5aaf22dcc49ccc48b980e5d1ce7ecc Log: Test JENKINS-40116 , JENKINS-38194 , JENKINS-38179 & JENKINS-38138 Confirm that characters which Windows requires be escaped in a batch file can be used as characters in a git password (as used through https with a username / password combination).

          Mark Waite added a comment -

          Sorry for the incorrect annotation from a commit. The bug that should have been mentioned in my commit message is JENKINS-40166, not this bug.

          Mark Waite added a comment - Sorry for the incorrect annotation from a commit. The bug that should have been mentioned in my commit message is JENKINS-40166 , not this bug.

            tfennelly Tom FENNELLY
            dhensen Dino Hensen
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: