[JIRA] (JENKINS-55095) There are users who are still using a legacy API token
Title: Message Title Hiten wala created an issue Jenkins / JENKINS-55095 There are users who are still using a legacy API token Issue Type: Task Assignee: Alex Earl Components: token-macro-plugin Created: 2018-12-10 07:07 Priority: Minor Reporter: Hiten wala I am Getting this error There are users who are still using a legacy API token. That system is not as secure as the new one because it stores the token in a recoverable manner on the disk. See list of impacted users. Build now link just flashes a tooltip that says "Build scheduled". Add Comment
[JIRA] (JENKINS-42856) Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel
Title: Message Title Gerry Weißbach commented on JENKINS-42856 Re: Unable to launch Windows slaves using Microsoft OpenSSH: Unexpected termination of the channel Please note our most recent version of the command is the following: Mark Waite your command shows a second quote after 'cd' which breaks the command. Prefix: cd C:/jenkins ; java -jar remoting.jar -workDir C:/jenkins ; exit 0 ; # " Postfix: " Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Michael Mrozek commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 I've been working around this by temporarily giving anonymous admin access and rebooting Jenkins once so it can convert the old data, then revoking the admin access. But I need to do it on every Jenkins upgrade, so it's not a permanent solution Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55094) "commands" and "args" are being defaulted using Kubernetes plugin
Title: Message Title Mohammad Norouzi created an issue Jenkins / JENKINS-55094 "commands" and "args" are being defaulted using Kubernetes plugin Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-12-10 04:42 Labels: kuberenetes-plugin Priority: Minor Reporter: Mohammad Norouzi We are using terraform and Jenkins configuration as yaml file to deploy Jenkins. When defining Kubernetes Pod templates, whether we set command and args to empty string or not providing it at all, after the deploying Jenkins or refreshing with new configuration, both values are being defaulted to: command: /bin/sh -c args: cat This causes issues because each docker image has its own entrypoint or cmd and this overrides them. So now everytime we redeploy Jenkins we have to manually remove command and args within the Jenkins user interface. For example, the jnlp container requires to run a specific command defined in jenkins/jnlp-slave:3.23-1-alpine Dockerfile but those default value makes the container not to be able to communicate with Jenkins I believe this is the issue with the UI template: https://github.com/jenkinsci/kubernetes-plugin/blob/b1ba0de0fc1fcc46937ab5f984289ff7b5594cef/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/ContainerTemplate/config.jelly#L26 I have created a question in stackoverflow but nobody replied:
[JIRA] (JENKINS-55093) multi branch job limit offset issue
Title: Message Title runze xia commented on JENKINS-55093 Re: multi branch job limit offset issue https://github.com/jenkinsci/blueocean-plugin/pull/1841 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55093) multi branch job limit offset issue
Title: Message Title runze xia created an issue Jenkins / JENKINS-55093 multi branch job limit offset issue Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-12-10 02:58 Priority: Major Reporter: runze xia In the current limit offset implementation, in some cases the data is inaccurate. For example, I have 11 data, but if I set the offset to 10, I might not get the 11th data. This problem will affect the experience of the jenkins blue api user. I think this part of the api implementation should not only consider the blueocean front end, but also consider the user of the api. Add Comment
[JIRA] (JENKINS-55092) linter for Jenkinsfile doesn't detect misspelled parameter names
Title: Message Title Dylan Nicholson updated an issue Jenkins / JENKINS-55092 linter for Jenkinsfile doesn't detect misspelled parameter names Change By: Dylan Nicholson Component/s: pipeline-model-definition-plugin Component/s: jenkinsfile-runner Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55092) linter for Jenkinsfile doesn't detect misspelled parameter names
Title: Message Title Dylan Nicholson created an issue Jenkins / JENKINS-55092 linter for Jenkinsfile doesn't detect misspelled parameter names Issue Type: Bug Assignee: Oleg Nenashev Components: jenkinsfile-runner, pipeline Created: 2018-12-10 01:12 Priority: Minor Reporter: Dylan Nicholson On a busy Jenkins system it can take up to 30 minutes before your job gets executed, then take several minutes to get to the step you've just added where you accidentally misspelled a parameter name to a Groovy command (sh in my case). The declarative-linter idea is great but something that can pick up any errors that are guaranteed to break your build when it finally executed would make a huge difference. Add Comment
[JIRA] (JENKINS-42755) BFA fails to catch pipeline related exceptions
Title: Message Title Justin Vallon commented on JENKINS-42755 Re: BFA fails to catch pipeline related exceptions I had the same trouble, and am also using the "timestamps" feature. When timestamps is active, it prefixes every line of output with a date+time; it seems BFA wants that to match as well. I added '^.*' to my rule, and now it matches the lines in the "Failure Cause Editor" and it was able to find "Identified Problems" in the build page. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55078) No longer able to start ECS slaves
Title: Message Title Stefan Graber commented on JENKINS-55078 Re: No longer able to start ECS slaves Same here... starting tasks with ecs-plugin 1.18 does not work anymore. Downgrade to 1.17 works. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55091) Pipeline - Provide better type information
Title: Message Title Rudolf-Walter Kiss-Szakacs started work on JENKINS-55091 Change By: Rudolf-Walter Kiss-Szakacs Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55091) Pipeline - Provide better type information
Title: Message Title Rudolf-Walter Kiss-Szakacs created an issue Jenkins / JENKINS-55091 Pipeline - Provide better type information Issue Type: Improvement Assignee: Rudolf-Walter Kiss-Szakacs Components: workflow-cps-plugin, workflow-step-api-plugin Created: 2018-12-09 18:53 Priority: Minor Reporter: Rudolf-Walter Kiss-Szakacs Currently, one can programmatically find out the parameters of pipeline steps. However, the result type is not available. Similarly, global variables do not expose their logical type to analysis. Provide a way to get more type information about steps and global variables, without running them. Add Comment
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title dan tran edited a comment on JENKINS-54515 Re: master triggers own branches on the second thought, i am going to create a delegate job to invoke my sub jobs directly. So we good ( a --> b --> delegate --> c,e,f etc )but, it would be great to have this fixed fix :) https://issues.jenkins-ci.org/browse/JENKINS-53382 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title dan tran edited a comment on JENKINS-54515 Re: master triggers own branches on the second thought, i am going to create a delegate job to trigger invoke my sub builds jobs directly . So we good ( a --> b --> delegate --> c,e,f etc )but, it would be great to this fixed :) https://issues.jenkins-ci.org/browse/JENKINS-53382 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title dan tran commented on JENKINS-54515 Re: master triggers own branches on the second thought, i am going to create a delegate job to trigger my sub builds. So we good ( a --> b --> delegate --> c,e,f etc ) but, it would be great to this fixed https://issues.jenkins-ci.org/browse/JENKINS-53382 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32320) Ability to configure changelog message truncation and inclusion of merge commits
Title: Message Title Mark Waite commented on JENKINS-32320 Re: Ability to configure changelog message truncation and inclusion of merge commits Changelog message summary truncation control has been added to git plugin 4.0.0 as the fix for JENKINS-29977. No release date for git plugin 4.0.0 yet, but builds are available now if you'd like to test them. Install: git plugin 4.0.0 pre-release build git client plugin 3.0.0 pre-release build Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32320) Ability to configure changelog message truncation and inclusion of merge commits
Title: Message Title Mark Waite edited a comment on JENKINS-32320 Re: Ability to configure changelog message truncation and inclusion of merge commits Changelog message summary truncation control has been added to git plugin 4.0.0 as the fix for JENKINS-29977. No release date for git plugin 4.0.0 yet, but builds are available now if you'd like to test them.Install:* [git client plugin 4 3 .0.0 pre-release build|https://ci.jenkins.io/job/Plugins/job/git- client- plugin/job/master/ 272 261 /artifact/org/jenkins-ci/plugins/git -client / 4 3 .0.0- rc2944 beta6-rc1837 . 7f8193132a79 0cc9ca3b5522 /git- 4 client-3 .0.0- rc2944 beta6-rc1837 . 7f8193132a79 0cc9ca3b5522 .hpi]* * [git client plugin 3 4 .0.0 pre-release build|https://ci.jenkins.io/job/Plugins/job/git- client- plugin/job/master/ 261 272 /artifact/org/jenkins-ci/plugins/git -client / 3 4 .0.0- beta6-rc1837 rc2944 . 0cc9ca3b5522 7f8193132a79 /git- client-3 4 .0.0- beta6-rc1837 rc2944 . 0cc9ca3b5522 7f8193132a79 .hpi] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32320) Ability to configure changelog message truncation and inclusion of merge commits
Title: Message Title Mark Waite edited a comment on JENKINS-32320 Re: Ability to configure changelog message truncation and inclusion of merge commits Changelog message summary truncation control has been added to git plugin 4.0.0 as the fix for JENKINS-29977. No release date for git plugin 4.0.0 yet, but builds are available now if you'd like to test them.Install:* [git client plugin 3.0.0 pre-release build|https://ci.jenkins.io/job/Plugins/job/git-client-plugin/job/master/261/artifact/org/jenkins-ci/plugins/git-client/3.0.0-beta6-rc1837.0cc9ca3b5522/git-client-3.0.0-beta6-rc1837.0cc9ca3b5522.hpi]* * [git plugin 4.0.0 pre-release build|https://ci.jenkins.io/job/Plugins/job/git-plugin/job/master/272/artifact/org/jenkins-ci/plugins/git/4.0.0-rc2944.7f8193132a79/git-4.0.0-rc2944.7f8193132a79.hpi] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title dan tran commented on JENKINS-54515 Re: master triggers own branches We have one large repo with 400+ maven modules including both production and integration test sources. Main repo build (~60min) does build integration test modules abut not running them. We also have many wrapper repos clone the main repo at build time and run * subset of integration tests at each repo ( ie main build trigger a number of parallel integration test builds * Platform sanity builds ( windows, etc) Merge them into a single pipeline are big, complex, and long. is there a way to disable maven pipeline event listener after we clone the main repo at the test pipelines? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33238) GitPlugin | Concurrent builds are serialized when publishing
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-33238 GitPlugin | Concurrent builds are serialized when publishing Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35356) Support for Stash Backup Client
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-35356 Support for Stash Backup Client Change By: Mark Waite Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46650) Snippet Generator fails with Gitlab repository Version
Title: Message Title Mark Waite updated JENKINS-46650 Fixed in git plugin 4.0.0 pre-release Jenkins / JENKINS-46650 Snippet Generator fails with Gitlab repository Version Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47733) Add a withGit pipeline step that provides git credentials
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-47733 Add a withGit pipeline step that provides git credentials Change By: Mark Waite Summary: Add a withGit pipeline step that provides git credentials Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47789) Git BuildData entry leaks in from Gerrit event triggered builds in build.xml
Title: Message Title Mark Waite updated JENKINS-47789 Jenkins / JENKINS-47789 Git BuildData entry leaks in from Gerrit event triggered builds in build.xml Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47789) Git BuildData entry leaks in from Gerrit event triggered builds in build.xml
Title: Message Title Mark Waite updated JENKINS-47789 See PR 578 for the proposed change being evaluated for possible inclusion in git plugin 4.0.0 Jenkins / JENKINS-47789 Git BuildData entry leaks in from Gerrit event triggered builds in build.xml Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51061) No commits are discovered by Jenkins after git force push
Title: Message Title Mark Waite updated JENKINS-51061 I cannot duplicate the problem. I force push frequently and have not seen issues with multibranch Pipelines. Since the original submitter has provided no more details, I'm closing this as "Cannot reproduce" Jenkins / JENKINS-51061 No commits are discovered by Jenkins after git force push Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51061) No commits are discovered by Jenkins after git force push
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-51061 No commits are discovered by Jenkins after git force push Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51061) No commits are discovered by Jenkins after git force push
Title: Message Title Mark Waite updated JENKINS-51061 Jenkins / JENKINS-51061 No commits are discovered by Jenkins after git force push Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51542) Git checkout is slower than the command line execution
Title: Message Title Mark Waite commented on JENKINS-51542 Re: Git checkout is slower than the command line execution And yet the second call to `git fetch` completes in 3 seconds (09:54:15 -> 09:54:18) while the first call to `git fetch` requires 60 seconds. The second call to `git fetch` does not seem to be a dramatic contributor to slower performance. Can you provide more details that compare the same commands from a command line? Are the same commands also using the same file system? Are there other differences which affect performance? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51673) PollSCM runs again when job on commit takes longer then the trigger
Title: Message Title Mark Waite stopped work on JENKINS-51673 Change By: Mark Waite Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52485) Git step in Scripted Pipeline gets skipped if Git Plugin is not installed
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-52485 Git step in Scripted Pipeline gets skipped if Git Plugin is not installed Change By: Mark Waite Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52875) Joda time class not found exception in git plugin changeset calculation
Title: Message Title Mark Waite updated JENKINS-52875 Since the submitter of the bug report has not replied to the request for additional information and I cannot duplicate the problem, I'm closing the bug Jenkins / JENKINS-52875 Joda time class not found exception in git plugin changeset calculation Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52875) Joda time class not found exception in git plugin changeset calculation
Title: Message Title Mark Waite updated JENKINS-52875 Jenkins / JENKINS-52875 Joda time class not found exception in git plugin changeset calculation Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53725) git-plugin cannot operate on a git-worktree
Title: Message Title Mark Waite updated JENKINS-53725 Fixed in git plugin 4.0.0 on the master branch Jenkins / JENKINS-53725 git-plugin cannot operate on a git-worktree Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53725) git-plugin cannot operate on a git-worktree
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-53725 git-plugin cannot operate on a git-worktree Change By: Mark Waite Comment: Fixed in git plugin 4.0.0 on the master branch Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53725) git-plugin cannot operate on a git-worktree
Title: Message Title Mark Waite commented on JENKINS-53725 Re: git-plugin cannot operate on a git-worktree Resolved in git plugin 4.0.0 by the broader exception handling Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54549) gitscm fail for multibranch pipeline after recent plugin upgrade
Title: Message Title Mark Waite commented on JENKINS-54549 Re: gitscm fail for multibranch pipeline after recent plugin upgrade I can't duplicate this problem. I'm running a Bitbucket branch source based multibranch Pipeline with Bitbucket server (not Bitbucket Enterprise). Can you provide any further details that will allow someone else to duplicate the problem? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54895) Jenkins build used wrong commit number
Title: Message Title Mark Waite commented on JENKINS-54895 Re: Jenkins build used wrong commit number Can you provide any further details on the conditions when the problem happened? Specifically, can you provide a numbered series of steps which will allow someone else to repeat the problem? If not, can you provide the job definition which shows the problem? Specifically, is it a Freestyle job or a Pipeline job or a multibranch Pipeline job? Does the job definition use any other git plugin extensions like "checkout to a subdirectory" or "Require a workspace"? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55090) Administrative monitor to recommend to use MySQL instead of embedded H2
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-55090 Administrative monitor to recommend to use MySQL instead of embedded H2 Issue Type: New Feature Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-12-09 14:54 Priority: Major Reporter: Cyrille Le Clerc Administrative monitor to recommend to use MySQL instead of embedded H2 for production grade workloads. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-50401) Checkout resolution misbehaves with local branch and forward slashes
Title: Message Title Mark Waite updated JENKINS-50401 Jenkins / JENKINS-50401 Checkout resolution misbehaves with local branch and forward slashes Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55014) Deadlocking around support-core-plugin log publishing
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-55014 Deadlocking around support-core-plugin log publishing Change By: Mark Waite Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15420) Support RhodeCode
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-15420 Support RhodeCode Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13413) Git icon(git-48x48.png) missing in job page.
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-13413 Git icon(git-48x48.png) missing in job page. Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14350) Add branch name to ChangeSetList
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-14350 Add branch name to ChangeSetList Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10880) Git plugin fails on remote Poll
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-10880 Git plugin fails on remote Poll Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14443) Build is broken out of the box
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-14443 Build is broken out of the box Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13580) git plugin "included regions" feature is bypassed when evaluating a merge commit
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-13580 git plugin "included regions" feature is bypassed when evaluating a merge commit Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13583) Error about sending to an empty list of recipients
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-13583 Error about sending to an empty list of recipients Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13550) Git "Tag to push" should trim whitespace
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-13550 Git "Tag to push" should trim whitespace Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13051) Setting branch name prevents branch from building
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-13051 Setting branch name prevents branch from building Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-11887) Support Git for "Repository browser" setting
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-11887 Support Git for "Repository browser" setting Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9635) git clone --progress not supported with older git binaries
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-9635 git clone --progress not supported with older git binaries Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-11749) Included regions feature for GitSCM plugin
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-11749 Included regions feature for GitSCM plugin Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13385) Jenkins stop working after upgrade
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-13385 Jenkins stop working after upgrade Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9510) GIT_BRANCH token macro non-fullName parses branch incorrectly
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-9510 GIT_BRANCH token macro non-fullName parses branch incorrectly Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13356) Git fast remote polling always triggers build when missing locale
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-13356 Git fast remote polling always triggers build when missing locale Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12369) when upgrading from 1.1.14 to 1.1.15 all git builds shown no succesfull builds on jenkins dashboard
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-12369 when upgrading from 1.1.14 to 1.1.15 all git builds shown no succesfull builds on jenkins dashboard Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12022) Push notification does not work with (project) based Matrix Authorization Strategy unless Anonymous has Job Read access
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-12022 Push notification does not work with (project) based Matrix Authorization Strategy unless Anonymous has Job Read access Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12323) Git rev-parse in git plugin gives a confusing revision for annotate tags
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-12323 Git rev-parse in git plugin gives a confusing revision for annotate tags Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-11107) List of changes is empty even they're already in the changelog.xml
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-11107 List of changes is empty even they're already in the changelog.xml Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12790) [Git Plugin] Post-receive hook fails because it claims to require authentication, why?
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-12790 [Git Plugin] Post-receive hook fails because it claims to require authentication, why? Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-11057) user.name and user.email settings are not applied for the commits by Maven 2 Release Plugin
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-11057 user.name and user.email settings are not applied for the commits by Maven 2 Release Plugin Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10408) Jenkins doesn't always build the git branch we asked
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-10408 Jenkins doesn't always build the git branch we asked Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10060) cannot use the "pass-through git commit that was built" parameter with triggered jobs
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-10060 cannot use the "pass-through git commit that was built" parameter with triggered jobs Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9914) Merge before build setting lost/reset on each configure
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-9914 Merge before build setting lost/reset on each configure Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10373) Unable to select Gerrit Trigger "Choosing Strategy"
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-10373 Unable to select Gerrit Trigger "Choosing Strategy" Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10348) Git 1.1.9 plugin breaks remote name cleaning
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-10348 Git 1.1.9 plugin breaks remote name cleaning Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9971) Git plugin throws NPE when setting up publisher
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-9971 Git plugin throws NPE when setting up publisher Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10272) Global git config name and email address settings not used
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-10272 Global git config name and email address settings not used Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10270) Git plugin advanced options disappear when you reopen the configuration screen
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-10270 Git plugin advanced options disappear when you reopen the configuration screen Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9702) NPE if 'Global Config user.{name,email} Value' are not set
Title: Message Title
Mark Waite closed an issue as Fixed
Jenkins / JENKINS-9702
NPE if 'Global Config user.{name,email} Value' are not set
Change By:
Mark Waite
Status:
Resolved Closed
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9566) Internal server error when viewing people.
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-9566 Internal server error when viewing people. Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9661) "git remote prune" failures for alternate, ssh:// repositories
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-9661 "git remote prune" failures for alternate, ssh:// repositories Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9339) "Nothing to do" could suggest fixes
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-9339 "Nothing to do" could suggest fixes Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9253) Add GIT_COMMIT to build environment
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-9253 Add GIT_COMMIT to build environment Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49337) GeneralNonBlockingStepExecution (was: InterruptedException from step tail call)
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: GeneralNonBlockingStepExecution (was: InterruptedException from step tail call) workflow-step-api 2.17 has been released. We will be able to release soon. We have to evaluate the adoption of workflow-step-api:2.17 to understand if asking this upgrade to the users of withMaven is sustainable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc updated JENKINS-54515 Fixed in 3.6.4 Jenkins / JENKINS-54515 master triggers own branches Change By: Cyrille Le Clerc Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc commented on JENKINS-54515 Re: master triggers own branches dan tran we brainstormed with Arnaud Héritier and we felt that a reasonable default behaviour would be to not trigger pipelines that work on the same pom.xml. The implementation we chose, as we don't capture for the moment the pom.xml details (1), is to not trigger pipeline that generate the artifact that would be the reason of the trigger. This solution is fixing all the problems of multi-module Maven projects with multiple git branches but is unfortunately excluding your scenario. How frequent in your organisation is this scenario of chaining pipeline using same pom.xml? How many Maven apps do you build? How many Maven pipelines do you have? How many of such chain of pipelines do you have? Did you consider merging these chained pipelines in a single pipeline job? Did you face problems trying this? (1) SCM details + path in the SCM repo + introducing a POM entity in our data model between the builds and the dependency Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title
Jen Varela Lijó commented on JENKINS-54207
Re: Update delete plugin flow to error out for anything other than file not found
Baptiste Mathus Mandie Smith, for the test, removing permissions on a file won't be enough to throw an error, as the `remove` method from `fs-extra` performs under the hood as `rm -rf` ( https://github.com/jprichardson/node-fs-extra/blob/master/docs/remove.md ). On the other hand, seems like permissions to delete a file are dependant on permissions of its parent folder and not so much on the file itself. Changing the permission on the folder and then trying to delete the folder with a file inside might error with `Directory not empty`, but `fs.chmodSync(path, mode)` seems to not work with directories :/ EISDIR: illegal operation on a directory, open '/evergreen/data/jenkins/home/plugins/dir' 61 | fs.mkdirSync(`${pluginPath}/dir`); {{ 62 | h.touchFile(`${pluginPath}/dir/somefile`);}} {{ > 63 | fs.chmodSync(`${pluginPath}/dir`, 444);}} {{ | ^}} {{ 64 | expect(() => {}} {{ 65 | Storage.removePlugins(['dir']);}} {{ 66 | }).toThrow();}} Do you have any other possible scenario to throw an error on plugin deletion?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title Jen Varela Lijó commented on JENKINS-54207 Re: Update delete plugin flow to error out for anything other than file not found PS: sorry for the horrible formatting..!! Can't manage to fix it :s Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title
Jen Varela Lijó edited a comment on JENKINS-54207
Re: Update delete plugin flow to error out for anything other than file not found
[~batmat] [~asmith_cb], for the test, removing permissions on a file won't be enough to throw an error, as the `remove` method from `fs-extra` performs under the hood as `rm -rf` ( [https://github.com/jprichardson/node-fs-extra/blob/master/docs/remove.md] ).On the other hand, seems like permissions to delete a file are dependant on permissions of its parent folder and not so much on the file itself. Changing the permission on the folder and then trying to delete the folder with a file inside might error with `Directory not empty`, but `fs.chmodSync(path, mode)` seems to not work with *directories* :/ {{ EISDIR: illegal operation on a directory, open '/evergreen/data/jenkins/home/plugins/dir' }} {{61 | fs.mkdirSync(`${pluginPath}/dir`);}} {{ 62 | h.touchFile(`${pluginPath}/dir/somefile`); }} {{ > 63 | fs.chmodSync(`${pluginPath}/dir`, 444); }} {{ | ^ }} {{ 64 | expect(() => { }} {{ 65 | Storage.removePlugins(['dir']); }} {{ 66 | }).toThrow(); }} Do you have any other possible scenario to throw an error on plugin deletion?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title
Jen Varela Lijó updated an issue
Jenkins / JENKINS-54207
Update delete plugin flow to error out for anything other than file not found
Change By:
Jen Varela Lijó
Comment:
[~batmat] [~asmith_cb], for the test, removing permissions on a file won't be enough to throw an error, as the `remove` method from `fs-extra` performs under the hood as `rm -rf` ( [https://github.com/jprichardson/node-fs-extra/blob/master/docs/remove.md] ).On the other hand, seems like permissions to delete a file are dependant on permissions of its parent folder and not so much on the file itself. Changing the permission on the folder and then trying to delete the folder with a file inside might error with `Directory not empty`, but `fs.chmodSync(path, mode)` seems to not work with *directories* :/{{EISDIR: illegal operation on a directory, open '/evergreen/data/jenkins/home/plugins/dir'}}61 | fs.mkdirSync(`${pluginPath}/dir`);{{ \{{ 62 | h.touchFile(`${pluginPath}/dir/somefile`);{{ \{{ > 63 | fs.chmodSync(`${pluginPath}/dir`, 444);{{ \{{ | ^{{ \{{ 64 | expect(() => {{{ {{ 65 | Storage.removePlugins(['dir']);{{ {}}{{{ 66 | }}}{{).toThrow(); Do you have any other possible scenario to throw an error on plugin deletion?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title
Jen Varela Lijó edited a comment on JENKINS-54207
Re: Update delete plugin flow to error out for anything other than file not found
[~batmat] [~asmith_cb], for the test, removing permissions on a file won't be enough to throw an error, as the `remove` method from `fs-extra` performs under the hood as `rm -rf` ( [https://github.com/jprichardson/node-fs-extra/blob/master/docs/remove.md] ).On the other hand, seems like permissions to delete a file are dependant on permissions of its parent folder and not so much on the file itself. Changing the permission on the folder and then trying to delete the folder with a file inside might error with `Directory not empty`, but `fs.chmodSync(path, mode)` seems to not work with *directories* :/{{EISDIR: illegal operation on a directory, open '/evergreen/data/jenkins/home/plugins/dir'}}{{ {{ 61 | fs.mkdirSync(`${pluginPath}/dir`);}} }} {{ \{{ 62 | h.touchFile(`${pluginPath}/dir/somefile`);}} }} {{ \{{ > 63 | fs.chmodSync(`${pluginPath}/dir`, 444);}} }} {{ \{{ | ^}} }} {{ \{{ 64 | expect(() => {}} }} {{ {{ 65 | Storage.removePlugins(['dir']);}} }} \ {{ {}}{{{ 66 | } }}{{ ).toThrow();}} }} Do you have any other possible scenario to throw an error on plugin deletion?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title
Jen Varela Lijó edited a comment on JENKINS-54207
Re: Update delete plugin flow to error out for anything other than file not found
[~batmat] [~asmith_cb], for the test, removing permissions on a file won't be enough to throw an error, as the `remove` method from `fs-extra` performs under the hood as `rm -rf` ( [https://github.com/jprichardson/node-fs-extra/blob/master/docs/remove.md] ). On the other hand, seems like permissions to delete a file are dependant on permissions of its parent folder and not so much on the file itself. Changing the permission on the folder and then trying to delete the folder with a file inside might error with `Directory not empty`, but `fs.chmodSync(path, mode)` seems to not work with *directories* :/{{EISDIR: illegal operation on a directory, open '/evergreen/data/jenkins/home/plugins/dir'}}{{61 | fs.mkdirSync(`${pluginPath}/dir`);}} \ {{ 62 | h.touchFile(`${pluginPath}/dir/somefile`);}} \ {{ > 63 | fs.chmodSync(`${pluginPath}/dir`, 444);}} \ {{ | ^}} \ {{ 64 | expect(() => {}}{{ 65 | Storage.removePlugins([' somefile dir ']);}} \ {{ 66 | }).toThrow();}} Do you have any other possible scenario to throw an error on plugin deletion?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title
Jen Varela Lijó commented on JENKINS-54207
Re: Update delete plugin flow to error out for anything other than file not found
Baptiste Mathus Mandie Smith, for the test, removing permissions on a file won't be enough to throw an error, as the `remove` method from `fs-extra` performs under the hood as `rm -rf` ( https://github.com/jprichardson/node-fs-extra/blob/master/docs/remove.md ). On the other hand, seems like permissions to delete a file are dependant on permissions of its parent folder and not so much on the file itself. Changing the permission on the folder and then trying to delete the folder with a file inside might error with `Directory not empty`, but `fs.chmodSync(path, mode)` seems to not work with directories :/ EISDIR: illegal operation on a directory, open '/evergreen/data/jenkins/home/plugins/dir' 61 | fs.mkdirSync(`${pluginPath}/dir`); {{ 62 | h.touchFile(`${pluginPath}/dir/somefile`);}} {{ > 63 | fs.chmodSync(`${pluginPath}/dir`, 444);}} {{ | ^}} {{ 64 | expect(() => {}} {{ 65 | Storage.removePlugins(['somefile']);}} {{ 66 | }).toThrow();}} Do you have any other possible scenario to throw an error on plugin deletion?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana updated JENKINS-53237 Nikolas Falco The version 3.0.0-M2 is available in Maven Central. Can you please adapt your plugin xUnit with the path of XSD? It has a new location https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd and old location for legacy versions https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd I hope this would work for you. Sorry. Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Tibor Digana Status: Open Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55089) Add a lineSeparator step
Title: Message Title Yoav Miles commented on JENKINS-55089 Re: Add a lineSeparator step On second thought, I think it's better for readFile and writeFile to know how to convert line endings than having to do it manually with another step, but then the change would be less trivial... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title runze xia commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed ava.net.SocketException: Socket closed at java.net.SocketInputStream.read(SocketInputStream.java:204) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at okio.Okio$2.read(Okio.java:139) at okio.AsyncTimeout$2.read(AsyncTimeout.java:237) Caused: java.net.SocketTimeoutException: timeout at okio.Okio$4.newTimeoutException(Okio.java:230) at okio.AsyncTimeout.exit(AsyncTimeout.java:285) at okio.AsyncTimeout$2.read(AsyncTimeout.java:241) at okio.RealBufferedSource.indexOf(RealBufferedSource.java:345) at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:217) at okhttp3.internal.http1.Http1Codec.readHeaderLine(Http1Codec.java:212) at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189) at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:88) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:125) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at io.fabric8.kubernetes.client.utils.BackwardsCompatibilityInterceptor.intercept(BackwardsCompatibilityInterceptor.java:104) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at io.fabric8.kubernetes.client.utils.ImpersonatorInterceptor.intercept(ImpersonatorInterceptor.java:56) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at io.fabric8.kubernetes.client.utils.HttpClientUtils$2.intercept(HttpClientUtils.java:107) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200) at okhttp3.RealCall.execute(RealCall.java:77) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:379) at
[JIRA] (JENKINS-55089) Add a lineSeparator step
Title: Message Title Yoav Miles updated an issue Jenkins / JENKINS-55089 Add a lineSeparator step Change By: Yoav Miles We can't use System.lineSeparator() reliably as it returns the master node's line separator Please include System . Adding a lineSeparator() in the default signature whitelist, thanks :) step is useful for writing files on various agents. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title runze xia commented on JENKINS-53532 Re: KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed I also encountered this problem, I think this problem will greatly affect the user experience, because it can inexplicably cause the pipeline to fail. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55089) Add a lineSeparator step
Title: Message Title Yoav Miles assigned an issue to rsandell Jenkins / JENKINS-55089 Add a lineSeparator step Change By: Yoav Miles Assignee: Andrew Bayer rsandell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55089) Add a lineSeparator step
Title: Message Title Yoav Miles updated an issue Jenkins / JENKINS-55089 Add a lineSeparator step Change By: Yoav Miles We can't use System.lineSeparator() reliably as it returns the master node's line separator Please include System.lineSeparator() in the default signature whitelist, thanks :) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53532) KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed
Title: Message Title runze xia updated an issue Jenkins / JENKINS-53532 KubernetesClientException: Operation: [get] for kind: [Pod] with name: [maven-3-jdk-8-hgdv3] in namespace: [jenkins] failed Change By: runze xia Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55089) Add a lineSeparator step
Title: Message Title Yoav Miles updated an issue Jenkins / JENKINS-55089 Add a lineSeparator step Change By: Yoav Miles Summary: Scripts not permitted to use staticMethod java.lang.System Add a lineSeparator step Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55089) Scripts not permitted to use staticMethod java.lang.System lineSeparator
Title: Message Title Yoav Miles commented on JENKINS-55089 Re: Scripts not permitted to use staticMethod java.lang.System lineSeparator Oleg Nenashev thanks for the prompt response. I'll change this report to ask for a new step, as my case can't be generalized (Jenkins only manages Windows machines at my site). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55089) Scripts not permitted to use staticMethod java.lang.System lineSeparator
Title: Message Title Yoav Miles updated an issue Jenkins / JENKINS-55089 Scripts not permitted to use staticMethod java.lang.System lineSeparator Change By: Yoav Miles Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55089) Scripts not permitted to use staticMethod java.lang.System lineSeparator
Title: Message Title Yoav Miles updated an issue Jenkins / JENKINS-55089 Scripts not permitted to use staticMethod java.lang.System lineSeparator Change By: Yoav Miles Component/s: pipeline-utility-steps-plugin Component/s: script-security-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55089) Scripts not permitted to use staticMethod java.lang.System lineSeparator
Title: Message Title Oleg Nenashev commented on JENKINS-55089 Re: Scripts not permitted to use staticMethod java.lang.System lineSeparator Yoav Miles it may be safe to add it, but it will unlikely get you the result you expect in Jenkins Pipeline. In Pipeline scripts will always return the master's system separator. Maybe it's better to propose a new step in Pipeline Utility steps Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43911) Environment variables can't be used in agent configuration
Title: Message Title efo plo commented on JENKINS-43911 Re: Environment variables can't be used in agent configuration Would also like to have this implemented. We need to dynamically assign a label based on branch, so that branches of Team A run on the resources of that team, etc. We contact Consul for the mapping of branch to label. Currently this is not possible as the label _expression_ is evaluated before the pipeline is run, not at the beginning of the relevant step, so any changes to variables or environment do not affect the node where the step is run. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54512) can not change workspace in k8s pipeline
Title: Message Title runze xia commented on JENKINS-54512 Re: can not change workspace in k8s pipeline Carlos Sanchez yes i have tried with `dir`, It also ditn't work properly, there are similar errors Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
