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

Blue ocean won't create or edit jenkinsfile when using git

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • Blue Ocean 1.3

      Steps to recreate:

      open Blue Ocean and login if not already logged in.

      click New Pipeline

      Select Git for where you store your code

      follow prompts to give it the necessary credentials with access to the repository and name it and save.

       

      What happens:

      Message that states You don't have any branches that contain a Jenkinsfile.

       

      What should happen:

      A Jenkins file is created and the developer can now use the Pipeline editor within Blue Ocean to edit that file.

       

          [JENKINS-47137] Blue ocean won't create or edit jenkinsfile when using git

          focus zheng added a comment - - edited

          You don't have any branches that contain a Jenkinsfile

          A Jenkinsfile is defined in your repository and describes how your pipeline will work. this shows after I create a gitlab blueocean.

          Blue Ocean version 1.2.4 · Core 2.10 · e2b50bd · (no branch) · 19th September 2017 08:42 PM

          focus zheng added a comment - - edited You don't have any branches that contain a Jenkinsfile A Jenkinsfile is defined in your repository and describes how your pipeline will work. this shows after I create a gitlab blueocean. Blue Ocean version 1.2.4 · Core 2.10 · e2b50bd · (no branch) · 19th September 2017 08:42 PM

          John Behm added a comment -

          Have likely the same issue:

          My setup: Gitea for code hosting, a fork of Gogs

          So I have an already existing repository that contains a c/c++ project where the default branch is not called master, but zCatch. 

          What I want to do is to create a simple pipeline in blue ocean that only executes some existing build scripts in a folder.

          What I want Blue ocean/jenkins to do is to simply add a jenkins file to the source's root folder and not to do anything else.

          What it actually does is to seemingly overwrite the branch or something for me not understandable, because after Blue ocean adds my pipeline, all I am left with is with my zCatch branch with only a jenkinsfile and the rest of the code is gone. The commit history only seems to show one commit that is the one Blue ocean created.

          John Behm added a comment - Have likely the same issue: My setup: Gitea for code hosting, a fork of Gogs So I have an already existing repository that contains a c/c++ project where the default branch is not called master, but zCatch.  What I want to do is to create a simple pipeline in blue ocean that only executes some existing build scripts in a folder. What I want Blue ocean/jenkins to do is to simply add a jenkins file to the source's root folder and not to do anything else. What it actually does is to seemingly overwrite the branch or something for me not understandable, because after Blue ocean adds my pipeline, all I am left with is with my zCatch branch with only a jenkinsfile and the rest of the code is gone. The commit history only seems to show one commit that is the one Blue ocean created.

          John Behm added a comment -

          see my first comment

          John Behm added a comment - see my first comment

            Unassigned Unassigned
            paradoxicalgorm Ryan Taylor
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: