Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add build agent for Node.js 18 (master) #795

Merged
merged 6 commits into from
Feb 13, 2023
Merged

Conversation

cschweikert
Copy link
Member

  • add jenkins-agent for Node.js 18
  • update chrome to 100.0.4896.127 (latest)
  • update documentation

Fixes #794

Tasks:

  • Updated documentation in docs/modules/... directory

@cschweikert
Copy link
Member Author

Hm, builds are failing. Doesn't find all of the dependencies yet. Maybe because Node.js 18 was released only a week ago. I'll try again later and keep you posted.

FROM opendevstackorg/ods-jenkins-agent-base-ubi8:latest

# Labels consumed by Red Hat build service
LABEL com.redhat.component="jenkins-agent-nodejs-18-rhel7-container" \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't it ubi8 instead of rhel7 ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now as I look at this... the labels section definitely needs improvement. Regarding this topic there seems to be #506 for dealing with this on all agents. I would not fix it with this PR.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer to fix it now.

- name: ODS_GIT_REF
required: true
- name: JENKINS_AGENT_DOCKERFILE_PATH
value: Dockerfile.centos7
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we default to ubi8 ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering why we have those two flavors of the Dockerfile in the first place.

@michaelsauter @braisvq1996 Do we still need both?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have both because centos7 was used for Openshift 3 installation and ubi8 for Openshift 4 -> Check config
Better maintain both until we decide to drop Openshift 3 completely.

.github/workflows/continuous-integration-workflow.yml Outdated Show resolved Hide resolved
@BraisVQ
Copy link
Contributor

BraisVQ commented Jun 10, 2022

Hi @cschweikert @tbugfinder -> nodesource
It seems nodejs18 is not working with Centos 7 and Rhel7

@cschweikert
Copy link
Member Author

@braisvq1996 good point. Does anything speak against moving on to Centos/RHEL 8? Like already mentioned in one of the discussions above I have no clue about the implications of this switch (e.g. just for the nodejs18 thingy). If it is fine, I can also try that out for now.

@BraisVQ
Copy link
Contributor

BraisVQ commented Jun 10, 2022

Switching to Centos8 and/or Rhel8 is a big change.
Right now if we do it the ODSBox we have will not work but this is something we would need to do sooner or later
image

@michaelsauter
Copy link
Member

@braisvq1996 I think this just confirms that you'll need to investigate an alternative to the current ODS Box. Maintaining CentOS/RHEL7 base images will be a hassle more and more, plus the box is OpenShift 3.11 only so won't give you reliable results. The box should not block the uptake of Node 18 I believe.

@BraisVQ
Copy link
Contributor

BraisVQ commented Jun 13, 2022

@michaelsauter you have your reason, the box is using OKD3, and this does not "help" for Openshift 4 tests....
Either way I would not break the box "on purpose" if we can avoid it

@tbugfinder
Copy link
Contributor

As per my understanding nodejs project will not build CentOS7 binaries.
nodejs/node#43246

So for CentOS7 we could compile proper GLIBC version 2.27 within the Image and see if that would work with the RHEL8 binary.

In regards to the ubi8 image, do you want to wait for RHEL providing nodejs18 repo (sounds like Sept/Oct timeframe) or use the installer of the CentOS7 Dockerfile which would already be available.

@tbugfinder
Copy link
Contributor

@braisvq1996 @cschweikert
NodeJS 18 + ubi8 built successfully.

IMHO, CentOS7 support has to dropped here to move forward.

@BraisVQ
Copy link
Contributor

BraisVQ commented Feb 13, 2023

@tbugfinder @cschweikert centos agents have been removed so if the conficts get resolved we could merge this into master

@BraisVQ
Copy link
Contributor

BraisVQ commented Feb 13, 2023

I have already removed centos from this pr so if there is anything left to update as it has been quite some time since its creation we can do it and merge it

Copy link
Contributor

@tbugfinder tbugfinder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@cschweikert
Copy link
Member Author

@braisvq1996 thanks finishing this one ❤️

@cschweikert cschweikert merged commit 6984918 into master Feb 13, 2023
@cschweikert cschweikert deleted the add-nodejs-18-agent branch February 13, 2023 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provide build agent for Node.js 18
4 participants