Repository navigation
What to use for CI #62
Description
Postject was using CircleCI under the Postman account and it got disconnected after the repo got transferred to the nodejs org. Now that CI doesn't work anymore, it's time to reconsider what we should use for CI:
- use a CircleCI account from Node.js on the free tier
- switch to Node.js' Jenkins CI
- use GitHub Actions
- something else
@nodejs/single-executable wdyt?
Activity
jviotti commentedon Oct 28, 2022
One of the eventual goals of Postject is the support AIX's XCOFF. Given that, it'd be cool if we can use a CI system that supports AIX. How does Node.js core do it? If there is AIX under Jenkins, is there any chance we could reuse that?
Otherwise, the simplest approach is probably GitHub Actions?
mhdawson commentedon Oct 28, 2022
Since this is under the Node.js org I suggest we use Node.js' Jenkins CI.
That is where we ensure we can test on all Node.js supported platform/versions. I can help set up a jenkins job. Ideally it would be as easy as clone this repo, then run make test or some equivalent, although I know it is often more complicated than that.
mhdawson commentedon Oct 28, 2022
And to answer @jviotti, yes we have instances of all supported platforms including AIX :)
jviotti commentedon Oct 28, 2022
Sounds exciting!
RaisinTen commentedon Oct 31, 2022
Thanks, that sounds great! We would need a way to run https://github.com/nodejs/postject/blob/0d7aab19f2472f159c08802e67bfb4d64611ca1d/.circleci/config.yml on Jenkins.
jviotti commentedon Oct 31, 2022
@RaisinTen Jenkins won't be able to run the CircleCI config, of course. We would need to get rid of that
.circlecifolder, refactor these steps into i.e. shell scripts, and then configure Jenkins to run them instead.Add Jenkins CI job for Postject
jenkins: add postject pipeline
RaisinTen commentedon Dec 14, 2022
@tony-go and I spent some time today to come up with a jenkins pipeline to unblock postject's development: nodejs/build#3114