use Self hosted runners in github workflow action

once you migrated your repos into github. you might want to set up some workflow actions whenever there is something changed on the github repo. In the actions, you might try invoking some APIs which is not public faced but internal private ones to do some checkup such as checkmarx scan. If you use github default runners, which is ubuntu-latest, you might encounter errors like could not resolve host. 0curl: (6) Could not resolve host: your.internal.host.com Use self-hosted runners here you a

Post, Code and Quiet Time. use Self hosted runners in github workflow action By Errong Leng – 29 Apr 2024 – View online → Photo by Annie Spratt / Unsplash once you migrated your repos into github. you might want to set up some workflow actions whenever there is something changed on the github repo. In the actions, you might try invoking some APIs which is not public faced but internal private ones to do some checkup such as checkmarx scan. If you use github default runners, which is ubuntu-latest, you might encounter errors like could not resolve host. 0curl: (6) Could not resolve host: your.internal.host.com Use self-hosted runners here you are the solution. You can add a self-hosted runner to a repository, an organization, or an enterprise. If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place. For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "About self-hosted runners." Warning: We recommend that you only use self-hosted runners with private repositories. This is because forks of your public repository can potentially run dangerous code on your self-hosted runner machine by creating a pull request that executes the code in a workflow. For more information, see "About self-hosted runners." You can set up automation to scale the number of self-hosted runners. For more information, see "Autoscaling with self-hosted runners." You can register ephemeral runners that perform a single job before the registration is cleaned up by using just-in-time runner registration. For more information, see "Security hardening for GitHub Actions." Adding self-hosted runners - GitHub Docs You can add a self-hosted runner to a repository, an organization, or an enterprise. GitHub Docs Post, Code and Quiet Time. © 2024 – Unsubscribe

get the github.event json and branch name in github Actions workflow scripts

Assuming you want to run checkmarx scan on any push event to make sure the codes committed do not have major secruity concerns. You can set up a workflow like below: name: Trigger Checkmarx Scan Workflow on: push: branches-ignore: - main - master - develop jobs: checkmarxscan: runs-on: linux steps: - name: Trigger Checkmarx Scan env: checkmarx_scan_webhook : yourwebhookjenkinsjoburl=&checkmarxProjectId= project_name: yourche

