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

Make the JobDSL playground available internally

      It would be of a great value if the jobDSL Playground Engine, which links now to http://job-dsl.herokuapp.com/ can run internally Dynamic-DSL style as presented in https://github.com/jenkinsci/job-dsl-plugin/blob/master/docs/Dynamic-DSL.md 

      To simplify if the Jenkins installation is available at http://localhost:8080 the DSL API viewer will be available at http://localhost:8080/plugin/job-dsl/api-viewer/index.html and the Playground can be available at http://localhost:8080/plugin/job-dsl/api-viewer/index.html or a configurable internal location so you can take advantage of Dynamic-DSL

          [JENKINS-67438] Make the JobDSL playground available internally

          Tim Jacomb added a comment -

          Isn't this already available jamietanna?

          Tim Jacomb added a comment - Isn't this already available jamietanna ?

          Jamie Tanna added a comment -

          Hey timja the Playground itself isn't available, only the API viewer.

          isurugiu out of interest, what would the perceived benefit of the Playground give you? Is it testing that the DSL itself works, or that you can easily add new jobs without needing to commit to source repos?

          Jamie Tanna added a comment - Hey timja the Playground itself isn't available, only the API viewer. isurugiu out of interest, what would the perceived benefit of the Playground give you? Is it testing that the DSL itself works, or that you can easily add new jobs without needing to commit to source repos?

          Iulian Surugiu added a comment - - edited

          Hi,

          jamietanna & timja

          Without trying to think about what I was having in mind about one year ago when I opened this, I think that both would be beneficial, but primarily would be dev/testing DSL against the current jobdsl plugin version installed on the local Jenkins installation and not a remote one.

          Of course, obvious things like security, plugin versions, or any other local-specific environment customizations would be more appropriate to use when testing.

          Iulian Surugiu added a comment - - edited Hi, jamietanna  & timja Without trying to think about what I was having in mind about one year ago when I opened this, I think that both would be beneficial, but primarily would be dev/testing DSL against the current jobdsl plugin version installed on the local Jenkins installation and not a remote one. Of course, obvious things like security, plugin versions, or any other local-specific environment customizations would be more appropriate to use when testing.

            jamietanna Jamie Tanna
            isurugiu Iulian Surugiu
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: