jeremyepling

I have some good news. You'll be able to do this with reusable workflows and it's shipping soon. https://github.com/github/roadmap/issues/98

If you need to lock down reusable deployment workflows, these features will enable that. https://github.com/github/roadmap/issues/249 https://github.com/github/roadmap/issues/220

I think these will solve that. If not, let me know. https://github.com/github/roadmap/issues/249 https://github.com/github/roadmap/issues/220

You can go to your organization settings / Actions and choose the specific repos that can use Actions. Repo admins can’t override that.

We’ve archived a few repos in the last couple months because of this. A we’ll also look at the contributor changes you suggested.

That’s correct. You should use the one that best meets your needs.

I’m glad they’re working for you. Reusable workflows is our next feature to improve reuse. https://github.com/github/roadmap/issues/98

Thanks for taking the time to share your experience. I work on GitHub Actions and am familiar with the limitations you're experiencing. Below is more info on where we're at with each of these issues, using the numbers in your Table of Contents. Also, we have a lot of other new things planned for Actions as you can see in our roadmap. https://github.com/github/roadmap/projects/1?card_filter_que...

2.1 We're starting work on this in the next couple of months. We plan to ship it in early 2022.

2.2 We want to speed up the pace of GitHub Enterprise Server releases, but I don't have more info to share.

2.3 We're looking at ways to not require a GHEC account or "unified" license.

2.4 The limits are much higher with the GitHub hosted runners, but this is a current limit of self-hosted runners.

3.1 It's on our backlog. No date to share.

3.2 I haven't heard this before and thanks for sharing the scenario. We'll think about it.

3.3 This will ship in October.

3.4 We're doing some performance optimizations for GHES 3.4 that should fix this.

3.5 This shipped recently - https://github.blog/changelog/2021-08-25-github-actions-redu...

3.6 We have a couple API improvements coming later this year.

3.7 We're looking into this, but no dates to share.

We're dedicated to making Actions a great experience. As you would assume, I'm very excited about the future of Actions and getting feedback like this helps us make it better.

You don’t need to sign up. It’s open to everyone with a GitHub Account. Also, you don’t need to use Actions. You can just push a container. Here’s a doc that shows you how to push a container. https://docs.github.com/en/packages/getting-started-with-git...

I’m a product manager on Azure Pipelines. Can you tell me more about what’s missing in the docs and language support to make it better. Email works as well jepling at microsoft dot com.

Open source projects get unlimited self-hosted agents. Let me know if you aren't experiencing that. I'll make sure it's clear in the docs and the website. jepling at microsoft dot com.

I'd like to learn more about why Azure Pipelines was slower for your build. Feel free to email me. jepling at microsoft dot com.

I'm a product manager on Azure Pipelines. I'd like to learn more about your pipeline so we can improve the performance of our hosted build agents. It's something we're improving right now. Feel free to email me. jepling at microsoft dot com

Thanks for the detailed and thoughtful feedback. I'd love to get on a call with you to discuss your needs and some of the items on our roadmap. If you're interested, email me at jepling@microsoft.com.

We're working on the design for autoscaling self-hosted agents. We call it "Bring your own subscription". Ya, it needs a better name. You can read more about our thoughts here. https://github.com/Microsoft/azure-pipelines-agent/blob/mast...

We're adding CD/release features to YAML pipelines right now. I'd like to chat about the features you want to see first since we're prioritizing.

Docker layering caching is something we're discussing. There are some trade-offs with it vs. other approaches.

You can use secure files. https://docs.microsoft.com/en-us/azure/devops/pipelines/libr...

I'm a Product Manager on the Azure Pipelines team and happy to answer any questions.

I'm a Microsoft employee on the Git team.

Microsoft is moving to Git and we use Team Services / TFS as our Git server for all private repositories. GitHub is only used for OSS since that's where the OSS community is.

I'm a Microsoft employee on the Git team. We do have a distributed, caching, incremental build system and a distributed test system. Right now, they're completely internal - like Google. They're called CloudBuild and CloudTest. They're very fast and no one thinks twice about kicking off a build.