[FOLIO-3948] Fix pipelines for new modules and libs Created: 22/Dec/23  Updated: 10/Jan/24  Resolved: 10/Jan/24

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Maksym Sinichenkom Assignee: Unassigned
Resolution: Done Votes: 0
Labels: reviewed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Requires
is required by MODLOGINKC-1 mod-login-keycloak - token endpoint r... Closed
Sprint: DevOps Requests
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

The new modules and libs were added recently, but there are some problems with CI.
List of modules:

libs

backend modules - please check Jenkinsfiles 

If any questions, please contact Maksym Sinichenkom 
cc: Yauhen Vavilkin



 Comments   
Comment by David Crossley [ 10/Jan/24 ]

Your Jenkinsfiles are totally wrong.

You need to follow the document https://dev.folio.org/guidelines/create-new-repo/

Follow the links. There is even a document explicitly devoted to Jenkinsfile.

 

Comment by Maksym Sinichenkom [ 10/Jan/24 ]

Hello David Crossley. Dev team created PR with Jenkinsfile changes. 

buildMvn {
  publishModDescriptor = 'no'
  mvnDeploy = 'yes'
  buildNode = 'jenkins-agent-java17'
} 

But checks for this PR also failed.

Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar (default-cli) on project folio-java-checkstyle: Unable to load component class org.sonar.scanner.scan.filesystem.InputComponentStore: Unable to load component interface org.sonar.scanner.scan.branch.BranchConfiguration: Could not find a default branch for project with key 'org.folio:folio-java-checkstyle'. Make sure project exists. 

 Should these changes be made directly to the master branch? Or do we need to delete the repository and create it again with the correct Jenkinsfile?

Comment by David Crossley [ 10/Jan/24 ]

Yes as the documentation says: Jenkinsfile direct to master.

Comment by Maksym Sinichenkom [ 10/Jan/24 ]

Thanks! Fix Jenkinsfile in the master branch works. All libs pushed to nexus successfully.
But sometimes a problem with starting Keycloak test  container appears: https://jenkins-aws.indexdata.com/blue/organizations/jenkins/folio-org%2Fmod-users-keycloak/detail/master/9/pipeline 

11:08:30 INFO  GenericContainer     Creating container for image: quay.io/keycloak/keycloak:23.0.3
11:08:30 INFO  RegistryAuthLocator  Failure when attempting to lookup auth config. Please ignore if you don't have images in an authenticated registry. Details: (dockerImageName: quay.io/keycloak/keycloak:23.0.3, configFile: /home/jenkins/.docker/config.json, configEnv: DOCKER_AUTH_CONFIG). Falling back to docker-java default behaviour. Exception message: Status 404: No config supplied. Checked in order: /home/jenkins/.docker/config.json (file not found), DOCKER_AUTH_CONFIG (not set)
11:08:30 INFO  GenericContainer     Container quay.io/keycloak/keycloak:23.0.3 is starting: 721a655a9a03d2bfb58e9aa758e6043b3d0b50d265914a76a6db92f70dd88254
11:08:31 INFO  HttpWaitStrategy     /hungry_goldwasser: Waiting for 120 seconds for URL: http://172.17.0.1:51847 (where port 51847 maps to container port 8080)
11:08:31 INFO  Slf4jLogConsumer     STDOUT: [0.003s][warning][os,thread] Failed to start thread "GC Thread#0" - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
11:08:31 INFO  Slf4jLogConsumer     STDOUT: #
11:08:31 INFO  Slf4jLogConsumer     STDOUT: # There is insufficient memory for the Java Runtime Environment to continue.
11:08:31 INFO  Slf4jLogConsumer     STDOUT: # Cannot create worker GC thread. Out of system resources.
11:08:31 INFO  Slf4jLogConsumer     STDOUT: # An error report file with more information is saved as:
11:08:31 INFO  Slf4jLogConsumer     STDOUT: # /tmp/hs_err_pid87.log
11:10:31 ERROR GenericContainer     Could not start container 

I think it can be addressed in a separate ticket. 

Comment by David Crossley [ 10/Jan/24 ]

I am closing this ticket.

Please encourage all of your teams to follow the documentation in the future.

Generated at Thu Feb 08 23:31:57 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.