[JIRA] (JENKINS-59992) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title Wadeck Follonier updated JENKINS-59992 Symptoms resolved in 2.223 Jenkins / JENKINS-59992 "Jenkins.instance is missing" error when restarting Jenkins Change By: Wadeck Follonier Status: In Review Closed Resolution: Fixed Released As: 2.223 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to
[JIRA] (JENKINS-40129) Extend GitChangeSet to get the repository name
Title: Message Title Hans-Eric Jönsson edited a comment on JENKINS-40129 Re: Extend GitChangeSet to get the repository name This feature would be really appreciated as we would like to trigger certain actions when a specific file is changed, but since we are also using a shared-pipeline, things become a bit wonky to figure out if the change in question is in the shared-pipeline or in the repository in question, ** because the file-name exists in both repos. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176775.1480530768000.14469.1587450722927%40Atlassian.JIRA.
[JIRA] (JENKINS-40129) Extend GitChangeSet to get the repository name
Title: Message Title Hans-Eric Jönsson commented on JENKINS-40129 Re: Extend GitChangeSet to get the repository name This feature would be really appreciated as we would like to trigger certain actions when a specific file is changed, but since we are also using a shared-pipeline, things become a bit wonky to figure out if the change in question is in the shared-pipeline or in the repository in question, **because the file-name exists in both repos. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176775.1480530768000.14456.1587450721508%40Atlassian.JIRA.
[JIRA] (JENKINS-61584) Method java.util.regex.Matcher find is no longer whitelisted
Title: Message Title Reinhold Füreder commented on JENKINS-61584 Re: Method java.util.regex.Matcher find is no longer whitelisted Thanks Devin Nusbaum! (Also thanks for taking a closer look and re-adding three more accidentally lost signatures...) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205281.158462305.14442.1587449760189%40Atlassian.JIRA.
[JIRA] (JENKINS-39787) bitbucket branch source plugin creates duplicate build notifications
Title: Message Title James Selvakumar commented on JENKINS-39787 Re: bitbucket branch source plugin creates duplicate build notifications Is this fixed? Is there any work around for this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176376.1479328939000.14439.1587447240826%40Atlassian.JIRA.
[JIRA] (JENKINS-61982) jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61982
jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Change By:
Mark Waite
The pipeline build step plugin online documentation inside Jenkins is much more detailed in its description of the {{wait}} argument. The description of the wait argument in the pipeline syntax includes a full page of details in addition to the description of the {{wait}} argument.It is not clear to me why that page of details is included for the online help of the {{wait}} argument. The detail seems almost unrelated, though possibly it is describing some conditions which might be applied to the wait argument?The help page for the {{wait}} parameter of the pipeline step {{build}} inside a running Jenkins server looks like this: !screencapture-mark-pc2-markwaite-net-8080-pipeline-syntax-2020-04-20-22_12_40-edit.png|thumbnail! When viewed on [jenkins.io|https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job], the section for parameter {{wait}} is + empty + of any description.I assume the reason it is empty of https://jenkins.io/ is because the help for the wait parameter is written using groovy rather than html. Refer to the [source code|https://github.com/jenkinsci/pipeline-build-step-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-wait.groovy] to see the implementation.Documentation should more frequently remind users that their Jenkins server is the best reference for pipeline documentation. The documentation that is generated inside their Jenkins server reflects *exactly* the versions they are running.
Add Comment
[JIRA] (JENKINS-61982) jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61982
jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Change By:
Mark Waite
The pipeline build step plugin online documentation inside Jenkins is much more detailed in its description of the {{wait}} argument. The description of the wait argument in the pipeline syntax includes a full page of details in addition to the description of the {{wait}} argument.It is not clear to me why that page of details is included for the online help of the {{wait}} argument. The detail seems almost unrelated, though possibly it is describing some conditions which might be applied to the wait argument?The help page for the {{wait}} parameter of the pipeline step {{build}} inside a running Jenkins server looks like this: !screencapture-mark-pc2-markwaite-net-8080-pipeline-syntax-2020-04-20-22_12_40-edit.png|thumbnail! When viewed on [jenkins.io|https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job], the section for parameter {{wait}} is +empty+ of any description.I assume the reason it is empty of on https://jenkins.io/ is because the help for the wait parameter is written using groovy rather than html. Refer to the [source code|https://github.com/jenkinsci/pipeline-build-step-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-wait.groovy] to see the implementation.Documentation should more frequently remind users that their Jenkins server is the best reference for pipeline documentation. The documentation that is generated inside their Jenkins server reflects *exactly* the versions they are running.
Add Comment
[JIRA] (JENKINS-61982) jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61982 jenkins..io docs for 'waite' parameter of pipeline 'build' step are incomplete Issue Type: Bug Assignee: Unassigned Attachments: screencapture-mark-pc2-markwaite-net-8080-pipeline-syntax-2020-04-20-22_12_40-edit.png Components: pipeline-build-step-plugin Created: 2020-04-21 04:25 Environment: Jenkins 2.222.1. pipeline build step plugin 2.12 Priority: Minor Reporter: Mark Waite The pipeline build step plugin online documentation inside Jenkins is much more detailed in its description of the wait argument. The description of the wait argument in the pipeline syntax includes a full page of details in addition to the description of the wait argument. It is not clear to me why that page of details is included for the online help of the wait argument. The detail seems almost unrelated, though possibly it is describing some conditions which might be applied to the wait argument? The help page for the wait parameter of the pipeline step build inside a running Jenkins server looks like this:When viewed on jenkins.io, the section for parameter wait is empty of any description. I assume the reason it is empty of https://jenkins.io/ is because the help for the wait parameter is written using groovy rather than html. Refer to the source code to see the implementation. Documentation should more frequently remind users that their Jenkins server is the best reference for pipeline documentation. The documentation that is generated inside their Jenkins server reflects exactly the versions they are running
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K commented on JENKINS-61981 Re: unable to delete workspace after attaching a file to confluence through confluence publisher Request to verify and merge the code fix to master. https://github.com/jenkinsci/confluence-publisher-plugin/pull/16 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205871.1587432755000.14428.1587442740168%40Atlassian.JIRA.
[JIRA] (JENKINS-61939) Duplicate warnings not eliminated/combined
Title: Message Title Timothy Brackett edited a comment on JENKINS-61939 Re: Duplicate warnings not eliminated/combined Missing include keyword and unused function duplicated in this small [example| [ https://github.com/bracketttc/jenkins-errors] |https://github.com/bracketttc/example] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205819.1587074798000.14426.1587442500119%40Atlassian.JIRA.
[JIRA] (JENKINS-61939) Duplicate warnings not eliminated/combined
Title: Message Title Timothy Brackett edited a comment on JENKINS-61939 Re: Duplicate warnings not eliminated/combined Missing include keyword and unused function duplicated in this small [example|[https://github.com/bracketttc/ example jenkins-errors ] ] |https://github . com/bracketttc/example] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205819.1587074798000.14424.1587442440122%40Atlassian.JIRA.
[JIRA] (JENKINS-61939) Duplicate warnings not eliminated/combined
Title: Message Title Timothy Brackett commented on JENKINS-61939 Re: Duplicate warnings not eliminated/combined Missing include keyword and unused function duplicated in this small [example|https://github.com/bracketttc/example]. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205819.1587074798000.14422.1587442320120%40Atlassian.JIRA.
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205871.1587432755000.14420.1587441900202%40Atlassian.JIRA.
[JIRA] (JENKINS-53442) Compatibility with Configuration As Code Plugin
Title: Message Title Jon Tancer commented on JENKINS-53442 Re: Compatibility with Configuration As Code Plugin There is currently an open PR to add JCasC compatibility to the Thin backup plugin. https://github.com/jenkinsci/thin-backup-plugin/pull/18 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193812.1536240543000.14418.1587441720153%40Atlassian.JIRA.
[JIRA] (JENKINS-22153) Add attachment comment for confluence publisher
Title: Message Title Tejo K commented on JENKINS-22153 Re: Add attachment comment for confluence publisher Joe Hansche, can you please check on this as well. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153932.1394642065000.14415.1587441540229%40Atlassian.JIRA.
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61850 TFS pull request verification build uses wrong branch Change By: Mark Waite Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205713.1586436018000.14405.1587436500238%40Atlassian.JIRA.
[JIRA] (JENKINS-61922) Invoking another pipeline job from pipeline throws ClosedChannelException at end.
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Closing as cannot reproduce. If you can provide instructions that others can use to consistently duplicate the problem, please provide them and reopen the issue. Jenkins / JENKINS-61922 Invoking another pipeline job from pipeline throws ClosedChannelException at end. Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-60903) Include information about number of CPUs and memory in the node view
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60903 Include information about number of CPUs and memory in the node view Change By: Mark Waite A node property can display additional information in a dedicated jelly.We could use this to display additional information like number of CPUs and installed memory for the machines which are fetched when getting the OS information. We could also include that additional information in the automatically generated labels for the agent. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204294.1580302479000.14400.1587436260222%40Atlassian.JIRA.
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K Hello All, Hope you guys are doing great. Can you please help me on the following issue with a This is a freestyle project, that runs in windows Jenkins server. My windows Jenkins workspace folder has full access(read/write/modify etc). When I first run the build, I am able to push & attach the file successfully to confluence from jenkins. The file(say *Project3XOutput_202004201748*) is generated in the build\resources folder. My output file has timestamp embedded in the name. But from the next build onwards, I encounter an issue with the deleting or clearing the workspace because of the file *Project3XOutput_202004201748*. I couldnt delete the file *Project3XOutput_202004201748* from the *Jenkins server machine* itself. The file automatically re-appears after refresh even when I made a shift+delete from the Jenkins machine.The only way I can resolve this is to stop the Jenkins server and restart the Jenkins server. After a restart, the first build ran was working fine, but subsequent builds result in the same cleaning issue of the workspace.I see the filename as 0B in the workspace.!image-2020-04-20-20-56-58-876.png!-- Unable to delete the workspace is shown when I run the clean build gradle command. [Project3X] $ cmd /c call C:\WINDOWS\TEMP\jenkins4496026035965746988.batC:\Program Files (x86)\Jenkins\workspace\Project3X>exit 0 [Gradle] - Launching build. [Project3X] $ cmd.exe /C "gradle.bat clean test && exit %%ERRORLEVEL%%" Starting a Gradle Daemon, 80 busy and 1 incompatible and 10 stopped Daemons could not be reused, use --status for details : *clean* FAILEDFAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':clean'. > Unable to delete directory: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources Build step 'Invoke Gradle script' changed build result to FAILURE - 2) When I try to wipe out the workspace manually in Jenkins, I get Also: *java.nio.file.AccessDeniedException:* C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources\Project3XOutput_202004201748.xlsx at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.updateAttributes(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.setReadOnly(Unknown Source) at jenkins.util.io.PathRemover.makeWritable(PathRemover.java:298) at jenkins.util.io.PathRemover.makeRemovable(PathRemover.java:259) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:239) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K Hello All,This is a freestyle project, that runs in windows Jenkins server. My windows Jenkins workspace folder has full access(read/write/modify etc). When I first run the build, I am able to push & attach the file successfully to confluence from jenkins. The file(say *Project3XOutput_202004201748*) is generated in the build\resources folder. My output file has timestamp embedded in the name. But from the next build onwards, I encounter an issue with the deleting or clearing the workspace because of the file *Project3XOutput_202004201748*. I couldnt able to delete the file *Project3XOutput_202004201748* from the * Jenkins server machine * itself. The file will automatically re-appear after refresh even when I made a shift+delete from the Jenkins machine.The only way I can resolve this is to stop the Jenkins server and restart the Jenkins server. After a restart, the first build ran was working fine, but subsequent builds result in the same cleaning issue of the workspace.I see the filename as 0B in the workspace.!image-2020-04-20-20-56-58-876.png!-- Unable to delete the workspace is shown when I run the clean build gradle command. [Project3X] $ cmd /c call C:\WINDOWS\TEMP\jenkins4496026035965746988.batC:\Program Files (x86)\Jenkins\workspace\Project3X>exit 0 [Gradle] - Launching build. [Project3X] $ cmd.exe /C "gradle.bat clean test && exit %%ERRORLEVEL%%" Starting a Gradle Daemon, 80 busy and 1 incompatible and 10 stopped Daemons could not be reused, use --status for details : *clean* FAILEDFAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':clean'. > Unable to delete directory: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources Build step 'Invoke Gradle script' changed build result to FAILURE - 2) When I try to wipe out the workspace manually in Jenkins, I get Also: *java.nio.file.AccessDeniedException:* C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources\Project3XOutput_202004201748.xlsx at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.updateAttributes(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.setReadOnly(Unknown Source) at jenkins.util.io.PathRemover.makeWritable(PathRemover.java:298) at jenkins.util.io.PathRemover.makeRemovable(PathRemover.java:259) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:239) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemo
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K Hello All,This is a freestyle project, that runs in windows Jenkins server. My windows Jenkins workspace folder has full access(read/write/modify etc). When I first run the build, I am able to push & attach the file successfully to confluence from jenkins. The file(say *Project3XOutput_202004201748*) is generated in the build\resources folder. My output file has timestamp embedded in the name. But from the next build onwards, I encounter an issue with the deleting or clearing the workspace because of the file *Project3XOutput_202004201748*. I couldnt able to delete the file *Project3XOutput_202004201748* from the *Jenkins server machine* itself. The file will automatically re- appear appears after refresh even when I made a shift+delete from the Jenkins machine.The only way I can resolve this is to stop the Jenkins server and restart the Jenkins server. After a restart, the first build ran was working fine, but subsequent builds result in the same cleaning issue of the workspace.I see the filename as 0B in the workspace.!image-2020-04-20-20-56-58-876.png!-- Unable to delete the workspace is shown when I run the clean build gradle command. [Project3X] $ cmd /c call C:\WINDOWS\TEMP\jenkins4496026035965746988.batC:\Program Files (x86)\Jenkins\workspace\Project3X>exit 0 [Gradle] - Launching build. [Project3X] $ cmd.exe /C "gradle.bat clean test && exit %%ERRORLEVEL%%" Starting a Gradle Daemon, 80 busy and 1 incompatible and 10 stopped Daemons could not be reused, use --status for details : *clean* FAILEDFAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':clean'. > Unable to delete directory: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources Build step 'Invoke Gradle script' changed build result to FAILURE - 2) When I try to wipe out the workspace manually in Jenkins, I get Also: *java.nio.file.AccessDeniedException:* C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources\Project3XOutput_202004201748.xlsx at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.updateAttributes(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.setReadOnly(Unknown Source) at jenkins.util.io.PathRemover.makeWritable(PathRemover.java:298) at jenkins.util.io.PathRemover.makeRemovable(PathRemover.java:259) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:239) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(P
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K Hello All,This is a freestyle project, that runs in windows Jenkins server. My windows Jenkins workspace folder has full access(read/write/modify etc). When I first run the build, I am able to push & attach the file successfully to confluence from jenkins. The file(say *Project3XOutput_202004201748*) is generated in the build\resources folder. My output file has timestamp embedded in the name. From But from the next build onwards, I encounter an issue with the deleting or clearing the workspace because of the file *Project3XOutput_202004201748*. I couldnt able to delete the file *Project3XOutput_202004201748* from the Jenkins machine itself. The file will automatically re-appear after refresh even when I made a shift+delete from the Jenkins machine.The only way I can resolve this is to stop the Jenkins server and restart the Jenkins server. After a restart, the first build ran was working fine, but subsequent builds result in the same cleaning issue of the workspace.I see the filename as 0B in the workspace.!image-2020-04-20-20-56-58-876.png!-- Unable to delete the workspace is shown when I run the clean build gradle command. [Project3X] $ cmd /c call C:\WINDOWS\TEMP\jenkins4496026035965746988.batC:\Program Files (x86)\Jenkins\workspace\Project3X>exit 0 [Gradle] - Launching build. [Project3X] $ cmd.exe /C "gradle.bat clean test && exit %%ERRORLEVEL%%" Starting a Gradle Daemon, 80 busy and 1 incompatible and 10 stopped Daemons could not be reused, use --status for details : *clean* FAILEDFAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':clean'. > Unable to delete directory: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources Build step 'Invoke Gradle script' changed build result to FAILURE - 2) When I try to wipe out the workspace manually in Jenkins, I get Also: *java.nio.file.AccessDeniedException:* C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources\Project3XOutput_202004201748.xlsx at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.updateAttributes(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.setReadOnly(Unknown Source) at jenkins.util.io.PathRemover.makeWritable(PathRemover.java:298) at jenkins.util.io.PathRemover.makeRemovable(PathRemover.java:259) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:239) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K Attachment: image-2020-04-20-20-56-58-876.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205871.1587432755000.14386.1587434280320%40Atlassian.JIRA.
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K Hello All, This is a freestyle project, that runs in windows Jenkins server . My windows Jenkins workspace folder has full access(read/write/modify etc). When I first run the build, I am able to push & attach the file successfully to confluence from jenkins. The file(say *Project3XOutput_202004201748*) is generated in the build\resources folder. My output file has timestamp embedded in the name. From the next build onwards, I encounter an issue with the deleting or clearing the workspace because of the file *Project3XOutput_202004201748*. I couldnt able to delete the file *Project3XOutput_202004201748* from the Jenkins machine itself. The file will automatically re-appear after refresh even when I made a shift+delete from the Jenkins machine.The only way I can resolve this is to stop the Jenkins server and restart the Jenkins server. After a restart, the first build ran was working fine, but subsequent builds result in the same cleaning issue of the workspace.I see the filename as 0B in the workspace. !image-2020-04-20-20-56-58-876.png!-- Unable to delete the workspace is shown when I run the clean build gradle command. [Project3X] $ cmd /c call C:\WINDOWS\TEMP\jenkins4496026035965746988.batC:\Program Files (x86)\Jenkins\workspace\Project3X>exit 0 [Gradle] - Launching build. [Project3X] $ cmd.exe /C "gradle.bat clean test && exit %%ERRORLEVEL%%" Starting a Gradle Daemon, 80 busy and 1 incompatible and 10 stopped Daemons could not be reused, use --status for details : *clean* FAILEDFAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':clean'. > Unable to delete directory: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources Build step 'Invoke Gradle script' changed build result to FAILURE - 2) When I try to wipe out the workspace manually in Jenkins, I get Also: *java.nio.file.AccessDeniedException:* C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources\Project3XOutput_202004201748.xlsx at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.updateAttributes(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.setReadOnly(Unknown Source) at jenkins.util.io.PathRemover.makeWritable(PathRemover.java:298) at jenkins.util.io.PathRemover.makeRemovable(PathRemover.java:259) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:239) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216) a
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K This is a freestyle project , that runs in windows . My windows Jenkins workspace folder has full access(read/write/modify etc). When I first run the build, I am able to push & attach the file successfully to confluence from jenkins. The file(say *Project3XOutput_202004201748*) is generated in the build\resources folder. My output file has timestamp embedded in the name. From the next build onwards, I encounter an issue with the deleting or clearing the workspace because of the file *Project3XOutput_202004201748*. I couldnt able to delete the file *Project3XOutput_202004201748* from the Jenkins machine itself. The file will automatically re-appear after refresh even when I made a shift+delete from the Jenkins machine.The only way I can resolve this is to stop the Jenkins server and restart the Jenkins server. After a restart, the first build ran was working fine, but subsequent builds result in the same cleaning issue of the workspace.I see the filename as 0B in the workspace.!image-2020-04-20-20-56-58-876.png!-- Unable to delete the workspace is shown when I run the clean build gradle command. [Project3X] $ cmd /c call C:\WINDOWS\TEMP\jenkins4496026035965746988.batC:\Program Files (x86)\Jenkins\workspace\Project3X>exit 0 [Gradle] - Launching build. [Project3X] $ cmd.exe /C "gradle.bat clean test && exit %%ERRORLEVEL%%" Starting a Gradle Daemon, 80 busy and 1 incompatible and 10 stopped Daemons could not be reused, use --status for details : *clean* FAILEDFAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':clean'. > Unable to delete directory: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources Build step 'Invoke Gradle script' changed build result to FAILURE - 2) When I try to wipe out the workspace manually in Jenkins, I get Also: *java.nio.file.AccessDeniedException:* C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources\Project3XOutput_202004201748.xlsx at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.updateAttributes(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.setReadOnly(Unknown Source) at jenkins.util.io.PathRemover.makeWritable(PathRemover.java:298) at jenkins.util.io.PathRemover.makeRemovable(PathRemover.java:259) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:239) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216) at jenkins.util.io.PathRemo
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K Attachment: Passing with no files to attach.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205871.1587432755000.14384.1587433500123%40Atlassian.JIRA.
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K This is a freestyle project. Unable to delete the workspace is shown when I run the clean build gradle command. [Project3X] $ cmd /c call C:\WINDOWS\TEMP\jenkins4496026035965746988.batC:\Program Files (x86)\Jenkins\workspace\Project3X>exit 0 [Gradle] - Launching build. [Project3X] $ cmd.exe /C "gradle.bat clean test && exit %%ERRORLEVEL%%" Starting a Gradle Daemon, 80 busy and 1 incompatible and 10 stopped Daemons could not be reused, use --status for details : *clean* FAILEDFAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':clean'. > Unable to delete directory: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources Build step 'Invoke Gradle script' changed build result to FAILURE - 2) When I try to wipe out the workspace manually in Jenkins, I get Also: * java.nio.file.AccessDeniedException: * C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources\Project3XOutput_202004201748.xlsx at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.updateAttributes(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.setReadOnly(Unknown Source) at jenkins.util.io.PathRemover.makeWritable(PathRemover.java:298) at jenkins.util.io.PathRemover.makeRemovable(PathRemover.java:259) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:239) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)Also: Also: * java.nio.file.DirectoryNotEmptyException: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources * at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source) at java.nio.file.Files.deleteIfExists(Unknown Source) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237) Also: * java.nio.file.DirectoryNotEmptyException: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources * at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.Abst
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K This is a freestyle project. Unable to delete the workspace is shown when I run the clean build gradle command. [Project3X] $ cmd /c call C:\WINDOWS\TEMP\jenkins4496026035965746988.batC:\Program Files (x86)\Jenkins\workspace\Project3X>exit 0 [Gradle] - Launching build.[Project3X] $ cmd.exe /C "gradle.bat clean test && exit %%ERRORLEVEL%%"Starting a Gradle Daemon, 80 busy and 1 incompatible and 10 stopped Daemons could not be reused, use --status for details:*clean* FAILEDFAILURE: Build failed with an exception. * What went wrong:Execution failed for task ':clean'.> Unable to delete directory: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources Build step 'Invoke Gradle script' changed build result to FAILURE * Try: Run with -- stacktrace option to get the stack trace. Run with -- info or -- debug option --- 2) When I try to wipe out the workspace manually in Jenkins, I get more log output Also: java . Run nio.file.AccessDeniedException: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources\Project3XOutput_202004201748.xlsx at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.updateAttributes(Unknown Source) at sun.nio.fs.WindowsFileAttributeViews$Dos.setReadOnly(Unknown Source) at jenkins.util.io.PathRemover.makeWritable(PathRemover.java:298) at jenkins.util.io.PathRemover.makeRemovable(PathRemover.java:259) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:239) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226) at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215) at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:96)Also: Also: java.nio.file.DirectoryNotEmptyException: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source) at java.nio.file.Files.deleteIfExists(Unknown Source) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237) Also: java.nio.file.DirectoryNotEmptyException: C:\Program Files (x86)\Jenkins\workspace\Project3X\bui
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K [Project3X] $ cmd /c call C:\WINDOWS\TEMP\jenkins4496026035965746988.batC:\Program Files (x86)\Jenkins\workspace\Project3X>exit 0 [Gradle] - Launching build.[Project3X] $ cmd.exe /C "gradle.bat clean test && exit %%ERRORLEVEL%%"Starting a Gradle Daemon, 80 busy and 1 incompatible and 10 stopped Daemons could not be reused, use --status for details:*clean* FAILEDFAILURE: Build failed with an exception.* What went wrong:Execution failed for task ':clean'.> Unable to delete directory: C:\Program Files (x86)\Jenkins\workspace\Project3X\build\resources* Try:Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.* Get more help at [https://help.gradle.org|https://help.gradle.org/]BUILD FAILED in 8s1 actionable task: 1 executedBuild step 'Invoke Gradle script' changed build result to FAILUREBuild step 'Invoke Gradle script' marked build as failure Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence through confluence publisher
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence through confluence publisher Change By: Tejo K Summary: unable to delete workspace after attaching a file to confluence . through confluence publisher Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205871.1587432755000.14376.1587432840238%40Atlassian.JIRA.
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence.
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence. Change By: Tejo K Attachment: Failure screenshot.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205871.1587432755000.14374.1587432780344%40Atlassian.JIRA.
[JIRA] (JENKINS-61981) unable to delete workspace after attaching a file to confluence.
Title: Message Title Tejo K created an issue Jenkins / JENKINS-61981 unable to delete workspace after attaching a file to confluence. Issue Type: Bug Assignee: Joe Hansche Attachments: Failure screenshot.png Components: confluence-publisher-plugin Created: 2020-04-21 01:32 Environment: Jenkins version: 2.222.1 Confluence Publisher: 2.0.5 Atlassian Confluence 7.3.1 Priority: Major Reporter: Tejo K Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title
David Rodriguez edited a comment on JENKINS-61943
Re: Jenkins2, P4 Plugin: Error must create client ' to access local files
Hi Karl,The P4 command below is executed within maven {code:java}/bin/sh -c p4 -d /data/jenkins_home/workspace/admin-ui-4.2 changes -m1 ...{code} Why doesn't the P4CLIENT persist throughout the job like it does with Jenkins1. This way it's backward compatible when upgrading from jenkin1 to jenkins2. Otherwise the P4 Plugin it's not backward compatible.I modified the job on both jenkins1 and jenkin2 job by removing the maven step and adding adding only the shell step to execute the above command. The jenkins job config.xml and console logs are attached. * [^jenkins1-job-config.xml][^jenkins1-job-console.log][^jenkins2-job-config.xml][^jenkins2-job-console.log]!/jira/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!Note on Jenkin1, the P4 command below in the log returns an expected change from the perforce repo. Is it possible for the the P4 plugin in Jenkins2 to do the same? If so, how?Jenkin1 shell: {code:java}echo "P4CLIENT = $P4CLIENT"echo "P4_CLIENT = $P4_CLIENT"echo "PWD = `pwd`"cmd="/usr/bin/p4 -d /data/builds/workspace/drod-test-1.6 changes -m1 ..."`$cmd`{code} {panel:title=Jenkin1 console log}Sync complete, took 1003 ms[drod-test-1.6] $ /bin/sh -xe /tmp/hudson1085421712960825854.sh+ echo P4CLIENT = ci-drod-test-1.6-1091564373P4CLIENT = ci-drod-test-1.6-1091564373+ echo P4_CLIENT = P4_CLIENT = + pwd+ echo PWD = /data/builds/workspace/drod-test-1.6PWD = /data/builds/workspace/drod-test-1.6+ cmd=/usr/bin/p4 -d /data/builds/workspace/drod-test-1.6 changes -m1 ...+ /usr/bin/p4 -d /data/builds/workspace/drod-test-1.6 changes -m1 ...*{color:#4c9aff}+ Change 290033 on 2018/11/16 by davidt@FR-NBSPT6 ' IT test fail'{color}*/tmp/hudson1085421712960825854.sh: 8: /tmp/hudson1085421712960825854.sh: Change: not foundBuild step 'Execute shell' marked build as failureFinished: FAILURE{panel} Jenkin2 shell: {code:java}echo "P4CLIENT = $P4CLIENT"echo "P4_CLIENT = $P4_CLIENT"echo "PWD = `pwd`"cmd="/usr/bin/p4 -d /data/jenkins_home/workspace/drod-test-2.222 changes -m1 ..."`$cmd`{code} {panel:title=Jenkin2 console log}[drod-test-2.222] $ /bin/sh -xe /tmp/jenkins7634372390604735818.sh+ echo P4CLIENT = P4CLIENT = + echo P4_CLIENT = ci-drod-test-2.222P4_CLIENT = ci-drod-test-2.222+ pwd+ echo PWD = /data/jenkins_home/workspace/drod-test-2.222PWD = /data/jenkins_home/workspace/drod-test-2.222+ cmd=/usr/bin/p4 -d /data/jenkins_home/workspace/drod-test-2.222 changes -m1 ...+ /usr/bin/p4 -d /data/jenkins_home/workspace/drod-test-2.222 changes -m1 ...*{color:#de350b}... - must create client 'ip-10-21-2-84' to access local files.{color}*+ Build step 'Execute shell'{panel}
Add Comment
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Hi Karl, The P4 command below is executed within maven /bin/sh -c p4 -d /data/jenkins_home/workspace/admin-ui-4.2 changes -m1 ... Why doesn't the P4CLIENT persist throughout the job like it does with Jenkins1. This way it's backward compatible when upgrading from jenkin1 to jenkins2. Otherwise the P4 Plugin it's not backward compatible. I modified the job on both jenkins1 and jenkin2 job by removing the maven step and adding adding only the shell step to execute the above command. The jenkins job config.xml and console logs are attached. jenkins1-job-config.xmljenkins1-job-console.logjenkins2-job-config.xmljenkins2-job-console.log Note on Jenkin1, the P4 command below in the log returns an expected change from the perforce repo. Is it possible for the the P4 plugin in Jenkins2 to do the same? If so, how? Jenkin1 shell: echo "P4CLIENT = $P4CLIENT" echo "P4_CLIENT = $P4_CLIENT" echo "PWD = `pwd` "cmd="/usr/bin/p4 -d /data/builds/workspace/drod-test-1.6 changes -m1 ..." `$cmd` Jenkin1 console log Sync complete, took 1003 ms [drod-test-1.6] $ /bin/sh -xe /tmp/hudson1085421712960825854.sh + echo P4CLIENT = ci-drod-test-1.6-1091564373 P4CLIENT = ci-drod-test-1.6-1091564373 + echo P4_CLIENT = P4_CLIENT = + pwd + echo PWD = /data/builds/workspace/drod-test-1.6 PWD = /data/builds/workspace/drod-test-1.6 + cmd=/usr/bin/p4 -d /data/builds/workspace/drod-test-1.6 changes -m1 ... + /usr/bin/p4 -d /data/builds/workspace/drod-test-1.6 changes -m1 ... + Change 290033 on 2018/11/16 by davidt@FR-NBSPT6 ' IT test fail' /tmp/hudson1085421712960825854.sh: 8: /tmp/hudson1085421712960825854.sh: Change: not found Build step 'Execute shell' marked build as failure Finished: FAILURE Jenkin2 shell: echo "P4CLIENT = $P4CLIENT" echo "P4_CLIENT = $P4_CLIENT" echo "PWD = `pwd`" cmd="/usr/bin/p4 -d /data/jenkins_home/workspace/drod-test-2.222 changes -m1 ..." `$cmd`
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: David Rodriguez Attachment: jenkins2-job-config.xml Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14364.1587426720236%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: David Rodriguez Attachment: jenkins2-job-console.log Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14366.1587426720266%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: David Rodriguez Attachment: jenkins2-job-console.log Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14362.1587426660297%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: David Rodriguez Attachment: jenkins1-job-console.log Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14360.1587426660227%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: David Rodriguez Attachment: jenkins1-job-config.xml Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14358.1587426600194%40Atlassian.JIRA.
[JIRA] (JENKINS-44466) Allow plugins to override aspects of the Blue Ocean theme
Title: Message Title Ricardo Catalfo commented on JENKINS-44466 Re: Allow plugins to override aspects of the Blue Ocean theme We are using Blue Ocean with generic pipelines and custom backend (custom approvals & audits via rest calls) and a way to customize the main UI will be very useful. Just like Brandon, we use colors to help some users easily identify Test vs Production Environments. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182294.1495611527000.14346.1587424620640%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Marky Jackson commented on JENKINS-61980 Re: Plugin Failed to load the Matrix Can you share a screenshot of the config page in the Jenkins UI? Also, can you share you scrape config? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205870.1587423122000.14339.1587423360203%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Monil Patel created an issue Jenkins / JENKINS-61980 Plugin Failed to load the Matrix Issue Type: Bug Assignee: Marky Jackson Attachments: Capture.PNG Components: prometheus-plugin Created: 2020-04-20 22:52 Environment: Jenkins 2.222.1 Prometheus plugin v.2.0.7 or v.2.0.0 Labels: Prometheus Priority: Blocker Reporter: Monil Patel I installed the Prometheus plugin v.2.0.7 on my jenkins master which run on v.2.222.1. After installing, when i visited htts://jenkins_url/prometheus it shows blank page. The strange thing is that i installed same plugin on different instance which has exactly similar configuration works well. I double checked all the configuration of the plugin but every thing looks correct based on the documentation.
[JIRA] (JENKINS-46669) When setting up, "Continue as Admin" button can be made less confusing
Title: Message Title Sam Hrncir assigned an issue to Sam Hrncir Jenkins / JENKINS-46669 When setting up, "Continue as Admin" button can be made less confusing Change By: Sam Hrncir Assignee: Sam Hrncir Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185009.1504680543000.14333.1587422640575%40Atlassian.JIRA.
[JIRA] (JENKINS-49362) Master unable to connect to GitHub using IBM JDK 8 - Unable to find acceptable protocols
Title: Message Title Mark Waite commented on JENKINS-49362 Re: Master unable to connect to GitHub using IBM JDK 8 - Unable to find acceptable protocols Jenkins now also supports JDK 11. AdoptOpenJDK 11 on z390x provides a just in time compiler that should provide good performance with Jenkins without the requirement to upgrade okhttp to a newer version in the various Jenkins components. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188229.1517798676000.14330.1587422400186%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Liam Newman resolved as Fixed Fixed in Blue Ocean 1.23.0 Jenkins / JENKINS-61822 Unable to authorize blueocean with github Change By: Liam Newman Status: Open Resolved Resolution: Fixed Released As: 1.23.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-61979) cannot select/add credentials in settings -> github server
Title: Message Title Orange Cat created an issue Jenkins / JENKINS-61979 cannot select/add credentials in settings -> github server Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2020-04-20 22:10 Environment: Fedora 31 workstation awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.separator / java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 55.0 java.home /usr/lib/jvm/java-11-openjdk-11.0.6.10-0.fc31.x86_64 java.io.tmpdir /tmp java.library.path /usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 11.0.6+10 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 11 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.java.com/bugreport/ java.vendor.version 18.9 java.version 11.0.6 java.version.date 2020-01-14 java.vm.compressedOopsMode Zero based java.vm.info mixed mode, sharing java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 11 java.vm.vendor Oracle Corporation java.vm.version 11.0.6+10 jdk.debug release JENKINS_HOME /var/lib/jenkins jetty.git.hash a304fd9f351f337e7c0e2a7c28878dd536149c6c jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib jnidispatch.path /var/lib/jenkins/.cache/JNA/temp/jna7061041560422982676.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 5.5.17-200.fc31.x86_64 path.separator : sun.arch.data.model 64 sun.boot.library.path /usr/lib/jvm/java-11-openjdk-11.0.6.10-0.fc31.x86_64/lib sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 --prefix=/jenkins sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country CN user.dir / user.home /var/lib/jenkins use
[JIRA] (JENKINS-61977) Adding a credential of specific type
Title: Message Title Orange Cat assigned an issue to Unassigned Jenkins / JENKINS-61977 Adding a credential of specific type Change By: Orange Cat Assignee: Orange Cat Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205866.1587392127000.14275.158742303%40Atlassian.JIRA.
[JIRA] (JENKINS-61977) Adding a credential of specific type
Title: Message Title Orange Cat assigned an issue to Orange Cat Jenkins / JENKINS-61977 Adding a credential of specific type Change By: Orange Cat Assignee: Orange Cat Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205866.1587392127000.14273.1587419940322%40Atlassian.JIRA.
[JIRA] (JENKINS-42940) Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet
Title: Message Title Devin Nusbaum updated JENKINS-42940 A fix for this issue was just released in version 2.20 of Pipeline: Basic Steps Plugin. Jenkins / JENKINS-42940 Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: workflow-basic-steps 2.20 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-59776) workflow-basic-steps-plugin "waitUntil" should have a quiet mode
Title: Message Title Devin Nusbaum resolved as Fixed A fix for this issue was just released in version 2.20 of Pipeline: Basic Steps Plugin. Thanks Bryan Jensen for adding the new option! Jenkins / JENKINS-59776 workflow-basic-steps-plugin "waitUntil" should have a quiet mode Change By: Devin Nusbaum Status: Open Resolved Assignee: Bryan Jensen Resolution: Fixed Released As: workflow-basic-steps 2.20 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60801) Variable changes are shared between matrix (parallel) stages.
Title: Message Title Corey Woodcox commented on JENKINS-60801 Re: Variable changes are shared between matrix (parallel) stages. We also see this in a similar build script. We have a job that loops through a list of versions and fires off several docker image builds in parallel and at the end of the script the image name variables have overwritten each other. I can try and grab more information if you think it would help troubleshoot. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204130.1579197922000.14243.1587414240105%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title
Charles Smith edited a comment on JENKINS-61356
Re: Unable to connect to slave via Launch Agent mode(SSH)
[~ifernandezcalvo]Thank you for all your updates on this issue. Yes, I'm 1000% sure that it's the PRIVATE key(not PUBLIC) that I'm copying into the SSH credential field that asks for the PRIVATE key. I've created another keypair({color:# FF ff }61356-key{color} & {color:# FF ff }61356-key.pub{color}) and able to ssh without issue from the Master to the Build(slave) system using this test keypair. However, the same keypair isn't working when used by the shh credential plugin to launch the build agent. I've attached the keypair for your usage testing /visibility. If this is an issue with copying/pasting the keypair with added Unix line breaks, then what is a workaround for this? I'm a Unix guy so I copy the PRIVATE key from my Putty terminal directly into the SSH credential field. Is there another way of doing this to test this theory? Other than that, we're currently running RHEL7.8:{code:java}$ ssh -VOpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017{code} We also run security McAfee software that may potentially be an issue when creating the keypair:{code:java}# systemctl status mfeespd.service; systemctl status mfetpd.service● mfeespd.service - McAfee Endpoint Security Platform for Linux Loaded: loaded (/usr/lib/systemd/system/mfeespd.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2020-04-15 14:13:48 CDT; 5 days ago Docs: man:mfeespd(8) Main PID: 4574 (mfeespd)Tasks: 9 Memory: 2.9M CGroup: /system.slice/mfeespd.service └─4574 /opt/McAfee/ens/esp/bin/mfeespdApr 15 14:13:46 ansible-baseline-rhel7-test.uscis.dhs.gov systemd[1]: Starting M...Apr 15 14:13:46 ansible-baseline-rhel7-test.uscis.dhs.gov prepare-mfeesp.sh[4561]: ...Apr 15 14:13:48 ansible-baseline-rhel7-test.uscis.dhs.gov systemd[1]: Started Mc...Hint: Some lines were ellipsized, use -l to show in full.● mfetpd.service - McAfee Endpoint Security for Linux Threat Prevention Loaded: loaded (/usr/lib/systemd/system/mfetpd.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2020-04-15 14:13:49 CDT; 5 days ago Docs: man:mfetpd(8) Main PID: 4732 (mfetpd)Tasks: 49 Memory: 1.4G CGroup: /system.slice/mfetpd.service ├─ 4732 /opt/McAfee/ens/tp/bin/mfetpd ├─ 4777 /opt/McAfee/ens/tp/bin/mfetpd ├─20076 /opt/McAfee/ens/tp/bin/mfetpd └─20084 /opt/McAfee/ens/tp/bin/mfetpdApr 15 14:13:49 ansible-baseline-rhel7-test.uscis.dhs.gov systemd[1]: Starting M...Apr 15 14:13:49 ansible-baseline-rhel7-test.uscis.dhs.gov systemd[1]: Started Mc...Apr 15 14:13:50 ansible-baseline-rhel7-test.uscis.dhs.gov mfetpd[4732]: error: F...Hint: Some lines were ellipsized, use -l to show in full.{code}However, the keypair works when I use it to ssh from the shell.
Add Comment
[JIRA] (JENKINS-53287) [zephyr-for-jira-test-management] - ZephyrforJiraPlugin: Security risk when the job is misconfigured
Title: Message Title vignesh nehru commented on JENKINS-53287 Re: [zephyr-for-jira-test-management] - ZephyrforJiraPlugin: Security risk when the job is misconfigured Atleast your able to move the test from jenkins to Zephr with in Jira.For me the the jobs itself dont appear in the jenkins configuration and it says as 'No Project' Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185739.1507291696000.14231.1587413340396%40Atlassian.JIRA.
[JIRA] (JENKINS-61829) 403 error while fetching the JIRA projects in jenkins
Title: Message Title vignesh nehru commented on JENKINS-61829 Re: 403 error while fetching the JIRA projects in jenkins Yeah i see the same problem.The Projects are not getting listed under the project list dropdown.This is making the usabity of zephr very low on integrating automated tests.I have. junit report getting created correctly but cannot upload the results into Jira due to this error Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205682.1586256225000.14222.1587413160292%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith updated an issue Jenkins / JENKINS-61356 Unable to connect to slave via Launch Agent mode(SSH) Change By: Charles Smith Attachment: 61356-key.txt Attachment: 61356-key.pub.txt Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.14217.1587412320289%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Ivan Fernandez Calvo Thank you for all your updates on this issue. Yes, I'm 1000% sure that it's the PRIVATE key(not PUBLIC) that I'm copying into the SSH credential field that asks for the PRIVATE key. I've created another keypair(61356-key & 61356-key.pub) and able to ssh without issue from the Master to the Build(slave) system using this test keypair. However, the same keypair isn't working when used by the shh credential plugin to launch the build agent. I've attached the keypair for your usage/visibility. If this is an issue with copying/pasting the keypair with added Unix line breaks, then what is a workaround for this? I'm a Unix guy so I copy the PRIVATE key from my Putty terminal directly into the SSH credential field. Is there another way of doing this to test this theory? Other than that, we're currently running RHEL7.8: $ ssh -V OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017 We also run security McAfee software that may potentially be an issue when creating the keypair: # systemctl status mfeespd.service; systemctl status mfetpd.service ● mfeespd.service - McAfee Endpoint Security Platform for Linux Loaded: loaded (/usr/lib/systemd/system/mfeespd.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2020-04-15 14:13:48 CDT; 5 days ago Docs: man:mfeespd(8) Main PID: 4574 (mfeespd) Tasks: 9 Memory: 2.9M CGroup: /system.slice/mfeespd.service └─4574 /opt/McAfee/ens/esp/bin/mfeespdApr 15 14:13:46 ansible-baseline-rhel7-test.uscis.dhs.gov systemd[1]: Starting M... Apr 15 14:13:46 ansible-baseline-rhel7-test.uscis.dhs.gov prepare-mfeesp.sh[4561]: ... Apr 15 14:13:48 ansible-baseline-rhel7-test.uscis.dhs.gov systemd[1]: Started Mc... Hint: Some lines were ellipsized, use -l to show in full. ● mfetpd.service - McAfee Endpoint Security for Linux Threat Prevention Loaded: loaded (/usr/lib/systemd/system/mfetpd.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2020-04-15 14:13:49 CDT; 5 days ago Docs: man:mfetpd(8) Main PID: 4732 (mfetpd) Tasks: 49 Memory: 1.4G CGroup: /system.slice/mfetpd.service ├─ 4732 /opt/McAfee/ens/tp/bin/mfetpd ├─ 4777 /opt/McAfee/ens/tp/bin/mfetpd ├─20076 /opt/McAfee/ens/tp/bin/mfetpd └─20084 /opt/McAfee/ens/tp/bin/mfetpdApr 15 14:13:49 ansible-baseline-rhel7-test.uscis.dhs.gov systemd[1]: Starting M... Apr 15 14:13:49 ansible-baseline-rhel7-test.uscis.dhs.gov systemd[1]: Started Mc... Apr 15 14:13:50 ansible-baseline-rhel7-test.uscis.dhs.gov mfetpd[4732]: error: F... Hint: Some lines were ellipsized, use -l to show in full. However, the keypair works when I use it to ssh from the shell.
[JIRA] (JENKINS-52310) Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support
Title: Message Title Gavin Mogan closed an issue as Fixed Jenkins / JENKINS-52310 Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support Change By: Gavin Mogan Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192093.1530522315000.14185.1587408961055%40Atlassian.JIRA.
[JIRA] (JENKINS-56662) BlueOcean fails to complete loading
Title: Message Title Gavin Mogan assigned an issue to Unassigned Jenkins / JENKINS-56662 BlueOcean fails to complete loading Change By: Gavin Mogan Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198296.1553169344000.14181.1587408960941%40Atlassian.JIRA.
[JIRA] (JENKINS-46521) Non-multibranch pipelines do not have any changeset information
Title: Message Title Gavin Mogan assigned an issue to Unassigned Jenkins / JENKINS-46521 Non-multibranch pipelines do not have any changeset information Change By: Gavin Mogan Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184838.1504013955000.14187.1587408961168%40Atlassian.JIRA.
[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Gavin Mogan assigned an issue to Unassigned Jenkins / JENKINS-56773 High master CPU usage introduced by Blue Ocean 1.14.0 Change By: Gavin Mogan Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198417.1553679453000.14166.1587408900434%40Atlassian.JIRA.
[JIRA] (JENKINS-38220) Support for EC2 instance profile credentials
Title: Message Title John La Barge edited a comment on JENKINS-38220 Re: Support for EC2 instance profile credentials I'v noticed that there is a checkbox that is labeled as "Use EC2 instance profile to obtain credentials" but even if it's checked, if no private key is supplied it throws a NPE. This seems incorrect or at least confusing to me. Instead I'd propose that if that box is checked, no private key is required. There are essentially two steps to getting the agent: 1) provisioning the ec2 instance - for which the instance credentials can be used and 2) connecting to the agent. If this is required to connect to the agent, that can be internalized instead with a temporary ssh key. So in that case I would remove the logic that seeks to use the supplied private key and instead generate a key and use it silently. Thoughts (before I start implementing the PR) ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174381.1473894967000.14157.1587405900278%40Atlassian.JIRA.
[JIRA] (JENKINS-38220) Support for EC2 instance profile credentials
Title: Message Title John La Barge edited a comment on JENKINS-38220 Re: Support for EC2 instance profile credentials I'v noticed that there is a checkbox that is labeled as "Use EC2 instance profile to obtain credentials" but even if it's checked, if no private key is supplied it throws a NPE. This seems incorrect or at least confusing to me. Instead I'd propose that if that box is checked, no private key is required. If this is required to connect to the agent, that can be internalized instead with a temporary ssh key. So in that case I would remove the logic that seeks to use the supplied private key and instead generate a key and use it silently. Thoughts (before I start implementing the PR) ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174381.1473894967000.14155.1587405600662%40Atlassian.JIRA.
[JIRA] (JENKINS-38220) Support for EC2 instance profile credentials
Title: Message Title John La Barge commented on JENKINS-38220 Re: Support for EC2 instance profile credentials I'v noticed that there is a checkbox that is labeled as "Use EC2 instance profile to obtain credentials" but even if it's checked, if no private key is supplied it throws a NPE. This seems incorrect or at least confusing to me. Instead I'd propose that if that box is checked, no private key is required. If this is required to connect to the agent, that can be internalized instead with a temporary ssh key. So in that case I would remove the logic that seeks to use the supplied private key and instead generate a key and use it silently. Thoughts? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174381.1473894967000.14139.1587405540305%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixing#createProject() does not call Jenkins#checkGoodName
Title: Message Title
Calvin Park commented on JENKINS-61956
Re: ItemGroupMixing#createProject() does not call Jenkins#checkGoodName
Looked into it more and came up with this.
// Create a folder and its parent folders
// mkdir -p folder_path
Folder create_folder_and_parent_folders(String folder_path) {
// If the folder already exists, return
Folder folder = Jenkins.instance.getItemByFullName(folder_path)
if (folder)
return folder
String folder_name, parent_path
def parent_folder
// If the folder is top level, set parent to Jenkins itself
if (!folder_path.contains("/")) {
parent_folder = Jenkins.instance
folder_name = folder_path
}
// If the folder is a sub-folder, recurse to create/fetch the parent folder
else {
parent_path = StringUtils.substringBeforeLast(folder_path, "/")
parent_folder = create_folder_and_parent_folders(parent_path)
folder_name = StringUtils.substringAfterLast(folder_path, "/")
}
// Create the folder in the parent folder
return parent_folder.createProject(Folder.class, folder_name)
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request >I appreciate you looking into this. What is the timetable for changing the core library? not soon, I do not have a start date to make it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.14136.1587403260206%40Atlassian.JIRA.
[JIRA] (JENKINS-61919) Audit trail plugin shows anonymous user logged out
Title: Message Title Ankur commented on JENKINS-61919 Re: Audit trail plugin shows anonymous user logged out I am forwarding all logs to Splunk. Here is how it shows up there: Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205793.1586970989000.14134.1587401880357%40Atlassian.JIRA.
[JIRA] (JENKINS-61919) Audit trail plugin shows anonymous user logged out
Title: Message Title Ankur updated an issue Jenkins / JENKINS-61919 Audit trail plugin shows anonymous user logged out Change By: Ankur Attachment: Splunk Anonymous entry.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205793.1586970989000.14132.1587401880332%40Atlassian.JIRA.
[JIRA] (JENKINS-61915) Only reject servers whose name ends with bitbucket.org
Title: Message Title Stefan Marklund updated an issue Jenkins / JENKINS-61915 Only reject servers whose name ends with bitbucket.org Change By: Stefan Marklund Summary: FormValidation checkBaseUrl only allow Only reject servers whose name ends with bitbucket.org Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205789.1586958535000.14094.1587399840220%40Atlassian.JIRA.
[JIRA] (JENKINS-61978) AD user not able to login using Active Directory plugin
Title: Message Title Jason Gibbons created an issue Jenkins / JENKINS-61978 AD user not able to login using Active Directory plugin Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2020-04-20 16:04 Environment: Jenkins 2.190.2 AD plugin version 2.16 Server running on Windows 2012 server Priority: Minor Reporter: Jason Gibbons For most users the AD plugin is working well. However for one user on the domain, all login attempts are being refused because of incorrect password. The password he is using is, however, the correct one and is the one used to login to all other resources on the network. It is uniquely with the Jenkins server that the problem occurs. Looking at the logs (full output below) for all users that succeed in logging in I see this kind of entry: dn=CN=,OU=,OU=Services,OU=,OU=Locations,DC=misys,DC=global,DC=ad but for the case of this one user, and only this user, the dn is in upper case: Login failure: Incorrect password for DN=CN=,OU=,OU=Users,OU=,OU=Locations,DC=misys,DC=global,DC=ad The only difference at this level appears to be that "DN" is in upper case. This is probably just a quirk in the error logging. One difference about his name that may be salient is that it contains a cedilla. A recent forced flush and reassignment of all user passwords was implemented across the company, the user could log in prior to that event but now, even after changing his password, login is not possible for the user. The issue replicates for this user using different Jenkins server instances (same version of Jenkins plus plug in). It also replicates no matter which workstation the user attempts to login from (his own or someone else's). Full error log is as follows: Login failure: Incorrect password for
[JIRA] (JENKINS-61915) FormValidation checkBaseUrl only allow bitbucket.org
Title: Message Title Stefan Marklund commented on JENKINS-61915 Re: FormValidation checkBaseUrl only allow bitbucket.org Hello, To add a little additional context. When the server name contains bitbucket.org the plugin will not accept the server because it checks with "contains" for bitbucket.org. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205789.1586958535000.14089.1587398580434%40Atlassian.JIRA.
[JIRA] (JENKINS-61915) FormValidation checkBaseUrl only allow bitbucket.org
Title: Message Title Stefan Marklund updated an issue Jenkins / JENKINS-61915 FormValidation checkBaseUrl only allow bitbucket.org Change By: Stefan Marklund Attachment: image-2020-04-20-18-00-25-407.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205789.1586958535000.14086.1587398460246%40Atlassian.JIRA.
[JIRA] (JENKINS-61840) Revamp the buttons
Title: Message Title Oleg Nenashev updated JENKINS-61840 Jenkins / JENKINS-61840 Revamp the buttons Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.233 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205699.1586355412000.14083.1587397320295%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Ivan Fernandez Calvo I appreciate you looking into this. What is the timetable for changing the core library? I'm trying to determine if my team should continue with the deprecated version of the plugin or maybe pursue another auth method for the time being. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.14081.1587397200197%40Atlassian.JIRA.
[JIRA] (JENKINS-61365) plugin not appearing in pluginManager
Title: Message Title Mark Kirichenko updated JENKINS-61365 Jenkins / JENKINS-61365 plugin not appearing in pluginManager Change By: Mark Kirichenko Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205018.1583498875000.14079.1587396780118%40Atlassian.JIRA.
[JIRA] (JENKINS-61208) Read-only system - View admin monitors
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-61208 Read-only system - View admin monitors Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204758.1582563776000.14078.1587393960383%40Atlassian.JIRA.
[JIRA] (JENKINS-61208) Read-only system - View admin monitors
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61208 Read-only system - View admin monitors Change By: Oleg Nenashev Released As: Jenkins 2.233 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204758.1582563776000.14076.1587393960356%40Atlassian.JIRA.
[JIRA] (JENKINS-52717) Make a release of the folder-properties-plugin
Title: Message Title Miguelángel Fernández edited a comment on JENKINS-52717 Re: Make a release of the folder-properties-plugin I had forgotten to close this a long while ago. I've made a few releases since. [https://github.com/jenkinsci/folder-properties-plugin/releases /tag/v0.1 ] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192607.153242181.14062.1587392520324%40Atlassian.JIRA.
[JIRA] (JENKINS-47055) Jenkins kubernetes plugin - support freestyle jobs
Title: Message Title Tavin Cole commented on JENKINS-47055 Re: Jenkins kubernetes plugin - support freestyle jobs Is there another issue to track container selection for freestyle jobs? Is it technically impossible? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185445.1506084538000.14065.1587392520371%40Atlassian.JIRA.
[JIRA] (JENKINS-52717) Make a release of the folder-properties-plugin
Title: Message Title Miguelángel Fernández closed an issue as Fixed I had forgotten to close this a long while ago. https://github.com/jenkinsci/folder-properties-plugin/releases/tag/v0.1 Jenkins / JENKINS-52717 Make a release of the folder-properties-plugin Change By: Miguelángel Fernández Status: Open Closed Resolution: Fixed Released As: v0.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61977) Adding a credential of specific type
Title: Message Title
Miguelángel Fernández created an issue
Jenkins / JENKINS-61977
Adding a credential of specific type
Issue Type:
Task
Assignee:
Unassigned
Components:
credentials-plugin
Created:
2020-04-20 14:15
Labels:
createItem
Priority:
Minor
Reporter:
Miguelángel Fernández
Say that in a Jenkins configuration the list of available credential types is "A", "B" and "C". Create a job with a credential input parameter FOO_CRED and limit the possible types to type, say "B". Go to Build with Parameters on the job and click the Add button to create a new credential to be used in FOO_CRED. You will see that all the credential types are listed ("A", "B" and "C"), rather than just the ones that the present input parameter is limited to. Ideally, only the types the present input parameter is limited to should be in the dropdown —in this case only "A" should be visible.
Add Comment
[JIRA] (JENKINS-61952) Matcher.find() and Matcher.group(String) are no longer whitelisted
Title: Message Title Devin Nusbaum updated JENKINS-61952 Jenkins / JENKINS-61952 Matcher.find() and Matcher.group(String) are no longer whitelisted Change By: Devin Nusbaum Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205833.1587150538000.14057.1587391020545%40Atlassian.JIRA.
[JIRA] (JENKINS-42940) Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet
Title: Message Title Devin Nusbaum updated JENKINS-42940 Jenkins / JENKINS-42940 Timeout step hangs after restart if timeout occurred, but enclosed block did not exit yet Change By: Devin Nusbaum Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179951.1490019942000.14056.1587391020532%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Alan Wong commented on JENKINS-61949 Re: Configuration of action triggers in an Organization folder Our company has been primarily using Organization folders due to ease of administration (rather than either manually creating multi-branch projects or using Job DSL). When an Org folder scans a compatible repository, it automatically creates a multi-branch project based on settings in the Org folder settings. As far as I can tell, these multi-branch projects do not allow further alterations independent from the Org folder. Because the multi-branch projects are not alterable, if action triggers are added to the Org folder, it might need to be setup to allow each repository to determine the values (otherwise, every multi-branch project will have the same values). I am actually using this method right now to keep everything inside the same repository, it is just targeting the /develop branch for now, but it will be updated to /master at some point. But I am only using this for deletion, not creation. I can definitely see that creation would pose a huge issue with race conditions. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscrib
[JIRA] (JENKINS-61976) OAuth2 Active Directory Access token does not work with Rest API
Title: Message Title Matthew Gallagher created an issue Jenkins / JENKINS-61976 OAuth2 Active Directory Access token does not work with Rest API Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2020-04-20 12:56 Environment: Jenkins ver. 2.187 Priority: Minor Reporter: Matthew Gallagher I currently use the Rest API's to access jobs and other information on Jenkins. However, I would like to use Active Directory to secure the Jenkins box. The only way to access the API with AD turned on is through an API token, but the only way I can find to generate this is either through the website or with the API if I already have a token. I can retrieve the OAuth2 credentials including the Access Token, but this does not appear to work with the API. Is there a way to allow this Access Token to generate an API key for the user? Add Comment
[JIRA] (JENKINS-61594) Getting exception when running Micro Focus Plugin for Performance Center Git Integration
Title: Message Title Chris Simon commented on JENKINS-61594 Re: Getting exception when running Micro Focus Plugin for Performance Center Git Integration Hi Daniel, Thank you for your response. We actually started having an environment issue with our LRE Server as well, so once that is resolved I will try the steps you sent and provide an update. Thanks again Chris Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205291.1584650208000.14048.1587387240178%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title
Karl Wirth commented on JENKINS-61943
Re: Jenkins2, P4 Plugin: Error must create client ' to access local files
Hi David Rodriguez, Thanks. The SCM class not longer hard codes all that information. In later versions of the plugin everything is built on the fly. So instead of specifying P4PORT and P4USER you pull in the Jenkins credential that encapsulates P4PORT, P4USER and P4PASSWD:
p4-userpass
P4CLIENT is also dynamically built based on 'name':
jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}
For example if your node is WIN10, your job is mybuild and it runs on executor (Jenkins build thread) 1 the P4CLIENT (variable P4_CLIENT) would be:
jenkins-WIN10-mybuild-1
If you knew the job only ever runs on one node you could hard code the client name in the job definition to be 'ci-admin-ui-4.2'. As for the error its occurring after P4Jenkins has finished and after the command "/data/jenkins_home/tools/apache-maven-3.6.3/bin/mvn -s " has executed. Also P4Jenkins doesnt use the 'p4' binary it uses P4Java that is dynamically sent to the slave as teh job executes:
ha:4Lo+a7u/lzaTkq1HGH3U8JSMfSgah36g77z15FvpSvDYYB+LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEuhYV5Rf55ZekOlc7RKnPKH7IxMBQUcQgBdWQnJ9XnJ+TqucMoUEKGSCAEaSwAACsNFCqYA==[ERROR] Failed to execute goal com.mycom:mycom-build-info-plugin:1.0.14:create (vernum) on project admin.ui: Unable to fetch p4 head version for path/data/jenkins_home/workspace/admin-ui-4.2: P4 process `/bin/sh -c p4 -d /data/jenkins_home/workspace/admin-ui-4.2 changes -m1 ...` returned error code;rc;1;Error message;... - must create client 'ip-10-21-2-84' to access local files. -> [Help 1]
Note that it's running '/bin/sh -c p4'. So if this is not Maven then it is another script or job that is being executed by the Jenkins job. The problem is that the P4CLIENT being built on the fly is not being passed to the environment that the job is executing under which is why I think it needs to be passed or picked up explicitly. For example if it's bash try using 'export P4CLIENT=P4_CLIENT'. For example below is the output when I run a shell script from the job that displaye P4CLIENT and P4_CLIENT: Note that P4CLIENT is not set but P4_CLIENT is.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Attachment: image-2020-04-20-13-40-22-145.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14036.1587386460169%40Atlassian.JIRA.
[JIRA] (JENKINS-61970) Download metadata failed for timeout in jenkins master pod, then JVM is terminating
Title: Message Title gao yanyu edited a comment on JENKINS-61970 Re: Download metadata failed for timeout in jenkins master pod, then JVM is terminating How to install jenkins offline with k8s, what configuration need I pay attention to? I want to know this situation, because not any time I can access to the Internet. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205859.1587377475000.14034.1587383700176%40Atlassian.JIRA.
[JIRA] (JENKINS-61970) Download metadata failed for timeout in jenkins master pod, then JVM is terminating
Title: Message Title gao yanyu commented on JENKINS-61970 Re: Download metadata failed for timeout in jenkins master pod, then JVM is terminating How to install jenkins offline with k8s, what configuration need I pay attention to? I want to know this situation, because not any time I can access to Internet. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205859.1587377475000.14032.1587383700145%40Atlassian.JIRA.
[JIRA] (JENKINS-61970) Download metadata failed for timeout in jenkins master pod, then JVM is terminating
Title: Message Title
gao yanyu updated an issue
Jenkins / JENKINS-61970
Download metadata failed for timeout in jenkins master pod, then JVM is terminating
Change By:
gao yanyu
when I install jenkins by kubernetes, jenkins container will download metadata and check updates server, what does these two steps do specifically? and how can I deal with the result of JVM terminated, because of timeout with updates server.{code:java}// EnvVars.masterEnvVars.get("JENKINS_HOME") 2020-04-20 09 08 : 47:10.776+ [id=1] INFO org.eclipse.jetty.util.log.Log#initialized: Logging initialized @466ms to org.eclipse.jetty.util.log.JavaUtilLog2020-04-20 08:47:10.913+ [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file2020-04-20 08:47:12.326+ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath2020-04-20 08:47:12.390+ [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-9.4.z-SNAPSHOT; built: 2019-05-02T00:04:53.875Z; git: e1bc35120a6617ee3df052294e433f3a25ce7097; jvm 1.8.0_242-b082020-04-20 08:47:12.724+ [id=1] INFO o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet2020-04-20 08:47:12.776+ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node02020-04-20 08:47:12.777+ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults2020-04-20 08:47:12.780+ [id=1] INFO o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 66ms2020-04-20 08:47:13.274+ [id=1] INFO hudson.WebAppMain#contextInitialized: Jenkins home directory: /var/jenkins_home found at: EnvVars.masterEnvVars.get("JENKINS_HOME")2020-04-20 08:47:13.437+ [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started w.@2a2da905{Jenkins v2.204.5,/,file:///var/jenkins_home/war/,AVAILABLE}{/var/jenkins_home/war}2020-04-20 08:47:13.455+ [id=1] INFO o.e.j.server.AbstractConnector#doStart: Started ServerConnector@533bda92{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}2020-04-20 08:47:13.456+ [id=1] INFO org.eclipse.jetty.server.Server#doStart: Started @3145ms2020-04-20 08:47:13.460+ [id=20] INFO winstone.Logger#logInternal: Winstone Servlet Engine v4.0 running: controlPort=disabled2020-04-20 08:47:15.232+ [id=25] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization2020-04-20 08:47:15.443+ [id=26] INFO hudson.PluginManager#considerDetachedPlugin: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/command-launcher.jpi2020-04-20 08:47:15.457+ [id=26] INFO hudson.PluginManager#considerDetachedPlugin: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/jdk-tool.jpi2020-04-20 08:47: 18 .072+ [id=26] INFO jenkins.InitReactorRunner$1#onAttained : 31 Listed all plugins2020-04-20 08:47:25 . 717 255 + [id=25] INFO jenkins.InitReactorRunner$1#onAttained: Loaded Prepared all jobs2020 plugins2020 -04-20 09 08 : 18 47 : 31 25 . 717 284 + [i
[JIRA] (JENKINS-61970) Download metadata failed for timeout in jenkins master pod, then JVM is terminating
Title: Message Title gao yanyu updated an issue Jenkins / JENKINS-61970 Download metadata failed for timeout in jenkins master pod, then JVM is terminating Change By: gao yanyu Issue Type: Story Bug Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205859.1587377475000.14028.1587382980174%40Atlassian.JIRA.
[JIRA] (JENKINS-61975) Powershell command was not found on a different OS slave machine
Title: Message Title Shintaro Tanikawa created an issue Jenkins / JENKINS-61975 Powershell command was not found on a different OS slave machine Issue Type: Bug Assignee: Unassigned Components: powershell-plugin Created: 2020-04-20 11:26 Environment: # Master Slave - OS: Windows10 - Jenkins: org.jenkins-ci.main:jenkins-war:2.222.1 - Powershell plugin: 1.4 # Slave - OS: macOS Catalina - pwsh: PowerShell 7.0.0 - PATH: /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin Labels: powershell slave pwsh Priority: Major Reporter: Shintaro Tanikawa When I tried to use powershell-plugin on each slave machines(Win and Mac) from Win master machine, just MacOS slave machine had an error because no such found `pwsh` command. Here's the error log details. [test] $ pwsh -NonInteractive -File /var/folders/7s/624v46091sdgcf0b1qt98v6hz4r8lc/T/jenkins7665436840857556803.ps1 FATAL: コマンドの実行に失敗しました java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to mac at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.rem
[JIRA] (JENKINS-61974) Test Results Aggregator - Special character in Job name
Title: Message Title SON T DANG created an issue Jenkins / JENKINS-61974 Test Results Aggregator - Special character in Job name Issue Type: Improvement Assignee: Socrates Sidereas Attachments: Kazam_screenshot_1.png Components: test-results-aggregator-plugin Created: 2020-04-20 11:25 Environment: Jenkins 2.231, Test Results Aggregator 1.0.7 Priority: Minor Reporter: SON T DANG **If a job name contains special characters, must specify job name with characters in UTF-8. Otherwise, it produces "Job Not found" For example, if job's name is "Some Test", I must specify "Some%20Test" Need an improvement to avoid requiring filling in special characters in UTF-8 Add Comment
[JIRA] (JENKINS-55426) Using "for in" loop for generating tasks for "parallel" execution, causes all tasks to have last value from iterated collection
Title: Message Title
Sergei S edited a comment on JENKINS-55426
Re: Using "for in" loop for generating tasks for "parallel" execution, causes all tasks to have last value from iterated collection
I catched similar bug with ".each" loop inside parallel stages.Jenkins 2.222 (tested on 2.232 too) , pipeline groovy plugin 2.80 {code:java}def deploymentStages = [:]configGlobal = ["stage-a":["childMap":["key1":"val-1-stage-A", "key2":"val-2-stage-A", "childList":["child-list-value-stage-A"]]], "stage-b":["childMap":["key1":"val-1-stage-B", "key2":"val-2-stage-B", "childList":["child-list-value-stage-B"pipeline {agent anystages {stage('Parent') {steps {script { configGlobal.each { item -> deploymentStages["${item.key}"] = { stage("${item.key}") { config = item.value.childMap newList = [config.key1, config.key2] echo "before loop" echo newList.toString() config.childList.each{ value -> newList.add(value) } echo "after loop" echo newList.toString() } } } parallel deploymentStages}}}}}{code} Output: !image-2020-04-20-14-01-42-072.png!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are sub
[JIRA] (JENKINS-61972) Time is wrongly displayed on running Jobs
Title: Message Title Dag Wieers updated an issue Jenkins / JENKINS-61972 Time is wrongly displayed on running Jobs Change By: Dag Wieers Comment: I recorded a small video with the issue happening when reloading the page.[^Screencast from 20-04-20 131437.webm] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205861.1587378754000.14019.1587381600070%40Atlassian.JIRA.
[JIRA] (JENKINS-61972) Time is wrongly displayed on running Jobs
Title: Message Title Dag Wieers updated an issue Jenkins / JENKINS-61972 Time is wrongly displayed on running Jobs Change By: Dag Wieers Attachment: Screencast from 20-04-20 131437.webm Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205861.1587378754000.14015.1587381540193%40Atlassian.JIRA.
[JIRA] (JENKINS-61972) Time is wrongly displayed on running Jobs
Title: Message Title Dag Wieers updated an issue Jenkins / JENKINS-61972 Time is wrongly displayed on running Jobs Change By: Dag Wieers Attachment: Screencast from 20-04-20 131437.webm Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205861.1587378754000.14017.1587381540287%40Atlassian.JIRA.
[JIRA] (JENKINS-61972) Time is wrongly displayed on running Jobs
Title: Message Title Dag Wieers updated an issue Jenkins / JENKINS-61972 Time is wrongly displayed on running Jobs Change By: Dag Wieers Comment: I recorded a small video with the issue happening when reloading the page.[^Screencast from 20-04-20 13:14:37.webm] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205861.1587378754000.14016.1587381540270%40Atlassian.JIRA.
[JIRA] (JENKINS-61972) Time is wrongly displayed on running Jobs
Title: Message Title Dag Wieers updated an issue Jenkins / JENKINS-61972 Time is wrongly displayed on running Jobs Change By: Dag Wieers Attachment: Screencast from 20-04-20 131414.webm Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205861.1587378754000.14018.1587381540322%40Atlassian.JIRA.
[JIRA] (JENKINS-61972) Time is wrongly displayed on running Jobs
Title: Message Title Dag Wieers updated an issue Jenkins / JENKINS-61972 Time is wrongly displayed on running Jobs Change By: Dag Wieers Attachment: Screencast from 20-04-20 131414.webm Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205861.1587378754000.14013.1587381480084%40Atlassian.JIRA.