Post, Code and Quiet Time. get the github.event json and branch name in github Actions workflow scripts By Errong Leng – 29 Apr 2024 – View online → Photo by Evie S. / Unsplash Assuming you want to run checkmarx scan on any push event to make sure the codes committed do not have major secruity concerns. You can set up a workflow like below: name: Trigger Checkmarx Scan Workflow on: push: branches-ignore: - main - master - develop jobs: checkmarxscan: runs-on: linux steps: - name: Trigger Checkmarx Scan env: checkmarx_scan_webhook : yourwebhookjenkinsjoburl=&checkmarxProjectId= project_name: yourcheckmarxprojectname GITHUB_EVENT: ${{ toJson(github.event) }} BRANCH_NAME: ${{ github.head_ref || github.ref_name }} run: | curl -X POST "${checkmarx_scan_webhook}${project_name}&branchName=$BRANCH_NAME" -H 'Content-Type: application/json' -d "$GITHUB_EVENT" use branches-ignore I used branches-ignore to let this action will be triggered on any branch except the branches ignored. json github.event first set github.event to env. GITHUB_EVENT: ${{ toJson(github.event) }} and then use it in the run command. -d "$GITHUB_EVENT" make sure you use double quotes " and $ to read it, otherwise you will get error. get branch name by default, the github.event does not include the branch name. but you can use below script to get the branch name and set it as env. BRANCH_NAME: ${{ github.head_ref || github.ref_name }} And then pass it as query parameter in the webhook url. &branchName=$BRANCH_NAME" jenkins job as a webhook from the curl command, it will send out the github.event as a json body and branchName as query. The json body and query will be resolved as variables in the runtime of the jenkins job and you can use them directly in the jenkins scripts. After the workflow action is triggered successfully, it will print out the resolved variables as well. Check the resolvedVariables in the console log of the action. {"jobs":{"CheckMarxScan-FromWebhook":{"regexpFilterExpression":"","triggered":true,"resolvedVariables":{"branchName":"workflow/checkmarx-scan-onpush","branchName_0":"workflow/checkmarx-scan-onpush","checkmarxProjectId":"xxx","checkmarxProjectId_0":"xxxxxx","commits":"[{\"author\":{\"email\":\"xx@xx\",\"name\":\"Leng, Errong\",\"username\":\"Errong-Leng\"},\"committer\":{\"email\":\"noreply@github.com\",\"name\":\"GitHub\",\"username\":\"web-flow\"},\"distinct\":true,\"id\":\"e4b472116628a53f5b48caf10b2590d6e2602c7a\",\"message\":\"change job name\",\"timestamp\":\"2024-04-26T16:44:46-07:00\",\"tree_id\":\"d5e94f1955254c2612d37aeb6e72fd5e3ddc2efb\",\"ur ... This will help you set up the jenkins job scripts as well. Happy Debugging and Codding! Post, Code and Quiet Time. © 2024 – Unsubscribe

git fetch error in jenkins pipeline, use skipDefaultCheckout and dir directive for the fix

Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress git@github.com:xxx.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: ERROR: Repository not found. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Double confirm the repo url and credentials used for git command you might see the above errors sometimes in your Jenkins pipeline. the error message might b

Post, Code and Quiet Time. git fetch error in jenkins pipeline, use skipDefaultCheckout and dir directive for the fix By Errong Leng – 29 Apr 2024 – View online → Photo by Roman Synkevych / Unsplash Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress git@github.com:xxx.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: ERROR: Repository not found. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Double confirm the repo url and credentials used for git command you might see the above errors sometimes in your Jenkins pipeline. the error message might be right in case you do not put the right repository url or you don't have the right credential to access it. Mixed .git under the same working repo if you 100% sure, you have the right url and using the right credentials, but you still see such errors. Then check in another way. Make sure the working directory is empty before you checkout a new repo. In case there is already a .git folder before you checkout and the repo was for a different url, you might see the above error as well. Jenkins pipeline skip default checkout and use dir change working directory skipDefaultCheckout Skip checking out code from source control by default in the agent directive. For example: options { skipDefaultCheckout() } if the pipeline scripts is coming from a repo and the repo going to be in the pipelien is another one, you might encouter the above error as well. Since by default, the pipeline scripts repo will be checkout first. and then checkout the target repo to run build or run checkmarx scan if used as a webhook. We can use the skipDefaultCheckout option to avoid these issue. pipeline { agent { label "yourlabel" } options { skipDefaultCheckout(true) } stages { And further more, we can leverage ```dir``` directive as well, to do the checkout in a separate working folder. so that even the target repo was checkout in the working space, it will won't affect the next job. def workspaceDir = "${BUILD_ID}" ... stage("SCM Checkout") { steps { dir(workspaceDir) { git credentialsId: "your_credential", url: "${repository_ssh_url}", branch: "${branchName}" } } } The ${BUILD_ID} is unique for the builds of the same jenkins job. so use it as workspace directory will make sure the code will be checkout in a sole folder even these builds running parallelly. Post, Code and Quiet Time. © 2024 – Unsubscribe

react native run on android Caused by: java.util.concurrent.ExecutionException: com.android.tools.r8.internal.Jj: java.lang.NullPointerException: Cannot invoke "String.length()" because "" is null

Today I would like to continue my react native app development work. After I run npm start , I got below quite strange error. I build the app via android studio, no build issue. Quite strange problem. Caused by: java.util.concurrent.ExecutionException: com.android.tools.r8.internal.Jj: java.lang.NullPointerException: Cannot invoke "String.length()" because "" is null Caused by: com.android.builder.dexing.DexArchiveBuilderException: Error while dexing. at com.android.builder.dexing.D8De

Post, Code and Quiet Time. react native run on android Caused by: java.util.concurrent.ExecutionException: com.android.tools.r8.internal.Jj: java.lang.NullPointerException: Cannot invoke "String.length()" because "" is null By Errong Leng – 23 Apr 2024 – View online → Photo by Libby Penner / Unsplash Today I would like to continue my react native app development work. After I run npm start , I got below quite strange error. I build the app via android studio, no build issue. Quite strange problem. Caused by: java.util.concurrent.ExecutionException: com.android.tools.r8.internal.Jj: java.lang.NullPointerException: Cannot invoke "String.length()" because "" is null Caused by: com.android.builder.dexing.DexArchiveBuilderException: Error while dexing. at com.android.builder.dexing.D8DexArchiveBuilder.getExceptionToRethrow(D8DexArchiveBuilder.java:140) at com.android.builder.dexing.D8DexArchiveBuilder.convert(D8DexArchiveBuilder.java:117) at com.android.build.gradle.internal.dexing.DexWorkActionKt.process(DexWorkAction.kt:175) ... 39 more Caused by: com.android.tools.r8.CompilationFailedException: Compilation failed to complete, origin: /Users/qingyirongrong/Work/coca/coca/android/app/build/intermediates/javac/debug/classes/com/lengerrong/coca/ads/AppOpenAdManager$2.class at Version.fakeStackEntry(Version_3.3.83.java:0) at com.android.tools.r8.internal.Hj.a(R8_3.3.83_3e328a3bbd0c840823c96123eb0f6192f0adf17b30ae46f695be39af0bc3505e:75) at com.android.tools.r8.internal.Hj.a(R8_3.3.83_3e328a3bbd0c840823c96123eb0f6192f0adf17b30ae46f695be39af0bc3505e:28) at com.android.tools.r8.internal.Hj.a(R8_3.3.83_3e328a3bbd0c840823c96123eb0f6192f0adf17b30ae46f695be39af0bc3505e:27) at com.android.tools.r8.internal.Hj.b(R8_3.3.83_3e328a3bbd0c840823c96123eb0f6192f0adf17b30ae46f695be39af0bc3505e:2) at com.android.tools.r8.D8.run(R8_3.3.83_3e328a3bbd0c840823c96123eb0f6192f0adf17b30ae46f695be39af0bc3505e:11) at com.android.builder.dexing.D8DexArchiveBuilder.convert(D8DexArchiveBuilder.java:115) ... 40 more Caused by: java.lang.NullPointerException FAILURE: Build completed with 2 failures. 1: Task failed with an exception. ----------- * What went wrong: Execution failed for task ':app:dexBuilderDebug'. > There were multiple failures while executing work items > A failure occurred while executing com.android.build.gradle.internal.dexing.DexWorkAction > Failed to process: /Users/qingyirongrong/Work/coca/coca/android/app/build/intermediates/javac/debug/classes > A failure occurred while executing com.android.build.gradle.internal.dexing.DexWorkAction > Failed to process: /Users/qingyirongrong/Work/coca/coca/android/app/build/intermediates/javac/debug/classes > A failure occurred while executing com.android.build.gradle.internal.dexing.DexWorkAction > Failed to process: /Users/qingyirongrong/Work/coca/coca/android/app/build/intermediates/javac/debug/classes > A failure occurred while executing com.android.build.gradle.internal.dexing.DexWorkAction > Failed to process: /Users/qingyirongrong/Work/coca/coca/android/app/build/intermediates/javac/debug/classes * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. ============================================================================== 2: Task failed with an exception. ----------- * What went wrong: java.lang.StackOverflowError (no error message) * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. ============================================================================== * Get more help at https://help.gradle.org BUILD FAILED in 6s at makeError (/Users/qingyirongrong/Work/coca/coca/node_modules/execa/index.js:174:9) at /Users/qingyirongrong/Work/coca/coca/node_modules/execa/index.js:278:16 at processTicksAndRejections (node:internal/process/task_queues:96:5) at async runOnAllDevices (/Users/qingyirongrong/Work/coca/coca/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:82:7) at async Command.handleAction (/Users/qingyirongrong/Work/coca/coca/node_modules/@react-native-community/cli/build/index.js:108:9) info Run CLI with --verbose flag for more details. I realized I encounter the problems using higher JDK versions. My laptop OS upgraded, and the java version is now using JDK 21. java -version openjdk version "21" 2023-09-19 OpenJDK Runtime Environment Zulu21.28+85-CA (build 21+35) OpenJDK 64-Bit Server VM Zulu21.28+85-CA (build 21+35, mixed mode, sharing) If you have already installed JDK on your system, we recommend JDK 17. You may encounter problems using higher JDK versions. Setting up the development environment · React Native This page will help you install and build your first React Native app. React Native Solution: Downgrade JDK to 17 brew tap homebrew/cask-versions brew install --cask zulu17 # Get path to where cask was installed to double-click installer brew info --cask zulu17 or via sdkman sdk install java 17.0.1-zulu sdk use java 17.0.1-zulu check java version again. java -version openjdk version "17.0.1" 2021-10-19 LTS OpenJDK Runtime Environment Zulu17.30+15-CA (build 17.0.1+12-LTS) OpenJDK 64-Bit Server VM Zulu17.30+15-CA (build 17.0.1+12-LTS, mixed mode, sharing) Happy Coding again with my reactive app > Task :app:installDebug Installing APK 'app-debug.apk' on 'Pixel_XL_API_31(AVD) - 12' for :app:debug Installed on 1 device. w: Detected multiple Kotlin daemon sessions at build/kotlin/sessions Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings BUILD SUCCESSFUL in 45s 160 actionable tasks: 51 executed, 109 up-to-date info Connecting to the development server... 8081 info Starting the app on "emulator-5554"... Starting: Intent { cmp=com.lengerrong.coca/.MainActivity } BUNDLE ./index.js LOG Running "Coca" with {"initialProps":{"launchAdStatus":"AdImpression"},"rootTag":11} Post, Code and Quiet Time. © 2024 – Unsubscribe

Don't Forget to Update Spring Cloud Version When Upgrading Spring Cloud Gateway

Hey everyone, Today, I'd like to share a quick tip for those of you who are upgrading Spring Cloud Gateway in your projects. It's important to remember that when you upgrade Spring Cloud Gateway, you also need to update the Spring Cloud version to ensure compatibility. Here's why: Spring Cloud Gateway relies on specific features and dependencies provided by Spring Cloud. If you upgrade Spring Cloud Gateway without updating the Spring Cloud version, you may encounter compatibility issues and y

Post, Code and Quiet Time. Don't Forget to Update Spring Cloud Version When Upgrading Spring Cloud Gateway By Errong Leng – 19 Apr 2024 – View online → Photo by Han Chenxu / Unsplash Hey everyone, Today, I'd like to share a quick tip for those of you who are upgrading Spring Cloud Gateway in your projects. It's important to remember that when you upgrade Spring Cloud Gateway, you also need to update the Spring Cloud version to ensure compatibility. Here's why: Spring Cloud Gateway relies on specific features and dependencies provided by Spring Cloud. If you upgrade Spring Cloud Gateway without updating the Spring Cloud version, you may encounter compatibility issues and your gateway may not work as expected. To avoid this, always make sure to update the <spring-cloud.version> property in your pom.xml or build.gradle file along with the Spring Cloud Gateway version. For example, if you're upgrading to Spring Cloud Gateway x.y.z, ensure that the <spring-cloud.version> property is set to a compatible version. As of now, for Spring Cloud Gateway, a new API based on Spring 6, Spring Boot 3 and Project Reactor. The compatible Spring Cloud version is 2023.0.1. <properties> <spring-cloud.version>2023.0.1</spring-cloud.version> </properties> By keeping both the Spring Cloud Gateway and Spring Cloud versions in sync, you'll ensure a smooth upgrade process and avoid any unexpected issues. I hope this tip helps you in your Spring Cloud Gateway upgrades! Happy coding! Post, Code and Quiet Time. © 2024 – Unsubscribe