You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'll need a aws.ci.jenkins.io DNS A record (pointed by the CNAME ci.jenkins.io once migrated) to the public IPv4 of the controller, and a AAAA record with the public IPv6.
If need be, we'll define a private DNS A record aws.ci.jenkins.io so agents can reach the controller through private subnets
Inbound:
Anywhere HTTP + HTTPS on both IPv4 and IPv6
SSH from the (Azure private VPN) only. We'll set up the VPN routing of users to override routing like we did for the pkg.origin.jenkins.io, usage.jio and census.jio VMs.
Private subnets HTTP, HTTPS, JNLP
Outbound (IPv4 only):
HTTP+ HTTPS + HKP to everywhere
SSH to GitHub public IPs and to private subnets
The text was updated successfully, but these errors were encountered:
This issue tracks the work to migrate ci.jenkins.io controller to the AWS Sponsored.
Current resources:
public_vnet
for it but it is not used anymore)Target for the new VM:
aws.ci.jenkins.io
DNSA
record (pointed by the CNAMEci.jenkins.io
once migrated) to the public IPv4 of the controller, and aAAAA
record with the public IPv6.A
recordaws.ci.jenkins.io
so agents can reach the controller through private subnetsThe text was updated successfully, but these errors were encountered: