[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey updated JENKINS-41403 Jenkins / JENKINS-41403 Additions to Github APIs for Organizations and Repositories Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey updated JENKINS-41403 Jenkins / JENKINS-41403 Additions to Github APIs for Organizations and Repositories Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Cliff Meyers commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories James Dumay Vivek and I chatted earlier and sorted this out; we're all good for now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title James Dumay commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Cliff Meyers Vivek Pandey not sure what I should be chiming in here for? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Cliff Meyers commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Per discussion, boolean flag is okay as long as the "pipelines" array is preserved. This is important when a user wants to transition from "auto-discover" to "single repo" so that we can call the "update" REST API and provide accurate list for "repoNames": [].concat(pipelines, newRepoName) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Cliff Meyers Ok, so all you need is to determine auto-discover or not. How about backend API returns a boolean - I was trying to avoid that but this seems like most logical solution given challenges listing requested repos. Sounds good to you? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Cliff Meyers commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories If we drop "requestedRepos" we can't determine whether the user originally picked "autodiscover" or "one repo" and this has a profound implication on what we can do with the re-entrant flow for Github Creation. Seems appropriate to pull James Dumay into this conversation as he had originally conceived of the feature. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Michael Neale Cliff Meyers Actually I don't see how it can work in all cases no matter which way we go. Internally its represented as pattern that user can tweak as well in classic. So there is no guarunteed round trip. I propose to drop requestedRepos property as there doesn't seem a way to provide that in consistent way. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Michael Neale commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Vivek Pandey if we can discriminate between if it was created by blue ocean or not* - sure. Perhaps could be another field? I would leave it to Cliff Meyers. However, I think it is probably fine to omit it. What about the case that it was created by blue ocean originally, but a user tweaks the regex after the fact - it would then be invalidated and we would have to know somehow - is this possible ? Is it necessary to be a property - as if it is a list of patterns, it is pretty clear that it is a list (ie space separated right? or not reasonable to reverse it out of the pattern?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Michael Neale Cliff Meyers requestedRepos is saved as pattern using underlying GitHub-branch-source library. If you create org pipeline using BO creation flow there is way to get list of requested repo (BO api saves list of requested repos as properties on the org folder). However users can create org pipeline using classic and give any kind of regex pattern and its not possible to get meaningful list of repositories. Basically, if its created using classic, this field is going to be empty but that might get interpreted as auto-scanned. So is it reasonable behavior that "requestedRepos" element is present only if org folder was created using BO GitHub creation flow? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41403 Additions to Github APIs for Organizations and Repositories Change By: James Dumay Sprint: pannonian , iapetus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Cliff Meyers commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories I am in agreement: this looks good. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Michael Neale commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Yes that is right. And the assumption is that the name of the org is the name of the top level org folder item so that the UI knows what to look up to fetch what repos are setup etc. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title
Vivek Pandey commented on JENKINS-41403
Re: Additions to Github APIs for Organizations and Repositories
As discussed in backend meeting, the only change will be made in pipeline API that returns org folder pipeline. Following tasks are expected:
Ensure jenkins.branch.OrganizationFolder capability is returned for blueocean organization folder
Following changes are expected in pipeline JSON response:
{
"pipeline":"blueocean-plugin",
"requestedRepos":["master", "task/JENMINS-123"],
"pipelines": ["master", "task/JENMINS-123"]
}
pipelines array is subset of requestedRepos (if not empty) as some of the repos might not have Jenkinsfile
{
"pipeline":"blueocean-plugin",
"requestedRepos":["master", "task/JENMINS-123"],
"pipelines": ["task/JENMINS-123"] //no Jenkinsfile on master
}
If requestedRepos is empty then consider it as auto-discover
{
"pipeline":"blueocean-plugin",
"requestedRepos":[], //auto-discover
"pipelines": ["master", "task/JENMINS-123"]
}
Cliff Meyers Michael Neale did I get everything that needs to be done in API for this ticket?
Add Comment
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Michael Neale commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Cliff Meyers there would be a few ways to solve it that are suitable I am sure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Cliff Meyers commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Michael Neale Well this is a real problem if we can't define a rule or convention to identify these org folders in a consistent manner. Let's discuss in the meeting later today. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Michael Neale commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Vivek Pandey Cliff Meyers yes, returning an empty list or not empty is enough for the UI to decide what should be shown. The other question is a little more vexing. Lets say we have a github org called "cloudbeers". In jenkins today you could create as many instances of the cloudbees github org folder as you want - naming them all something creative, but al of the same thing (or with different filter criteria etc). There may be a valid case for this (not terribly likely, but you may apply different PR rules to some named subset of repos - I am fishing for a reason here). The bottom line is that when you say "github org" - which one of these is the One True github org? In the blue ocean creation flow, you chose "github" and then it enumerate the org (folders?) it knows about, but that implies there is One True github org folder that you will add repos to (or make it auto discovery)? Do we assume the named item is the github orgs name? If things are created through blue ocean we can control this for sure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title
Vivek Pandey commented on JENKINS-41403
Re: Additions to Github APIs for Organizations and Repositories
Cliff Meyers >> So auto-discover is false if in model there are no branch filtering specified? that is branch filter is empty then its auto-discover? > What we call "auto discover" in the UI is the mode where there is no filtering of repositories. You said "branch filtering" but I think perhaps you mean "repository filtering" First of all there could be more than one jenkins org folder for a given GitHub organization. Second there is no definitive way to tell if it was auto-discover. This is UI concept so I can provide an element that can provide list of requested repos when jenkins org folder was created. If its empty you can compute its auto-discover. So my proposed json element in GitHub organization response could be:
{
...
"isJenkinsOrganizationPipeline":true,
"jenkinsOrganizationPipelines":[
{
"pipeline":"cloudbeers1",
"requestedRepos":["PR-7"],
"_links" : {
"self" : {
"_class" : "io.jenkins.blueocean.rest.hal.Link",
"href" : "/organizations/jenkins/pipelines/cloudbeers1/"
}
}
},
{
"pipeline":"cloudbeers2",
"requestedRepos":[], //will fetch all repos
"_links" : {
"self" : {
"_class" : "io.jenkins.blueocean.rest.hal.Link",
"href" : "/organizations/jenkins/pipelines/cloudbeers2/"
}
}
}
]
...
}
There could be more than one jenkins org folder for a given GitHub org, I am not sure how useful its going to be. I would avoid doing it unless there is UX defined to handle it. Lets chat about it Monday, will be good to have James Dumay and Michael Neale around to get clarification on expected UX.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey edited a comment on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories [~cliffmeyers]> I added #2 to this list, related to the HAL href to the Jenkins org folder. Let me know if you think that's doable. It I would avoid doing it as HAL that is not doable inside _links element . HAL links are HTTP reachable resources, org folder contains repositories and not other way round. This way when you fetch jenkins org folder (/jenkins/scm/github/organizations/cliffmeyers/) you should see HAL link to repositories. Besides if you are accessing /jenkins/scm/github/organizations/cliffmeyers/repositories/ then you already have org folder link that is /jenkins/scm/github/organizations/cliffmeyers/. I could expose it as separate element, but it should be a collection as there could be more than one jenkins org folder for a given GitHub organization. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Cliff Meyers > I added #2 to this list, related to the HAL href to the Jenkins org folder. Let me know if you think that's doable. It is not doable. HAL links are HTTP reachable resources, org folder contains repositories and not other way round. This way when you fetch jenkins org folder (/jenkins/scm/github/organizations/cliffmeyers/) you should see HAL link to repositories. Besides if you are accessing /jenkins/scm/github/organizations/cliffmeyers/repositories/ then you already have org folder link that is /jenkins/scm/github/organizations/cliffmeyers/. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey started work on JENKINS-41403 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Cliff Meyers edited a comment on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories 1. > So auto-discover is false if in model there are no branch filtering specified? that is branch filter is empty then its auto-discover? What we call "auto discover" in the UI is the mode where there is no filtering of repositories. You said "branch filtering" but I think perhaps you mean "repository filtering" 2. > yeah can be done, I guess you want it to be true if there is job for this repo inside this org folder Yes, that's exactly right.These fields will allow us to customize the UI appropriately when the user selects a Github organization that already has an org folder created in Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-41403
Additions to Github APIs for Organizations and Repositories
Change By:
Cliff Meyers
I would like to request two additions to the Github APIs.When listing organizations via {{/jenkins/scm/github/organizations/?credentialId=github}} the response is currently:{code}[{"_class": "io.jenkins.blueocean.blueocean_github_pipeline.GithubOrganization","_links": {"repositories": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/jenkinsci/repositories/"},"self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/jenkinsci/"}},"avatar": "https://avatars.githubusercontent.com/u/107424?v=3=50","jenkinsOrganizationPipeline": false,"name": "jenkinsci"}, {"_class": "io.jenkins.blueocean.blueocean_github_pipeline.GithubUserOrganization","_links": {"repositories": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/cliffmeyers/repositories/"},"self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/cliffmeyers/"}},"avatar": "https://avatars.githubusercontent.com/u/143466?v=3=50","jenkinsOrganizationPipeline": true,"name": "cliffmeyers"}, {"_class": "io.jenkins.blueocean.blueocean_github_pipeline.GithubOrganization","_links": {"repositories": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/cloudbees/repositories/"},"self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/cloudbees/"}},"avatar": "https://avatars.githubusercontent.com/u/235526?v=3=50","jenkinsOrganizationPipeline": false,"name": "cloudbees"}]{code} 1. For organizations where jenkinsOrganizationPipeline is {{true}}, could we add an additional field that indicates whether "auto discover" is enabled? This is equivalent to a Github org folder that was created without specifying any repository names (i.e. empty "repoNames" array) 2. For organizations where jenkinsOrganizationPipeline is {{true}}, could we also add a HAL link to the Jenkins org folder? This will make REST API update calls much easier. When listing repositories via {{/jenkins/scm/github/organizations/cliffmeyers/repositories/?credentialId=github=1=100}} the response is currently:{code}{"_class": "io.jenkins.blueocean.blueocean_github_pipeline.GithubRespositoryContainer","_links": {"self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/cliffmeyers/repositories/"}},
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Cliff Meyers commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Vivek Pandey I added #2 to this list, related to the HAL href to the Jenkins org folder. Let me know if you think that's doable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Cliff Meyers commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories 1. What we call "auto discover" in the UI is the mode where there is no filtering of repositories. You said "branch filtering" but I think perhaps you mean "repository filtering" 2. Yes, that's exactly right. These fields will allow us to customize the UI appropriately when the user selects a Github organization that already has an org folder created in Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Vivek Pandey commented on JENKINS-41403 Re: Additions to Github APIs for Organizations and Repositories Cliff Meyers > For organizations where jenkinsOrganizationPipeline is true, could we add an additional field that indicates whether "auto discover" is enabled? So auto-discover is false if in model there are no branch filtering specified? that is branch filter is empty then its auto-discover? > Could we add a field to the repository object that indicates whether a pipeline has already been created for it? yeah can be done, I guess you want it to be true if there is job for this repo inside this org folder Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-41403
Additions to Github APIs for Organizations and Repositories
It would be nice to have this API sooner rather than later so I can spend some more time on these re-entrant flows. Thanks Vivek Pandey!
Change By:
Cliff Meyers
Sprint:
pannonian
I would like to request two additions to the Github APIs. When listing organizations via {{/jenkins/scm/github/organizations/?credentialId=github}} the response is currently:{code}[{"_class": "io.jenkins.blueocean.blueocean_github_pipeline.GithubOrganization","_links": {"repositories": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/jenkinsci/repositories/"},"self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/jenkinsci/"}},"avatar": "https://avatars.githubusercontent.com/u/107424?v=3=50","jenkinsOrganizationPipeline": false,"name": "jenkinsci"}, {"_class": "io.jenkins.blueocean.blueocean_github_pipeline.GithubUserOrganization","_links": {"repositories": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/cliffmeyers/repositories/"},"self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/cliffmeyers/"}},"avatar": "https://avatars.githubusercontent.com/u/143466?v=3=50","jenkinsOrganizationPipeline": true,"name": "cliffmeyers"}, {"_class": "io.jenkins.blueocean.blueocean_github_pipeline.GithubOrganization","_links": {"repositories": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/cloudbees/repositories/"},"self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/organizations/jenkins/scm/github/organizations/cloudbees/"}},"avatar": "https://avatars.githubusercontent.com/u/235526?v=3=50","jenkinsOrganizationPipeline": false,"name": "cloudbees"}]{code}For organizations where jenkinsOrganizationPipeline is {{true}}, could we add an additional field that indicates
[JIRA] (JENKINS-41403) Additions to Github APIs for Organizations and Repositories
Title: Message Title Cliff Meyers created an issue Jenkins / JENKINS-41403 Additions to Github APIs for Organizations and Repositories Issue Type: Improvement Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Jan/25 12:19 AM Priority: Minor Reporter: Cliff Meyers Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
