[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding It's not the same issue. I was not declaring a scripted variable in a declarative stage, and using it in another script bloc in another declarative stage. Declaring the variable at the beginning before opening the pipeline block, fixed the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193525.1536104702000.4645.1569400980550%40Atlassian.JIRA.
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Hello, I'm reproducing these simptoms with 1.62. Could this be the same issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193525.1536104702000.4623.1569399660483%40Atlassian.JIRA.
[JIRA] (JENKINS-59515) Create reference documentation for Docker Workflow plugin
Title: Message Title Ovidiu-Florin Bogdan created an issue Jenkins / JENKINS-59515 Create reference documentation for Docker Workflow plugin Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin Created: 2019-09-24 18:20 Labels: plugin pipeline user-experience plugins Priority: Minor Reporter: Ovidiu-Florin Bogdan The Docker Workflow documentation is structured as a tutorial/introduction on how to use the plugin. Because of this finding all the arguments a function can have, and finding all the functions an object has is difficult, if they are all listed in that documentation. A reference documentation page would greatly help with finding the information needed about how to use the functionality this plugin provides. For example check any of the declarative pipeline steps documentation: https://jenkins.io/doc/pipeline/steps/kubernetes-pipeline-steps/. Add Comment
[JIRA] (JENKINS-53923) Collecting build job results using [.result] property returns null
Title: Message Title
Ovidiu-Florin Bogdan updated an issue
Jenkins / JENKINS-53923
Collecting build job results using [.result] property returns null
Change By:
Ovidiu-Florin Bogdan
I would like to collect all triggered jobs results.My script looks like this: {code:groovy} stage('Integration Tests') { steps { script { def jobs = [:] def childJob def childJobName pipelineIntegrationJobs.each {i -> jobs["${nirvanaMajor}.${nirvanaMinor}_${i}"] = { childJob = build (job: "${nirvanaMajor}.${nirvanaMinor}_${i}", parameters: [ string(name: 'branch', value: "${svnBranch}", description: 'svn repository url'), string(name: 'buildmajor', value: '10', description: 'release major identifier'), string(name: 'buildminor', value: '4', description: 'release minor identifier'), string(name: 'fix', value: "${env.fix}", description: 'fix level'), string(name: 'buildnumber', value: "${env.buildNumber}", description: 'artifacts build number'), string(name: 'revision', value: "${env.buildNumber}", description: 'checkout revision'), string(name: 'joblabel', value: "${pipelineName}", description: "optional job description") ], quietPeriod: 0, propagate: false, wait: true).result}childJobName = "${nirvanaMajor}.${nirvanaMinor}_${i}"results.put(childJobName, childJob) } parallel jobs } } } {code} In the post section of the pipeline I have this: {code:groovy} script { println "" println "Job Status Summary:" results.each{ k, v -> println "${k}:${v}" } println ""} {code} This yields properly the job names but not job statuses: {noformat} 12:22:41 Job Status Summary:[Pipeline] echo12:22:41 10.4_test_foundation_win:null[Pipeline] echo12:22:41 10.4_test_foundation_linux:null[Pipeline] echo12:22:41 10.4_test_client_win:null[Pipeline] echo12:22:41 10.4_test_client_linux:null[Pipeline] echo12:22:41 10.4_test_base_linux:null[Pipeline] echo12:22:41 10.4_test_base_win:null[Pipeline] echo12:22:41 10.4_test_admin_api_win:null[Pipeline] echo12:22:41 10.4_test_admin_api_linux:null[Pipeline] echo12:22:41 10.4_test_admin_api_cluster_win:null[Pipeline] echo12:22:41 10.4_test_admin_api_cluster_linux:null[Pipeline] echo12:22:41 10.4_test_jms_win:null[Pipeline] echo12:22:41 10.4_test_jms_linux:null[Pipeline] echo12:22:41 10.4_test_client_tool_linux:null[Pipeline] echo12:22:41 10.4_test_client_tool_win:null[Pipeline] echo12:22:41 10.4_test_cluster_tool_linux:null[Pipeline] echo12:22:41 10.4_test_cluster_tool_win:null[Pipeline] echo12:22:41 10.4_test_admin_tool_win:null[Pipeline] echo12:22:41 10.4_test_admin_tool_linux:null[Pipeline] echo12:22:41 10.4_test_cpp_linux:null[Pipeline] echo12:22:41 10.4_test_cpp_win:null[Pipeline] echo12:22:41 10.4_test_cpp_osx:null {noformat} Could this be because of [wait: true]? What is wrong?According to the documentation here: https://jenkins.io/doc/pipeline/steps/pipeline-build-step/ I should be able to collect the statuses exactly like this.
[JIRA] (JENKINS-57934) Cannot set URL variable in pipeline: you tried to assign a value to the class 'java.net.URL'
Title: Message Title
Ovidiu-Florin Bogdan created an issue
Jenkins / JENKINS-57934
Cannot set URL variable in pipeline: you tried to assign a value to the class 'java.net.URL'
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-06-10 09:34
Environment:
Jenkins ver. 2.164.3 BlueOcean 1.16.0 Pipeline 2.6
Labels:
pipeline jenkins user-experience
Priority:
Minor
Reporter:
Ovidiu-Florin Bogdan
With the following Jenkinsfile I get an error complaining that you tried to assign a value to the class 'java.net.URL'
pipeline {
environment {
URL = "" class="code-quote" style="color: #009100">"http://foomybar.com"
}
agent any
stages {
stage ("do the thing") {
steps {
sh "echo ${env.URL}"
}
}
}
}
I cannot set the URL environment variable through the environment block.
[JIRA] (JENKINS-57321) Cannot set diferent shebang in shell in Docker in pipeline
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-57321 Re: Cannot set diferent shebang in shell in Docker in pipeline I have tried just now. It works. I didn't think the newline after """ gets into the executed script. Thank you Carlos Sanchez. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199091.1556886771000.19593.1557225900458%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57321) Cannot set diferent shebang in shell in Docker in pipeline
Title: Message Title Ovidiu-Florin Bogdan closed an issue as Not A Defect Jenkins / JENKINS-57321 Cannot set diferent shebang in shell in Docker in pipeline Change By: Ovidiu-Florin Bogdan Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199091.1556886771000.19595.1557225900486%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57321) Cannot set diferent shebang in shell in Docker in pipeline
Title: Message Title
Ovidiu-Florin Bogdan created an issue
Jenkins / JENKINS-57321
Cannot set diferent shebang in shell in Docker in pipeline
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker, pipeline
Created:
2019-05-03 12:32
Environment:
Jenkins 2.164.2 Docker Pipeline Plugin 1.18 Pipeline Plugin 2.6 Blue Ocean Plugin 1.14.0
Labels:
user-experience pipeline
Priority:
Major
Reporter:
Ovidiu-Florin Bogdan
With the following pipeline:
pipeline{
agent none
stages{
stage('deploy') {
agent {
docker {
image 'alpine:latest'
}
}
steps {
sh """
#!/bin/sh
echo foo
"""
}
}
}
}
I get the following output:
[Pipeline] Start of Pipeline (hide)
[Pipeline] stage
[Pipeline] { (deploy)
[Pipeline] node
Running on Auto-launched Jenkins NextGen build slave (i-XXX) in /home/jenkins/workspace/XXX
[Pipeline] {
[Pipeline] checkout
Git checkout logs...
[Pipeline] withEnv
[Pipeline] {
[Pipeline] sh
+
[JIRA] (JENKINS-50218) Conan init fails when using Artifactory plugin
Title: Message Title
Ovidiu-Florin Bogdan edited a comment on JENKINS-50218
Re: Conan init fails when using Artifactory plugin
{{ I've found that this particular error is happening only when the ` * CONAN_USER_HOME ` * env variable is set, or when the home is set via the ` * Artifactory.newConanClient() ` ` * _* userHome ` *_ argument. }} You * MUST * leave the ` * CONAN_USER_HOME ` * unset, and let the Artifactory plugin set it. Otherwise it blows.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50218) Conan init fails when using Artifactory plugin
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-50218 Re: Conan init fails when using Artifactory plugin I've found that this particular error is happening only when the `CONAN_USER_HOME` env variable is set, or when the home is set via the `Artifactory.newConanClient()` `userHome` argument. You MUST leave the `CONAN_USER_HOME` unset, and let the Artifactory plugin set it. Otherwise it blows. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50218) Conan init fails when using Artifactory plugin
Title: Message Title
Ovidiu-Florin Bogdan created an issue
Jenkins / JENKINS-50218
Conan init fails when using Artifactory plugin
Issue Type:
Bug
Assignee:
Eyal Ben Moshe
Components:
artifactory-plugin
Created:
2018-03-16 13:30
Environment:
Jenkins 2.89.4 (using Official jenkins/jenkins:2.89.4 docker image) Artifactory plugin 2.15.0
Labels:
plugin pipeline
Priority:
Blocker
Reporter:
Ovidiu-Florin Bogdan
When using the Artifactory plugin in a Jenkins pipeline, the job fails because the conan_log.log file is missing. I guess this is happening during the initialization of the conan client. Pipeline:
pipeline {
agent none
stages {
stage('Build') {
parallel {
stage('Build Linux') {
agent {
docker {
image 'internalDockerImage'
label 'linux'
}
}
environment {
CONAN_USER_HOME = "${env.WORKSPACE}/conan_home"
}
steps {
script {
def client = Artifactory.newConanClient()
def server_name = client.remote.add server: server, repo: artifactory_repo
client.run(command: "config install https://git-repo/conan-settings/archive/master.zip")
client.run(command: "create --profile Linux-Release . ourteam/unstable")
client.run(command: "create --profile Linux-Debug . ourteam/unstable")
[JIRA] (JENKINS-49697) Single quote in credentials password causing job crash
Title: Message Title Ovidiu-Florin Bogdan closed an issue as Fixed Jenkins / JENKINS-49697 Single quote in credentials password causing job crash Change By: Ovidiu-Florin Bogdan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49697) Single quote in credentials password causing job crash
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-49697 Re: Single quote in credentials password causing job crash Hello, Thank you for such a quick reaction. I've looked over the commit and it seems like it's doing the right thing, but I'm not that familiar with the plugin sources, and I didn't dive in deeper at this moment. I am unable to test at this moment, as I'd need to deploy a test instance of Jenkins, and that would take some time, which I don't have currently. I can't test on our production system, and we've changed the password in question to avoid this issue. Running in Docker is still problematic, but that would be a different issue, for which I'll open another issue when I have the time, to gather a repeatable usecase. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13128) Artifacts Permissions Stripped
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-13128 Re: Artifacts Permissions Stripped If the patch in question is done in the right place, then it seems to me that we are just using a function from ANT to copy the file. Isn't that the function that strips the permissions? I don't see other places that could mess with the file properties. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13128) Artifacts Permissions Stripped
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-13128 Re: Artifacts Permissions Stripped Oleg Nenashev I see that it's stuck in a merge conflict. Even if that conflict would be solved, will that ever get merged in? IMO the proper solution is to simply NOT STRIP file properties, and just keep them as they are. It should assume that the developer who made the job knows what they are doing, and expects things to happen as he set them. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13128) Artifacts Permissions Stripped
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-13128 Re: Artifacts Permissions Stripped Jenkins 2.89.4 here and this issue is present. Workarounds are to archive the artifact, and then extract it, or to reset the permissions after fetching it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19465) Slave hangs while being launched
Title: Message Title Ovidiu-Florin Bogdan edited a comment on JENKINS-19465 Re: Slave hangs while being launched The Support Core plugin gives empty logs for the slave in discussion.The slave node get's no connection attempt via ssh from the master. Getting the slave stack trace is not possible since the slave.jar is not being executed.I'm having no luck with the *nsenter* utility to enter and obtain the master stack trace. I need to restart the container holding master with --privileged to be able to get the stack trace. THis would be rather tricky. - P.S. Symlinking * /dev/urandom * to * /dev/random * on the slave has no affect. I realize now that I should've done this on the master. -*/dev/random* on master has enough entropy, it works just fine. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19465) Slave hangs while being launched
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-19465 Re: Slave hangs while being launched The Support Core plugin gives empty logs for the slave in discussion. The slave node get's no connection attempt via ssh from the master. Getting the slave stack trace is not possible since the slave.jar is not being executed. I'm having no luck with the nsenter utility to enter and obtain the master stack trace. I need to restart the container holding master with --privileged to be able to get the stack trace. THis would be rather tricky. P.S. Symlinking /dev/urandom to /dev/random on the slave has no affect. I realize now that I should've done this on the master. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49718) Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-49718 Re: Adding Artifactory server to conan client fails and PRINTS PASSWORD!! If credentials for Artifactory aren't set in any way, it does something and it crashes Conan: Remote '11836215-a959-46e2-829d-ab8c0cddb688' username: Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/conans/client/command.py", line 1099, in run method(args[0][1:]) File "/usr/local/lib/python3.6/site-packages/conans/client/command.py", line 730, in user password=args.password) File "/usr/local/lib/python3.6/site-packages/conans/client/conan_api.py", line 63, in wrapper return f(*args, **kwargs) File "/usr/local/lib/python3.6/site-packages/conans/client/conan_api.py", line 563, in user self._manager.user(remote, name, password) File "/usr/local/lib/python3.6/site-packages/conans/client/manager.py", line 549, in user name, password = self._user_io.request_login(remote_name=remote, username=name) File "/usr/local/lib/python3.6/site-packages/conans/client/userio.py", line 30, in request_login user_input = self.get_username(remote_name) File "/usr/local/lib/python3.6/site-packages/conans/client/userio.py", line 44, in get_username return self._get_env_username(remote_name) or raw_input() EOFError: EOF when reading a line ERROR: EOF when reading a line Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49718) Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
Title: Message Title
Ovidiu-Florin Bogdan commented on JENKINS-49718
Re: Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
The exact same thing happens if not using the Credentials plugin and provided the user and password in the corresponding fiends of the Artifactory server settings.
ERROR: HTTPSConnectionPool(host='conan.bintray.com', port=443): Max retries exceeded with url: /v1/users/authenticate (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 110] Connection timed out',))
Unable to connect to conan-center=https://conan.bintray.com
sh: : No such file or directory
1. It should not show the password. 2. it should not try to connect to conan-center, especially since the Enable push to Bintray is disabled.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49718) Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
Title: Message Title
Ovidiu-Florin Bogdan created an issue
Jenkins / JENKINS-49718
Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
Issue Type:
Bug
Assignee:
Eyal Ben Moshe
Components:
artifactory-plugin
Created:
2018-02-23 12:47
Environment:
Jenkins 2.89.3 from the Docker image jenkins/jenkins:2.89.3 The build is running inside a Docker container.
Labels:
plugin jenkins pipeline security
Priority:
Critical
Reporter:
Ovidiu-Florin Bogdan
When adding the Artifactory server to Conan as a remote, it fails with rejecting the username and password for conan-center (the default conan remote) and then prints the credential password on the screen by saying that it's an unknown command. Jenkinsfile follows:
def LINUX_DOCKER_IMAGE = ""
def ARTIFACTORY_NAME = ""
def ARTIFACTORY_REPO = ""
String setup_conan = "config install "
node('linux') {
stage("Get Sources"){
checkout scm
}
docker.image(LINUX_DOCKER_IMAGE) {
def server = Artifactory.server ARTIFACTORY_NAME
def client = Artifactory.newConanClient userHome: "/tmp/conan_home"
def serverName = client.remote.add server: server, repo: ARTIFACTORY_REPO
stage("Setup Conan") {
client.run(command: setup_conan)
}
stage("Build package") {
client.run(comnand: "create --profile Linux-Release . foo/bar")
}
stage("Upload package") {
String command = "upload -r ${serve
[JIRA] (JENKINS-19465) Slave hangs while being launched
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-19465 Re: Slave hangs while being launched I'd love to. How do I get them? can you point me to some docs on this? I have both Jenkins Master and Slave running in Docker containers. Now it works because I've changed the slave IP, triggered a connection that failed, then switched back the IP and it worked. For the moment I've used Sergii Ovcharenko's solution and linked /dev/urandom to /dev/random, but I can change it back if you tell me how to get the stacktraces from a running Jenkins. Remember I don't have any errors, no messages in the node connection log. Just the spinning gif thingy. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19465) Slave hangs while being launched
Title: Message Title Ovidiu-Florin Bogdan reopened an issue This issue is still happening on SSH slaves 1.25.1 with Jenkins 2.89.3. The curious thing is that I only see it on one of our slaves. Jenkins / JENKINS-19465 Slave hangs while being launched Change By: Ovidiu-Florin Bogdan Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+uns
[JIRA] (JENKINS-19465) Slave hangs while being launched
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-19465 Re: Slave hangs while being launched I"m still seeing this issue in SSh slaves plugin 1.25.1 with Jenkins 2.89.3. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49697) Single quote in credentials password causing job crash
Title: Message Title Ovidiu-Florin Bogdan created an issue Jenkins / JENKINS-49697 Single quote in credentials password causing job crash Issue Type: Bug Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2018-02-22 13:42 Environment: Jenkins 2.89.3 From the official Docker image: jenkins/jenkins:2.89.3 Labels: plugin jenkins Priority: Critical Reporter: Ovidiu-Florin Bogdan Having a (or multiple) single quote(s) in the password of the user used by Artifactory causes the job to crash when using the Conan package manager during the ConanAddUser step. This is the classic SQL injection security hole. I just caught it because I'm running the job in a Docker contaier. I've looked through the plugin code and I found that the single and probably best place where this can be escaped is in https://github.com/JFrogDev/jenkins-artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/util/plugins/PluginsUtils.java#L67 Or just before https://github.com/JFrogDev/jenkins-artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/util/Credentials.java#L43 Since after this the password is scrambled and cannot be escaped anymore. In my desperation I've also asked on StackOverflow about this: https://stackoverflow.com/questions/48907089/jenkins-pipeline-with-docker-and-artifactory
