Problem identified and followed up at
https://issues.jenkins-ci.org/browse/INFRA-2154
On Monday, 17 June 2019 11:33:10 UTC+2, Damien Coraboeuf wrote:
>
> Note that the issue can be reproduced very easily:
>
> curl -vL --output test.hpi https://
>
Can you execute a command on a remote ssh session on the agent? something
like the following commands `ssh USER@JENKINS_AGENT echo "OK"`, `ssh -t
USER@JENKINS_AGENT echo "OK"`, `ssh -T USER@JENKINS_AGENT echo "OK"`
--
You received this message because you are subscribed to the Google Groups
Hello fellow Jenkins users and developers,
I am a product manager at CloudBees and have taken over responsibility for the
Jenkins Blue Ocean sub-project. Over the last year, the teams working on
Jenkins at CloudBees have looked at the initiative of overhauling the Jenkins
user experience. This
Hello All,
Please help me out with adding a Windows slave into Jenkins.
I am using Launch Method as "Launch agent by connecting it to the master".
Which provides me three options to connect the slave machine.
Connect agent to Jenkins one of these ways:
-
[image: launch agent]
>From a europe-west1 GCP instance I even get timeouts:
Checking update center connectivity
java.net.SocketTimeoutException: connect timed out
Sometimes I get a reply after > 20s.
On Monday, June 17, 2019 at 11:33:10 AM UTC+2, Damien Coraboeuf wrote:
>
> Note that the issue can be reproduced
The "Unsupported major/minor version" message means that you are attempting
to run Java code that requires a Java 8 virtual machine on a Java version
that is less than Java 8. It could be a configuration error in your PATH.
It could be an installation error on the computer. It could be that the
The SSH version on the IBM i server, that is where the slave should run, is:
> ssh -V
OpenSSH_6.9p1, OpenSSL 1.0.2r 26 Feb 2019
$
Enabling logging on the slave did not help. All I get is an empty log file
'remoting.log.0', when using the following logger configuration file:
#
Sure I can. Here is the result of the commands executed from a Windows Bash
shell:
traddatz@CNDEA041500 MINGW64 ~
$ ssh raddatz@10.200.36.33 echo "OK"
raddatz@10.200.36.33's password:
OK
traddatz@CNDEA041500 MINGW64 ~
$ ssh -t raddatz@10.200.36.33 echo "OK"
raddatz@10.200.36.33's password:
OK
if the SCM is git, then 'git webhook' can be used.
On 18 Jun 2019 12:02 am, "jayanta deb" wrote:
> u r using which SCM?
>
>
> On 16 Jun 2019 8:03 pm, "Jyc Zuan" wrote:
>
>> Hi,
>>
>>
>> I'm new to the group, I'm not sure if this topic has been already
>> discussed in the past.
>>
>> With
Hi,
We currently have an issue where Jenkins is accepeting weak 1024-bit
Diffie-Hellman keys. We are currently running 2.16.3 on Windows Server
2019. What can I check in the Jenkin's config to solve this? I've been
reading that editing the security files can help but for older versions of
Your help was most welcome. Thank you very much for that. Most likely I will
contact IBM support, now. Maybe they can help. At least it seems that it is not
directly a Jenkins problem.
Again, thank you.
Thomas.
--
You received this message because you are subscribed to the Google Groups
Sorry the auth type drop-down didn't paste. These are the options I see
for the types of credentials to create.
[image: image.png]
On Mon, Jun 17, 2019 at 7:41 PM Jeff wrote:
> I have a server running Jenkins 2.176.1 and am adding a new SonarQube 7.7
> configuration.
>
> I was able to connect
I run out of ideas, I could be some configuration option in
/etc/ssh/sshd_config but I am not sure
--
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, send an email
to
I have a server running Jenkins 2.176.1 and am adding a new SonarQube 7.7
configuration.
I was able to connect to SonarQube anonymously, but have since enabled the
option to force authentication.
I am now in need of adding a User Token (or credentials), but I see no
option for doing so in a way
Note that the issue can be reproduced very easily:
curl -vL --output test.hpi https:
//updates.jenkins.io/download/plugins/workflow-durable-task-step-plugin/2.31/workflow-durable-task-step-plugin.hpi
Sometimes it works, sometimes it does not.
On Monday, 17 June 2019 10:07:06 UTC+2, Damien
Hi,
This morning, we keep having 404 errors when downloading plugins from
https://updates.jenkins.io, for example:
https://updates.jenkins.io/download/plugins/pipeline-milestone-step/1.3.1/pipeline-milestone-step.hpi
(just an example, all kinds of plugins are impacted).
We have this issue
16 matches
Mail list logo
