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

Steps from shared libraries should be available from the editor

    Details

    • Similar Issues:

      Description

      Pipeline library functions ideally would show up "like" steps in the blue ocean editor. 

      This may require additional type information so the REST API can furnish the editor with the meta data as needed. If the functions were delivered via a plugin, say like https://github.com/jenkinsci/simple-build-for-pipeline-plugin - then there is a possibility for an interface to be used that can be discovered to provide the meta data needed to make the function calls "look like" a step (ie blue ocean can lookup function extension metadata, and service it up for the editor). Libraries don't have type information now, so a mechanism like this would be acceptable for those that want to have the metadata/editor support. 

       

      – Original –

      The only thing holding us back from starting to use the pipeline editor is an inability to include our shared groovy library steps. I'm not sure the level of effort that would be required to have them in the pipeline editor, but at this point a large chunk of our Jenkinsfiles are made up of calls to our shared libraries, and we currently have to ask people to avoid using the editor because they can't even see the documentation for those libraries while in blue ocean.

        Attachments

          Issue Links

            Activity

            Hide
            jamesdumay James Dumay added a comment -

            Spencer Malone thanks for filing this. Supporting steps from shared libraries is something we want to build soon.

            Show
            jamesdumay James Dumay added a comment - Spencer Malone thanks for filing this. Supporting steps from shared libraries is something we want to build soon.
            Hide
            michaelneale Michael Neale added a comment -

            I have tweaked this to make it clearer. something like: https://github.com/jenkinsci/simple-build-for-pipeline-plugin/blob/master/src/main/java/org/jenkinsci/plugins/pipelinedsl/PipelineDSLGlobal.java could be enhanced to have optional meta data. 

             

            Blue ocean rest api could then load that up via discovered extensions, and serve it up to the editor. The work for this would be mostly on the blue ocean side (and the editor is now merged into the blue ocean codebase anyway)

            Show
            michaelneale Michael Neale added a comment - I have tweaked this to make it clearer. something like: https://github.com/jenkinsci/simple-build-for-pipeline-plugin/blob/master/src/main/java/org/jenkinsci/plugins/pipelinedsl/PipelineDSLGlobal.java  could be enhanced to have optional meta data.    Blue ocean rest api could then load that up via discovered extensions, and serve it up to the editor. The work for this would be mostly on the blue ocean side (and the editor is now merged into the blue ocean codebase anyway)
            Hide
            spencermalone Spencer Malone added a comment -

            That seems reasonable

            Show
            spencermalone Spencer Malone added a comment - That seems reasonable

              People

              • Assignee:
                Unassigned
                Reporter:
                spencermalone Spencer Malone
              • Votes:
                10 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated: