Re: Use AdoptOpenJDK as JDK Tool download source

In that case, you suggested a solution with a repository manager like Sonatype Nexus or Artifactory. I like this proposal and we already are using Nexus in our organization. Our Linux build servers have OpenJDK available to be installed through SUSE repositories. It is mostly for our Windows and

Jenkins Pipelines: Use jx-release-version

I read the CloudBees blog on jx-release-version. > > x-release-version calculates the next version number based on the current > Git tag, or current specified version on pom.xml/Makefile https://www.cloudbees.com/blog/automatically-versioning-your-application-jenkins-x It looks interesting to de

Re: Jenkins Performance loading slow

We have enabled cache for LDAP authentication Cache size 20 Cache TTL 5 min 0 sec Is there a workaround? Disabling cache perhaps? onsdag 20. mars 2019 00.03.01 UTC+1 skrev Stuart Rowe følgende: > > Since you have the Active Directory plugin installed, can you confirm that > you have caching ena

Re: Jenkins Performance loading slow

ter. onsdag 20. mars 2019 15.15.14 UTC+1 skrev Sverre Moe følgende: > > We have enabled cache for LDAP authentication > Cache size 20 > Cache TTL 5 min 0 sec > > > Is there a workaround? Disabling cache perhaps? > > onsdag 20. mars 2019 00.03.01 UTC+1 skrev Stuart Rowe følg

Re: Jenkins Performance loading slow

and increased memory usage on > the master. > > onsdag 20. mars 2019 15.15.14 UTC+1 skrev Sverre Moe følgende: >> >> We have enabled cache for LDAP authentication >> Cache size 20 >> Cache TTL 5 min 0 sec >> >> >> Is there a workaround? Disabling ca

Re: Jenkins Performance loading slow

I did try to delete the cookies from Jenkins, and it became much faster at loading. onsdag 20. mars 2019 15.22.52 UTC+1 skrev Sverre Moe følgende: > > I tried increasing the cache > Size 50 > TTL 1 hour > > Still loading is really slow for some. > Refresh main page, fast.

Jenkins Startup warning cannot find files

During each startup Jenkins comes out with a lot of: WARNING Could not find file /var/lib/jenkins/jobs/projectA/branches/* It is Multibranch pipeline projects. What is this about and how can I fix it? -- You received this message because you are subscribed to the Google Groups "Jenkins User

Blue Ocean: Hide certain projects from Pipelines

Is it possible to not show certain pipelines in Blue Ocean. We have one coverity job for each project. ProjectA ProjectA_cov ProjectB ProjectB_cov This pollutes the Pipelines list in Blue Ocean. Is it possible to avoid seing them. In Jenkins Classic, we have views where these projects are not vi

Unit tests for Scripted Pipeline

Is it possible to create unit tests for our scripted pipeline? How can certain sections of the pipeline be mocked, like fetching from Git, tagging to Git, Uploading to Nexus? Anyone been able to fully unit test scripted pipeline? I found this project at GitHub regarding Unit testing pipelines.

Re: Jenkins Startup warning cannot find files

There was no more output. Just two lines of Warning, lots of them 2019.04.04 10:30.00 com.cloudbees.hudson.plugins.folder.AbstractFolder loadChildren WARNING: Could not find file /var/lib/jenkins/jobs/projectName/branches/branchName/config.xml søndag 7. april 2019 22.08.21 UTC+2 skrev Ivan Fern

Re: Jenkins Startup warning cannot find files

It seems these are old builds, that no longer exists. We keep only the last N builds. I have not checked all, but I think I can say that they all are probably from old builds that no longer exists. søndag 7. april 2019 22.17.20 UTC+2 skrev Sverre Moe følgende: > > There was no more output

Views in Blue Ocean

Has there been any consideration about getting Views in Blue Ocean? The listing of pipelines becomes to large and distinct lists per view would be much better. Having favourites does help, but just a little. I want to see all projects under a certain git namespace. Also there are certain mainten

Pipeline with Staging builds before Release

Does anyone use Jenkins Pipeline with Staging? To stage a build (hold it back) until some criteria has been met. No user interaction or manual process involved, fully automatic. We have N Multibranch pipeline jobs in Jenkins with various dependencies on each other. When building a release we ne

Re: Blue Ocean: Hide certain projects from Pipelines

I found one workarround Create a Folder Job. Move all Coverity jobs into this. And they will not be seen in Blue Ocean. søndag 7. april 2019 00.07.54 UTC+2 skrev Sverre Moe følgende: > > Is it possible to not show certain pipelines in Blue Ocean. > > We have one coverity job for

Re: Blue Ocean: Hide certain projects from Pipelines

I rejoiced to soon. They did indeed show on Blue Ocean. folder > job1_cov folder > job2_cov torsdag 11. april 2019 12.35.55 UTC+2 skrev Sverre Moe følgende: > > I found one workarround > > Create a Folder Job. Move all Coverity jobs into this. And they will not >

Re: Blue Ocean: Hide certain projects from Pipelines

Found this https://issues.jenkins-ci.org/browse/JENKINS-39343 Seems there is planned some filtering feature to Blue Ocean. It is Very Old issue. I really hope it will done soon. torsdag 11. april 2019 12.42.40 UTC+2 skrev Sverre Moe følgende: > > I rejoiced to soon. They did indeed show o

Re: Views in Blue Ocean

https://issues.jenkins-ci.org/browse/JENKINS-39343 mandag 8. april 2019 09.55.05 UTC+2 skrev Sverre Moe følgende: > > Has there been any consideration about getting Views in Blue Ocean? > > The listing of pipelines becomes to large and distinct lists per view > would be much b

Jenkins Slow when user not logged in

When a user is not logged in then loading Jenkins can be extremely slow. Is this a known issue with Jenkins? We are running Jenkins LTS 2.150.1. Using LDAP authentication: Logged-in users can do anything, enabled anonymous read access. Enabled Cache: Cache size 50 Cache TTL 1 hour -- You r

Warnings Next Generation Plugin With GCC C++

How do I use this plugin to record and show C/C++ Warnings/Errors from GCC? There is two tools available GNU C Compiler (gcc3) and GNU C Compiler (gcc4), but are those for C? We are using a much newer version of GCC. Otherwise I could only find these for C++ recordIssues(tools: [cppCheck()]) rec

Re: Warnings Next Generation Plugin With GCC C++

/some_thing_file None from the sles nodes are shown. mandag 6. mai 2019 12.27.29 UTC+2 skrev Sverre Moe følgende: > > How do I use this plugin to record and show C/C++ Warnings/Errors from GCC? > > There is two tools available GNU C Compiler (gcc3) and GNU C Compiler > (gcc4), but are those

Re: Warnings Next Generation Plugin With GCC C++

mandag 6. mai 2019 12.55.15 UTC+2 skrev Ullrich Hafner følgende: > > > > I think I should rename the Tools > > GNU C Compiler (gcc4) -> GNU C Compiler > GNU C Compiler (gcc3) -> GNU C Compiler (3 and older) > > And the ID to gcc. > > Would that make sense? > > That makes sense. -- You received

Re: Warnings Next Generation Plugin With GCC C++

output showed none of the sles12.3 warnings. mandag 6. mai 2019 13.01.22 UTC+2 skrev Sverre Moe følgende: > > It seems to be very confused. > I am bulding on 4 nodes > opensuse42.3 > opensuse15.0 > sles12.3 > sles15.0 > > They have each their own gcc4 ID, but they have the

Re: Warnings Next Generation Plugin With GCC C++

mandag 6. mai 2019 13.23.02 UTC+2 skrev Ullrich Hafner følgende: > > There are some open issues about that: > https://issues.jenkins-ci.org/browse/JENKINS-44450 > https://issues.jenkins-ci.org/browse/JENKINS-55258 > > As a workaround you should pipe the log to a file. > How so, is there a pipelin

Pipeline: Show changes on build for rebased commits

Jenkins does not show changes after commits have been rebased. Build #1: has 3 changes (commits) Build #2: no changes The second build actually has the same three changes. but these are not shown. They are same changes as before, but just slightly changed (git rebased). I want the changes show

Re: Pipeline: Show changes on build for rebased commits

In Blue Ocean, under Changes, getting "There are no changes for this run". However there are changes. Is there no way I can force it to show the changes? mandag 13. mai 2019 16.27.27 UTC+2 skrev Sverre Moe følgende: > > Jenkins does not show changes after commits have been rebas

Re: Jenkins Pipelines: Use jx-release-version

two are finished and commited (not pushed yet), but I am waiting for my PR to be merged before I submit more PRs. torsdag 7. mars 2019 20.58.40 UTC+1 skrev Sverre Moe følgende: > > I read the CloudBees blog on jx-release-version. >> >> x-release-version calculates the next versi

Running a Pipeline multiple times in parallel

Our build Scripted Pipeline have several stages each in parallel executions. [image: Screenshot_20190521_181654.png] I need to run two parallel Pipeline builds in the same Run. I want this Stage view to duplicate and be run in parallel. However my test parallel script does not look good in Blue

Warnings Next Generation Plugin: Keep its history after discard builds

The "Warnings Trend" graphs are empty. >From out last build: sles15.0-x86_64: No warnings No warnings for 28 builds, i.e. since build 3 This might be because we delete old builds. We keep only the last 10 builds. In this case build #3 has been deleted. Is there a workaround for this? We do not w

Pipeline: The sh step does not show all output

The standard output from the sh-step does not show all the output: final def output = sh(returnStdout: true, label: "Build and Package", script : "make") writeFile(file: 'buildOutputFile.txt', text: output) The Blue Ocean log output from a single Node shows all the warnings, but the output from t

Re: Pipeline: The sh step does not show all output

I found a way to ouput both stdout and stderr, but then I didn't get either in Jenkins Console. sh("make 2>&1 | tee buildOutputFile.txt") mandag 27. mai 2019 12.20.17 UTC+2 skrev Sverre Moe følgende: > > The standard output from the sh-step does not show all the out

Re: Pipeline: The sh step does not show all output

>&3) | tee buildOutput.txt >&4) 3>&1) | (read xs; exit $xs)) 4>&1") Not quite sure how! mandag 27. mai 2019 12.57.28 UTC+2 skrev Ullrich Hafner følgende: > > Would a workaround as shown in > https://issues.jenkins-ci.org/browse/JENKINS-54832 help? >

Re: Pipeline: The sh step does not show all output

I got it to work by modifying my original sh step. I had to remove returnStdout sh(label: "Build and Package", script: "make 2>&1 | tee buildOutputFile.txt" ) mandag 27. mai 2019 15.50.07 UTC+2 skrev Sverre Moe følgende: > > Not sure I understand that wo

Re: Pipeline: The sh step does not show all output

This workaround gave me some problem with failing builds. The step no longer is marked failed when it fails. mandag 27. mai 2019 16.27.11 UTC+2 skrev Sverre Moe følgende: > > I got it to work by modifying my original sh step. I had to remove > returnStdout > > sh(label: &qu

Pipeline: OutOfMemoryError on build sh step

What is the usual culprit of this OutOfMemory problem? It happened at a "sh" step. It says nothing about HEAP or PermGen. My Jenkins has 8GB of MaxHeap, and are only now using 6GB. Running Jenkins LTS 2.150.1 java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thre

Re: Pipeline: The sh step does not show all output

I did not set such a parameter Like so? sh("set -o pipefail\n commandA | commandB") fredag 31. mai 2019 13.41.50 UTC+2 skrev Baptiste Mathus følgende: > > Likely because when calling scripts this way, `set -o pipefail` is not set > maybe? > > Le ven. 31 mai 2019 à 10:06

Re: Pipeline: The sh step does not show all output

Tried various solutions. Settled with this which works: sh(label: "Build and Package", script: """ set -o pipefail make 2>&1 | tee buildOutputFile.txt """) fredag 31. mai 2019 13.50.23 UTC+2 skrev Sverre Moe følgende: > > I d

Re: Pipeline: The sh step does not show all output

Marvelous, thanks, I'll try that. fredag 31. mai 2019 18.20.28 UTC+2 skrev Daniel Saier følgende: > > You can also use the tee step > , > > which automatically propagates the return codes of the steps inside o

Pipeline: Automatic gpg signing

I am trying to sign our RPM packages built on Jenkins. However it fails, probably because it asks for the passphrase. gpg: signing failed: Inappropriate ioctl for device error: gpg exec failed (2) Sometimes it works for a little while when I have signed manually in the console. When I sign manu

Re: Pipeline: Automatic gpg signing

; > ## end of rpm-sign.exp > > > > On Sunday, June 2, 2019 at 6:04:35 AM UTC-7, Sverre Moe wrote: >> >> I am trying to sign our RPM packages built on Jenkins. However it fails, >> probably because it asks for the passphrase. >> >> gpg: signing failed:

Multiple resources with same name not working

I have created a read-write resource lock master-sles12.3-read SLES 12.3 repository for master build environment #1 Labels master-sles12.3-write master-sles12.3-read SLES 12.3 repository for master build environment #2 Labels master-sles12.3-write master-sles12.3-read SLES 12.3 repository for ma

Pipeline: Shell step oddity removes escaped slash

I have the following Pipeline step to find specific files: sh("find . -regex '.*${packageName}-[0-9.]+-.\\.noarch\\.rpm'") The Output: [Pipeline] sh + find . -regex '.*package-name-[0-9.]+-.\.noarch\.rpm' This does not return any result. Both of these two works in Bash: find . -regex '.*meos-dash

Re: Jenkins Performance loading slow

+1 skrev Sverre Moe følgende: > > I did try to delete the cookies from Jenkins, and it became much faster at > loading. > > onsdag 20. mars 2019 15.22.52 UTC+1 skrev Sverre Moe følgende: >> >> I tried increasing the cache >> Size 50 >> TTL 1 hour >> >

Memory issues with Jenkins

We have assigned 8GB of memory to our Jenkins instance. JAVA_OPTIONS=-Xmx8g Still we experience memory issues after a while running. java.lang.OutOfMemoryError: unable to create new native thread We have: aprox 40 connected build agents aprox 400 pipeline jobs We have a test Jenkins instance run

Re: Memory issues with Jenkins

Today it has been chaotic. Several build agents disconnected Unexpected termination of the channel Many builds failed because of Memory error. I have tried restarting Jenkins several times today. Anyone have any suggestions? tirsdag 2. juli 2019 14.34.25 UTC+2 skrev Sverre Moe følgende

Jenkins Agents getting disconnected

Lately we have experienced disconnected Agents. Running Jenkins LTS 2.150.1 Java 8u181. Same for both Jenkins server and all build agents. Looking at the log it shows this: ERROR: [07/04/19 14:47:18] [SSH] Error deleting file. java.util.concurrent.TimeoutException at java.util.concurrent.Future

Re: Jenkins Agents getting disconnected

On the build agents that gets disconnected there is plenty of available disk space. When there are trying to connect, there are no remoting.jar java process on the agent running. lørdag 6. juli 2019 22.59.31 UTC+2 skrev Karan Kaushik følgende: > > Hi > > We had been facing the same issue with J

Re: Memory issues with Jenkins

jenkins.io/blog/2016/11/21/gc-tuning/ explained this part (and > much more) quite well. > > Then, once you understand better when it crashes, possibly you'll want to > analyze a heap dump to see what is causing the problem. > > Cheers > > > Le mar. 2 juil. 2019 à

Re: Memory issues with Jenkins

nd better when it crashes, possibly you'll want to >> analyze a heap dump to see what is causing the problem. >> >> Cheers >> >> >> Le mar. 2 juil. 2019 à 15:30, Sverre Moe > >> a écrit : >> >>> Today it has been chaotic. >>>

Re: Memory issues with Jenkins

Sverre Moe følgende: > > > Since we don't use 32bit, the reason must be > - the virtual memory of the OS has been fully depleted > > How can I check for this, and remedy it? > > fredag 5. juli 2019 03.17.38 UTC+2 skrev Jan Monterrubio følgende: > >> Correct me if

Re: Jenkins Agents getting disconnected

Strange If I configure the agent, save then try to reconnect it is able to create a connection and is back online. tirsdag 9. juli 2019 13.20.55 UTC+2 skrev Sverre Moe følgende: > > On the build agents that gets disconnected there is plenty of available > disk space. > > When t

Re: Jenkins Agents getting disconnected

I don't actually have to do anything, judt open Configure, Save, then Relaunch Agent. fredag 12. juli 2019 13.30.05 UTC+2 skrev Sverre Moe følgende: > > Strange > If I configure the agent, save then try to reconnect it is able to create > a connection and is back online. &g

Re: Jenkins Agents getting disconnected

s. fredag 12. juli 2019 14.23.24 UTC+2 skrev Sverre Moe følgende: > > I don't actually have to do anything, judt open Configure, Save, then > Relaunch Agent. > > fredag 12. juli 2019 13.30.05 UTC+2 skrev Sverre Moe følgende: >> >> Strange >> If I configure the

Re: Memory issues with Jenkins

jenkins@meoscorebs12:~> ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 80229 max locked memory (kbytes, -l)

Re: Jenkins Agents getting disconnected

I suspected it might be related, but was not sure. The odd thing this just started being a problem a week ago. Nothing as far as I can see has changed on the Jenkins server. lørdag 13. juli 2019 13.04.44 UTC+2 skrev Ivan Fernandez Calvo følgende: > > I saw that you have another question related

Re: Memory issues with Jenkins

-Support#ajavaparameters søndag 14. juli 2019 13.29.22 UTC+2 skrev Sverre Moe følgende: > > jenkins@meoscorebs12:~> ulimit -a > core file size (blocks, -c) unlimited > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size

Re: Jenkins Agents getting disconnected

unrelated: When this happens we have some builds on other nodes that stops working. They are aborted, but are still showing as running. The only thing that works is deleting the agent and creating it again, that or restarting Jenkins. søndag 14. juli 2019 13.31.51 UTC+2 skrev Sverre Moe følgende

Re: Jenkins Agents getting disconnected

- cleaning up connection [07/17/19 12:04:10] [SSH] Connection closed. My Jenkins server has over 500 threads open Threads: 506 total, 0 running, 506 sleeping, 0 stopped, 0 zombie onsdag 17. juli 2019 10.24.12 UTC+2 skrev Sverre Moe følgende: > > We have had to blissfull days of stable J

Re: Jenkins Agents getting disconnected

. onsdag 17. juli 2019 12.40.14 UTC+2 skrev Sverre Moe følgende: > > It seems to be the monitoring that gets the agents disconnected. > > Got this in my log file this last time they got disconnectd. > > Jul 17, 2019 11:58:22 AM > hudson.init.impl.InstallUnc

Re: Jenkins Agents getting disconnected

I cannot see any specific plugins in the stacktrace. There are several duplicate threads. Here are some of them. Most common denominator seems to be about SSH. Thread 29360: (state = BLOCKED) - java.lang.Object.wait(long) @bci=0 (Compiled frame; information may be imprecise) - java.lang.Object.

Re: Jenkins Agents getting disconnected

There is no such reference in my jstack output. The output says no deadlock detected. I will try that site for analyzing the jstack. Even a normal running Jenkins has many BLOCKED threads. If that is normal I don't know. We have a test Jenkins instance running on Java 11. That one does not have

Pipeline: Expected call wound up catching different method

I got a problem with my Pipeline which has worked fine up until recently. I don't quite understand what the problem is: expected to call Build.checkUpstream but wound up catching releaseUtility.getReleaseBranch; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/ expected to call Bu

Re: Jenkins Agents getting disconnected

I was unable to determine something from the stack output Here is the result: https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTkvMDcvMjkvLS1qc3RhY2sudHh0LS05LTE2LTI3 torsdag 18. juli 2019 11.28.06 UTC+2 skrev Sverre Moe følgende: > > There is no such reference in my jstack

Re: Memory issues with Jenkins

orum/#!topic/jenkinsci-users/UDyaH-kfqqA I also have an jstack output analyzed: https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTkvMDcvMjkvLS1qc3RhY2sudHh0LS05LTE2LTI3 søndag 14. juli 2019 13.48.57 UTC+2 skrev Sverre Moe følgende: > > I checked out that link > > Tried the

Re: Jenkins Agents getting disconnected

vice for you Jenkins HOME this is probably your bottleneck, if > not check the IO stats on the OS to see where you have the bottleneck. > > El lunes, 29 de julio de 2019, 11:20:50 (UTC+2), Sverre Moe escribió: >> >> I was unable to determine something from the stack output

Re: Memory issues with Jenkins

Have not yet resolved the issue. Not found a solution, nor what the cause actually is. lørdag 3. august 2019 13.04.10 UTC+2 skrev guerkan demirci følgende: > > Hi Sverre Moe, > > could you resolve the issue? > I have the same problem with Jenkins. > > Best > > > Am

Re: Jenkins Agents getting disconnected

ommendation is to NOT use NFS for JENKINS_HOME). >> >> >> https://support.cloudbees.com/hc/en-us/articles/115000486312-CJP-Performance-Best-Practices-for-Linux#nfs >> >> and >> https://support.cloudbees.com/hc/en-us/articles/217479948-NFS-Guide >> >> On

Re: Jenkins Agents getting disconnected

We do have one NFS, for copying build artifacts to RPM repository. tirsdag 6. august 2019 09.08.48 UTC+2 skrev Sverre Moe følgende: > > I was mistaken. We did not use NFS. > The disk for JENKINS_HOME (Jenkins running on VM), is a LVM disk. > > mandag 29. juli 2019 18.15.20 U

Re: Memory issues with Jenkins

Sadly I was mistaken. We do not use NFS for JENKINS_HOME. We do however use NFS for the location where builds copy the RPM build artifacts. mandag 5. august 2019 22.17.46 UTC+2 skrev Ivan Fernandez Calvo følgende: > > Hi, > > Severe has another email thread open, I think it is the same Jenkins

Gradle Tool Failed Download

This has worked before. Now that we where to upgrade from Gradle 5.0 to 5.5 and added the tool gradle-5.5 it fails to retrieve the archive. Anyone have an idea what the problem might be? Running both Jenkins and Agents on Java 8 Update 221. Is there any way arround this without hacking the JRE

Re: Gradle Tool Failed Download

.gradle.org/distributions/gradle-5.5.1-bin.zip Gives same Stacktrace. onsdag 7. august 2019 18.51.37 UTC+2 skrev Sverre Moe følgende: > > This has worked before. Now that we where to upgrade from Gradle 5.0 to > 5.5 and added the tool gradle-5.5 it fails to retrieve the archive. > > An

Re: Gradle Tool Failed Download

. > > When I download from that URL, my web browser reports no issues from > Google Chrome on Windows and no issues from wget on a FreeBSD computer. > > On Wed, Aug 7, 2019 at 10:51 AM Sverre Moe > wrote: > >> This has worked before. Now that we where to upgrade from G

Re: Gradle Tool Failed Download

from my network instead of the copy from the internet. > > On Wed, Aug 7, 2019 at 11:56 AM Sverre Moe > wrote: > >> I have no modifed cacerts. >> >> Using wget also fails on the agent, until I set a proxy. >> The Jenkins server does have proxy configured,

Re: Gradle Tool Failed Download

Perhaps I could use instead the Installers "Run Shell Command", or "Run Batch Command". Then unpack it myself, ensuring it gets unpacked within the tool name directory. Would I need both in order for it to work on Linux and Windows? onsdag 7. august 2019 21.04.09 UTC+2 skrev

Re: Gradle Tool Failed Download

ugust 2019 21.10.59 UTC+2 skrev Sverre Moe følgende: > > Perhaps I could use instead the Installers "Run Shell Command", or "Run > Batch Command". > Then unpack it myself, ensuring it gets unpacked within the tool name > directory. > Would I need both in order f

Re: Gradle Tool Failed Download

#sec:custom_gradle_distribution onsdag 7. august 2019 22.00.53 UTC+2 skrev Richard Bywater følgende: > > Personally with Gradle I've always found it easier to use Gradle Wrapper > instead of full installs. > > Don't know if that's an option for you or not. > > Richard. > > On Thu,

Re: Gradle Tool Failed Download

our self using "Run Shell Command". onsdag 7. august 2019 23.42.57 UTC+2 skrev Sverre Moe følgende: > > I am not very keen on checking in the gradle wrapper to git. Though I do > see the appeal. > > Now with Gradle 5.5 I am planning on creating a custom Gradle distribution

Re: Memory issues with Jenkins

ailable build agent instead. tirsdag 6. august 2019 09.48.50 UTC+2 skrev Sverre Moe følgende: > > Sadly I was mistaken. We do not use NFS for JENKINS_HOME. > > We do however use NFS for the location where builds copy the RPM build > artifacts. > > mandag 5. august 2019 22.17.4

Re: Memory issues with Jenkins

), which would confirm that you are hitting JENKINS-58684 > <https://issues.jenkins-ci.org/browse/JENKINS-58684>. > > The advice to stop building on master is definitely a good idea as well. > > On Aug 14, 2019, at 07:11, Sverre Moe > > wrote: > > We got an 30 minute fre

Re: Memory issues with Jenkins

I created a Pipeline job to run jstack every 10 minutes (though running on Jenkins master since that is where the Jenkins is running). onsdag 14. august 2019 16.07.02 UTC+2 skrev Félix Belzunce Arcos følgende: > > Hi Sverre Moe, > > I am the person who talked to you this morning

Re: Memory issues with Jenkins

r. 3 Configured many of our build agents to be offline and come online on demand 4 Upgraded our Jenkins server: The old server was running SLES12. We Set up a new VM with SLES15, and copied JENKINS_HOME over to this new server. onsdag 14. august 2019 16.17.06 UTC+2 skrev Sverre Moe følgende:

Blue Ocean: Incomplete or missing Stages and Steps

Sometimes when a build fails, Blue Ocean does not show any completed or failed stages. All stages show the same Step, with an incomplete build output (it is missing the beginning of the output). No stepsThis stage has no steps The entire build output is all displayed under this "step". [image:

Re: Gradle Tool Failed Download

ption after 5.5, I think we would to stick with the option > of unpacking the installer our self using "Run Shell Command". > > onsdag 7. august 2019 23.42.57 UTC+2 skrev Sverre Moe følgende: >> >> I am not very keen on checking in the gradle wrapper to git. Though I d

Re: Gradle Tool Failed Download

RE > > On Mon, Sep 23, 2019 at 05:37 Daniel Beck > wrote: > >> >> >> On Mon, Sep 23, 2019 at 2:28 PM Sverre Moe > > wrote: >> >>> ERROR: Failed to download >>> https://services.gradle.org/distr

Re: Gradle Tool Failed Download

ad... >> that might be a good alternative if you can’t upgrade the JRE >> >> On Mon, Sep 23, 2019 at 05:37 Daniel Beck wrote: >> >>> >>> >>> On Mon, Sep 23, 2019 at 2:28 PM Sverre Moe wrote: >>> >>>> ERROR: Failed to d

Re: Gradle Tool Failed Download

Which projects has the source code for the Maven, Gradle and Groovy Tool installers? I want to have a check to see if there is something to be done on the Gradle and Groovy tool installers. onsdag 25. september 2019 10.30.17 UTC+2 skrev Sverre Moe følgende: > > The Gradle tool installer

Re: Gradle Tool Failed Download

proxy configured, but the build agents do not have any proxy configured. I have same problem using Gradle wrapper, but as mentioned earlier here gradle wrapper works if I configure proxy properties. onsdag 25. september 2019 10.41.32 UTC+2 skrev Sverre Moe følgende: > > Which projects h

Re: Gradle Tool Failed Download

ould > run probably on a different machine, with different JRE, so that doesn't > tell you much.) > > > On Wed, Sep 25, 2019 at 10:59 AM Sverre Moe > wrote: > >> Both the MavenInstaller and GradleInstaller are very similar >> >> public static class MavenIns

Re: Gradle Tool Failed Download

a quick no-op if the tool is already installed. Getting none of the Bash magic for checking empty directory to work. onsdag 25. september 2019 11.38.23 UTC+2 skrev Sverre Moe følgende: > > There is no Exception thrown when running that in script console. > > Result: PK > A > gra

Multibranch Pipeline: Checkout fatal bad object

The first build of any Branch or Tag the checkout step outputs one line with fatal bad object, for a different git commit hash than the one checked out. Anyone know what the reason for this is? > git fetch --tags --progress --depth=25 -- ssh://g...@git.company.com/apps/app-project.git +refs/

Re: Multibranch Pipeline: Checkout fatal bad object

Checking out Revision d7989b6aa4e91962f5aeb807ad26e52432034b64 (master) > git config core.sparsecheckout # timeout=10 > git checkout -f d7989b6aa4e91962f5aeb807ad26e52432034b64 onsdag 30. oktober 2019 11.56.22 UTC+1 skrev Sverre Moe følgende: > > The first build of any Branch or

Coverage API: jacoco instead of jacocoAdapter

Publish Coverage from JaCoCo using the new Coverage API: https://jenkins.io/blog/2018/08/17/code-coverage-api-plugin-1/ It makes a statement in this blog: > publishCoverage adapters: [jacocoAdapter('target/site/jacoco/jacoco.xml')] > You can also use jacoco instead of jacocoAdapter if you didn't

RegEx Job Filter for SCM Not Working

I am trying to get the Regular Expression Job Filter to work with SCM Configuration. Regular Expression: ssh://g...@git.company.com/various/.* Match Value: Job SCM Configuration Match Type: Include Matched But no jobs are listed in the View. I want it to list all jobs that have SCM configuratio

The pipeline emailextrecipients step takes too long time

Calling the pipeline step emailextrecipients when there are changes takes too much time. A normal git checkout that takes 10-15 seconds, will usually take 1-2 minutes when there are changes, just because of emailextrecipients. All I want is the authors from the current build changes. I see no rea

Re: The pipeline emailextrecipients step takes too long time

e følgende: > > You can turn on debug mode in the global config for Email Ext. The code > isn't really doing anything major, it just looks at the changesets and get > the authors, so I am not sure why it would be taking that long. > > On Fri, Apr 24, 2020 at 1:59 PM Sverre Mo

Re: The pipeline emailextrecipients step takes too long time

author: Sverre Moe Adding Sverre Moe with address sve...@company.com Analyzing: sve...@company.com Looking for: sve...@company.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: sve...@company.com => found type: 0 Analyzing: sve...@company.com Looking

Re: The pipeline emailextrecipients step takes too long time

skrev Sverre Moe følgende: > > Yes it did. > > Just one simple little commit, and Checkout took a little over 1 minute > > [Pipeline] emailextrecipients > <https://build-ci.spacetec.no:8443/view/All%20meosconfig/job/meosconfig-dashboard-layouts/job/master/168/console#> &g

Re: The pipeline emailextrecipients step takes too long time

How can I add timestamp to the debug output? søndag 26. april 2020 18.30.59 UTC+2 skrev slide følgende: > > Can you add timestamps? It's hard to tell from what you posted when things > are occurring. > > On Sun, Apr 26, 2020, 01:16 Sverre Moe > > wrote: > >>

Re: The pipeline emailextrecipients step takes too long time

s. > > > > On Sunday, April 26, 2020 at 12:30:59 PM UTC-4, slide wrote: >> >> Can you add timestamps? It's hard to tell from what you posted when >> things are occurring. >> >> On Sun, Apr 26, 2020, 01:16 Sverre Moe wrote: >> >>> Yes it d

Re: The pipeline emailextrecipients step takes too long time

ord Street, 4th floor, tower 3 > Lowell, MA 01851 > 1.978.257.2183 (*cell*) > <http://www.riftio.com>www.riftio.com > -- > *From:* jenkins...@googlegroups.com < > jenkins...@googlegroups.com > on behalf of Sverre Moe < > sver...@gmail.c

Re: The pipeline emailextrecipients step takes too long time

, 2020 at 14:32 Sverre Moe > > wrote: > >> How can I add timestamp to the debug output? >> >> søndag 26. april 2020 18.30.59 UTC+2 skrev slide følgende: >>> >>> Can you add timestamps? It's hard to tell from what you posted when >>> t

  1   2   3   4   >