Executing Maven build in jenkins pod(container) using jenkins Kubernetes
Created a maven build
I am cloning from git
Then trying to execute the junit scripts
For few builds I faced pom.xml path issue
Later after clone I faced java.nio.channels.ClosedChannelException
Now directly once the build starts getting this error java.nio.channels.ClosedChannelException
More Info:
I also increased memory but didnt worked
enter image description here
I was using the same port for docker Jenkins and local jenkins. I made com.nirima.jenkins.plugins.docker.DockerContainerWatchdog.enabled=false on ALL the Jenkins servers as per some reference.But still facing the issue
Related
I am running sonar-scanner for a repo from gitlab on jenkins. Sonar-scanner upload reports to sonarqube successfully.
The roadmap on jenkins is that: clone repo from gitlab. Start sonar-scanner inside docker container. Sonar-scanner upload reports to sonarqube and open discussion on gitlab commit.
The report file dir size is 13 MB zip size 6MB. I am using proxy for sonarqube. That means my proxy is set correctly(On kubernetes with annotation that is nginx.ingress.kubernetes.io/proxy-body-size).
My problem is that gitlab issue publisher not finishing for analysis. I tried on a directory that produces 100kb report file size that is successfully open disscussion on gitlab. I think my issue is related with the report size. But couldn't find any solution.
Do you have any?
Additional infoes:
Sonarqube version: 7.9.3 (build 33349) CE
Sonar-Scanner: sonarsource/sonar-scanner-cli: latest(Digest:sha256:135815)
Gitlab Version: GitLab Community Edition 11.9.1
Sonar-gitlab-plugin: https://github.com/gabrie-allaigre/sonar-gitlab-plugin (sonar-gitlab-plugin-4.1.0-SNAPSHOT)
Sonarqube was behind a load balancer. I increased proxy-body-size on both sonarqube and nginx load balancer to 25 mb and t solved. If you face with similar issue look your web server configs.
I installed Jenkins on my -AWS EC2 Ubuntu- and on the same server I'm running Docker. what I'm trying to do is to build a pipeline via Jenkins on that EC2 Instance. my jenkinsfile stored on Github
When I run the pipeline I get the following error:
Jenkins’ doesn’t have label ‘docker'
How to solve this problem?
I went to manage Jenkins -> global tools and also to configure system
but non of these solve the problem.
Any suggestions?
I am trying to create a Jenkins pipeline on Openshift, that automatically runs a Jenkins service when we start the pipeline build. I referred few templates online and created a Jenkins pod and a pipeline. But whenever I try to run the pipeline, It shows build status as "not started.
Later, I created a standalone Jenkins service in Openshift, created a Jenkins file in open shift and tried executing it. I encountered authentication issues while connecting with Openshift from Jenkins.
Can anyone guide me, if I am missing something or any other working templates for a pipeline?
Thanks
It’s because of permissions
Jenkins runs with Jenkins user and openshift doesn’t know how to connect to it
Create a new service account in openshift jenkins
I am trying to create a jenkins job that will build a github project inside a docker container that shall be generated from the Dockerfile contained in the github project itself. To do so, I am using docker slaves plugin but I am running into an issue when I run the jenkins job.
Error during container provisioning
The configuration I am using for the jenkins job is the following:
jenkins job config
So the job right now should only clone the repo and build the image. Any suggestions?
The solution to the problem was to set the remoting image to jenkinsci/slave in the global configuration of jenkins
Jenkins global config
I'm trying out DevOps with VSTS, Docker and Java and I'm stuck with failing builds PFA screenshots of the same.
VSTS build failing while Queue Jenkins job task
Job is successfully executed on Jenkins and .War file is also produced.
This has been setup on Azure following document
https://github.com/msdevno/hol-oss-devops
Another approach is to have the commit to VSTS trigger the build in Jenkins. Then have Jenkins trigger the release in VSTS. Setting up CI/CD with the TFS Plugin for Jenkins This would not require using VSTS for build.
I was able to resolve the above issue.
My guess worked out correct.
Changing the Public IP from Dynamic to Static caused this issue.
Looked into Jenkins configuration(Manange Jenkins > Configure System > Jenkins Location > Jenkins URL) This was containing dynamic IP and now I've changed it to new static IP and voila it works fine. Build Succeeds and status updated on VSTS as well :)
Thanks for sparing your time in looking to my issue #Starain-MSFT & #Donovan