[JIRA] (JENKINS-49607) ssh-slaves-plugin should report the required java version when none found
Title: Message Title Roman Pickl commented on JENKINS-49607 Re: ssh-slaves-plugin should report the required java version when none found I filed a PR (https://github.com/jenkinsci/ssh-slaves-plugin/pull/83). The Java level necessary in the error message now depends on the Jenkins Version used (Version used for tests defined in jenkins.version of POM.xml). It will return: on jenkins >= JAVA8_MINIMAL_SINCE (=2.54 see JavaProvider.java): java.io.IOException: Could not find any known supported java version (a minimum level of 8 is required) in [java, /usr/bin/java, /usr/java/default/bin/java, /usr/java/latest/bin/java, /usr/local/bin/java, /usr/local/java/bin/java, /home/test/slave/jdk/bin/java], and we also failed to install JDK as a fallback on jenkins < JAVA8_MINIMAL_SINCE (=2.54 see JavaProvider): java.io.IOException: Could not find any known supported java version (a minimum level of 7 is required) in [java, /usr/bin/java, /usr/java/default/bin/java, /usr/java/latest/bin/java, /usr/local/bin/java, /usr/local/java/bin/java, /home/test/slave/jdk/bin/java], and we also failed to install JDK as a fallback During testing I also noted that: Automatically installing the DEFAUL_JDK as defined in SSHLauncher.java does not work anymore and fails with "Oracle now requires Oracle account to download previous versions of JDK. Please specify your Oracle account username/password." docker-fixtures have to be updated (the image fails with 1.4 when installing openssh-server=1:7.5p1-10) 1.6 works. (already covered in #82) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-39028) [RFE] keep build forever - expose for current build and allow in sandbox
Title: Message Title Roman Pickl commented on JENKINS-39028 Re: [RFE] keep build forever - expose for current build and allow in sandbox nice! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Roman Pickl commented on JENKINS-47625 Re: Swarm client 3.6: disableSslVerification has no effect I ran into the same issue with 3.8 today, but it seems to work with 3.13 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-61484) tooltip for long path hinders clicking on file link
Title: Message Title Roman Pickl created an issue Jenkins / JENKINS-61484 tooltip for long path hinders clicking on file link Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-03-15 20:22 Environment: Jenkins ver. 2.204.5 Warnings Next Generation Plugin 8.1.0 Bootstrap 4 API Plugin 4.4.1-10 Popper.js API Plugin 1.16.0-6 DataTables.net API Plugin 1.10.20-14 ECharts API Plugin 4.6.0-8 Analysis Model API Plug-in 8.0.1 windows 10 firefox 61 / chrome 68 Priority: Minor Reporter: Roman Pickl when the detail view table only contains a few entries (e.g. two) and the filepaths are very long, the tooltip covers the links to the srcfile. as a result I can neither click the first entry nor the second one. Add Comment
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl closed an issue as Fixed Jenkins / JENKINS-58177 Leading - in workspace directory names mangled in multibranch pipeline Change By: Roman Pickl Status: Resolved Closed 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.200228.1561442061000.4404.1585757880258%40Atlassian.JIRA.
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title Roman Pickl commented on JENKINS-56255 Re: occasionally builds the branch for a PR also I have the same issue. I have the feeling it is even worse. the started branch builds (with multiple stages/agents) seem to fail as jenkins already cleans up after detecting a 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.197825.1550941413000.9372.1586619660190%40Atlassian.JIRA.
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title Roman Pickl commented on JENKINS-56255 Re: occasionally builds the branch for a PR also Brian J Murrell does the workaround in https://issues.jenkins-ci.org/browse/JENKINS-58442 "fix" this for you? I'm interested, because I've implemented it as well and it looks ok so far. 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.197825.1550941413000.10816.1586866500330%40Atlassian.JIRA.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Roman Pickl commented on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
I used Andreas Ringlstetter's solution: https://issues.jenkins-ci.org/browse/JENKINS-9104?focusedCommentId=360603&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-360603 we solved it like this in a jenkins github multi-branch setup with jenkinsfiles: bat """ mkdir tmp set MSPDBSRV_ENDPOINT= ${BUILD_TAG} set TMP=${Workspace}tmp set TEMP=${Workspace}tmp set TMPDIR=${Workspace}tmp build.bat """
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.139260.1300499644000.14702.1587468841800%40Atlassian.JIRA.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Roman Pickl edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
I used [~ext3h]'s solution:https://issues.jenkins-ci.org/browse/JENKINS-9104?focusedCommentId=360603&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-360603 we solved it like this in a jenkins github multi-branch setup with jenkinsfiles: {code:java} bat """ mkdir tmp set _MSPDBSRV_ENDPOINT_= ${BUILD_TAG} set TMP=${Workspace}\\tmp set TEMP=${Workspace}\\tmp set TMPDIR=${Workspace}\\tmp build.bat """ {code}
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.139260.1300499644000.14795.1587468902158%40Atlassian.JIRA.
[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title Roman Pickl updated JENKINS-60762 Jenkins / JENKINS-60762 pipeline used to wait to schedule task now stops immediately Change By: Roman Pickl Status: Fixed but Unreleased Closed 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.204023.1579003891000.19019.1588091460278%40Atlassian.JIRA.
[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title Roman Pickl updated JENKINS-60762 we cannot reproduce this after some updates. Jenkins / JENKINS-60762 pipeline used to wait to schedule task now stops immediately Change By: Roman Pickl Status: Open Fixed but Unreleased 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 this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion o
[JIRA] (JENKINS-59704) NoSuchMethodError occurs when promoting a build using parametrized trigger
Title: Message Title Roman Pickl commented on JENKINS-59704 Re: NoSuchMethodError occurs when promoting a build using parametrized trigger not the original reporter, but thanks this worked for us. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202405.157054141.9211.1576529521207%40Atlassian.JIRA.
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title Roman Pickl commented on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly I see this (or something related) for all branches. once in a while jenkins throws away everything (maybe after a problem with scanning our local github) and restarts all builds. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196496.1546519053000.1527.1577954760495%40Atlassian.JIRA.
[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title Roman Pickl created an issue Jenkins / JENKINS-60762 pipeline used to wait to schedule task now stops immediately Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2020-01-14 12:11 Environment: Jenkins ver. 2.204.1 Priority: Minor Reporter: Roman Pickl I'm not sure this is a bug, but I want to file it anyway: We have a declarative pipeline where we need to restart one of the nodes and continue in a later stage. So in this node we do bat 'shutdown /s /t 30 & exit 0' The next step uses the same node. Before updating some plugins and or jenkins (I assume the jenkins plugins) it behaved like this: When trying to run the following stage on this node, the node is not connected yet, jenkins is Still waiting to schedule task '' is offline and then after it started and connected it schedules the task and finishes the stage successfully. after the update it immediately fails with: was marked offline: Connection was broken: java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179) at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795) at jenkins.util.ContextResettingExecutorService$1.run(Conte
[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title
Roman Pickl updated an issue
Jenkins / JENKINS-60762
pipeline used to wait to schedule task now stops immediately
Change By:
Roman Pickl
I'm not sure this is a bug, but I want to file it anyway:We have a declarative pipeline where we need to restart one of the nodes and continue in a later stage.So in this node we do {noformat} bat 'shutdown /s /t 30 & exit 0' {noformat} The next step uses the same node.Before updating some plugins and or jenkins (I assume the jenkins plugins) it behaved like this: When trying to run the following stage on this node, the node is not connected yet, jenkins is{noformat}Still waiting to schedule task'' is offline{noformat}and then after it started and connected it schedules the task and finishes the stage successfully.after the update it immediately fails with:{noformat} was marked offline: Connection was broken: java.nio.channels.ClosedChannelExceptionat org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)at java.lang.Thread.run(Unknown Source){noformat} I solved this with adding a sleep to wait for the machine to be online again, but is there a better solution?
Add Comment
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled Ulli Hafner thanks for pointing me to this ticket in gitter. I tried to whitelist it, but it did not work for me. I also tried io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor (note the $) but this did not work either. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled Thanks for the update. Not sure whether you address Mark or me but I guess we experience the same problem. I'm nt sure what you are implying though. do you mean that everything should work out of the box (with master-agent security enabled) or it should only work if the command is whitelisted? So I updated the plugin to the latest version 5.0.0 (from 4.0.0) and activated master-agent security again. i'll come back to you with the results. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.13163.1559027700653%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl edited a comment on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled Thanks for the update.Not sure whether you address Mark or me but I guess we experience the same problem. I'm nt not sure what you are implying though. do you mean that everything should work out of the box (with master-agent security enabled) or it should only work if the command is whitelisted?So I 've updated the plugin to the latest version 5.0.0 (from 4.0.0) and activated master-agent security again. i'll come back to you with the results. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.13174.1559027700842%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled I'm still running into 09:49:28 [Clang-Tidy] [-ERROR-] Can't copy some affected workspace files to Jenkins build folder: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.13314.1559031000352%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled we are using the https://wiki.jenkins.io/display/JENKINS/Swarm+Plugin to run slaves and run some builds inside docker on a separate machine then the one the jenkins master runs on (windows 7) security settings Security is enabled Access Control works via LDAP Logged-in users can do everything, anonymous read access is permitted tcp port for jnlp agents is set to Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.13325.1559031960237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled i thought the issue is that copying files from the slave to master does not work (as mentioned in https://issues.jenkins-ci.org/browse/JENKINS-56007?focusedCommentId=363080&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-363080) , to me it seems as if the test does the opposite (copying a file to the slave). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.13334.1559032260330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl edited a comment on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled i thought the issue is that copying files from the slave to master does not work (as mentioned in https://issues.jenkins-ci.org/browse/JENKINS-56007?focusedCommentId=363080&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-363080) , to me it seems as if the test does the opposite (copying a file to the slave) , but of course I'm lacking context . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.13364.1559033220230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled we are using Jenkins ver. 2.164.3 (latest lts release) \secrets\filepath-filters.d\30-default.conf exists and has a timestamp from the last restart of jenkins yesterday (i think) i have added a warningsng.conf file in \secrets\whitelisted-callables.d with one line: io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.14231.1559069460249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled Great! Thanks for the update. Is whitelisting still needed after this change? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.16801.1559240880248%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled Ok thanks. No it did not. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.16823.1559244480259%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title
Roman Pickl created an issue
Jenkins / JENKINS-58177
Leading - in workspace directory names mangled in multibranch pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
branch-api-plugin
Created:
2019-06-25 05:54
Environment:
jenkins-war:2.176.1 branch-api-plugin: 2.5.2
Priority:
Minor
Reporter:
Roman Pickl
Apparently, some of our workspaces for specific branch names are mangled in a way that the directories start with a "-" (or multiple!). This would require some special handling in scripts and we would like to avoid that. There also have been some discussions about this special case in the now obsolete implementation in JENKINS-38706: https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=272733&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272733 https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=324422&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-324422 https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=345815&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-345815 https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=348257&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-348257 I had a look and it seems to happen here: https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/WorkspaceLocatorImpl.java#L193 It can be tested with this small java program:
import org.apache.commons.lang3.StringUtils;
public class Test {
public static voi
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title
Roman Pickl updated an issue
Jenkins / JENKINS-58177
Leading - in workspace directory names mangled in multibranch pipeline
Change By:
Roman Pickl
Apparently, some of our workspaces for specific branch names are mangled in a way that the directories start with a "-" (or multiple!). This would require some special handling in scripts and we would like to avoid that. There also have been some discussions about this special case in the now obsolete implementation in JENKINS-38706:https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=272733&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272733https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=324422&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-324422https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=345815&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-345815https://issues.jenkins-ci.org/browse/JENKINS-38706?focusedCommentId=348257&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-348257I had a look and it seems to happen here:[https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/WorkspaceLocatorImpl.java#L193] It can be tested with this small java program: {code:java}import org.apache.commons.lang3.StringUtils;public class Test {public static void main(String args[]) {int MAX_LENGTH=32;String fullName= "JIRA-1054_rename_1234_to_abcdef_try2";String mnemonic = mnemonicOf(fullName);String path = StringUtils.right(mnemonic, MAX_LENGTH); System.out.println(path);}private static String mnemonicOf(String name) {// Do not need the complexity of NameMangler here, since we uniquify as needed.return name.replaceAll("(%[0-9A-F]{2}|[^a-zA-Z0-9-_.])+", "_");}}{code} For the moment i have increased MAX_LENGTH on our jenkins, but I would really love to see this fixed in Jenkins.
Add Comment
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl assigned an issue to Jesse Glick Jenkins / JENKINS-58177 Leading - in workspace directory names mangled in multibranch pipeline Change By: Roman Pickl Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.7826.1561442160183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl commented on JENKINS-58177 Re: Leading - in workspace directory names mangled in multibranch pipeline Jesse Glick maybe you could have a look at it or share your opinion, as you have worked on JENKINS-2111. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.7828.1561442280168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl assigned an issue to Roman Pickl Jenkins / JENKINS-58177 Leading - in workspace directory names mangled in multibranch pipeline Change By: Roman Pickl Assignee: Roman Pickl Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.9167.1561539541048%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl commented on JENKINS-58177 Re: Leading - in workspace directory names mangled in multibranch pipeline thanks for the fast feedback. find a pull request here https://github.com/jenkinsci/branch-api-plugin/pull/161 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.9275.1561549560177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl assigned an issue to Jesse Glick Jenkins / JENKINS-58177 Leading - in workspace directory names mangled in multibranch pipeline Change By: Roman Pickl Assignee: Roman Pickl Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.9277.1561549560202%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl stopped work on JENKINS-58177 Change By: Roman Pickl Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.9455.1561557062532%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl assigned an issue to Jesse Glick Jenkins / JENKINS-58177 Leading - in workspace directory names mangled in multibranch pipeline Change By: Roman Pickl Assignee: Roman Pickl Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.9457.1561557062981%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl assigned an issue to Roman Pickl Jenkins / JENKINS-58177 Leading - in workspace directory names mangled in multibranch pipeline Change By: Roman Pickl Assignee: Jesse Glick Roman Pickl Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.9449.1561557062385%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58177) Leading - in workspace directory names mangled in multibranch pipeline
Title: Message Title Roman Pickl started work on JENKINS-58177 Change By: Roman Pickl Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200228.1561442061000.9453.1561557062458%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
