Page History

...

• Oct 21st:
  • Configure admin section of GE
    • Access control: LDAP and email server config will happen post-meeting
    • Access control: Setting up temporary local users for Drew and Gavin will happen post-meeting
    • Access control: Setting up local users for CI-Jenkins and CI-GitHub-Actions will happen post-meeting
  • RDS setup still in progress
• Oct 27th:
  • Gavin was OOO and not able to attend the meeting 
  • Setup of certificate, external DB, LDAP, and email server config in admin section still in progress
  • Question from Etienne:
    • Are the Jenkins servers used by the ASF on a recent version?
• November 3rd:
  • Gavin, Drew, and Rus were in attendance
  • LDAP Bind account has been created, LDAP can now be set up in coming week
    • LDAP has been connected, with no search filter.
    • LDAP users were granted build scan view , build scan publish  and build cache read
  • Additionally, Email will be handled by the LDAP account (once we verify that the user in question has SMTP auth rights)
  • SSL, RDS and S3 have all been set up
• November 10th:
  • Gavin, Drew, Rus, and Etienne were in attendance
  • Discussed how to configure the infrastructute-jenkins project to verify successful publication of build scans
• November 17th:
  • Gavin and Etienne were in attendance
  • Build scan publishing for local build on developer machine confirmed to work by both Gavin and Etienne
  • Build scan publishing for CI build on GitHub Actions confirmed to work by Gavin
  • Next steps:
    • Log in as system user, delete local user for Gavin, Gavin to re-login, and user will be taken from LDAP, then add admin permissions
    • Drew to do the same (local user already deleted by Gavin today)
    • Set up Jenkins job for infrastructure-jenkins project and inject access token of the dedicated, local Jenkins user created already in GE
    • Enable Jenkins Gradle plugin on the Jenkins controller owned by the infrastructure team
    • Have a call with the GE team to configure the Jenkins Gradle plugin to auto-configure the builds with publishing of a build scan
    • Wait for feedback from Greg on the agreement before tackling rollout of the build scan capturing for all CI builds
• November 24th:
  • Gavin, Rus, and Etienne were in attendance
  • Agreement has been signed between Apache (Greg) and Gradle (Rolf)
  • All build scan publishing experiments for GitHub Actions, Jenkins, and Buildbot have been completed successfully
  • Progress on installation automation via Terraform  has been paused while waiting for the agreement, but will be picked up again by Gavin soon
  • Next step:
    • Verify that the GE-enablement in Jenkins (via Gradle Jenkins plugin) works on the Infra controller
    • Decide on what controller to active the GE enablement next
    • Discuss creation of a GE/Apache convention plugin (Gradle) and extension (Maven) to centralize the build-side configuration of GE 
• December 8th:
  • Gavin, Drew, and Etienne were in attendance
  • Next step:
    • ASF to reach out to Apache Beam project and confirm they are ok/happy to get GE build scans for all their CI builds
    • Once ok has been received, enable GE injection on Apache Beam Jenkins controller (similar to what has been done for the Infra team Jenkins controller)
    • Gradle to provide PR to enable GE via configuration in the build, such that they get build scans not only for CI builds but also for all local builds
• December 15th:
  • Drew and Etienne were in attendance
  • Etienne indicated that they may have solved the workspace id problem
    • Root cause fix: Gradle raised an issue on the Apache RAT plugin because it should ignore the .mvn directory including sub-directories as part of the default excludes
    • Workaround: Gradle will add the missing exclude dynamically, available in the upcoming GE Maven extension 1.16.1 (will be released this Friday)
  • Next Steps:
    • ASF to upgrade to GE 2022.4
      • Upgrade Gradle Enterprise server to the latest version in the k8s cluster
    • ASF to upgrade Jenkins Gradle plugin
      • New version will be released early next week 
      • The new version will ship with GE Maven extension 1.16.1 that fixes the RAT plugin issue regarding default excludes
      • For any Apache project using the RAT plugin, this will no longer lead to build failures related to a missing file header in the workspace id file
    • ASF to reach out to the Apache Beam project maintainers
      • Also mention that Gradle had already optimized their build sometimes in the past, via multiple PRs that all got merged back then
      • Gradle team will re-verify that the Apache Beam Gradle build is fully optimized and create PRs if needed (this and next week)

...