Outbound ip addresses of the Appveyor servers

What is the outbound ip addresses of appveyor servers ? I have got to run the acceptance tests they fail because of the ip restriction set in the application

  1. the ip addressees I detected are these below

    23.101.129.233
    23.101.139.232
    23.101.136.22
    23.101.132.65
    23.101.142.160
    23.101.137.199

    is there any way to have one ip address for all my acceptance requests ?

  2. +1

    Good Post. Very important feature for security.

  3. Well, every build is always running on a new virtual machine with random public IP. I'm not sure we could easily control this parameter in Microsoft Azure environment.

    However, good news is that right now we are working on a new plan which will have pre-deterministic public IPs. It could be ready in 2-3 weeks. For now you could just checking for the range of IPs, kind of 23.101.*.

  4. We also need this for security. Any updates?

  5. Making final touches to a new build environment. Will be ready for private testing this week.

  6. Hey guys,

    The new build environment is ready for beta testing. We are going to move all paying customers to this new environment till the end of this month.

    If you want to be the first to give it a try please let me know and we'll switch your account to new environment.

  7. I can verify that this works great!

  8. I did not understand how we use this feature. Feodor could you elaborate about this? How can we use this feature ?

  9. What feature do you mean?

  10. From this post>>>
    What is the outbound ip addresses of appveyor servers ? I have got to run the acceptance tests they fail because of the ip restriction set in the application

    >>>>>>>>> what I understand is : We will have a specific Ip address for our appveyor application. I want to know how we enable that.

  11. Oh, you can't have a specific IP assigned to your worker, but now it's a well-defined range of worker IPs:

    Public IP addresses assigned to build workers:

    173.193.24.178 - 173.193.24.190
    173.193.56.154 - 173.193.56.158
    

    In CIDR notation:

    173.193.24.176/28
    173.193.56.152/29
    
  12. Thank you.

    That was what we needed as the acceptance test are running in Appveyor. That was a big requirement for us.

    Keep up the good work

    Have a great weekend.

  13. Has the ip addresses changed lately?

    I saw the ip addresses below from appveyor instead:

    173.192.42.20
    173.192.42.22
    173.193.165.164
    173.193.165.166

  14. Added a new host recently - will publish its IPs later today.

    -Feodor

  15. Thank you!

  16. Feodor, you might want to update the SSDT publishing page with the new IPs as well...just spent a few hours trying to figure out why only some of my SSDT deployments were working on my Azure database.

  17. Good catch, thanks! It's been updated.

  18. http://www.appveyor.com/updates/2015/04/13

    Hoping the IP range is going to be a bit more stable going forward. I'm very curious about the switch to SoftLayer.

  19. It's been SoftLayer all the time. We switched data center within SoftLayer and unfortunately IPs are bound to DC.

  20. I'm picking up some new IPs starting 104 and 108. Azure is rejecting these and so my build is failing.

    Could you update the documentation with the new ranges please ? Thanks.

  21. We'll be setting up a router on this new environment to have a single external IP address. What account/project is that?

  22. A single IP address would be great. This is the build https://ci.appveyor.com/project/scascarini/nakedobjectsframework-btilm

  23. We're having the same issue as before where the SSDT Publishing Page is out of date. If at least all of the deploy tasks could be done through this single external IP, it would help a lot for those of us deploying to SQL Azure.

  24. Hi Adam,

    There is a link to actual IP addresses range: http://www.appveyor.com/docs/build-configuration#ip-addresses

  25. Appears that this link described above no longer publishes the IP addresses.

    Also, when publishing the IP addresses, can you also do the correct CIDR notations too?

    Thanks guys.

  26. Sorry, we rearranged our documentation a little. Here is the link: https://www.appveyor.com/docs/build-environment/#ip-addresses

    Those all are separate IP addresses from different datacenters and cloud services we use, so for each of them /32 is CIDR notation :) We understand that it would be better to have single CIDR-based firewall rule, but to provide better performance and reliability we need to spread across different locations.

  27. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:19 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions