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

Modify creation flows to take the user directly to the pipeline editor when no Jenkinsfiles found

    XMLWordPrintable

    Details

    • Epic Link:
    • Sprint:
      Blue Ocean 1.3, Blue Ocean 1.4 - beta 3
    • Similar Issues:

      Description

      To reduce the number of steps a user needs to take, if a user adds a repository with no Jenkinsfiles, create the Jenkins job as it currently does and then take the user directly to the pipeline editor to create one.

      Note: should probably make an informational toast or something to notify the user exactly why they were sent to the editor.

        Attachments

          Issue Links

            Activity

            Hide
            jamesdumay James Dumay added a comment -

            Keith Zantow wheres this one at?

            Show
            jamesdumay James Dumay added a comment - Keith Zantow wheres this one at?
            Hide
            kzantow Keith Zantow added a comment - - edited

            James Dumay haven't made much progress on this one yet. If you want it in 1.3, let me know (it looks like you do based on the sprint...). This is a non-trivial change, due to a number of factors including how long it may take for indexing to complete and timeouts, etc.

            Show
            kzantow Keith Zantow added a comment - - edited James Dumay haven't made much progress on this one yet. If you want it in 1.3, let me know (it looks like you do based on the sprint...). This is a non-trivial change, due to a number of factors including how long it may take for indexing to complete and timeouts, etc.
            Hide
            jamesdumay James Dumay added a comment -

            Keith Zantow I won't block 1.3 for this but lets target for 1.4

            Show
            jamesdumay James Dumay added a comment - Keith Zantow I won't block 1.3 for this but lets target for 1.4
            Hide
            kshultz Karl Shultz added a comment -

            Testing notes:

            • It's likely that existing automated tests (maybe starting somewhere around here) might need to be overloaded/reworked/something once this change is in place. That could implicitly prove that the actions between adding the repo, and being taken to the editor, have been removed.
            Show
            kshultz Karl Shultz added a comment - Testing notes: It's likely that existing automated tests (maybe starting somewhere around here ) might need to be overloaded/reworked/something once this change is in place. That could implicitly prove that the actions between adding the repo, and being taken to the editor, have been removed.
            Hide
            kzantow Keith Zantow added a comment -

            This has been implemented and the tests were modified to account for this behavior.

            Show
            kzantow Keith Zantow added a comment - This has been implemented and the tests were modified to account for this behavior.

              People

              • Assignee:
                kzantow Keith Zantow
                Reporter:
                kzantow Keith Zantow
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: