This plugin has not been updated much the last 2-3 years.
https://github.com/jenkinsci/ssh-steps-plugin
I wonder if I should abandon it.
onsdag 19. januar 2022 kl. 12:33:24 UTC+1 skrev Sverre Moe:
> When I have a script with multiple lines, I do not get any output from the
>
When I have a script with multiple lines, I do not get any output from the
script in the console output of the pipeline job.
https://www.jenkins.io/doc/pipeline/steps/ssh-steps/#sshscript-ssh-steps-sshscript-execute-scriptfile-on-remote-node
pipeline {
agent {
label 'docker-agent'
}
Pipeline as YAML is interesting, but it looks to still be in development.
https://www.jenkins.io/blog/2018/04/25/configuring-jenkins-pipeline-with-yaml-file/
https://www.jenkins.io/projects/gsoc/2020/project-ideas/pipeline-as-yaml-experiment/
https://plugins.jenkins.io/pipeline-as-yaml/
fredag
We are using Jenkins Pipelines, but need to maintain build dependencies.
Since DependencyGraph does not work on Pipeline jobs, I have created a set
of FreeStyle jobs for each Multibranch Pipeline job.
We get the upstream dependencies for each Pipeline job (from the RPM spec
file
I do not have any additional artifact managers installed.
Strange no one has made other artifact managers for like Nexus or plain
file storage on a file server.
fredag 10. desember 2021 kl. 14:08:46 UTC+1 skrev dheinric:
> Am Freitag, dem 10.12.2021 um 04:58 -0800 schrieb Sverre Moe:
>
> *P
uploading to a Maven
repository.
Strange considering: "This plugin goal is to upload artifacts generated
from non-maven projects to Nexus"
Perhaps I would need to make my own customer Artifact Manager.
fredag 10. desember 2021 kl. 13:44:08 UTC+1 skrev Sverre Moe:
> https://brokenco
https://brokenco.de/2018/01/04/external-artifacts-jenkins.html
Not an ideal solution. More of a hack.
torsdag 9. desember 2021 kl. 13:22:20 UTC+1 skrev Sverre Moe:
> Can Jenkins show artifacts stored in external repositories?
>
> We want to avoid storing the build artifacts on th
Can Jenkins show artifacts stored in external repositories?
We want to avoid storing the build artifacts on the Jenkins server. This
takes up a lot of space. Even though we have limited artifacts retention to
the last 5 builds only.
archiveArtifacts allowEmptyArchive: true, artifacts:
User branches are like
origin/username/CICD
Official branches are origin/CICD og origin/master
All part of the same project.
CICD branch has a different Declarative Pipeline for CICD release build and
deployment.
Same goes for user branches that are based on this CICD branch.
All other branches
We have a branch in projectA called CICD.
This branch we want to be triggered automatically after the master branch
has built.
However we do not want user branches of the CICD to be triggered
automatically.
Is it possible to avoid configuring a trigger if the branch is not CICD?
This is
. 19:53:09 UTC+2 skrev Sverre Moe:
> I tried to add a BuildStrategy to the BranchSource, to skip the first
> branch indexing.
>
> I did this to avoid Jenkins to build all branches after changing the SCM
> configuration.
> Otherwise Jenkins would have to build 400+ repositoris w
Recently we have been getting an Proxy Error each time we try to change
some configuration in Jenkins.
On Save and Apply, Jenkins gives us the following error:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request
I tried to add a BuildStrategy to the BranchSource, to skip the first
branch indexing.
I did this to avoid Jenkins to build all branches after changing the SCM
configuration.
Otherwise Jenkins would have to build 400+ repositoris with 20-30 branches
in each.
final def buildStrategies =
No reason. We now use the Code Coverage API, so just uninstalled the JaCoCo
Plugin.
tirsdag 8. juni 2021 kl. 21:12:51 UTC+2 skrev ullrich...@gmail.com:
> Is there a reason that you are still using the old and unmaintained JaCoCo
> plugin and not the code-coverage-api plugin? The functionality
Job Type Filter
GitLab Group
Include Matched
Does not work.
It includes ALL projects in Jenkins, Pipeline and Multibranch Pipeline jobs.
All I want is to include only the GitLab Group projects.
There are no issues registered.
--
You received this message because you are subscribed to the
I have upgraded all the plugins, then restarted Jenkins.
It fails to start properly.
Any idea what the problem here is about?
The website is loading, but shows the following Stacktrace
java.lang.IllegalArgumentException: Unable to inject class
hudson.model.UserIdMapper at
tools support, making
sure we have the same version of git installed everywhere.
fredag 30. april 2021 kl. 12:36:24 UTC+2 skrev Sverre Moe:
> BRANCH1
> + git branch
> * (no branch)
>
> BRANCH2
> + git branch
> * (HEAD detached at 5abd860)
>
> The same project, but one
BRANCH1
+ git branch
* (no branch)
BRANCH2
+ git branch
* (HEAD detached at 5abd860)
The same project, but one branch does not return any branches on `git
branch`.
Any clue as to why?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
There are two options for GitLab when selecting a repository browser in the
SCM configuration.
1) GitLab
2) gitlab
The first one does not take any parameters.
The second one takes URL and Version parameters.
What is the difference?
How does the first one get the correct URL to GitLab for the
I will check out the Job DSL Documentation and try my luck to write the
configuration my self.
I had hope this XML Job to Job DSL would help me save some time.
multibranchPipelineJob("my_awesome_job") {
}
tirsdag 23. mars 2021 kl. 11:11:30 UTC+1 skrev Sverre Moe
Shame. I like Configuration by Code. We use mainly only Multibranch
Pipeline.
It is the one of the major things I think Jenkins is lacking. It has
Configuration by Code for Jenkins Configuration, but limited for Job
Configuration, supported by this plugin.
mandag 22. mars 2021 kl. 22:29:26
. mars 2021 kl. 19:30:56 UTC+1 skrev Sverre Moe:
> I even tried to uncheck the GitLab Configuration for authentication
> `Enable authentication for '/project' end-point`
>
> But alas, still not working.
>
> mandag 22. mars 2021 kl. 19:17:12 UTC+1 skrev Sverre Moe:
>
>&g
I even tried to uncheck the GitLab Configuration for authentication
`Enable authentication for '/project' end-point`
But alas, still not working.
mandag 22. mars 2021 kl. 19:17:12 UTC+1 skrev Sverre Moe:
> GitLab Plugin API access no longer works:
> It wirj
> The Jenkins job is a Mu
GitLab Plugin API access no longer works:
It wirj
The Jenkins job is a Multibranch Pipeline.
The SCM is Git (not Git Project)
This has worked before.
Then we upgraded Jenkins LTS from 2.263 to 2.277
Along with many plugin updates.
Now it no longer works.
GitLab is able to send the notification,
I have tried out the XML Job to DSL Job Plugin.
It lists all single Pipeline jobs under a Multibranch Pipeline job.
It does not seem to be able to export the Multibranch Pipeline Job.
The DSL Job Plugin does seem to support Multibranch Pipeline jobs.
There is no open issues to suggest this is a
-head".
Is there any way to get the same with GitLab Group?
The updateGitlabCommitStatus run within a Jenkinsfile on a GitLab Group
Project does not make its way into GitLab.
tirsdag 16. mars 2021 kl. 19:32:59 UTC+1 skrev Sverre Moe:
> Is it possible to combine both *GitLab Plugin* with *
failed
Analysis pending
I do not know if this is possible with the GitLab API.
I tried running the GitLab Plugin steps, within a GitLab Group Merge
Request build.
It did nothing. No information on GitLab MR when I sent
updateGitlabCommitStatus
lørdag 6. mars 2021 kl. 21:41:20 UTC+1 skrev Sverre
When we moved our git repositories to Gitlab, checkout failed when using
Credentials for SCM Repository for our Multibranch Pipeline Projects.
[Mon Mar 15 14:31:33 CET 2021] Starting branch indexing...
> git --version # timeout=10
> git --version # 'git version 2.26.2'
using GIT_SSH to set
estions. Pull requests welcomed to
> https://github.com/jenkinsci/gitlab-branch-source-plugin/blob/master/README.md
>
>
> On Mon, Mar 15, 2021 at 9:23 AM Sverre Moe wrote:
>
>> More detailed information is needed on the documentation for GitLab
>> Branch Source Plugin
More detailed information is needed on the documentation for GitLab Branch
Source Plugin
https://plugins.jenkins.io/gitlab-branch-source/
If one also has the GitLab Plugin, the Jenkins Configuration has two
sections called GitLab.
This should be mentioned so not to confuse.
About iii.
What is the preferred way to Integrate both Jenkins and GitLab?
What is the best way to do it?
GitLab has deploy keys. I have created deploy keys for all 30 Jenkins build
agents.
I have added these deploy keys to each project. We only got 8 projects
migrated from Gitolite at the moment. Adding
it is not as elegant as using Java Stream API.
søndag 7. februar 2021 kl. 19:00:39 UTC+1 skrev Sverre Moe:
>
> The following piece of code works fine in Groovy, but Jenkins complains
> about unexpected token: ->
>
> final def files = findFiles(glob: filePattern)
> final def ro
The following piece of code works fine in Groovy, but Jenkins complains
about unexpected token: ->
final def files = findFiles(glob: filePattern)
final def rootNode = files.stream()
.map(file -> findByContent(file.getPath()))
.filter(node -> node != null)
versions prior to 2.0 will miss many, many
> improvements that have been made to command line git.
>
> On Wed, Oct 14, 2020 at 10:21 AM Sverre Moe wrote:
>
>> Cloning Git with an old version of Git now seems to fail
>>
>> Cloning the remote Git repository ERROR: Error
Cloning Git with an old version of Git now seems to fail
Cloning the remote Git repository ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not init
/home/build/jenkins/workspace/rebuild-packages/base at
Still seeing this problem.
Not on every jobs
I wonder if I should report a bug for this.
Now running Jenkins LTS 2.222.3
Blue Ocean 1.23.1
torsdag 2. april 2020 kl. 19:09:03 UTC+2 skrev Sverre Moe:
> I noticed something odd today.
> When I opened Blue Ocean on a recent build I noticed tha
The plugin does not support Pipeline projects for SCM Configuration
filtering on RegEx.
I have created a change
request: https://issues.jenkins-ci.org/browse/JENKINS-62233
mandag 4. mai 2020 11.51.52 UTC+2 skrev Sverre Moe følgende:
>
> According to documentation it should be po
difficult to maintain if I had to list each jobs in this
file for each view.
tirsdag 7. april 2020 10.42.54 UTC+2 skrev Sverre Moe følgende:
>
> I am trying to get the Regular Expression Job Filter to work with SCM
> Configuration.
>
> Regular Expression: ssh://g...@git.
.
>
> On Wed, Apr 29, 2020 at 8:18 AM Sverre Moe > wrote:
>
>> My code for finding the changeset authors worked fine.
>> If any developers have wrong email address, then so be it.
>> This solution is much much faster.
>>
>> def getAuthors(build) {
>
My code for finding the changeset authors worked fine.
If any developers have wrong email address, then so be it.
This solution is much much faster.
def getAuthors(build) {
final def authors = []
final def changeSets = build.changeSets
for (def cs: changeSets) {
final def
e debugging into
> Jenkins?
>
>
>
> But I guess that email-ext insider Slide might have much better hints…
>
>
>
> HTH Reinhold
>
>
>
> *From:* jenkins...@googlegroups.com <
> jenkins...@googlegroups.com > *On Behalf Of *Sverre Moe
> *Sent:* Mi
sets.
/Sverre
tirsdag 28. april 2020 22.52.06 UTC+2 skrev Sverre Moe følgende:
>
>
> Found this setting in Configure Global Security for LDAP:
> Disable Ldap Email Resolver
> I ticked it, now I will see if that can help the issue.
>
>
> LDAP Caching:
> I had n
the changeset so an email address. It provides an extension point for
> this that other plugins can implement to provide that service. If you are
> having long delays accessing LDAP, that would definitely point to that as a
> culprit for the length of time.
>
>
>
> On M
esolve usernames
>> from the changeset so an email address. It provides an extension point for
>> this that other plugins can implement to provide that service. If you are
>> having long delays accessing LDAP, that would definitely point to that as a
>> culprit for the
:
>
> There is no lookup until the email is sent. There may be a call to resolve
> a username to the email address though. Are you using ldap or AD?
>
> On Mon, Apr 27, 2020, 01:39 Sverre Moe >
> wrote:
>
>> Well at this point I am not sending any email, yet.
>> I
It seems emailextrecipients are using 60 seconds for each email it finds.
I am going to add the timestamper plugin to see what parts of the debug
output from emailextrecipients are taking so long.
mandag 27. april 2020 10.39.30 UTC+2 skrev Sverre Moe følgende:
>
> Well at this poin
, 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
>>> things
treet, 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.com &g
e lookups.
>
>
>
> 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 did.
>&g
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:
>
>> Yes
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
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
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 Moe &g
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
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
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
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
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
ripting 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
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 MavenInstaller extends Downl
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 projec
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 ins
stead...
>> 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
e 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 download
>>> https://services.gradle.org/distr
come an option 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
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".
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:
>
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
), 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
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
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
#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, 8 Aug 2019, 7:3
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
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
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, but n
.
>
> 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
le.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.
>
> Any
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
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
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
n 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 Mon, Jul
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
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
/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 ulimit settin
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
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
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
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)
-
.
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
- 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
or 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
-for-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
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
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,
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 a
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
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
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 I’m w
tter 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.
>>> Several
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 à 1
1 - 100 of 378 matches
Mail list logo
