chrisrpatterson

6 ms·

1. 1.▲
   by chrisrpatterson 5y ago

   Yes a malicious fork will NOT be able to get a JWT just like they are not able to get any other secrets or privledges to the repo.
2. 2.▲
   by chrisrpatterson 6y ago

   https://github.blog/changelog/2020-10-01-github-actions-depr...
3. 3.▲
   by chrisrpatterson 6y ago

   self-hosted runners can be deployed for an org as well https://github.blog/changelog/2020-04-22-github-actions-orga... .
4. 4.▲
   by chrisrpatterson 7y ago

   Hi, GitHub Actions product manager here. Thanks for your interest in GitHub Actions. You can set a property `continue-on-error: true` for each step and the runner will ignore a failed result and continue the workflow. For more details on w
5. 5.▲
   by chrisrpatterson 8y ago

   @nbevans could you provide a few more details here on the agent and where it is hosted? The agent itself does not rely on the IIS worker pool and we are not aware of any bugs in this area. If we have some we would love to get them address
6. 6.▲
   by chrisrpatterson 8y ago

   We really hate to hear you are having such a bad experience. The engineering manager has reached out on Twitter and included me. I would love to see what I can do to help
7. 7.▲
   by chrisrpatterson 8y ago

   We fully support building those on our VS 2017 vm image. Building those inside of a container I do not believe is currently supported by Windows.
8. 8.▲
   by chrisrpatterson 8y ago

   [PM on the Azure Pipelines team] The primary focus here is making the individual services easier for teams to adopt. Azure pipelines for CI/CD, Azure Boards for planning, etc. Those services support the overall goal of improving your
9. 9.▲
   by chrisrpatterson 8y ago

   Hi avsm, We absolutely support building Windows Docker Images. At the moment you are limited to either Server 2016 or Server 1803 based images but that is something we are working on enhancing. I would be interested in understanding your
10. 10.▲
    by chrisrpatterson 8y ago

    Azure Pipelines has all of the same features on VSTS Build and Release but adds an option for defining your CI pipeline in YAML (this feature was previously in preview).