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

Support native Git for pipeline creation and editing

    XMLWordPrintable

    Details

    • Sprint:
      Blue Ocean 1.0-rc4, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean 1.3
    • Similar Issues:

      Description

      Improvement on roadmap

      This improvement is on the Blue Ocean project roadmap. Check the roadmap page for updates.

      Scope

      • User can click New Pipeline then pick Git and author a new Jenkinsfile using the Editor and save it back to the repository.
      • User can click Edit Pipeline then author the existing Jenkinsfile using the Editor and save their changes back to the repository
        • In a new branch
        • On the current branch

      Notes

      There are a number of security and user experience concerns that the team have to solve to get this working. 

       

      Design brief

      The user experience should match the equivalent Github feature as much as possible.
      The largest notable difference is that creating and editing with plain Git has noticeably more network traffic than Github. This means the user may have to wait for Blue Ocean to retrieve the content of the repository before showing them the Editor or before their save action is completed.

      Loading the editor

      • Developer clicks the edit action
      • Developer sees a progress dialog with a message "Loading your Jenkinsfile"
        • This could take a while as we have to do a shallow clone of the repository
        • How much progress information do we get from the clone? If we can easily get this info we can use a determinate progress indicator rather than a indeterminate one.
      • Developer should be able to cancel the load if it takes too long
      • Developer sees the Editor

      Saving from the editor

      1. Developer clicks save
      2. Developer sees the save dialog and then confirms
        • May commit back to new branch or current branch
      3. Developer sees progress dialog with message "Saving your pipeline"
      4. Developer lands back on the Activity screen

      Technical notes

      Unlike Github, Blue Ocean needs to make a shallow clone of the repository on the master in order to perform any operations. It is important to do whatever we can to make the editor work for developers at the best possible speed.

        Attachments

          Issue Links

            Activity

            Hide
            cliffmeyers Cliff Meyers added a comment -

            Keith Zantow you're absolutely write. A property probably makes sense here.

            Show
            cliffmeyers Cliff Meyers added a comment - Keith Zantow you're absolutely write. A property probably makes sense here.
            Hide
            kzantow Keith Zantow added a comment -

            Cliff Meyers Vivek Pandey in this case it's a dynamic capability - is there a way to execute some code to determine capabilities for something? E.g. it is based on the configured branch source, based on the URL and credentials and ultimately the ability to perform a specific action. We can't really use class metadata for this without defining more types of BlueScmSource, which I suppose we could do, but seems wrong. We could just add a property instead and allow the ScmSources to calculate as needed.

            Show
            kzantow Keith Zantow added a comment - Cliff Meyers Vivek Pandey in this case it's a dynamic capability - is there a way to execute some code to determine capabilities for something? E.g. it is based on the configured branch source, based on the URL and credentials and ultimately the ability to perform a specific action. We can't really use class metadata for this without defining more types of BlueScmSource, which I suppose we could do, but seems wrong. We could just add a property instead and allow the ScmSources to calculate as needed.
            Hide
            cliffmeyers Cliff Meyers added a comment -

            Okay right. I wonder if adding this to BlueScmSource would be appropriate. it could also be a Capability exposed on a subclass of BlueScmSource. cc Vivek Pandey for input.

            Show
            cliffmeyers Cliff Meyers added a comment - Okay right. I wonder if adding this to BlueScmSource would be appropriate. it could also be a Capability exposed on a subclass of BlueScmSource. cc Vivek Pandey for input.
            Hide
            kzantow Keith Zantow added a comment -

            Cliff Meyers In order to show the editor icon, the pipeline must support writing back to the repo. GH, BB and Git with SSH all work, but HTTPS git may not, etc.

            Show
            kzantow Keith Zantow added a comment - Cliff Meyers In order to show the editor icon, the pipeline must support writing back to the repo. GH, BB and Git with SSH all work, but HTTPS git may not, etc.
            Hide
            cliffmeyers Cliff Meyers added a comment -

            Keith Zantow I don't quite follow your statement about items "supporting saving" - can you elaborate?

            Show
            cliffmeyers Cliff Meyers added a comment - Keith Zantow I don't quite follow your statement about items "supporting saving" - can you elaborate?

              People

              • Assignee:
                kzantow Keith Zantow
                Reporter:
                michaelneale Michael Neale
              • Votes:
                42 Vote for this issue
                Watchers:
                49 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: