Compare commits

..

5 Commits

Author SHA1 Message Date
Ryan van Zeben
6054417c26 Update ownership.yaml 2023-09-15 13:34:15 -04:00
Ryan van Zeben
7260fb7f61 Create ownership.yaml 2023-09-15 13:33:15 -04:00
Ryan van Zeben
0bc3793a68 Create SUPPORT.md 2023-09-15 13:18:30 -04:00
Ryan van Zeben
ab1bc511a8 Update README.md 2023-09-15 13:15:59 -04:00
Ryan van Zeben
0ac3a85234 Add in contributing file 2023-09-15 13:07:14 -04:00
4 changed files with 65 additions and 10 deletions

19
CONTRIBUTING.md Normal file
View File

@@ -0,0 +1,19 @@
# Contributing
## Submitting a pull request
1. Fork and clone the repository
1. Create a new branch: `git checkout -b my-branch-name`
1. Push to your fork and submit a pull request
1. Pat yourself on the back and wait for your pull request to be reviewed and merged
## Tips for working this repository:
> - The repository is huge right now, you don't want to waste your time and disk space to get those unrelated files.
> - Ignore LFS files during initial `git clone` the repo with `GIT_LFS_SKIP_SMUDGE=1 git clone https://mseng@dev.azure.com/mseng/AzureDevOps/_git/CIPlat.Externals`
> - Ignore LFS files during any `git checkout` or `git fetch` operation with `GIT_LFS_SKIP_SMUDGE=1`.
> - You do want the LFS smudge filter to run during `git add` and `git push`, make sure you don't have `GIT_LFS_SKIP_SMUDGE=1` when you run `git add` and `git push`.
> - More `Git-LFS` doc is at https://github.com/git-lfs/git-lfs/tree/main/docs
Thanks! :heart: :heart: :heart:
GitHub Actions Team :octocat:

View File

@@ -1,8 +1,11 @@
# alpine_nodejs
# GitHub Alpine NodeJS
[GitHub Actions Runner](https://github.com/actions/runner/blob/main/src/Misc/externals.sh) download alpine node.js from https://vstsagenttools.blob.core.windows.net/tools/nodejs
[![Actions Status](https://github.com/actions/alpine_nodejs/workflows/Build%20Alpine%20Node.js/badge.svg)](https://github.com/actions/alpine_nodejs/actions)
The [workflow](https://github.com/TingluoHuang/alpine_nodejs/actions/workflows/docker-image.yml) in this repository can compile a partial-static node.js for alpine and create a [GitHub release](https://github.com/TingluoHuang/alpine_nodejs/releases) for it.
The Alpine NodeJS repo houses a redistribution of NodeJS builds that are used within the [GitHub Actions Runner](https://github.com/actions/runner/blob/main/src/Misc/externals.sh).
## Getting Started
The [workflow](https://github.com/actions/alpine_nodejs/actions/workflows/docker-image.yml) in this repository can compile a partial-static node.js for alpine and create a [GitHub release](https://github.com/actions/alpine_nodejs/releases) for it.
- Queue workflow using `workflow_dispatch` trigger and set the `node` version you want to compile as input, ex: `v12.22.7`
![queue workflow](./res/queueWorkflow.png)
@@ -13,10 +16,3 @@ The [workflow](https://github.com/TingluoHuang/alpine_nodejs/actions/workflows/d
- There should be a newly created release that matches the version you want for `node`, and it is able to run on alpine.
![new release](./res/createdRelease.png)
- Once we get [approval](https://github.com/github/open-source-releases/issues/205) to change the current repository from `private` to `public`, then we can consume the release assets directly. In the meantime, you will need to follow [instructions](https://dev.azure.com/mseng/AzureDevOps/_wiki/wikis/AzureDevOps.wiki/4037/How-to-upload-resource-to-vstsagenttools.blob.core.windows.net) to check-in the compiled alpine node.js from the release assets as a `Git-LFS` files to https://dev.azure.com/mseng/AzureDevOps/_git/CIPlat.Externals and get it mirror into https://vstsagenttools.blob.core.windows.net/tools/nodejs
> Tips for working with `CIPlat.Externals` repository:
> - The repository is huge right now, you don't want to waste your time and disk space to get those unrelated files.
> - Ignore LFS files during initial `git clone` the repo with `GIT_LFS_SKIP_SMUDGE=1 git clone https://mseng@dev.azure.com/mseng/AzureDevOps/_git/CIPlat.Externals`
> - Ignore LFS files during any `git checkout` or `git fetch` operation with `GIT_LFS_SKIP_SMUDGE=1`.
> - You do want the LFS smudge filter to run during `git add` and `git push`, make sure you don't have `GIT_LFS_SKIP_SMUDGE=1` when you run `git add` and `git push`.
> - More `Git-LFS` doc is at https://github.com/git-lfs/git-lfs/tree/main/docs

14
SUPPORT.md Normal file
View File

@@ -0,0 +1,14 @@
# Support
## How to file issues and get help
This project uses GitHub issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
For help or questions about using this project, please check the [discussions](https://github.com/actions/alpine_nodejs/discussions)
`actions/alpine_nodejs` is under active development and maintained by GitHub staff **AND THE COMMUNITY**. We will do our best to respond to support, feature requests, and community questions in a timely manner.
## GitHub Support Policy
Support for this project is limited to the resources listed above.

26
ownership.yaml Normal file
View File

@@ -0,0 +1,26 @@
---
version: 1
ownership:
- name: actions-alpine-nodejs
long_name: Actions Alpine NodeJS
description: Alpine NodeJS redeployment for actions runner
tier: 2
kind: artifact
team: github/c2c-actions-runtime
team_slack: actions-runners
repo: https://github.com/actions/alpine_nodejs
maintainer: benwells
exec_sponsor: isethi
qos: maintenance
sev1:
pagerduty: https://github.pagerduty.com/escalation_policies#PT5KQ9D
tta: '1 business days'
sev2:
slack: actions-runtime
issue: https://github.com/actions/alpine_nodejs/issues
tta: '2 business days'
sev3:
slack: actions
issue: https://github.com/actions/alpine_nodejs/issues
tta: '2 weeks'
dependencies: [ ]