San Song Daddy :)

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  

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  

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  

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  

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