-
Story
-
Resolution: Fixed
-
Critical
-
None
-
-
tethys, pannonian, Blue Ocean 1.1, Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2
This improvement is completed and scheduled for release in 1.2. Check the roadmap page for updates.
In Scope
- New option "Github Enterprise"
- Requires us to provide a URL to Github enterprise as part of the step that accepts the token
Blocked on ATH harness for creation JENKINS-42600
Mockups defined at https://cloudbees.atlassian.net/wiki/display/UX/Pipeline+Creation#PipelineCreation-GithubEnterprise
- is blocked by
-
JENKINS-42600 Creation tests for "GitHub" flow
-
- Resolved
-
- is duplicated by
-
JENKINS-45554 BlueOcean to use organization GitHub
-
- Closed
-
-
JENKINS-43659 Creating pipelines using Blue Ocean with GitHub Enterprise
-
- Resolved
-
- is related to
-
JENKINS-46251 Need to get Jenkinsfiles which can use more than 1 project in the same repo
-
- Resolved
-
-
-
- Open
-
- links to
[JENKINS-40855] Developer wants to connect to a GitHub Enterprise server
| Epic Link | New: JENKINS-36588 [ 172614 ] |
| Rank | New: Ranked higher |
| Sprint | Original: kraken [ 166 ] | New: tethys [ 161 ] |
| Rank | New: Ranked higher |
| Sprint | Original: tethys [ 161 ] | New: tethys, pannonian [ 161, 211 ] |
| Issue Type | Original: Bug [ 1 ] | New: Story [ 10002 ] |
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
jamesdumay I recall seeing an e-mail about this but I am not sure if our access was ever granted or how to go about testing it?
vivek if we can confirm this week we have access then perhaps I'll schedule a meeting to talk about what changes are needed. I think your API design for Github might already account for this with the URL field.
vivek cliffmeyers can you please discuss what API changes might be needed to allow Github Enterprise server URL to be used?
I have asked CloudBees internal OPs team to get you access to the testing server