[JIRA] (JENKINS-60757) "poll: false" has no effect in scm (and git) pipeline steps
Title: Message Title
Aleksandr Mezin created an issue
Jenkins / JENKINS-60757
"poll: false" has no effect in scm (and git) pipeline steps
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-scm-step-plugin
Created:
2020-01-14 07:49
Priority:
Minor
Reporter:
Aleksandr Mezin
When I create a pipeline job with the following Jenkinsfile (not from SCM):
properties([pipelineTriggers([pollSCM('H/2 * * * *')])])
node() {
git(url: 'https://github.com/amezin/jenkins-cant-stop-polling.git', poll: false)
}
I expect that it won't be triggered when I push something to https://github.com/amezin/jenkins-cant-stop-polling However, it becomes triggered by SCM change. Polling log ends with "Changes found". Real use case is more complex and involves a custom SCM plugin, but this simple pipeline with git step behaves the same way. As a workaround, I'll add 'poll' option to our custom SCM plugin (and make its compareRemoteRevisionWith() return NO_CHANGES when set to false). I do not know any workaround for Git and Mercurial plugins (I'd prefer not to build a custom patched version of these).
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Jagjeet Chadha edited a comment on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Can anyone tell me how o fix the mentioned issue? I have started seeing the same error on Jenkins 2.213 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.188450.151859845.7860.1578986460401%40Atlassian.JIRA.
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Jagjeet Chadha commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Can anyone tell me how o fix the mentioned 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.188450.151859845.7847.1578986400377%40Atlassian.JIRA.
[JIRA] (JENKINS-60398) Maven Artifact ChoiceListProvider (Nexus) sorting issue
Title: Message Title Stephan Watermeyer commented on JENKINS-60398 Re: Maven Artifact ChoiceListProvider (Nexus) sorting issue What is this second issue about? If you want to have this issue fixed you should have raised a PullRequest (a git commit with the fix for your problem) on Github, so that i can merge your commit to the master branch and build a new release. 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.203453.157587112.7843.1578985380220%40Atlassian.JIRA.
[JIRA] (JENKINS-60753) Creating PR in reference to JENKINS-60398
Title: Message Title Stephan Watermeyer assigned an issue to Unassigned Jenkins / JENKINS-60753 Creating PR in reference to JENKINS-60398 Change By: Stephan Watermeyer Assignee: Stephan Watermeyer 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.204012.1578975714000.7841.1578985200270%40Atlassian.JIRA.
[JIRA] (JENKINS-60756) Failed to deploy. java.io.IOException: Remote call on JNLP4-connect connection from x.x.x.x/x.x.x.x:abcd failed
Title: Message Title
Jagjeet Chadha created an issue
Jenkins / JENKINS-60756
Failed to deploy. java.io.IOException: Remote call on JNLP4-connect connection from x.x.x.x/x.x.x.x:abcd failed
Issue Type:
Bug
Assignee:
Karl-Heinz Marbaise
Components:
java-client-api
Created:
2020-01-14 06:56
Environment:
Jenkins 2.213
Labels:
jenkins jnlp-slave
Priority:
Major
Reporter:
Jagjeet Chadha
{{ArtifactDeployer] - Starting deployment from the post-action ... [ArtifactDeployer] - [ERROR] - Failed to deploy. java.io.IOException: Remote call on JNLP4-connect connection from x.x.x.x/x.x.x.x:abcd failed [ArtifactDeployer] - [ERROR] - Remote call on JNLP4-connect connection from x.x.x.x/x.x.x.x:abcd failed Build step '[ArtifactDeployer] - Deploy the artifacts from build workspace to remote locations' changed build result to FAILURE Build step '[ArtifactDeployer] - Deploy the artifacts from build workspace to remote locations' marked build as failure Skipping Cobertura coverage report as build was not UNSTABLE or better ...}}
[JIRA] (JENKINS-60755) Unable to add Jobs to view as List View Section. Observing "java.lang.ClassCastException: JSON keys must be strings."
Title: Message Title Aman Raj created an issue Jenkins / JENKINS-60755 Unable to add Jobs to view as List View Section. Observing "java.lang.ClassCastException: JSON keys must be strings." Issue Type: Bug Assignee: Unassigned Components: views-containing-job-plugin Created: 2020-01-14 06:08 Environment: Production Priority: Major Reporter: Aman Raj On trying to add jobs to Jenkins view as a List View Section, I am observing the issue "java.lang.ClassCastException: JSON keys must be strings." Screencast - https://screencast-o-matic.com/watch/cYV21ivk7u Stack trace error - java.lang.ClassCastException: JSON keys must be strings. at net.sf.json.JSONObject._fromJSONObject(JSONObject.java:874) at net.sf.json.JSONObject.fromObject(JSONObject.java:152) at net.sf.json.JSONSerializer.toJSON(JSONSerializer.java:108) at net.sf.json.AbstractJSON._processValue(AbstractJSON.java:239) at net.sf.json.JSONObject._processValue(JSONObject.java:2599) at net.sf.json.JSONObject.processValue(JSONObject.java:2665) at net.sf.json.JSONObject.element(JSONObject.java:1738) at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:980) at net.sf.json.JSONObject._fromString(JSONObject.java:1145) at net.sf.json.JSONObject.fromObject(JSONObject.java:162) at net.sf.json.JSONObject.fromObject(JSONObject.java:132) at org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:1020) at hudson.plugins.sectioned_view.SectionedView.submit(SectionedView.java:153) at hudson.model.View.doConfigSubmit(View.java:992) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at
[JIRA] (JENKINS-60754) Jenkins test harness InjectedTest freezes on 8+ core machines
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-60754 Jenkins test harness InjectedTest freezes on 8+ core machines Issue Type: Bug Assignee: Oliver Gondža Components: jenkins-test-harness Created: 2020-01-14 05:41 Environment: 8 core FreeBSD machine 50+ Core Ubuntu 16.04 machine Platform Labeler plugin, git client plugin, and git plugin with concurrency greater than 1 Priority: Major Reporter: Mark Waite When I run tests with platformlabeler plugin commit 361a98 and git plugin commit f2b6b39 on a computer with 8 cores or more, the InjectedTest hangs. Both are using the most recent parent pom and the jenkins test harness version provided by that parent pom. Add Comment
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite When creating a build in Jenkins using GIT and Bitbucket, I get the following error FATAL: Null value not allowed as an environment variable: GIT_URL_2java.lang.IllegalArgumentException: Null value not allowed as an environment variable: GIT_URL_2 at hudson.EnvVars.put(EnvVars.java:356) at hudson.EnvVars.put(EnvVars.java:74) at hudson.plugins.git.GitSCM.buildEnvVars(GitSCM.java:1265) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:927) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1075) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILUREProblem requires that a repository is added to the Freestyle job definition which has *no repository URL*. If the repository URL is non-empty, the problem does not occur. See [my sample job|https://github.com/MarkEWaite/docker-lfs/commit/e88aae2f8a0268664d731e557fc0da184a94f495] to duplicate the problem. Add Comment
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite Priority: Minor Trivial 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.174799.1475161307000.7825.1578978540791%40Atlassian.JIRA.
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite When creating a build in Jenkins using GIT and Bitbucket, I get the following error FATAL: Null value not allowed as an environment variable: GIT_URL_2java.lang.IllegalArgumentException: Null value not allowed as an environment variable: GIT_URL_2 at hudson.EnvVars.put(EnvVars.java:356) at hudson.EnvVars.put(EnvVars.java:74) at hudson.plugins.git.GitSCM.buildEnvVars(GitSCM.java:1265) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:927) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1075) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE Problem requires that a repository is added to the Freestyle job definition which has *no repository URL*. If the repository URL is non-empty, the problem does not occur. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-38608) Null value not allowed as an environment variable: GIT_URL_2
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-38608 Null value not allowed as an environment variable: GIT_URL_2 Change By: Mark Waite Priority: Blocker Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174799.1475161307000.7811.1578978121269%40Atlassian.JIRA.
[JIRA] (JENKINS-46588) Pipeline Branch Specifier "blank for 'any'" fails
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-46588 Pipeline Branch Specifier "blank for 'any'" fails Change By: Mark Waite In Pipeline Job, "Branches to build configuration" it's said "blanck for any" but it fails when I manually trigger the build with :java.lang.IllegalArgumentException: Invalid refspec refs/heads/**see screen shots for more details is there any other way to build all branches? *Work around the issue by disabling lightweight checkout in the job definition* 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.184913.1504266201000.7797.1578977761032%40Atlassian.JIRA.
[JIRA] (JENKINS-46588) Pipeline Branch Specifier "blank for 'any'" fails
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-46588 Pipeline Branch Specifier "blank for 'any'" fails Change By: Mark Waite Priority: Blocker Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184913.1504266201000.7795.1578977760964%40Atlassian.JIRA.
[JIRA] (JENKINS-38127) Git plugin does not build arbitrary tags in history
Title: Message Title Mark Waite closed an issue as Won't Fix This bug report is requesting to build the same commit again based on a new tag name being assigned to the commit. The git plugin considers a SHA-1 as the key to decide if a build should be run again. Once a SHA-1 has been built, it won't be built again by the polling mechanism because it has already been built. Jenkins / JENKINS-38127 Git plugin does not build arbitrary tags in history Change By: Mark Waite Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You
[JIRA] (JENKINS-48137) Multibranch Pipeline: Concurrently spawned jobs fail to checkout due to TLS
Title: Message Title Mark Waite closed an issue as Cannot Reproduce That message is a failure of command line git, not a failure of the git plugin. The git plugin won't be modified to alter this behavior of command line git. Jenkins / JENKINS-48137 Multibranch Pipeline: Concurrently spawned jobs fail to checkout due to TLS Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group
[JIRA] (JENKINS-44816) Java Vm Crash while SCM Polling on SLES 11 and SLES 12
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-44816 Java Vm Crash while SCM Polling on SLES 11 and SLES 12 Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182874.1497246679000.7779.1578976740449%40Atlassian.JIRA.
[JIRA] (JENKINS-60398) Maven Artifact ChoiceListProvider (Nexus) sorting issue
Title: Message Title Sirisha Joel commented on JENKINS-60398 Re: Maven Artifact ChoiceListProvider (Nexus) sorting issue Hi Stephan Watermeyer, Created a PR JENKINS-60753 Can you verify if it has come through in the correct format? I work with Shyam and hence updating this case. Thank & Regards Sirisha 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.203453.157587112.7774.1578975840162%40Atlassian.JIRA.
[JIRA] (JENKINS-60753) Creating PR in reference to JENKINS-60398
Title: Message Title Sirisha Joel created an issue Jenkins / JENKINS-60753 Creating PR in reference to JENKINS-60398 Issue Type: Bug Assignee: Stephan Watermeyer Components: jenkinslint-plugin Created: 2020-01-14 04:21 Environment: Production Priority: Minor Reporter: Sirisha Joel Creating this PR in reference to JENKINS-60398 to get the release updated Add Comment
[JIRA] (JENKINS-60752) Print friendly message when View entered incorrectly
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-60752 Print friendly message when View entered incorrectly Change By: Joel Brown Labels: P4_VERIFY 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.204010.1578962417000.7761.1578964140083%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake commented on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar hi Federico Pellegrin actually here what I want is exclude this Dapper Packages (which is Dapper.dll) from generating my NunitFast Code coverage reports. eg: So I changed my code as you suggested. But after I include -excludebyfile or -filter like below to exclude Dapper packages I'm getting zero Code coverage output in NunitFast unit test reports. my new code is below: .$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll -excludebyfile:-[Dapper*] --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" even I tried with -filter option as well but I'm still get the below results which is zero output, I think these filtering options are only for exclude class or methods, but here we going to exclude an entire package (Dapper.dll), so is that why I'm getting below crazy out-put ? Could you suggest something new Federico Pellegrin ? Thanks ! 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
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-59308 Cobertura Code coverage all reports are showing in similar Change By: Amila Gunathilake Attachment: image-2020-01-14-06-32-26-863.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.201856.1568169015000.7754.1578963720288%40Atlassian.JIRA.
[JIRA] (JENKINS-13042) Unable to checkout SCM repository once for complex configuration matrixes
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-13042 Unable to checkout SCM repository once for complex configuration matrixes Change By: Mark Waite 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.143502.1331333931000.7740.1578963181221%40Atlassian.JIRA.
[JIRA] (JENKINS-13417) git-plugin: rev-parse dereferencing tags breaks on Windows
Title: Message Title Mark Waite closed an issue as Won't Fix The Jenkins git plugin does not test with cygwin git and does not plan to add support for cygwin git. Git for Windows is well maintained and well supported and is known to work with the Jenkins git plugin. Jenkins / JENKINS-13417 git-plugin: rev-parse dereferencing tags breaks on Windows Change By: Mark Waite 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
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Title: Message Title Mark Waite updated JENKINS-14575 Jenkins / JENKINS-14575 SCM checkout retry count not working Change By: Mark Waite Status: Reopened 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.145260.1343246886000.7716.1578962882498%40Atlassian.JIRA.
[JIRA] (JENKINS-14917) Build is not triggered for new tag (without new commit)
Title: Message Title Mark Waite updated JENKINS-14917 Jenkins / JENKINS-14917 Build is not triggered for new tag (without new commit) Change By: Mark Waite Status: Reopened 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.145618.1345807655000.7713.1578962882464%40Atlassian.JIRA.
[JIRA] (JENKINS-22591) Does not spawn build if a branch refers to the same SHA1 as another already built branch
Title: Message Title Mark Waite closed an issue as Won't Fix This behavior is deeply ingrained in the git plugin. Changing it would break many, many use cases. Won't fix. Jenkins / JENKINS-22591 Does not spawn build if a branch refers to the same SHA1 as another already built branch Change By: Mark Waite 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
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-59308 Cobertura Code coverage all reports are showing in similar Change By: Amila Gunathilake Attachment: image-2020-01-14-06-13-43-821.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.201856.1568169015000.7683.1578962580248%40Atlassian.JIRA.
[JIRA] (JENKINS-60752) Print friendly message when View entered incorrectly
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-60752 Print friendly message when View entered incorrectly Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-01-14 00:40 Priority: Trivial Reporter: Joel Brown When a view is created, look for common mistakes and print something to the console log that there may be a problem. Still keeping running – just print an info message. When the (incorrect) client gets used, the failure message logged doesn't offer any guidance as to what might be wrong. Things to look for: spaces in path that aren'ts. For example, there are three spaces in one view mapping line but not any quotes. left side ends with "..." but right side doesn't. And vice versa. Add Comment
[JIRA] (JENKINS-30339) Expand variables in Freestyle job 'local subdirectory' field
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-30339 Expand variables in Freestyle job 'local subdirectory' field Change By: Mark Waite Summary: Inconsistent GIT_BRANCH behaviour Expand variables in Freestyle job 'local subdirectory' field 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.164932.1441710831000.7680.1578962280301%40Atlassian.JIRA.
[JIRA] (JENKINS-60751) Support pr:reviewer:updated webhook to trigger builds
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-60751 Support pr:reviewer:updated webhook to trigger builds Issue Type: Improvement Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2020-01-14 00:27 Priority: Minor Reporter: Owen Mehegan It would be useful to be able to trigger a build if the PR reviewer list is changed after the PR is first opened. This happens pretty commonly, so for users who have a build workflow that is partly organized around reviewers, support for this hook event would be useful. Relevant code is here: https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.4.4/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/hooks/HookEventType.java Add Comment
[JIRA] (JENKINS-9016) Git creates usernames based on 'name' not the email.
Title: Message Title Mark Waite updated JENKINS-9016 Jenkins / JENKINS-9016 Git creates usernames based on 'name' not the email. Change By: Mark Waite Status: Reopened 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.139161.1299868575000.7658.1578961684936%40Atlassian.JIRA.
[JIRA] (JENKINS-25389) Allow push of tags created during the build
Title: Message Title Mark Waite updated JENKINS-25389 Jenkins / JENKINS-25389 Allow push of tags created during the build Change By: Mark Waite Status: Reopened 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.158953.1414735893000.7668.1578961685070%40Atlassian.JIRA.
[JIRA] (JENKINS-23299) Project building from tag builds at each polling interval
Title: Message Title Mark Waite updated JENKINS-23299 Jenkins / JENKINS-23299 Project building from tag builds at each polling interval Change By: Mark Waite Status: Reopened 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.155445.1401838289000.7666.1578961685040%40Atlassian.JIRA.
[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-12972 Add option to run 'git bisect' to find which commit added new bugs Change By: Mark Waite Component/s: git-bisect-plugin Component/s: git-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.143432.1330856879000.7594.1578961622261%40Atlassian.JIRA.
[JIRA] (JENKINS-13086) Clone to directory named for repository
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins Pipeline allows checkout to user defined directory names and allows multiple repositories to be used in a single Jenkins job. This won't be implemented in the git plugin because it is already available in Jenkins Pipeline Jenkins / JENKINS-13086 Clone to directory named for repository Change By: Mark Waite 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
[JIRA] (JENKINS-13228) Git Plugin should allow configuration of local subdirectory per repository
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins Pipeline allows configuration of a local subdirectory per repository in both declarative and scripted Pipelines. This will not be implemented in the git plugin because it can be done much more effectively with Pipelines. Jenkins / JENKINS-13228 Git Plugin should allow configuration of local subdirectory per repository Change By: Mark Waite 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
[JIRA] (JENKINS-42708) Expose the GIT_URL, BRANCH and COMMIT that originally triggered the build
Title: Message Title Mark Waite closed an issue as Won't Fix Won't implement further changes to support multiple SCM plugin. Use the Jenkins pipeline for multiple SCM use cases. Jenkins / JENKINS-42708 Expose the GIT_URL, BRANCH and COMMIT that originally triggered the build Change By: Mark Waite 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
[JIRA] (JENKINS-47524) Git verify-commit HEAD after checkout
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-47524 Git verify-commit HEAD after checkout Change By: Mark Waite Summary: " Git verify-commit HEAD after checkout " 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.185981.1508403862000.7561.1578960480196%40Atlassian.JIRA.
[JIRA] (JENKINS-50789) Create missing tests for P1 cases
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-50789 Create missing tests for P1 cases Change By: Mark Waite Assignee: Raul Arabaolaza 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.189899.1523615138000.7559.1578960300136%40Atlassian.JIRA.
[JIRA] (JENKINS-49757) Git plugin calls fetch twice per checkout
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-49757 Git plugin calls fetch twice per checkout Change By: Mark Waite Summary: Git plugin calls fetch twice for a single job per checkout 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.188703.151969992.7553.1578959940338%40Atlassian.JIRA.
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Martin Henschke commented on JENKINS-60649 Re: Bitbucket Server Integration plugin does not work for Pipelines Hi Trung, thanks for reporting this. We are aware of the issue and are looking at solutions. In the meantime, there is a workaround to this issue: Create your pipelines project as normal. Within that project, start a build of that project and wait for it to resolve (it does not need to be successful, just running it is enough) Once completed, click "configure" to go back to the project configuration Ensure the "Bitbucket Server trigger build after push" build trigger is checked Save the project configuration This should trigger the webhook to be created in Bitbucket Server. If you're having trouble with this solution, you can also create a webhook manually in your repository settings- create it with the URL `http:///bitbucket-server-webhook/trigger`, with the secret field empty, and with the "push" event checked. Feel free to reach out if you have any other issues. 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
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Udaya Sree commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error I am also facing the same issue with Jira Cloud and "Jira Trigger Plugin 1.0.0". Please let us know if anyone has fix to 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.194307.1537972591000.7539.1578957660257%40Atlassian.JIRA.
[JIRA] (JENKINS-60602) Bitbucket integration with Jenkins
Title: Message Title Alex Martynenko reopened an issue Jenkins / JENKINS-60602 Bitbucket integration with Jenkins Change By: Alex Martynenko Resolution: Not A Defect Status: Closed Reopened 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.203827.157762360.7515.1578951480317%40Atlassian.JIRA.
[JIRA] (JENKINS-60602) Bitbucket integration with Jenkins
Title: Message Title Alex Martynenko commented on JENKINS-60602 Re: Bitbucket integration with Jenkins Hi Christian Del Monte Thanks for respond. Right now my current scenario looks like: 1. Get date of latest release (by username, message) - git commit date (git log) Filter git log and find those data 2. Get list of merged pull requests after last release Curl -> to bitbucket API pull request with filtering: state: merged destination branch: develop updated_on (Result of step 1) (Check if updated_on is date when PR has been merged) 3. Parse response from Bitbucket API (Retrieve from PR "title" and "id") 4. Integrate output file (data with "title" and "id" after step 3) with Jenkins For me is more important step 4 right now. And the main question is: I will have output text file with all merged pull requests (after 3 steps). How is better to inject it to Jenkins in parametrised field? (showed on attachment release-notes.png) My logic is the next: Such field should have such ID, how to get it? And how is better to do such implementation? Some plugins or is possible via Jenkins API with proper CURL request? I mean to publish data that is specified in some text file directly to parametrised field. Thanks in advance. Regards, Alexander. 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-52019) Declarative build failures with Java 10
Title: Message Title
René Scheibe updated an issue
Jenkins / JENKINS-52019
Declarative build failures with Java 10
Change By:
René Scheibe
Building with more or less the bleeding edge versions for Java 10 testing and running the simplest pipeline: {code:java} pipeline \ { agent anystages \ { stage('Say Hello') \ { steps \ { echo 'Hello World!' } } }} {code} I get the following logs with a stack trace: {code:java} Started by user unknown or anonymousRunning in Durability level: MAX_SURVIVABILITY[Pipeline] End of PipelineBUG! exception in phase 'class generation' in source unit 'jar:file:/var/jenkins_home/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy' unsupported Target MODULE at org.codehaus.groovy.vmplugin.v5.Java5.getElementCode(Java5.java:341) at org.codehaus.groovy.vmplugin.v5.Java5.configureAnnotationFromDefinition(Java5.java:234) at org.codehaus.groovy.vmplugin.v5.Java5.configureAnnotation(Java5.java:244) at org.codehaus.groovy.classgen.AnnotationVisitor.visit(AnnotationVisitor.java:97) at org.codehaus.groovy.classgen.ExtendedVerifier.visitAnnotation(ExtendedVerifier.java:252) at org.codehaus.groovy.classgen.ExtendedVerifier.visitAnnotations(ExtendedVerifier.java:139) at org.codehaus.groovy.classgen.ExtendedVerifier.visitConstructorOrMethod(ExtendedVerifier.java:95) at org.codehaus.groovy.classgen.ExtendedVerifier.visitMethod(ExtendedVerifier.java:91) at org.codehaus.groovy.ast.ClassNode.visitContents(ClassNode.java:1081) at org.codehaus.groovy.classgen.ExtendedVerifier.visitClass(ExtendedVerifier.java:74) at org.codehaus.groovy.control.CompilationUnit$17.call(CompilationUnit.java:804) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:254) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:250) at groovy.lang.GroovyClassLoader.recompile(GroovyClassLoader.java:766) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:718) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:787) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:553) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell$TimingLoader.loadClass(CpsGroovyShell.java:158) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:553) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:677) at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:787) at
[JIRA] (JENKINS-60750) Setup wizard asks to set root URL even when already set if admin user creation skipped
Title: Message Title Jesse Glick updated JENKINS-60750 Jenkins / JENKINS-60750 Setup wizard asks to set root URL even when already set if admin user creation skipped Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204008.1578945652000.7469.1578946380080%40Atlassian.JIRA.
[JIRA] (JENKINS-60750) Setup wizard asks to set root URL even when already set if admin user creation skipped
Title: Message Title Jesse Glick started work on JENKINS-60750 Change By: Jesse Glick 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.204008.1578945652000.7468.1578945720083%40Atlassian.JIRA.
[JIRA] (JENKINS-60750) Setup wizard asks to set root URL even when already set if admin user creation skipped
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-60750 Setup wizard asks to set root URL even when already set if admin user creation skipped Issue Type: Bug Assignee: Jesse Glick Components: core Created: 2020-01-13 20:00 Labels: lts-candidate setup-wizard Priority: Minor Reporter: Jesse Glick JENKINS-31661 included a new panel in the setup wizard to define the Jenkins root URL. This was supposed to be skipped when the root URL had already been defined by other means (such as a Groovy init hook), but that logic only worked when proceeding through the panel to create an initial admin user; if you picked the link to skip creating a separate user (just keeping the default admin user) then you were still asked to configure the root URL. Add Comment
[JIRA] (JENKINS-60625) Dashboard rendering blocked on UpdateSite.getJSONObject
Title: Message Title Oliver Gondža commented on JENKINS-60625 Re: Dashboard rendering blocked on UpdateSite.getJSONObject I would like to give this change some more soaking time so postponing to 2.204.3 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.203858.1578003601000.7436.1578944820267%40Atlassian.JIRA.
[JIRA] (JENKINS-60625) Dashboard rendering blocked on UpdateSite.getJSONObject
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60625 Dashboard rendering blocked on UpdateSite.getJSONObject Change By: Oliver Gondža Labels: 2.204.2-rejected lts-candidate performance 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.203858.1578003601000.7430.1578944700353%40Atlassian.JIRA.
[JIRA] (JENKINS-60554) EscapedMarkupFormatter does not properly handle a null argument
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60554 EscapedMarkupFormatter does not properly handle a null argument Change By: Oliver Gondža Labels: lts 2.204.2 - candidate 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.203661.1576837156000.7422.1578944400276%40Atlassian.JIRA.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title Patrick Ruckstuhl updated JENKINS-43894 Jenkins / JENKINS-43894 Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Change By: Patrick Ruckstuhl Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181422.149329524.7410.1578943620742%40Atlassian.JIRA.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title D Pasto edited a comment on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Good call [~tario] ! It works! I assumed I could just use environment variables that I believe existed, but whether it doesn't really exist, or the plugin only sees a subset of environment variables, it correctly found the reference repo using an env defined in the node! It's not as clean as an automatically defined variable would be, but it looks like it works! We have a good sized repo so even though we're on-prem, I was seeing 2+ minute fetches for those stages where the hard-coded path was wrong, but this brings it down to 15 seconds in my first few runs Edit: forgot the most important part - this lets me define a single path (using forward slashes) that works on both Linux and Windows nodes. 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.181422.149329524.7396.1578942540367%40Atlassian.JIRA.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title D Pasto commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Good call Patrick Ruckstuhl Unable to render embedded object: File ( It works) not found. I assumed I could just use environment variables that I believe existed, but whether it doesn't really exist, or the plugin only sees a subset of environment variables, it correctly found the reference repo using an env defined in the node! It's not as clean as an automatically defined variable would be, but it looks like it works! We have a good sized repo so even though we're on-prem, I was seeing 2+ minute fetches for those stages where the hard-coded path was wrong, but this brings it down to 15 seconds in my first few runs 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.181422.149329524.7385.1578942060314%40Atlassian.JIRA.
[JIRA] (JENKINS-59107) User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2)
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59107 User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2) Change By: Oliver Gondža Labels: lts 2.204.2 - candidate 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.201530.1566934526000.7379.1578941280438%40Atlassian.JIRA.
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60351 can not disable the retries of Util.delete Change By: Oliver Gondža Labels: lts 2.204.2 - candidate 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.203368.1575383029000.7376.1578941040316%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Oliver Gondža Labels: 2.204.1-rejected lts 2.204.2 - candidate fixed regression 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.199072.1556795988000.7361.1578940680601%40Atlassian.JIRA.
[JIRA] (JENKINS-60167) AtomicFileWriter performance issue on CephFS in case of Empty File creation
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60167 AtomicFileWriter performance issue on CephFS in case of Empty File creation Change By: Oliver Gondža Labels: 2.204.1-rejected lts 2.204.2 - candidate 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.203119.1573721452000.7357.1578940500176%40Atlassian.JIRA.
[JIRA] (JENKINS-60092) ArrayIndexOutOfBoundsException in getPrimaryView when no view exists
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60092 ArrayIndexOutOfBoundsException in getPrimaryView when no view exists Change By: Oliver Gondža Labels: exception lts 2.204.2 - candidate fixed exception 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.202937.1573145385000.7354.1578940440239%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Put on my test server, works great. Not sure you need to do it any differently but up to you. 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.203842.1577724088000.7352.1578939120129%40Atlassian.JIRA.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title Patrick Ruckstuhl commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo D Pasto did you actually specify HOME as an explicit variable on the node or are you just depending on an existing environment variable. If I remember correctly we're using this with some 4.* version for a while, but always with explicitly specified node variables. 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.181422.149329524.7339.1578937800287%40Atlassian.JIRA.
[JIRA] (JENKINS-60625) Dashboard rendering blocked on UpdateSite.getJSONObject
Title: Message Title Jesse Glick commented on JENKINS-60625 Re: Dashboard rendering blocked on UpdateSite.getJSONObject Note that I am still inclined to look for ways to patch or bypass this library to minimize even background CPU, but that would be tracked as a separate issue and presumably not be an LTS candidate. 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.203858.1578003601000.7335.1578937380053%40Atlassian.JIRA.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title Mark Waite commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo I've proposed automatic repository caching as a Google Summer of Code idea and have offered the pull request as a starting point for consideration. Have you tried the alternative that is described by Jesse Glick? It seems like it would work in your case if you perform the environment variable expansion in the Jenkins checkout statement. 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.181422.149329524.7325.1578937020404%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Daniel Beck Released As: Jenkins 2.208 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.199072.1556795988000.7310.1578936361304%40Atlassian.JIRA.
[JIRA] (JENKINS-60092) ArrayIndexOutOfBoundsException in getPrimaryView when no view exists
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-60092 ArrayIndexOutOfBoundsException in getPrimaryView when no view exists Change By: Daniel Beck Released As: Jenkins 2.206 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.202937.1573145385000.7307.1578936361220%40Atlassian.JIRA.
[JIRA] (JENKINS-60625) Dashboard rendering blocked on UpdateSite.getJSONObject
Title: Message Title Daniel Beck updated JENKINS-60625 Jenkins / JENKINS-60625 Dashboard rendering blocked on UpdateSite.getJSONObject Change By: Daniel Beck Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203858.1578003601000.7302.1578936300292%40Atlassian.JIRA.
[JIRA] (JENKINS-60625) Dashboard rendering blocked on UpdateSite.getJSONObject
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-60625 Dashboard rendering blocked on UpdateSite.getJSONObject Change By: Daniel Beck Released As: Jenkins 2.212 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.203858.1578003601000.7304.1578936300326%40Atlassian.JIRA.
[JIRA] (JENKINS-60484) Blue Ocean organization folder job can't be parsed by 2.204.1-rc build
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-60484 Blue Ocean organization folder job can't be parsed by 2.204.1-rc build Change By: Daniel Beck Labels: lts-candidate 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.203573.1576374806000.7300.1578936240294%40Atlassian.JIRA.
[JIRA] (JENKINS-20608) Cannot use Env Var in Task Name
Title: Message Title Olivier Schiavo updated JENKINS-20608 Jenkins / JENKINS-20608 Cannot use Env Var in Task Name Change By: Olivier Schiavo Status: In Review 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.152129.1384545932000.7286.1578936121560%40Atlassian.JIRA.
[JIRA] (JENKINS-20608) Cannot use Env Var in Task Name
Title: Message Title Olivier Schiavo updated JENKINS-20608 Jenkins / JENKINS-20608 Cannot use Env Var in Task Name Change By: Olivier Schiavo Resolution: Fixed Status: Closed In Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152129.1384545932000.7284.1578936121515%40Atlassian.JIRA.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title D Pasto commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Any updates on releasing this? I verified it does not work on my v4.0 plugin (can resolve $JENKINS_HOME but not $HOME so is useless) and the changelog does not list it for that or v4.1 beta We have pipelines across many nodes, including different platforms, so we can't take full advantage of reference repos (the workaround of manually re-defining the checkout for every stage would be maintenance disaster) — we need a way of dynamically building the reference repo path per node per pipeline. 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.181422.149329524.7261.1578935340301%40Atlassian.JIRA.
[JIRA] (JENKINS-60685) Kubernetes plugin crashes from v1.22.4
Title: Message Title MARY Olivier commented on JENKINS-60685 Re: Kubernetes plugin crashes from v1.22.4 It's ok on 1.16.3 too. Just little issue created for that JENKINS-60735 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.203929.1578472634000.7243.1578932640347%40Atlassian.JIRA.
[JIRA] (JENKINS-59808) Jenkins PR(pull request) build fails for 1st time
Title: Message Title Christian Del Monte closed an issue as Not A Defect Jenkins / JENKINS-59808 Jenkins PR(pull request) build fails for 1st time Change By: Christian Del Monte 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.202539.1571256507000.7241.1578932340326%40Atlassian.JIRA.
[JIRA] (JENKINS-60418) issue of Integration webhook with bitbucket when using bitbucket pull and push plugin
Title: Message Title Christian Del Monte closed an issue as Cannot Reproduce Jenkins / JENKINS-60418 issue of Integration webhook with bitbucket when using bitbucket pull and push plugin Change By: Christian Del Monte Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203480.1575978042000.7239.1578932280318%40Atlassian.JIRA.
[JIRA] (JENKINS-60418) issue of Integration webhook with bitbucket when using bitbucket pull and push plugin
Title: Message Title Christian Del Monte commented on JENKINS-60418 Re: issue of Integration webhook with bitbucket when using bitbucket pull and push plugin Hi, the 404 problem doesn't seem to be related to the plugin itself. It could depend on your Jenkins installation / configuration 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.203480.1575978042000.7237.1578932280292%40Atlassian.JIRA.
[JIRA] (JENKINS-58607) Problem configuring BitBucket Push and Pull Request Plugin
Title: Message Title Christian Del Monte closed an issue as Not A Defect Jenkins / JENKINS-58607 Problem configuring BitBucket Push and Pull Request Plugin Change By: Christian Del Monte Status: In Progress 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.200768.1563829779000.7233.1578932160589%40Atlassian.JIRA.
[JIRA] (JENKINS-60602) Bitbucket integration with Jenkins
Title: Message Title Christian Del Monte closed an issue as Not A Defect Jenkins / JENKINS-60602 Bitbucket integration with Jenkins Change By: Christian Del Monte 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.203827.157762360.7235.1578932160641%40Atlassian.JIRA.
[JIRA] (JENKINS-60602) Bitbucket integration with Jenkins
Title: Message Title Christian Del Monte commented on JENKINS-60602 Re: Bitbucket integration with Jenkins Hello Alex Martynenko thank you for your message. As we understand it, there are in you scenario two unrelated jobs: the first one is triggered automatically in case of merged PR, whereas the second one is a parametrized job triggered manually. The first one gives to disposal some Info, which are somehow collected. These infos are afer that going to be used from the second job as parameters. You could write those infos in a file, using a bash command, so you can read them directly as a file parameter. Hopefully this can help you. For issues and proposals, please use the github repo of the plugin. https://github.com/jenkinsci/bitbucket-push-and-pull-request-plugin Thanks 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.203827.157762360.7230.1578932040178%40Atlassian.JIRA.
[JIRA] (JENKINS-56290) Impossible to Add Streams with Exact Names to Multibranch Pipeline
Title: Message Title Kevin Williamson commented on JENKINS-56290 Re: Impossible to Add Streams with Exact Names to Multibranch Pipeline Doc update released 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.197869.155119216.7228.1578931861830%40Atlassian.JIRA.
[JIRA] (JENKINS-60363) Include TLSv1.2 instruction in P4-Plugin Doc
Title: Message Title Kevin Williamson updated JENKINS-60363 Doc update released Jenkins / JENKINS-60363 Include TLSv1.2 instruction in P4-Plugin Doc Change By: Kevin Williamson Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203386.1575459106000.7223.1578931861341%40Atlassian.JIRA.
[JIRA] (JENKINS-60745) NullPointerException from Severity.collectSeveritiesFrom
Title: Message Title Arno Moonen commented on JENKINS-60745 Re: NullPointerException from Severity.collectSeveritiesFrom These jobs are generated using XML manipulation in Job DSL (so we can also "compile" the DSL without a Jenkins CI environment). I might have missed these XML properties. I'll have a look at the Job DSL tomorrow. 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.204001.1578905757000.7221.1578930840273%40Atlassian.JIRA.
[JIRA] (JENKINS-60745) NullPointerException from Severity.collectSeveritiesFrom
Title: Message Title
Ulli Hafner edited a comment on JENKINS-60745
Re: NullPointerException from Severity.collectSeveritiesFrom
Seems that the health descriptor section {{ ... }} is missing. Did you edit these files manually? Do your other builds also have a missing {{ ... }} section? Or is this just missing for some specific builds.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204001.1578905757000.7219.1578930420121%40Atlassian.JIRA.
[JIRA] (JENKINS-60745) NullPointerException from Severity.collectSeveritiesFrom
Title: Message Title
Ulli Hafner edited a comment on JENKINS-60745
Re: NullPointerException from Severity.collectSeveritiesFrom
Seems that the health descriptor section {{ is missing. Did you edit these files manually? Do your other builds also have a missing {{
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.204001.1578905757000.7217.1578930360452%40Atlassian.JIRA.
[JIRA] (JENKINS-60745) NullPointerException from Severity.collectSeveritiesFrom
Title: Message Title Ulli Hafner commented on JENKINS-60745 Re: NullPointerException from Severity.collectSeveritiesFrom Seems that the health descriptor section is missing. Did you edit these files manually? Do your other builds also have a missing section? Or is this just missing for some specific builds. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204001.1578905757000.7215.1578930360399%40Atlassian.JIRA.
[JIRA] (JENKINS-59834) Retry Mechanism for collate and analyze when it fails
Title: Message Title Sandeep Moras commented on JENKINS-59834 Re: Retry Mechanism for collate and analyze when it fails Hi Daniel Danan. Happy New Year! Has this change been prioritized. Do you have an update on when this might be available? This is being a blocker for our CICD adoption. 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.202569.157136096.7213.1578929100197%40Atlassian.JIRA.
[JIRA] (JENKINS-60685) Kubernetes plugin crashes from v1.22.4
Title: Message Title tsukasa omoto updated an issue Jenkins / JENKINS-60685 Kubernetes plugin crashes from v1.22.4 Change By: tsukasa omoto Comment: v1.22.5 fixes 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.203929.1578472634000.7200.1578928260729%40Atlassian.JIRA.
[JIRA] (JENKINS-60685) Kubernetes plugin crashes from v1.22.4
Title: Message Title tsukasa omoto updated JENKINS-60685 v1.22.5 fixes this issue! Jenkins / JENKINS-60685 Kubernetes plugin crashes from v1.22.4 Change By: tsukasa omoto Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60685) Kubernetes plugin crashes from v1.22.4
Title: Message Title tsukasa omoto commented on JENKINS-60685 Re: Kubernetes plugin crashes from v1.22.4 v1.22.5 fixes 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.203929.1578472634000.7199.1578928260707%40Atlassian.JIRA.
[JIRA] (JENKINS-49411) Error creating view inside view
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-49411 Error creating view inside view Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188287.1517941624000.7168.1578924600444%40Atlassian.JIRA.
[JIRA] (JENKINS-51291) 'new view' wrong url - not relative
Title: Message Title Jesse Glick commented on JENKINS-51291 Re: 'new view' wrong url - not relative JENKINS-48447 broke usage in folders: inside a folder, the New View link actually creates a view at the Jenkins root. 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.190625.1526291411000.7161.1578924420718%40Atlassian.JIRA.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site/Server
Title: Message Title Mark Slipets edited a comment on JENKINS-47309 Re: Plugin || Confluence Publisher || Not working with confluence cloud site/Server Hi [~jhansche], please consider to review [https://github.com/jenkinsci/confluence-publisher-plugin/pull/15 , ] , might be useful in scope of current 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.185734.1507283628000.7151.1578924420484%40Atlassian.JIRA.
[JIRA] (JENKINS-51291) 'new view' wrong url - not relative
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51291 'new view' wrong url - not relative Change By: Jesse Glick Labels: folders newbie-friendly view 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.190625.1526291411000.7145.1578924360407%40Atlassian.JIRA.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site/Server
Title: Message Title Mark Slipets commented on JENKINS-47309 Re: Plugin || Confluence Publisher || Not working with confluence cloud site/Server Hi Joe Hansche, please consider to review https://github.com/jenkinsci/confluence-publisher-plugin/pull/15, might be useful in scope of current 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.185734.1507283628000.7135.1578924241624%40Atlassian.JIRA.
[JIRA] (JENKINS-60749) Authenticate using OAuth in JIRA plugin
Title: Message Title Arno Moonen created an issue Jenkins / JENKINS-60749 Authenticate using OAuth in JIRA plugin Issue Type: Improvement Assignee: Unassigned Components: jira-plugin Created: 2020-01-13 12:56 Environment: Jenkins ver. 2.204.1 JIRA plugin 3.0.11 Priority: Major Reporter: Arno Moonen Since Jira Server does not have the ability to generate API tokens (similar to what Jira Cloud offers), I think it would be better if the Jira plugin would also support OAuth, so I do not have to put the general password for my service account into Jenkins. Add Comment
[JIRA] (JENKINS-60679) java.lang.NoSuchMethodError: org.bouncycastle.asn1.DERNull.equals(Lorg/bouncycastle/asn1/ASN1Encodable;)Z
Title: Message Title Arnaud Lefebvre commented on JENKINS-60679 Re: java.lang.NoSuchMethodError: org.bouncycastle.asn1.DERNull.equals(Lorg/bouncycastle/asn1/ASN1Encodable;)Z Thank you very much for your hint, it was indeed somehow related to the classpath, I've been told a specific version of bouncycastle was used in our icedtea8 java package to mainly avoid TLS issues, which explains why I still have the issue on my laptop and our jenkins. We'll switch to Java 11 which solves the problem. Again, thanks for your time on this matter 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.203923.1578419245000.7120.1578920040486%40Atlassian.JIRA.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site/Server
Title: Message Title Moses Thomas updated an issue Jenkins / JENKINS-47309 Plugin || Confluence Publisher || Not working with confluence cloud site/Server Change By: Moses Thomas Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185734.1507283628000.7111.1578919980656%40Atlassian.JIRA.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site/Server
Title: Message Title Moses Thomas updated an issue Jenkins / JENKINS-47309 Plugin || Confluence Publisher || Not working with confluence cloud site/Server Change By: Moses Thomas Summary: Plugin || Confluence Publisher || Not working with confluence cloud site /Server Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185734.1507283628000.7101.1578919741140%40Atlassian.JIRA.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site
Title: Message Title
Moses Thomas commented on JENKINS-47309
Re: Plugin || Confluence Publisher || Not working with confluence cloud site
We also have this related issue for our Confluence server 7.1.0 (Critical issue) Confluence Publisher plugin in version 1.8, please could you provide solution or workaround
07:04:56 [confluence] - Uploading file: test_report.csv (application/octet-stream)
07:04:56 ERROR: Unable to upload file...
07:04:56 AxisFault
07:04:56 faultCode: \{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
07:04:56 faultSubcode:
07:04:56 faultString: org.xml.sax.SAXException: Bad types (class com.atlassian.confluence.rpc.soap.beans.RemoteAttachment - long)
07:04:56 faultActor:
07:04:56 faultNode:
07:04:56 faultDetail:
07:04:56 {}faultData:"http://lang.java" xsi:nil="true" xsi:type="ns2:Throwable"/>"http://lang.java" xsi:nil="true" xsi:type="ns3:Exception"/>"xsd:string">Bad types (class com.atlassian.confluence.rpc.soap.beans.RemoteAttachment - long)
07:04:56 \{http://xml.apache.org/axis/}hostname:teamwork.gigaset.com
07:04:56
07:04:56 org.xml.sax.SAXException: Bad types (class com.atlassian.confluence.rpc.soap.beans.RemoteAttachment -> long)
07:04:56 at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
07:04:56 at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
07:04:56 at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
07:04:56 at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:609)
07:04:56 at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1776)
07:04:56 at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2964)
07:04:56 at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
07:04:56 at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:118)
07:04:56 at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:504)
07:04:56 at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:849)
07:04:56 at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:778)
07:04:56 at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
07:04:56 at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
07:04:56 at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:642)
07:04:56 at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:326)
07:04:56 at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
07:04:56 at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
07:04:56 at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
07:04:56 at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
07:04:56 at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
07:04:56 at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
07:04:56 at org.apache.axis.client.Call.invoke(Call.java:2767)
07:04:56 at org.apache.axis.client.Call.invoke(Call.java:2443)
07:04:56 at
[JIRA] (JENKINS-60748) clone options (--rev) not well suited for large repositories
Title: Message Title
Dirk Heinrichs updated an issue
Jenkins / JENKINS-60748
clone options (--rev) not well suited for large repositories
Change By:
Dirk Heinrichs
When cloning a large repository (~2G, general_delta format), using --rev to only clone a specific branch can lead to vastly increased clone times as shown in the table below:||--rev default||--uncompressed||elapsed time|||(/)|(/)|16:12,05||(/)|(-)|15:21,41||(-)|(/)|1:24,41||(-)|(-)|8:18,24|The times have been measured on a Linux host using the following command:{code:java}time hg clone {code}As can be seen, adding _ --rev default_ default increases the clone time dramatically, while adding _ -- uncompressed_ uncompressed yields the fastest result. On Windows, the situation is even worse (~3 - 4 times slower).It would therefor be nice if one could enable or disable clone options on a per-job basis, or even have something similar to Git plugin's "Additional Behaviours" which allows to specify "Advanced clone behaviours" (and many more).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
