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

Feature: JDK 17 Upgrade Support Series - Jenkins Images #406

Closed
3 tasks done
jacksondelametter opened this issue Oct 10, 2024 · 1 comment
Closed
3 tasks done

Feature: JDK 17 Upgrade Support Series - Jenkins Images #406

jacksondelametter opened this issue Oct 10, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@jacksondelametter
Copy link
Contributor

jacksondelametter commented Oct 10, 2024

Description

In #133 we modified the build-parent to use JDK 17. When building aiSSEMBLE with the updated build-parent, some modules do not build successfully. This is a series of ticket to fix broken modules and verify they work correctly. This issue will focus on the Jenkins image functionality.

DOD

  • Modify the aiSSEMBLE Jenkins agent and controller to use JDK 17
  • Verify a successful build with the modification
  • Verify Jenkins can be accessed as well as the agent is using JDK 17

Test Steps

  • Clone the aiSSEMBLE repository https://github.com/boozallen/aissemble.
  • In the project's root directory, execute the following and verify successful builds
    • mvn clean install -pl :aissemble-jenkins -amd Note: Make sure the aissemble-jenkins-controller and aissemble-jenkins-agent images actually build.
    • mvn clean install -pl :aissemble-infrastructure-chart
  • Execute helm install jenkins extensions/extensions-helm/aissemble-infrastructure-chart/ --values extensions/extensions-helm/aissemble-infrastructure-chart/values.yaml --set argo-cd.enabled=false,ingress-nginx.enabled=false,jenkins.controller.image.pullPolicy="IfNotPresent",jenkins.controller.serviceType=LoadBalancer. This may take a few seconds for the Jenkins pod to initialize.
  • In a browser, access Jenkins with the following URL http://localhost:8080/
    • Execute kubectl exec --namespace jenkins -it svc/jenkins -c jenkins -- /bin/cat /run/secrets/additional/chart-admin-password && echo to get the user admin password
    • Login with the admin username and password generated from the previous step
  • Execute docker run ghcr.io/boozallen/aissemble-jenkins-agent:1.10.0-SNAPSHOT
  • In another terminal, execute docker ps | grep jenkins-agent, take note of the container ID
  • Execute docker exec -it CONTAINER_ID bash
    • In the jenkins-agent container, execute java --version. Verify the version is Java 17.
    • Execute exit to exit out of the container
  • Execute docker stop CONTAINER_ID
  • Execute helm uninstall jenkins
@jacksondelametter jacksondelametter added the enhancement New feature or request label Oct 10, 2024
@jacksondelametter jacksondelametter added this to the 1.10.0 milestone Oct 10, 2024
@jacksondelametter jacksondelametter self-assigned this Oct 10, 2024
jacksondelametter added a commit that referenced this issue Oct 15, 2024
@cwoods-cpointe
Copy link
Contributor

Final test passed. Jenkins comes up and exec shows java 17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants