[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Mark Waite commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Expected to release in git client plugin 3.1.2 within the next 2 weeks 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.198962.1556378819000.4701.1582337580800%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Mark Waite updated JENKINS-57205 Jenkins / JENKINS-57205 Null pointer exception in JGit pre-build merge Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198962.1556378819000.4699.1582337580754%40Atlassian.JIRA.
[JIRA] (JENKINS-61187) Option to create ref-spec to target branch when cloning
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61187 Option to create ref-spec to target branch when cloning Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204731.1582328137000.4677.1582331880268%40Atlassian.JIRA.
[JIRA] (JENKINS-61187) Option to create ref-spec to target branch when cloning
Title: Message Title Mark Waite commented on JENKINS-61187 Re: Option to create ref-spec to target branch when cloning Multibranch pipelines for most repository providers (GitHub, Bitbucket, GitLab, and Gitea) should already automatically narrow the refspec for the specific branch in the checkout. The branch source provider in the git plugin does not perform that narrowing, but users can perform the narrowing themselves in the checkout command if needed. 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.204731.1582328137000.4675.1582331880181%40Atlassian.JIRA.
[JIRA] (JENKINS-61131) vsphere-cloud: Credentials selection is broken in UI since 2.22
Title: Message Title Steve Bouché commented on JENKINS-61131 Re: vsphere-cloud: Credentials selection is broken in UI since 2.22 Also seeing this on LTS 2.204.2 with plugin 2.22. Downgrading to 2.21 allows credential selection. 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.204653.1582040133000.4672.1582331340193%40Atlassian.JIRA.
[JIRA] (JENKINS-61187) Option to create ref-spec to target branch when cloning
Title: Message Title Stephane Odul updated an issue Jenkins / JENKINS-61187 Option to create ref-spec to target branch when cloning Change By: Stephane Odul Summary: Option to create ref-spec to target branch when cloning 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.204731.1582328137000.4670.1582329000401%40Atlassian.JIRA.
[JIRA] (JENKINS-61187) Option to ref-spec to target branch when cloning
Title: Message Title Stephane Odul created an issue Jenkins / JENKINS-61187 Option to ref-spec to target branch when cloning Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2020-02-21 23:35 Environment: Jenkins 2.204.2 Git Plugin 4.1.1 Priority: Major Reporter: Stephane Odul We use the Kubernetes plugin to run Jenkins which means that every stage in our pipelines will always perform a full clone. Unfortunately this mean that the current behavior is to fetch all the branches which uses a lot more bandwidth and RAM than we need. We can can manually set the ref-spec to the target branch if the job will only run against a specific branch, but we have many pipelines that are allowed to run against any branch, in which case the ref-spec need to be left to default. We've had many pipeline failures caused by the git process running out of memory, or by the git server timing out. To work around these issue we have a shell script that wraps the git cli to: retry the commands 5 times, with backoff logic so stages won't fail due to a network/server glitch while fetching. detect if $BRANCH is set (GIT_BRANCH is not exposed here) and if the wildcard ref-spec is set massage the git fetch command to only fetch the targeted branch. This approach has lowered out git checkout times by 3x, the number of objects by 10x and the amount of data fetched from the git server by over 10x. It would be great to add theses 2 improvements directly into the git plugin so that others can benefit from this. We do know about the option to
[JIRA] (JENKINS-61186) Add lastBuild/consoleFull#footer as an option
Title: Message Title Patrick Einheber created an issue Jenkins / JENKINS-61186 Add lastBuild/consoleFull#footer as an option Issue Type: Improvement Assignee: Fred G Components: extra-columns-plugin Created: 2020-02-21 23:04 Priority: Minor Reporter: Patrick Einheber It would be great to have lastBuild/consoleFull#footer instead of lastBuild/console as an option for a couple of reasons: Default to loading the whole log Default to seeing the last lines of a stopped/errored job. Add Comment
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Brian Ray updated JENKINS-57205 Jenkins / JENKINS-57205 Null pointer exception in JGit pre-build merge Change By: Brian Ray 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.198962.1556378819000.4657.1582323480613%40Atlassian.JIRA.
[JIRA] (JENKINS-61147) load build parameters during repository scan
Title: Message Title Brandon Fryslie commented on JENKINS-61147 Re: load build parameters during repository scan This is not necessary if you are using the Job DSL plugin (which you should be regardless). Instead of defining the parameters in your Jenkinsfile, put them in the .groovy file where your Job DSL is defined. Then the parameters are available on the initial run of the job. https://jenkinsci.github.io/job-dsl-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.204677.1582120134000.4654.1582321920130%40Atlassian.JIRA.
[JIRA] (JENKINS-61185) Not picking up JIRA key issues in commit messages
Title: Message Title Tony Nguyen created an issue Jenkins / JENKINS-61185 Not picking up JIRA key issues in commit messages Issue Type: Bug Assignee: Rafal Myslek Attachments: Untitled.png Components: atlassian-jira-software-cloud-plugin Created: 2020-02-21 21:13 Priority: Minor Reporter: Tony Nguyen I entered the Jira key issue into a commit message as testing but it doesn't seem to be detecting it after build in Jenkins. Picture attached of a test run Add Comment
[JIRA] (JENKINS-61179) Project configuration for JMS Plugin not saved
Title: Message Title Scott Hebert commented on JENKINS-61179 Re: Project configuration for JMS Plugin not saved This bug seems to have been introduced in version 1.1.6 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.204722.1582294215000.4650.1582318140177%40Atlassian.JIRA.
[JIRA] (JENKINS-58991) Getting NullPointerException com.bettercloud.vault.api.Logical.read after upgrade to 2.3.0
Title: Message Title
Micheal Waltz edited a comment on JENKINS-58991
Re: Getting NullPointerException com.bettercloud.vault.api.Logical.read after upgrade to 2.3.0
We just started getting this issue again after updating to Jenkins 2.204.2 and the Hashicorp Vault Plugin ( [ https://github.com/jenkinsci/hashicorp-vault-plugin ] ) from 2.5.0 to 3.1.1. Error is,{code:java}FATAL: nulljava.lang.NullPointerException at com.datapipe.jenkins.vault.VaultBuildWrapper.provideEnvironmentVariablesFromVault(VaultBuildWrapper.java:139) at com.datapipe.jenkins.vault.VaultBuildWrapper.setUp(VaultBuildWrapper.java:94) at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:146) at hudson.model.Build$BuildExecution.doRun(Build.java:157) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1853) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427) {code}We've rolledback the plugin to 2.5.0 but it still occurs. Verified the Global jenkins-plugin is set to KV Engine Version 1, and all the jobs are set to 1 as well. Vault server version is 1.0.2 and KV 2 is not enabled.Oddly this only happens with triggered jobs: timer, github push/PR, triggered from another job. Running or re-building a job manually will not have this error. I will to open opened an issue in the hashicorp-vault-plugin Github repo as well for this and will update this issue with the corresponding issue ID : https://github . com/jenkinsci/hashicorp-vault-plugin/issues/81 Other information: * Jenkins Master OS: Ubuntu 18.04.4 * Jenkins Version: 2.204.2 * Vault Plugin Version: 2.5.0 and 3.1.1 * Java version: OpenJDK Runtime Environment (build 1.8.0_242-8u242-b08-0ubuntu3~18.04-b08) * Vault Server version: 1.0.2 * Jenkins jobs all run on remote jenkins agents using swarm plugin version 3.18 and Java 1.8.0-8u242 on Ubuntu 18.04
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58991) Getting NullPointerException com.bettercloud.vault.api.Logical.read after upgrade to 2.3.0
Title: Message Title Micheal Waltz commented on JENKINS-58991 Re: Getting NullPointerException com.bettercloud.vault.api.Logical.read after upgrade to 2.3.0 We just started getting this issue again after updating to Jenkins 2.204.2 and the Hashicorp Vault Plugin (https://github.com/jenkinsci/hashicorp-vault-plugin) from 2.5.0 to 3.1.1. Error is, FATAL: nulljava.lang.NullPointerException at com.datapipe.jenkins.vault.VaultBuildWrapper.provideEnvironmentVariablesFromVault(VaultBuildWrapper.java:139) at com.datapipe.jenkins.vault.VaultBuildWrapper.setUp(VaultBuildWrapper.java:94) at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:146) at hudson.model.Build$BuildExecution.doRun(Build.java:157) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1853) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427) We've rolledback the plugin to 2.5.0 but it still occurs. Verified the Global jenkins-plugin is set to KV Engine Version 1, and all the jobs are set to 1 as well. Vault server version is 1.0.2 and KV 2 is not enabled. Oddly this only happens with triggered jobs: timer, github push/PR, triggered from another job. Running or re-building a job manually will not have this error. I will to open an issue in the hashicorp-vault-plugin Github repo as well for this and will update this issue with the corresponding issue ID. Other information: Jenkins Master OS: Ubuntu 18.04.4 Jenkins Version: 2.204.2 Vault Plugin Version: 2.5.0 and 3.1.1 Java version: OpenJDK Runtime Environment (build 1.8.0_242-8u242-b08-0ubuntu3~18.04-b08) Vault Server version: 1.0.2 Jenkins jobs all run on remote jenkins agents using swarm plugin version 3.18 and Java 1.8.0-8u242 on Ubuntu 18.04 Add Comment
[JIRA] (JENKINS-56377) console log hangs in web browser after upgrade
Title: Message Title Sundar Kasturi commented on JENKINS-56377 Re: console log hangs in web browser after upgrade We are facing the same issue.. Chrome does not respond or return back on a large console log Any idea when this would be resolved? Seems open from about a year. 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.197963.1551669398000.4594.1582316040254%40Atlassian.JIRA.
[JIRA] (JENKINS-61183) Can't able save golbal config in jenkins after install Extension Plugin (V2.68)
Title: Message Title Alex Earl commented on JENKINS-61183 Re: Can't able save golbal config in jenkins after install Extension Plugin (V2.68) If you are blocked, then downgrade. I will look when I have time. 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.204727.1582313426000.4592.1582315980165%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Brian Ray commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Thanks Mark Waite. PR is imminent, Monday at the latest but more likely this afternoon. The full Git Client test suite just finished up here on my local, rebased-to-fresh-master branch. 100% success and and coverage on getTags() via Jacoco (largely in thanks to existing tests to be sure). After grabbing some lunch I should be able slip the plugin into my test Jenkins and confirm the downstream NPE is squashed. 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.198962.1556378819000.4578.1582315200227%40Atlassian.JIRA.
[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue
Title: Message Title Usama Tariq created an issue Jenkins / JENKINS-61184 Jira Trigger Plugin Issue Issue Type: Bug Assignee: Dan Alvizu Attachments: image-2020-02-22-00-49-41-433.png, image-2020-02-22-00-50-33-023.png Components: jira-ext-plugin, jira-trigger-plugin Created: 2020-02-21 19:56 Environment: jenkins 2.176 Jira trigget 1.0.0 jira ext-plugin 0.9 Labels: plugin Priority: Critical Reporter: Usama Tariq Hi Team, We have integrated the jenkins with jira for auto deployment. but now we are facing the issue that its not triggering the auto deployment. After consulting with Jira cloud team they intimated us that its happening due to the deprecation of the use of specific keys that contain information to identify users, such as "name" and "userKey". https://confluence.atlassian.com/cloud/blog/2018/06/say-goodbye-to-usernames-in-atlassian-cloud https://community.developer.atlassian.com/t/announcement-reminder-on-removal-of-user-names/34111 And we are using username and password in Jira trigger plugin. However, they temporarily disabled a feature flag that enables on our instance. Which causes the auto deployment issue for time being, But its just for 4-5 days. After that they permanently uses accountid option then again we will stuck in huge trouble. The main concern to raise this issue with your team is that Jira trigger plugin and Jira ext plugin
[JIRA] (JENKINS-61183) Can't able save golbal config in jenkins after install Extension Plugin (V2.68)
Title: Message Title Jegatheswari Balakrishnan commented on JENKINS-61183 Re: Can't able save golbal config in jenkins after install Extension Plugin (V2.68) Hi Alex Earl Could you please help me to resolve this issue ASAP. Actually we are blocking with this. 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.204727.1582313426000.4565.1582314960113%40Atlassian.JIRA.
[JIRA] (JENKINS-10622) Cron Tab still running even when the job is disabled
Title: Message Title Daniel Beck commented on JENKINS-10622 Re: Cron Tab still running even when the job is disabled Based on Kanstantsin Shautsou's comment, this might not be newbie-friendly after all. 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.140816.1312821348000.4560.1582314840239%40Atlassian.JIRA.
[JIRA] (JENKINS-61183) Can't able save golbal config in jenkins after install Extension Plugin (V2.68)
Title: Message Title Jegatheswari Balakrishnan created an issue Jenkins / JENKINS-61183 Can't able save golbal config in jenkins after install Extension Plugin (V2.68) Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 2020-02-21 19:30 Priority: Blocker Reporter: Jegatheswari Balakrishnan We have installed "Email Extension Plugin (V2.68)" in our jenkins . After install, we couldn't able to save Golbal configuration (Manage jenkins -> configure system), its giving below error. Jenkins Version :Jenkins ver. 2.176.1 net.sf.json.JSONException: JSONObject["hudson-plugins-emailext-ExtendedEmailPublisher"] is not a JSONObject. at net.sf.json.JSONObject.getJSONObject(JSONObject.java:2006) at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:3763) at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:3729) 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 org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at
[JIRA] (JENKINS-60117) Rework sorting for the Enabled columns of Installed in Plugin Manager
Title: Message Title Sam Hrncir commented on JENKINS-60117 Re: Rework sorting for the Enabled columns of Installed in Plugin Manager I'll also look into this and report. 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.202966.157338165.4548.1582313460873%40Atlassian.JIRA.
[JIRA] (JENKINS-10622) Cron Tab still running even when the job is disabled
Title: Message Title
Sam Hrncir edited a comment on JENKINS-10622
Re: Cron Tab still running even when the job is disabled
From reviewing {color:#172b4d}Gregory Boissinot I ' s account, he seems to be no longer activly contributing for the past 3 years and should be taken off as assignee ll have a look at this bug.{color} issue and report
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.140816.1312821348000.4540.1582313400199%40Atlassian.JIRA.
[JIRA] (JENKINS-10622) Cron Tab still running even when the job is disabled
Title: Message Title Sam Hrncir assigned an issue to Sam Hrncir Jenkins / JENKINS-10622 Cron Tab still running even when the job is disabled Change By: Sam Hrncir Assignee: Gregory Boissinot Sam Hrncir 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.140816.1312821348000.4538.1582313340356%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Mark Waite commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Brian Ray I'm starting the planning so that we can release a new version of the git plugin in the next 1-2 weeks. I'd love to include this fix in a git client plugin release at the same time, if it is ready. Thanks again for your work on it! There are 3 pull requests to the git plugin that need to be evaluated and merged before the release. Wanted you to know the plans for the release in case that information helps 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.198962.1556378819000.4520.1582312680253%40Atlassian.JIRA.
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title Allan C commented on JENKINS-56594 Re: Warnings trend graph has no y-axis legend Replicated this bug successfully on Jenkins 2.204.2, with a simple freestyle sample (execute shell). 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.198216.1552902109000.4514.1582312380688%40Atlassian.JIRA.
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title Allan C updated an issue Jenkins / JENKINS-56594 Warnings trend graph has no y-axis legend Change By: Allan C Attachment: image-2020-02-21-14-12-22-279.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.198216.1552902109000.4507.1582312380519%40Atlassian.JIRA.
[JIRA] (JENKINS-61118) Run condition trigger missing from v2.68 (Email Extension Plugin)
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-61118 Run condition trigger missing from v2.68 (Email Extension Plugin) Change By: Alex Earl Assignee: Alex Earl 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.204632.1581961109000.4494.1582312020405%40Atlassian.JIRA.
[JIRA] (JENKINS-61118) Run condition trigger missing from v2.68 (Email Extension Plugin)
Title: Message Title Alex Earl commented on JENKINS-61118 Re: Run condition trigger missing from v2.68 (Email Extension Plugin) The Run condition trigger is not part of email-ext. 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.204632.1581961109000.4496.1582312020449%40Atlassian.JIRA.
[JIRA] (JENKINS-61118) Run condition trigger missing from v2.68 (Email Extension Plugin)
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-61118 Run condition trigger missing from v2.68 (Email Extension Plugin) Change By: Alex Earl Component/s: run-condition-extras-plugin Component/s: email-ext-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.204632.1581961109000.4492.1582312020375%40Atlassian.JIRA.
[JIRA] (JENKINS-60811) java connection refused error while setting up mail notification
Title: Message Title Alex Earl closed an issue as Not A Defect Jenkins / JENKINS-60811 java connection refused error while setting up mail notification Change By: Alex Earl 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.204143.1579331247000.4490.1582311900490%40Atlassian.JIRA.
[JIRA] (JENKINS-60811) java connection refused error while setting up mail notification
Title: Message Title Alex Earl edited a comment on JENKINS-60811 Re: java connection refused error while setting up mail notification Connections refused means your configuration is incorrect somehow. The server is refusing your connection. This is not a big bug in the 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.204143.1579331247000.4488.1582311900407%40Atlassian.JIRA.
[JIRA] (JENKINS-60011) mail to user full name not email
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-60011 mail to user full name not email Change By: Alex Earl Component/s: email-ext-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.202831.1572585332000.4484.1582311840215%40Atlassian.JIRA.
[JIRA] (JENKINS-60011) mail to user full name not email
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-60011 mail to user full name not email Change By: Alex Earl Assignee: Alex Earl 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.202831.1572585332000.4486.1582311840244%40Atlassian.JIRA.
[JIRA] (JENKINS-60117) Rework sorting for the Enabled columns of Installed in Plugin Manager
Title: Message Title Sam Hrncir assigned an issue to Kalana Wijethunga Jenkins / JENKINS-60117 Rework sorting for the Enabled columns of Installed in Plugin Manager Change By: Sam Hrncir Assignee: Sam Hrncir Kalana Wijethunga 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.202966.157338165.4481.1582311780422%40Atlassian.JIRA.
[JIRA] (JENKINS-58972) Jenkins not sending valid report email attachment for failure build
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-58972 Jenkins not sending valid report email attachment for failure build Change By: Alex Earl Status: Open Closed Resolution: Incomplete 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.201319.1565986545000.4478.1582311780378%40Atlassian.JIRA.
[JIRA] (JENKINS-60117) Rework sorting for the Enabled columns of Installed in Plugin Manager
Title: Message Title Sam Hrncir assigned an issue to Sam Hrncir Jenkins / JENKINS-60117 Rework sorting for the Enabled columns of Installed in Plugin Manager Change By: Sam Hrncir Assignee: Kalana Wijethunga Sam Hrncir 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.202966.157338165.4468.1582311720517%40Atlassian.JIRA.
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-59198 NullPointerException in hudson.util.Secret$1.convert Change By: Alex Earl Status: In Progress Closed Resolution: Incomplete 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.201641.1567478279000.4462.1582311660305%40Atlassian.JIRA.
[JIRA] (JENKINS-58570) smtpHost ignored when CasC attempts to set smtpUsername / smtpPassword
Title: Message Title Alex Earl commented on JENKINS-58570 Re: smtpHost ignored when CasC attempts to set smtpUsername / smtpPassword You could try adding a field like this: extendedEmailPublisher: overrideGlobalSettings: true 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.200720.1563529454000.4460.1582311600146%40Atlassian.JIRA.
[JIRA] (JENKINS-60927) Use disconnect icon for Disconnect and Delete Agent
Title: Message Title Sam Hrncir assigned an issue to Sam Hrncir Jenkins / JENKINS-60927 Use disconnect icon for Disconnect and Delete Agent Change By: Sam Hrncir Assignee: Sam Hrncir 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.204324.1580417196000.4458.1582311540207%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Brian Ray started work on JENKINS-57205 Change By: Brian Ray 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.198962.1556378819000.4451.1582311300593%40Atlassian.JIRA.
[JIRA] (JENKINS-61169) Non-Serializable exception thrown on wrong object
Title: Message Title
Matthew Eggers updated an issue
Jenkins / JENKINS-61169
Non-Serializable exception thrown on wrong object
Change By:
Matthew Eggers
I am getting an exception when attempting to serialize a groovy Map that I've generated:{code:java}an exception which occurred: in field groovy.lang.Closure.delegate in object Script1$_run_closure1@30d6aac5 in field com. nike.acid. pipeline.configuration.adaptors.AdvancedClientAdaptor.clientConverter in object com. nike.acid. pipeline.configuration.adaptors.AdvancedClientAdaptor@629f71ba in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@2c17fa09 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@1635b321 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@146f27c2 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@19d1436 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@1d8bbdc9 in field com.cloudbees.groovy.cps.Continuable.e in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@39c61bdb in field org.jenkinsci.plugins.workflow.cps.CpsThread.program in object org.jenkinsci.plugins.workflow.cps.CpsThread@7ebbe670 in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@3b2aa9f8 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@3b2aa9f8Caused: java.io.NotSerializableException: Script1 {code}The problem here is, I'm not asking {{AdvancedClientAdaptor}} to persist the {{clientConverter}} field (It has Closures in it). I'm asking it to persist a JsonStringified groovy map. The issue appears to be in the {{AdvanceClientAdaptor}} class I've written. It accepts groovy map that it performs transformations on. Here is a trivial example: {code:java}def Map = [ targetConfig: [ foo: "bar" ], clientConverter: [ foo: { targetConfig, value -> targetConfig['foo'] = value }]] {code} The {{AdvancedClientConverter}} class basically accepts this Map as an input, assigns 2 member property variables to _each_ of the 2 map fields above:{code:java}class AdvancedClientConverter implements Serializable { Map targetConfig Map clientConverter def steps //running groovy instance AdvancedClientConverter(Map converterMap, def steps) { this.clientConverter = converterMap.clientConverter this.targetConfig = converterMap.targetConfig this.steps = steps } def converterOperation() { this.targetConfig.foo = this.clientConverter.foo(this.targetConfig, "baz"); String fileString = JsonOutput.prettyPrint(JsonOutput.toJson(targetConfig))} steps.echo ("final config: ${fileString}") steps.writeFile file: "FinalConfig.text", text: fileString return target }} {code}The above is all invoked in a running Jenkins
[JIRA] (JENKINS-49742) Multi-line string seems to be broken when triggered from the pipeline.
Title: Message Title Sam Hrncir assigned an issue to Sam Hrncir Jenkins / JENKINS-49742 Multi-line string seems to be broken when triggered from the pipeline. Change By: Sam Hrncir Assignee: Sam Hrncir 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.188685.1519653887000.4440.1582310400206%40Atlassian.JIRA.
[JIRA] (JENKINS-60021) Scan all builds only re-scans failed builds
Title: Message Title Adam Brousseau commented on JENKINS-60021 Re: Scan all builds only re-scans failed builds Sorry for the question here, where do I find the "Scan all builds" button? 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.202844.1572622669000.4437.1582307160203%40Atlassian.JIRA.
[JIRA] (JENKINS-18666) Submodule reference
Title: Message Title boris ivan updated an issue Jenkins / JENKINS-18666 Submodule reference Change By: boris ivan Method underlined textMethod `submoduleUpdate` should accept `reference` the same way as `clone` does.git submodule update --init --recursive --reference $referenceSpeeds up submodule update when using a local mirror. 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.150014.1373318147000.4414.1582304940420%40Atlassian.JIRA.
[JIRA] (JENKINS-55559) net.sf.json.JSONException: Invalid JSON String with Octopus Deploy Deployment plugin
Title: Message Title
alex poole commented on JENKINS-9
Re: net.sf.json.JSONException: Invalid JSON String with Octopus Deploy Deployment plugin
Big help thanks David, thought I was going mad with my sample JSON refusing to parse. NB to others, same issue when using readJSON() in the Pipeline Utility plugin: https://jenkins.io/doc/pipeline/steps/pipeline-utility-steps/ Instead of trusting others' JSON to come pre-trimmed, just read it in and trim it as David suggests;
def configString = readFile("userfile.json")
configString = configString.trim()
def configJSON = readJSON text: configString
The "file" version of readJSON is unusable unless you can guarantee no top/tail whitespace and/or you don't care if it breaks the pipeline Cheers Alex
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.196721.1547427129000.4406.1582304640189%40Atlassian.JIRA.
[JIRA] (JENKINS-60222) Centos 8, not working email send - TLC error
Title: Message Title Alex Earl closed an issue as Not A Defect Jenkins / JENKINS-60222 Centos 8, not working email send - TLC error Change By: Alex Earl 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.203195.1574241065000.4396.1582303860347%40Atlassian.JIRA.
[JIRA] (JENKINS-61179) Project configuration for JMS Plugin not saved
Title: Message Title Scott Hebert started work on JENKINS-61179 Change By: Scott Hebert 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.204722.1582294215000.4391.1582303680255%40Atlassian.JIRA.
[JIRA] (JENKINS-61179) Project configuration for JMS Plugin not saved
Title: Message Title Scott Hebert commented on JENKINS-61179 Re: Project configuration for JMS Plugin not saved I have reproduced this. Thanks for the report! 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.204722.1582294215000.4393.1582303680281%40Atlassian.JIRA.
[JIRA] (JENKINS-40443) Possibility to know the current stage in a Pipeline
Title: Message Title Frank Escobar commented on JENKINS-40443 Re: Possibility to know the current stage in a Pipeline It would be good if we can get the stageName and stageResult 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.177110.1481724538000.4381.1582303440299%40Atlassian.JIRA.
[JIRA] (JENKINS-61130) "ignoring quality gate result for one build" feature seems not to work
Title: Message Title
R. F. edited a comment on JENKINS-61130
Re: "ignoring quality gate result for one build" feature seems not to work
The official Pipeline Syntax documentation is: # 1. Ignore Quality Gate (Default for ignoreQualityGate: false):If checked, then the last finished build of the reference job will be used as baseline no matter if the quality gate of that build has been passed or not." ... Jenkins will mark all builds as unstable until the issues have been resolved." # 2. Ignore Failed Builds (Default for ignoreFailedBuilds: true):If checked, then only successful or unstable builds will be considered as baseline. I have noticed that:1. It seems like that against the documentation "unstable builds" are treated as failed!Even if QualityGate is configured with unstable: true neither the "Reset quality gate" button is displayed nor after re-running the job the previous UNSTABLE build is concidered as new baseline. {noformat} 00:02:39.415 [Static Analysis] Attaching ResultAction with ID 'analysis' to run 'XYZ/aa/develop #12'.00:02:39.436 [Static Analysis] Using reference build 'XYZ/aa/develop #10' to compute new, fixed, and outstanding issues00:02:39.436 [Static Analysis] Issues delta (vs. reference build): outstanding: 61, new: 52, fixed: 100:02:39.436 [Static Analysis] Evaluating quality gates00:02:39.436 [Static Analysis] -> PASSED - New (errors only): 0 - Quality QualityGate: 100:02:39.436 [Static Analysis] -> PASSED - New (severity high only): 0 - Quality QualityGate: 100:02:39.436 [Static Analysis] -> WARNING - New (severity normal only): 51 - Quality QualityGate: 400:02:39.436 [Static Analysis] -> PASSED - New (severity low only): 1 - Quality QualityGate: 1000:02:39.436 [Static Analysis] -> Some quality gates have been missed: overall result is WARNING00:02:39.436 [Static Analysis] Enabling health report (Healthy=1, Unhealthy=12, Minimum Severity=LOW)00:02:39.483 [Static Analysis] Created analysis result for 113 issues (found 52 new issues, fixed 1 issues) {noformat} This explains why adding "ignoreQualityGate: true" to my pipeline did not solve my problem because the parameter ignoreFailedBuilds was still true (default).2. Since "unstable" and "failed" builds are treated equally the plugin now would force me to set "ignoreFailedBuilds: false".If I would do this then defining a QualityGate does not realy make sense anymore because the baseline is always the previous build of the last one.Even if I would define a QualityGate and set it to unstable I cannot differenciate between UNSTABLE (publish SNAPSHOTS) and FAILED (abort and do not publish RELEASE) anymore because the plugin checks the build status and not its quality gate status.Or am I missing something?
Add Comment
[JIRA] (JENKINS-61130) "ignoring quality gate result for one build" feature seems not to work
Title: Message Title R. F. commented on JENKINS-61130 Re: "ignoring quality gate result for one build" feature seems not to work The official Pipeline Syntax documentation is: Ignore Quality Gate (Default for ignoreQualityGate: false): If checked, then the last finished build of the reference job will be used as baseline no matter if the quality gate of that build has been passed or not. " ... Jenkins will mark all builds as unstable until the issues have been resolved." Ignore Failed Builds (Default for ignoreFailedBuilds: true): If checked, then only successful or unstable builds will be considered as baseline. I have noticed that: 1. It seems like that against the documentation "unstable builds" are treated as failed! Even if QualityGate is configured with unstable: true neither the "Reset quality gate" button is displayed nor after re-running the job the previous UNSTABLE build is concidered as new baseline. 00:02:39.415 [Static Analysis] Attaching ResultAction with ID 'analysis' to run 'XYZ/aa/develop #12'. 00:02:39.436 [Static Analysis] Using reference build 'XYZ/aa/develop #10' to compute new, fixed, and outstanding issues 00:02:39.436 [Static Analysis] Issues delta (vs. reference build): outstanding: 61, new: 52, fixed: 1 00:02:39.436 [Static Analysis] Evaluating quality gates 00:02:39.436 [Static Analysis] -> PASSED - New (errors only): 0 - Quality QualityGate: 1 00:02:39.436 [Static Analysis] -> PASSED - New (severity high only): 0 - Quality QualityGate: 1 00:02:39.436 [Static Analysis] -> WARNING - New (severity normal only): 51 - Quality QualityGate: 4 00:02:39.436 [Static Analysis] -> PASSED - New (severity low only): 1 - Quality QualityGate: 10 00:02:39.436 [Static Analysis] -> Some quality gates have been missed: overall result is WARNING 00:02:39.436 [Static Analysis] Enabling health report (Healthy=1, Unhealthy=12, Minimum Severity=LOW) 00:02:39.483 [Static Analysis] Created analysis result for 113 issues (found 52 new issues, fixed 1 issues) This explains why adding "ignoreQualityGate: true" to my pipeline did not solve my problem because the parameter ignoreFailedBuilds was still true (default). 2. Since "unstable" and "failed" builds are treated equally the plugin now would force me to set "ignoreFailedBuilds: false". If I would do this then defining a QualityGate does not realy make sense anymore because the baseline is always the previous build of the last one. Even if I would define a QualityGate and set it to unstable I cannot differenciate between UNSTABLE (publish SNAPSHOTS) and FAILED (abort and do not publish RELEASE) anymore because the plugin checks the build status and not its quality gate status. Or am I missing something?
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Stefan Cordes commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON JsonParseUtil is released in version 5.2.0, see https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid#comment-137009716 Kamil Cichy commented on pull request #93: JRJC-240: Added support for accountId. Hello everyone, First of all I’m sorry it took so long to merge this PR. This is because this plugin is not supported. It means nobody is watching the PR queue and we don’t have any time budgeted to work on this. You should really thank @Andy Heinzer for nudging us to merge it I reviewed the code to ensure it was backwards-compatible. Then I had to do some extra work to fix the CI for this plugin (it’s been broken since 8.4.0). Only then I was able to release it (the second attempt was successful). I’m only writing this to justify our inability to support this plugin properly. What seems to be a single “merge” click was in fact a couple of hours of work. Anyway, this PR is merged, plugin version 5.2.0 has been released. Hopefully better late than ever. Kamil Jira Server and DC developer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Stefan Cordes commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error 5.2.0 is release, see https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid#comment-137009716 Kamil Cichy commented on pull request #93: JRJC-240: Added support for accountId. Hello everyone, First of all I’m sorry it took so long to merge this PR. This is because this plugin is not supported. It means nobody is watching the PR queue and we don’t have any time budgeted to work on this. You should really thank @Andy Heinzer for nudging us to merge it I reviewed the code to ensure it was backwards-compatible. Then I had to do some extra work to fix the CI for this plugin (it’s been broken since 8.4.0). Only then I was able to release it (the second attempt was successful). I’m only writing this to justify our inability to support this plugin properly. What seems to be a single “merge” click was in fact a couple of hours of work. Anyway, this PR is merged, plugin version 5.2.0 has been released. Hopefully better late than ever. Kamil Jira Server and DC developer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-44456) Provide a way to access a stage name from within the stage and its contents
Title: Message Title Frank Escobar edited a comment on JENKINS-44456 Re: Provide a way to access a stage name from within the stage and its contents It would be better if we can get the current stage name and the *RESULT*. **On that way we can take decisions based on current stage result in the post conditions . 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.182284.1495556078000.4339.1582300320350%40Atlassian.JIRA.
[JIRA] (JENKINS-44456) Provide a way to access a stage name from within the stage and its contents
Title: Message Title Frank Escobar commented on JENKINS-44456 Re: Provide a way to access a stage name from within the stage and its contents It would be better if we can get the current stage name and the RESULT. **On that way we can take decisions based on current stage result. 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.182284.1495556078000.4326.1582300080366%40Atlassian.JIRA.
[JIRA] (JENKINS-57557) JCasC: Branch discovery traits failure in config roundtrips (strategyId)
Title: Message Title Francisco Fernández updated JENKINS-57557 Jenkins / JENKINS-57557 JCasC: Branch discovery traits failure in config roundtrips (strategyId) Change By: Francisco Fernández Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199468.155835070.4321.1582299060264%40Atlassian.JIRA.
[JIRA] (JENKINS-61182) When 2 projects have a repo with the same name in them, the plugin picks the first regardless of the project selected.
Title: Message Title ryan eberly created an issue Jenkins / JENKINS-61182 When 2 projects have a repo with the same name in them, the plugin picks the first regardless of the project selected. Issue Type: Bug Assignee: Unassigned Attachments: image-2020-02-21-10-27-42-301.png Components: bitbucket-plugin Created: 2020-02-21 15:28 Priority: Minor Reporter: ryan eberly we have a project called policy-api in both projects https://bitbucket.company.com/projects/JAVA https://bitbucket.company.com/projects/JAVAL When we chose the Java project, policy-api appears twice in the repository name list and regardless of which we select the repo url is always the JAVAL one. Add Comment
[JIRA] (JENKINS-44503) Build hangs and Eventually fails
Title: Message Title ryan eberly commented on JENKINS-44503 Re: Build hangs and Eventually fails We used to get this issue as well on Windows. Updating to latest version of git for windows resolved it. Maybe issue can be closed - IMO. 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.182339.1495784262000.4318.1582298580171%40Atlassian.JIRA.
[JIRA] (JENKINS-61181) JMS Plugin sends messages to an ActiveMQ topic instead of a queue
Title: Message Title
T.K. Z.V created an issue
Jenkins / JENKINS-61181
JMS Plugin sends messages to an ActiveMQ topic instead of a queue
Issue Type:
Bug
Assignee:
Scott Hebert
Components:
jms-messaging-plugin
Created:
2020-02-21 15:00
Environment:
Jenkins 2.204.2, JMS Messaging Plugin 1.1.13
Priority:
Major
Reporter:
T.K. Z.V
To reproduce: 1. Create an ActiveMQ provider: In global Jenkins configuration under "CI Monitor" "JMS Messaging Providers" add an ActiveMQ provider. Enable "Use queues rather than topics." Set the provider name to e.g. "Provider1". Set other parameters as appropriate and save the configuration. 2. Create a pipeline project (other types may not work, bug https://issues.jenkins-ci.org/browse/JENKINS-61179). 3. Add a script that would only send a message to the provider created above:
pipeline {
agent any
stages {
stage('Hello') {
steps {
sendCIMessage failOnError: true, messageContent: '',
messageProperties: '',
messageType: 'TestingStarted',
overrides: [:], providerName: 'Provider1'
}
}
}
}
4. Check the ActiveMQ server – a topic has been created rather than a queue. Setting a different queue with "overrides" parameter does not help – the message still goes to a topic with the same name. "waitForCIMessage" correctly works both with queues and topics.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Karl Wirth commented on JENKINS-55985 Re: Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Team Cloud - Thanks. I've let the devs know. 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.197398.1549406943000.4308.1582296480281%40Atlassian.JIRA.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-55985 Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Change By: Karl Wirth Comment: Raising to P1 to highlight to dev. 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.197398.1549406943000.4303.1582296240494%40Atlassian.JIRA.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Karl Wirth commented on JENKINS-55985 Re: Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Raising to P1 to highlight to dev. 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.197398.1549406943000.4299.1582296240446%40Atlassian.JIRA.
[JIRA] (JENKINS-61180) Cannot delete job after using webhook to bitbucket
Title: Message Title Sean Lyons updated an issue Jenkins / JENKINS-61180 Cannot delete job after using webhook to bitbucket Change By: Sean Lyons After setting up a test project job with the webhook functionality, and running a build, the project job can no longer be deleted , a . A log is attached. The project is a declarative 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.204723.1582295097000.4291.1582295220157%40Atlassian.JIRA.
[JIRA] (JENKINS-61180) Cannot delete job after using webhook to bitbucket
Title: Message Title Sean Lyons updated an issue Jenkins / JENKINS-61180 Cannot delete job after using webhook to bitbucket Change By: Sean Lyons After setting up a test project with the webhook functionality, the project can no longer be deleted, a log is attached. The project is a declarative 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.204723.1582295097000.4289.1582295160147%40Atlassian.JIRA.
[JIRA] (JENKINS-61180) Cannot delete job after using webhook to bitbucket
Title: Message Title Sean Lyons created an issue Jenkins / JENKINS-61180 Cannot delete job after using webhook to bitbucket Issue Type: Bug Assignee: Kristy Hughes Attachments: crash_trace.log Components: atlassian-bitbucket-server-integration-plugin Created: 2020-02-21 14:24 Environment: Jenkins Version: 2.176.1 Atlassian Bitbucket v5.16.2 Bitbucket Server Integration 1.0.4 Priority: Minor Reporter: Sean Lyons After setting up a test project with the webhook functionality, the project can no longer be deleted, a log is attached. The project is a declarative pipeline. Add Comment
[JIRA] (JENKINS-61179) Project configuration for JMS Plugin not saved
Title: Message Title T.K. Z.V created an issue Jenkins / JENKINS-61179 Project configuration for JMS Plugin not saved Issue Type: Bug Assignee: Scott Hebert Components: jms-messaging-plugin Created: 2020-02-21 14:10 Environment: Jenkins 2.204.2, JMS Messaging Plugin 1.1.13 Priority: Major Reporter: T.K. Z.V To reproduce: 1. Create a new freestyle project. 2. Add a build step "CI Notifier" or "CI Subscriber". 3. Enter any values in the forms for "CI Notifier" or "CI Subscriber". 4. Press "Save". 5. Open the project configuration again – the values you entered have disappeared, the configuration reverted to default values. Add Comment
[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Title: Message Title Vincent Latombe updated JENKINS-61178 Jenkins / JENKINS-61178 When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir Change By: Vincent Latombe 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.204721.1582289664000.4283.1582291920199%40Atlassian.JIRA.
[JIRA] (JENKINS-61177) "Accessing steps" again. Now "No tool named Maven found"
Title: Message Title
gek updated an issue
Jenkins / JENKINS-61177
"Accessing steps" again. Now "No tool named Maven found"
Change By:
gek
I trying to use an [ example | from [ docs| https://jenkins.io/doc/book/pipeline/shared-libraries/#accessing-steps] ]from docs . Copy and paste both of{quote}{color:#43}class {color}Utilities {color:#43}implements {color}Serializable { {color:#43}def {color}{color:#660e7a}steps{color} Utilities(steps) {{color:#43}this{color}.{color:#660e7a}steps {color}= steps} {color:#43}def {color}mvn(args) { {color:#660e7a}steps{color}.sh {color:#008000}"{color}$\{steps.tool {color:#008000}'Maven'{color}}{color:#008000}/bin/mvn -o {color}${args}{color:#008000}"{color} }}{quote}{quote}and{quote}{quote}{color:#808000}@{color}Library({color:#008000}'lib@trunk/pipelines/jlib/trunk'{color}) _{color:#43}import {color}derivative.Utilities{color:#43}def {color}utils = {color:#43}new {color}Utilities({color:#43}this{color}){color:#808080}{color}node { stage ({color:#008000}'some'{color}) { utils.mvn {color:#008000}'clean package'{color} }}{quote}and then get the following output:{quote}ERROR: No tool named Maven found{quote}I have tried to susbstitute 'Maven' to 'git' , because i'd like to pass git into shared lib. But getting same message:{quote}ERROR: No tool named git found{quote}I cannot understand, what exactly is {color:#660e7a}steps{color}.sh? Is it bash script?
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-61177) "Accessing steps" again. Now "No tool named Maven found"
Title: Message Title
gek edited a comment on JENKINS-61177
Re: "Accessing steps" again. Now "No tool named Maven found"
looks like it must not be a{quote}{color:#008000} {color:#660e7a} steps{color}.sh {color:#008000}"{color}$\{steps.tool {color:#008000}'Maven'\{color}}/bin/mvn -o {color}${args}{color:#008000}"{color} { color}{ quote}{color:#172b4d}but{color}{quote}{color:#172b4d} {color:#660e7a} this.{color}{color:#008000} {color:#008000}{color:#660e7a} steps{color}.sh {color:#008000}"{color}$\{steps.tool {color:#008000}'Maven'\{color}}/bin/mvn -o {color}${args}{color:#008000}"{color} {color}{color}{color} {quote}{color:#172b4d}or, in my case{color}{quote}{color:#172b4d} {color:#660e7a} this.{color}{color:#008000} {color:#008000}{color:#660e7a} steps{color}.git {color}{color}{color} {quote} *there is need to fix documentation.*
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.204719.1582282896000.4280.1582291560062%40Atlassian.JIRA.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Team Cloud commented on JENKINS-55985 Re: Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Karl Wirth exactly, we still have this issue that prevents us from upgrading. Unfortunately, we also hit the issue JENKINS-55737 that is fixed in 1.9.7. Now we're in the dilemma that we need to upgrade, but can't. 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.197398.1549406943000.4277.1582290780234%40Atlassian.JIRA.
[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Title: Message Title Vincent Latombe started work on JENKINS-61178 Change By: Vincent Latombe 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.204721.1582289664000.4275.1582289760172%40Atlassian.JIRA.
[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-61178 When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir Change By: Vincent Latombe Assignee: Vincent Latombe 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.204721.1582289664000.4273.1582289700541%40Atlassian.JIRA.
[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Title: Message Title
Vincent Latombe created an issue
Jenkins / JENKINS-61178
When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2020-02-21 12:54
Priority:
Minor
Reporter:
Vincent Latombe
The following Jenkinsfile fails
podTemplate(containers: [
containerTemplate(name: 'busybox', image: 'busybox', ttyEnabled: true, command: '/bin/cat', workingDir: '/src')
]) {
node (POD_LABEL) {
stage('Run') {
sh 'env | sort'
container('busybox') {
sh 'env | sort'
}
}
}
}
Whereas this one works
podTemplate(containers: [
containerTemplate(name: 'jnlp', image: 'jenkinsci/jnlp-slave:latest'),
containerTemplate(name: 'busybox', image: 'busybox', ttyEnabled: true, command: '/bin/cat', workingDir: '/src')
]) {
node (POD_LABEL) {
stage('Run') {
sh 'env | sort'
container('busybox') {
sh 'env | sort'
}
}
}
}
The reason is https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L130 calls
[JIRA] (JENKINS-60843) Support Secret File credential type
Title: Message Title Chris Kilding updated JENKINS-60843 Jenkins / JENKINS-60843 Support Secret File credential type Change By: Chris Kilding Status: In Review Resolved Resolution: Fixed Released As: 0.2.2 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.204201.1579778647000.4269.1582289700482%40Atlassian.JIRA.
[JIRA] (JENKINS-60843) Support Secret File credential type
Title: Message Title Chris Kilding updated JENKINS-60843 Jenkins / JENKINS-60843 Support Secret File credential type Change By: Chris Kilding 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.204201.1579778647000.4268.1582289700406%40Atlassian.JIRA.
[JIRA] (JENKINS-61121) Too many open files when using Resource root URL
Title: Message Title Daniel Beck updated JENKINS-61121 Jenkins / JENKINS-61121 Too many open files when using Resource root URL Change By: Daniel Beck Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.222 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.204636.1582020729000.4212.1582285740389%40Atlassian.JIRA.
[JIRA] (JENKINS-61177) "Accessing steps" again. Now "No tool named Maven found"
Title: Message Title
gek commented on JENKINS-61177
Re: "Accessing steps" again. Now "No tool named Maven found"
looks like it must not be a
steps.sh "${steps.tool 'Maven'{color}}/bin/mvn -o ${args}"
but
this.steps.sh "${steps.tool 'Maven'{color}}/bin/mvn -o ${args}"
or, in my case
this.steps.git
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.204719.1582282896000.4191.1582283760056%40Atlassian.JIRA.
[JIRA] (JENKINS-61177) "Accessing steps" again. Now "No tool named Maven found"
Title: Message Title
gek created an issue
Jenkins / JENKINS-61177
"Accessing steps" again. Now "No tool named Maven found"
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin
Created:
2020-02-21 11:01
Priority:
Minor
Reporter:
gek
I trying to use an example from docs. Copy and paste both of
class Utilities implements Serializable { def steps Utilities(steps) {{color:#43}this.steps = steps} def mvn(args) { steps.sh "${steps.tool 'Maven'{color}}/bin/mvn -o ${args}" } }
and
@Library('lib@trunk/pipelines/jlib/trunk') _ import derivative.Utilities def utils = new Utilities(this) node { stage ('some') { utils.mvn 'clean package' } }
and then get the following output:
ERROR: No tool named Maven found
I have tried to susbstitute 'Maven' to 'git' , because i'd like to pass git into shared lib. But getting same message:
ERROR: No tool named git found
I cannot understand, what exactly is steps.sh? Is it bash script?
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title
Stefan Cordes edited a comment on JENKINS-53794
Re: jira-trigger-plugin fails to trigger job and throws error
{quote}Merged pull requestMerged in master (pull request #93)78059d9Jakub Sławiński18 minutes ago{quote}[https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93] Due to "JRJC-240: Bump plugin version to 5.2.0-SNAPSHOT" it looks like next version will be 5.2.0 and not 5.1.7.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194307.1537972591000.4178.1582282440420%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Matej Dro commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error I stand corrected. 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.4164.1582282380386%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Stefan Cordes commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error Merged pull request Merged in master (pull request #93) 78059d9 Jakub Sławiński 18 minutes ago https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93 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.4150.1582282140337%40Atlassian.JIRA.
[JIRA] (JENKINS-61173) Audit trail plugin stop working unexpectedly
Title: Message Title Pierre Beitz commented on JENKINS-61173 Re: Audit trail plugin stop working unexpectedly An Nguyen provided stack is not related with the Audit Trail plugin but to a known issue with the Multiple SCM plugin: https://issues.jenkins-ci.org/browse/JENKINS-39598 Do you have more details about the issue with Audit Trail Plugin: what exactly do you mean by stopped working? Is there anything else in the logs that would explain an issue with the Audit Trail 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.204713.1582259655000.4147.1582281480140%40Atlassian.JIRA.
[JIRA] (JENKINS-61175) Provide different JiraIssueUpdater for cloud and server
Title: Message Title
Stefan Cordes updated an issue
Jenkins / JENKINS-61175
Provide different JiraIssueUpdater for cloud and server
Change By:
Stefan Cordes
According to Ben_Kelley from ATLASSIAN TEAM the currently used libraryjira-rest-java-client is for server-edition of Jira only,see [https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944]{quote} Ben_Kelley ATLASSIAN TEAM TuesdayPlease note the section under "Compatibility with Jira" for JRJC on [ https://ecosystem.atlassian.net/wiki/spaces/JRJC/overview ] The Jira REST Java Client works with Jira Server, but not with Jira Cloud.{quote} When communicating with the cloud edition a self-generated (java) client should be used:[https://community.atlassian.com/t5/Jira-articles/Generating-a-REST-client-for-Jira-Cloud/ba-p/1307133] As the jenkins jira-plugin should work with cloud edition +and+ onpremise server edition of Jira I guess there should be a "generic api" above of the [https://bitbucket.org/atlassian/jira-rest-java-client] and the self-generatedencapsulating the core-jira-functions necessary for jira-pluginto be sure all functions provided by jira-plugin work on both. Current APIs:Server Platform:https://docs.atlassian.com/software/jira/docs/api/REST/8.7.1/Cloud Platform: (v3 is already available as beta)https://developer.atlassian.com/cloud/jira/platform/rest/v2/
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61176) Logstash-gelf is not supported in Java 11
Title: Message Title Jakub Walder created an issue Jenkins / JENKINS-61176 Logstash-gelf is not supported in Java 11 Issue Type: Bug Assignee: Unassigned Attachments: logging.properties Components: _unsorted Created: 2020-02-21 10:01 Environment: Jenkins version: 2.190.3, 2.204.2 OpenJDK 11 Debian container Labels: java11-compatibility Priority: Minor Reporter: Jakub Walder I am running Jenkins on docker container based on OpenJDK 11. I am using logstash-gelf plugin (https://github.com/mp911de/logstash-gelf) to redirect logs directly to Graylog. Before changing to Java 11 it was working on Java 8, but now during startup of container I got those logs: Can't load log handler "biz.paluch.logging.gelf.jul.GelfLogHandler" java.lang.ClassNotFoundException: biz.paluch.logging.gelf.jul.GelfLogHandler java.lang.ClassNotFoundException: biz.paluch.logging.gelf.jul.GelfLogHandler at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at
[JIRA] (JENKINS-61175) Provide different JiraIssueUpdater for cloud and server
Title: Message Title Stefan Cordes created an issue Jenkins / JENKINS-61175 Provide different JiraIssueUpdater for cloud and server Issue Type: New Feature Assignee: Unassigned Components: jira-plugin Created: 2020-02-21 09:49 Priority: Minor Reporter: Stefan Cordes According to Ben_Kelley from ATLASSIAN TEAM the currently used library jira-rest-java-client is for server-edition of Jira only, see https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944 Ben_Kelley ATLASSIAN TEAM Tuesday Please note the section under "Compatibility with Jira" for JRJC on https://ecosystem.atlassian.net/wiki/spaces/JRJC/overview The Jira REST Java Client works with Jira Server, but not with Jira Cloud. When communicating with the cloud edition a self-generated (java) client should be used: https://community.atlassian.com/t5/Jira-articles/Generating-a-REST-client-for-Jira-Cloud/ba-p/1307133 As the jenkins jira-plugin should work with cloud edition and onpremise server edition of Jira I guess there should be a "generic api" above of the https://bitbucket.org/atlassian/jira-rest-java-client and the self-generated encapsulating the core-jira-functions necessary for jira-plugin to be sure all functions provided by jira-plugin work on both.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - Thanks and happy I can help. 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.168534.1456438321000.4132.1582278120237%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance after update
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance after update Change By: Christoph Fetzer Attachment: Capture.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.201861.156818559.4123.1582275060068%40Atlassian.JIRA.
