[JIRA] (JENKINS-59784) Unable to view a pdf file from jenkins workspace
Title: Message Title
Hussain Khan commented on JENKINS-59784
Re: Unable to view a pdf file from jenkins workspace
Thanks Daniel! I checked the browser's console and it shows the following error: "Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-C7vpsE1KLI7RuUgCprJTQZin6dWK+ccynbOx+OqjVow='), or a nonce ('nonce-...') is required to enable inline execution." So it does seems to be a CSP problem. When you said alternative you meant that we can relax the rule set right with the help fo this doc - https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy
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.202514.1571129142000.8482.1571204220164%40Atlassian.JIRA.
[JIRA] (JENKINS-24138) Archived file names can change when moved from slave to master
Title: Message Title Kim Abbott commented on JENKINS-24138 Re: Archived file names can change when moved from slave to master Thank you, looks promising, will take a look. Did you add this via global properties or via EnvInject API Plugin? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156612.1407335439000.8477.1571202420229%40Atlassian.JIRA.
[JIRA] (JENKINS-59798) Support notarizing as a build step
Title: Message Title Kim Abbott created an issue Jenkins / JENKINS-59798 Support notarizing as a build step Issue Type: New Feature Assignee: Unassigned Components: xcode-plugin Created: 2019-10-16 04:55 Priority: Major Reporter: Kim Abbott Due to app requirements for Catalina MacOS, all newly built apps must be notarized. It would be great to incorporate the submission of an app for notarization (and retrieving and subsequent attaching the ticket to the app) as a build step using this plugin. Add Comment
[JIRA] (JENKINS-23349) Item names containing an emoji are not accessible
Title: Message Title Bruno Meneguello commented on JENKINS-23349 Re: Item names containing an emoji are not accessible I've created and linked a ticket detailing the problem 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.155495.1402054331000.8467.1571197320331%40Atlassian.JIRA.
[JIRA] (JENKINS-59723) Missing Delay Setting in Performance Signature Plugin
Title: Message Title rachel lee commented on JENKINS-59723 Re: Missing Delay Setting in Performance Signature Plugin Hi Rapheal, Do you have chance to take a look on this issue? Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202439.1570699941000.8465.1571195640101%40Atlassian.JIRA.
[JIRA] (JENKINS-59654) improve SSH connection capabilities- Instance connect
Title: Message Title Raihaan Shouhell updated an issue Jenkins / JENKINS-59654 improve SSH connection capabilities- Instance connect Change By: Raihaan Shouhell Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202344.1570184756000.8463.1571195160269%40Atlassian.JIRA.
[JIRA] (JENKINS-45852) Bitbucket project icons not displaying properly since 2.2.2.
Title: Message Title Michael Lasevich edited a comment on JENKINS-45852 Re: Bitbucket project icons not displaying properly since 2.2.2. FYI - After some digging, i identified the underlying issue and opened JENKINS- 39977 59797 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.184064.1501247779000.8454.1571192400243%40Atlassian.JIRA.
[JIRA] (JENKINS-45852) Bitbucket project icons not displaying properly since 2.2.2.
Title: Message Title Michael Lasevich commented on JENKINS-45852 Re: Bitbucket project icons not displaying properly since 2.2.2. FYI - After some digging, i identified the underlying issue and opened JENKINS-39977 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.184064.1501247779000.8450.1571192340151%40Atlassian.JIRA.
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich created an issue Jenkins / JENKINS-59797 AvatarCache does not support authenticated scm access Issue Type: New Feature Assignee: Unassigned Components: scm-api-plugin Created: 2019-10-16 02:14 Priority: Minor Reporter: Michael Lasevich Not sure if this is a bug, request for feature or just need for education but either way I am hoping you can help... I was troubleshooting a plugin based on scm-api-plugin (bitbucket-branch-source-plugin) and discovered something odd. The plugin uses AvatarCache to manage "Org" images, but that was not working. Upon digging into it, I discovered that since our SCM requires authentication, the image URL requires authentication too. But as far as I can see, AvatarCache does not have any support for getting urls with authentication. So my questions are: Am I seeing this correct? Or am I missing something? Was this intentional or an oversight? I am guessing most SCM repos that are not OSS projects will require authentication, so how can this work for most SCMs? Is the expectation for those plugins that use authenticated access to SCM to not use AvatarCache, but to implement it internally? Or is there another mechanism in scm-api-plugin? Assuming the answer is that each plugin must implement its own avatar handling, are there recommended approaches/patterns for those of us not familiar with Jenkins internals? Thank you so much
[JIRA] (JENKINS-29893) Allow exclusions for git clean
Title: Message Title
Mark Waite edited a comment on JENKINS-29893
Re: Allow exclusions for git clean
I have no plans currently to implement this in the plugin. It is simple to call the {{git clean}} command from Jenkins Pipeline and is not much more difficult to call it from Freestyle jobs. The {{git clean}} command does not require authentication, so does not need the added logic that the git plugin provides for authentication support.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164471.1439300117000.8442.1571188560220%40Atlassian.JIRA.
[JIRA] (JENKINS-29893) Allow exclusions for git clean
Title: Message Title Mark Waite commented on JENKINS-29893 Re: Allow exclusions for git clean I have no plans currently to implement this in the plugin. It is simple to call the git clean command from Jenkins Pipeline and is not much more difficult to call it from Freestyle jobs. 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.164471.1439300117000.8435.1571188440334%40Atlassian.JIRA.
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Petr H edited a comment on JENKINS-54959 Re: Offer a new Unarchive installer which takes Java archive structure into account - automatically installed JDK (when it worked):hudson.model.JDK/JDK8u152/bin/- manually downloaded and locally used binary archive (jdk-8u212-linux-x64.tar.gz in this example):hudson.model.JDK/JDK8/*jdk1.8.0_212*/bin/Although I can set the *Subdirectory of extracted archive* to "jdk1.8.0_212" (for the above example) which sets the java home correctly, I'd like to get the same result as with the automatically installed JDK - e.g. without that additional subdirectory in the filesystem path . 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.195983.1543566344000.8429.1571185440333%40Atlassian.JIRA.
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Petr H edited a comment on JENKINS-54959 Re: Offer a new Unarchive installer which takes Java archive structure into account - automatically installed JDK (when it worked):hudson.model.JDK/JDK8u152/bin/- manually downloaded and locally used binary archive (jdk-8u212-linux-x64.tar.gz in this example):hudson.model.JDK/JDK8/*jdk1.8.0_212*/bin/ Although I can set the *Subdirectory of extracted archive* to "jdk1.8.0_212" (for the above example) which sets the java home correctly, I'd like to get the same result as with the automatically installed JDK - e.g. without that additional subdirectory. 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.195983.1543566344000.8423.1571185380197%40Atlassian.JIRA.
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Petr H commented on JENKINS-54959 Re: Offer a new Unarchive installer which takes Java archive structure into account automatically installed JDK (when it worked): hudson.model.JDK/JDK8u152/bin/ manually downloaded and locally used binary archive (jdk-8u212-linux-x64.tar.gz in this example): hudson.model.JDK/JDK8/jdk1.8.0_212/bin/ Although I can set the Subdirectory of extracted archive to "jdk1.8.0_212" (for the above example) which sets the java home correctly, I'd like to get the same result as with the automatically installed JDK - e.g. without that additional subdirectory. 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.195983.1543566344000.8421.1571185260347%40Atlassian.JIRA.
[JIRA] (JENKINS-29893) Allow exclusions for git clean
Title: Message Title Borja Domínguez commented on JENKINS-29893 Re: Allow exclusions for git clean Any news? I would like to see "Clean before checkout" behaviour to have an option to add an exclude pattern: https://git-scm.com/docs/git-clean Now I'm executing the command myself without using this behaviour as it does not support it. Example: 'git clean -fdx -e MyFolderToExclude' 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.164471.1439300117000.8410.1571183040239%40Atlassian.JIRA.
[JIRA] (JENKINS-51865) Stage locks are created for skipped stages in declarative pipeline
Title: Message Title Falko Modler commented on JENKINS-51865 Re: Stage locks are created for skipped stages in declarative pipeline I created a PR for this: https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/356 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.191345.1528726775000.8398.1571179260456%40Atlassian.JIRA.
[JIRA] (JENKINS-23349) Item names containing an emoji are not accessible
Title: Message Title Alex Earl commented on JENKINS-23349 Re: Item names containing an emoji are not accessible Is it removing the character from URL's as was originally posted in this issue? 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.155495.1402054331000.8388.1571176620277%40Atlassian.JIRA.
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title
Suganya Ravikumar edited a comment on JENKINS-54250
Re: Disable restarting stages in jenkinsfile optionally
We added the check to each stage and marked the build as ABORTED to prevent the build form going GREEN. ``` @NonCPS def call() { script { restartedFromStage = currentBuild.getBuildCauses().any{ cause -> cause._class == 'org.jenkinsci.plugins.pipeline.modeldefinition.causes.RestartDeclarativePipelineCause' }if (restartedFromStage){ error 'Restarting build from a stage is disabled. Please rerun build from start.' currentBuild.result = 'ABORTED' return false }else{ return true }} } ...``` in each stage we check ``` when { _expression_{ return call() }steps { ... ```
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194892.1540468831000.8372.1571176321416%40Atlassian.JIRA.
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title
Suganya Ravikumar edited a comment on JENKINS-54250
Re: Disable restarting stages in jenkinsfile optionally
We added the check to each stage and marked the build as ABORTED to prevent the build form going GREEN. ``` @NonCPSdef call() {script {restartedFromStage = currentBuild.getBuildCauses().any { cause -> cause._class == 'org.jenkinsci.plugins.pipeline.modeldefinition.causes.RestartDeclarativePipelineCause'} if (restartedFromStage) { { error 'Restarting build from a stage is disabled. Please rerun build from start.' currentBuild.result = 'ABORTED' return false } else { { return true } }}... ``` in each stage we check ``` when { _expression_ { { return call() } steps {... ```
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194892.1540468831000.8355.1571176321170%40Atlassian.JIRA.
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title
Suganya Ravikumar commented on JENKINS-54250
Re: Disable restarting stages in jenkinsfile optionally
We added the check to each stage and marked the build as ABORTED to prevent the build form going GREEN. @NonCPS def call() { script { restartedFromStage = currentBuild.getBuildCauses().any { cause -> cause._class == 'org.jenkinsci.plugins.pipeline.modeldefinition.causes.RestartDeclarativePipelineCause' } if (restartedFromStage) { error 'Restarting build from a stage is disabled. Please rerun build from start.' currentBuild.result = 'ABORTED' return false } else { return true } } } ... in each stage we check when { _expression_ { return call() } steps { ...
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194892.1540468831000.8338.1571176260433%40Atlassian.JIRA.
[JIRA] (JENKINS-59796) Item names with U+00E7 (Cedilla) raise errors
Title: Message Title Daniel Beck commented on JENKINS-59796 Re: Item names with U+00E7 (Cedilla) raise errors Is this just JENKINS-59406? Could you test with 2.196? 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.202526.1571173911000.8335.1571175000230%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59794 Using a period as the branch name in .gitModules does not work. Change By: Mark Waite Labels: submodules 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.202524.1571167644000.8331.1571174400607%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59794 Using a period as the branch name in .gitModules does not work. Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202524.1571167644000.8333.1571174400707%40Atlassian.JIRA.
[JIRA] (JENKINS-59796) Item names with U+00E7 (Cedilla) raise errors
Title: Message Title Bruno Meneguello created an issue Jenkins / JENKINS-59796 Item names with U+00E7 (Cedilla) raise errors Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-15 21:11 Labels: url-encoding views jobs Priority: Critical Reporter: Bruno Meneguello Version 2.190.1 How to reproduce: Create a view or job having "ç" (not in display name) Try to build a pipeline or open API view Workaround: Rename job/view to remove cedilla character (it's ok to have cedilla in display name) Stack trace: With a job named /Test/Çedilla: WARNING h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: job.shortUrl in /job/Test/. Reason: java.lang.reflect.InvocationTargetException java.lang.NullPointerException Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor363.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at
[JIRA] (JENKINS-59795) Option to skip any builds after indexing multibranch pipeline.
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-59795 Option to skip any builds after indexing multibranch pipeline. Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-10-15 21:08 Priority: Major Reporter: Joel Brown Using a multibranch pipeline, we want the scan to pick up new branches BUT to skip the check for changes and the possible build. The jobs are user initiated only. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-23349) Item names containing an emoji are not accessible
Title: Message Title Bruno Meneguello commented on JENKINS-23349 Re: Item names containing an emoji are not accessible I've upgraded jenkins to latest LTS today and noticed problem with "ç" (cedilla) char U+00E7. 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.155495.1402054331000.8320.1571173440333%40Atlassian.JIRA.
[JIRA] (JENKINS-56567) Build fails when reading more than 125 environment credentials at the same time
Title: Message Title
Pete Moore commented on JENKINS-56567
Re: Build fails when reading more than 125 environment credentials at the same time
Thank you Devin your workaround is a lot cleaner than my workaround which was this.
parallel(
group_0 : {
parallel(
item0 : { sh "echo this is item 0" },
item1 : { sh "echo this is item 1" },
...
)
},
group_1 : {
parallel(
item200 : { sh "echo this is item 200" },
item201 : { sh "echo this is item 201" },
...
)
},
)
Is the limit in Jenkins or groovy? If the limit is in Jenkins can we look forward to a fix? New users (Ive talked to) like me are pretty stunned by such a small limit.
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.198182.1552584474000.8316.1571172060273%40Atlassian.JIRA.
[JIRA] (JENKINS-59779) Warnings Trend Graph Not Appearing For Builds
Title: Message Title Alex C commented on JENKINS-59779 Re: Warnings Trend Graph Not Appearing For Builds By build ID you mean the Jenkins BUILD_ID correct? BUILD_ID is most certainly unique for each build, although each build may have the same DisplayName in my case. I suppose I could just make sure each BUILD_DISPLAY_NAME is different. 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.202506.157106850.8313.1571171580232%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Jon Roberts created an issue Jenkins / JENKINS-59794 Using a period as the branch name in .gitModules does not work. Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-10-15 19:27 Priority: Minor Reporter: Jon Roberts When you specify the branch name as a '.' (period) in .gitModules you should be able to use the --remote option to update submodules to the head the branch that matches the parent branch. When doing this in Jenkins we get the following error: hudson.plugins.git.GitException: Command "/usr/bin/git submodule update --init --recursive --remote curavi-common" returned status code 1: stdout: stderr: Cloning into 'curavi-common'... fatal: Needed a single revision Unable to find current origin/. revision in submodule path 'curavi-common' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1202) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at
[JIRA] (JENKINS-56567) Build fails when reading more than 125 environment credentials at the same time
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-56567
Re: Build fails when reading more than 125 environment credentials at the same time
[~pete312] This limitation only affects map and list literals. In scripted Pipeline, you should be able to adapt your script as a workaround. Instead of creating a parallel step with branches inline like this:{code:java}parallel(branch1: { ... }, branch2: { ... }){code}Create the branches separately like this:{code:java}Map branches = [ : ]branches['branch1'] = { ... }branches['branch2'] = { ... }parallel(branches){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198182.1552584474000.8307.1571164200287%40Atlassian.JIRA.
[JIRA] (JENKINS-56567) Build fails when reading more than 125 environment credentials at the same time
Title: Message Title
Devin Nusbaum commented on JENKINS-56567
Re: Build fails when reading more than 125 environment credentials at the same time
Pete Moore This limitation only affects map and list literals. In scripted Pipeline, you should be able to adapt your script as a workaround. Instead of creating a parallel step with branches inline like this:
parallel(branch1: { ... }, branch2: { ... })
Create the branches separately like this:
Map branches = []
branches['branch1'] = { ... }
branches['branch2'] = { ... }
parallel(branches)
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.198182.1552584474000.8302.1571164140219%40Atlassian.JIRA.
[JIRA] (JENKINS-59793) Possible thread leak 'QueueSubTaskMetrics' in metrics
Title: Message Title Daniel Beck commented on JENKINS-59793 Re: Possible thread leak 'QueueSubTaskMetrics' in metrics Interesting, that might have been a source of too many threads on ci.jenkins.io recently as well. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202523.1571157685000.8299.1571163360297%40Atlassian.JIRA.
[JIRA] (JENKINS-56567) Build fails when reading more than 125 environment credentials at the same time
Title: Message Title
Pete Moore edited a comment on JENKINS-56567
Re: Build fails when reading more than 125 environment credentials at the same time
In case there is any problems recreating this it's present in scripted pipelines. This code will produce test.txt to reproduce the error{{ }}{{ bash-4.2$ python << EOF | tee test.txt}}{{print('node {\n parallel(\n')}}{{for i in range(200):}}{{ print(' item%s : \{ sh "echo this is item %s" },' % (i,i))}}{{print(' )\n}\n')}}{{EOF}}copy paste the output from that to jenkins window or run load "test.txt". and you get this errorWorkflowScript: 4: Map expressions can only contain up to 125 entries @ line 4, column 12. item0 : \{ sh "echo this is item 0" },
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.198182.1552584474000.8295.1571163180845%40Atlassian.JIRA.
[JIRA] (JENKINS-56567) Build fails when reading more than 125 environment credentials at the same time
Title: Message Title
Pete Moore edited a comment on JENKINS-56567
Re: Build fails when reading more than 125 environment credentials at the same time
In case there is any problems recreating this it's present in scripted pipelines. This code will produce test.txt to reproduce the error {{}}{{ bash-4.2$ python << EOF | tee test.txt }} {{ print('node {\n parallel(\n') }} {{ for i in range(200): }} {{ print(' item%s : \{ sh "echo this is item %s" },' % (i,i)) }} {{ print(' )\n}\n') }} {{ EOF }} copy paste the output from that to jenkins window or run load "test.txt". and you get this errorWorkflowScript: 4: Map expressions can only contain up to 125 entries @ line 4, column 12. item0 : \{ sh "echo this is item 0" },
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.198182.1552584474000.8290.1571163180416%40Atlassian.JIRA.
[JIRA] (JENKINS-56567) Build fails when reading more than 125 environment credentials at the same time
Title: Message Title Pete Moore commented on JENKINS-56567 Re: Build fails when reading more than 125 environment credentials at the same time I should add that this is limiting on large projects where you want to make a lot of jobs go parallel. 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.198182.1552584474000.8285.1571162880242%40Atlassian.JIRA.
[JIRA] (JENKINS-56567) Build fails when reading more than 125 environment credentials at the same time
Title: Message Title
Pete Moore commented on JENKINS-56567
Re: Build fails when reading more than 125 environment credentials at the same time
In case there is any problems recreating this it's present in scripted pipelines. This code will produce test.txt to reproduce the error bash-4.2$ python << EOF | tee test.txt print('node {\n parallel(\n') for i in range(200): print(' item%s : \{ sh "echo this is item %s" } ,' % (i,i)) print(' )\n}\n') EOF copy paste the output from that to jenkins window or run load "test.txt". and you get this error WorkflowScript: 4: Map expressions can only contain up to 125 entries @ line 4, column 12. item0 : { sh "echo this is item 0" },
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.198182.1552584474000.8280.1571162760343%40Atlassian.JIRA.
[JIRA] (JENKINS-59793) Possible thread leak 'QueueSubTaskMetrics' in metrics
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-59793 Possible thread leak 'QueueSubTaskMetrics' in metrics Issue Type: Bug Assignee: Unassigned Components: metrics-plugin Created: 2019-10-15 16:41 Environment: Metrics 4.0.2.5 Labels: plugin Priority: Major Reporter: Ramon Leon In one large instance we can see 3000 threads with this shape: "QueueSubTaskMetrics [#11342]" #5508106 daemon prio=5 os_prio=0 tid=0x7efcf085a800 nid=0x52c7 in Object.wait() [0x7efbccb32000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:75) - locked <0x000512c01d10> (a hudson.model.queue.FutureImpl) at jenkins.metrics.impl.JenkinsMetricProviderImpl.lambda$asSupplier$3(JenkinsMetricProviderImpl.java:1142) at jenkins.metrics.impl.JenkinsMetricProviderImpl$$Lambda$388/1851215464.get(Unknown Source) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Locked ownable synchronizers: - <0x0004dc401fb0> (a java.util.concurrent.ThreadPoolExecutor$Worker)
[JIRA] (JENKINS-59792) Update README for AppCenter
Title: Message Title Abel Berhane commented on JENKINS-59792 Re: Update README for AppCenter https://github.com/abelberhane/appcenter-plugin/blob/master/README.md 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.202522.1571157542000.8266.1571157600652%40Atlassian.JIRA.
[JIRA] (JENKINS-59759) localhost not allowed for jeknins with gitlab-branch-source-plugin
Title: Message Title ebundy ebundy commented on JENKINS-59759 Re: localhost not allowed for jeknins with gitlab-branch-source-plugin Hello, It works perfectly. I added a small PR on https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/57 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.202482.1570880817000.8268.1571157600760%40Atlassian.JIRA.
[JIRA] (JENKINS-59792) Update README for AppCenter
Title: Message Title Abel Berhane created an issue Jenkins / JENKINS-59792 Update README for AppCenter Issue Type: Improvement Assignee: Abel Berhane Components: appcenter-plugin Created: 2019-10-15 16:39 Labels: hacktoberfest Priority: Minor Reporter: Abel Berhane Updated ReadMe in a few areas: 1) Removed the release notes from upcoming functionality since its been released 2) Added a breakdown of what the Plugin can currently do 3) Added a breakdown of what the Plugin is expecting you to fill out and some helpful hints. Add Comment
[JIRA] (JENKINS-41187) Stage "when" should have "stage" condition
Title: Message Title Brian Nacey commented on JENKINS-41187 Re: Stage "when" should have "stage" condition Has there need any progress on this? I find myself in need of a solution to know if an earlier stage has been built. 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.177948.148477995.8241.1571157540742%40Atlassian.JIRA.
[JIRA] (JENKINS-41187) Stage "when" should have "stage" condition
Title: Message Title Brian Nacey edited a comment on JENKINS-41187 Re: Stage "when" should have "stage" condition Has there need been any progress on this? I find myself in need of a solution to know if an earlier stage has been built. 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.177948.148477995.8254.1571157541165%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Mathieu Delrocq updated an issue
Jenkins / JENKINS-59790
Container cannot connect to node because it doesn't exist
Change By:
Mathieu Delrocq
We recently updated our version of Jenkins to 2.176.3. And now a connection error with docker-agent randomly block the queue of jobs :{code:java}Refusing headers from remote: Unknown client name: docker-00026wu6nor9w{code}The docker container is ready and try to connect to the Jenkins master but the node doesn't exist yet.I saw in the code of docker-plugin that the container is created and started before the Jenkins node. While the connection method is JNLP, the commands to download and run the remoting.jar are executed at the start of the container. But at this moment, the node wasn't added to Jenkins master.Have you ever encountered this error ? Is there a solution ? If not I suggest Is it possible to modify provision methods to and create the Jenkins node before instanciate the container to fix this issue . ? Jenkins version : 2.176.3docker-plugin version : 1.1.7
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Mathieu Delrocq updated an issue
Jenkins / JENKINS-59790
Container cannot connect to node because it doesn't exist
Change By:
Mathieu Delrocq
We recently updated our version of Jenkins to 2.176.3. And now a connection error with docker-agent randomly block the queue of jobs :{code:java}Refusing headers from remote: Unknown client name: docker-00026wu6nor9w{code}The docker container is ready and try to connect to the Jenkins master but the node doesn't exist yet.I saw in the code of docker-plugin that the container is created and started before the Jenkins node. While the connection method is JNLP, the commands to download and run the remoting.jar are executed at the start of the container. But at this moment, the node wasn't added to Jenkins master.Have you ever encountered this error ? Is there a solution ?Is it possible to modify provision methods and create the Jenkins node before instanciate the container to fix this issue?Jenkins version : 2.176.3docker-plugin version : 1.1.7
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Mathieu Delrocq updated an issue
Jenkins / JENKINS-59790
Container cannot connect to node because it doesn't exist
Change By:
Mathieu Delrocq
We recently updated our version of Jenkins to 2.176.3. And now a connection error with docker-agent randomly block the queue of jobs :{code:java}Refusing headers from remote: Unknown client name: docker-00026wu6nor9w{code}The docker container is ready and try to connect to the Jenkins master but the node doesn't exist yet.I saw in the code of docker-plugin that the container is created and started before the Jenkins node. While the connection method is JNLP, the commands to download and run the remoting.jar are executed at the start of the container. But at this moment, the node wasn't added to Jenkins master. Have you ever encountered this error ? Is there a solution ?If not I suggest to modify provision methods to create the Jenkins node before instanciate the container to fix this issue.Jenkins version : 2.176.3docker-plugin version : 1.1.7
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Mathieu Delrocq updated an issue
Jenkins / JENKINS-59790
Container cannot connect to node because it doesn't exist
Change By:
Mathieu Delrocq
We recently updated our version of Jenkins to 2 . Now 176.3. And now a connection error with docker-agent randomly block the queue of jobs :{code:java}Refusing headers from remote: Unknown client name: docker-00026wu6nor9w{code}The docker container is ready and try to connect to the Jenkins master but the node doesn't exist yet.I saw in the code of docker-plugin that the container is created and started before the Jenkins node. While the connection method is JNLP, the commands to download and run the remoting.jar are executed at the start of the container. But at this moment, the node wasn't added to Jenkins master. I suggest to modify provision methods to create the Jenkins node before instanciate the container to fix this issue.Jenkins version : 2.176.3docker-plugin version : 1.1.7
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58490) Support symbol file upload
Title: Message Title Alexander Siemer-Schmetzke commented on JENKINS-58490 Re: Support symbol file upload Hey Mez Pahlan, found some minutes to work on it. Due to limited time, I didn't refactor much and mainly kept it as it is. Looking forward to your comments, PR is open. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200628.1563184462000.8219.1571156880220%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Mathieu Delrocq updated an issue
Jenkins / JENKINS-59790
Container cannot connect to node because it doesn't exist
Change By:
Mathieu Delrocq
We recently updated our version of Jenkins. Now a connection error with docker-agent block the queue of jobs :{code:java}Refusing headers from remote: Unknown client name: docker-00026wu6nor9w{code}The docker container is ready and try to connect to the Jenkins master but the node doesn't exist yet.I saw in the code of docker-plugin that the container is created before the Jenkins node.I purpose suggest to modify provision methods to create the Jenkins node before instanciate the container to fix this issue.Jenkins version : 2.176.3docker-plugin version : 1.1.7
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
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Mathieu Delrocq updated an issue
Jenkins / JENKINS-59790
Container cannot connect to node because it doesn't exist
Change By:
Mathieu Delrocq
We recently updated our version of Jenkins. Now a connection error with docker-agent block the queue of jobs :{code:java}Refusing headers from remote: Unknown client name: docker-00026wu6nor9w{code}The docker container is ready and try to connect to the Jenkins master but the node doesn't exist yet.I saw in the code of docker-plugin that the container is created before the Jenkins node.I purpose to modify provision methods to create the Jenkins node before instanciate the container to fix this issue. Jenkins version : 2.176.3docker-plugin version : 1.1.7
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
[JIRA] (JENKINS-59779) Warnings Trend Graph Not Appearing For Builds
Title: Message Title Ulli Hafner commented on JENKINS-59779 Re: Warnings Trend Graph Not Appearing For Builds Hmm, I'm not sure what I can do here. I think it is ok to expect that the build ID and the name is unique. 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.202506.157106850.8208.1571155560124%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated JENKINS-59707 Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Status: Open Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-2.12 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.202408.1570569525000.8206.1571155500312%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier commented on JENKINS-59707 Re: Give more details in the connection success panel I did these improvements. It will be enough for now. 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.202408.1570569525000.8204.1571155440192%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Attachment: Screenshot 2019-10-15 18.01.19.png Attachment: Screenshot 2019-10-15 18.00.37.png Attachment: Screenshot 2019-10-15 18.00.01.png Attachment: Screenshot 2019-10-15 17.59.39.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-59779) Warnings Trend Graph Not Appearing For Builds
Title: Message Title Alex C edited a comment on JENKINS-59779 Re: Warnings Trend Graph Not Appearing For Builds Yes, I do have multiple builds with the same name '3.9.5'. The name '3.9.5' is set thought a script which outputs the version # of my app:currentBuild.displayName = sh(script: 'make ios-version' , returnStdout: true).trim()I see now that when I remove the duplicate builds from build history, the graph appears to show! 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.202506.157106850.8200.1571154420128%40Atlassian.JIRA.
[JIRA] (JENKINS-59784) Unable to view a pdf file from jenkins workspace
Title: Message Title Daniel Beck commented on JENKINS-59784 Re: Unable to view a pdf file from jenkins workspace If it's a CSP problem, your browser's debug/network console should tell you. Note that Jenkins 2.200 has an alternative to CSP for user-generated content (that is not simply disabling it) 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.202514.1571129142000.8187.1571153940156%40Atlassian.JIRA.
[JIRA] (JENKINS-59779) Warnings Trend Graph Not Appearing For Builds
Title: Message Title Alex C commented on JENKINS-59779 Re: Warnings Trend Graph Not Appearing For Builds Yes, I do have multiple builds with the same name '3.9.5'. The name '3.9.5' is set thought a script which outputs the version # of my app: currentBuild.displayName = sh(script: 'make ios-version' , returnStdout: true).trim() 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.202506.157106850.8178.1571153520166%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Victor Martinez commented on JENKINS-59668 Re: Run wrapper process in the background fails with the latest changes Thanks again for the help, I finally managed to find the issue related to the $PATH, which it was related to a manipulation of the env map, the env seems to be a global map therefore when running a parallel step using different OS its behavior might be unpredictable. Thanks again and thanks for caring about LAUNCH_DIAGNOSTICS to be the default approach. I'll close this ticket now if you don't mind Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.8153.1571152922781%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Victor Martinez closed an issue as Not A Defect Jenkins / JENKINS-59668 Run wrapper process in the background fails with the latest changes Change By: Victor Martinez Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.8154.1571152922838%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Gregory PICOT started work on JENKINS-59790 Change By: Gregory PICOT Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8039.1571150521725%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Gregory PICOT stopped work on JENKINS-59790 Change By: Gregory PICOT Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8042.1571150521809%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Dave Nichols edited a comment on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Also having this issue with Gitlab, multibranch pipelines, and Jenkins 2.150.2.Jenkins is running as a container with nginx. Also not 100% on this but I don't think all of the branches disappeared, only a subset disappeared and I can't find a reason why only those. 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.196298.154504211.8024.1571149081579%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Dave Nichols commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Also having this issue with Gitlab, multibranch pipelines, and Jenkins 2.150.2. Jenkins is running as a container with nginx. 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.196298.154504211.8011.1571148960459%40Atlassian.JIRA.
[JIRA] (JENKINS-59778) Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object
Title: Message Title Devin Nusbaum closed an issue as Won't Fix Jenkins / JENKINS-59778 Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object Change By: Devin Nusbaum Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202502.1571054173000.8008.1571148540515%40Atlassian.JIRA.
[JIRA] (JENKINS-59778) Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object
Title: Message Title Devin Nusbaum commented on JENKINS-59778 Re: Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object Alexander Samoylov GroovyInstallation is Java code from a plugin. Compared to Groovy code in Pipeline, the most important differences are that it is not CPS-transformed, it is not sandbox-transformed, its class loader hierarchy is different, and there is a class file on disk for it somewhere instead of whatever happens for Groovy code run by the embedded Groovy interpreter. I suspect the latter is what is causing problems in your case. Both Pipeline Groovy code and remoting do some tricky low-level things, and so they don't play well together. If you just want to run some Groovy code for debugging purposes, you could try using the script console, which will at least eliminate the Pipeline-specific complexities, to see if that makes a difference. 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.202502.1571054173000.8004.1571148480209%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel commented on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target Hey Aleksi Simell, I upgraded from 1.23 to 2.0.1 on September, 7 (did not re-create publisher, just re-applied config for InfluxDB) on September, 9 I recreated config for InfluxDB plugin and also restarted Jenkins to upgrade other plugins on October, 15 (today) I re-created config for InfluxDB one more time After publisher recreation and re-enabling plugin I can see some data in InfluxDB - no new warnings so far, so it looks good! However I discovered two files related to plugin in JENKINS_HOME: -rw-r--r-- 1 jenkins jenkins 986 Oct 15 12:53 /var/lib/jenkins/jenkinsci.plugins.influxdb.InfluxDbGlobalConfig.xml "influxdb@2.0.1"> -rw-r--r-- 1 jenkins jenkins 903 Sep 9 14:29 /var/lib/jenkins/jenkinsci.plugins.influxdb.InfluxDbPublisher.xml "influxdb@1.23"> Can the presence of `jenkinsci.plugins.influxdb.InfluxDbPublisher.xml` cause this issue? Should I delete the old config file? Thanks, Denis Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You
[JIRA] (JENKINS-59778) Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object
Title: Message Title Alexander Samoylov edited a comment on JENKINS-59778 Re: Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object [~dnusbaum], Yes, it never worked for me. I will try to describe my use case better.I ran some Java code on slave for debugging purposes. I used the class GroovyInstallation in my pipeline script and the problem was the getExecutable(VirtualChannel channel) method of this class returned null (even after the successful installation).The method getExecutable(VirtualChannel channel) does almost the same what I wrote in my example above (see https://github.com/jenkinsci/groovy-plugin/blob/master/src/main/java/hudson/plugins/groovy/GroovyInstallation.java), that is uses Callable. I wanted to do the same directly from the pipeline code in order to run my modified version of getExecutable (with printouts etc.), but as you see it failed with those exceptions.Obviously I had a question, why Callable usage this works via the instance of GroovyInstallation, but does not work from the pipeline directly. I didn't understand what is actually the difference and that's why opened this ticket. If you think that this is not supported, why then it works fine via the instance of GroovyInstallation? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59778) Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object
Title: Message Title Alexander Samoylov commented on JENKINS-59778 Re: Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object Devin Nusbaum, Yes, it never worked for me. I will try to describe my use case better. I ran some Java code on slave for debugging purposes. I used the class GroovyInstallation in my pipeline script and the problem was the getExecutable(VirtualChannel channel) method of this class returned null (even after the successful installation). The method getExecutable(VirtualChannel channel) does almost the same what I wrote in my example above (see https://github.com/jenkinsci/groovy-plugin/blob/master/src/main/java/hudson/plugins/groovy/GroovyInstallation.java), that is uses Callable. I wanted to do the same directly from the pipeline code in order to run my modified version of getExecutable (with printouts etc.), but as you see it failed with those exceptions. Obviously I had a question, why Callable usage this works via the instance of GroovyInstallation, but does not work from the pipeline directly. I didn't understand what is actually the difference and that's why opened this ticket. If you think that this is not supported, why then it works fine via the instance of GroovyInstallation? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-55035) Simplify security realms
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-55035 Simplify security realms Change By: Daniel Beck Summary: SImplify Simplify security realms 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.196077.1544023664000.7986.1571146920213%40Atlassian.JIRA.
[JIRA] (JENKINS-59778) Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object
Title: Message Title Devin Nusbaum commented on JENKINS-59778 Re: Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object Yes, using remoting directly from Pipelines is not supported. The supported way to do this from Pipeline is to implement Step in a plugin, and have the step handle the interactions with remoting. Alexander Samoylov, this has never worked for you, right? Or did it work previously before some plugin/core upgrade? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202502.1571054173000.7981.1571146080237%40Atlassian.JIRA.
[JIRA] (JENKINS-51287) Stage view overlaps test overview
Title: Message Title Reinhold Füreder commented on JENKINS-51287 Re: Stage view overlaps test overview I think this has been fixed some time ago 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.190621.1526284437000.7977.1571145900322%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Jeffrey Bennett commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Carsten's approach seems to suggest that the behavior of all node() elements can be offloaded to subordinate groovy scripts. Rather than having the developer do it manually, wouldn't it be nice if that's what Jenkins did for you. In other words, jenkins parses the developer provided jenkinsfile, and manufactures script-with-load and the loaded-scripts that it then works off of. This would then be a true solution. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.7910.1571145605481%40Atlassian.JIRA.
[JIRA] (JENKINS-45852) Bitbucket project icons not displaying properly since 2.2.2.
Title: Message Title Markus Glück commented on JENKINS-45852 Re: Bitbucket project icons not displaying properly since 2.2.2. agreed. 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.184064.1501247779000.7875.1571144700225%40Atlassian.JIRA.
[JIRA] (JENKINS-56037) SCM Polling with p4-plugin triggers builds several times
Title: Message Title Paul Allen updated JENKINS-56037 Jenkins / JENKINS-56037 SCM Polling with p4-plugin triggers builds several times Change By: Paul Allen Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197457.1549569383000.7861.1571143740845%40Atlassian.JIRA.
[JIRA] (JENKINS-59785) java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList
Title: Message Title Mark Waite commented on JENKINS-59785 Re: java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList You might try creating a new job from the same repository that places the job definition inside the job (rather than in the Jenkinsfile and then runs many, many stages in parallel, without performing any of the other work that is performed in the real pipeline. I don't have other ideas to offer. 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.202515.1571130622000.7859.1571143380288%40Atlassian.JIRA.
[JIRA] (JENKINS-59785) java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59785 java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202515.1571130622000.7857.1571143020144%40Atlassian.JIRA.
[JIRA] (JENKINS-55559) net.sf.json.JSONException: Invalid JSON String with Octopus Deploy Deployment plugin
Title: Message Title
David Madl commented on JENKINS-9
Re: net.sf.json.JSONException: Invalid JSON String with Octopus Deploy Deployment plugin
I've found that readJSON (net.sf.json.JSONSerializer.toJSON()), at least in json-lib-2.4-jdk15.jar, may fail due to leading and trailing whitespace. For example, the following is broken:
import net.sf.json.JSONSerializer
demo = JSONSerializer.toJSON("""
{}
""") // fails with net.sf.json.JSONException: Invalid JSON String
Whereas the following works:
demo = JSONSerializer.toJSON("""{}""")
You may want to trim() your strings before passing into readJSON / JSONSerializer.toJSON(). Hope this helps.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59754) Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines
Title: Message Title Radi Berkovich edited a comment on JENKINS-59754 Re: Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines I actually see that relogin succedded - "having successful RE-LOGIN".Please explain what happen with plugin when it "drop" the connection, what exactly happen. Can you please sent me full log file to radislav.berkov...@microfocus.com 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.202477.1570821116000.7849.1571142480221%40Atlassian.JIRA.
[JIRA] (JENKINS-59396) AWT initialized even with -Djava.awt.headless=true
Title: Message Title Julien Bréda commented on JENKINS-59396 Re: AWT initialized even with -Djava.awt.headless=true There is no problem without Tomcat : the provided command works almost well. Despite of this, we don't use the same code to launch the webapp with or without Tomcat : with Tomcat the first executed class is hudson.WebAppMain without it, the first one is Main. At this point the problem can be caused by two things (or maybe others I couldn't imagine) : Tomcat The static code and its usage (hudson.WebAppMain) Moreover, I did a heapdump (when using the Tomcat instance). In this file we can see the system properties. java.awt.headless appears among them. Thanks to it, we can tell that Tomcat is not the problem : it doesn't alter the system properties. I think the static code should be reviewed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
true, release:false}], JunitTestsPublisher[disabled=false,healthScaleFactor=,keepLongStdio=false,ignoreAttachments=false]]11:25:04 [withMaven] Available options: 11:25:04 [withMaven] using JDK installation sapjvm-811:25:04 $ /bin/sh -c "which mvn"11:25:04 [withMaven] using Maven installation provided by the build agent with executable /usr/local/bin/mvn[Pipeline] {[Pipeline] sh11:25:05 + mvn -Dmaven.test.failure.ignore clean package11:25:05 - withMaven Wrapper script -11:25:05 Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)11:25:05 Maven home: /usr/local/maven11:25:05 Java version: 1.8.0_77, vendor: SAP AG, runtime: /usr/lib/jvm/sapjvm_8/jre11:25:05 Default locale: en_US, platform encoding: ANSI_X3.4-196811:25:05 OS name: "linux", version: "4.14.138+", arch: "amd64", family: "unix"11:25:05 [INFO] [jenkins-event-spy] Generate /srv/jenkins/workspace/test pipeline@tmp/withMaven3fe3ef73/maven-spy-20191015-092505-8403902332112577080839.log.tmp ...11:25:06 [INFO] Scanning for projects...11:25:06 [INFO] 11:25:06 [INFO] < test:simple-maven-project-with-tests >11:25:06 [INFO] Building simple-maven-project-with-tests 1.0-SNAPSHOT11:25:06 [INFO] [ jar ]-{code}Same log snipped when pipeline is executed on slave looks like this:{code}Checking out Revision fbe787fbf5b8fce670b4401b2d348ff7a4357160 (origin/master)Commit message: "first commit"[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build)[Pipeline] script[Pipeline] {[Pipeline] withMaven[withMaven] Options: [org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher[disabled=false], org.jenkinsci.plugins.pipeline.maven.publishers.DependenciesFingerprintPublisher[disabled=false, scopes=[compile, provided, runtime], versions={snapshot:true, release:false}], JunitTestsPublisher[disabled=false,healthScaleFactor=,keepLongStdio=false,ignoreAttachments=false]][withMaven] Available options: [withMaven] using JDK installation sapjvm-8$ /bin/sh -c "which mvn"[withMaven] using Maven installation provided by the build agent with executable /usr/bin/mvn[Pipeline] {[Pipeline] sh+ mvn -Dmaven.test.failure.ignore clean package- withMaven Wrapper script -Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/var/lib/jenkins/workspace/test pipeline@tmp/withMaven805d1277/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/var/lib/jenkins/workspace/test pipeline@tmp/withMaven805d1277" Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-27T15:06:16Z)Maven home: /usr/share/mavenJava version: 1.8.0_221, vendor: SAP AG, runtime: /usr/lib/jvm/sapjvm_8/jreDefault locale: en_US, platform encoding: ANSI_X3.4-1968OS name: "linux", version: "4.14.138+", arch: "amd64", family: "unix"Seen branch in repository origin/masterSeen 1 remote branch > git show-ref --tags -d # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f fbe787fbf5b8fce670b4401b2d348ff7a4357160[INFO] [jenkins-event-spy] Generate /var/lib/jenkins/workspace/test pipeline@tmp/withMaven805d1277/maven-spy-20191015-093038-6193675996080952171854.log.tmp ...[INFO] Scanning for projects...[INFO] [INFO] < test:simple-maven-project-with-tests >[INFO] Building simple-maven-project-with-tests 1.0-SNAPSHOT[INFO] [ jar ]-{code} All installed Pipeline related List of plugins and their versions you can see version is listed below:{code}PrioritySorter: 3.6.0 (Priority Sorter Plugin)ace-editor: 1.1 (_javascript_ GUI Lib: ACE Editor bundle plugin)ansicolor: 0.6.2 (AnsiColor)antisamy-markup-formatter: 1.6 (OWASP Markup Formatter Plugin)apache-httpcomponents-client-4-api: 4.5.10-1.0 (Apache HttpComponents Client 4.x API Plugin)authentication-tokens: 1.3 (Authentication Tokens API Plugin)blueocean: 1.19.0 (Blue Ocean)blueocean-autofavorite: 1.2.4 (Autofavorite for Blue Ocean)blueocean-bitbucket-pipeline: 1.19.0 (Bitbucket Pipeline for Blue Ocean)blueocean-commons: 1.19.0 (Common API for Blue Ocean)blueocean-config: 1.19.0 (Config API for Blue Ocean)blueocean-core-js: 1.19.0 (Blue Ocean Core JS)blueocean-dashboard: 1.19.0 (Dashboard for Blue Ocean)blueocean-display-url: 2.3.0 (Display URL for Blue Ocean)blueocean-events: 1.19.0 (Events API for Blue Ocean)blueocean-executor-info: 1.19.0 (Blue Ocean Executor Info)blueocean-git-pipeline: 1.19.0 (Git Pipeline for Blue Ocean)blueocean-github-pipeline: 1.19.0 (GitHub Pipeline for Blue Ocean)blueocean-i18n: 1.19.0 (i18n for Blue Ocean)blueocean-jira: 1.19.0 (JIRA Integration for Blue Ocean)blueocean-jwt: 1.19.0 (JWT for Blue Ocean)blueocean-personalization: 1.19.0 (Personalization f
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Ljubisa Punosevac updated an issue Jenkins / JENKINS-59788 Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Change By: Ljubisa Punosevac Attachment: Screenshot 2019-10-15 at 14.04.14.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.7844.1571142000724%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Ljubisa Punosevac updated an issue Jenkins / JENKINS-59788 Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Change By: Ljubisa Punosevac Attachment: Screenshot 2019-10-15 at 14.04.34.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.7846.1571142000748%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title
Art V updated an issue
Jenkins / JENKINS-59777
nested docker.withRegistry() does not work
Change By:
Art V
With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.Example: {code:java}node('docker') {docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {sh('docker pull repo1/library/image:latest')sh('docker pull repo2/libraryimage:latest')}}}{code}From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?Is there any workaround for this? * - Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files] - - This MR introduced the env variables - specifically `DOCKER_CONFIG` - * --Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with- -https://issues.jenkins-ci.org/browse/JENKINS-52737-- -Made a MR for to use the latest docker-commons:- -[-https://github.com/jenkinsci/docker-workflow-plugin/pull/193-]- * Update – Fixes need on the docker-commons logic. MR here: [https://github.com/jenkinsci/docker-commons-plugin/pull/82]
Add Comment
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title
Art V updated an issue
Jenkins / JENKINS-59777
nested docker.withRegistry() does not work
Change By:
Art V
With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.Example: {code:java}node('docker') {docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {sh('docker pull repo1/library/image:latest')sh('docker pull repo2/libraryimage:latest')}}}{code}From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?Is there any workaround for this? * -Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]- -This MR introduced the env variables - specifically `DOCKER_CONFIG`- * --Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with- - - https://issues.jenkins-ci.org/browse/JENKINS-52737-- - -Made a MR for to use the latest docker-commons:- -[-https://github.com/jenkinsci/docker-workflow-plugin/pull/193-]- * Update – Fixes need on the docker-commons logic. MR here: [https://github.com/jenkinsci/docker-commons-plugin/pull/82]
Add Comment
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title
Art V updated an issue
Jenkins / JENKINS-59777
nested docker.withRegistry() does not work
Change By:
Art V
With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.Example: {code:java}node('docker') {docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {sh('docker pull repo1/library/image:latest')sh('docker pull repo2/libraryimage:latest')}}}{code}From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?Is there any workaround for this? * Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files] This MR introduced the env variables - specifically `DOCKER_CONFIG` * - - Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with - - https://issues.jenkins-ci.org/browse/JENKINS-52737- - -Made a MR for to use the latest docker-commons:- - [-https://github.com/jenkinsci/docker-workflow-plugin/pull/193-] - * Update – Fixes need on the docker-commons logic. MR here: [https://github.com/jenkinsci/docker-commons-plugin/pull/82]
Add Comment
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
ions={snapshot:true, release:false}], JunitTestsPublisher[disabled=false,healthScaleFactor=,keepLongStdio=false,ignoreAttachments=false]]11:25:04 [withMaven] Available options: 11:25:04 [withMaven] using JDK installation sapjvm-811:25:04 $ /bin/sh -c "which mvn"11:25:04 [withMaven] using Maven installation provided by the build agent with executable /usr/local/bin/mvn[Pipeline] {[Pipeline] sh11:25:05 + mvn -Dmaven.test.failure.ignore clean package11:25:05 - withMaven Wrapper script -11:25:05 Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)11:25:05 Maven home: /usr/local/maven11:25:05 Java version: 1.8.0_77, vendor: SAP AG, runtime: /usr/lib/jvm/sapjvm_8/jre11:25:05 Default locale: en_US, platform encoding: ANSI_X3.4-196811:25:05 OS name: "linux", version: "4.14.138+", arch: "amd64", family: "unix"11:25:05 [INFO] [jenkins-event-spy] Generate /srv/jenkins/workspace/test pipeline@tmp/withMaven3fe3ef73/maven-spy-20191015-092505-8403902332112577080839.log.tmp ...11:25:06 [INFO] Scanning for projects...11:25:06 [INFO] 11:25:06 [INFO] < test:simple-maven-project-with-tests >11:25:06 [INFO] Building simple-maven-project-with-tests 1.0-SNAPSHOT11:25:06 [INFO] [ jar ]-{code}Same log snipped when pipeline is executed on slave looks like this:{code}Checking out Revision fbe787fbf5b8fce670b4401b2d348ff7a4357160 (origin/master)Commit message: "first commit"[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build)[Pipeline] script[Pipeline] {[Pipeline] withMaven[withMaven] Options: [org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher[disabled=false], org.jenkinsci.plugins.pipeline.maven.publishers.DependenciesFingerprintPublisher[disabled=false, scopes=[compile, provided, runtime], versions={snapshot:true, release:false}], JunitTestsPublisher[disabled=false,healthScaleFactor=,keepLongStdio=false,ignoreAttachments=false]][withMaven] Available options: [withMaven] using JDK installation sapjvm-8$ /bin/sh -c "which mvn"[withMaven] using Maven installation provided by the build agent with executable /usr/bin/mvn[Pipeline] {[Pipeline] sh+ mvn -Dmaven.test.failure.ignore clean package- withMaven Wrapper script -Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/var/lib/jenkins/workspace/test pipeline@tmp/withMaven805d1277/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/var/lib/jenkins/workspace/test pipeline@tmp/withMaven805d1277" Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-27T15:06:16Z)Maven home: /usr/share/mavenJava version: 1.8.0_221, vendor: SAP AG, runtime: /usr/lib/jvm/sapjvm_8/jreDefault locale: en_US, platform encoding: ANSI_X3.4-1968OS name: "linux", version: "4.14.138+", arch: "amd64", family: "unix"Seen branch in repository origin/masterSeen 1 remote branch > git show-ref --tags -d # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f fbe787fbf5b8fce670b4401b2d348ff7a4357160[INFO] [jenkins-event-spy] Generate /var/lib/jenkins/workspace/test pipeline@tmp/withMaven805d1277/maven-spy-20191015-093038-6193675996080952171854.log.tmp ...[INFO] Scanning for projects...[INFO] [INFO] < test:simple-maven-project-with-tests >[INFO] Building simple-maven-project-with-tests 1.0-SNAPSHOT[INFO] [ jar ]-{code} All installed Pipeline related plugins and their versions you can see in the attached screenshots.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Ljubisa Punosevac updated an issue Jenkins / JENKINS-59788 Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Change By: Ljubisa Punosevac Attachment: Screenshot 2019-10-15 at 14.04.34.png Attachment: Screenshot 2019-10-15 at 14.04.14.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.7825.1571141160205%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Art V assigned an issue to Jesse Glick Jenkins / JENKINS-59777 nested docker.withRegistry() does not work Change By: Art V Assignee: Jesse Glick 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.202501.1571053962000.7815.1571140561231%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title
Art V updated an issue
Jenkins / JENKINS-59777
nested docker.withRegistry() does not work
Change By:
Art V
With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.Example: {code:java}node('docker') {docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {sh('docker pull repo1/library/image:latest')sh('docker pull repo2/libraryimage:latest')}}}{code}From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?Is there any workaround for this? * Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files] This MR introduced the env variables - specifically `DOCKER_CONFIG` * - Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with https://issues.jenkins-ci.org/browse/JENKINS-52737 - - Made a MR for to use the latest docker-commons: - [ - https://github.com/jenkinsci/docker-workflow-plugin/pull/193 - ] * Update – Fixes need on the docker-commons logic. MR here: [https://github.com/jenkinsci/docker-commons-plugin/pull/82]
Add Comment
[JIRA] (JENKINS-59791) Add SCM blames info to the Warnings Next Generation Plugin remote api
Title: Message Title ying yang created an issue Jenkins / JENKINS-59791 Add SCM blames info to the Warnings Next Generation Plugin remote api Issue Type: New Feature Assignee: Ulli Hafner Attachments: image-2019-10-15-19-18-40-074.png Components: git-forensics-plugin, warnings-ng-plugin, warnings-plugin Created: 2019-10-15 11:22 Environment: Git Forensics Plugin version 0.3.2; Warnings Next Generation version 6.1.0 Labels: plugin Priority: Minor Reporter: ying yang I have installed the Git Forensics Plugin on jenkins and use it with Warnings Next Generation Plugin, and I can see the SCM Blames on the html page, but I can not get those blames data from remote API. Can it be available to fetch blames data through remote api ? I hope the blames info can be added in the exsiting API like "[build-url]/[tool-id]/all/api/json" as new properties. thank you
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq created an issue Jenkins / JENKINS-59790 Container cannot connect to node because it doesn't exist Issue Type: Bug Assignee: Nicolas De Loof Components: docker-plugin Created: 2019-10-15 10:48 Labels: plugin exception slave Priority: Critical Reporter: Mathieu Delrocq We recently updated our version of Jenkins. Now a connection error with docker-agent block the queue of jobs : Refusing headers from remote: Unknown client name: docker-00026wu6nor9w The docker container is ready and try to connect to the Jenkins master but the node doesn't exist yet. I saw in the code of docker-plugin that the container is created before the Jenkins node. I purpose to modify provision methods to create the Jenkins node before instanciate the container to fix this issue.
[JIRA] (JENKINS-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Jeff G commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan Same issue. Does anyone have a way to abort these? I tried using Scriptler as though it were a build but could not find the right combination. 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.187738.1516006604000.7754.1571136420656%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel commented on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target Yes, sure, I will do it and come back to here with results. 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.202441.1570700819000.7750.1571135520256%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier commented on JENKINS-59707 Re: Give more details in the connection success panel Ryan Campbell I don't think we want to expose the # of probes or Advisor version. I think we just want to say something like "Connection successful" for the Server: Ok. It's what we have today. I will keep it. It was to show that even if the plugin doesn't evolve much, on the server side we are regularly updating it I really like showing the previous upload vs. next. Where is that data coming from? The previous information we have it already. It's recorded in the configuration each time we send a bundle (I don't like to store it here but I don't know if we can do better). It was already displayed for some time but I'm trying to make it more visible. I would love to display the next upload but I'm not able to find a such info in a AsyncPeriodicWork. I have to dig more... 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.202408.1570569525000.7751.1571135520271%40Atlassian.JIRA.
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Paul Allen started work on JENKINS-59213 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201664.156755142.7746.1571135460672%40Atlassian.JIRA.
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-59213 P4 Plugin - Errors when syncing symlinks Change By: Paul Allen Labels: P4_SUPPORT P4_VERIFY p4-plugin symlink 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.201664.156755142.7743.1571135460563%40Atlassian.JIRA.
[JIRA] (JENKINS-59611) Symlink target update fails when "noclobber" set
Title: Message Title Paul Allen assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-59611 Symlink target update fails when "noclobber" set Change By: Paul Allen Assignee: Charusheela Bopardikar 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.202252.1569940696000.7735.1571135402111%40Atlassian.JIRA.
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Paul Allen assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-59213 P4 Plugin - Errors when syncing symlinks Change By: Paul Allen Assignee: Karl Wirth Charusheela Bopardikar 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.201664.156755142.7739.1571135403556%40Atlassian.JIRA.
[JIRA] (JENKINS-59611) Symlink target update fails when "noclobber" set
Title: Message Title Paul Allen started work on JENKINS-59611 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202252.1569940696000.7732.1571135340687%40Atlassian.JIRA.
[JIRA] (JENKINS-59475) Possibility to remove SID from existing role
Title: Message Title Abhyudaya Sharma commented on JENKINS-59475 Re: Possibility to remove SID from existing role See: https://github.com/jenkinsci/folder-auth-plugin/pull/38 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.202089.156923802.7728.1571134921597%40Atlassian.JIRA.
[JIRA] (JENKINS-59686) MicroFocus Build Report Publish Error
Title: Message Title Ricardo Nazareth commented on JENKINS-59686 Re: MicroFocus Build Report Publish Error Hi Maria Narcisa Galan, I guess u are asking for Jenkins script. Tell me if u need UFT script. Pipeline im using: Anyway, i think that i my solved the problem. We define the HeapSize min and max, and use the Garbage Collector G1. Until now i test whit both slaves working and saving evidences on both, and no crash so far. I will continue to test this, to make sure if will not break again. 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.202384.1570454666000.7730.1571134921817%40Atlassian.JIRA.
