• Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • blueocean-plugin
    • None
    • pacific, 1.0-b05/b-06

      In Scope

      • Move pipeline editor to its own repository called blueocean-pipleine-editor-plugin
      • Leave it on your personal account for the moment and we can then follow this guide later to get it on the jenkinsci org https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
      • Setup a multi-branch pipeline on blueocean.io

          [JENKINS-38321] Move Pipeline editor to new repository

          Josh McDonald added a comment -

          Not in jenkinsci org on GH yet, but exists at: https://github.com/sophistifunk/blueocean-pipeline-editor

          Not sure what needs to be done to bring it over to jenkinsci, and to get all the security props and PR templates and stuff, but probably want to get those done before we mark this as closed.

          Josh McDonald added a comment - Not in jenkinsci org on GH yet, but exists at: https://github.com/sophistifunk/blueocean-pipeline-editor Not sure what needs to be done to bring it over to jenkinsci, and to get all the security props and PR templates and stuff, but probably want to get those done before we mark this as closed.

          Michael Neale added a comment -

          This is almost done, there is a HOSTING backlog. Once it is, I will setup CI for it (with a Jenkinsfile).

          cc sophistifunk - I don't expect there are tests in it yet but it will just run mvn test the usual way to validate PRs.

          Michael Neale added a comment - This is almost done, there is a HOSTING backlog. Once it is, I will setup CI for it (with a Jenkinsfile). cc sophistifunk - I don't expect there are tests in it yet but it will just run mvn test the usual way to validate PRs.

          Josh McDonald added a comment -

          No tests yet - it's mostly UI code, and when UI is changing and in-progress, tests only get in the way. It is high up on my TODO list to extract some of the graph-management code out of its current home in a component, which will then have tests.

          Josh McDonald added a comment - No tests yet - it's mostly UI code, and when UI is changing and in-progress, tests only get in the way. It is high up on my TODO list to extract some of the graph-management code out of its current home in a component, which will then have tests.

          Michael Neale added a comment -

          sophistifunk yeah no problem, that is what I assumed. This is a separate repo, so you can use literally anything to test it, I am sure it can be catered for. Even a bunch of cats taped together.

          Michael Neale added a comment - sophistifunk yeah no problem, that is what I assumed. This is a separate repo, so you can use literally anything to test it, I am sure it can be catered for. Even a bunch of cats taped together.

            michaelneale Michael Neale
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: