[JIRA] (JENKINS-40677) ability to delete parameter-files stuff after a build completes
Title: Message Title Xie Shiquan commented on JENKINS-40677 Re: ability to delete parameter-files stuff after a build completes Voting for a way to delete/manage files in fileParameters subdirectory in the Jobs folder. My current build process involves uploading a 300+MB installer file to Jenkins, which would then be deployed on whichever node that is running the build to test the installer file. The file would be cleared from the respective workspaces at the end of the job, but the uploaded file stays in the fileParameters folder, which bulks up the Jenkins directory considerably over time. These files will never be used again after the job is done, so there isn't much point in keeping these in the Jobs folder. The installers can be rebuilt at anytime in the future since the file version information is already extracted during build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177379.1482764946000.9078.1572940740196%40Atlassian.JIRA.
[JIRA] (JENKINS-60054) Wrong umask? Containers with non-root user don't have permissions to agent durable script folders
Title: Message Title
Dmytro Kryvenko updated an issue
Jenkins / JENKINS-60054
Wrong umask? Containers with non-root user don't have permissions to agent durable script folders
Change By:
Dmytro Kryvenko
This setup used to work in older versions, I suspect regression happened somewhere around changing working directory to {{/home/jenkins/agent}}.When running container with non-root user (of course having {{fsGroup}}/{{supplementalGroups}} to {{1000}} to match jnlp slave GUID) getting the following error:{code} process apparently never started in /home/jenkins/agent/workspace/ure-xxx-terraform-module_PR-1@tmp/durable-79996fba (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer){code}Doing that reveals:{code} LAUNCHER: open /home/jenkins/agent/workspace/ure-xxx-terraform-module_PR-1@tmp/durable-cc0559df/jenkins-log.txt: permission denied{code}I know there's a lot of similar issues being reported recently, but this one is different and not related to the {{workingDir}} in {{jnlp}} slave. I am using {{jenkins/jnlp-slave:3.35-5-alpine}} image and have {{workingDir}} correctly defaulting to {{/home/jenkins/agent}}.I've seen mainly two suggested workarounds to the issue - change user/group in the container and use {{runAsUser}} in pod definition. None of this is relevant. To build a flexible CICD you want users to have an ability to specify a dockerhub image (well, at least a tag to whitelisted images) so change of image is not viable. Adding {{runAsUser: 1000}} might work in some limited cases but in reality not viable either. A lot of stuff (let's start with git client) will complain the user for that UID doesn't exist and crash.Just to summarize, expected behaviour would be: as long as{code} securityContext: fsGroup: 1000 supplementalGroups: - 1000{code}is set on the pod, using containers with non-root and non-{{/home/jenkins}} home should work just fine like they used to.I found another workaround, which is applying this on jnlp container:{code} command: - /bin/bash args: - "-c" - "umask 0002 002 ; jenkins-agent"{code}But I would imagine it wouldn't be secure? Or is it not?
Add Comment
[JIRA] (JENKINS-60033) InvalidPathException when scanning for issues
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60033 InvalidPathException when scanning for issues Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/254 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202858.1572860452000.9075.1572940680364%40Atlassian.JIRA.
[JIRA] (JENKINS-60054) Wrong umask? Containers with non-root user don't have permissions to agent durable script folders
Title: Message Title
Dmytro Kryvenko updated an issue
Jenkins / JENKINS-60054
Wrong umask? Containers with non-root user don't have permissions to agent durable script folders
Change By:
Dmytro Kryvenko
This setup used to work in older versions, I suspect regression happened somewhere around changing working directory to ` {{ /home/jenkins/agent ` }} .When running container with non-root user (of course having ` {{ fsGroup ` }} / ` {{ supplementalGroups ` }} to ` {{ 1000 ` }} to match jnlp slave GUID) getting the following error: ``` {{code}} process apparently never started in /home/jenkins/agent/workspace/ure-xxx-terraform-module_PR-1@tmp/durable-79996fba(running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) ``` {{code}} Doing that reveals: ``` {{code}} LAUNCHER: open /home/jenkins/agent/workspace/ure-xxx-terraform-module_PR-1@tmp/durable-cc0559df/jenkins-log.txt: permission denied ``` {{code}} I know there's a lot of similar issues being reported recently, but this one is different and not related to the ` {{ workingDir ` }} in ` {{ jnlp ` }} slave. I am using ` {{ jenkins/jnlp-slave:3.35-5-alpine ` }} image and have ` {{ workingDir ` }} correctly defaulting to ` {{ /home/jenkins/agent ` }} .I've seen mainly two suggested workarounds to the issue - change user/group in the container and use ` {{ runAsUser ` }} in pod definition. None of this is relevant. To build a flexible CICD you want users to have an ability to specify a dockerhub image (well, at least a tag to whitelisted images) so change of image is not viable. Adding ` {{ runAsUser: 1000 ` }} might work in some limited cases but in reality not viable either. A lot of stuff (let's start with git client) will complain the user for that UID doesn't exist and crash.Just to summarize, expected behaviour would be: as long as ``` {{code}} securityContext:fsGroup: 1000supplementalGroups:- 1000 ``` {{code}} is set on the pod, using containers with non-root and non- {{ /home/jenkins }} home should work just fine like they used to.I found another workaround, which is applying this on jnlp container: ``` {{code}} command: - /bin/bash args: - "-c" - "umask 0002; jenkins-agent" ``` {{code}} But I would imagine it wouldn't be secure? Or is it not?
[JIRA] (JENKINS-60054) Wrong umask? Containers with non-root user don't have permissions to agent durable script folders
Title: Message Title
Dmytro Kryvenko updated an issue
Jenkins / JENKINS-60054
Wrong umask? Containers with non-root user don't have permissions to agent durable script folders
Change By:
Dmytro Kryvenko
This setup used to work in older versions, I suspect regression happened somewhere around changing working directory to {{/home/jenkins/agent}}.When running container with non-root user (of course having {{fsGroup}}/{{supplementalGroups}} to {{1000}} to match jnlp slave GUID) getting the following error:{ { code} } process apparently never started in /home/jenkins/agent/workspace/ure-xxx-terraform-module_PR-1@tmp/durable-79996fba (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer){ { code} } Doing that reveals:{ { code} } LAUNCHER: open /home/jenkins/agent/workspace/ure-xxx-terraform-module_PR-1@tmp/durable-cc0559df/jenkins-log.txt: permission denied{ { code} } I know there's a lot of similar issues being reported recently, but this one is different and not related to the {{workingDir}} in {{jnlp}} slave. I am using {{jenkins/jnlp-slave:3.35-5-alpine}} image and have {{workingDir}} correctly defaulting to {{/home/jenkins/agent}}.I've seen mainly two suggested workarounds to the issue - change user/group in the container and use {{runAsUser}} in pod definition. None of this is relevant. To build a flexible CICD you want users to have an ability to specify a dockerhub image (well, at least a tag to whitelisted images) so change of image is not viable. Adding {{runAsUser: 1000}} might work in some limited cases but in reality not viable either. A lot of stuff (let's start with git client) will complain the user for that UID doesn't exist and crash.Just to summarize, expected behaviour would be: as long as{ { code} } securityContext: fsGroup: 1000 supplementalGroups: - 1000{ { code} } is set on the pod, using containers with non-root and non-{{/home/jenkins}} home should work just fine like they used to.I found another workaround, which is applying this on jnlp container:{ { code} } command: - /bin/bash args: - "-c" - "umask 0002; jenkins-agent"{ { code} } But I would imagine it wouldn't be secure? Or is it not?
Add Comment
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title efo plo commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Thanks Liam Newman. With your fix, can the attachment be compiled and run? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.9061.1572940140473%40Atlassian.JIRA.
[JIRA] (JENKINS-60054) Wrong umask? Containers with non-root user don't have permissions to agent durable script folders
Title: Message Title Dmytro Kryvenko created an issue Jenkins / JENKINS-60054 Wrong umask? Containers with non-root user don't have permissions to agent durable script folders Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-11-05 07:48 Environment: Jenkins: 2.190.2 kubernetes-plugin: 1.21.1 jnlp slave: jenkins/jnlp-slave:3.35-5-alpine Priority: Minor Reporter: Dmytro Kryvenko This setup used to work in older versions, I suspect regression happened somewhere around changing working directory to `/home/jenkins/agent`. When running container with non-root user (of course having `fsGroup`/`supplementalGroups` to `1000` to match jnlp slave GUID) getting the following error: ``` process apparently never started in /home/jenkins/agent/workspace/ure-xxx-terraform-module_PR-1@tmp/durable-79996fba (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) ``` Doing that reveals: ``` LAUNCHER: open /home/jenkins/agent/workspace/ure-xxx-terraform-module_PR-1@tmp/durable-cc0559df/jenkins-log.txt: permission denied ``` I know there's a lot of similar issues being reported recently, but this one is different and not related to the `workingDir` in `jnlp` slave. I am using `jenkins/jnlp-slave:3.35-5-alpine` image and have `workingDir` correctly defaulting to `/home/jenkins/agent`. I've seen mainly two suggested workarounds to the issue - change user/group in the container and use `runAsUser` in pod definition. None of this is relevant. To build a flexible CICD you want users to have an ability to specify a dockerhub image (well, at least a tag to whitelisted images) so change of image is not viable. Adding `runAsUser: 1000` might work in some limited cases but in
[JIRA] (JENKINS-59986) Exception "Illegal char" on build log event parsing
Title: Message Title Ulli Hafner started work on JENKINS-59986 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202792.1572447497000.9057.1572938760323%40Atlassian.JIRA.
[JIRA] (JENKINS-60033) InvalidPathException when scanning for issues
Title: Message Title Ulli Hafner started work on JENKINS-60033 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202858.1572860452000.9055.1572938760289%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Amit Dar edited a comment on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat I am about to upgrade my server to 2.190.2, does anyone know if this issue still present? (also using ArtifactDeployer...) *UPDATE:*looks like there is already a [PR|[https://github.com/jenkinsci/artifactdeployer-plugin/pull/13]] with the solution waiting for approval... [~seanturner83], can you handle this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.9042.1572937620513%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Amit Dar edited a comment on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat I am about to upgrade my server to 2.190.2, does anyone know if this issue still present? (also using ArtifactDeployer...) *UPDATE:*looks like there is already a [PR|[https://github.com/jenkinsci/artifactdeployer-plugin/pull/13]] with the solution waiting for approval... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.9028.1572937560398%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Amit Dar commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat I am about to upgrade my server to 2.190.2, does anyone know if this issue still present? (also using ArtifactDeployer...) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.9014.1572937201538%40Atlassian.JIRA.
[JIRA] (JENKINS-22400) Git timeout on other actions than fetch/clone
Title: Message Title Mark Waite updated JENKINS-22400 Jenkins / JENKINS-22400 Git timeout on other actions than fetch/clone Change By: Mark Waite Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154201.139599399.9003.1572931260592%40Atlassian.JIRA.
[JIRA] (JENKINS-12513) git plugin should automatically remove .git/index.lock if the job is killed
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-12513 git plugin should automatically remove .git/index.lock if the job is killed Change By: Mark Waite Assignee: Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142879.1327423442000.8967.1572931203134%40Atlassian.JIRA.
[JIRA] (JENKINS-12513) git plugin should automatically remove .git/index.lock if the job is killed
Title: Message Title Mark Waite updated JENKINS-12513 Jenkins / JENKINS-12513 git plugin should automatically remove .git/index.lock if the job is killed Change By: Mark Waite Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142879.1327423442000.8964.1572931203093%40Atlassian.JIRA.
[JIRA] (JENKINS-22400) Git timeout on other actions than fetch/clone
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-22400 Git timeout on other actions than fetch/clone Change By: Mark Waite Comment: Timeout support for JGit clone is first included in git client plugin 3.0.0-beta1. Prior to that version, JGit silently ignored timeout settings. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154201.139599399.8996.1572931203705%40Atlassian.JIRA.
[JIRA] (JENKINS-41392) disableConcurrentBuilds should take an optional boolean parameter that defaults to "true"
Title: Message Title
Nik Geo edited a comment on JENKINS-41392
Re: disableConcurrentBuilds should take an optional boolean parameter that defaults to "true"
Removing of disableConcurrentBuilds() in PR from scripted pipeline didn't affect my develop branch until I went and manually removed it from branch's config.xml {code:java}node { properties( [ disableConcurrentBuilds(), ] ) stage('stage 1') { sleep(3) }}{code} manual changes to config.xml{code:java}--org.jenkinsci.plugins.workflow.job.properties.DisableConcurrentBuildsJobProperty ... -- Jenkinsfile false {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178174.1485289108000.8927.1572930360437%40Atlassian.JIRA.
[JIRA] (JENKINS-41392) disableConcurrentBuilds should take an optional boolean parameter that defaults to "true"
Title: Message Title
Nik Geo commented on JENKINS-41392
Re: disableConcurrentBuilds should take an optional boolean parameter that defaults to "true"
Removing of disableConcurrentBuilds() in PR from scripted pipeline didn't affect my develop branch until I went and manually removed it from branch's config.xml
node {
properties(
[
disableConcurrentBuilds(),
]
)
stage('stage 1') {
sleep(3)
}
}
manual changes to config.xml
'1.1' encoding='UTF-8'?>
"workflow-job@2.34">
"workflow-multibranch@2.21">
--org.jenkinsci.plugins.workflow.job.properties.DisableConcurrentBuildsJobProperty
--
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-60052) Simplify git submodule update command
Title: Message Title Mark Waite commented on JENKINS-60052 Re: Simplify git submodule update command Per pull request 348 the --jobs argument first appeared in command line git 2.9.0. The Jenkins git plugin runs on CentOS 7, Debian 9, and Ubuntu 16, all that deliver a version prior to CLI git 2.9.0. Retaining compatibility with versions of command line git prior to 2.9.0 is crucial for the many users running on those versions of command line git. I believe there were also compatibility failures reported by the automated tests in the git client plugin or the git plugin. I didn't find references to automated test failures in a brief review of the comments on the pull request, but that's my recollection. The submodule implementation in the git client predates many of the improvements in command line git. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202882.1572927459000.8916.1572929580236%40Atlassian.JIRA.
[JIRA] (JENKINS-60053) Create null diff file on config history
Title: Message Title Владислав Ненашев updated an issue Jenkins / JENKINS-60053 Create null diff file on config history Change By: Владислав Ненашев Attachment: screenshot-2.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202883.1572928345000.8914.1572928500148%40Atlassian.JIRA.
[JIRA] (JENKINS-60053) Create null diff file on config history
Title: Message Title Владислав Ненашев updated an issue Jenkins / JENKINS-60053 Create null diff file on config history Change By: Владислав Ненашев Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202883.1572928345000.8912.1572928440260%40Atlassian.JIRA.
[JIRA] (JENKINS-60053) Create null diff file on config history
Title: Message Title
Владислав Ненашев updated an issue
Jenkins / JENKINS-60053
Create null diff file on config history
Change By:
Владислав Ненашев
We began to notice that the plug-in creates records of changes for no apparent reason for Job Configuration History Plugin 2.24 on [Jenkins ver. 2.176.3|https://jenkins.io/], which ultimately led to exhaustion inode on the disk array.I think it is necessary to modify the plugin, for the absence of empty saves.{code:java}root@SBT-OAINR-0077:/opt/jenkins/jenkins_home/config-history/jobs/AtlassianDevelopment/jobs/dpm/jobs/core/jobs/ci/jobs/PR_DPMCORE_Multibranch2/branches/master$ diff 2019-11-05_06-49-23/config.xml 2019-11-05_06-49-22/config.xmlroot@SBT-OAINR-0077:/opt/jenkins/jenkins_home/config-history/jobs/AtlassianDevelopment/jobs/dpm/jobs/core/jobs/ci/jobs/PR_DPMCORE_Multibranch2/branches/master$ diff 2019-11-05_06-49-23/history.xml 2019-11-05_06-49-22/history.xml6c6< 2019-11-05_06-49-23---> 2019-11-05_06-49-22root@SBT-OAINR-0077:/opt/jenkins/jenkins_home/config-history/jobs/AtlassianDevelopment/jobs/dpm/jobs/core/jobs/ci/jobs/PR_DPMCORE_Multibranch2/branches/master{code} !image-2019-11-05-11-29-48-833.png!!image-2019-11-05-11-31-09-466.png!
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60053) Create null diff file on config history
Title: Message Title Владислав Ненашев created an issue Jenkins / JENKINS-60053 Create null diff file on config history Issue Type: Bug Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2019-11-05 04:32 Priority: Blocker Reporter: Владислав Ненашев We began to notice that the plug-in creates records of changes for no apparent reason for Job Configuration History Plugin 2.24 on Jenkins ver. 2.176.3, which ultimately led to exhaustion inode on the disk array. I think it is necessary to modify the plugin, for the absence of empty saves. root@SBT-OAINR-0077:/opt/jenkins/jenkins_home/config-history/jobs/AtlassianDevelopment/jobs/dpm/jobs/core/jobs/ci/jobs/PR_DPMCORE_Multibranch2/branches/master$ diff 2019-11-05_06-49-23/config.xml 2019-11-05_06-49-22/config.xml root@SBT-OAINR-0077:/opt/jenkins/jenkins_home/config-history/jobs/AtlassianDevelopment/jobs/dpm/jobs/core/jobs/ci/jobs/PR_DPMCORE_Multibranch2/branches/master$ diff 2019-11-05_06-49-23/history.xml 2019-11-05_06-49-22/history.xml 6c6 < 2019-11-05_06-49-23 --- > 2019-11-05_06-49-22 root@SBT-OAINR-0077:/opt/jenkins/jenkins_home/config-history/jobs/AtlassianDevelopment/jobs/dpm/jobs/core/jobs/ci/jobs/PR_DPMCORE_Multibranch2/branches/master
[JIRA] (JENKINS-60052) Simplify git submodule update command
Title: Message Title Jesse Rittner commented on JENKINS-60052 Re: Simplify git submodule update command Can you clarify what compatibility issues were encountered? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202882.1572927459000.8904.1572928140192%40Atlassian.JIRA.
[JIRA] (JENKINS-60052) Simplify git submodule update command
Title: Message Title
Jesse Rittner updated an issue
Jenkins / JENKINS-60052
Simplify git submodule update command
Change By:
Jesse Rittner
For some reason, the git-client plugin iterates through the list of submodules (presumably by parsing the .gitmodules file) and manually issues a {{git submodule update}} command for each. Instead of this, it should simply issue a single {{git submodule update}} command without specifying a particular submodule, and the then let the CLI do its job.As part of this change, the new {{threads}} property of SubmoduleUpdateCommand should just be passed as {{--jobs}} rather than manually spawning threads in Java/Groovy.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-60035) Issue While executing job - Silk Performer & Jenkin Integration
Title: Message Title Chandrakumar Sekar updated an issue Jenkins / JENKINS-60035 Issue While executing job - Silk Performer & Jenkin Integration Change By: Chandrakumar Sekar Environment: Jenkin 2.190.1 & , Silk Performer 17.5 and Java 1.8 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202861.1572865762000.8902.1572928080151%40Atlassian.JIRA.
[JIRA] (JENKINS-60052) Simplify git submodule update command
Title: Message Title Mark Waite commented on JENKINS-60052 Re: Simplify git submodule update command That type of change was attempted as part of the threaded submodule update implementation. We were unable to retain compatibility with previous behaviors. Retaining compatibility is critical for users depending on the git plugin. If you have a pull request that retains compatibility and switches to use git submodule update, I'm confident there will be reviewers willing to assist with the review. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202882.1572927459000.8900.1572927900123%40Atlassian.JIRA.
[JIRA] (JENKINS-60052) Simplify git submodule update command
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60052 Simplify git submodule update command Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202882.1572927459000.8898.1572927720138%40Atlassian.JIRA.
[JIRA] (JENKINS-60052) Simplify git submoudle update command
Title: Message Title Jesse Rittner created an issue Jenkins / JENKINS-60052 Simplify git submoudle update command Issue Type: Story Assignee: Mark Waite Components: git-client-plugin Created: 2019-11-05 04:17 Priority: Minor Reporter: Jesse Rittner For some reason, the git-client plugin iterates through the list of submodules (presumably by parsing the .gitmodules file) and manually issues a git submodule update command for each. Instead of this, it should simply issue a single git submodule update command without specifying a particular submodule, and the let the CLI do its job. As part of this change, the new threads property of SubmoduleUpdateCommand should just be passed as --jobs rather than manually spawning threads in Java/Groovy. Add Comment
[JIRA] (JENKINS-60052) Simplify git submodule update command
Title: Message Title Jesse Rittner updated an issue Jenkins / JENKINS-60052 Simplify git submodule update command Change By: Jesse Rittner Summary: Simplify git submoudle submodule update command Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202882.1572927459000.8896.1572927480416%40Atlassian.JIRA.
[JIRA] (JENKINS-60035) Issue While executing job - Silk Performer & Jenkin Integration
Title: Message Title Chandrakumar Sekar updated an issue Jenkins / JENKINS-60035 Issue While executing job - Silk Performer & Jenkin Integration Change By: Chandrakumar Sekar Labels: Jenkin SilkPerformer plugin silk - silkperformer performer-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202861.1572865762000.8892.1572926040287%40Atlassian.JIRA.
[JIRA] (JENKINS-47154) GitHub Rate Limits are compared using the Jenkins master time not the http response's Date
Title: Message Title Liam Newman edited a comment on JENKINS-47154 Re: GitHub Rate Limits are compared using the Jenkins master time not the http response's Date The 10 hours issue may have been due to a date parsing issue in github-api: [https://github.com/github-api/github-api/commit/4802c97e89b0386fe6bb9cac63c97783e314b61d#diff-199201938f94e2f9ab096fe20ec4ab78] As for disabling the rate limit function we've already got a PR in the works to provide a simpler implementation. [https://github.com/jenkinsci/github-branch-source-plugin/pull/242] But the last bit of testing seems to have stalled out. Helping get this PR over the line would seem to be a much better use of your time than forking.However, not checking it is not an option. If you exceed the rate limit, GitHub will make you feel their pain. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185558.1506502537000.8879.1572923040915%40Atlassian.JIRA.
[JIRA] (JENKINS-47154) GitHub Rate Limits are compared using the Jenkins master time not the http response's Date
Title: Message Title Liam Newman commented on JENKINS-47154 Re: GitHub Rate Limits are compared using the Jenkins master time not the http response's Date The 10 hours issue may have been due to a date parsing issue in github-api: https://github.com/github-api/github-api/commit/4802c97e89b0386fe6bb9cac63c97783e314b61d#diff-199201938f94e2f9ab096fe20ec4ab78 As for disabling the rate limit function we've already got a PR in the works to provide a simpler implementation. https://github.com/jenkinsci/github-branch-source-plugin/pull/242 But the last bit of testing seems to have stalled out. Helping get this PR over the line would seem to be a much better use of your time than forking. However, not checking it is not an option. If you exceed the rate limit, GitHub will make you feel their pain. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185558.1506502537000.8877.1572923040890%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating
Title: Message Title Liam Newman edited a comment on JENKINS-59321 Re: github-branch-source plugin throws InvocationTargetException when creating [~lostinberlin]Here's a PR that I believe addresses your issue. Sorry for the wait. [https://github.com/jenkinsci/github-branch-source-plugin/pull/254] Once it passes CI and there is a link to an "incremental" in the PR, would you be willing to give it a try? (Here it is: [https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.9-rc941.09ba8e411aa7/] ) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.8863.1572922320153%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating
Title: Message Title Liam Newman edited a comment on JENKINS-59321 Re: github-branch-source plugin throws InvocationTargetException when creating [~lostinberlin]Here's a PR that I believe addresses your issue. Sorry for the wait. [https://github.com/jenkinsci/github-branch-source-plugin/pull/254] Okay, Once it isn't quite ready. But when it passes CI and there is a link to an "incremental" in the PR, would you be willing to give it a try for me ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.8860.1572920400181%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating
Title: Message Title Liam Newman edited a comment on JENKINS-59321 Re: github-branch-source plugin throws InvocationTargetException when creating [~lostinberlin]Here's a PR that I believe addresses your issue. Sorry for the wait. [https://github.com/jenkinsci/github-branch-source-plugin/pull/254] Assuming it passes CI Okay , there will it isn't quite ready. But when it is would you be a link willing to an incremental you can give it try out. for me? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.8857.1572918480384%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating
Title: Message Title Liam Newman commented on JENKINS-59321 Re: github-branch-source plugin throws InvocationTargetException when creating Steve Boardwell Here's a PR that I believe addresses your issue. Sorry for the wait. https://github.com/jenkinsci/github-branch-source-plugin/pull/254 Assuming it passes CI, there will be a link to an incremental you can try out. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.8854.1572916620256%40Atlassian.JIRA.
[JIRA] (JENKINS-60051) A blocked Project still occupies an Executor
Title: Message Title
Mikhail T created an issue
Jenkins / JENKINS-60051
A blocked Project still occupies an Executor
Issue Type:
Bug
Assignee:
Unassigned
Components:
core, parameterized-trigger-plugin
Created:
2019-11-05 01:09
Priority:
Minor
Reporter:
Mikhail T
I've created a job, that builds the same sources into 32- or 64-bit binaries depending on the build parameter. The name of the job is "Compile". I then created two convenience wrapper-projects, one for each architecture: "Compile-64" and "Compile-32". The wrapper-projects do nothing other than trigger a build of compile with the correct parameter (using the Parametrized Parameter Plugin as suggested here). The checkbox for "Block until the triggered projects finish their builds" is On. If I start both of the wrapper projects ("Compile-64" and "Compile-32") they both kick off an instance of "Compile", as one would expect. Unfortunately, those triggered instances of "Compile" never actually begin – they remain pending, because our only two Executors are occupied by the blocked wrappers. A classic deadlock caused by the blocked builds still occupying an executor...
Add Comment
[JIRA] (JENKINS-60050) Add title into the ChangeRequestSCMHead interface
Title: Message Title Rick started work on JENKINS-60050 Change By: Rick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202880.1572913411000.8850.1572913500134%40Atlassian.JIRA.
[JIRA] (JENKINS-60050) Add title into the ChangeRequestSCMHead interface
Title: Message Title Rick updated JENKINS-60050 Jenkins / JENKINS-60050 Add title into the ChangeRequestSCMHead interface Change By: Rick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202880.1572913411000.8851.1572913500183%40Atlassian.JIRA.
[JIRA] (JENKINS-60050) Add title into the ChangeRequestSCMHead interface
Title: Message Title Rick created an issue Jenkins / JENKINS-60050 Add title into the ChangeRequestSCMHead interface Issue Type: Improvement Assignee: Rick Components: scm-api-plugin Created: 2019-11-05 00:23 Priority: Minor Reporter: Rick As we know change requests in many git providers are necessary such as GitHub, Gitlab and so on. In my use cases, users want to get the title which they might send build email base on the change request title. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-59980) Merge beforeOptions, beforeInput and beforeAgent into a single before attribute
Title: Message Title Falko Modler commented on JENKINS-59980 Re: Merge beforeOptions, beforeInput and beforeAgent into a single before attribute Liam Newman While I am always glad to help improving Jenkins (plugins) I currently don't have time for this, sorry. PS: Are you sure about changing the example from before 'options' to before git? Right now we don't have beforeGit, so do you have something new in mind? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202785.1572385981000.8847.1572911880256%40Atlassian.JIRA.
[JIRA] (JENKINS-59980) Merge beforeOptions, beforeInput and beforeAgent into a single before attribute
Title: Message Title Liam Newman edited a comment on JENKINS-59980 Re: Merge beforeOptions, beforeInput and beforeAgent into a single before attribute This is totally doable and would likely have minimal impact. It could even be done without changing the underlying AST representation if needed. [~famod] Are you interested in submitting this change? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202785.1572385981000.8831.1572911520782%40Atlassian.JIRA.
[JIRA] (JENKINS-59980) Merge beforeOptions, beforeInput and beforeAgent into a single before attribute
Title: Message Title Liam Newman commented on JENKINS-59980 Re: Merge beforeOptions, beforeInput and beforeAgent into a single before attribute This is totally doable and would likely have minimal impact. It could even be done without changing the underlying AST representation if needed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202785.1572385981000.8828.1572911460173%40Atlassian.JIRA.
[JIRA] (JENKINS-59980) Merge beforeOptions, beforeInput and beforeAgent into a single before attribute
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-59980
Merge beforeOptions, beforeInput and beforeAgent into a single before attribute
Change By:
Liam Newman
There are now _three_ different {{before}} attributes for {{when}} which are evaluated in this very order:- {{beforeOptions}}- {{beforeInput}}- {{beforeAgent}}The documentation tries to describe this "highlander principle" but it would be much more logical and readable if there was only a single attribute {{before}} allowing only a single value of {{options}}, {{input}} or {{agent}}.E.g.:{noformat}when {before 'options' git // ...}{noformat} Migration consideration: The old dedicated {{before}} attributes should not be removed right away. Instead those attributes should be marked deprecated and their usage should yield warnings in the log.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Alex Katz edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
I'm encountering the same error message on Ubuntu 18.04 except it seems to be breaking a git checkout step ({{checkout scm}}) and possibly other sh steps, not in a docker container. Also running durable-task v1.33 but also running lots of other plugins and I haven't tried reproducing the issue on clean system yet.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.8822.1572910080173%40Atlassian.JIRA.
[JIRA] (JENKINS-60049) Sonar Quality Gate plugin Throwing 400 after 8.0 Upgrade
Title: Message Title vishnu jam updated an issue Jenkins / JENKINS-60049 Sonar Quality Gate plugin Throwing 400 after 8.0 Upgrade Change By: vishnu jam Summary: Sonar Quality Gate plugin Throwing 400 after 8.0 Upgrade Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202878.1572909422000.8812.1572909480716%40Atlassian.JIRA.
[JIRA] (JENKINS-60049) Sonar Quality Gate plugin Throwing 400 after 8.0 Upgrade
Title: Message Title vishnu jam updated an issue Jenkins / JENKINS-60049 Sonar Quality Gate plugin Throwing 400 after 8.0 Upgrade Change By: vishnu jam Summary: Sonar QUALITY GATE Quality Gate plugin Throwing 400 after 8.0 Upgrade Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202878.1572909422000.8810.1572909480677%40Atlassian.JIRA.
[JIRA] (JENKINS-60049) Sonar QUALITY GATE Throwing after 8.0 Upgrade
Title: Message Title vishnu jam created an issue Jenkins / JENKINS-60049 Sonar QUALITY GATE Throwing after 8.0 Upgrade Issue Type: Bug Assignee: Ivana Sh Components: quality-gates-plugin Created: 2019-11-04 23:17 Priority: Major Reporter: vishnu jam After SQ upgrade the plugin throwing an error "msg":"The 'component' parameter is missing"}]}"msg":"The 'component' parameter is missing"}]} at org.quality.gates.sonar.api.SonarHttpRequester.executeGetRequest(SonarHttpRequester.java:124) The Jenkins Plugin used : 1.3.1 The SQ community passed a reference https://community.sonarsource.com/t/the-component-parameter-is-missing/13736/4 Add Comment
[JIRA] (JENKINS-60049) Sonar QUALITY GATE plugin Throwing 400 after 8.0 Upgrade
Title: Message Title vishnu jam updated an issue Jenkins / JENKINS-60049 Sonar QUALITY GATE plugin Throwing 400 after 8.0 Upgrade Change By: vishnu jam Summary: Sonar QUALITY GATE plugin Throwing 400 after 8.0 Upgrade Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202878.1572909422000.8808.1572909480642%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Alex Katz edited a comment on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container I'm encountering the same error message on Ubuntu 18.04 except it seems to be breaking a git checkout step and possibly other sh steps, not in a docker container. Also running durable-task v1.33 but also running lots of other plugins and I haven't tried reproducing the issue on clean system yet. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.8803.1572908820192%40Atlassian.JIRA.
[JIRA] (JENKINS-60048) Forensics date relative to build date
Title: Message Title Andreas Pabst created an issue Jenkins / JENKINS-60048 Forensics date relative to build date Issue Type: Bug Assignee: Unassigned Components: forensics-api-plugin, warnings-ng-plugin Created: 2019-11-04 23:05 Priority: Minor Reporter: Andreas Pabst The "Last Commit" and "Added"-Columns in the forensics table show the date relative to the date of the build (e.g. 2 days ago). But when viewing the build information, I would expect the date to be relative to the current time. Otherwise one has to calculate the time of the commit by adding the time that has passed since the build, which I find to be quite cumbersome. This is related to JENKINS-60014 and the discussion in https://github.com/jenkinsci/forensics-api-plugin/pull/47. Add Comment
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Alex Katz edited a comment on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container I'm encountering the same error message on Ubuntu 18.04 except it seems to be breaking a git checkout step and possibly other sh steps , not in a docker container . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.8799.1572908640190%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Alex Katz edited a comment on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container I'm encountering the same issue error message on Ubuntu 18.04 except it seems to be breaking a git checkout step and possibly other sh steps. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.8796.1572908580189%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Alex Katz edited a comment on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container I'm encountering the a similar same issue on Amazon Linux 2018.03 and Ubuntu 18.04 with the same error message. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.8793.1572908220164%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Alex Katz edited a comment on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container I'm encountering the same a similar issue on Amazon Linux 2018.03 and Ubuntu 18.04 with the same error message. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.8790.1572907380189%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Alex Katz commented on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container I'm encountering the same issue on Amazon Linux 2018.03 and Ubuntu 18.04 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.8787.1572907320162%40Atlassian.JIRA.
[JIRA] (JENKINS-57435) Cannot configure SSH credentials via Job DSL
Title: Message Title René Scheibe commented on JENKINS-57435 Re: Cannot configure SSH credentials via Job DSL The same issue exists with the https://github.com/jenkinsci/plain-credentials-plugin. It also uses a Secret parameter. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199248.1557757091000.8780.1572906960216%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman updated JENKINS-56500 Jenkins / JENKINS-56500 Declarative pipeline restricted in code size Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8769.1572906720810%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman edited a comment on JENKINS-56500
Re: Declarative pipeline restricted in code size
There is partial fix for this in v1.4.0. Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting the a JVM property \ (either on the command-line or in Jenkins script console): { { org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true }. }} As noted, this still works to some extent for pipelines using `def` variables, but not as well. Please give it a try and provide feedback.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8700.1572906661865%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Liam Newman commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script If you are using Declarative: There is partial fix for this in v1.4.0. Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting a JVM property (either on the command-line or in Jenkins script console): org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true As noted, this still works to some extent for pipelines using `def` variables, but not as well. Please give it a try and provide feedback. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.8702.1572906661897%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman commented on JENKINS-56500
Re: Declarative pipeline restricted in code size
There is partial fix for this in v1.4.0. Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting the property {org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true}. As noted, this still works to some extent for pipelines using `def` variables, but not as well. Please give it a try and provide feedback.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8680.1572906540276%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman updated JENKINS-56500 Jenkins / JENKINS-56500 Declarative pipeline restricted in code size Change By: Liam Newman Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8669.1572906241365%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman started work on JENKINS-56500 Change By: Liam Newman Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8667.1572906241340%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Steve Graham commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. ok - thanks. I got my build failure list from 1 year ago back again. BFA version is now 1.24. , jenkins is 2.202 ( just about to go up to 2.203 ) I tried changing the global config and my build-failure list is still there. Relieved but still lost any additions I made in the last year. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202251.1569939008000.8651.1572903660257%40Atlassian.JIRA.
[JIRA] (JENKINS-60044) mavenConsole tool doesn't extract compile warnings
Title: Message Title Ulli Hafner commented on JENKINS-60044 Re: mavenConsole tool doesn't extract compile warnings Typically, maven users have both parsers installed. In this case it would be surprising to see the same warning twice. Additionally, maven warnings and compiler warnings share no common properties. (Example: https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/master/629/) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202872.1572887363000.8648.1572903540155%40Atlassian.JIRA.
[JIRA] (JENKINS-60047) Jenkins hangs after network instability(packet loss)
Title: Message Title
Qiuchen Dong created an issue
Jenkins / JENKINS-60047
Jenkins hangs after network instability(packet loss)
Issue Type:
Bug
Assignee:
Jeff Thompson
Components:
core, remoting
Created:
2019-11-04 20:26
Environment:
Jenkins 2.138, Jenkins 2.190.2; Windows 10
Priority:
Major
Reporter:
Qiuchen Dong
We seem to have some network instability. Every week or so, all our agents disconnect from Jenkins and Jenkins becomes unresponsive. Jenkins needs to be restarted afterwards. Looking at build logs, they all seem to disconnect at the same time (possibly due to network load). Jenkins logs are not showing any errors. I've managed to reproduce similar symptoms with a local version of jenkins simulating a bad network: 1. Have default jenkins instance running on localhost ("java -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar jenkins.war --httpPort=12000") 2. Open the jenkins webpage and login to landing page 25 times (chrome) 3. Use Clumsy 0.2 to drop all packets for 40s on localhost TCP - IPV4 Expected Result: Jenkins webpage loads after we stop dropping packets Actual Result: Jenkins webpage is unresponsive. Agents cannot no longer connect through JNLP3 or JNLP4
[JIRA] (JENKINS-60046) Validate Credentials Id during Pipeline validation, similar to tools
Title: Message Title Liam Newman commented on JENKINS-60046 Re: Validate Credentials Id during Pipeline validation, similar to tools Some work was done on this, but it was not completed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202875.1572898903000.8644.1572899040116%40Atlassian.JIRA.
[JIRA] (JENKINS-60046) Validate Credentials Id during Pipeline validation, similar to tools
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-60046 Validate Credentials Id during Pipeline validation, similar to tools Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2019-11-04 20:21 Priority: Minor Reporter: Liam Newman We should be able to validate credentials id during Pipeline validation similar to what we do with tools. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title jerry wiltse commented on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script This matrix is how I learned about it. It might be helpful to you: https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8634.1572898800155%40Atlassian.JIRA.
[JIRA] (JENKINS-41759) Add possibilities to read environment from trusted properties file
Title: Message Title Liam Newman commented on JENKINS-41759 Re: Add possibilities to read environment from trusted properties file Michael Fowler No, the code was never merged. See the linked PR for details. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178600.1486387032000.8606.1572898441000%40Atlassian.JIRA.
[JIRA] (JENKINS-41759) Add possibilities to read environment from trusted properties file
Title: Message Title Liam Newman assigned an issue to Unassigned Jenkins / JENKINS-41759 Add possibilities to read environment from trusted properties file Change By: Liam Newman Assignee: Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178600.1486387032000.8628.1572898441264%40Atlassian.JIRA.
[JIRA] (JENKINS-41759) Add possibilities to read environment from trusted properties file
Title: Message Title Liam Newman assigned an issue to Andrew Bayer Jenkins / JENKINS-41759 Add possibilities to read environment from trusted properties file Change By: Liam Newman Assignee: rsandell Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178600.1486387032000.8625.1572898441231%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title a b commented on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script We're on the latest version 19.03.4 on Server 2019 (1809) now. Just edited my previous comment with more info. I get different results from docker build if I add the --isolation flag. Fails either way but getting a different result makes me thing it's attempting to apply the isolation setting. Either way I don't think it will solve our issues. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8612.1572898441078%40Atlassian.JIRA.
[JIRA] (JENKINS-41759) Add possibilities to read environment from trusted properties file
Title: Message Title Liam Newman stopped work on JENKINS-41759 Change By: Liam Newman Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178600.1486387032000.8618.1572898441143%40Atlassian.JIRA.
[JIRA] (JENKINS-41759) Add possibilities to read environment from trusted properties file
Title: Message Title Liam Newman updated JENKINS-41759 Jenkins / JENKINS-41759 Add possibilities to read environment from trusted properties file Change By: Liam Newman Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178600.1486387032000.8596.1572898380483%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title
a b edited a comment on JENKINS-59893
Re: bat calls hang in Windows Docker container in declarative pipeline script
[~solvingj] Does not work for me. At least not when trying to pull a 1903 image on Server 2019 1809. Maybe I only works for backward comparability, not forward? {code:java}>docker build --isolation="hyperv" -t "test_full" -f Dockerfile_1903 . Sending build context to Docker daemon 13.82kB Step 1/7 : FROM mcr.microsoft.com/powershell:7.0.0-preview.5-nanoserver-1903 7.0.0-preview.5-nanoserver-1903: Pulling from powershell a Windows version 10.0.18362-based image is incompatible with a 10.0.17763 host{code}*Edit*: If I try and older version like _nanoserver-1803_ I get "_The container operating system does not match the host operating system_." on a powershell step.without the --isolation flag. When adding the flag I get " The _The request is not supported supported_ ." on the same step.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8594.1572898260284%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title jerry wiltse commented on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script I think you either need to be on a newer version of docker, or you need to enable experimental features. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8576.1572898203531%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title jerry wiltse edited a comment on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script I don't use quotes, but i don't think that's the issue. I think you either need to be on a newer version of docker, or you need to enable experimental features. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8584.1572898203819%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title
a b edited a comment on JENKINS-59893
Re: bat calls hang in Windows Docker container in declarative pipeline script
[~solvingj] Does not work for me. At least not when trying to pull a 1903 image on Server 2019 1809. Maybe I only works for backward comparability, not forward? {code:java}>docker build --isolation="hyperv" -t "test_full" -f Dockerfile_1903 . Sending build context to Docker daemon 13.82kB Step 1/7 : FROM mcr.microsoft.com/powershell:7.0.0-preview.5-nanoserver-1903 7.0.0-preview.5-nanoserver-1903: Pulling from powershell a Windows version 10.0.18362-based image is incompatible with a 10.0.17763 host{code}*Edit*: If I try and older version like _nanoserver-1803_ I get " The _The container operating system does not match the host operating system system_ ." on a powershell step.without the --isolation flag. When adding the flag I get "The request is not supported." on the same step.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8582.1572898203654%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title
a b edited a comment on JENKINS-59893
Re: bat calls hang in Windows Docker container in declarative pipeline script
[~solvingj] Does not work for me. At least not when trying to pull a 1903 image on Server 2019 1809. Maybe I only works for backward comparability, not forward? ** {code:java}>docker build --isolation="hyperv" -t "test_full" -f Dockerfile_1903 . Sending build context to Docker daemon 13.82kB Step 1/7 : FROM mcr.microsoft.com/powershell:7.0.0-preview.5-nanoserver-1903 7.0.0-preview.5-nanoserver-1903: Pulling from powershell a Windows version 10.0.18362-based image is incompatible with a 10.0.17763 host{code}*Edit*: If I try and older version I get ` "The container operating system does not match the host operating system." ` on a powershell step.without the ` --isolation ` flag. When adding the flag I get ` " The request is not supported. ` " on the same step.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8570.1572898080303%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title
a b edited a comment on JENKINS-59893
Re: bat calls hang in Windows Docker container in declarative pipeline script
[~solvingj] Does not work for me. At least not when trying to pull a 1903 image on Server 2019 1809. Maybe I only works for backward comparability, not forward? ** {code:java}>docker build --isolation="hyperv" -t "test_full" -f Dockerfile_1903 . Sending build context to Docker daemon 13.82kB Step 1/7 : FROM mcr.microsoft.com/powershell:7.0.0-preview.5-nanoserver-1903 7.0.0-preview.5-nanoserver-1903: Pulling from powershell a Windows version 10.0.18362-based image is incompatible with a 10.0.17763 host{code} *Edit*: If I try and older version I get `"The container operating system does not match the host operating system."` on a powershell step.without the `--isolation` flag. When adding the flag I get `The request is not supported.` on the same step.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8564.1572898020292%40Atlassian.JIRA.
[JIRA] (JENKINS-60044) mavenConsole tool doesn't extract compile warnings
Title: Message Title James Howe commented on JENKINS-60044 Re: mavenConsole tool doesn't extract compile warnings Ah, that's quite surprising behaviour. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202872.1572887363000.8558.1572897300248%40Atlassian.JIRA.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198858.1555612432000.8555.1572896820487%40Atlassian.JIRA.
[JIRA] (JENKINS-60041) P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Title: Message Title Ken Morse commented on JENKINS-60041 Re: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US Sure, Karl Wirth – log of brand new Freestyle job below and screenshot attached. Started by user Ken Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on buildvpc10 in workspace E:\WinPC\Main\p4test (p4):cmd:... p4 login -s p4 login -s User p4dti-replicator0 ticket expires in 8 hours 40 minutes. (p4):stop:3 (p4):cmd:... p4 client -o BuildMachine-Perforce-Test p4 client -o BuildMachine-Perforce-Test (p4):stop:4 (p4):cmd:... p4 counter change p4 counter change (p4):stop:5 (p4):cmd:... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/... Change 34054 on 2014/03/05 by Ken@Ken_Viper_P4Test 'Test change 2 of 2. ' (p4):stop:6 (p4):cmd:... p4 counter change p4 counter change (p4):stop:7 (p4):cmd:... p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...@33054,34054 p4 changes -m1 -ssubmitted //BuildMachine-Perforce-Test/...@33054,34054 Change 34054 on 2014/03/05 by Ken@Ken_Viper_P4Test 'Test change 2 of 2. ' (p4):stop:8 P4: builds: 34054 P4: Connection retry: 1 Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US ERROR: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60041) P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Title: Message Title Ken Morse updated an issue Jenkins / JENKINS-60041 P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US Change By: Ken Morse Attachment: P4SCM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202869.1572884428000.8551.1572894300310%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title
a b edited a comment on JENKINS-59893
Re: bat calls hang in Windows Docker container in declarative pipeline script
[~solvingj] Does not work for me. At least not when trying to pull a 1903 image on Server 2019 1809. Maybe I only works for backward comparability, not forward? {code:java}>docker build --isolation="hyperv" -t "test_full" -f Dockerfile_1903 .Sending build context to Docker daemon 13.82kBStep 1/7 : FROM mcr.microsoft.com/powershell:7.0.0-preview.5-nanoserver-19037.0.0-preview.5-nanoserver-1903: Pulling from powershella Windows version 10.0.18362-based image is incompatible with a 10.0.17763 host{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8544.1572894120586%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title a b commented on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script jerry wiltse Does not work for me. At least not when trying to pull a 1903 image on Server 2019 1809. Maybe I only works for backward comparability, not forward? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.8543.1572894120576%40Atlassian.JIRA.
[JIRA] (JENKINS-60044) mavenConsole tool doesn't extract compile warnings
Title: Message Title Ulli Hafner updated JENKINS-60044 Jenkins / JENKINS-60044 mavenConsole tool doesn't extract compile warnings Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202872.1572887363000.8535.1572893760330%40Atlassian.JIRA.
[JIRA] (JENKINS-60044) mavenConsole tool doesn't extract compile warnings
Title: Message Title Ulli Hafner updated JENKINS-60044 This is intentional. There are specific parsers for the compile goal. In your case the Java parser will find these warnings. All other warnings are picked up by the maven console parser. Jenkins / JENKINS-60044 mavenConsole tool doesn't extract compile warnings Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-59793) Possible thread leak 'QueueSubTaskMetrics' in metrics
Title: Message Title Ramon Leon commented on JENKINS-59793 Re: Possible thread leak 'QueueSubTaskMetrics' in metrics I’m trying to cancel jobs while in the Queue (cancel) or once running (getExecutor().interrupt()), but in this way, the job is correctly finished so the metrics thread is freed. I need to figure out a way to kill a job in a way that the future is not set in the WorkUnitContext: https://github.com/jenkinsci/jenkins/blob/264980c707c6cafc01369378b1e90d247561df78/core/src/main/java/hudson/model/queue/WorkUnitContext.java#L132 Most likely playing with several executors and subtasks and interrupting some of them. Still working, any clue on how to achieve that is welcome Daniel Beck Jesse Glick Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202523.1571157685000.8531.1572889080294%40Atlassian.JIRA.
[JIRA] (JENKINS-60041) P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Title: Message Title Karl Wirth commented on JENKINS-60041 Re: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US Hi Ken Morse - Can you please try creating a new freestyle job that just does an SCM sync from Perforce and see if the same error occurs. If it does please send me the full console log and a screen shot showing the SCM configuration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202869.1572884428000.8525.1572889020185%40Atlassian.JIRA.
[JIRA] (JENKINS-60045) JCasC export doesn't work with Custom Tools installed and configured
Title: Message Title TJ Rue created an issue Jenkins / JENKINS-60045 JCasC export doesn't work with Custom Tools installed and configured Issue Type: Bug Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin, customtools-plugin Created: 2019-11-04 17:28 Environment: QA Priority: Minor Reporter: TJ Rue When the Custom Tools plugin is installed and a Custom Tool is configured and JCasc 'View Configuration' button is clicked and the following error results in the Casc output: ```customTool: installations: |- FAILED TO EXPORT com.cloudbees.jenkins.plugins.customtools.CustomTool$DescriptorImpl#installations: java.lang.IllegalArgumentException: argument type mismatch at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423)``` I attempted this with the following versions: Configuration as Code Plugin version 1.32 Configuration as Code Support Plugin version 1.19 Custom Tools version .6 Jenkins version 2.190.1
[JIRA] (JENKINS-60044) mavenConsole tool doesn't extract compile warnings
Title: Message Title James Howe created an issue Jenkins / JENKINS-60044 mavenConsole tool doesn't extract compile warnings Issue Type: Bug Assignee: Ulli Hafner Attachments: image-2019-11-04-17-08-44-596.png Components: warnings-ng-plugin Created: 2019-11-04 17:09 Environment: Jenkins 2.190.2 Warnings 7.1.0 Maven 3.6.2 Priority: Major Reporter: James Howe I have a build that logs multiple warnings across multiple maven executions. However the warning plugin is only picking up the warnings from add-resource and test, not compile nor testCompile. recordIssues tool: mavenConsole(), qualityGates: [[threshold: 1, type: 'TOTAL', unstable: true]] Console log (abbreviated) [INFO] --- license-maven-plugin:2.0.0:add-third-party (default) @ project --- [WARNING] [WARNING] licenseMerges will be overridden by licenseMergesUrl. [WARNING] [INFO] Writing third-party file to
[JIRA] (JENKINS-57012) Allow folder scope credential for Jira connection
Title: Message Title Mathieu Delrocq updated JENKINS-57012 Jenkins / JENKINS-57012 Allow folder scope credential for Jira connection Change By: Mathieu Delrocq Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198713.1555344179000.8515.1572886200481%40Atlassian.JIRA.
[JIRA] (JENKINS-57012) Allow folder scope credential for Jira connection
Title: Message Title Mathieu Delrocq updated JENKINS-57012 Jenkins / JENKINS-57012 Allow folder scope credential for Jira connection Change By: Mathieu Delrocq Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198713.1555344179000.8517.1572886200515%40Atlassian.JIRA.
[JIRA] (JENKINS-57012) Allow folder scope credential for Jira connection
Title: Message Title Mathieu Delrocq updated JENKINS-57012 Jenkins / JENKINS-57012 Allow folder scope credential for Jira connection Change By: Mathieu Delrocq Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198713.1555344179000.8509.1572886140228%40Atlassian.JIRA.
[JIRA] (JENKINS-59989) Cannot Run Tests from ALM after upgrading to 5.8
Title: Message Title Anda Sorina Laakso commented on JENKINS-59989 Re: Cannot Run Tests from ALM after upgrading to 5.8 Hi Julian, Can you tell where I could upload the fix for you to test it? Maybe an ftp server. I want to confirm that the issue is fixed before introducing it in the next release. Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202796.1572457328000.8505.1572886020685%40Atlassian.JIRA.
[JIRA] (JENKINS-59989) Cannot Run Tests from ALM after upgrading to 5.8
Title: Message Title Anda Sorina Laakso edited a comment on JENKINS-59989 Re: Cannot Run Tests from ALM after upgrading to 5.8 Hi Julian,Can you tell where I could upload the fix for you to test it? Maybe an ftp server.I want to confirm that the issue is fixed before introducing it in the next release. My email is: anda-sorina.laa...@microfocus.com . Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202796.1572457328000.8507.1572886080126%40Atlassian.JIRA.
[JIRA] (JENKINS-57012) Allow folder scope credential for Jira connection
Title: Message Title Mathieu Delrocq updated JENKINS-57012 Jenkins / JENKINS-57012 Allow folder scope credential for Jira connection Change By: Mathieu Delrocq Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198713.1555344179000.8503.1572886020628%40Atlassian.JIRA.
