Re: error

I'm afraid I've no clue what's this is about and no context neither. You might need to provide more details if you want some help. Besides, unreachable means too many things, but worth also explain what you have tried in your end plus how you get there Cheers -- You received this message beca

Re: Jenkins Plugin upgrade from 1.454 to 1.651.3

Hi, the latest 1.x release of this artefact is 1.645: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/plugin/ Cheers, Steffen Am Mittwoch, 6. Februar 2019 08:45:55 UTC+1 schrieb Panagiotis Labrou: > > Hi there, > > > > We have a few custom Jenkins plugins developed for version 1.454

Re: Get Ansible "PLAY RECAP" Failed value from Jenkins pipeline

I use also ansible and I took the approach to convert the ansible playbook output to JUnit format and that helps me to see the number of executed tasks and their status (success, failed, skipped). In case you are interested about it: - https://docs.ansible.com/ansible/latest/plugins/callback/ju

RE: Jenkins Plugin upgrade from 1.454 to 1.651.3

Hi Steffen, Thank you for your reply. Yes I agree with this but if I want to install 1.651.3 war file for Jenkins which one from plugin site should I select in my plugin’s pom file? I have tried the following but it didn’t work org.jenkins-ci.plugins plugin 2.0

Re: Jenkins Plugin upgrade from 1.454 to 1.651.3

IIUC, you would like to use a WAR file different than the default one, if so, then you might need to use the properties section to enforce the version you'd like to: - https://github.com/jenkinsci/plugin-pom/tree/plugin-2.0 ... org.jenkins-ci.plugins plugin-pom 2.0 1.651.

Re: Jenkins Plugin upgrade from 1.454 to 1.651.3

If I recall correctly, since `plugin-pom` 2.0, the version of the Jenkins the plugin is built for is set with the `jenkins.version` property, as Victor said. So you could basically use the latest `plugin-pom` (3.37) and stil compile for `1.651.3`. It's a minimal core version requirement. Doesn't me

Remoting issue

We've been seeing job termination due to slave disconnects, and would like help in solving this issue. Jenkins 2.140 ssh-slaves-plugin 1.29.4 Ubuntu 16.04.5 Hypervisor, plugin Libvirt 1.8.6 Slave guest: Ubuntu 18.04.1 I've been looking at the wiki note here: https://wiki.

Re: Remoting issue

...forgot to mention that Jenkins and the VMs are all running on the same machine, so network activity shouldn't be an issue. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, sen

remoting issue

We've been seeing job termination due to slave disconnects, and would like help in solving this issue. Jenkins 2.140 ssh-slaves-plugin 1.29.4 Ubuntu 16.04.5 Hypervisor, plugin Libvirt 1.8.6 Slave guest: Ubuntu 18.04.1 Jenkins and the VMs are all running on the same machine, so network activity

Re: remoting issue

>Jenkins and the VMs are all running on the same machine, so network activity shouldn't be an issue. network is not an issue, but performance response, Could it be? it is not a good idea to run the Jenkins Master and Agents in the same machine, if you use Docker container and you do not limit t

What should be used instead of the various Deprecated plugins?

I've noticed that our builds now have a list of Deprecated plugins: - [Deprecated] Publish Findbugs Analysis results - [Deprecated] Scan for Compiler warnings - [Deprecated] Publish combined static analysis results What are the replacements for those? -- You received this message beca

Re: remoting issue

My reading of the code indicates that the timeout value is set by "kexTimeout" in com\trilead\ssh2\Connection.java at line 693. That appears to be set in SSHLauncher.openConnection():1184. The value we're using for 'launchTimeoutMillis' should be 15000, assuming that it comes from "Startup Id

Re: What should be used instead of the various Deprecated plugins?

https://github.com/jenkinsci/warnings-ng-plugin There should be a upgrade notice in your system configuration if you have not installed the new plugin. > Am 06.02.2019 um 18:18 schrieb John Lussmyer : > > I've noticed that our builds now have a

Re: remoting issue

This timeout, it is only for the connection stage, and it includes whole retry reconnections, long history, the default value is 210 seconds, less than 30-60 seconds it is not a good value and only if you have reties to 0. I do not know how many agents you spin at the same time, I would try to