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

Facing problem when integrating Blue Ocean with Bitbucket

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • blueocean-plugin
    • None
    • Jenkins Docker
    • Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2

      My problem is occurring when I am trying to integrate Blue Ocean with Bitbucket. I have a repository where I have a Dockerfile for my project. I am trying to run a build using the Dockerfile but I am unable to do so as Blue Ocean gives me the error "You don't have any branches that contain a Jenkinsfile". Although, I have a jenkins file in my repository as well which looks similar to

      Jenkinsfile (Declarative Pipeline)

       

      pipeline\{
      
         agent any
      
         stages \{
      
            stage('Build') \{
      
               steps \{
      
                   cd Docker
      
                   docker build -t dockerselenium .
      
              }
      
          }
      
        }
      
      }
      

       

      Steps taken to create a pipeline using Blue Ocean

      1. Select GIT in the first step as I am using bitbucket.
      2. Enter the repo url in the format of 'https://<username>@bitbucket.org/<username>/<project>/<reponame>.git'
      3. Enter username and password as I am using HTTPS to connect to bitbucket.
      4. Add credential to Blue Ocean by clicking on the 'ADD' button.
      5. Click on the button 'Create a pipeline'.

      After these steps are completed it gives me an error saying 'You don't have any branches that contain a Jenkinsfile'.

      I also tried to check the configuration of the task created in jenkins. This is the log which I get after the execution of 'MultiBranch Pipeline' scan is completed.

      Started by user
      
      [Soumyajit Basu|http://localhost:8080/user/corefinder88]
      
      [Wed Apr 12 22:21:44 IST 2017] Starting branch indexing... > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to
      
      [https://sbasuhoverr@bitbucket.org/hoverr/dockersetup.git]
      
      > git config remote.origin.url
      
      [https://sbasuhoverr@bitbucket.org/hoverr/dockersetup.git]
       # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* ERROR: Timeout after 10 minutes
      
      [ERROR|http://stacktrace.jenkins-ci.org/search?query=ERROR]
      
      : [Wed Apr 12 22:41:44 IST 2017] Could not update folder level actions from source e597234e-f5b8-45f7-a4e0-9fea5fcfd1df
      
      [hudson.plugins.git.GitException|http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException]
      
      : Command "git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*" returned status code 143: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1799) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1525) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:65) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:316) at jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:222) at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:390) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:691) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:585) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:266) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:162) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:967) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405) [Wed Apr 12 22:41:44 IST 2017] Finished branch indexing. Indexing took 10 min FATAL: Failed to recompute children of dockersetup
      
      [hudson.plugins.git.GitException|http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException]
      
      : Command "git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*" returned status code 143: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1799) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1525) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:65) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:316) at jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:222) at jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:390) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:691) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:585) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:266) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:162) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:967) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405)
      
      Finished: FAILURE
      

          [JENKINS-43546] Facing problem when integrating Blue Ocean with Bitbucket

          James Dumay added a comment -

          corefinder89 it appears that Jenkins is timing out when connecting to Bitbucket.org (you can see ERROR: Timeout after 10 minutes in the log).

          Would you happen to be behind a proxy?

          James Dumay added a comment - corefinder89 it appears that Jenkins is timing out when connecting to Bitbucket.org (you can see ERROR: Timeout after 10 minutes in the log). Would you happen to be behind a proxy?

          James Dumay added a comment -

          Assigning to myself during investigation

          James Dumay added a comment - Assigning to myself during investigation

          Philipp Gayret added a comment - - edited

          Just to add, we are having the same issue. We're currently trying out Jenkins 2 for the first time. We have a fairly large repository, and are indeed behind a (http) proxy, also using Stash (aka Bitbucket).

          It appears to run for 10 minutes, which is getting to 98% of a git clone of our main repository (...rofl).

           

          ERROR: Timeout after 10 minutes
          ERROR: Error cloning remote repo 'origin'
          hudson.plugins.git.GitException: Command "git fetch --tags --progress https://*******.git +refs/heads/*:refs/remotes/origin/*" returned status code 143:
          

          Philipp Gayret added a comment - - edited Just to add, we are having the same issue. We're currently trying out Jenkins 2 for the first time. We have a fairly large repository, and are indeed behind a (http) proxy, also using Stash (aka Bitbucket). It appears to run for 10 minutes, which is getting to 98% of a git clone of our main repository (...rofl).   ERROR: Timeout after 10 minutes ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress https: //*******.git +refs/heads/*:refs/remotes/origin/*" returned status code 143:

          jamesdumay No I am not behind a proxy

          Soumyajit Basu added a comment - jamesdumay No I am not behind a proxy

          Philipp Gayret added a comment - - edited

          At your Git SCM part of your configuration under "Additonal Behaviours" you can add "Advanced Clone Behaviours" in where you can fill in the field "Timeout (in minutes) for clone and fetch operations". Putting 30 there will print on your git fetch "# timeout=30".

          This is working for us. ( Complete checkout took 23 minutes. )

          Using Jenkins Pipeline Groovy DSL the code looks somewhat like:

          checkout([$class                           : 'GitSCM',
                    poll                             : true,
                    branches                         : [[name: branch]],
                    doGenerateSubmoduleConfigurations: false,
                    extensions                       : [[$class           : 'CloneOption',
                                                         noTags           : false,
                                                         reference        : '',
                                                         shallow          : false,
                                                         timeout: 30]],
                    submoduleCfg                     : [],
                    userRemoteConfigs                : [[url: repository]]])
          

          I believe you can close this issue.

          Philipp Gayret added a comment - - edited At your Git SCM part of your configuration under "Additonal Behaviours" you can add "Advanced Clone Behaviours" in where you can fill in the field "Timeout (in minutes) for clone and fetch operations". Putting 30 there will print on your git fetch "# timeout=30". This is working for us. ( Complete checkout took 23 minutes. ) Using Jenkins Pipeline Groovy DSL the code looks somewhat like: checkout([$class : 'GitSCM' , poll : true , branches : [[name: branch]], doGenerateSubmoduleConfigurations: false , extensions : [[$class : 'CloneOption' , noTags : false , reference : '', shallow : false , timeout: 30]], submoduleCfg : [], userRemoteConfigs : [[url: repository]]]) I believe you can close this issue.

          James Dumay added a comment -

          stephenconnolly hrmpw in this case clones will fail with the default timeout if the clone is taking a long time. If we are still retrieving data from the git server (say, fast connection but a lot of data to be transfered) why do we honour this timeout at all?

          James Dumay added a comment - stephenconnolly hrmpw in this case clones will fail with the default timeout if the clone is taking a long time. If we are still retrieving data from the git server (say, fast connection but a lot of data to be transfered) why do we honour this timeout at all?

            jamesdumay James Dumay
            corefinder89 Soumyajit Basu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: