EFI: Move to GitHub actions

[sheplu]

Motivation

GitHub Action is a well know CI/CD tool that is also the main tools on Github. Using said actions would allow us to reduce the number of external dependencies while also using all the feature from github (and the integration).
If possible all other solutions (like jenkins or saas) should be remove and rewritten to leverage github action

Expectation

Only rely on github action for all ci/cd operation, without using external SaaS solution with different configuration

Implementation

Go through all projects and all orgs, removing and updation ci/cd implementation

Status

Part: Technical
Status:

• jshttp
• pillarjs
• expressjs

Draft

GitHub Actions are a great tool widely used by all Open Source Projects. This is still relatively new (a few years already) but allows all projects to not have to switch between different technologies and providers for the CI/CD part.

[UlisesGascon]

Here is a list of projects using Travis across the organization:

• https://github.com/pillarjs/encodeurl
• https://github.com/pillarjs/resolve-path
• https://github.com/pillarjs/extend-proto
• https://github.com/pillarjs/qs-strict
• https://github.com/pillarjs/routington
• https://github.com/pillarjs/templation
• https://github.com/pillarjs/ssl-redirect
• https://github.com/jshttp/basic-auth
• https://github.com/jshttp/vary
• https://github.com/jshttp/on-headers
• https://github.com/jshttp/methods
• https://github.com/jshttp/media-typer
• https://github.com/jshttp/spdy-push
• https://github.com/jshttp/etag
• https://github.com/jshttp/http-utils
• https://github.com/expressjs/method-override
• https://github.com/expressjs/morgan
• https://github.com/expressjs/multer
• https://github.com/expressjs/serve-index
• https://github.com/expressjs/serve-favicon
• https://github.com/expressjs/response-time
• https://github.com/expressjs/connect-multiparty
• https://github.com/expressjs/timeout
• https://github.com/expressjs/flash
• https://github.com/expressjs/express-paginate
• https://github.com/expressjs/errorhandler
• https://github.com/expressjs/api-error-handler
• https://github.com/expressjs/express-expose

Some of them have high chance to be just deprecated, based on #134. Note that api-error-handler is archived but not deprecated in NPM

[kibertoad]

@wesleytodd I can pickup some of this work, if it's already time for it

[wesleytodd]

This is like the third issue I have seen with a list of repos which need something. I think we should make a spreadsheet with all of these as rows and each column being "needs X to be done" so we can track it centrally.

@kibertoad Can we do a central shared workflow for this? So that we can just reference that and have the bulk of the stuff in one place? Other than that I think yeah lets go on it!

[sheplu]

@wesleytodd yep this would be the plan, to have some repo like a "express-actions" (or other name) that would only provide github action (step / workflows) and this would be imported everywhere. This would include

• install
• run test (all of them, maybe split them on multiple job for parallelism)
• get all reports / compute reports (other things)
• publish a package

By doing that we should be able to reduce all the workflow to only importing from a central repo, having a lot less maintenance.
As they are not harmonized right now, do we want to target and have that only for a new major release of all packages?

CF this issue #182

[wesleytodd]

Ship IT!

[kibertoad]

@wesleytodd Can I get permissions to create repos for the org?

[sheplu]

@kibertoad jumping in my train and creating that + access

Are we good with the name "github-action" ? I guess we can rename that later on too

[wesleytodd]

Ah, I think that is an admin thing. We should probably document the process for that, but maybe for now lets just use the .github repo? https://github.com/expressjs/.github/

[wesleytodd]

Before we make repos we should have a bit of a cool off to make sure folks have time to reply.

[kibertoad]

Let's start with .github and see if we'll need an extra repo as we go

[bjohansebas]

We already use GitHub Actions in the vast majority of our repos, and I see that the main point here is having reusable GitHub Actions, but that’s already being tracked in #182. So I’m going to close this. If anything is missing, feel free to open an issue in the appropriate repo.