[JIRA] (JENKINS-58777) sh step stuck on when adding inheritFrom in the kubernetes agent section
Title: Message Title
jubel han updated an issue
Jenkins / JENKINS-58777
sh step stuck on when adding inheritFrom in the kubernetes agent section
Change By:
jubel han
After upgraded the kubernetes-plugin to 1.18.0, all of my pipelines hanging on in the one of shell step, and it ended up with the following error.{code:java}process apparently never started in /home/jenkins/workspace/playaround@tmp/durable-3833ccbe (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer){code}After a deep investigation, I've reproduced the issue with the following minimal pipeline code.{code:java}pipeline {agent {kubernetes {label 'playaround'containerTemplate(name: 'busybox', image: 'busybox', command: 'cat', ttyEnabled: true)inheritFrom 'default'}}stages {stage('debug') {steps {sh "echo in steps"script {sh "echo in script"container('busybox') { sh "echo in busybox container"}}}}}}{code} t It hanging on in the last sh step inside of the `busybox` container. and it works if I using the default `jnlp` container or by removing the `inheritFrom` from agent definition.This is a major issue for running the pipelines using kubernetes plugin.as the workaround, I've rollback to the version `1.17.3`, all works.
Add Comment
[JIRA] (JENKINS-58777) sh step stuck on when adding inheritFrom in the kubernetes agent section
Title: Message Title
jubel han created an issue
Jenkins / JENKINS-58777
sh step stuck on when adding inheritFrom in the kubernetes agent section
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-08-02 05:38
Environment:
kubernetes-plugin:1.18.0
Labels:
kubernetes-plugin
Priority:
Major
Reporter:
jubel han
After upgraded the kubernetes-plugin to 1.18.0, all of my pipelines hanging on in the one of shell step, and it ended up with the following error.
process apparently never started in /home/jenkins/workspace/playaround@tmp/durable-3833ccbe
(running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
After a deep investigation, I've reproduced the issue with the following minimal pipeline code.
pipeline {
agent {
kubernetes {
label 'playaround'
containerTemplate(name: 'busybox', image: 'busybox', command: 'cat', ttyEnabled: true)
inheritFrom 'default'
}
}
stages {
stage('debug') {
[JIRA] (JENKINS-55363) Support different SSH providers
Title: Message Title Thai Pham commented on JENKINS-55363 Re: Support different SSH providers Ivan Fernandez Calvo do you happen to have any progress on implementing this 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.196466.154610799.6041.1564721100130%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Kyle Manna commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation with just released 1.19 the thread will have a special name so we can identify if this is the culprit. Thanks! Just installed sse-gateway 1.19, will monitor tomorrow and next week and report back. 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.200967.156416397.6034.1564718280213%40Atlassian.JIRA.
[JIRA] (JENKINS-58747) Parameters: This property type is not supported - Ocean blue
Title: Message Title ashish mishra updated an issue Jenkins / JENKINS-58747 Parameters: This property type is not supported - Ocean blue Change By: ashish mishra 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.201050.1564641236000.6032.1564717320333%40Atlassian.JIRA.
[JIRA] (JENKINS-58700) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent
Title: Message Title Chu CW updated JENKINS-58700 Jenkins / JENKINS-58700 java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent Change By: Chu CW 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.200989.156439021.6028.1564717140239%40Atlassian.JIRA.
[JIRA] (JENKINS-58700) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent
Title: Message Title Chu CW updated JENKINS-58700 Jenkins / JENKINS-58700 java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent Change By: Chu CW 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.200989.156439021.6029.1564717140301%40Atlassian.JIRA.
[JIRA] (JENKINS-58700) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent
Title: Message Title Chu CW stopped work on JENKINS-58700 Change By: Chu CW 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.200989.156439021.6030.1564717140330%40Atlassian.JIRA.
[JIRA] (JENKINS-58700) java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent
Title: Message Title Chu CW started work on JENKINS-58700 Change By: Chu CW 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.200989.156439021.6027.1564717080080%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Olivier Lamy commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation with just released 1.19 the thread will have a special name so we can identify if this is the culprit. Please let us know. Thanks 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.200967.156416397.6022.1564715520251%40Atlassian.JIRA.
[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod
Title: Message Title Eyal Ben Moshe commented on JENKINS-58643 Re: CPS Mismatches on cpsScript.InvokeMethod Can you please be more specific? What does simplifying the plugin and making it more normal mean? How can we maintain the existing APIs and avoid this warning message? 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.200910.1563983113000.6016.1564711260262%40Atlassian.JIRA.
[JIRA] (JENKINS-57256) Kubernetes plugin Windows agent support
Title: Message Title Miguel Suarez edited a comment on JENKINS-57256 Re: Kubernetes plugin Windows agent support did anybody solve this? I was able to provision the pod with a Windows jnlp agent and the logs show connected but it gets stuck not executing the step for the Windows container and the pod is stuck. 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.199020.1556632253000.6010.1564708680179%40Atlassian.JIRA.
[JIRA] (JENKINS-57256) Kubernetes plugin Windows agent support
Title: Message Title Miguel Suarez commented on JENKINS-57256 Re: Kubernetes plugin Windows agent support did anybody solve this? I was able to provision the pod with a Windows jnlp agent and the logs show connected but it gets stuck not executing the step for the Windows container and the pod is stuck. 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.199020.1556632253000.6004.1564708380191%40Atlassian.JIRA.
[JIRA] (JENKINS-58606) Add info about backup plugins to support bundle
Title: Message Title Owen Wood closed an issue as Fixed Jenkins / JENKINS-58606 Add info about backup plugins to support bundle Change By: Owen Wood Status: Resolved 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.200766.1563824088000.6001.1564706880391%40Atlassian.JIRA.
[JIRA] (JENKINS-58337) Promotion Console Log
Title: Message Title Andrew McGilvray updated an issue Jenkins / JENKINS-58337 Promotion Console Log Change By: Andrew McGilvray Attachment: jenkins_downgrade.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.200449.1562224689000.5986.1564706640544%40Atlassian.JIRA.
[JIRA] (JENKINS-58337) Promotion Console Log
Title: Message Title Andrew McGilvray commented on JENKINS-58337 Re: Promotion Console Log Are you in the "Installed" tab? 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.200449.1562224689000.5994.1564706641121%40Atlassian.JIRA.
[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version
Title: Message Title
Basil Crow commented on JENKINS-58716
Re: Failure to check out specified tag for incremental version
this is necessary but not sufficient in order to solve the problem
Here's a sketch of a possible solution. Introduce a new property for the GitHub organization, say scmOrganization. Then use it from , , and :
jenkinsci
scm:git:git://github.com/${scmOrganization}/${project.artifactId}-plugin.git
scm:git:g...@github.com:${scmOrganization}/${project.artifactId}-plugin.git
https://github.com/${scmOrganization}/${project.artifactId}-plugin
[...]
(To implement this, the archetype would need to be updated and IncrementalifyMojo#update would need to evolve to be able to update an existing POM with this change.) With this in place, the git-changelist-maven-extension in incrementals-tools could be updated to set this property for incrementals builds. In particular, we should be able to look up the Git remote in Main#afterSessionStart. From there, we can parse out the organization and set scmOrganization to the appropriate value for incrementals builds.
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
[JIRA] (JENKINS-58776) ConcurrentModificationException while using warnings plugin
Title: Message Title Russ Tennant created an issue Jenkins / JENKINS-58776 ConcurrentModificationException while using warnings plugin Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-08-01 23:46 Environment: Jenkins ver. 2.187 Plugins Name ↓ Version Enabled ace-editor 1.1 true adoptopenjdk 1.1 true analysis-collector 2.0.0 true analysis-core 1.96 true analysis-model-api 5.2.0 true ansicolor 0.6.2 true ant 1.9 true antisamy-markup-formatter 1.5 true apache-httpcomponents-client-4-api 4.5.5-3.0 true authentication-tokens 1.3 true authorize-project 1.3.0 true aws-credentials 1.27 true aws-java-sdk 1.11.594 true basic-branch-build-strategies 1.3.2 true bitbucket-oauth 0.9 true blueocean 1.18.0 true blueocean-autofavorite 1.2.4 true blueocean-bitbucket-pipeline 1.18.0 true blueocean-commons 1.18.0 true blueocean-config 1.18.0 true blueocean-core-js 1.18.0 true blueocean-dashboard 1.18.0 true blueocean-display-url 2.3.0 true blueocean-events 1.18.0 true blueocean-executor-info 1.18.0 true blueocean-git-pipeline 1.18.0 true blueocean-github-pipeline 1.18.0 true blueocean-i18n 1.18.0 true blueocean-jira 1.18.0 true blueocean-jwt 1.18.0 true blueocean-personalization 1.18.0 true blueocean-pipeline-api-impl 1.18.0 true blueocean-pipeline-editor 1.18.0 true blueocean-pipeline-scm-api 1.18.0 true blueocean-rest 1.18.0 true blueocean-rest-impl 1.18.0 true blueocean-web 1.18.0 true bouncycastle-api 2.17 true branch-api 2.5.4 true build-failure-analyzer 1.22.0 true build-timeout 1.19 true checkstyle 4.0.0 true cloudbees-bitbucket-branch-source 2.4.5 true cloudbees-folder 6.9 true command-launcher 1.3 true config-file-provider 3.6.2 true credentials 2.2.0 true credentials-binding 1.19 true cvs 2.14 true dashboard-view 2.10 true display-url-api 2.3.1 true docker-commons 1.15 true docker-workflow 1.18 true durable-task 1.30 true ec2-fleet 1.10.0 true email-ext 2.66 true external-monitor-job 1.7 true extra-columns 1.20 true favorite 2.3.2 true findbugs 5.0.0 true git 4.0.0-rc true git-client 3.0.0-rc true git-server 1.7 true github 1.29.4 true github-api 1.95 true github-branch-source 2.5.5 true github-oauth 0.32 true github-organization-folder 1.6 true gradle 1.33 true handlebars 1.1.1 true handy-uri-templates-2-api 2.1.7-1.0 true htmlpublisher 1.18 true icon-shim 2.0.3 true jackson2-api 2.9.9.1 true javadoc 1.5 true jdk-tool 1.3 true jenkins-design-language 1.18.0 true jira 3.0.8 true jquery 1.12.4-0 true jquery-detached 1.2.1 true jquery-ui 1.0.2 true jsch 0.1.55.1 true junit 1.28 true ldap 1.20
[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version
Title: Message Title Basil Crow commented on JENKINS-58716 Re: Failure to check out specified tag for incremental version Rather, this code should be looking for a /project/scm/tag and honoring it if present As explained in jenkinsci/plugin-compat-tester#181 (comment), this is necessary but not sufficient in order to solve the problem. 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.201008.1564430335000.5977.1564699800180%40Atlassian.JIRA.
[JIRA] (JENKINS-58650) Support proxy for App Center uploads
Title: Message Title Mez Pahlan updated JENKINS-58650 Jenkins / JENKINS-58650 Support proxy for App Center uploads Change By: Mez Pahlan Status: Resolved Fixed but Unreleased 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.200923.156451000.5964.1564693860244%40Atlassian.JIRA.
[JIRA] (JENKINS-58650) Support proxy for App Center uploads
Title: Message Title Mez Pahlan started work on JENKINS-58650 Change By: Mez Pahlan 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.200923.156451000.5956.1564693800803%40Atlassian.JIRA.
[JIRA] (JENKINS-58650) Support proxy for App Center uploads
Title: Message Title Mez Pahlan updated JENKINS-58650 Jenkins / JENKINS-58650 Support proxy for App Center uploads Change By: Mez Pahlan 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.200923.156451000.5958.1564693800832%40Atlassian.JIRA.
[JIRA] (JENKINS-58650) Support proxy for App Center uploads
Title: Message Title Mez Pahlan updated JENKINS-58650 Jenkins / JENKINS-58650 Support proxy for App Center uploads Change By: Mez Pahlan 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.200923.156451000.5960.1564693800866%40Atlassian.JIRA.
[JIRA] (JENKINS-57971) Add user documentation to the Plugin Installation Manager tool
Title: Message Title Natasha Stopa started work on JENKINS-57971 Change By: Natasha Stopa 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.199955.1560277111000.5953.1564693440209%40Atlassian.JIRA.
[JIRA] (JENKINS-58074) Unknown user displaying in jenkins for commits
Title: Message Title Mark Waite updated JENKINS-58074 The Jenkins issue tracker is not a support forum. Please use the Jenkins user mailing list or Jenkins chat systems to request help. Refer to https://jenkins.io/chat/ and https://jenkins.io/mailing-lists/ for more information on chat systems and mailing lists. Jenkins / JENKINS-58074 Unknown user displaying in jenkins for commits Change By: Mark Waite Status: Open Fixed but Unreleased 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.200098.156087171.5948.1564692600486%40Atlassian.JIRA.
[JIRA] (JENKINS-58074) Unknown user displaying in jenkins for commits
Title: Message Title Mark Waite updated JENKINS-58074 Jenkins / JENKINS-58074 Unknown user displaying in jenkins for commits Change By: Mark Waite 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.200098.156087171.5951.1564692600542%40Atlassian.JIRA.
[JIRA] (JENKINS-57714) folder names wont change
Title: Message Title Mark Waite updated JENKINS-57714 Jenkins / JENKINS-57714 folder names wont change Change By: Mark Waite 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.199656.1559048913000.5945.1564692480176%40Atlassian.JIRA.
[JIRA] (JENKINS-57714) folder names wont change
Title: Message Title Mark Waite updated JENKINS-57714 The "Rename" link on the page of the job (or folder) will change the name of the item as stored in the JENKINS_HOME file system. The description allows more verbose text than would commonly be used in the item name. Jenkins / JENKINS-57714 folder names wont change Change By: Mark Waite Status: Open Fixed but Unreleased 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.199656.1559048913000.5943.1564692420202%40Atlassian.JIRA.
[JIRA] (JENKINS-58775) Dependencies of Lower Version Plugin May be Downloaded even though Not Needed
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58775 Dependencies of Lower Version Plugin May be Downloaded even though Not Needed Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-08-01 20:35 Labels: plugin-manager gsoc-2019 Priority: Minor Reporter: Natasha Stopa Right now, if there's a requested plugin or a plugin that's a dependency that is lower than a required version of the same plugin, that lower version of the plugin is "replaced" by the higher version. However, one issue with this is that the lower version might have required dependencies that the higher one doesn't require, and these unneeded plugins are never cleaned up and will be downloaded even though they're not needed. Example: Suppose the user wants to download DotCi (version 2.3) and the latest version of DotCi-InstallPackages. DotCi:2.3 depends on matrix project and github-oauth, github-oauth has an entire tree of dependencies DotCi-InstallPackages depends on DotCi:2.32.1, which no longer depends on github-oauth DotCi:2.3 will be replaced by DotCi:2.32.1, but all of its dependencies that are no longer needed will still be marked as being needed to be installed If a plugin is replaced by a higher version, the original plugin's children should probably be removed from the list of installed plugins (and also replaced with the higher version's dependencies) . But what if one of those children was replaces a lower version of another plugin? You would have to restore the original version of that other plugin. This seems like it could get complicated somewhat quickly, so another way to do this could be to build the full dependency tree without any replacements first, then "optimize" the tree after.
[JIRA] (JENKINS-49235) Fingerprinting added in ssh-slaves causes memory-leak and performance issue with dynamic slaves
Title: Message Title Matt Sicker updated JENKINS-49235 Released in credentials-2.2.1. Jenkins / JENKINS-49235 Fingerprinting added in ssh-slaves causes memory-leak and performance issue with dynamic slaves Change By: Matt Sicker Status: Fixed but Unreleased Resolved Released As: credentials-2.2.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.188081.1517243908000.5931.1564691760932%40Atlassian.JIRA.
[JIRA] (JENKINS-56607) Broken Jelly permission check creates MANAGE_DOMAINS user
Title: Message Title Matt Sicker updated JENKINS-56607 Released in credentials-2.2.1. Jenkins / JENKINS-56607 Broken Jelly permission check creates MANAGE_DOMAINS user Change By: Matt Sicker Status: Fixed but Unreleased Resolved Released As: credentials-2.2.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.198230.1552949216000.5941.1564691761131%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Florian Schmaus commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications so Florian Schmaus should follow up with the merge of https://github.com/jenkinsci/jabber-plugin/pull/18 That PR has conflicts that you need to resolve first. 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.172870.1469028488000.5896.1564691640992%40Atlassian.JIRA.
[JIRA] (JENKINS-30572) Parallel step snippet generator error
Title: Message Title Devin Nusbaum stopped work on JENKINS-30572 Change By: Devin Nusbaum 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.165173.1442846622000.5882.1564690981234%40Atlassian.JIRA.
[JIRA] (JENKINS-30572) Parallel step snippet generator error
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-30572 Parallel step snippet generator error Change By: Devin Nusbaum Assignee: Devin Nusbaum 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.165173.1442846622000.5880.1564690981210%40Atlassian.JIRA.
[JIRA] (JENKINS-30572) Parallel step snippet generator error
Title: Message Title Devin Nusbaum commented on JENKINS-30572 Re: Parallel step snippet generator error Ok, the GDSL issues should be fixed in Pipeline: Groovy Plugin version 2.73. The documentation issues and error when "generate snippet" is clicked still exist, and I'm not sure of a good way to fix them without more special casing for the parallel step. I'm going to move this back to 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.165173.1442846622000.5856.1564690920531%40Atlassian.JIRA.
[JIRA] (JENKINS-33217) DescribableHelper does not detect stray parameters
Title: Message Title Devin Nusbaum commented on JENKINS-33217 Re: DescribableHelper does not detect stray parameters The changes in Structs have been integrated into Pipeline: Groovy Plugin version 2.73 for Pipeline steps. 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.168598.1456760629000.5846.1564690620383%40Atlassian.JIRA.
[JIRA] (JENKINS-33217) DescribableHelper does not detect stray parameters
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-33217 DescribableHelper does not detect stray parameters Change By: Devin Nusbaum Released As: structs 1.20 , workflow-cps 2.73 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.168598.1456760629000.5842.1564690620297%40Atlassian.JIRA.
[JIRA] (JENKINS-58501) Metaprogramming with InvokerHelper and MethodMissing triggers CPS MisMatch log
Title: Message Title Devin Nusbaum updated JENKINS-58501 A fix for this issue was just released in version 2.73 of Pipeline: Groovy Plugin. Jenkins / JENKINS-58501 Metaprogramming with InvokerHelper and MethodMissing triggers CPS MisMatch log Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-cps 2.73 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
[JIRA] (JENKINS-58426) Adding functionality to edit build configurations of child folders from parent organization
Title: Message Title Yashwanth Nalla assigned an issue to Yashwanth Nalla Jenkins / JENKINS-58426 Adding functionality to edit build configurations of child folders from parent organization Change By: Yashwanth Nalla Assignee: Yashwanth Nalla 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.200555.1562766751000.5834.1564689780061%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title
Mark Waite edited a comment on JENKINS-58751
Re: TAG_NAME is not populated in declarative multibranch pipeline
Please provide more details on the multibranch pipeline that you created. Preferably, provide step-by-step instructions that someone else can use to duplicate the problem.You said:{quote}I configured a multibranch pipeline to check out via git, discover branches, discover tags and the added clone behaviour to fetch tags.{quote}You didn't say:* What version of the git client plugin, git plugin, github branch source, bitbucket branch source, Gitea, pipeline, and other plugins you're using* Which SCM implementation you used to create the multibranch pipeline (git, GitHub branch source, Bitbucket, Gitea, something else)* What other options you configured as part of defining the multibranch pipeline* The configuration file ( {{config.xml}} ) of the multibranch pipeline that is showing the problem Assumptions I made:* {{Windows 10}} means that the Jenkins server is running on Windows 10.* Git for Windows 2.22 is being used on the Windows 10 Jenkins server. I don't see anything that hints this is somehow connected to a specific version of command line git on Windows, so I assumed the version I have installed on my Windows computer* Java 8 as provided by AdoptOpenJDK, since that is what I have installed on my Windows computer now that Oracle JDK requires a license purchase from Oracle for commercial use* Latest releases of all the relevant plugins* GitHub as the provider for the multibranch pipeline definition (not git, not Bitbucket, and not Gitea)
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
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Jim Klimov assigned an issue to Jim Klimov Jenkins / JENKINS-36826 Support Jenkins Pipeline for Jabber notifications Change By: Jim Klimov Assignee: kutzi Jim Klimov 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.172870.1469028488000.5798.1564689062135%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Jim Klimov commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications I can now merge the IM and IRC PRs, but did not ask for Jabber rights (so Florian Schmaus should follow up with the merge of https://github.com/jenkinsci/jabber-plugin/pull/18). I ported that logic for ircbot so there would be an ircNotify pipeline step as well, and can at least confirm that this coupling works 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.172870.1469028488000.5762.1564689061544%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: Mark Waite Summary: TAG_NAME is not populated in descriptive declarative multibranch pipeline 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.201054.1564649736000.5759.1564689000159%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in descriptive multibranch pipeline
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-58751 TAG_NAME is not populated in descriptive multibranch pipeline Change By: Mark Waite Assignee: Mark Waite 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.201054.1564649736000.5757.1564688940363%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in descriptive multibranch pipeline
Title: Message Title
Mark Waite edited a comment on JENKINS-58751
Re: TAG_NAME is not populated in descriptive multibranch pipeline
Please provide more details on the multibranch pipeline that you created. Preferably, provide step-by-step instructions that someone else can use to duplicate the problem.You said:{quote}I configured a multibranch pipeline to check out via git, discover branches, discover tags and the added clone behaviour to fetch tags.{quote}You didn't say:* What version of the git client plugin, git plugin, github branch source, p bitbucket branch source, Gitea, pipeline, and other plugins you're using* Which SCM implementation you used to create the multibranch pipeline (git, GitHub branch source, Bitbucket, Gitea, something else)* What other options you configured as part of defining the multibranch pipeline* The configuration file ( {{config.xml}} ) of the multibranch pipeline that is showing the problem
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.201054.1564649736000.5755.1564688940336%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in descriptive multibranch pipeline
Title: Message Title Mark Waite commented on JENKINS-58751 Re: TAG_NAME is not populated in descriptive multibranch pipeline Please provide more details on the multibranch pipeline that you created. Preferably, provide step-by-step instructions that someone else can use to duplicate the problem. You said: I configured a multibranch pipeline to check out via git, discover branches, discover tags and the added clone behaviour to fetch tags. You didn't say: What version of the git client plugin, git plugin, github branch source,p bitbucket branch source, Gitea, pipeline, and other plugins you're using Which SCM implementation you used to create the multibranch pipeline (git, GitHub branch source, Bitbucket, Gitea, something else) What other options you configured as part of defining the multibranch pipeline The configuration file ( config.xml ) of the multibranch pipeline that is showing the problem 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.201054.1564649736000.5753.1564688940306%40Atlassian.JIRA.
[JIRA] (JENKINS-58773) Builds stuck after Querying the current revision of branch
Title: Message Title Parichay Barpanda commented on JENKINS-58773 Re: Builds stuck after Querying the current revision of branch What is your GitLab Server version? 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.201079.156468431.5748.1564687560108%40Atlassian.JIRA.
[JIRA] (JENKINS-58773) Builds stuck after Querying the current revision of branch
Title: Message Title Parichay Barpanda commented on JENKINS-58773 Re: Builds stuck after Querying the current revision of branch Hi Peter, thanks for installing the plugin. I am not sure if it is a problem with the plugin because our tests has been successful. My initial guess is you are using a declarative syntax in your Jenkinsfile and you do not have Pipeline:declarative installed in your Jenkins instance. Can you try using a scripted pipeline and perform the build. Also want you to try this hpi: https://ci.jenkins.io/job/Plugins/job/gitlab-branch-source-plugin/job/hotfix%252Fwebhook-2.0/lastSuccessfulBuild/artifact/io/jenkins/plugins/gitlab-branch-source/0.0.6-rc367.c03b88a61fc1/gitlab-branch-source-0.0.6-rc367.c03b88a61fc1.hpi Please let me know if this doesn't fix your issue. 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.201079.156468431.5746.1564687500145%40Atlassian.JIRA.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Pavel Roskin commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies OK, I think I understand it. Posting here to help others understand similar issues. The dependency chain (without test dependencies) was: stashNotifier -> git 2.0 -> git-client 1.4.4 -> ssh-agent 1.3 -> sshd-core 0.8.0 Now it is: stashNotifier 1.19 -> git 3.0.0 -> git-client 2.0.0 git-client 2.0.0 doesn't depend on ssh-agent, so that cuts the non-test dependency chain and stops the bundling. The version of sshd-core (0.14.0) was determined by a shorter chain that involved test dependencies: stashNotifier 1.19 => plugin 3.40 -> jenkins-war 2.60.3 ~> sshd 1.11 -> sshd-core 0.14.0 I'm using => for a child-parent relationship (which doesn't count towards the length of the dependency chain) and ~> for a test dependency. mvn dependency:tree was showing a shorter dependency chain, but with the scope based on analyzing the whole tree, which made it look like a test dependency was pulling in a compile dependency. I don't see a way to make maven omit test dependencies or to show all paths leading to a transitive dependency. It would have helped with debugging the issue. 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.194562.1539080849000.5744.1564687020324%40Atlassian.JIRA.
[JIRA] (JENKINS-58773) Builds stuck after Querying the current revision of branch
Title: Message Title
Peter Leibiger updated an issue
Jenkins / JENKINS-58773
Builds stuck after Querying the current revision of branch
Change By:
Peter Leibiger
I installed the latest version of the plugin as HPI and configured my Gitlab Server.I managed to create a Gitlab Group and the plugin found my example branch with a Jenkinsfile.After starting a build on the branch, it is stuck forever after Querying the current revision of branch. Same happens when I create this as single Multibranch Project.{code:java}Gestartet durch Benutzer TestQuerying the current revision of branch feature/FOO...Current revision of branch feature/FOO is 80b4ef81acc9c9e14b42e80e8bf74cd7fd5d5bb9{code}Stuck here with the little animated circle icon. EDIT:After 20min timeout I get a Git exception: {code:java}[GitLab Pipeline Status] Notifying branch build status: FAILED Test/FOO: There was a failure building this commit[GitLab Pipeline Status] Notifiedhudson.plugins.git.GitException: Command "git fetch --tags --force --progress origin +refs/heads/*:refs/remotes/origin/* --prune" returned status code 143:stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:406) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:293) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:103) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{code}
Add Comment
[JIRA] (JENKINS-58774) Could not parse Perforce changelog
Title: Message Title Noel C created an issue Jenkins / JENKINS-58774 Could not parse Perforce changelog Issue Type: Bug Assignee: Emilio Escobar Components: changelog-history-plugin, p4-plugin Created: 2019-08-01 19:15 Environment: Jenkins Ver 2.176.2 P4 ver 1.10.1 Priority: Minor Reporter: Noel C Hi, I'm having problem where Jenkins is not able to generate the changes (e.g. "No changes from last build"). But changelog.xml exist and looks valid. It looks like my issue is due to special characters (e.g. "&", and "+" at least) within the tags such as below blahblah_&_blahblah I see the below in my Jenkins log: Could not parse Perforce changelog: /var/lib/jenkins/jobs//builds/28/changelog.xml Aug 01, 2019 8:54:08 AM SEVERE org.jenkinsci.plugins.p4.changes.P4ChangeParser parse Add Comment
[JIRA] (JENKINS-58606) Add info about backup plugins to support bundle
Title: Message Title Owen Wood updated JENKINS-58606 Released as 2.59 Jenkins / JENKINS-58606 Add info about backup plugins to support bundle Change By: Owen Wood 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.200766.1563824088000.5735.1564686660548%40Atlassian.JIRA.
[JIRA] (JENKINS-49235) Fingerprinting added in ssh-slaves causes memory-leak and performance issue with dynamic slaves
Title: Message Title Matt Sicker updated JENKINS-49235 Merged to master. Jenkins / JENKINS-49235 Fingerprinting added in ssh-slaves causes memory-leak and performance issue with dynamic slaves Change By: Matt Sicker Status: In Review 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.188081.1517243908000.5733.1564686480829%40Atlassian.JIRA.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title
Noel C edited a comment on JENKINS-52661
Re: P4 Plugin fails to parse changelog
Hi,I am getting similar issue where Jenkins is not able to generate the changes (e.g. "No changes from last build"). But changelog.xml exist and looks valid. It looks like my issue is due to special characters (e.g. "&", and "+" at least) within the tags such as below{color:#b00117}blahblah_&_blahblah clientI clientId> {color}I see the below in my Jenkins log:Could not parse Perforce changelog: /var/lib/jenkins/jobs//builds/28/changelog.xml{color:#88aa88}Aug 01, 2019 8:54:08 AM{color} {color:#aa}SEVERE{color} {color:#aa}org.jenkinsci.plugins.p4.changes.P4ChangeParser parse {color}
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.192535.1532016996000.5718.1564686360526%40Atlassian.JIRA.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Noel C commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog Hi, I am getting similar issue where Jenkins is not able to generate the changes (e.g. "No changes from last build"). But changelog.xml exist and looks valid. It looks like my issue is due to special characters (e.g. "&", and "+" at least) within the tags such as below blahblah_&_blahblah I see the below in my Jenkins log: Could not parse Perforce changelog: /var/lib/jenkins/jobs//builds/28/changelog.xml Aug 01, 2019 8:54:08 AM SEVERE org.jenkinsci.plugins.p4.changes.P4ChangeParser parse 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.192535.1532016996000.5710.1564686300270%40Atlassian.JIRA.
[JIRA] (JENKINS-58170) Allow credential parameters to shadow credential ids in lookup
Title: Message Title Matt Sicker commented on JENKINS-58170 Re: Allow credential parameters to shadow credential ids in lookup Linking related issues that can be implemented through this 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.200221.1561401761000.5707.1564686180105%40Atlassian.JIRA.
[JIRA] (JENKINS-56607) Broken Jelly permission check creates MANAGE_DOMAINS user
Title: Message Title Matt Sicker updated JENKINS-56607 Merged to master. Jenkins / JENKINS-56607 Broken Jelly permission check creates MANAGE_DOMAINS user Change By: Matt Sicker Status: In Review 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.198230.1552949216000.5706.1564685640235%40Atlassian.JIRA.
[JIRA] (JENKINS-58773) Builds stuck after Querying the current revision of branch
Title: Message Title Peter Leibiger created an issue Jenkins / JENKINS-58773 Builds stuck after Querying the current revision of branch Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-01 18:31 Environment: Jenkins 2.187 on Mac Priority: Minor Reporter: Peter Leibiger I installed the latest version of the plugin as HPI and configured my Gitlab Server. I managed to create a Gitlab Group and the plugin found my example branch with a Jenkinsfile. After starting a build on the branch, it is stuck forever after Querying the current revision of branch. Same happens when I create this as single Multibranch Project. Gestartet durch Benutzer Test Querying the current revision of branch feature/FOO... Current revision of branch feature/FOO is 80b4ef81acc9c9e14b42e80e8bf74cd7fd5d5bb9 Stuck here with the little animated circle icon.
[JIRA] (JENKINS-58772) Fall-back user for Active Directory plugin does not work
Title: Message Title Chris Johnson updated an issue Jenkins / JENKINS-58772 Fall-back user for Active Directory plugin does not work Change By: Chris Johnson Environment: Active Directory => 2.16Jenkins => 2.176.2os.arch x86_64os.name Mac OS Xos.version 10.14.6 java.runtime.name OpenJDK Runtime Environmentjava.runtime.version 1.8.0_222-b10java.specification.name Java Platform API Specificationjava.specification.vendor Oracle Corporationjava.specification.version 1.8java.vendor AdoptOpenJDKjava.version 1.8.0_222java.vm.info mixed modejava.vm.name OpenJDK 64-Bit Server VMjava.vm.specification.name Java Virtual Machine Specificationjava.vm.specification.vendor Oracle Corporationjava.vm.specification.version 1.8java.vm.vendor AdoptOpenJDKjava.vm.version 25.222-b10 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.201078.1564682674000.5695.1564682880213%40Atlassian.JIRA.
[JIRA] (JENKINS-58772) Fall-back user for Active Directory plugin does not work
Title: Message Title Chris Johnson updated an issue Jenkins / JENKINS-58772 Fall-back user for Active Directory plugin does not work Change By: Chris Johnson Environment: Active Directory => 2.16Jenkins => 2.176.2os.arch x86_64os.name Mac OS Xos.version 10.14.6 Using the 'Active Directory' plugin, I configured it to point to our LDAP server and everything works fine there. However I also checked the option to use a `fall-back` user to login to my Jenkins server just in case our LDAP connection failed. See attached image.The problem is when I log out and try to login with my 'fall-back' user, it fails to login, and I just get the normal 'invalid username and password' error message. See attached image.I expected to be able to login with the one non-LDAP user account. The documentation says it should be possible.Note:The LDAP integration works fine. I have tested logging with many different LDAP accounts, and they work fine. VERSIONS:Active Directory => 2.16Jenkins => 2.176.2 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
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Pritam Kadam commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation I did face this issue today and it seemed like `sse-gateway` thread leak issue. Earlier jenkins was creating threads exponentially on every build but once I updated all the plugins, issue got resolved. Now it uses on an average overall 100 threads. And when I monitored all the threads, they were all named with `Timer-$id` 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.200967.156416397.5688.1564682760214%40Atlassian.JIRA.
[JIRA] (JENKINS-58772) Fall-back user for Active Directory plugin does not work
Title: Message Title Chris Johnson created an issue Jenkins / JENKINS-58772 Fall-back user for Active Directory plugin does not work Issue Type: Bug Assignee: Félix Belzunce Arcos Attachments: fall-back.png, Sign_in__Jenkins_failed.png Components: active-directory-plugin Created: 2019-08-01 18:04 Priority: Minor Reporter: Chris Johnson Using the 'Active Directory' plugin, I configured it to point to our LDAP server and everything works fine there. However I also checked the option to use a `fall-back` user to login to my Jenkins server just in case our LDAP connection failed. See attached image. The problem is when I log out and try to login with my 'fall-back' user, it fails to login, and I just get the normal 'invalid username and password' error message. See attached image. I expected to be able to login with the one non-LDAP user account. The documentation says it should be possible. Note: The LDAP integration works fine. I have tested logging with many different LDAP accounts, and they work fine. VERSIONS: Active Directory => 2.16 Jenkins => 2.176.2
[JIRA] (JENKINS-58627) jenkins agent getting terminated with version 2.176.2
Title: Message Title Chethan Mahabaleswara commented on JENKINS-58627 Re: jenkins agent getting terminated with version 2.176.2 Hello Oleg, I see the fix is released as part of jenskins V 2.181, for Component remoting [15489]. But when i tried with jenkins version 2.187, observed the same issue/ error I had also tried jenkins version 2.176.2, but I see fix is not released in this version. 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.200795.1563941135000.5683.1564680540233%40Atlassian.JIRA.
[JIRA] (JENKINS-58627) jenkins agent getting terminated with version 2.176.2
Title: Message Title Chethan Mahabaleswara updated an issue Jenkins / JENKINS-58627 jenkins agent getting terminated with version 2.176.2 More information about the issue - I'm having an issue while using Networl Connection Emulator that it just terminates the jenkins agent process as explained below: Scenario 1 - I have jenkins agent set up in Windows 2012 machine where connection emulator is installed. I run a python script through jenkins pipeline to set the latency and open the connection emulator using python function "subprocess.Popen(["schtasks","/Run","/TN","StartNetworkEmulator"]) ", which opens emulator from windows task scheduler as a last step. Once the connection emulator is opened, it interferes with the jenkins agent process and terminates the jenkins agent and master communication. I have to close the emulator and restart the jenkins agent windows service to make agent communicate with jenkins master Scenario 2 - There are no jenkins jobs or pipeline running. Jenkins agent is active and connected to Master. When I open and run Connection emulator manually by going C:\Program Files, the jenkins agent and master communication is broken. Sometimes I see Linkage error and few times "Error while determining if vetoers exist" The error log observed in build and slave are attached. Note - Same job or pipeline works with no issues with old jenkins version 2.76 having remoting version 3.11. But we want to upgrade to new windows server where I installed latest jenkins version. Is this a bug with latest version of jenkins ? Appreciate any help in fixing this issue Thanks, Chethan Change By: Chethan Mahabaleswara Attachment: Error log_in Build.txt Attachment: Agent Log_V1.txt Add Comment
[JIRA] (JENKINS-58288) Integrate Cloud API implementation with Helm chart
Title: Message Title Long Nguyen resolved as Done Jenkins / JENKINS-58288 Integrate Cloud API implementation with Helm chart Change By: Long Nguyen Status: In Progress Resolved Resolution: Done 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.200352.1562008698000.5672.1564679220102%40Atlassian.JIRA.
[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0
Title: Message Title Vincent Latombe commented on JENKINS-58766 Re: kubernetes-plugin access denied after update to 1.18.0 Steffen Seckler Could you be more explicit by providing an example of pod template definition (either config.xml or snippet of Jenkinsfile) ? 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.201071.1564670804000.5671.1564678200152%40Atlassian.JIRA.
[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0
Title: Message Title
Vincent Latombe updated an issue
Jenkins / JENKINS-58766
kubernetes-plugin access denied after update to 1.18.0
Change By:
Vincent Latombe
After updating to kubernetes-plugin 1.18.0 I got an error when using the old /home/jenkins directory inside of a pod template definition. Using /home/jenkins/agent in the pod templates worked, however. The error was: ``` {code} Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from (hidden). at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at hudson.FilePath.mkdirs(FilePath.java:1246) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:821) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1169) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)java.nio.file.AccessDeniedException: /home/jenkins/workspace at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at hudson.FilePath.mkdirs(FilePath.java:3239) at hudson.FilePath.access$1300(FilePath.java:212) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1254) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1250) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-58767) Binary compatibility issue with 1.15 line
Title: Message Title Vincent Latombe updated JENKINS-58767 Jenkins / JENKINS-58767 Binary compatibility issue with 1.15 line Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: 1.15.10 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.201072.1564671718000.5664.1564677060448%40Atlassian.JIRA.
[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod
Title: Message Title Jesse Glick commented on JENKINS-58643 Re: CPS Mismatches on cpsScript.InvokeMethod Best would be to reconsider what the artifactory plugin is doing, and simplify its implementation to be more normal. To the extent that is impossible for backward compatibility reasons, TBD—Devin Nusbaum can check effectiveness & safety of the above patch. 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.200910.1563983113000.5662.1564677000318%40Atlassian.JIRA.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Jesse Glick commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies Note that while poking around I did discover what looks like a proper bug in the mojo: JENKINS-58771. 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.194562.1539080849000.5655.1564676460238%40Atlassian.JIRA.
[JIRA] (JENKINS-58771) JARs bundled which are transitive deps of a plugin but via a test-scoped trail
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-58771 JARs bundled which are transitive deps of a plugin but via a test-scoped trail Issue Type: Bug Assignee: Unassigned Components: maven-hpi-plugin, workflow-cps-global-lib-plugin Created: 2019-08-01 16:19 Priority: Major Reporter: Jesse Glick Discovered in the context of JENKINS-53957. Details Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58733) Cannot delete project
Title: Message Title Jesse Glick updated JENKINS-58733 Jenkins / JENKINS-58733 Cannot delete project Change By: Jesse Glick 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.201032.1564503798000.5651.1564676100405%40Atlassian.JIRA.
[JIRA] (JENKINS-58733) Cannot delete project
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58733 Cannot delete project Change By: Jesse Glick Labels: deletion regression windows 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.201032.1564503798000.5649.1564676100380%40Atlassian.JIRA.
[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod
Title: Message Title Eyal Ben Moshe commented on JENKINS-58643 Re: CPS Mismatches on cpsScript.InvokeMethod Jesse Glick, so what should we do to resolve this issue? Can we perhaps allow specific steps to be excluded and avoid this message? 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.200910.1563983113000.5643.1564675920187%40Atlassian.JIRA.
[JIRA] (JENKINS-58733) Cannot delete project
Title: Message Title Jesse Glick started work on JENKINS-58733 Change By: Jesse Glick 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.201032.1564503798000.5640.1564675812369%40Atlassian.JIRA.
[JIRA] (JENKINS-58733) Cannot delete project
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-58733 Cannot delete project Change By: Jesse Glick Assignee: Jesse Glick 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.201032.1564503798000.5638.1564675811396%40Atlassian.JIRA.
[JIRA] (JENKINS-58733) Cannot delete project
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58733 Cannot delete project Change By: Jesse Glick Issue Type: Task 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.201032.1564503798000.5634.1564675802019%40Atlassian.JIRA.
[JIRA] (JENKINS-58290) WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Title: Message Title Jesse Glick commented on JENKINS-58290 Re: WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator Daniel Jeznach you can file a separate issue (using the is caused by option to Link) with complete, minimal steps to reproduce from scratch. Offhand I suspect the pkill command is to blame, perhaps by killing too much. It is possible you did not need this to begin with—exiting a node block already sends a termination signal to all processes which inherited the (IIRC) JENKINS_MAGIC_COOKIE environment variable passed to any nested sh steps. 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.200355.156202156.5632.1564675560156%40Atlassian.JIRA.
[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod
Title: Message Title Jesse Glick commented on JENKINS-58643 Re: CPS Mismatches on cpsScript.InvokeMethod Although I should say that since docker-workflow and pipeline-model-definition use the less problematic approach of exposing CPS-transformed Groovy, the receiverClass in those cases should not be loaded by a Jenkins plugin class loader as far as I know, so I do not believe such a patch would mask mistakes in those plugins, though it is worth confirming this. (To confuse matters, pipeline-model-definition-plugin/pipeline-model-definition/src/main/groovy/ exists, but as far as Jenkins is concerned these are just plain old classes in the plugin. The CPS-transformed code that would be involved here is in pipeline-model-definition-plugin/pipeline-model-definition/src/main/groovy/**/*.groovy. 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.200910.1563983113000.5629.1564675200246%40Atlassian.JIRA.
[JIRA] (JENKINS-58337) Promotion Console Log
Title: Message Title Rita S commented on JENKINS-58337 Re: Promotion Console Log How do I downgrade the plugin, I don't see the downgrade button. 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.200449.1562224689000.5614.1564674840812%40Atlassian.JIRA.
[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58643 CPS Mismatches on cpsScript.InvokeMethod It does not seem like a great workaround either. We already explicitly discourage domain-specific plugins from using GlobalVariable and implementing DSLs, but what ArtifactoryServer is doing is an additional complication: the returned object, or one of its resultant objects, is implemented in Java rather than CPS-transformed Groovy. I would consider this to be an unsupported and unsupportable trick. Change By: Jesse Glick Component/s: artifactory-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.200910.1563983113000.5624.1564674900248%40Atlassian.JIRA.
[JIRA] (JENKINS-58337) Promotion Console Log
Title: Message Title Rita S updated an issue Jenkins / JENKINS-58337 Promotion Console Log Change By: Rita S Attachment: image-2019-08-01-10-53-08-973.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.200449.1562224689000.5606.1564674840683%40Atlassian.JIRA.
[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Title: Message Title Rita S commented on JENKINS-58534 Re: Impossible to access promotion's console output (navigation is broken from links and breadcrumbs) I have the same issue. 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.200683.1563381278000.5600.1564674720410%40Atlassian.JIRA.
[JIRA] (JENKINS-58767) Binary compatibility issue with 1.15 line
Title: Message Title Vincent Latombe started work on JENKINS-58767 Change By: Vincent Latombe 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.201072.1564671718000.5594.1564674542033%40Atlassian.JIRA.
[JIRA] (JENKINS-58767) Binary compatibility issue with 1.15 line
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-58767 Binary compatibility issue with 1.15 line Change By: Vincent Latombe Assignee: Carlos Sanchez Vincent Latombe 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.201072.1564671718000.5591.1564674540623%40Atlassian.JIRA.
[JIRA] (JENKINS-58767) Binary compatibility issue with 1.15 line
Title: Message Title Vincent Latombe updated JENKINS-58767 Jenkins / JENKINS-58767 Binary compatibility issue with 1.15 line Change By: Vincent Latombe 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.201072.1564671718000.5596.1564674542094%40Atlassian.JIRA.
[JIRA] (JENKINS-58770) Reconsider GAV scheme
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-58770 Reconsider GAV scheme Issue Type: Task Assignee: Jesse Glick Components: bom Created: 2019-08-01 15:42 Priority: Critical Reporter: Jesse Glick Oleg Nenashev was the first to be confused by the version scheme for the BOM, which partially but not completely matches Jenkins core versions. A cheap fix would be to version the BOM like 2.176.100, 2.176.101, etc., so that it is obviously not the same. A more complicated change would be to drop the current branch/merge scheme, doing everything in master, and have a separate artifactId for each line as a reactor module, so you might import something like io.jenkins.tools.bom:bom-2.176.x:3. This would likely also work better with Dependabot, but involves a number of challenges: Figuring out how to minimize the number of places where plugin versions are specified. Perhaps the latest BOM could specify all the versions and then BOMs for older lines could import it and override a few versions, assuming that works for importers (it should, given flattening). Adjusting the PCT runs to handle different lines. Should just be a technical refactoring. Avoid maintaining multiple copies of the sample plugin, while testing it against each line. Perhaps it could default to the latest line but select an older line to use based on a POM profile.
[JIRA] (JENKINS-58657) sh not working inside docker container
Title: Message Title Erik Wegner commented on JENKINS-58657 Re: sh not working inside docker container This seems somewhat related to https://github.com/jenkinsci/docker/issues/626#issuecomment-508444712 In my scenario, there are two containers on a kubernetes pod, one is the jnlp-slave. The directory /home/jenkins/agent/workspace/@tmp/durable-831063bb exists and is used for steps running inside the jnlp-container. The sh-step running inside the other container tries to access the wrong directory and outputs these messages: sh: 1: cannot create /home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-log.txt: Permission denied sh: 1: cannot create /home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-result.txt.tmp: Permission denied touch: cannot touch '/home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-log.txt': Permission denied mv: cannot stat '/home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-result.txt.tmp': No such file or directory touch: cannot touch '/home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-log.txt': Permission denied 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.200938.1564047916000.5585.1564673640398%40Atlassian.JIRA.
[JIRA] (JENKINS-58769) Add trait to choose the mode of notification
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58769 Add trait to choose the mode of notification Issue Type: New Feature Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-01 15:33 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda 2 types of GitLab pipeline status: 1. Job Status 2. Pipeline Stage Status Add Comment
[JIRA] (JENKINS-45693) Ability to decorate Pipeline builds as a global extension
Title: Message Title Jesse Glick commented on JENKINS-45693 Re: Ability to decorate Pipeline builds as a global extension Richard Schaefer inside in the POM. Note however that workflow-api #97, if merged & released, would avoid the need for 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.183889.150055953.5568.1564672621384%40Atlassian.JIRA.
[JIRA] (JENKINS-58768) Mailer doesn't authenticate properly with Gmail
Title: Message Title Dan Hentschel created an issue Jenkins / JENKINS-58768 Mailer doesn't authenticate properly with Gmail Issue Type: Bug Assignee: Adrien Lecharpentier Components: mailer-plugin Created: 2019-08-01 15:03 Environment: Jenkins: 2.187 (Linux) Mailer: 1.24 Labels: plugin mailer Priority: Major Reporter: Dan Hentschel This appears to be a regression in Mailer 1.24. I just updated that plugin this morning. If I go to Manage Jenkins -> Configure System -> Email notification -> Advanced -> Test configuration by sending test e-mail, the test fails with: Failed to send out e-mail com.sun.mail.smtp.SMTPSendFailedException: 530-5.5.1 Authentication Required. Learn more at 530 5.5.1 https://support.google.com/mail/?p=WantAuthError r14sm33254971qke.47 - gsmtp If I downgrade to the 1.23 version of Mailer, and don't change my configuration at all, then the test email is sent successfully. Email configuration: SMTP server: smtp.gmail.com Default user e-mail suffix: blank Use SMTP Authentication: true User Name and Password: set correctly Use SSL: true SMTP Port: 465 Reply-To Address: no-re...@allworx.com Charset: UTF-8
[JIRA] (JENKINS-58767) Binary compatibility issue with 1.15 line
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-58767 Binary compatibility issue with 1.15 line Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-08-01 15:01 Priority: Minor Reporter: Vincent Latombe In 1.15.1 JENKINS-56082 introduced the ability to merge yaml fragments when merging pod templates. Notably, it changed the persisted form of yaml from a String to a List (source) In some use cases we have at CloudBees, this is breaking persistence capability as KubernetesCloud objects are being copied between different Jenkins instances. Adding a field is usually fine except here it is replacing an existing field. As the List is only used for use cases of merging pod templates (a single textfield was exposed in the UI), where these are actually transient and never persisted, I am going to revert persistence to a single String field in order to achieve compatibility. Add Comment
[JIRA] (JENKINS-58089) Can't configure report pattern in job configuration UI
Title: Message Title Pieter-Jan Busschaert commented on JENKINS-58089 Re: Can't configure report pattern in job configuration UI Can somebody please write a changelog entry for that DTKit update that mentions this issue? I had the same problem and it took a while (until finding this issue) that the DTKit update might be related. Even better: make the xUnit plugin depend on that updated version of the DTKit plugin? (I typically wait to update plugins if I can't find a changelog entry for the update) 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.200130.1560932882000.5540.1564671720502%40Atlassian.JIRA.
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58656 Wrapper process leaves zombie when no init process present Change By: Jesse Glick Labels: pipeline regression 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.200936.1564038973000.5537.1564671660122%40Atlassian.JIRA.
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-58656
Wrapper process leaves zombie when no init process present
Adding to kubernetes plugin as it is important to check whether there is a practical impact on a Kubernetes node. Does something in K8s itself reap zombies? Can we reproduce a PID exhaustion error by repeatedly running brief sh steps? The defense for {[command-launcher}} + jenkins/slave is documented (just use docker run --init) if not enforced at runtime, but it is unknown at this time whether this affects a typical Kubernetes pod using jenkins/jnlp-slave.
Change By:
Jesse Glick
Component/s:
kubernetes-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.200936.1564038973000.5535.1564671600272%40Atlassian.JIRA.
[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0
Title: Message Title Steffen Seckler updated an issue Jenkins / JENKINS-58766 kubernetes-plugin access denied after update to 1.18.0 Change By: Steffen Seckler After updating to kubernetes-plugin 1.18.0 I got an error when using the old /home/jenkins directory inside of a pod template definition. Using /home/jenkins/agent in the pod templates worked, however. The error was:```Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from (hidden). at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at hudson.FilePath.mkdirs(FilePath.java:1246) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:821) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1169) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)java.nio.file.AccessDeniedException: /home/jenkins/workspace at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at hudson.FilePath.mkdirs(FilePath.java:3239) at hudson.FilePath.access$1300(FilePath.java:212) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1254) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1250) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0
Title: Message Title Steffen Seckler created an issue Jenkins / JENKINS-58766 kubernetes-plugin access denied after update to 1.18.0 Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-08-01 14:46 Environment: Jenkins 2.187, kubernetes-plugin 1.18.0 Priority: Minor Reporter: Steffen Seckler After updating to kubernetes-plugin 1.18.0 I got an error when using the old /home/jenkins directory inside of a pod template definition. Using /home/jenkins/agent in the pod templates worked, however. The error was: ``` Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from (hidden). at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at hudson.FilePath.mkdirs(FilePath.java:1246) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:821) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1169) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
[JIRA] (JENKINS-58604) Full Stage View only showing one
Title: Message Title Brian J Murrell commented on JENKINS-58604 Re: Full Stage View only showing one This only seems to happen while a job is in progress. Once the job completes, the older entries show up in the stage view. 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.200764.1563816065000.5515.1564670640358%40Atlassian.JIRA.
[JIRA] (JENKINS-56511) Failed Loading plugin Role-based Authorization Strategy
Title: Message Title Vladislav Gorbunov commented on JENKINS-56511 Re: Failed Loading plugin Role-based Authorization Strategy Install dependencies plugin - Configuration-as-Code plugin version 1.21 or higher for fix this error 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.198118.1552340918000.5512.1564670340174%40Atlassian.JIRA.
[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent
Title: Message Title Steffen Seckler updated JENKINS-58705 Jenkins / JENKINS-58705 Change default working dir to /home/jenkins/agent Change By: Steffen Seckler 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.200995.1564403053000.5509.1564670280216%40Atlassian.JIRA.
