[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Amit Dar commented on JENKINS-56874 Re: Log4j2.xml file in the plugin causes unexpected errors I'm experiencing the same issue. Jenkins 2.164.3 with micro focus tools 5.8. 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.198543.1554368545000.18420.1559452920192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29833) Gitcolony notification failed - java.lang.IllegalArgumentException: Invalid url:
Title: Message Title VENKATESH ILANGO commented on JENKINS-29833 Re: Gitcolony notification failed - java.lang.IllegalArgumentException: Invalid url: https://github.com/jenkinsci/gitcolony-plugin/pull/1 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.164410.1438872888000.18417.1559451181287%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42930) Use System proxy when available
Title: Message Title Basil Crow commented on JENKINS-42930 Re: Use System proxy when available I took a shot at implementing this in #105. That change uses the SystemDefaultHttpClient class, which supports the following Java properties: The following system properties are taken into account by this class: ssl.TrustManagerFactory.algorithm javax.net.ssl.trustStoreType javax.net.ssl.trustStore javax.net.ssl.trustStoreProvider javax.net.ssl.trustStorePassword java.home ssl.KeyManagerFactory.algorithm javax.net.ssl.keyStoreType javax.net.ssl.keyStore javax.net.ssl.keyStoreProvider javax.net.ssl.keyStorePassword http.proxyHost http.proxyPort https.proxyHost https.proxyPort http.nonProxyHosts http.keepAlive http.maxConnections The semantics of these properties are defined here. I don't have a proxy server against which to test this. Is anyone willing to try out my PR against their proxy server and report back with the results? Add Comment This message was sent
[JIRA] (JENKINS-57810) Pipeline build succeeded but the file was not sent to the ssh target host
Title: Message Title joss.ji joss commented on JENKINS-57810 Re: Pipeline build succeeded but the file was not sent to the ssh target host My analysis should be my environment configuration problem I followed the steps of docker.io/doc. At present, the environment configuration of jenkins in the documentation seems to be basically not mentioned (for example, maven, git and other content configuration, can be directly called by wizard or docker, it is actually very convenient) Therefore, my configuration can be understood as blank (only a few places in ssh configuration, including jdk are not configured with global tools, will there be problems in this place) But if there is a problem with the configuration, how to build successfully, I call docker image nodejs to construct a successful one, indicating that the build part of the previous stage is normal. All I am confused 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.199761.1559438377000.18408.1559440800125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48247) Swarm Client should not restart when labelsFile changes
Title: Message Title Basil Crow commented on JENKINS-48247 Re: Swarm Client should not restart when labelsFile changes Can you try using -disableClientsUniqueId as a temporary workaround? 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.186828.151180704.18405.1559439000243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45295) Swarm Client should update labels on the fly when labelsFile changes
Title: Message Title Basil Crow commented on JENKINS-45295 Re: Swarm Client should update labels on the fly when labelsFile changes Can you try using -disableClientsUniqueId as a temporary workaround? 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.183432.149918364.18403.1559439000212%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57810) Pipeline build succeeded but the file was not sent to the ssh target host
Title: Message Title
joss.ji joss commented on JENKINS-57810
Re: Pipeline build succeeded but the file was not sent to the ssh target host
log:
Started by user norway.admin
> git rev-parse --is-inside-work-tree # timeout=10
Setting origin to http://git.inorway.cn/norwayERP/norway_ui_pc.git
> git config remote.origin.url http://git.inorway.cn/norwayERP/norway_ui_pc.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
> git --version # timeout=10
> git config --get remote.origin.url # timeout=10
using GIT_ASKPASS to set credentials Git username/password for http://git.inorway.cn/gogs/wherecar_common_v2.git
> git fetch --tags --force --progress origin +refs/heads/*:refs/remotes/origin/*
Seen branch in repository origin/develop
Seen branch in repository origin/hotfix
Seen branch in repository origin/master
Seen 3 remote branches
Obtained Jenkinsfile from e03421f32b29b16ce096923f2b92ec4f76c77a43
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /var/jenkins_home/workspace/norway_ui_pc_develop
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential git:bc02b36ff5a6e631fe243c0f30104683a745ce242b7e69cddfa79f26a69db1bf
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://git.inorway.cn/norwayERP/norway_ui_pc.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching without tags
Fetching upstream changes from http://git.inorway.cn/norwayERP/norway_ui_pc.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials Git username/password for http://git.inorway.cn/gogs/wherecar_common_v2.git
> git fetch --no-tags --force --progress http://git.inorway.cn/norwayERP/norway_ui_pc.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision e03421f32b29b16ce096923f2b92ec4f76c77a43 (develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f e03421f32b29b16ce096923f2b92ec4f76c77a43
> git branch -a -v --no-abbrev # timeout=10
> git branch -D develop # timeout=10
> git checkout -b develop e03421f32b29b16ce096923f2b92ec4f76c77a43
Commit message: "jenkins config: ssh"
> git rev-list --no-walk e03421f32b29b16ce096923f2b92ec4f76c77a43 # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] sh
+ docker inspect -f . node_cnpm:8.0.1
.
[Pipeline] withDockerContainer
Jenkins seems to be running inside container 5c9cd7c9f6d6c43857db56b06164983ab199a7b0208fc2b34feecbd1848348a3
$ docker run -t -d -u 0:0 -p 3000:3000 -w /var/jenkins_home/workspace/norway_ui_pc_develop --volumes-from 5c9cd7c9f6d6c43857db56b06164983ab199a7b0208fc2b34feecbd1848348a3 -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e node_cnpm:8.0.1 cat
$ docker top 6b4fc4c52c127c7645a1a4459fb5332c8a9af00fe15bc5db939c8e42c4aa56d2 -eo pid,comm
[Pipeline] {
[Pipeline]
[JIRA] (JENKINS-57810) Pipeline build succeeded but the file was not sent to the ssh target host
Title: Message Title joss.ji joss commented on JENKINS-57810 Re: Pipeline build succeeded but the file was not sent to the ssh target host 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.199761.1559438377000.18397.1559438640213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57810) Pipeline build succeeded but the file was not sent to the ssh target host
Title: Message Title joss.ji joss updated an issue Jenkins / JENKINS-57810 Pipeline build succeeded but the file was not sent to the ssh target host Change By: joss.ji joss Attachment: image-2019-06-02-09-23-06-711.png 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.199761.1559438377000.18395.1559438640187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57810) Pipeline build succeeded but the file was not sent to the ssh target host
Title: Message Title
joss.ji joss updated an issue
Jenkins / JENKINS-57810
Pipeline build succeeded but the file was not sent to the ssh target host
Change By:
joss.ji joss
I am learning jenkins, there is a problem that has not been resolved for several weeks, as follows:My environmentNote: My configuration is basically configured with reference to the contents of jenkins.io/doc, so I found that the latest file does not have a lot of configuration parameters configured, basically solved with pipeline syntax.Host: docker in host: 192.168.9.16 (node: master)Target host host:192.168.9.23 (lable: prod.9.23) task:Use nodejs npm build (has been successful, success will generate dist/* under path)Send the successful result to the specified path /data/www/mytest on the target hostproblem:The display is successful, but the target host does not get the file.How to execute the host command in the docker environment, or execute the remote host command? my jenkinsfile:{code:java}pipeline {agent {docker {image 'node_cnpm:8.0.1'args '-p 3000:3000'}}environment {CI = 'true'}stages {stage('Build') {steps {sh 'node -v'sh 'npm -v'sh 'cnpm -v'sh 'pwd'sh 'ls'sh 'chmod -R 777 ./'sh 'rm -rf node_modules/'sh 'ls'sh 'npm cache clean -f'sh 'cnpm install 'sh 'npm run test'}} stage('deploy') {steps {sshPublisher(publishers: [sshPublisherDesc(configName: 'prod.9.23', transfers: [sshTransfer(cleanRemote: false, excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '/data/www/test.erp.ui.pc', remoteDirectorySDF: false, removePrefix: 'dist', sourceFiles: 'dist/*.*')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)])}}}}{code}
Add Comment
[JIRA] (JENKINS-57810) Pipeline build succeeded but the file was not sent to the ssh target host
Title: Message Title joss.ji joss created an issue Jenkins / JENKINS-57810 Pipeline build succeeded but the file was not sent to the ssh target host Issue Type: Bug Assignee: Matt Sicker Components: ssh-credentials-plugin Created: 2019-06-02 01:19 Environment: Centos 7.4 Docker jenkinsci/blueocean:latest Code is in git (gogs) Chrome Nginx (docker by latest) My jenkins_home is mounted to the host under /data/docker/jenkins/jenkins_home Jenkins docker run user root The tool Publish over SSH is used under jenkins (if you don't use this method, please tell me which methods are simpler) The host and the target host have implemented ssh secret login (even after I did the ssh secret configuration after the docker exec -it jenkins bash, the same is not possible) Labels: ssh Priority: Major Reporter: joss.ji joss I am learning jenkins, there is a problem that has not been resolved for several weeks, as follows: My environment Note: My configuration is basically configured with reference to the contents of jenkins.io/doc, so I found that the latest file does not have a lot of configuration parameters configured, basically solved with pipeline syntax. Host: docker in host: 192.168.9.16 (node: master) Target host host:192.168.9.23 task: Use nodejs npm build (has been successful, success will generate dist/* under path) Send the successful result to the specified path /data/www/mytest on the target host problem: The display is successful, but the target host does not get the file. How to execute the host
[JIRA] (JENKINS-34337) Job Naming Strategy doesn't enforce restriction on rename
Title: Message Title James Milligan commented on JENKINS-34337 Re: Job Naming Strategy doesn't enforce restriction on rename I've started taking a look at this as my first foray into Jenkins. Looks like it's still a defect with recent versions (2.11 of the plugin and 2.177 of Jenkins). After some digging, I think there's already an old PR that just needs some tidying up and bringing up to date: https://github.com/jenkinsci/role-strategy-plugin/pull/16 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.169895.1461076986000.18387.1559428020144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34337) Job Naming Strategy doesn't enforce restriction on rename
Title: Message Title James Milligan assigned an issue to James Milligan Jenkins / JENKINS-34337 Job Naming Strategy doesn't enforce restriction on rename Change By: James Milligan Assignee: James Milligan 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.169895.1461076986000.18381.1559427720368%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34337) Job Naming Strategy doesn't enforce restriction on rename
Title: Message Title James Milligan started work on JENKINS-34337 Change By: James Milligan Status: Open In Progress 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.169895.1461076986000.18383.1559427720393%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39443) Sanitise description string as it may contains troublesome chars
Title: Message Title Basil Crow closed an issue as Cannot Reproduce This is no longer an issue in recent versions of Swarm client and Jenkins core. See the test added in #100. Jenkins / JENKINS-39443 Sanitise description string as it may contains troublesome chars Change By: Basil Crow Status: Open Closed Resolution: Cannot Reproduce 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.175975.1478091214000.18375.1559424120306%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50970) SLF4J logging not working in Swarm client
Title: Message Title Basil Crow updated JENKINS-50970 Fixed in #98. I've also added documentation for the logging subsystem in #99. Jenkins / JENKINS-50970 SLF4J logging not working in Swarm client Change By: Basil Crow Status: Open Fixed but Unreleased Resolution: Fixed Released As: 3.17 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.190118.1524590516000.18371.1559422860336%40Atlassian.JIRA. For more
[JIRA] (JENKINS-50970) SLF4J logging not working in Swarm client
Title: Message Title Basil Crow assigned an issue to Basil Crow Jenkins / JENKINS-50970 SLF4J logging not working in Swarm client Change By: Basil Crow Assignee: Basil Crow 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.190118.1524590516000.18367.1559419560154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50970) SLF4J logging not working in Swarm client
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-50970 SLF4J logging not working in Swarm client Change By: Basil Crow Summary: SLF4J logging not working in Jenkins Swarm plugin client 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.190118.1524590516000.18363.1559414820192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25421) Allow Swarm client to be used when CSRF is disabled
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-25421 Allow Swarm client to be used when CSRF is disabled Change By: Basil Crow Priority: Minor Major 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.158985.1415054026000.18352.1559414760863%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39443) Sanitise description string as it may contains troublesome chars
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-39443 Sanitise description string as it may contains troublesome chars Change By: Basil Crow Priority: Minor Major 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.175975.1478091214000.18350.1559414760821%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41694) Slave can't connect to master using swarm swarm-client-2.2
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-41694 Slave can't connect to master using swarm swarm-client-2.2 Change By: Basil Crow Priority: Major Minor 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.178501.1486059556000.18346.1559414700212%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43119) Want a way to monitor Swarm client via TCP or UDP
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-43119 Want a way to monitor Swarm client via TCP or UDP Change By: Basil Crow Priority: Minor Major 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.180233.1490581837000.18341.1559414640630%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44115) Enable Remoting work dir by default in Swarm Plugin
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-44115 Enable Remoting work dir by default in Swarm Plugin Change By: Basil Crow Priority: Minor Major 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.181741.1494227581000.18339.1559414640603%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47281) swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects
Title: Message Title Basil Crow closed an issue as Duplicate This looks like a duplicate of JENKINS-25421. The workaround is to enable CSRF on the Jenkins master. Jenkins / JENKINS-47281 swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects Change By: Basil Crow Status: Open Closed Resolution: Duplicate 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.185701.1507154346000.18333.1559414460224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36667) swarm client 2.1 unable to connect to jenkins instance
Title: Message Title Basil Crow closed an issue as Duplicate This looks like a duplicate of JENKINS-25421. The workaround is to enable CSRF on the Jenkins master. Jenkins / JENKINS-36667 swarm client 2.1 unable to connect to jenkins instance Change By: Basil Crow Status: Open Closed Resolution: Duplicate 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.172699.1468434521000.18329.1559414401710%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25421) Allow Swarm client to be used when CSRF is disabled
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-25421 Allow Swarm client to be used when CSRF is disabled Change By: Basil Crow Summary: Allow Swarm plugin requires "Prevent Cross Site Request Forgery exploits" client to be enabled. used when CSRF is disabled 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.158985.1415054026000.18316.1559414401450%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25421) Allow Swarm client to be used when CSRF is disabled
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-25421 Allow Swarm client to be used when CSRF is disabled Change By: Basil Crow Issue Type: Bug New Feature 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.158985.1415054026000.18327.1559414401687%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45295) Swarm Client should update labels on the fly when labelsFile changes
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-45295 Swarm Client should update labels on the fly when labelsFile changes Change By: Basil Crow Summary: Swarm Client shutting down should update labels on the fly when labelsFile changes 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.183432.149918364.18304.1559414160155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45295) Swarm Client shutting down when labelsFile changes
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-45295 Swarm Client shutting down when labelsFile changes Change By: Basil Crow Issue Type: Bug New Feature 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.183432.149918364.18301.1559414100240%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40842) swarm 2.2 SEGV w/ java-1.8.0-openjdk-1.8.0.111-0.b15.el6_8.x86_64
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-40842 swarm 2.2 SEGV w/ java-1.8.0-openjdk-1.8.0.111-0.b15.el6_8.x86_64 Change By: Basil Crow Priority: Critical Major 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.177557.1483633759000.18296.1559414040588%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41694) Slave can't connect to master using swarm swarm-client-2.2
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-41694 Slave can't connect to master using swarm swarm-client-2.2 Change By: Basil Crow Priority: Critical Major 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.178501.1486059556000.18298.1559414040617%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49730) JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-49730 JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER Change By: Basil Crow Priority: Critical Minor 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.188672.1519568304000.18286.1559413920464%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47866) Swarm Slave Appears online on Jenkins UI though the instance has been terminated
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-47866 Swarm Slave Appears online on Jenkins UI though the instance has been terminated Change By: Basil Crow Priority: Major Minor 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.186378.1510077141000.18288.1559413920489%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35151) Swarm matrix authorization no show
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-35151 Swarm matrix authorization no show Change By: Basil Crow Priority: Critical Minor 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.170835.1464267101000.18281.1559413740250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43119) Want a way to monitor Swarm client via TCP or UDP
Title: Message Title Basil Crow commented on JENKINS-43119 Re: Want a way to monitor Swarm client via TCP or UDP Hey Vikas Kumar, there isn't a way to do this as of today. Pull requests are welcome! 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.180233.1490581837000.18277.1559413560117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43119) Want a way to monitor Swarm client via TCP or UDP
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-43119 Want a way to monitor Swarm client via TCP or UDP Change By: Basil Crow Issue Type: Bug New Feature 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.180233.1490581837000.18273.1559413500441%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43119) Want a way to monitor Swarm client via TCP or UDP
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-43119 Want a way to monitor Swarm client via TCP or UDP Change By: Basil Crow Summary: Monitor Swam Want a way to monitor Swarm client on some port ? via TCP or UDP 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.180233.1490581837000.18271.1559413500399%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55256) ssh-agent in pipeline leaves defunct processes on swarm client
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-55256 ssh-agent in pipeline leaves defunct processes on swarm client Change By: Basil Crow Component/s: swarm-plugin 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.196339.1545212313000.18265.1559413260323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55256) ssh-agent in pipeline leaves defunct processes on swarm client
Title: Message Title Basil Crow commented on JENKINS-55256 Re: ssh-agent in pipeline leaves defunct processes on swarm client This bug doesn't seem to be specific to the SSH slaves plugin or the Swarm Plugin. I'm reassigning this to the SSH Agent plugin component. 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.196339.1545212313000.18263.1559413260286%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17144) Add support for private keys for authentiation
Title: Message Title Basil Crow commented on JENKINS-17144 Re: Add support for private keys for authentiation While a workaround exists, I think the user experience could be improved, or at least better documented. I'll have to think more about how best to achieve this. 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.147975.1362973544000.18252.1559413080189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20668) Persist Jenkins swarm slaves when they go offline
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-20668 Persist Jenkins swarm slaves when they go offline Change By: Basil Crow Priority: Major Minor 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.152188.1384943874000.18237.1559413021385%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9639) Let Swarm Client load settings from property files
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-9639 Let Swarm Client load settings from property files Change By: Basil Crow Priority: Major Minor 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.139813.1305007185000.18247.1559413021555%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42492) swarm plugin always adds the "swarm" label to all nodes by default.
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-42492 swarm plugin always adds the "swarm" label to all nodes by default. Change By: Basil Crow Priority: Minor Trivial 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.179419.1488795572000.18249.1559413021588%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10267) Allow tunnel to master from swarm nodes
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-10267 Allow tunnel to master from swarm nodes Change By: Basil Crow Priority: Major Minor 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.140455.1310159929000.18240.1559413021438%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39000) Provide way to set or disable slave timeout
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-39000 Provide way to set or disable slave timeout Change By: Basil Crow Priority: Major Minor 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.175418.1476472352000.18224.1559412961211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17144) Add support for private keys for authentiation
Title: Message Title Basil Crow commented on JENKINS-17144 Re: Add support for private keys for authentiation See the workaround in JENKINS-48708. 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.147975.1362973544000.18216.1559412960950%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42930) Use System proxy when available
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-42930 Use System proxy when available Change By: Basil Crow Priority: Minor Major 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.179940.1490008795000.18222.1559412961145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48708) Username Password for OAuth based authentication
Title: Message Title Basil Crow closed an issue as Duplicate Duplicate of JENKINS-17144. Jenkins / JENKINS-48708 Username Password for OAuth based authentication Change By: Basil Crow Status: Open Closed Resolution: Duplicate 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.187410.1514290669000.18203.1559412900437%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47281) swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-47281 swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects Change By: Basil Crow Issue Type: New Feature Bug 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.185701.1507154346000.18201.1559412780273%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9639) Let Swarm Client load settings from property files
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-9639 Let Swarm Client load settings from property files Change By: Basil Crow Summary: Let Swarm CLI Client load settings from property files 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.139813.1305007185000.18195.1559412540442%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10267) Allow tunnel to master from swarm nodes
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-10267 Allow tunnel to master from swarm nodes Change By: Basil Crow Summary: Allow tunnel to master from " swarm " nodes 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.140455.1310159929000.18197.1559412540469%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41694) Slave can't connect to master using swarm swarm-client-2.2
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-41694 Slave can't connect to master using swarm swarm-client-2.2 Change By: Basil Crow Assignee: Benjamin Marosan 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.178501.1486059556000.18187.1559412480419%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39820) The server rejected the connection: None of the protocols were accepted
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-39820 The server rejected the connection: None of the protocols were accepted Change By: Basil Crow Assignee: halasson simatupang 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.176415.1479387275000.18184.1559412480363%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48477) Swarm client should use remoting version of master
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-48477 Swarm client should use remoting version of master Change By: Basil Crow Issue Type: Improvement New Feature 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.187086.1512986195000.18169.1559412361008%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48248) pidFile switch should prevent launching of multiple copies
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-48248 pidFile switch should prevent launching of multiple copies Change By: Basil Crow Issue Type: Improvement New Feature 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.186829.1511808585000.18166.1559412360974%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48708) Username Password for OAuth based authentication
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-48708 Username Password for OAuth based authentication Change By: Basil Crow Issue Type: Improvement New Feature 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.187410.1514290669000.18175.1559412361071%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50970) SLF4J logging not working in Jenkins Swarm plugin
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-50970 SLF4J logging not working in Jenkins Swarm plugin Change By: Basil Crow Issue Type: Improvement Bug 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.190118.1524590516000.18177.1559412361091%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31084) Swarm slaves should allow some level of control interaction
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-31084 Swarm slaves should allow some level of control interaction Change By: Basil Crow Issue Type: Improvement New Feature 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.165731.1445439406000.18157.1559412302040%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42492) swarm plugin always adds the "swarm" label to all nodes by default.
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-42492 swarm plugin always adds the "swarm" label to all nodes by default. Change By: Basil Crow Issue Type: Improvement New Feature 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.179419.1488795572000.18160.1559412302075%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17144) Add support for private keys for authentiation
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-17144 Add support for private keys for authentiation Change By: Basil Crow Issue Type: Improvement New Feature 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.147975.1362973544000.18143.1559412301794%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47281) swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-47281 swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects Change By: Basil Crow Issue Type: Improvement New Feature 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.185701.1507154346000.18162.1559412302094%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20668) Persist Jenkins swarm slaves when they go offline
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-20668 Persist Jenkins swarm slaves when they go offline Change By: Basil Crow Issue Type: Improvement New Feature 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.152188.1384943874000.18154.1559412301981%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10267) Allow tunnel to master from "swarm" nodes
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-10267 Allow tunnel to master from "swarm" nodes Change By: Basil Crow Issue Type: Improvement New Feature Affects Version/s: current 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.140455.1310159929000.18133.1559412240278%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48247) Swarm Client should not restart when labelsFile changes
Title: Message Title Basil Crow closed an issue as Fixed Duplicate of JENKINS-45295. Jenkins / JENKINS-48247 Swarm Client should not restart when labelsFile changes Change By: Basil Crow Status: Open Closed Resolution: Fixed 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.186828.151180704.18130.1559412120236%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47391) Swarm plugin with -labelsFile does not delete removed labels
Title: Message Title Basil Crow updated JENKINS-47391 This was fixed in #75 and released in 3.15. Jenkins / JENKINS-47391 Swarm plugin with -labelsFile does not delete removed labels Change By: Basil Crow Status: In Review Resolved Resolution: Fixed Released As: 3.15 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.185829.1507743288000.18128.1559412000356%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-47391) Swarm plugin with -labelsFile does not delete removed labels
Title: Message Title Basil Crow started work on JENKINS-47391 Change By: Basil Crow Status: Open In Progress 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.185829.1507743288000.18122.1559411940336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47391) Swarm plugin with -labelsFile does not delete removed labels
Title: Message Title Basil Crow updated JENKINS-47391 Jenkins / JENKINS-47391 Swarm plugin with -labelsFile does not delete removed labels Change By: Basil Crow Status: In Progress Review 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.185829.1507743288000.18124.1559411940374%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52878) API key authentication within swarm/agent
Title: Message Title Basil Crow updated JENKINS-52878 Jenkins / JENKINS-52878 API key authentication within swarm/agent Change By: Basil Crow Status: Fixed but Unreleased Closed Resolution: Done 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.192815.1533306035000.18119.1559411820274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39360) Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins
Title: Message Title Basil Crow updated JENKINS-39360 Fixed in #62 and released in 3.10. You can now download the Swarm Client from the Jenkins master via: http:///swarm/swarm-client.jar Jenkins / JENKINS-39360 Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins Change By: Basil Crow Status: In Review Resolved Resolution: Fixed 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.175881.1477678289000.18114.1559411700284%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39360) Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins
Title: Message Title Basil Crow started work on JENKINS-39360 Change By: Basil Crow Status: Open In Progress 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.175881.1477678289000.18108.1559411580503%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39360) Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins
Title: Message Title Basil Crow updated JENKINS-39360 Jenkins / JENKINS-39360 Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins Change By: Basil Crow Status: In Progress Review 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.175881.1477678289000.18112.1559411580616%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31514) Jenkins Swarm slave goes remains offline after master restarts
Title: Message Title Basil Crow closed an issue as Not A Defect Jenkins / JENKINS-31514 Jenkins Swarm slave goes remains offline after master restarts Change By: Basil Crow 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.166424.1447318889000.18102.1559411160302%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41937) update center still reports 2.2 as latest release
Title: Message Title Basil Crow commented on JENKINS-41937 Re: update center still reports 2.2 as latest release Both the Update Center and the Jenkins wiki now correctly show the latest version of the Swarm Plugin as 3.16. 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.178793.1486746279000.18097.1559410980337%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41937) update center still reports 2.2 as latest release
Title: Message Title Basil Crow closed an issue as Cannot Reproduce Jenkins / JENKINS-41937 update center still reports 2.2 as latest release Change By: Basil Crow Status: Open Closed Resolution: Cannot Reproduce 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.178793.1486746279000.18099.1559410980360%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title Vasily Yanov updated JENKINS-57779 Jenkins / JENKINS-57779 Bitbucket plugin JSONObject["username"] not found Change By: Vasily Yanov Status: Fixed but Unreleased Closed Released As: https://github.com/jenkinsci/bitbucket-plugin/releases/tag/bitbucket-1.1.9 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.199726.1559290809000.18087.1559408940953%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Vasily Yanov updated an issue Jenkins / JENKINS-53946 Bitbucket plugin unable to parse a Pull Request JSON Object Change By: Vasily Yanov Released As: https://github.com/jenkinsci/bitbucket-plugin/releases/tag/bitbucket-1.1.9 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.194548.1539012261000.18086.1559408940939%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Vasily Yanov reopened an issue Sorry. Wrong window Jenkins / JENKINS-53946 Bitbucket plugin unable to parse a Pull Request JSON Object Change By: Vasily Yanov Resolution: Fixed Status: Closed Reopened 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.194548.1539012261000.18081.1559408940859%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Vasily Yanov updated JENKINS-53946 Jenkins / JENKINS-53946 Bitbucket plugin unable to parse a Pull Request JSON Object Change By: Vasily Yanov Status: Closed Fixed but Unreleased Released As: https://github.com/jenkinsci/bitbucket-plugin/releases/tag/bitbucket-1.1.9 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.194548.1539012261000.18071.1559408880736%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Vasily Yanov updated JENKINS-53946 Jenkins / JENKINS-53946 Bitbucket plugin unable to parse a Pull Request JSON Object Change By: Vasily Yanov Status: Fixed but Unreleased Closed 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.194548.1539012261000.18073.1559408880836%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title Vasily Yanov updated JENKINS-57779 Jenkins / JENKINS-57779 Bitbucket plugin JSONObject["username"] not found Change By: Vasily Yanov Status: Open Fixed but Unreleased Resolution: Fixed 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.199726.1559290809000.18059.1559408760822%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57779) Bitbucket plugin JSONObject["username"] not found
Title: Message Title Vasily Yanov commented on JENKINS-57779 Re: Bitbucket plugin JSONObject["username"] not found Looks like the issue is solved. Thank you for quick turnaround! 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.199726.1559290809000.18058.1559408760811%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12512) Text Finder plugin help could be more informative
Title: Message Title Basil Crow updated JENKINS-12512 Resolved in #28. Jenkins / JENKINS-12512 Text Finder plugin help could be more informative Change By: Basil Crow Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jenkinsci/text-finder-plugin/pull/28 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.142878.1327423122000.18049.1559406720406%40Atlassian.JIRA. For more
[JIRA] (JENKINS-42827) html not rendered
Title: Message Title Basil Crow closed an issue as Cannot Reproduce Jenkins / JENKINS-42827 html not rendered Change By: Basil Crow Status: Open Closed Resolution: Cannot Reproduce 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.179827.1489636482000.18046.1559404200398%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42827) html not rendered
Title: Message Title Basil Crow commented on JENKINS-42827 Re: html not rendered I can't reproduce this on Jenkins 2.150.1 with the latest version of Text Finder (1.11). Can you please upgrade to Text Finder 1.11 and Jenkins 2.150 or later and see if the issue is resolved? 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.179827.1489636482000.18043.1559404200347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42827) html not rendered
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-42827 html not rendered Change By: Basil Crow Attachment: freestyle.png Attachment: pipeline.png 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.179827.1489636482000.18040.1559404140160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24862) Allow Textfinder to optionally change failed builds to unstable
Title: Message Title Basil Crow closed an issue as Duplicate Unfortunately, Jenkins doesn't support this. See JENKINS-19641 and JENKINS-25350. Jenkins / JENKINS-24862 Allow Textfinder to optionally change failed builds to unstable Change By: Basil Crow Status: Open Closed Resolution: Duplicate 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.157693.141161000.18036.1559403900296%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25350) Text finder plugin cannot change test result from Failure to UNSTABLE
Title: Message Title Basil Crow closed an issue as Duplicate Jenkins / JENKINS-25350 Text finder plugin cannot change test result from Failure to UNSTABLE Change By: Basil Crow Status: Open Closed Resolution: Duplicate 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.158913.1414540281000.18032.1559403840521%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53191) Release a new plugin version
Title: Message Title Basil Crow commented on JENKINS-53191 Re: Release a new plugin version Released as 1.11 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.193217.1534952927000.18029.1559403720090%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53191) Release a new plugin version
Title: Message Title Basil Crow updated JENKINS-53191 Jenkins / JENKINS-53191 Release a new plugin version Change By: Basil Crow Status: Open Fixed but Unreleased Resolution: Fixed Released As: 1.11 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.193217.1534952927000.18025.1559403660319%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53191) Release a new plugin version
Title: Message Title Basil Crow updated JENKINS-53191 See the documentation for usage instructions. Jenkins / JENKINS-53191 Release a new plugin version Change By: Basil Crow Status: Fixed but Unreleased Resolved 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.193217.1534952927000.18027.1559403660343%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34983) Make text finder plugin compatible with pipeline
Title: Message Title Basil Crow updated JENKINS-34983 See the documentation for usage information. Jenkins / JENKINS-34983 Make text finder plugin compatible with pipeline Change By: Basil Crow Status: Fixed but Unreleased Resolved 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.170654.1463745823000.18023.1559403602860%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34983) Make text finder plugin compatible with pipeline
Title: Message Title Basil Crow updated JENKINS-34983 Jenkins / JENKINS-34983 Make text finder plugin compatible with pipeline Change By: Basil Crow Status: Open Fixed but Unreleased Resolution: Fixed Released As: 1.11 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.170654.1463745823000.17995.1559403601297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34983) Make text finder plugin compatible with pipeline
Title: Message Title Basil Crow stopped work on JENKINS-34983 Change By: Basil Crow Status: In Progress Open 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.170654.1463745823000.17980.1559403542598%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34983) Make text finder plugin compatible with pipeline
Title: Message Title Basil Crow updated JENKINS-34983 Jenkins / JENKINS-34983 Make text finder plugin compatible with pipeline Change By: Basil Crow Status: In Review Progress 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.170654.1463745823000.17978.1559403542545%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34983) Make text finder plugin compatible with pipeline
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-34983 Make text finder plugin compatible with pipeline Change By: Basil Crow Issue Type: Improvement Story 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.170654.1463745823000.17963.1559403542293%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-57347 Re: Performance degradation running pipeline step sh on remote agents I've used the Docker compose environment defined on https://github.com/kuisathaverat/jenkins-issues/tree/master/JENKINS-57347 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.199122.1557175676000.17948.1559400780182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-57347 Performance degradation running pipeline step sh on remote agents Change By: Ivan Fernandez Calvo 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.199122.1557175676000.17946.1559399640279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-57347
Re: Performance degradation running pipeline step sh on remote agents
yep, something happens on 2.150.2, it does not have a consistent time of execution it differed about 5-10 secs, but it is not related with the ssh-slaves plugin and it seems resolved on 2.164.3 it has taken 9 sec
Started by user unknown or anonymous
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on ssh-agent in /home/jenkins/workspace/test
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] stage
[Pipeline] { (One)
[Pipeline] script
[Pipeline] {
[Pipeline] sh
[2019-06-01T14:24:31.793Z] + /bin/bash -c time hostname
[2019-06-01T14:24:31.799Z]
[2019-06-01T14:24:31.799Z] real 0m0.001s
[2019-06-01T14:24:31.799Z] user 0m0.000s
[2019-06-01T14:24:31.800Z] sys 0m0.000s
[Pipeline] echo
[2019-06-01T14:24:32.509Z] cc32194b98d6
[2019-06-01T14:24:32.509Z]
[Pipeline] sh
[2019-06-01T14:24:32.993Z] + /bin/bash -c time hostname
[2019-06-01T14:24:32.994Z]
[2019-06-01T14:24:32.994Z] real 0m0.001s
[2019-06-01T14:24:32.994Z] user 0m0.000s
[2019-06-01T14:24:32.994Z] sys 0m0.000s
[Pipeline] echo
[2019-06-01T14:24:33.102Z] cc32194b98d6
[2019-06-01T14:24:33.103Z]
[Pipeline] sh
[2019-06-01T14:24:33.965Z] + /bin/bash -c time hostname
[2019-06-01T14:24:33.965Z]
[2019-06-01T14:24:33.965Z] real 0m0.001s
[2019-06-01T14:24:33.965Z] user 0m0.000s
[2019-06-01T14:24:33.965Z] sys 0m0.000s
[Pipeline] echo
[2019-06-01T14:24:34.008Z] cc32194b98d6
[2019-06-01T14:24:34.009Z]
[Pipeline] sh
[2019-06-01T14:24:34.403Z] + /bin/bash -c time hostname
[2019-06-01T14:24:34.404Z]
[2019-06-01T14:24:34.404Z] real 0m0.001s
[2019-06-01T14:24:34.404Z] user 0m0.000s
[2019-06-01T14:24:34.404Z] sys 0m0.000s
[Pipeline] echo
[2019-06-01T14:24:34.500Z] cc32194b98d6
[2019-06-01T14:24:34.500Z]
[Pipeline] sh
[2019-06-01T14:24:35.185Z] + /bin/bash -c time hostname
[2019-06-01T14:24:35.185Z]
[2019-06-01T14:24:35.185Z] real 0m0.001s
[2019-06-01T14:24:35.185Z] user 0m0.000s
[2019-06-01T14:24:35.185Z] sys 0m0.000s
[Pipeline] echo
[2019-06-01T14:24:35.228Z] cc32194b98d6
[2019-06-01T14:24:35.228Z]
[Pipeline] sh
[2019-06-01T14:24:36.213Z] + /bin/bash -c time hostname
[2019-06-01T14:24:36.213Z]
[2019-06-01T14:24:36.213Z] real 0m0.002s
[2019-06-01T14:24:36.213Z] user 0m0.000s
[2019-06-01T14:24:36.213Z] sys 0m0.000s
[Pipeline] echo
[2019-06-01T14:24:36.600Z] cc32194b98d6
[2019-06-01T14:24:36.600Z]
[Pipeline] sh
[2019-06-01T14:24:37.111Z] + /bin/bash -c time hostname
[2019-06-01T14:24:37.111Z]
[2019-06-01T14:24:37.111Z] real 0m0.001s
[2019-06-01T14:24:37.111Z] user 0m0.000s
[2019-06-01T14:24:37.111Z] sys 0m0.000s
[Pipeline] echo
[2019-06-01T14:24:37.617Z] cc32194b98d6
[2019-06-01T14:24:37.617Z]
[Pipeline] sh
[2019-06-01T14:24:38.289Z] + /bin/bash -c time hostname
[2019-06-01T14:24:38.289Z]
[2019-06-01T14:24:38.289Z] real 0m0.001s
[2019-06-01T14:24:38.289Z] user 0m0.000s
[2019-06-01T14:24:38.289Z] sys 0m0.000s
[Pipeline] echo
[2019-06-01T14:24:38.396Z] cc32194b98d6
[2019-06-01T14:24:38.396Z]
[Pipeline] sh
[2019-06-01T14:24:38.889Z] + /bin/bash -c time hostname
[2019-06-01T14:24:38.889Z]
[2019-06-01T14:24:38.889Z] real 0m0.001s
[2019-06-01T14:24:38.889Z] user 0m0.000s
[2019-06-01T14:24:38.889Z] sys 0m0.000s
[Pipeline] echo
[2019-06-01T14:24:39.006Z] cc32194b98d6
[2019-06-01T14:24:39.006Z]
[Pipeline] sh
[2019-06-01T14:24:39.881Z] + /bin/bash -c time hostname
[2019-06-01T14:24:39.881Z]
[JIRA] (JENKINS-57809) Default timestamp formats should not be boldfaced
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-57809 Default timestamp formats should not be boldfaced Issue Type: Improvement Assignee: Steven G Brown Components: timestamper-plugin Created: 2019-06-01 13:38 Labels: ux Priority: Minor Reporter: Jesse Glick DEFAULT_TIMESTAMP_FORMAT and DEFAULT_ELAPSED_TIME_FORMAT wrap the text in , which makes the timestamp more prominent than the log text it is preceding. This seems backwards. A timestamp should not grab attention but mostly stay out of the way unless you are specifically looking for it. Add Comment
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-57347
Re: Performance degradation running pipeline step sh on remote agents
I was unable to replicate the issue on a Docker environment using [Jenkins ver. 2.164.3|https://jenkins.io/] and ssh-slaves 1.29.4, I will make another test with [Jenkins ver. 2.150.2|https://jenkins.io/]{code}Started by user unknown or anonymousStarted by user unknown or anonymousRunning anonymousRunning in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] nodeRunning nodeRunning on ssh-agent in /home/jenkins/workspace/test [Pipeline] \ { [Pipeline] timestamps [Pipeline] { [Pipeline] stage [Pipeline] { (One) [Pipeline] script [Pipeline] { [Pipeline] sh [2019-06-01T13:05:35.854Z] + /bin/bash -c time hostname [2019-06-01T13:05:35.855Z] [2019-06-01T13:05:35.855Z] real 0m0.001s [2019-06-01T13:05:35.855Z] user 0m0.000s [2019-06-01T13:05:35.855Z] sys 0m0.000s [Pipeline] echo [2019-06-01T13:05:35.967Z] cc9f8b5c29e1 [2019-06-01T13:05:35.967Z] [Pipeline] sh [2019-06-01T13:05:36.432Z] + /bin/bash -c time hostname [2019-06-01T13:05:36.434Z] [2019-06-01T13:05:36.434Z] real 0m0.004s [2019-06-01T13:05:36.434Z] user 0m0.000s [2019-06-01T13:05:36.434Z] sys 0m0.000s [Pipeline] echo [2019-06-01T13:05:36.536Z] cc9f8b5c29e1 [2019-06-01T13:05:36.537Z] [Pipeline] sh [2019-06-01T13:05:36.961Z] + /bin/bash -c time hostname [2019-06-01T13:05:36.961Z] [2019-06-01T13:05:36.961Z] real 0m0.001s [2019-06-01T13:05:36.961Z] user 0m0.000s [2019-06-01T13:05:36.961Z] sys 0m0.000s [Pipeline] echo [2019-06-01T13:05:37.069Z] cc9f8b5c29e1 [2019-06-01T13:05:37.069Z] [Pipeline] sh [2019-06-01T13:05:37.516Z] + /bin/bash -c time hostname [2019-06-01T13:05:37.516Z] [2019-06-01T13:05:37.516Z] real 0m0.002s [2019-06-01T13:05:37.516Z] user 0m0.000s [2019-06-01T13:05:37.516Z] sys 0m0.000s [Pipeline] echo [2019-06-01T13:05:37.554Z] cc9f8b5c29e1 [2019-06-01T13:05:37.555Z] [Pipeline] sh [2019-06-01T13:05:38.008Z] + /bin/bash -c time hostname [2019-06-01T13:05:38.008Z] [2019-06-01T13:05:38.008Z] real 0m0.001s [2019-06-01T13:05:38.009Z] user 0m0.000s [2019-06-01T13:05:38.009Z] sys 0m0.000s [Pipeline] echo [2019-06-01T13:05:38.148Z] cc9f8b5c29e1 [2019-06-01T13:05:38.148Z] [Pipeline] sh [2019-06-01T13:05:38.736Z] + /bin/bash -c time hostname [2019-06-01T13:05:38.737Z] [2019-06-01T13:05:38.737Z] real 0m0.001s [2019-06-01T13:05:38.737Z] user 0m0.000s [2019-06-01T13:05:38.737Z] sys 0m0.000s [Pipeline] echo [2019-06-01T13:05:38.756Z] cc9f8b5c29e1 [2019-06-01T13:05:38.756Z] [Pipeline] sh [2019-06-01T13:05:39.342Z] + /bin/bash -c time hostname [2019-06-01T13:05:39.342Z] [2019-06-01T13:05:39.342Z] real 0m0.001s [2019-06-01T13:05:39.342Z] user 0m0.000s [2019-06-01T13:05:39.342Z] sys 0m0.000s [Pipeline] echo [2019-06-01T13:05:39.447Z] cc9f8b5c29e1 [2019-06-01T13:05:39.448Z] [Pipeline] sh [2019-06-01T13:05:39.826Z] + /bin/bash -c time hostname [2019-06-01T13:05:39.826Z] [2019-06-01T13:05:39.826Z] real 0m0.001s [2019-06-01T13:05:39.826Z] user 0m0.000s [2019-06-01T13:05:39.826Z] sys 0m0.000s [Pipeline] echo [2019-06-01T13:05:39.846Z] cc9f8b5c29e1 [2019-06-01T13:05:39.847Z] [Pipeline] sh [2019-06-01T13:05:40.324Z] + /bin/bash -c time hostname [2019-06-01T13:05:40.324Z] [2019-06-01T13:05:40.324Z] real 0m0.001s [2019-06-01T13:05:40.324Z] user 0m0.000s [2019-06-01T13:05:40.324Z] sys 0m0.000s [Pipeline] echo [2019-06-01T13:05:40.354Z] cc9f8b5c29e1 [2019-06-01T13:05:40.354Z] [Pipeline] sh [2019-06-01T13:05:40.826Z] + /bin/bash -c time hostname [2019-06-01T13:05:40.826Z]
