[JIRA] (TEST-177) Issue1
Title: Message Title sangavi vijay created an issue test / TEST-177 Issue1 Issue Type: Task Assignee: Oleg Nenashev Components: foo13 Created: 2019-09-24 05:14 Priority: Minor Reporter: sangavi vijay 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
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite commented on JENKINS-59497 Re: Git clone in pipeline ignoring reference repo The RelativeTargetDir extension is not recommended for use in Pipeline. The dir() and ws() directives are native Pipeline directives that are better suited for use than the git plugin specific extension RelativeTargetDir. That does not affect this case, but is good advice for your implementation. My test cases used both dir() and RelativeTargetDir successfully. 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.202115.1569286759000.3836.1569299460303%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite updated JENKINS-59497 Jenkins / JENKINS-59497 Git clone in pipeline ignoring reference repo Change By: Mark Waite Status: Fixed but Unreleased 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.202115.1569286759000.3841.1569299460375%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite updated JENKINS-59497 Jenkins / JENKINS-59497 Git clone in pipeline ignoring reference repo Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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.202115.1569286759000.3831.1569299340302%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite commented on JENKINS-59497 Re: Git clone in pipeline ignoring reference repo I can't duplicate the problem you're describing. I've created a test job that confirms the reference repository is honored by both command line git and JGit. I've confirmed that for the command line git implementation, the diagnostic message is consistently printed and the reference repository is consistently used. The reference repository path may be specified incorrectly in the checkout step. The reference repository may be missing on the agent where the workspace is being created. 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.202115.1569286759000.3829.1569299340272%40Atlassian.JIRA.
[JIRA] (JENKINS-59499) Job timed out - Tests Aborted - Still tests are marked as passed
Title: Message Title Sanjeeth Nayak updated an issue Jenkins / JENKINS-59499 Job timed out - Tests Aborted - Still tests are marked as passed Change By: Sanjeeth Nayak Test runs getting aborted due to job time out issue. And result pan will mark all the not run tests as passed (Which is dangerous as we might blindly think tests have passed but it has not even attempted to run)Logs: Started by upstream project "DM_UAT_TestPipelines/Pipeline-DM_DPTBs_FAR-GER" build number 24 originally caused by: Started by timer Running as SYSTEM Building in workspace D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC [JOBFOLDER_ABC] $ D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC\HpToolsLauncher.exe -paramfile props24092019010010681.txt "Started..." Timeout is set to: 5000 Run mode is set to: RUN_REMOTE Starting test set execution Test set name: Reg_ABC, Test set id: 5103 Number of tests in set: 15 Test 1: [1]004_a_abc will run on host: ne2dhtm0111 Test 2: [1]005_a_abc will run on host: ne2dhtm0111 Test 3: [1]006_a_abc will run on host: ne2dhtm0111 Test 4: [1]007_a_abc will run on host: ne2dhtm0111 Test 5: [1]008_a_abcItinerary will run on host: ne2dhtm0111 Test 6: [1]009_a_abc will run on host: ne2dhtm0111 Test 7: [1]013_a_abc will run on host: ne2dhtm0111 Test 8: [1]017_a_abc will run on host: ne2dhtm0111 Test 9: [1]016_a_abc will run on host: ne2dhtm0111 Test 10: [1]018_a_abc will run on host: ne2dhtm0111 Test 11: [1]019_a_abc will run on host: ne2dhtm0111 Test 12: [1]010_a_abcr will run on host: ne2dhtm0111 Test 13: [1]011_a_abc will run on host: ne2dhtm0111 Test 14: [1]012_a_abc will run on host: ne2dhtm0111 Test 15: [1]014_a_abc will run on host: ne2dhtm0111 "Scheduler started at:24/09/2019 01:00:16 --- 24/09/2019 01:00:16 Running: [1]004_a_abc 24/09/2019 01:00:16 Running test: [1]004_a_abc, Test id: 547, Test instance id: 764 Test: [1]004_a_abc, Id: 764, Execution status: Running Close last test 24/09/2019 02:23:33 Test complete: [1]004_a_Acceptance --- Test: [1]004_a_abc, Status: Running, Message: Connecting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312313 Test: [1]005_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=17632 Test: [1]006_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312314 Test: [1]007_a_abc, Status:
[JIRA] (JENKINS-59499) Job timed out - Tests Aborted - Still tests are marked as passed
Title: Message Title Sanjeeth Nayak updated an issue Jenkins / JENKINS-59499 Job timed out - Tests Aborted - Still tests are marked as passed Change By: Sanjeeth Nayak Started by upstream project "DM_UAT_TestPipelines/Pipeline- DM_PDBTs_FAR DM_DPTBs_FAR -GER" build number 24 originally caused by: Started by timer Running as SYSTEM Building in workspace D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC [JOBFOLDER_ABC] $ D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC\HpToolsLauncher.exe -paramfile props24092019010010681.txt "Started..." Timeout is set to: 5000 Run mode is set to: RUN_REMOTE Starting test set execution Test set name: Reg_ABC, Test set id: 5103 Number of tests in set: 15 Test 1: [1]004_a_abc will run on host: ne2dhtm0111 Test 2: [1]005_a_abc will run on host: ne2dhtm0111 Test 3: [1]006_a_abc will run on host: ne2dhtm0111 Test 4: [1]007_a_abc will run on host: ne2dhtm0111 Test 5: [1]008_a_abcItinerary will run on host: ne2dhtm0111 Test 6: [1]009_a_abc will run on host: ne2dhtm0111 Test 7: [1]013_a_abc will run on host: ne2dhtm0111 Test 8: [1]017_a_abc will run on host: ne2dhtm0111 Test 9: [1]016_a_abc will run on host: ne2dhtm0111 Test 10: [1]018_a_abc will run on host: ne2dhtm0111 Test 11: [1]019_a_abc will run on host: ne2dhtm0111 Test 12: [1]010_a_abcr will run on host: ne2dhtm0111 Test 13: [1]011_a_abc will run on host: ne2dhtm0111 Test 14: [1]012_a_abc will run on host: ne2dhtm0111 Test 15: [1]014_a_abc will run on host: ne2dhtm0111 "Scheduler started at:24/09/2019 01:00:16 --- 24/09/2019 01:00:16 Running: [1]004_a_abc 24/09/2019 01:00:16 Running test: [1]004_a_abc, Test id: 547, Test instance id: 764 Test: [1]004_a_abc, Id: 764, Execution status: Running Close last test 24/09/2019 02:23:33 Test complete: [1]004_a_Acceptance --- Test: [1]004_a_abc, Status: Running, Message: Connecting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312313 Test: [1]005_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=17632 Test: [1]006_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312314 Test: [1]007_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312315 Test: [1]008_a_abc, Status: Waiting, Message: Waiting..., Link:
[JIRA] (JENKINS-59499) Job timed out - Tests Aborted - Still tests are marked as passed
Title: Message Title Sanjeeth Nayak updated an issue Jenkins / JENKINS-59499 Job timed out - Tests Aborted - Still tests are marked as passed Change By: Sanjeeth Nayak Started by upstream project "DM_UAT_TestPipelines/Pipeline-DM_PDBTs_FAR- REG GER " build number 24originally caused by: Started by timerRunning as SYSTEMBuilding in workspace D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC[JOBFOLDER_ABC] $ D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC\HpToolsLauncher.exe -paramfile props24092019010010681.txt"Started..."Timeout is set to: 5000Run mode is set to: RUN_REMOTEStarting test set executionTest set name: Reg_ABC, Test set id: 5103Number of tests in set: 15Test 1: [1]004_a_abc will run on host: ne2dhtm0111Test 2: [1]005_a_abc will run on host: ne2dhtm0111Test 3: [1]006_a_abc will run on host: ne2dhtm0111Test 4: [1]007_a_abc will run on host: ne2dhtm0111Test 5: [1]008_a_abcItinerary will run on host: ne2dhtm0111Test 6: [1]009_a_abc will run on host: ne2dhtm0111Test 7: [1]013_a_abc will run on host: ne2dhtm0111Test 8: [1]017_a_abc will run on host: ne2dhtm0111Test 9: [1]016_a_abc will run on host: ne2dhtm0111Test 10: [1]018_a_abc will run on host: ne2dhtm0111Test 11: [1]019_a_abc will run on host: ne2dhtm0111Test 12: [1]010_a_abcr will run on host: ne2dhtm0111Test 13: [1]011_a_abc will run on host: ne2dhtm0111Test 14: [1]012_a_abc will run on host: ne2dhtm0111Test 15: [1]014_a_abc will run on host: ne2dhtm0111"Scheduler started at:24/09/2019 01:00:16---24/09/2019 01:00:16 Running: [1]004_a_abc24/09/2019 01:00:16 Running test: [1]004_a_abc, Test id: 547, Test instance id: 764Test: [1]004_a_abc, Id: 764, Execution status: RunningClose last test24/09/2019 02:23:33 Test complete: [1]004_a_Acceptance---Test: [1]004_a_abc, Status: Running, Message: Connecting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312313Test: [1]005_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=17632Test: [1]006_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312314Test: [1]007_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312315Test: [1]008_a_abc, Status: Waiting, Message: Waiting..., Link:
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59497 Git clone in pipeline ignoring reference repo 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.202115.1569286759000.3818.1569298200181%40Atlassian.JIRA.
[JIRA] (JENKINS-59499) Job timed out - Tests Aborted - Still tests are marked as passed
Title: Message Title Sanjeeth Nayak created an issue Jenkins / JENKINS-59499 Job timed out - Tests Aborted - Still tests are marked as passed Issue Type: Bug Assignee: Kevin Lee Attachments: image-2019-09-24-09-38-31-434.png Components: microfocus-da-plugin Created: 2019-09-24 04:08 Environment: plugin version 5.8 Labels: uft Priority: Critical Reporter: Sanjeeth Nayak Started by upstream project "DM_UAT_TestPipelines/Pipeline-DM_PDBTs_FAR-REG" build number 24 originally caused by: Started by timer Running as SYSTEM Building in workspace D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC [JOBFOLDER_ABC] $ D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC\HpToolsLauncher.exe -paramfile props24092019010010681.txt "Started..." Timeout is set to: 5000 Run mode is set to: RUN_REMOTE Starting test set execution Test set name: Reg_ABC, Test set id: 5103 Number of tests in set: 15 Test 1: [1]004_a_abc will run on host: ne2dhtm0111 Test 2: [1]005_a_abc will run on host: ne2dhtm0111 Test 3: [1]006_a_abc will run on host: ne2dhtm0111 Test 4: [1]007_a_abc will run on host: ne2dhtm0111 Test 5: [1]008_a_abcItinerary will run on host: ne2dhtm0111 Test 6: [1]009_a_abc will run on host:
[JIRA] (JENKINS-58813) Cannot send Email notification over office365 smtp with starttls has no effect
Title: Message Title Paul Morahan commented on JENKINS-58813 Re: Cannot send Email notification over office365 smtp with starttls has no effect I had exactly the same problem with the same stack trace, same Jenkins version, and same configuration steps, and it required two things to fix it: 1) upgrading the Mailer plugin from v1.24 to v1.28 2) the sysadmin email address MUST match the sending SMTP user. I tried making it another valid user on the same domain, but that didn't work. A lot of people online say that it just needs to be another valid account, but from what I could see, it didn't work until they matched. So now I have a 'noreply' user as the system admin's email address in Jenkins 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.201125.1565011288000.3811.1569297420299%40Atlassian.JIRA.
[JIRA] (JENKINS-59498) ItemsContent should be selected by default
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-59498 ItemsContent should be selected by default Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ 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.202117.1569295137000.3808.1569295200127%40Atlassian.JIRA.
[JIRA] (JENKINS-59498) ItemsContent should be selected by default
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-59498 ItemsContent should be selected by default Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-09-24 03:18 Environment: support-core:2.57 Priority: Major Reporter: Allan BURDAJEWICZ As part of JENKINS-33628, the ItemsContent was moved to a new component to be able to disable it. But as part of the change: the component was made disabled by default the component is loading allBuilds of all items that is potentially (surely) more expensive than the previous method We should improve the performance of that item so that it can be made enabled by default again. Add Comment
[JIRA] (JENKINS-59457) all pipeline job failed after upgrade security script plugin
Title: Message Title Dennis Tran closed an issue as Won't Fix My apologies, this issue not come from security script plugin, but from Pipeline Nodes and Processes Plugin, I did not update Pipeline Groovy Plugin before update it. Jenkins / JENKINS-59457 all pipeline job failed after upgrade security script plugin Change By: Dennis Tran Status: Open Closed Resolution: Won't Fix 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
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title
Vincenzo Melandri created an issue
Jenkins / JENKINS-59497
Git clone in pipeline ignoring reference repo
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-09-24 00:59
Environment:
Jenkins 2.176.1 Git Plugin 3.9.1
Labels:
pipeline git
Priority:
Major
Reporter:
Vincenzo Melandri
On a freestyle project, everything works fine, but on a declarative pipeline I cannot make the reference repository to work Example of how we check out in the pipeline:
checkout(
[
$class : 'GitSCM',
branches : [[ name: "${branch}" ]],
doGenerateSubmoduleConfigurations: false,
extensions : [
[$class : 'RelativeTargetDirectory',
relativeTargetDir: targetDir
],
[$class : 'CloneOption',
reference: '/somefolder/repo'
]
],
userRemoteConfigs : [[
url : ssh://blahblah/some.git,
credentialsId: ourCredentialsId
]]
]
)
and the output looks like this:
[Pipeline] git
Fetching changes from the remote Git
[JIRA] (JENKINS-59496) Render HTML in the Extended Choice Parameter Description field
Title: Message Title Ben Langton created an issue Jenkins / JENKINS-59496 Render HTML in the Extended Choice Parameter Description field Issue Type: Improvement Assignee: vimil Components: extended-choice-parameter-plugin Created: 2019-09-24 00:48 Environment: Jenkins 2.195 Extended Choice Parameter Plugin 0.78 Priority: Minor Reporter: Ben Langton Some Parameter types render HTML in the Description field. Please make the Extended Choice Parameter Description field render HTML. An example (for a different plugin) is here: https://issues.jenkins-ci.org/browse/JENKINS-45029 Add Comment
[JIRA] (JENKINS-59495) Render HTML in Parameter Description field in Node and Label Parameter Plugin
Title: Message Title Ben Langton created an issue Jenkins / JENKINS-59495 Render HTML in Parameter Description field in Node and Label Parameter Plugin Issue Type: Improvement Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 2019-09-24 00:45 Environment: Jenkins 2.195 Node and Label Parameter Plugin 1.7.2 Priority: Minor Reporter: Ben Langton Some parameter Description fields (ex. built-in string parameter, et al) render HTML that is entered in the Description field. This is handy for improving the look, and calling users' attention to important parameters, etc. Please make the Description field of the Node parameter render HTML. Add Comment
[JIRA] (JENKINS-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title Vincenzo Melandri commented on JENKINS-54612 Re: Reference repo not used for Git clones on Windows SSH agents I am seeing a similar problem, but with ubuntu agents. It works with freestyle, but on declarative pipeline it doesn't work. It does not even try to load the reference repo 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.195401.154214014.3792.1569285540210%40Atlassian.JIRA.
[JIRA] (JENKINS-59494) InterruptedException: sleep interrupted aborting job during shell command leaves process running
Title: Message Title
Christopher Head created an issue
Jenkins / JENKINS-59494
InterruptedException: sleep interrupted aborting job during shell command leaves process running
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-09-23 23:29
Environment:
Jenkins 2.176.3 OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10)
Priority:
Minor
Reporter:
Christopher Head
A freestyle job was in progress. The current step was invocation of a chunk of shell script. Within the shell script, a Python instance was running. The red X button to abort the build was pressed, probably twice. The job disappeared from the list of running jobs and its status changed to aborted. However, the Bash and Python processes were still running, Jenkins still had the output pipe connected to them, and the following appeared in the server log: {{INFO: (job name and number) aborted java.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:784) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:818) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:813) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:813) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:805) at hudson.util.ProcessTree.killAll(ProcessTree.java:172) at hudson.Proc$LocalProc.destroy(Proc.java:385) at hudson.Proc$LocalProc.join(Proc.java:358) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
[JIRA] (JENKINS-59454) Increase Advisor bundle generation delay to 30mins
Title: Message Title Owen Wood updated JENKINS-59454 Jenkins / JENKINS-59454 Increase Advisor bundle generation delay to 30mins Change By: Owen Wood 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.202047.1568943413000.3762.1569279060245%40Atlassian.JIRA.
[JIRA] (JENKINS-59454) Increase Advisor bundle generation delay to 30mins
Title: Message Title Owen Wood commented on JENKINS-59454 Re: Increase Advisor bundle generation delay to 30mins https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/31 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.202047.1568943413000.3760.1569279060222%40Atlassian.JIRA.
[JIRA] (JENKINS-59454) Increase Advisor bundle generation delay to 30mins
Title: Message Title Owen Wood started work on JENKINS-59454 Change By: Owen Wood 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.202047.1568943413000.3758.1569278580193%40Atlassian.JIRA.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Jeff Thompson commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 I'm able to reproduce Matt's simple test case on Unix and Windows. Hopefully it's a reasonably good representation of the other problems people are experiencing. Looks like the `allowSymlinkEscape` property isn't working the way it was intended. I'll see if I can figure something out to make it work better. It may take a while to get that change put together. 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.197816.1550852223000.3749.1569277980212%40Atlassian.JIRA.
[JIRA] (JENKINS-59282) Concurrent build support
Title: Message Title Robin Jansohn commented on JENKINS-59282 Re: Concurrent build support I'm not sure I can follow. You want to deploy the same web application (just different builds) concurrently on one Tomcat? Is that even possible? What about race conditions (build #1 being deployed after build #2)? 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.201815.1568034162000.3694.1569272160113%40Atlassian.JIRA.
[JIRA] (TEST-176) Crear Secuencia Ahorros Savings fidelity
Title: Message Title JULIAN JOSE CASTELLANOS URIBE started work on TEST-176 Change By: JULIAN JOSE CASTELLANOS URIBE 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.202108.156926916.3692.1569270900096%40Atlassian.JIRA.
[JIRA] (JENKINS-59493) Must include region in s3 bucket URL; support for GovCloud
Title: Message Title candrews created an issue Jenkins / JENKINS-59493 Must include region in s3 bucket URL; support for GovCloud Issue Type: Bug Assignee: Unassigned Components: artifact-manager-s3-plugin Created: 2019-09-23 20:25 Priority: Major Reporter: candrews artifact-manager-s3-plugin hardcodes the S3 endpoint URL as: https://%s.s3.amazonaws.com/ See https://github.com/jenkinsci/artifact-manager-s3-plugin/blob/cca5bc848c1acf59524ae66cf983d0fe6e9a9667/src/main/java/io/jenkins/plugins/artifact_manager_jclouds/s3/S3BlobStore.java#L164 The region must be included for US GovCloud support. It also must be included for all buckets made after September 30, 2020: https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/ The URL should be: https://%s.s3..amazonaws.com/ Add Comment
[JIRA] (JENKINS-28253) Archiving hangs on named pipes
Title: Message Title Marc Benstein commented on JENKINS-28253 Re: Archiving hangs on named pipes This is still happening with Jenkins ver 2.176.3 OpenJDK 1.8.0_201 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.162682.143090000.3689.1569270300221%40Atlassian.JIRA.
[JIRA] (TEST-176) Crear Secuencia Ahorros Savings fidelity
Title: Message Title JULIAN JOSE CASTELLANOS URIBE commented on TEST-176 Re: Crear Secuencia Ahorros Savings fidelity Se debe crear Secuencia creada Secuencia creada 2019092308530017 secuencia ambientes2019090909183017 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.202108.156926916.3687.1569270060056%40Atlassian.JIRA.
[JIRA] (TEST-176) Crear Secuencia Ahorros Savings fidelity
Title: Message Title JULIAN JOSE CASTELLANOS URIBE assigned an issue to JULIAN JOSE CASTELLANOS URIBE test / TEST-176 Crear Secuencia Ahorros Savings fidelity Change By: JULIAN JOSE CASTELLANOS URIBE Assignee: Oleg Nenashev JULIAN JOSE CASTELLANOS URIBE 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.202108.156926916.3686.156927151%40Atlassian.JIRA.
[JIRA] (JENKINS-20713) java.lang.IllegalArgumentException: Error parsing entity tag '1385073575'
Title: Message Title Tony Noble updated JENKINS-20713 Unable to reproduce and both codebases have moved on to such a degree that this appears to have been fixed, either directly or indirectly. Jenkins / JENKINS-20713 java.lang.IllegalArgumentException: Error parsing entity tag '1385073575' Change By: Tony Noble Status: Open Fixed but Unreleased Assignee: Gregory Boissinot Tony Noble Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-19854) URLTrigger plugin polling doesn't honor "Execute concurrent builds if necessary"
Title: Message Title Tony Noble commented on JENKINS-19854 Re: URLTrigger plugin polling doesn't honor "Execute concurrent builds if necessary" I'm not convinced this should be default behaviour - nothing prevents the job from running concurrently if triggered manually, but it was a specific design choice not to poll for changes while a run was in progress. Perhaps a better solution would be to add an option that allows polling while builds are progressing. This would default to unchecked to maintain existing 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.151374.1380730578000.3679.1569269580158%40Atlassian.JIRA.
[JIRA] (JENKINS-19854) URLTrigger plugin polling doesn't honor "Execute concurrent builds if necessary"
Title: Message Title Tony Noble assigned an issue to Tony Noble Jenkins / JENKINS-19854 URLTrigger plugin polling doesn't honor "Execute concurrent builds if necessary" Change By: Tony Noble Assignee: Gregory Boissinot Tony Noble 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.151374.1380730578000.3675.1569269340997%40Atlassian.JIRA.
[JIRA] (JENKINS-19854) URLTrigger plugin polling doesn't honor "Execute concurrent builds if necessary"
Title: Message Title Tony Noble updated an issue Jenkins / JENKINS-19854 URLTrigger plugin polling doesn't honor "Execute concurrent builds if necessary" Change By: Tony Noble Issue Type: Bug New Feature 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.151374.1380730578000.3670.1569269340880%40Atlassian.JIRA.
[JIRA] (JENKINS-38604) Filter class directories
Title: Message Title centic updated JENKINS-38604 See JENKINS-56918 for adjusting the inclusion pattern some more. Jenkins / JENKINS-38604 Filter class directories Change By: centic Status: Reopened Fixed but Unreleased 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
[JIRA] (TEST-176) Crear Secuencia Ahorros Savings fidelity
Title: Message Title JULIAN JOSE CASTELLANOS URIBE created an issue test / TEST-176 Crear Secuencia Ahorros Savings fidelity Issue Type: Task Assignee: Oleg Nenashev Components: foo2 Created: 2019-09-23 20:06 Priority: Minor Reporter: JULIAN JOSE CASTELLANOS URIBE 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
[JIRA] (JENKINS-15843) URL Trigger Plugin: Display change in build summary page.
Title: Message Title Tony Noble assigned an issue to Tony Noble Jenkins / JENKINS-15843 URL Trigger Plugin: Display change in build summary page. Change By: Tony Noble Assignee: Gregory Boissinot Tony Noble 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.146645.1353076412000.3654.1569268980300%40Atlassian.JIRA.
[JIRA] (JENKINS-56918) Groovy Class Files Not Copied Over To View Code Coverage
Title: Message Title centic edited a comment on JENKINS-56918 Re: Groovy Class Files Not Copied Over To View Code Coverage I adjusted the default to "**/*.java,**/*.groovy,**/*. gs kt,**/*.kts " for the next release, will probably be called 3.0.5 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.198593.1554476525000.3658.1569268980377%40Atlassian.JIRA.
[JIRA] (JENKINS-57078) Pipeline support for urltrigger (and xtrigger)
Title: Message Title Tony Noble updated JENKINS-57078 Jenkins / JENKINS-57078 Pipeline support for urltrigger (and xtrigger) Change By: Tony Noble Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/urltrigger-plugin/releases/tag/urltrigger-0.46 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.198821.1555498379000.3650.1569268740561%40Atlassian.JIRA.
[JIRA] (JENKINS-57078) Pipeline support for urltrigger (and xtrigger)
Title: Message Title Tony Noble updated JENKINS-57078 Pipeline compatibility released in 0.46 Jenkins / JENKINS-57078 Pipeline support for urltrigger (and xtrigger) Change By: Tony Noble Status: Open Fixed but Unreleased 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
[JIRA] (JENKINS-57078) Pipeline support for urltrigger (and xtrigger)
Title: Message Title Tony Noble assigned an issue to Tony Noble Jenkins / JENKINS-57078 Pipeline support for urltrigger (and xtrigger) Change By: Tony Noble Assignee: Gregory Boissinot Tony Noble 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.198821.1555498379000.3644.1569268680207%40Atlassian.JIRA.
[JIRA] (JENKINS-48087) URLTrigger Plugin causes stack trace on pipeline job
Title: Message Title Tony Noble updated JENKINS-48087 Pipeline compatibility changes released in version 0.46 Jenkins / JENKINS-48087 URLTrigger Plugin causes stack trace on pipeline job Change By: Tony Noble Status: Open Fixed but Unreleased Assignee: Gregory Boissinot Tony Noble Resolution: Fixed Released As: https://github.com/jenkinsci/urltrigger-plugin/releases/tag/urltrigger-0.46 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-48087) URLTrigger Plugin causes stack trace on pipeline job
Title: Message Title Tony Noble updated JENKINS-48087 Jenkins / JENKINS-48087 URLTrigger Plugin causes stack trace on pipeline job Change By: Tony Noble 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.186651.1510930655000.3626.1569268622338%40Atlassian.JIRA.
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-58779
LogRotator stops cleaning, if a build directory has been deleted externally
Change By:
Josh Soref
The deletion of a build/run in Jenkins is handled by the {{ delete() }} method. It throws an exception, when the build directory on disk has already beenremoved been removed and stops deleting the build. Unfortunately, the {{ hudson.tasks.LogRotator.perform(Job) }} method does not check for this exception and will STOP _STOP_ cleaning up, once even just one build throws that exception. This behaviour can be fixed in the following ways (a pull-request will be uploaded shortly): # The {{ Run.delete() }} method must still unlink the job, even if the build directory has been removed externally. # The log output of {{ Run.delete() }} must be made less verbose (it prints the ENTIRE folder content by default, into the job that is doing the cleanup) # The {{ LogRotator.perform() }} method must handle the exceptions being thrown by {{ delete() }} gracefully.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-45872) Unable to use UrlTriggerPlugin in Jenkinsfile
Title: Message Title Tony Noble updated JENKINS-45872 Pipeline compatibility changes release in version 0.46 Jenkins / JENKINS-45872 Unable to use UrlTriggerPlugin in Jenkinsfile Change By: Tony Noble Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/urltrigger-plugin/releases/tag/urltrigger-0.46 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title Josh Soref started work on JENKINS-58779 Change By: Josh Soref 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.201089.1564737737000.3598.1569268380428%40Atlassian.JIRA.
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title Josh Soref stopped work on JENKINS-58779 Change By: Josh Soref 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.201089.1564737737000.3600.1569268380453%40Atlassian.JIRA.
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title Josh Soref updated JENKINS-58779 Jenkins / JENKINS-58779 LogRotator stops cleaning, if a build directory has been deleted externally Change By: Josh Soref Status: Open Fixed but Unreleased 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.201089.1564737737000.3602.1569268380480%40Atlassian.JIRA.
[JIRA] (JENKINS-45872) Unable to use UrlTriggerPlugin in Jenkinsfile
Title: Message Title Tony Noble started work on JENKINS-45872 Change By: Tony Noble 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.184085.1501487303000.3594.1569268320259%40Atlassian.JIRA.
[JIRA] (JENKINS-45872) Unable to use UrlTriggerPlugin in Jenkinsfile
Title: Message Title Tony Noble updated JENKINS-45872 Jenkins / JENKINS-45872 Unable to use UrlTriggerPlugin in Jenkinsfile Change By: Tony Noble 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.184085.1501487303000.3596.1569268320283%40Atlassian.JIRA.
[JIRA] (JENKINS-45872) Unable to use UrlTriggerPlugin in Jenkinsfile
Title: Message Title Tony Noble assigned an issue to Tony Noble Jenkins / JENKINS-45872 Unable to use UrlTriggerPlugin in Jenkinsfile Change By: Tony Noble Assignee: Gregory Boissinot Tony Noble 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.184085.1501487303000.3592.1569268260203%40Atlassian.JIRA.
[JIRA] (JENKINS-30188) URL Trigger doesn't work and gives NullPointerException
Title: Message Title Tony Noble updated JENKINS-30188 Both Jenkins and URLTriggerPlugin have moved on considerably since this issue was reported. Could not reproduce and assuming no longer an issue Jenkins / JENKINS-30188 URL Trigger doesn't work and gives NullPointerException Change By: Tony Noble Status: Open Fixed but Unreleased Assignee: Gregory Boissinot Tony Noble Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59404) High CPU usage in MapperBase.importFromFile in Benchmark Plugin
Title: Message Title Daniel Mercier commented on JENKINS-59404 Re: High CPU usage in MapperBase.importFromFile in Benchmark Plugin Hi Artalus, Back to work. There is a good chance that the threads are kept alive because I forgot to close the InputStreamReader. The behavior would match your observations and it is a safe change to add anyway. All the Unit tests are passing so I am pushing the modification to version '1.0.11' . I apologize for the impact it had on your system. Let me know if you still observe the CPU overload. Thank you, Daniel 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.201962.1568710397000.3583.1569265260127%40Atlassian.JIRA.
[JIRA] (JENKINS-59114) Maven output is not colorized
Title: Message Title Eyal Goren commented on JENKINS-59114 Re: Maven output is not colorized OK, when I use the pipeline maven integration plugin it does work, this issue can be 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.201539.1566962562000.3580.1569264240154%40Atlassian.JIRA.
[JIRA] (JENKINS-59490) Automatically label Oracle Linux agents
Title: Message Title Mark Waite updated JENKINS-59490 Jenkins / JENKINS-59490 Automatically label Oracle Linux agents Change By: Mark Waite Status: Resolved Fixed but Unreleased 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.202105.1569252551000.3578.1569263400180%40Atlassian.JIRA.
[JIRA] (JENKINS-59490) Automatically label Oracle Linux agents
Title: Message Title Mark Waite updated JENKINS-59490 Will be released in platformlabeler plugin 3.5 Jenkins / JENKINS-59490 Automatically label Oracle Linux agents Change By: Mark Waite 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
[JIRA] (JENKINS-59490) Automatically label Oracle Linux agents
Title: Message Title Mark Waite updated JENKINS-59490 Jenkins / JENKINS-59490 Automatically label Oracle Linux agents Change By: Mark Waite 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.202105.1569252551000.3576.1569263340077%40Atlassian.JIRA.
[JIRA] (JENKINS-47339) Users with only Job/Configure shouldn't be able to replay jobs
Title: Message Title Jesse Glick assigned an issue to Andrew Bayer Jenkins / JENKINS-47339 Users with only Job/Configure shouldn't be able to replay jobs Change By: Jesse Glick 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.185771.1507524911000.3573.1569263280243%40Atlassian.JIRA.
[JIRA] (JENKINS-59488) Cannot change or remove Git client plugin 3.0.0-rc
Title: Message Title Mark Waite updated JENKINS-59488 Jenkins / JENKINS-59488 Cannot change or remove Git client plugin 3.0.0-rc Change By: Mark Waite Status: Fixed but Unreleased 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.202103.1569251774000.3570.1569262800196%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Andrii Petrenko commented on JENKINS-59161 Re: ERROR: 530 Authentication required 1.28 is not fixing this issue. what i did: upgrade jenkins to 2.196 upgrade plugin to 1.28 updated jenkins config with correct user name and password save changes restart jenkins run test job. result: https://pastebin.com/nDuQ76KW 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.201598.1567204978000.3558.1569262620365%40Atlassian.JIRA.
[JIRA] (JENKINS-15896) Spaces in the path when the configuration axis values have spaces
Title: Message Title Drew Horn commented on JENKINS-15896 Re: Spaces in the path when the configuration axis values have spaces This is still a bug, is the matrix configurations feature still supported? Using "sometext\ someadditionaltext" doesn't work. When saving in the UI (latest Jenkins version) it's broken up into two lines. 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.146698.1353576064000.3552.1569260280192%40Atlassian.JIRA.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title Peter Wein commented on JENKINS-44808 Re: Unable to print stacktrace on jenkins pipeline Which is where we have begun! But I did not understand correctly your way of solving it and if it is a regular pattern of jenkins or workaround for a bug. Is there one filed to the bug tracker team? 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.182865.1497172331000.3545.1569257940411%40Atlassian.JIRA.
[JIRA] (JENKINS-59491) SSH slaves plugin support for proxy/ bastion/ jumpbox
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-59491 Re: SSH slaves plugin support for proxy/ bastion/ jumpbox This is mostly an infrastructure thing, you can create a tunnel with ssh from the master to the agent through the bastion host, then you can use the local port of the tunnel to connect to the agent, see https://www.ssh.com/ssh/tunneling/example or https://www.tecmint.com/create-ssh-tunneling-port-forwarding-in-linux/ 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.202106.1569252947000.3491.1569257520133%40Atlassian.JIRA.
[JIRA] (JENKINS-59488) Cannot change or remove Git client plugin 3.0.0-rc
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59488 Cannot change or remove Git client plugin 3.0.0-rc 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.202103.1569251774000.3489.1569257280131%40Atlassian.JIRA.
[JIRA] (JENKINS-59488) Cannot change or remove Git client plugin 3.0.0-rc
Title: Message Title Mark Waite updated JENKINS-59488 Jenkins / JENKINS-59488 Cannot change or remove Git client plugin 3.0.0-rc Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate 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.202103.1569251774000.3487.1569257220208%40Atlassian.JIRA.
[JIRA] (JENKINS-59488) Cannot change or remove Git client plugin 3.0.0-rc
Title: Message Title Mark Waite commented on JENKINS-59488 Re: Cannot change or remove Git client plugin 3.0.0-rc Refer to JENKINS-59336 for the alternatives. If you are critically dependent on the features that are in git client plugin 3.0.0-rc and git plugin 4.0.0-rc then you'll need to install the pre-release git plugin 4.0.0-beta11 and git client plugin 3.0.0-beta11. Most users are probably not critically dependent on the features that are in git client plugin 3.0.0-rc and git plugin 4.0.0-rc. In that case, dismiss the warnings about the missing field exception and continue using Jenkins. 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.202103.1569251774000.3485.1569257160141%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Matthew Brunton commented on JENKINS-59484 Re: EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory I cleaned the workspaces and then hit 'build' 4 times quickly. Below are the resulting folders: drwxr-xr-x 3 jenkins jenkins 4096 Sep 23 16:29 testMultibranch_testStream@3 drwxr-xr-x 2 jenkins jenkins 4096 Sep 23 16:29 testMultibranch_testStream@3@tmp drwxr-xr-x 3 jenkins jenkins 4096 Sep 23 16:29 testMultibranch_testStream@4 drwxr-xr-x 2 jenkins jenkins 4096 Sep 23 16:29 testMultibranch_testStream@4@tmp -rw-r--r-- 1 jenkins jenkins 54 Sep 23 16:29 workspaces.txt The two builds that should have used testMultibranch_testStream and testMultibranch_testStream@2 failed with an error: ERROR: P4: Task Exception: hudson.AbortException: P4JAVA: Error(s): Path '/var/jenkins_home/workspace/testMultibranch_testStream/test/...' is not under client's root '/var/jenkins_home/workspace/testMultibranch_testStream%403/test'. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59492) False positive CPS mismatch warning when calling a method pointer
Title: Message Title
Roman Donchenko created an issue
Jenkins / JENKINS-59492
False positive CPS mismatch warning when calling a method pointer
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2019-09-23 16:31
Environment:
Jenkins: 2.176.3 Pipeline: Groovy: 2.74
Priority:
Minor
Reporter:
Roman Donchenko
Run this pipeline:
def hello() {
echo 'hello'
}
(this.).call()
The output is as follows:
[Pipeline] Start of Pipeline
expected to call org.kohsuke.groovy.sandbox.impl.SandboxedMethodClosure.call but wound up catching WorkflowScript.hello; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/
[Pipeline] echo
hello
[Pipeline] End of Pipeline
Finished: SUCCESS
As evidenced by the "hello" output, the hello method runs normally, so the warning is a false positive.
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title
Marat Radchenko updated an issue
Jenkins / JENKINS-59152
Jenkins fails to properly abort "bat" step
Change By:
Marat Radchenko
# Windows# Jenkins 2.176.1# Create pipeline:{code}node() { bat "ping 127.0.0.1 -n 10"}{code}# Run pipeline# Abort pipeline# View build logExpected: pipeline aborts fast and without any issuesActual ( 66% reproducibility is less than 100% ):# It takes pipeline 20s to abort# Build log contains "Click here to forcibly terminate running steps" and "After 20s process did not stop", indicating that Jenkins has issues with stopping the pipeline# "Click here to forcibly terminate running steps" link is still visible even after the build has finished # Sometimes ping processes are NOT terminated even when build has aborted. Issue analysis:# There is a race condition between 2 minute timer in {{hudson.util.ProcessTree.WindowsOSProcess#killSoftly}} introduced for JENKINS-17116 by [PR#3414|https://github.com/jenkinsci/jenkins/pull/3414] and 20s timer in {{org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.Execution#stop}}. It is possible for {{DurableTaskStep}} to pretend that step was cancelled while it fact process is still running. Because of this race condition, it is possible to trick Jenkins into thinking that build has finished while if fact there are still processes running in workspace and potentially locking files there (this happens to us in practice).# {{org.jvnet.winp.WinProcess#sendCtrlC}} that is used in {{hudson.util.ProcessTree.WindowsOSProcess#killSoftly}} is NOT a proper way to terminate processes. Many apps do not interpret CTRL+C as a shutdown signal. ({{cmd.exe}} being the most important one here, because running {{bat}} in pipeline involved TWO {{cmd.exe}} - one running {{jenkins-wrapper.bat}} and second running {{jenkins-main.bat}}. Why you're not using [TerminateProcess function|https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-terminateprocess] from WinAPI?# There's a race condition between gathering of process list in {{hudson.util.ProcessTree.Windows#Windows}} constructor and killing of the processes, during which build can produce new processes that will not be attempted to be killed.# Usage of {{JENKINS_NODE_COOKIE}} to find what processes to kill is unreliable because 1) processes are free to alter their environment 2) [CreateProcessA|https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createprocessa] allows to pass custom environment variables 3) It has unpredictable order 4) It doesn't match Jenkins behavior on Linux
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Peter Wein commented on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Vassilena Treneva, thanks for the detailed answer. Yes I have an exception and for example in a code like this: ~~
try {
new CommonTools().copyArtifacts(
env['JOB_NAME'],
env.ARCHIVE_INPUT_FOLDER + '/JenkinsServerStack/',
env.JENKINS_SHARE)
}
catch (Exception eDF) {
utility.debugPrint(
env, name, 'Exception ' + eDF.getClass() + ' : CopyArtifacts somehow failed! ',
'lastSuccessful()')
eDF.printStackTrace()
}
but it does not print the StackTrace. It well gets the class by getClass:
02:55:40 [PolyspaceBugFinder:runSteps]: Exception e is thrown:hudson.AbortException: CopyArtifacts somehow failed!
lastSuccessful()
So no printStackTrace is printed. What am I doing wrong here?
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
[JIRA] (JENKINS-59488) Cannot change or remove Git client plugin 3.0.0-rc
Title: Message Title John McLean commented on JENKINS-59488 Re: Cannot change or remove Git client plugin 3.0.0-rc As a result of the downgrade, I am receiving errors in all builds for Unreadable Data: hudson.model.FreeStyleBuild CannotResolveClassException: hudson.plugins.git.util.BuildDetails, MissingFieldException: No field 'showEntireCommitSummaryInChanges' found in class 'hudson.plugins.git.GitChangeLogParser' 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.202103.1569251774000.3461.1569254520132%40Atlassian.JIRA.
[JIRA] (JENKINS-58337) Promotion Console Log
Title: Message Title Filipe Roque commented on JENKINS-58337 Re: Promotion Console Log I wasted some time with this bug. From what I can tell, the bug was introduced with commit 0a9e67654a0f072601fb3a24d420c3c09ebfd843, when upgrading jenkins.version property from 2.60.3 to 2.138.4. It happens because of commit ba33bd67cdaef87aba8a4e95dca8dcf108a7d73f , in 2.138.2, which added an interface StaplerProxy to class Run. This interface defines a method Object getTarget() with an implementation in class Run. The Promotion class, which derives from Run, also has a method getTarget but with return type AbstractBuild, so a synthetic method, with return type Object, is created by the compiler which invokes AbstractBuild getTarget(). javap -v ./promoted-builds-2.138.2/WEB-INF/lib/promoted-builds/hudson/plugins/promoted_builds/Promotion.class public hudson.model.AbstractBuild getRootBuild(); descriptor: ()Lhudson/model/AbstractBuild; flags: (0x0001) ACC_PUBLIC Code: stack=1, locals=1, args_size=1 0: aload_0 1: invokevirtual #9 // Method getTarget:()Lhudson/model/AbstractBuild; 4: invokevirtual #10 // Method hudson/model/AbstractBuild.getRootBuild:()Lhudson/model/AbstractBuild; 7: areturn LineNumberTable: line 93: 0 LocalVariableTable: Start Length Slot Name Signature 0 8 0 this Lhudson/plugins/promoted_builds/Promotion; Signature: #185 // ()Lhudson/model/AbstractBuild<**>; Renaming AbstractBuild getTarget() to AbstractBuild getTarget2() fixes the bug, but I have no idea of its impacts because of the @Exported annotation. Note: the new Object getTarget() method in Run as an annotation @Restricted(NoExternalUse.class) but I don't understand its meaning. Add Comment This message
[JIRA] (JENKINS-59488) Cannot change or remove Git client plugin 3.0.0-rc
Title: Message Title John McLean updated an issue Jenkins / JENKINS-59488 Cannot change or remove Git client plugin 3.0.0-rc Change By: John McLean Priority: Critical Minor 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.202103.1569251774000.3444.1569254220282%40Atlassian.JIRA.
[JIRA] (JENKINS-59488) Cannot change or remove Git client plugin 3.0.0-rc
Title: Message Title John McLean commented on JENKINS-59488 Re: Cannot change or remove Git client plugin 3.0.0-rc Reducing to minor bug since there is a workaround. 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.202103.1569251774000.3446.1569254220305%40Atlassian.JIRA.
[JIRA] (JENKINS-59488) Cannot change or remove Git client plugin 3.0.0-rc
Title: Message Title John McLean commented on JENKINS-59488 Re: Cannot change or remove Git client plugin 3.0.0-rc I have worked around this by manually uploading 2.8.6 onto the server. 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.202103.1569251774000.3442.1569254220258%40Atlassian.JIRA.
[JIRA] (JENKINS-47584) Result screen not refreshing with error "Cannot read property 'self' of undefined"
Title: Message Title Andrei Muresianu commented on JENKINS-47584 Re: Result screen not refreshing with error "Cannot read property 'self' of undefined" Could we please reopen 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.186054.1508756187000.3429.1569253200237%40Atlassian.JIRA.
[JIRA] (JENKINS-58189) Submitting user input causes unhandledPromiseRejection in Blue Ocean
Title: Message Title Andrei Muresianu updated an issue Jenkins / JENKINS-58189 Submitting user input causes unhandledPromiseRejection in Blue Ocean Change By: Andrei Muresianu Priority: Minor Critical 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.200243.1561475453000.3427.1569253080118%40Atlassian.JIRA.
[JIRA] (JENKINS-59491) SSH slaves plugin support for proxy/ bastion/ jumpbox
Title: Message Title Andrei Muresianu created an issue Jenkins / JENKINS-59491 SSH slaves plugin support for proxy/ bastion/ jumpbox Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2019-09-23 15:35 Priority: Minor Reporter: Andrei Muresianu I have a Jenkins Master running on serverA in vpcA. I have a server serverB that leaves in vpcB that I would like to register as a Jenkins slave. I have a jumpbox serverC that is accessible from anywhere. I can connect from serverA to serverB if I proxy through serverC first. I can connect with no problems with an ssh config file on the master similar to: Host slave User andrei ProxyCommand ssh andrei@gateway nc %h %p I would like to be able to connect serverB as a slave of Jenkins (serverA). I looked into launching the agent via execution of command on the slave, but that requires the agent.jar to be placed there - is there another way of doing this? Surely if connection from the master to the slave is possible, this could be done automatically, perhaps as part of this plugin?
[JIRA] (JENKINS-59490) Automatically label Oracle Linux agents
Title: Message Title Mark Waite started work on JENKINS-59490 Change By: Mark Waite 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.202105.1569252551000.3424.1569252780070%40Atlassian.JIRA.
[JIRA] (JENKINS-59490) Automatically label Oracle Linux agents
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59490 Automatically label Oracle Linux agents Change By: Mark Waite Labels: hacktoberfest newbie-friendly 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.202105.1569252551000.3418.1569252600507%40Atlassian.JIRA.
[JIRA] (JENKINS-59490) Automatically label Oracle Linux agents
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-59490 Automatically label Oracle Linux agents Issue Type: Improvement Assignee: Unassigned Components: platformlabeler-plugin Created: 2019-09-23 15:29 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Mark Waite Automatically label Red Hat Enterprise Linux agents with an easy to read label that includes the architecture, operating system name, and operating system version. Include a sample /etc/os-release file in the test suite and include the output of lsb_release -a in the test suite so that others can confirm the label operates as expected without installing their own copy of Red Hat Enterprise Linux. Add Comment
[JIRA] (JENKINS-59490) Automatically label Oracle Linux agents
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59490
Automatically label Oracle Linux agents
Change By:
Mark Waite
Automatically label Red Hat Enterprise Oracle Linux agents with an easy to read label that includes the architecture, operating system name, and operating system version. Include a sample /etc/os-release file in the test suite and include the output of {{lsb_release -a}} in the test suite so that others can confirm the label operates as expected without installing their own copy of Red Hat Enterprise Oracle Linux.
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-59489) Error in test configuration by sending test email
Title: Message Title la nerfy created an issue Jenkins / JENKINS-59489 Error in test configuration by sending test email Issue Type: Bug Assignee: la nerfy Components: email-ext-plugin, emailext-template-plugin Created: 2019-09-23 15:23 Environment: Windows Server 2016, Jenkins ver 2.194, Priority: Major Reporter: la nerfy After putting the smtp server (sendgrid) ,smtp authentication and port 25 then test the configuration by sending the test email. I get the error below.. I tried different configuration combinations but still get the same error. The smtp server is working when used by other servers. Test configuration ERROR A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at
[JIRA] (JENKINS-59488) Cannot change or remove Git client plugin 3.0.0-rc
Title: Message Title John McLean created an issue Jenkins / JENKINS-59488 Cannot change or remove Git client plugin 3.0.0-rc Issue Type: Bug Assignee: Mark Waite Attachments: git-client-bug.PNG Components: git-client-plugin Created: 2019-09-23 15:16 Environment: Jenkins ver. 2.176.3 Priority: Critical Reporter: John McLean Vulnerability in Git client plugin 3.0.0-rc cannot be resolved as no other versions show available. This is likely due to version 3.0.0-rc being automatically installed when the Jenkins server was initially deployed. Add Comment
[JIRA] (JENKINS-59487) Startup Trigger doesnt execute jobs in master
Title: Message Title
blastik . created an issue
Jenkins / JENKINS-59487
Startup Trigger doesnt execute jobs in master
Issue Type:
Bug
Assignee:
Emory Penney
Components:
startup-trigger-plugin
Created:
2019-09-23 14:54
Environment:
docker jenkins/jenkins:2.194-slim startup-trigger-plugin:2.9.3 configuration-as-code:1.30 configuration-as-code-support:1.18 saml:1.1.2 role-strategy:2.13 permissive-script-security:0.5 git:3.12.1 github:1.29.4 github-pullrequest:0.2.6 job-dsl:1.74 workflow-aggregator:2.6 uno-choice:2.1 groovy:2.2 ec2:1.45
Priority:
Critical
Reporter:
blastik .
similar to JENKINS-50681 i have this job groovy
job('Startup') {
triggers {
hudsonStartupTrigger {
// By default, the build is triggered when Jenkins instance starts.
label('')
// Give the quiet period before scheduling the job.
quietPeriod('0')
runOnChoice('ON_CONNECT')
// Pass node name as job parameter.
nodeParameterName('')
}
}
steps {
systemGroovyScriptFile('/jobs/startup_script.groovy')
}
}
my master has 1 executor. the job triggers but remains on hold showing: (pending—‘Jenkins’ is reserved for jobs with matching label _expression_) I've tried to set a label but didnt help
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Same here, been running with SymlinkEscape=true for quite a while. 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.197816.1550852223000.3402.1569249360313%40Atlassian.JIRA.
[JIRA] (JENKINS-59486) Restart Jenkins when installation is complete and no jobs are running should preload the restarting jenkins image
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59486 Restart Jenkins when installation is complete and no jobs are running should preload the restarting jenkins image Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-09-23 14:29 Priority: Minor Reporter: Josh Soref Steps: visit jenkins/pluginManager/installed select a plugin to update click the install button check the Restart Jenkins when installation is complete and no jobs are running box Actual results: Installing Plugins/Upgrades Preparation Checking internet connectivity Checking update center connectivity Success Mailer
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth commented on JENKINS-59484 Re: EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Hi Matthew Brunton - Please check on the Jenkins slave and master if an '@' executor number or '@script' directory is being created under 'workspaces'. I'm interested to know if '@' or a different delimiter is being used. 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.202099.1569244102000.3381.1569249000240%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-59484 EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Change By: Karl Wirth Assignee: Karl Wirth 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.202099.1569244102000.3350.1569248520199%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59484 EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Change By: Karl Wirth Labels: P4_SUPPORT 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.202099.1569244102000.3352.1569248520228%40Atlassian.JIRA.
[JIRA] (JENKINS-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title
Oliver Mueller edited a comment on JENKINS-37588
Re: Multibranch pipeline does not allow quiet time or throttle
We are using Jenkins 2.195, Multibranch 2.21 and Declarative version 1.3.9 and .Option quietPeriod seems to be accepted, but it does not NOT seem to work .We are using a declarative multibranch pipeline with these options : {code:java} pipeline { agent any options { quietPeriod 1200 timeout(time: 4, unit: 'HOURS') disableConcurrentBuilds()} ... {code}The pipeline will get executed immediately.
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.173704.1471877153000.3310.1569248460925%40Atlassian.JIRA.
[JIRA] (JENKINS-59485) Trust level "Contributors" is ambiguous, should be called "Collaborators" instead
Title: Message Title Fred G created an issue Jenkins / JENKINS-59485 Trust level "Contributors" is ambiguous, should be called "Collaborators" instead Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-09-23 14:08 Priority: Minor Reporter: Fred G The "Discover pull requests from forks" allows to set a trust level. The trust level "Contributors" is ambiguous, since it does not refer to all contributors, but actually only to collaborators (in the GitHub definition of collaborators => https://developer.github.com/v3/repos/collaborators/ ). Since GitHub collaborators have to be explicitly added to a repo, this is usually a smaller group of people. This ambiguity is somewhat explained in the info/help text (when you click on the icon left of the trust drop-down menu), but I'd recommend to make it clearer by renaming the entry in the drop-down to "Collaborator" or even "GitHub Collaborator". I don't see a value in using a different term for it. Actual examples of misunderstanding: https://bugs.eclipse.org/bugs/show_bug.cgi?id=549571 https://bugs.eclipse.org/bugs/show_bug.cgi?id=550512#c12 Add Comment
[JIRA] (JENKINS-42655) Active choices parameters not rendering after dsl generation
Title: Message Title Prashanth Boodithi commented on JENKINS-42655 Re: Active choices parameters not rendering after dsl generation I see the same issue, any workaround for 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.179605.1489140109000.3295.1569246840449%40Atlassian.JIRA.
[JIRA] (JENKINS-59482) Improve UX for selecting user-scoped credentials
Title: Message Title
Vít Zikmund edited a comment on JENKINS-59482
Re: Improve UX for selecting user-scoped credentials
Thanks for your consideration {color:#1d1c1d}FYI:{color}{color:#1d1c1d} [~jvz] , as author of the latest change you might want to put in your 2¢.{color}{color:#1d1c1d} [~stephenconnolly] (I know you’re very busy) since you have a vision for how user credentials work you may be interested too . {color}{color:#1d1c1d}Apologies for not explaining why I was tagging you originally in this comment.{color}
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.202097.1569241421000.3246.1569246060130%40Atlassian.JIRA.
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title Marat Radchenko updated an issue Jenkins / JENKINS-59152 Jenkins fails to properly abort "bat" step Change By: Marat Radchenko Component/s: workflow-durable-task-step-plugin Component/s: core Component/s: durable-task-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.201589.1567181048000.3244.1569245700063%40Atlassian.JIRA.
[JIRA] (JENKINS-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title
Oliver Mueller commented on JENKINS-37588
Re: Multibranch pipeline does not allow quiet time or throttle
We are using Declarative version 1.3.9 and quietPeriod does not seem to work:
options {
quietPeriod 1200
timeout(time: 4, unit: 'HOURS')
disableConcurrentBuilds()
}
The pipeline will get executed immediately.
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.173704.1471877153000.3204.1569245640995%40Atlassian.JIRA.
[JIRA] (JENKINS-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title
Oliver Mueller updated an issue
Jenkins / JENKINS-37588
Multibranch pipeline does not allow quiet time or throttle
Change By:
Oliver Mueller
Comment:
A very important hint is, that the quietPeriod option has to be written *WITHOUT* braces:so instead of writing:{code:java}quietPeriod(600){code}you need to write:{code:java}quietPeriod 600{code}jenkins will not give you a notice, warning or anything alike when using it with braces.
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.173704.1471877153000.3157.156921486%40Atlassian.JIRA.
[JIRA] (JENKINS-59292) org.apache.commons.jelly.JellyTagException looking at Parasoft results
Title: Message Title Alexander Mai edited a comment on JENKINS-59292 Re: org.apache.commons.jelly.JellyTagException looking at Parasoft results Yes, Parasoft Finding 10.4.2 [|http://rkqs.msg-gillardon.de:8080/pluginManager/plugin/parasoft-findings/thirdPartyLicenses] 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.201836.1568099107000.3154.1569244200208%40Atlassian.JIRA.
[JIRA] (JENKINS-59359) Reduce test time under 20 minutes for WarningsNextGenerationPluginTest (46 min)
Title: Message Title Ulli Hafner commented on JENKINS-59359 Re: Reduce test time under 20 minutes for WarningsNextGenerationPluginTest (46 min) Yes, I will do. I already have a lot of changes in my fork from the last testing course. I will create a PR ASAP. 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.201910.1568378623000.3152.1569244200186%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title
Matthew Brunton created an issue
Jenkins / JENKINS-59484
EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-09-23 13:08
Environment:
Docker image jenkins/jenkins:2.176.3 in a docker network with a Perforce instance (https://github.com/p4paul/helix-docker) using p4-plugin 1.10.3
Priority:
Blocker
Reporter:
Matthew Brunton
When using the p4 plugin to checkout to a subdirectory, EXECUTOR_NUMBER is always expanded in the Perforce workspace name to be '0'. This messes up concurrent builds that rely on the Perforce workspace root since each subsequent build uses the same workspace and overwrites the root directory. When not checking out to a subdirectory, the executor number is expanded correctly. It still doesn't match up with the result of 'echo ${EXECUTOR_NUMBER}', but at least multiple builds aren't clashing workspaces with each other. This occurs both when using 'checkoutToSubdirectory' under options as well as manually specifying a dir() step with 'checkout scm' under it. To reproduce, I used the jenkins/jenkins:2.176.3 docker image of Jenkins (I was able to reproduce it on 2.150.3, 2.164.3, and 2.176.3) with p4-plugin 1.10.3 as well as a clean docker instance of Perforce (https://github.com/p4paul/helix-docker). I created a stream depot with a dummy stream to use for tests. The workspace name format is still the default jenkins-${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER} I have been able to reproduce it by starting several concurrent builds on the same node (I tried both the master node and a slave node) and the following Jenkinsfiles:
[JIRA] (JENKINS-47533) Document the Gitea plugin
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-47533 Document the Gitea plugin Change By: Mark Waite Summary: Usage document not available Document the Gitea 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.185991.1508423991000.3145.1569244020362%40Atlassian.JIRA.
