Live data from Hacker News

Viewing profile — chrisrpatterson

chrisrpatterson

HN member
Joined
Sun, Jan 17, 2016, 3:51 PM UTC
HN karma
37
Public activity
10 items

About chrisrpatterson

No profile information was provided.

Recent public activity

  1. comment
    Comment #28538587

    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. comment
    Comment #24980407

    https://github.blog/changelog/2020-10-01-github-actions-depr...

  3. comment
    Comment #23195033

    self-hosted runners can be deployed for an org as well https://github.blog/changelog/2020-04-22-github-actions-orga... .

  4. comment
    Comment #20647717

    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 fai…

  5. comment
    Comment #18997762

    @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 th…

  6. comment
    Comment #18985419

    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. comment
    Comment #17953434

    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. comment
    Comment #17952847

    [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. Thos…

  9. comment
    Comment #17952800

    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 …

  10. comment
    Comment #17952713

    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).