-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
GitHub Branch Source 2.5.5
Summary
Starting with GitHub Branch Source 2.5.5 (see PR), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work.
Details
The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a git clone command. The ATH needs to be modified to accomodate this.
Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was set to @Ignore.
The page now looks like this when creating a new project:
It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI.
- relates to
-
JENKINS-58071 Cloudbees error upon initial install - FolderCredentialsProvider
-
- Open
-
[JENKINS-58717] Modify ATH to be compatible with new GitHub Branch Source UI
| Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
| Description |
Original:
*Summary* Starting with Git The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this. The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI. |
New:
*Summary* Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work. *Details* The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this. Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was being [{{@Ignore}} d|https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WorkflowMultibranchTest.java#L37]. The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI. |
| Description |
Original:
*Summary* Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work. *Details* The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this. Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was being [{{@Ignore}} d|https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WorkflowMultibranchTest.java#L37]. The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI. |
New:
*Summary* Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work. *Details* The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this. Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was set to [{{@Ignore}} d|https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WorkflowMultibranchTest.java#L37]. The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI. |
| Description |
Original:
*Summary* Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work. *Details* The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this. Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was set to [{{@Ignore}} d|https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WorkflowMultibranchTest.java#L37]. The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI. |
New:
*Summary* Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work. *Details* The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this. Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was set to [{{@Ignore}}|https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WorkflowMultibranchTest.java#L37]. The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI. |
| Description |
Original:
*Summary* Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work. *Details* The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this. Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why the test was set to [{{@Ignore}}|https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WorkflowMultibranchTest.java#L37]. The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI. |
New:
*Summary* Starting with GitHub Branch Source 2.5.5 (see [PR|https://github.com/jenkinsci/github-branch-source-plugin/pull/236]), we now have two ways to set up our remote repo for multibranch projects based on GitHub repositories. This ticket represents the accompanying updates that the acceptance test harness needs in order to make this work. *Details* The new UI offers, and defaults to, the ability to supply a single HTTPS URL, in much the same way you'd copy/paste such a URL into a {{git clone}} command. The ATH needs to be modified to accomodate this. Before the above-mentioned improvement to GitHub Branch Source, users needed to first supply the repository owner. For example, And then, if the repo owner had hundreds or even thousands of repos, it could take a very long time to populate the resulting drop-down menu. My suspicion is that this delay is the reason why [the test was set to {{@Ignore}}|https://github.com/jenkinsci/acceptance-test-harness/blob/e538cb7ffeeeb11ce5aad4de3b6bc59d03b9a56d/src/test/java/plugins/WorkflowMultibranchTest.java#L37]. The page now looks like this when creating a new project: !image-2019-07-29-16-25-51-544.png|thumbnail! It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI. |
| Assignee | Original: Oliver Gondža [ olivergondza ] | New: Karl Shultz [ kshultz ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Link | New: This issue is blocked by JENKINS-58071 [ JENKINS-58071 ] |
Assigning to myself.
I'm currently blocked by JENKINS-58071.