Installed blueocean

      • Create pipeline
      • choose github
      • choose my account (coupled to already created github access token)
      • choose my repo (which is a PRIVATE repo)
        • repo already contains a jenkinsfile
      • wait until pipeline gets created, never happens
      • blueocean state "pipeline being created, you can go back to dashboard"
      • back in dashboard, I see the newly created pipeline
      • click on pipeline: 

        You don't have any branches that contain a Jenkinsfile

      I don't? Djeeze, what this then?

       

      I am trying to get pipelines going for 4 days now.... Tried Bitbucket with apppassword => can't login.

       

      Trying github instead, moved archive over to new created private repo in github. Greated access token, created credentials in jenkins with username and PAT. But also this doesn't seem to work.

       

      Can somebody PLEASE confirm:

      • Is it possible to use blueocean pipelines for PRIVATE github repo (username + PAT)?
      • Is it possible to use blueocean pipelines for PRIVATE Bitbucket repo (username+apppassword)

       

      Are all the issues we encounter known? Will they get solved or is blueocean dropped (no longer supported?).

       

      Any guidance would be greatly appreciated...

       

      Many thanks

       

       

          [JENKINS-68965] unable to create pipeline for private github repo

          Bas Prins added a comment -

          Trying to validate branch source:

          Bas Prins added a comment - Trying to validate branch source:

          Bas Prins added a comment -

          Bas Prins added a comment -

          Mark Waite added a comment - - edited

          Thanks for reporting the issue. I'm able to duplicate the issue as you reported it using both GitHub and Bitbucket on my installation where I had removed the Blue Ocean Pipeline Editor plugin.

          If I install the Blue Ocean pipeline editor plugin, then I'm able to create Pipelines in empty GitHub repositories with Blue Ocean. I haven't yet confirmed that I can create new Pipelines in Bitbucket.

          As far as I can tell from reading the dependencies on plugins.jenkins.io, the current tutorial installation instructions install the Pipeline editor plugin and should not result in the problem you reported here. I'm not 100% certain of that, but it seems likely.

          Can you confirm that you have the Blue Ocean Pipeline Editor plugin installed?

          On a general note, no enhancements to Blue Ocean are currently planned. See the explanation posted to the Jenkins Developers mailing list. I've proposed to kmartens27 and to halkeye that we'll add information to the existing Blue Ocean documentation so that users know that new functionality is not being added to Blue Ocean and that the maintainers are only addressing selected significant security issues and functional defects.

          Mark Waite added a comment - - edited Thanks for reporting the issue. I'm able to duplicate the issue as you reported it using both GitHub and Bitbucket on my installation where I had removed the Blue Ocean Pipeline Editor plugin. If I install the Blue Ocean pipeline editor plugin, then I'm able to create Pipelines in empty GitHub repositories with Blue Ocean. I haven't yet confirmed that I can create new Pipelines in Bitbucket. As far as I can tell from reading the dependencies on plugins.jenkins.io , the current tutorial installation instructions install the Pipeline editor plugin and should not result in the problem you reported here. I'm not 100% certain of that, but it seems likely. Can you confirm that you have the Blue Ocean Pipeline Editor plugin installed? On a general note, no enhancements to Blue Ocean are currently planned. See the explanation posted to the Jenkins Developers mailing list . I've proposed to kmartens27 and to halkeye that we'll add information to the existing Blue Ocean documentation so that users know that new functionality is not being added to Blue Ocean and that the maintainers are only addressing selected significant security issues and functional defects.

          Bas Prins added a comment -

          Hi markewaite , thanks for confirming, then I can at least stop trying to get it to work.

          Do I understand your reply and what I read on the link you provided correctly that Blue Ocean will be dropped eventually? If that's the case, are there already alternatives I can try to achieve something similar? The idea behind Blue Ocean pipelines was absolutely brilliant, a super light weight approach to dockerize all different kind of build environment and automate builds for these different projects. Is there anything you can suggest? 

          Bas Prins added a comment - Hi markewaite , thanks for confirming, then I can at least stop trying to get it to work. Do I understand your reply and what I read on the link you provided correctly that Blue Ocean will be dropped eventually? If that's the case, are there already alternatives I can try to achieve something similar? The idea behind Blue Ocean pipelines was absolutely brilliant, a super light weight approach to dockerize all different kind of build environment and automate builds for these different projects. Is there anything you can suggest? 

          Mark Waite added a comment -

          Do I understand your reply and what I read on the link you provided correctly that Blue Ocean will be dropped eventually?

          Jenkins drops plugins very rarely and only with conditions specific to that plugin. For example, plugins that have very serious security issues may be dropped. Unmaintained plugins are rarely dropped unless there is another issue that prompts it to be dropped.

          There is so much interest and so much use of the pipeline visualization from Blue Ocean that I don't think it will be dropped.

          If that's the case, are there already alternatives I can try to achieve something similar?

          Tim Jacomb's Pipeline Graph Viewer plugin provides an alpha quality version of the pipeline visualization portion of Blue Ocean. It does not provide the Pipeline Editor portion of Blue Ocean

          Mark Waite added a comment - Do I understand your reply and what I read on the link you provided correctly that Blue Ocean will be dropped eventually? Jenkins drops plugins very rarely and only with conditions specific to that plugin. For example, plugins that have very serious security issues may be dropped. Unmaintained plugins are rarely dropped unless there is another issue that prompts it to be dropped. There is so much interest and so much use of the pipeline visualization from Blue Ocean that I don't think it will be dropped. If that's the case, are there already alternatives I can try to achieve something similar? Tim Jacomb's Pipeline Graph Viewer plugin provides an alpha quality version of the pipeline visualization portion of Blue Ocean. It does not provide the Pipeline Editor portion of Blue Ocean

          Bas Prins added a comment - - edited

          Hi markewaite 

          I am trying to use jenkins pipelines now without blue ocean, and getting stuck again after just the basic setup.

          I am defining the SCM as follows:

           

          Then, after adding a basic Jenkinsfile and a basic docker file, pushing the changes, I end up with another rather obscure error:

           
          Running on Jenkins in /var/jenkins_home/workspace/unode-pipeline[Pipeline] {[Pipeline] stage[Pipeline]

          { (Declarative: Checkout SCM)[Pipeline] checkoutThe recommended git tool is: git using credential github > git rev-parse --resolve-git-dir /var/jenkins_home/workspace/unode-pipeline/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/basprins/unode.git # timeout=10 Fetching upstream changes from https://github.com/basprins/unode.git > git --version # timeout=10 > git --version # 'git version 2.30.2' using GIT_ASKPASS to set credentials github > git fetch --tags --force --progress – https://github.com/basprins/unode.git +refs/heads/:refs/remotes/origin/ # timeout=10 > git rev-parse refs/remotes/origin/main^

          {commit}
          1. timeout=10
            Checking out Revision f80e28dbe3ba5c8038126d5ca992b07c6319acae (refs/remotes/origin/main)
            > git config core.sparsecheckout # timeout=10
            > git checkout -f f80e28dbe3ba5c8038126d5ca992b07c6319acae # timeout=10
            Commit message: "bla"
            > git rev-list --no-walk 4c22cbb50bf1e0ae3e3895283f35b54cf3970ef9 # timeout=10[Pipeline] }[Pipeline] // stage[Pipeline] withEnv[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Agent Setup)[Pipeline] isUnix[Pipeline] readFile[Pipeline] sh+ docker build -t 97957d46a8ccf7a59e306cdb01f4658b43815c4b -f Dockerfile .
            Error response from daemon: Client sent an HTTP request to an HTTPS server.

          My jenkinsfile:
          pipeline

          {     agent

          { dockerfile true }

              stages {
                  stage('Test') {
                      steps

          {                 echo 'node --version'             }

                  }
              }
          }

          My dockerfile:

          FROM ubuntu

          1. todo define image, start empty

          When I change the jenkinsfile back to `agent any`, the build succeeds. When I use agent { dockerfile true } it will always give the error

          Error response from daemon: Client sent an HTTP request to an HTTPS server.

          Am I doing something wrong? Googling doesn't get me any further. If it helps I will make a new dedicated ticket for this problem.

          Many thanks

           

          Bas Prins added a comment - - edited Hi markewaite   I am trying to use jenkins pipelines now without blue ocean, and getting stuck again after just the basic setup. I am defining the SCM as follows:   Then, after adding a basic Jenkinsfile and a basic docker file, pushing the changes, I end up with another rather obscure error:   Running on Jenkins in /var/jenkins_home/workspace/unode-pipeline [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Checkout SCM) [Pipeline] checkoutThe recommended git tool is: git using credential github > git rev-parse --resolve-git-dir /var/jenkins_home/workspace/unode-pipeline/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/basprins/unode.git # timeout=10 Fetching upstream changes from https://github.com/basprins/unode.git > git --version # timeout=10 > git --version # 'git version 2.30.2' using GIT_ASKPASS to set credentials github > git fetch --tags --force --progress – https://github.com/basprins/unode.git +refs/heads/ :refs/remotes/origin/ # timeout=10 > git rev-parse refs/remotes/origin/main^ {commit} timeout=10 Checking out Revision f80e28dbe3ba5c8038126d5ca992b07c6319acae (refs/remotes/origin/main) > git config core.sparsecheckout # timeout=10 > git checkout -f f80e28dbe3ba5c8038126d5ca992b07c6319acae # timeout=10 Commit message: "bla" > git rev-list --no-walk 4c22cbb50bf1e0ae3e3895283f35b54cf3970ef9 # timeout=10 [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Agent Setup) [Pipeline] isUnix [Pipeline] readFile [Pipeline] sh+ docker build -t 97957d46a8ccf7a59e306cdb01f4658b43815c4b -f Dockerfile . Error response from daemon: Client sent an HTTP request to an HTTPS server. My jenkinsfile: pipeline {     agent { dockerfile true }     stages {         stage('Test') {             steps {                 echo 'node --version'             }         }     } } My dockerfile: FROM ubuntu todo define image, start empty When I change the jenkinsfile back to `agent any`, the build succeeds. When I use agent { dockerfile true } it will always give the error Error response from daemon: Client sent an HTTP request to an HTTPS server. Am I doing something wrong? Googling doesn't get me any further. If it helps I will make a new dedicated ticket for this problem. Many thanks  

          Mark Waite added a comment -

          qbpr I'd suggest that you take that question to the Jenkins gitter channel, the Jenkins community forum, or the Jenkins user mailing list.

          Mark Waite added a comment - qbpr I'd suggest that you take that question to the Jenkins gitter channel , the Jenkins community forum, or the Jenkins user mailing list.

          Bas Prins added a comment -

          markewaite thx, created an account on Jenkins community. Hope somebody can free up some time for newbies... . Thx for the help. Feel free to close this issue!

          Bas Prins added a comment - markewaite thx, created an account on Jenkins community. Hope somebody can free up some time for newbies... . Thx for the help. Feel free to close this issue!

            Unassigned Unassigned
            qbpr Bas Prins
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: