[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz closed an issue as Fixed Jenkins / JENKINS-58717 Modify ATH to be compatible with new GitHub Branch Source UI Change By: Karl Shultz Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.8226.1579021381560%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz updated JENKINS-58717 This was fixed with 541. Jenkins / JENKINS-58717 Modify ATH to be compatible with new GitHub Branch Source UI Change By: Karl Shultz Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz commented on JENKINS-58717 Re: Modify ATH to be compatible with new GitHub Branch Source UI I've got a simple pull request up for review that adds the ability to set a single repository URL from a test, via the new field in GitHub Branch Source 2.5.5. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4380.1564520580215%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz updated JENKINS-58717 Jenkins / JENKINS-58717 Modify ATH to be compatible with new GitHub Branch Source UI Change By: Karl Shultz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4381.1564520580260%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz commented on JENKINS-58717 Re: Modify ATH to be compatible with new GitHub Branch Source UI I found a way to get past this, so I'm no longer blocked against 58071. But 58071 is still worth looking at. The behavior was, when working on the ATH from IntelliJ IDEA, I wanted to set an environment variable specifying a war file. Something like this: JENKINS_LOCAL_HOSTNAME=127.0.0.1;BROWSER=chrome;JENKINS_WAR=/some/path/to/jenkins.war When running that way, I was having problems getting the UI to load correctly. The trace itself can be seen here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4379.1564520520112%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz started work on JENKINS-58717 Change By: Karl Shultz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4172.1564502340089%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz commented on JENKINS-58717 Re: Modify ATH to be compatible with new GitHub Branch Source UI Assigning to myself. I'm currently blocked by JENKINS-58071. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4091.1564499100044%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz assigned an issue to Karl Shultz Jenkins / JENKINS-58717 Modify ATH to be compatible with new GitHub Branch Source UI Change By: Karl Shultz Assignee: Oliver Gondža Karl Shultz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.4085.1564498740349%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-58717
Modify ATH to be compatible with new GitHub Branch Source UI
Change By:
Karl Shultz
*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 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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-58717
Modify ATH to be compatible with new GitHub Branch Source UI
Change By:
Karl Shultz
*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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-58717
Modify ATH to be compatible with new GitHub Branch Source UI
Change By:
Karl Shultz
*Summary*Starting with Git 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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-58717
Modify ATH to be compatible with new GitHub Branch Source UI
Change By:
Karl Shultz
*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 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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-58717 Modify ATH to be compatible with new GitHub Branch Source UI Change By: Karl Shultz Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201009.1564432009000.3519.1564432081048%40Atlassian.JIRA.
[JIRA] (JENKINS-58717) Modify ATH to be compatible with new GitHub Branch Source UI
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-58717 Modify ATH to be compatible with new GitHub Branch Source UI Issue Type: Bug Assignee: Oliver Gondža Attachments: image-2019-07-29-16-25-51-544.png Components: acceptance-test-harness Created: 2019-07-29 20:26 Environment: GitHub Branch Source 2.5.5 Priority: Minor Reporter: Karl Shultz 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: It's possible that the ATH will also need to maintain some sort of backward compatibility with the old UI. Add Comment
