[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.
Title: Message Title anand acharya commented on JENKINS-54363 Re: ERROR: Could not send email as a part of the post-build publishers. Alex Earl - please confirm when the next version of the email extension plugin will be available with the fix of this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195113.1540977422000.544.1558072560119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title David Riemens commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs Devin Nusbaum : would you have an idea ? Just needed to update my pipeliine scripts, and again the ID's changed... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159718.141883805.537.1558070884174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
Title: Message Title annie chang commented on JENKINS-13916 Re: Multiline text parameter displays as single line issues seen from 2.150.1 new line was removed from a Multi-Line string parameter if the job is triggered via a scheduler. ( therefor, we can not re-submit the job if the job is triggered by scheduler new line was perserved if the job is triggered with a manual submission Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.144384.1337950164000.399.1558067700464%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57417) configFileProvider / withCredentials not working in declarative pipeline
Title: Message Title Richard Davis commented on JENKINS-57417 Re: configFileProvider / withCredentials not working in declarative pipeline Submitted PR #65 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199223.1557587492000.394.1558065360234%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman commented on JENKINS-57371 Re: error message when building PR Audun Halland Wait a minute. If you run the PR-47 job manually, using "Build Now" instead of via the scan, does the Pipeline run successfully? Also, what happens if you close and reopen that PR while making sure no other change goes into master? I think there are two different issues converging here: 1. If the update of master to the new PR is causing the pipeline to fail due to inconsistent commits 2. The Ignore committer strategy is then preventing the PR from being recognized as having been updated. There are likely other strategies that will also cause this to fail. Perhaps the right solution is to allow inconsistencies as long as the merge_commit is the child of two commits that are children of the two commits in the PR. I'm not especially happy with that though. It feels like it opens the door to possible problems. I need to think about what the correct behavior should be in this case. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.392.1558061400228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title Michelle Pogado commented on JENKINS-57171 Re: Permissive script security plugin is broken after updating to script security 1.58 Also experiencing the same problem with the following version: Jenkins 2.168 Script Security 1.58 Permissive Script Security 0.3 Pipeline: Groovy 2.68 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198922.1556125514000.388.1558057500621%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen commented on JENKINS-57513 Re: Split the large databound constructors into databound setters Matt Sicker Raihaan Shouhell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199415.1558053245000.374.1558054200105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen edited a comment on JENKINS-57513 Re: Split the large databound constructors into databound setters https://github.com/jenkinsci/configuration-as-code-plugin/issues/885https://github.com/jenkinsci/configuration-as-code-plugin/issues/381 we also had several users on gitter ask for help debugging null pointers and it all leads to those large data bound constructors that assume null does not exist. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199415.1558053245000.372.1558053540095%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen commented on JENKINS-57513 Re: Split the large databound constructors into databound setters https://github.com/jenkinsci/configuration-as-code-plugin/issues/885 https://github.com/jenkinsci/configuration-as-code-plugin/issues/381 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199415.1558053245000.370.1558053480139%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-57513 Split the large databound constructors into databound setters Issue Type: Task Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-05-17 00:34 Priority: Minor Reporter: Joseph Petersen Inside EC2 plugin there is a lot of constructors with a large set of databound constructors. Databound constructor should only be used for mandatory/final parameters Where databound setters should be used for optional parameters. https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#constructor-vs-setters Add Comment
[JIRA] (JENKINS-27164) docker-build-publish-plugin broken compatibility with token-macro-plugin
Title: Message Title Lance Albertson updated JENKINS-27164 Jenkins / JENKINS-27164 docker-build-publish-plugin broken compatibility with token-macro-plugin Change By: Lance Albertson Resolution: Fixed Status: Closed In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160957.1425056652000.363.1558048740434%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57512) Make About Jenkins always included in a bundle
Title: Message Title Dylan Dewhurst created an issue Jenkins / JENKINS-57512 Make About Jenkins always included in a bundle Issue Type: Improvement Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-05-16 22:11 Priority: Minor Reporter: Dylan Dewhurst When trying to troubleshoot a Jenkins instance, the about.md is always needed as it provides a lot of basic useful information that can be very important to finding a root cause. However there are times when you may be given a bundle without this file because the user did not check the About Jenkins box. This then requires you to have to ask for another one with the option checked. My proposal is to have the about.md always included in a support bundle since it has very useful information that is always needed. The About Jenkins option in the UI can either be removed or made un-editable so people know it will be included. Add Comment
[JIRA] (JENKINS-48518) Docker Pipeline: invalid volume specification with Windows slave and Linux master
Title: Message Title Larry Silverman commented on JENKINS-48518 Re: Docker Pipeline: invalid volume specification with Windows slave and Linux master I also just hit this. Did anyone find a workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187135.1513098516000.348.1558043880389%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43183) Can't see pipeline jobs in Global Build Stats
Title: Message Title Igor Sarkisov commented on JENKINS-43183 Re: Can't see pipeline jobs in Global Build Stats +1 to have global-build-stats-plugin support pipeline jobs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180302.1490774058000.335.1558039920712%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title
Liam Newman edited a comment on JENKINS-57371
Re: error message when building PR
[~audunhalland]{quote} This commit is set up to be ignored by jenkins (using Ignore Committer Strategy). So, the current tip of master branch is not 7e88 anymore, and I suspect that this has something to do with this problem.{quote}This is extremely useful! This could be where the problem is coming from. It is definitely some kind of incorrect assumptions made by github-branch-source. If you run the PR-47 job manually, using "Build Now" instead of via the scan, does the Pipeline run successfully? Here's the problem: The plugin needs to make sure that the base, source, and merge commits are in sync otherwise the master (which uses the merge_commit) could be looking at different information from other agents, which use the source+base to create a new merge on the local file system. From what you're describing, the ignore committer strategy forces plugin not to see the right base commit and so forces the commits out-of-sync. :( The merge_commit behavior was introduced in 2.5.0 - I was unaware of the filter trait you've mentioned. I'm looking at it now.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.330.1558038540226%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57281) Details Tab (in Details View)
Title: Message Title Nils Engelbrecht updated JENKINS-57281 Jenkins / JENKINS-57281 Details Tab (in Details View) Change By: Nils Engelbrecht Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199047.1556742712000.325.1558037940219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Damian Szczepanik commented on JENKINS-57497 Re: Cucumber Report displays incorrect total duration if total duration is more than 24 hours Attach JSON file for reference or even better report it to main tracker https://github.com/damianszczepanik/cucumber-reporting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.323.1558037700174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57483) Bump H2 to 1.4.199
Title: Message Title Cyrille Le Clerc closed an issue as Fixed fixed in 3.6.13 Jenkins / JENKINS-57483 Bump H2 to 1.4.199 Change By: Cyrille Le Clerc Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199343.1557922789000.315.1558036560184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Martin Weber commented on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline Possibly a duplicate of JENKINS-51060? But that should have been fixed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.321.1558036800158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Cyrille Le Clerc updated JENKINS-57324 fixed in 3.6.13 Jenkins / JENKINS-57324 Error running maven with settings file when running multibranch pipeline with a slash in the branch Change By: Cyrille Le Clerc Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.318.1558036620206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57332) PipelineMavenPluginDao#getGeneratedArtifacts() mixes artifact version and baseVersion
Title: Message Title Cyrille Le Clerc updated JENKINS-57332 Jenkins / JENKINS-57332 PipelineMavenPluginDao#getGeneratedArtifacts() mixes artifact version and baseVersion Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199106.1557094938000.316.1558036560220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman commented on JENKINS-57371 Re: error message when building PR Audun Halland This commit is set up to be ignored by jenkins (using Ignore Committer Strategy). So, the current tip of master branch is not 7e88 anymore, and I suspect that this has something to do with this problem. This is extremely useful! This could be where the problem is coming from. It is definitely some kind of incorrect assumptions made by github-branch-source. If you run the PR-47 job manually, using "Build Now" instead of via the scan, does the Pipeline run successfully? Here's the problem: The plugin needs to make sure that the base, source, and merge commits are in sync otherwise the master (which uses the merge_commit) could be looking at different information from other agents, which use the source+base to create a new merge on the local file system. From what you're describing, the ignore committer strategy forces plugin not to see the right base commit and so forces the commits out-of-sync. The merge_commit behavior was introduced in 2.5.0 - I was unaware of the filter trait you've mentioned. I'm looking at it now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.312.1558035900211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52382) Can't stop / cancel private repository builds
Title: Message Title Robert Ferris commented on JENKINS-52382 Re: Can't stop / cancel private repository builds I'm noticing this as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192176.1530780622000.309.1558034460179%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57511) Repeatedly seeing 'Failed to get "URL"' in Jenkins log
Title: Message Title Shannon Kerr created an issue Jenkins / JENKINS-57511 Repeatedly seeing 'Failed to get "URL"' in Jenkins log Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-05-16 17:27 Environment: Jenkins 2.150.3, latest plugins, Jenkins provided docker image. Priority: Minor Reporter: Shannon Kerr Repeatedly seeing these in my Jenkins log: May 16, 2019 12:59:08 PM WARNING io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1 getValue Failed to get "url" from a io.jenkins.blueocean.service.embedded.rest.ChangeSetResource java.lang.NullPointerException Caused: java.lang.reflect.InvocationTargetException at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:74) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.getValue(Export.java:196) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:303) at io.jenkins.blueocean.commons.stapler.export.Property.writeBuffered(Property.java:175) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:235) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at
[JIRA] (JENKINS-24831) Executor gets assigned multiple times
Title: Message Title Stacey Fletcher commented on JENKINS-24831 Re: Executor gets assigned multiple times Was the root cause ever figured out here? I am also seeing the same thing in our Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157660.1411495375000.296.1558026300144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48035) Github multibranch: GitHub Webhook is not created right after saving the job
Title: Message Title
Carlos Rodríguez López edited a comment on JENKINS-48035
Re: Github multibranch: GitHub Webhook is not created right after saving the job
[~rsandell] [~stephenconnolly] I am reopening this ticket again because the same reported issue seems to be back running (Regression?)h4. Environment{code:java}Jenkins LTS 2.164.2 * github:1.29.4 'GitHub plugin' * github-api:1.95 'GitHub API Plugin' * github-branch-source:2.5.0 *(update available)* 'GitHub Branch Source Plugin'{code}h4. ObservationWhat we see on logs{code:java}May 16, 2019 3:12:38 PM org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeWARNING: Failed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]java.lang.NullPointerException: There are no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]{code}But it is not right... I am using this repo https://github.com/mock-carlosrodlop-org/my-hw-maven-app with user:carlosrodlop and pass:APIToken and as you can tell from the following images carlosrodlop is an admin !repo-team.png|thumbnail! !repo-team-2.png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186577.1510760384000.289.1558025521301%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57453) Invalid encoded sequence when connecting Windows Agent with Bitvise SSH Server
Title: Message Title Jeff Thompson commented on JENKINS-57453 Re: Invalid encoded sequence when connecting Windows Agent with Bitvise SSH Server I doubt the encode sequence values are a reliable differentiator. I searched for the message and there are very few instances of it. The few that exist are mostly connected with Windows and / or Bitvise. Those seem to be the commonalities. There has been a long history of connection issues generally with SSH servers on Windows. Yes, the ssh-slaves-plugin uses a forked version of the trilead ssh library instead of the jsch one. So that one may not be relevant. I'm afraid I don't have any good suggestions for troubleshooting / debugging this. It kind of looks like this has some relation to the SSH transport. The only instances of this error are connected to SSH agents and your experience using a different SSH server show distinct variations in results. The trick is probably to figure out what it is about the SSH transport that is introducing the problem. The logs you provided only show information at the upper, remoting level and are insufficient to get further. You could try using Wireshark or some other network capture tool. That gives such low-level results that it's hard to sort through it and isolate the specific issue. You might be able to figure something out from it, though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199311.1557833375000.287.1558024860108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48035) Github multibranch: GitHub Webhook is not created right after saving the job
Title: Message Title Carlos Rodríguez López reopened an issue Jenkins / JENKINS-48035 Github multibranch: GitHub Webhook is not created right after saving the job Change By: Carlos Rodríguez López Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186577.1510760384000.279.1558024560382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48035) Github multibranch: GitHub Webhook is not created right after saving the job
Title: Message Title
Carlos Rodríguez López edited a comment on JENKINS-48035
Re: Github multibranch: GitHub Webhook is not created right after saving the job
[~rsandell] [~stephenconnolly] I am reopening this ticket again because the same reported issue seems to be back running(Regression?) h4. Enviroment Environment {code:java}Jenkins LTS 2.164.2 * github:1.29.4 'GitHub plugin' * github-api:1.95 'GitHub API Plugin' * github-branch-source:2.5.0 *(update available)* 'GitHub Branch Source Plugin'{code}h4. ObservationWhat we see on logs{code:java}May 16, 2019 3:12:38 PM org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeWARNING: Failed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]java.lang.NullPointerException: There are no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]{code}But it is not right... I am using this repo with user:carlosrodlop and pass:APIToken!repo-team.png|thumbnail! !repo-team-2.png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186577.1510760384000.272.1558024500738%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48035) Github multibranch: GitHub Webhook is not created right after saving the job
Title: Message Title Carlos Rodríguez López commented on JENKINS-48035 Re: Github multibranch: GitHub Webhook is not created right after saving the job rsandell Stephen Connolly I am reopening this ticket again because the same reported issue seems to be back running Enviroment Jenkins LTS 2.164.2 * github:1.29.4 'GitHub plugin' * github-api:1.95 'GitHub API Plugin' * github-branch-source:2.5.0 *(update available)* 'GitHub Branch Source Plugin' Observation What we see on logs May 16, 2019 3:12:38 PM org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafe WARNING: Failed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app] java.lang.NullPointerException: There are no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app] But it is not right... I am using this repo with user:carlosrodlop and pass:APIToken Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-48035) Github multibranch: GitHub Webhook is not created right after saving the job
Title: Message Title Carlos Rodríguez López updated an issue Jenkins / JENKINS-48035 Github multibranch: GitHub Webhook is not created right after saving the job Change By: Carlos Rodríguez López Attachment: repo-team-2.png Attachment: repo-team.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186577.1510760384000.258.1558024440276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57510) Default to use Android headless emulator
Title: Message Title Tim Kist updated an issue Jenkins / JENKINS-57510 Default to use Android headless emulator Change By: Tim Kist By defaulting to use the headless emulator binary in ` /emulator/emulator-headless ` . This eliminates the need for Qt and other UI libraries as the well as memory improvements. The Android emulator team have worked on this. See This is now a feature in emulator starting from 29.0.6 stable. Could also be an option in the plugin. [https://androidstudio.googleblog.com/2019/02/emulator-2818-canary.html] and [ https:// androidstudio.googleblog.com/2019/05/emulator-2906-stable.html][https:// youtu.be/Up3hyBSDAMA?t=1687 ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199412.1558022384000.256.1558024260107%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Nikita Bochenko edited a comment on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Constantly running into the same issue. Using both Job DSL+Pipeline and Pipeline directly to generate new jobs or update their configuration. Have no idea how to reproduce it as it seems very random. It seems if I reload configuration from disk, the error goes away for some time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194284.1537930113000.250.1558023720209%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Nikita Bochenko commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Constantly running into the same issue. Using both Job DSL+Pipeline and Pipeline directly to generate new jobs or update their configuration. Have no idea how to reproduce it as it seems very random. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194284.1537930113000.244.1558023660269%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57510) Default to use Android headless emulator
Title: Message Title Tim Kist created an issue Jenkins / JENKINS-57510 Default to use Android headless emulator Issue Type: New Feature Assignee: Christopher Orr Components: android-emulator-plugin Created: 2019-05-16 15:59 Labels: android-emulator-plugin Priority: Minor Reporter: Tim Kist By defaulting to use the headless emulator binary in `/emulator/emulator-headless`. This eliminates the need for Qt and other UI libraries as the Android emulator team have worked on this. See https://androidstudio.googleblog.com/2019/02/emulator-2818-canary.html and https://youtu.be/Up3hyBSDAMA?t=1687 Add Comment
[JIRA] (JENKINS-57509) Blaming not executed on first build from pipeline script
Title: Message Title
Andreas Pabst created an issue
Jenkins / JENKINS-57509
Blaming not executed on first build from pipeline script
Issue Type:
Bug
Assignee:
Unassigned
Components:
warnings-ng-plugin
Created:
2019-05-16 15:42
Priority:
Minor
Reporter:
Andreas Pabst
When creating a pipeline with a script, the git blamer is not executed on the first build of the pipeline. Steps to reproduce: 1. Create a pipeline with the following script:
node {
stage ('Build and Analysis') {
git 'https://github.com/jenkinsci/warnings-ng-plugin.git'
echo '[javac] src/main/java/io/jenkins/plugins/analysis/warnings/AndroidLint.java:10: warning: Test Warning for Jenkins'
recordIssues tool: java()
}
}
2. Build the pipeline 3. The console output shows, that the git blaming was skipped. Also, the blame table is missing from the build overview.
Skipping issues blame since Git is the only supported SCM up to now.
...
[Java] Skipping blaming as requested in the job configuration
4. Build the pipeline again 5. The console output now shows the log of the blamer, and the blame table is visible in the build overview.
[Java] Invoking Git blamer to create author and commit information for
[JIRA] (JENKINS-57508) NodeJSInstallation "home" parameter required but not documented
Title: Message Title
Michele Mauro updated an issue
Jenkins / JENKINS-57508
NodeJSInstallation "home" parameter required but not documented
Change By:
Michele Mauro
When configuring a NodeJS installation with the Configuration as Code plugin, the "home" argument of the NodeJSInstallation class constructor is required and its absence prevents the Jenkins instance to start. The bug is that it is not clear from the configuration UI, nor from an export of a working configuration, nor from any documentation that such a value is required, or what should be its value set to . In fact, just specifying it as an empty string solves the problem.Related github issue: [https://github.com/jenkinsci/configuration-as-code-plugin/issues/701]Related code: [https://github.com/jenkinsci/nodejs-plugin/blob/2d459b1507a763ef14303b3c7b727863ffd974f2/src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstallation.java#L70]*Steps to reproduce:*To have a working Jenkins instance using the Configuration as Code plugin, you must use something like the following as configuration for a NodeJS installation: {code:java}tool: nodejs:installations:- name: "Node 11.14" home: "" properties: - installSource: installers: - nodeJSinstaller: id: "11.14.0" npmPackagesRefreshHours: 72{code}Without the _home: ""_ value, the instance fails to start with the following error:{code:java}io.jenkins.plugins.casc.ConfiguratorException: home is required to configure class jenkins.plugins.nodejs.tools.NodeJSInstallation{code}With the empty _home_ value, everything works correctly. The bug is the fact that it is very hard to find (it probably requires inspection of the NodeJS plugin source code) that that value is required, is required in that position, and that an empty value is a correct default.*Possible solutions:* # One possible solution could be to remove the requirement on the parameter, possibly adding another constructor that sets the working empty value # Another solution could be adding some documentation (it's not clear to me where, however) to guide Configuration as Code users so that they are aware of the requirement
Add
[JIRA] (JENKINS-57508) NodeJSInstallation "home" parameter required but not documented
Title: Message Title Michele Mauro updated an issue Jenkins / JENKINS-57508 NodeJSInstallation "home" parameter required but not documented Change By: Michele Mauro Environment: jenkins 2.164.3nodejs-plugin 1.2.9configuration-as-code-plugin 1. 13 14configuration-as-code-support:1.14 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199410.1558021019000.235.1558021200137%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57508) NodeJSInstallation "home" parameter required but not documented
Title: Message Title Michele Mauro created an issue Jenkins / JENKINS-57508 NodeJSInstallation "home" parameter required but not documented Issue Type: Bug Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin, nodejs-plugin Created: 2019-05-16 15:36 Environment: jenkins 2.164.3 nodejs-plugin 1.2.9 configuration-as-code-plugin 1.13 Labels: plugin user-experience configuration Priority: Minor Reporter: Michele Mauro When configuring a NodeJS installation with the Configuration as Code plugin, the "home" argument of the NodeJSInstallation class constructor is required and its absence prevents the Jenkins instance to start. The bug is that it is not clear from the configuration UI, nor from an export of a working configuration, nor from any documentation that such a value is required, or what should be its value. In fact, just specifying it as an empty string solves the problem. Related github issue: https://github.com/jenkinsci/configuration-as-code-plugin/issues/701 Related code: https://github.com/jenkinsci/nodejs-plugin/blob/2d459b1507a763ef14303b3c7b727863ffd974f2/src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstallation.java#L70 Steps to reproduce: To have a working Jenkins instance using the Configuration as Code plugin, you must use something like the following as configuration for a NodeJS installation: tool: nodejs:
[JIRA] (JENKINS-54612) Reference repo not used for Git clones on Windows SSH agents
Title: Message Title Timor Raiman commented on JENKINS-54612 Re: Reference repo not used for Git clones on Windows SSH agents I'm seeing this with the pipeline only. (freestyle works). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195401.154214014.229.1558020180128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57326) Support jgit and jgitapache with Configuration as Code plugin
Title: Message Title Nicolas De Loof assigned an issue to Nicolas De Loof Jenkins / JENKINS-57326 Support jgit and jgitapache with Configuration as Code plugin Change By: Nicolas De Loof Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199098.1556975157000.227.1558019460335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57012) Allow folder scope credential for Jira connection
Title: Message Title Mathieu Delrocq commented on JENKINS-57012 Re: Allow folder scope credential for Jira connection A pull request was opened for this issue : https://github.com/jenkinsci/jira-plugin/pull/188. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198713.1555344179000.224.1558019400110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52600) credentials plugin uses Restricted jenkins.util.xml.XMLUtils
Title: Message Title Ramon Leon commented on JENKINS-52600 Re: credentials plugin uses Restricted jenkins.util.xml.XMLUtils Updated the PR to remove the dependency to restricted classes (not only XMLUtils) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192443.153181715.220.1558017660243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52600) credentials plugin uses Restricted jenkins.util.xml.XMLUtils
Title: Message Title Ramon Leon updated JENKINS-52600 Jenkins / JENKINS-52600 credentials plugin uses Restricted jenkins.util.xml.XMLUtils Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192443.153181715.216.1558017600281%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51020) Filter by name (with regular expression) not applied on tags during scanning causing overconsumption of API quota
Title: Message Title Daniel Martins commented on JENKINS-51020 Re: Filter by name (with regular _expression_) not applied on tags during scanning causing overconsumption of API quota This could be related to https://issues.jenkins-ci.org/browse/JENKINS-52147, as a means to mitigate the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190249.1524751101000.166.1558016820561%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45896) Malformed GitHub Plugin configuration (no protocol: )
Title: Message Title David Eddy updated an issue Jenkins / JENKINS-45896 Malformed GitHub Plugin configuration (no protocol: ) Change By: David Eddy Attachment: image-2019-05-16-10-32-20-133.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184115.1501568753000.196.1558017180452%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title Ray Kivisto reopened an issue Re-opening so we can track the discussion about if this is truly fixed or not, or if we should just update the plugin documentation with the `id` setting. Jenkins / JENKINS-43693 multibranchPipelineJob overrides old branch indexing sources Change By: Ray Kivisto Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181107.1492615058000.173.1558016881421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45896) Malformed GitHub Plugin configuration (no protocol: )
Title: Message Title David Eddy commented on JENKINS-45896 Re: Malformed GitHub Plugin configuration (no protocol: ) For anyone who runs into this problem in the future: Just use the default example URL in the API URL. That will allow the plugin to successfully valid the URL and let you move on. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184115.1501568753000.202.1558017180560%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title Mark Waite commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed Dana Maxfield I don't know of any other work arounds beyond those that I listed earlier. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.148793.1366035236000.160.1558016702659%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52147) Repository scan constantly checking tags, hitting rate limits
Title: Message Title Daniel Martins commented on JENKINS-52147 Re: Repository scan constantly checking tags, hitting rate limits We are being hit pretty hard by this as well. We have a couple of high-activity repositories with a few thousand tags each, and I can also see the constant tag scanning behavior in their respective "Repository Events" screen; branches are constanly being created/updated, so it's common for builds to be delayed for several minutes due to the plugin's rate limit protections. In the attached screenshot I show one of these events in which a push to some branch triggered the tag scanning behavior. I also found what it seems to be the relevant portion of the source code that seems to confirm the mentioned behavior (a push to a branch triggers the tag scanning). This behavior doesn't make much sense to me, especially for large repositories with a huge number of tags. Is there any way we can disable this behavior? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191764.1529692855000.96.1558016640288%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title Dana Maxfield commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed We continue to randomly hit this issue. When I created a new release branch, one that isn't being built by the build in question, the problem building started triggering on every poll. If I delete the release branch, triggering stops. No traces of the release branch exist within the problem build configuration OR source. Mark Waite I have also tried all of the work arounds you supplied (thank you btw), but none have worked. Is any data stored on the file system that I can delete or edit which will flush this out? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.148793.1366035236000.83.1558016463930%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24986) Offer an alternate location to store plugins and groovy hook scripts
Title: Message Title Jakub Bochenski commented on JENKINS-24986 Re: Offer an alternate location to store plugins and groovy hook scripts I'm confused about the status of this ticket. It seems to me that I'm deriving a custom docker image from the official one, installing plugins and hooks. The only issue I faced was https://github.com/jenkinsci/docker/issues/563 "Docker image can't be built with custom plugins / hook scripts." sounds rather scary to me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.158482.1412325985000.11.1558016160587%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52147) Repository scan constantly checking tags, hitting rate limits
Title: Message Title Daniel Martins updated an issue Jenkins / JENKINS-52147 Repository scan constantly checking tags, hitting rate limits Change By: Daniel Martins Attachment: tag-scanning.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191764.1529692855000.2.1558016102816%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54836) create a local user in jenkins with admin privilages
Title: Message Title Michael S commented on JENKINS-54836 Re: create a local user in jenkins with admin privilages I would like it too. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195825.1542979104000.3016.1558015380129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49120) Cannot save project configuration changes after upgraded Jenkins to 2.103
Title: Message Title Casey Wise commented on JENKINS-49120 Re: Cannot save project configuration changes after upgraded Jenkins to 2.103 Upgrading Publish Over plugins fixed me on this one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187955.1516747823000.3013.1558012920195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57507) Parameterized Trigger node label can get stuck
Title: Message Title Elliot Nelson created an issue Jenkins / JENKINS-57507 Parameterized Trigger node label can get stuck Issue Type: Bug Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2019-05-16 13:20 Environment: Jenkins 2.138.2, Plugin 2.35.2, Java 1.8.x, Linux Labels: parameterized-trigger plugin slave Priority: Minor Reporter: Elliot Nelson If Build A is set up to trigger a project using "Build On Same Node", and the machine running Build A disconnects from Jenkins (crash, network issue, reboot, etc.), what happens is that Build B is queued with the appropriate label (say "build-7"). Jenkins then cleans up the Label "build-7", because there are no machines with that label. The machine reconnects, causing Jenkins to create a new Label "build-7". However, the old Label instance representing the same label string (attached to the NodeAction in the plugin) is no longer referenced by Jenkins and can't be refreshed. The result is that the build waiting to build on "build-7" waits in the queue forever, even though the targeted machine is connected and live. The expected behavior is that if a machine with a matching node label is live, the build should start. A workaround, today, is to go into the Script Console and manually kick the orphaned label, upon which the orphaned build will start immediately. Example:
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Audun Halland edited a comment on JENKINS-57371 Re: error message when building PR However, I also found that "Scan Repository Now" does not see the pull request as updated, even if the tip of the PR branch is a merge that points to latest master. Log outputs: Getting remote branches...Checking branch masterGetting remote pull requests... ‘Jenkinsfile’ found Met criteriaNo changes detected: master (still at 76ff9c62d27d6b60666c08d0686e3100974fd1fe)Checking pull request #47 ‘Jenkinsfile’ found Met criteriaNo changes detected: PR-47 (still at 5729a1e31f5d0691d16801604312de0af03da009+7e881478aa951a0f9caad966907c68c5c058a935 (98e8973772d6f2075ea775f7e985e0a739e3fc34))Current master is 76ff, so the PR checker should not have tried to use 5729+7e88, but 5729+76ff. Question remains whether this is misinformation from github, or incorrect logic in github-branch-source. EDIT: PR strategy is "Merging the pull request with the current target branch revision". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.3001.1558012440197%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57506) jackshen: add author info to jenkins.io blog
Title: Message Title Jeff Pearce created an issue Jenkins / JENKINS-57506 jackshen: add author info to jenkins.io blog Issue Type: Task Assignee: Jeff Pearce Components: working-hours-plugin Created: 2019-05-16 13:08 Priority: Minor Reporter: Jeff Pearce Submit pull request to //github.com/jenkins-infra/jenkins.io.git to add author info Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57480) All old warnings are reported as new after server migration
Title: Message Title Marne closed an issue as Not A Defect Configuration problem Jenkins / JENKINS-57480 All old warnings are reported as new after server migration Change By: Marne Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199339.1557915687000.2995.1558011900228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57480) All old warnings are reported as new after server migration
Title: Message Title Marne updated an issue Jenkins / JENKINS-57480 All old warnings are reported as new after server migration Change By: Marne Comment: Configuration problem Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199339.1557915687000.2997.1558011900251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57480) All old warnings are reported as new after server migration
Title: Message Title Marne commented on JENKINS-57480 Re: All old warnings are reported as new after server migration Thanks, with this hint I found which configuration mistake of ours caused the problem. The fingerprints of the newer builds all started with "FALLBACK". So Jenkins was not able to read the files. It turned out that we did not configure the source file encoding. Not sure if the encoding Jenkins tried to read the files with changed due to the migration or what caused this to suddenly become a problem but after specifying the correct encoding the issue delta is correct again. Thank you very much for your help! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199339.1557915687000.2986.1558011840339%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Audun Halland commented on JENKINS-57371 Re: error message when building PR However, I also found that "Scan Repository Now" does not see the pull request as updated, even if the tip of the PR branch is a merge that points to latest master. Log outputs: Getting remote branches... Checking branch master Getting remote pull requests... ‘Jenkinsfile’ found Met criteria No changes detected: master (still at 76ff9c62d27d6b60666c08d0686e3100974fd1fe) Checking pull request #47 ‘Jenkinsfile’ found Met criteria No changes detected: PR-47 (still at 5729a1e31f5d0691d16801604312de0af03da009+7e881478aa951a0f9caad966907c68c5c058a935 (98e8973772d6f2075ea775f7e985e0a739e3fc34)) Current master is 76ff, so the PR checker should not have tried to use 5729+7e88, but 5729+76ff. Question remains whether this is misinformation from github, or incorrect logic in github-branch-source. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.2969.1558011480168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57505) Cannot quote $ (dolar sign) in yaml
Title: Message Title
Pavel Janoušek created an issue
Jenkins / JENKINS-57505
Cannot quote $ (dolar sign) in yaml
Issue Type:
Bug
Assignee:
Ewelina Wilkosz
Components:
configuration-as-code-plugin
Created:
2019-05-16 12:38
Priority:
Major
Reporter:
Pavel Janoušek
I need to put contect like (exactly): "${MY_TEXT}/foo" into a field in YAML file. Unfortunately, this construct is replaced by the output "/foo" because ${MY_TEXT} is tried to be resolved from environment - usually it is empty. I can't find a way, how to quote '$', tried many different ways, including: "${MY_TEXT}/foo" -> "/foo" "$${MY_TEXT}/foo" -> "$/foo" "\${MY_TEXT}/foo" -> unknown escape character error ($) "${MY_TEXT}/foo" -> unknown escape character error ({) Curiously, export uses the same "${MY_TEXT}/foo" construct which doesn't work obviously. For this case I've found two work-arounds:
define MY_TEST env variable with the content "${MY_TEST}" - this is needed for all such definitions...
define dolar sign as an env. variable e.g. DOLAR="$" and use construct like "${DOLAR} {MY_TEXT} /foo"
There are many cases when we need to take the environment variable content into YAML, but there should be a way how to don't do that if we need it too.
[JIRA] (JENKINS-57196) DOC: More description for 'Populate have list'
Title: Message Title Kevin Williamson updated JENKINS-57196 In the next release Jenkins / JENKINS-57196 DOC: More description for 'Populate have list' Change By: Kevin Williamson Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198950.1556289436000.2964.1558008540372%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57455) Jenkins is not exposing cipher for TLSv1.1 and TLS1
Title: Message Title Oleg Nenashev commented on JENKINS-57455 Re: Jenkins is not exposing cipher for TLSv1.1 and TLS1 As designed IMHO. We include only standard Ciphers from MINA SSHD, and TLS 1.1 ciphers are not offered there due to security reasons. It is possible to make ciphers configurable via system properties in https://github.com/jenkinsci/sshd-module/blob/d31495b398a02fca5b87d2aa332188f78a097052/src/main/java/org/jenkinsci/main/modules/sshd/SSHD.java#L44-L46 , I would be open to review and probably accept such patch Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199315.1557842321000.2962.1558007760145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Audun Halland commented on JENKINS-57371 Re: error message when building PR This also happens to us. I'm getting error message: ERROR: Invalid merge hash for pull request 47 : Head and base commits do match merge commit 5729a1e31f5d0691d16801604312de0af03da009+7e881478aa951a0f9caad966907c68c5c058a935 (98e8973772d6f2075ea775f7e985e0a739e3fc34) Finished: FAILURE. 5729 is the tip of the PR branch. 7e88 is the commit of the previously merged PR (onto master). However, our pipeline generates and pushes a release commit to github for the master job, where it updates the version number of the app, and tags that commit with the release number. This commit is set up to be ignored by jenkins (using Ignore Committer Strategy). So, the current tip of master branch is not 7e88 anymore, and I suspect that this has something to do with this problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.2959.1558007640230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57504) Failing to create node
Title: Message Title Héctor Garrido Fuentes created an issue Jenkins / JENKINS-57504 Failing to create node Issue Type: Bug Assignee: Jean-Christophe Sirot Components: ansible-plugin, blueocean-plugin Created: 2019-05-16 11:50 Environment: version 2.164.2 lts Priority: Blocker Reporter: Héctor Garrido Fuentes When trying to create a new node in jenkins we have this error. Stack trace org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.164.2.jar!/hudson/slaves/DumbSlave/configure-entries.jelly:61:73: Lhudson/tools/JDKInstaller; at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at
[JIRA] (JENKINS-52600) credentials plugin uses Restricted jenkins.util.xml.XMLUtils
Title: Message Title Ramon Leon commented on JENKINS-52600 Re: credentials plugin uses Restricted jenkins.util.xml.XMLUtils We're working on make credentials been able to be compiled on Java 11, so we need to remove this dependency: https://github.com/jenkinsci/credentials-plugin/pull/112 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192443.153181715.2948.1558006680609%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52600) credentials plugin uses Restricted jenkins.util.xml.XMLUtils
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-52600 credentials plugin uses Restricted jenkins.util.xml.XMLUtils Change By: Ramon Leon Assignee: Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192443.153181715.2953.1558006680763%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52600) credentials plugin uses Restricted jenkins.util.xml.XMLUtils
Title: Message Title Ramon Leon started work on JENKINS-52600 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192443.153181715.2951.1558006680700%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57503) JiraTestResultReporter-plugin's auto resolve feature is not working
Title: Message Title Jayesh Mahajan created an issue Jenkins / JENKINS-57503 JiraTestResultReporter-plugin's auto resolve feature is not working Issue Type: Bug Assignee: Catalin Luta Components: jiratestresultreporter-plugin Created: 2019-05-16 10:45 Environment: jenkins 2.138.2 OS Centos 7 Priority: Blocker Reporter: Jayesh Mahajan Dear Team, I integrate jenkins and jira to auto report the bug in jira. but facing problem in auto resolve case, its failing there give the error message about transition error. I tried to reproduce it but no luck and next time it not read my test case report even there is fail test is reported. I already took the help from cloud bees support but they ask me to raise ticket in jira. Please help me to resolve this problem ASAP. I followed following document. https://wiki.jenkins.io/display/JENKINS/JiraTestResultReporter-plugin#JiraTestResultReporter-plugin-JobConfiguration thank in advance. Add Comment
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title Andrea Lai reopened an issue I am re-opening as 2 people reported the change did not address the issue for some use cases. Jenkins / JENKINS-57171 Permissive script security plugin is broken after updating to script security 1.58 Change By: Andrea Lai Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198922.1556125514000.2922.1558001640977%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57494) MissingFieldException: No field 'charset' found in class 'org.jenkinsci.plugins.p4.tagging.TagAction'
Title: Message Title Robby He commented on JENKINS-57494 Re: MissingFieldException: No field 'charset' found in class 'org.jenkinsci.plugins.p4.tagging.TagAction' Hi Karl Wirth, thanks for your help. We will check this 'older unreadable data' prompt when the server encounter a memory increasement issue next time. Currently our server is running well. But thanks again. I will let you know if it would solve our problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199356.1557972637000.2919.1558001520257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57494) MissingFieldException: No field 'charset' found in class 'org.jenkinsci.plugins.p4.tagging.TagAction'
Title: Message Title Karl Wirth commented on JENKINS-57494 Re: MissingFieldException: No field 'charset' found in class 'org.jenkinsci.plugins.p4.tagging.TagAction' Hi Robby He - Thanks for highlighting this. Have you already been to 'Manage Jenkins' and tried to clear out old data? If you have not and that option is available, please make sure you have backed up your jobs then try clearing out the old data. Does this solve the problem? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199356.1557972637000.2917.1558000560281%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57494) MissingFieldException: No field 'charset' found in class 'org.jenkinsci.plugins.p4.tagging.TagAction'
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57494 MissingFieldException: No field 'charset' found in class 'org.jenkinsci.plugins.p4.tagging.TagAction' Change By: Karl Wirth Attachment: OldData.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199356.1557972637000.2915.1558000440235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title
Dan Mordechai edited a comment on JENKINS-51057
Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM
[~airadier] Thank you for this script! I will definitely try it as we are facing the same issue on our 2.107.2 Jenkins.Some things to point out: # I had to change the line {code:java}def dispatcher = channelSubscriber.this$0{code}to{code:java}def dispatcher = channelSubscriber.eventDispatcher{code} 2. Your script will only work for SSE gatway plugin version <= > 1.15 as the SSEChannelSubscriber inner class in EventDispatcher.java will not have the eventDispatcher member any more.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190313.1525203384000.2898.1557999780417%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57502) Cmake arguments sometimes are added to path in parallel build
Title: Message Title
Vladimir Eremeev created an issue
Jenkins / JENKINS-57502
Cmake arguments sometimes are added to path in parallel build
Issue Type:
Bug
Assignee:
Martin Weber
Components:
cmakebuilder-plugin
Created:
2019-05-16 09:34
Environment:
Jenkins version 2.164.3 cmake plugin version 2.6.1
Priority:
Blocker
Reporter:
Vladimir Eremeev
I'm trying to simulate matrix build using Pipeline Pipeline snippet {{def cmake_tasks(os_labels, configs, DL_on_off) { tasks = [:] def DL_dir_labels = ['ON': 'DL', 'OFF': 'noDL'] for(int i = 0; i < os_labels.size(); i++) { def os = os_labels[i] for (int j = 0; j < configs.size(); j++) { for (int k = 0; k < DL_on_off.size(); k++) { def config = configs[j] def DL = DL_on_off[k] def DL_dir_label = DL_dir_labels["${DL}"] def generator = "Ninja" def steps = [[withCmake: true]] def cmakeArgs = "-Dsomevar=somevalue" def cmake_inst = 'InSearchPath' tasks["${os}/${config}/${DL_dir_label}"] = { node("build && ${os}") { stage("${os}/${config}/${DL_dir_label}") { if (os == "windows") { bat """ ${env.WORKSPACE}\\DL\\test\\supportconfigure.cmd ${config} build_${config}_${DL_dir_label} ${DL} ninja """ } else { cmakeBuild(buildDir: "build_${config}_${DL_dir_label}", buildType: config, cleanBuild: true, cmakeArgs: cmakeArgs, generator: generator, installation: cmake_inst, sourceDir: ".", steps: steps) } } } } } } } return tasks } pipeline { agent none parameters { string(defaultValue: 'develop', description: 'Commit ID or branch name to build', name: 'branch', trim: false) } stages { stage('Checkout') { steps { script { // checkout on windows and linux } } } stage('Configure & Build') { steps { script { def OSes = ["windows", "linux"] def configs = ["Release", "Debug"] def DL_inc = ["ON", "OFF"] parallel cmake_tasks(OSes,
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Jayashree Rokde commented on JENKINS-57497 Re: Cucumber Report displays incorrect total duration if total duration is more than 24 hours We have used cucumber Report plug in version 4.6.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.2894.1557995700194%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57500) Update outdated dependencies
Title: Message Title Fred Blaise commented on JENKINS-57500 Re: Update outdated dependencies Created https://github.com/jenkinsci/jira-plugin/pull/190 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199363.1557993399000.2892.1557995040069%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57394) Rename JDK Tool Plugin to Oracle JDK Installer plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-57394 Rename JDK Tool Plugin to Oracle JDK Installer plugin Change By: Baptiste Mathus Labels: java11 triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199176.1557477158000.2889.1557994800480%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57395) Create administrative monitor to warn users about Oracle JDK Installer concerns
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-57395 Create administrative monitor to warn users about Oracle JDK Installer concerns Change By: Baptiste Mathus Labels: java11 triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199177.1557477277000.2891.1557994800501%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57496) Can't use customized jenkins-jnlp images when added the Kubernetes Plugin
Title: Message Title Carlos Sanchez closed an issue as Duplicate Jenkins / JENKINS-57496 Can't use customized jenkins-jnlp images when added the Kubernetes Plugin Change By: Carlos Sanchez Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199358.1557988176000.2887.1557994680242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev created an issue
Jenkins / JENKINS-57501
cmakeBuild does not set environment variables in Windows when run in Pipeline
Issue Type:
Bug
Assignee:
Martin Weber
Components:
cmakebuilder-plugin
Created:
2019-05-16 08:14
Environment:
Jenkins ver. 2.164.3 Cmake plugin version 2.6.1 Jenkins slave running on windows machine as a service.
Priority:
Blocker
Reporter:
Vladimir Eremeev
Pipeline snippet {{def cmake_tasks() { def tasks=[:] def steps = [[withCmake: true]] def os = "windows" def config = "Debug" def generator = "Ninja" def vars=""" LIB=C:Program Files (x86)Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;C:Program Files (x86)Microsoft Visual Studio 14.0\\VC\\ATLMFC\\LIB\\amd64;C:Program Files (x86)Windows Kits\\10\\lib\\10.0.17763.0\\ucrt\\x64;C:Program Files (x86)Windows Kits\\NETFXSDK\\4.6.1\\lib\\um\\x64;C:Program Files (x86)Windows Kits\\10\\lib\\10.0.17763.0\\umx64; PATH=C:Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:Program Files (x86)Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Windows\\Microsoft.NET\\Framework64\\;C:Program Files (x86)Windows Kits\\10\\bin\\x64;C:Program Files (x86)Windows Kits\\10\\bin\\x86;C:Program Files (x86)Microsoft SDKs\\Windows\\v10.0A\\binNETFX 4.6.1 Tools\\x64\\;C:Program Files (x86)Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\CMake\\bin;c:\\windows\\system32;C:Program FilesNVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\bin;C:Program FilesNVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\libnvvp;g:Bin; """ def cmakeArgs = "-DARG=VALUE" def cmake_inst = 'InSearchPath' steps.add([envVars: vars]) cmakeArgs = cmakeArgs + " -DCMAKE_C_COMPILER=cl -DCMAKE_CXX_COMPILER=cl -DCMAKE_MAKE_PROGRAM=g:\\Binninja"
[JIRA] (JENKINS-57500) Update outdated dependencies
Title: Message Title Fred Blaise created an issue Jenkins / JENKINS-57500 Update outdated dependencies Issue Type: Task Assignee: Unassigned Components: jira-plugin Created: 2019-05-16 07:56 Priority: Minor Reporter: Fred Blaise Hello, Could you please (especially) keep the jira-rest-java-client-api and jira-rest-java-client-core up-to-date. Thank you. fred Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records I'm not shure how the process is nowadays. As mentioned: It's really long time ago that I made this plugin Patch files are a god way: I'll look inside them at the weekend. And then I figure out how to release and deploy a fixed version. Also I tried to make the plugin compatibility test work, but it looks like that this is a major issue. This darcs plugin is really outdated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198924.1556132083000.2882.1557993420333%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30750) Jenkins all pages loads every 20 seconds
Title: Message Title manus commented on JENKINS-30750 Re: Jenkins all pages loads every 20 seconds Isn't this the same as JENKINS-19828? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165364.1443725514000.2877.1557993120204%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57499) booleanParam will give String variable
Title: Message Title
Christian Opitz created an issue
Jenkins / JENKINS-57499
booleanParam will give String variable
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2019-05-16 07:28
Environment:
Jenkins ver. 2.164.2
Priority:
Minor
Reporter:
Christian Opitz
Defining a boolean parameter will not return a boolean value as expected, but a String value. Defining the parameter:{{}}
parameters { booleanParam(name: 'bForceCheckout', defaultValue: false, description: '') }
Checking the type...
println bForceCheckout.getClass()
...will give you:
09:06:03 class java.lang.String
This of course leads to some nice behaviour when checking the variable in conditions...
[JIRA] (JENKINS-47307) Add help texts to configuration
Title: Message Title Aleksi Simell updated JENKINS-47307 Pull request 58 merged. Jenkins / JENKINS-47307 Add help texts to configuration Change By: Aleksi Simell Status: In Progress Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185732.1507282107000.2872.1557990480100%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57498) string value in Groovy script in Reactive Choice parameter replaced with null when approved in in-process script approval
Title: Message Title
nimesh saman created an issue
Jenkins / JENKINS-57498
string value in Groovy script in Reactive Choice parameter replaced with null when approved in in-process script approval
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Components:
active-choices-plugin
Created:
2019-05-16 07:06
Priority:
Blocker
Reporter:
nimesh saman
My reactive choice parameter groovy script is following def command = ["/bin/bash", "-c", "git ls-remote --tags " + repourl] def process = command.execute() process.waitFor() def t1 = [] def result = process.in.text.tokenize('n') for(i in result) { def tagName = i.split()[1].replaceAll('\\^{}','').replaceAll('refs/tags/', '') t1.add(tagName) } return t1 But when I check this script in in-process script approval it looks like this def command = ["/bin/bash", "-c", "git ls-remote --tags " + repourl] def process = command.execute() process.waitFor() def t1 = [] def result = process.in.text.tokenize(" ") for(i in result) { def tagName = i.split()[1].replaceAll('^{}','').replaceAll('refs/tags/', '') t1.add(tagName) } And when I approved it this script contains error I am blocked here
Add Comment
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Jayashree Rokde created an issue Jenkins / JENKINS-57497 Cucumber Report displays incorrect total duration if total duration is more than 24 hours Issue Type: Bug Assignee: Damian Szczepanik Attachments: Incorrect total duration.png Components: cucumber-reports-plugin Created: 2019-05-16 06:40 Priority: Minor Reporter: Jayashree Rokde When Total duration of feature is exceeding 24 hours, it gets reset to 0 so incorrect Total duration gets displayed. For Example, 1:40.915 when total duration was 25:40:915 Not able to find any option to format this Add Comment
[JIRA] (JENKINS-57496) Can't use customized jenkins-jnlp images when added the Kubernetes Plugin
Title: Message Title June Liu created an issue Jenkins / JENKINS-57496 Can't use customized jenkins-jnlp images when added the Kubernetes Plugin Issue Type: Task Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-05-16 06:29 Environment: Use docker image jenkins/jenkins:lts to install jenkins master. Kubernetes Plugin is V1.15.3 Labels: plugin Priority: Critical Reporter: June Liu I configure the Kubernetes container template and set the container name as "jnlp" to use my own images as agent. But when I build the job, the slave can't connect to master. Jenkins master logs as below INFO: Created Pod: kube-system/jnlp-n3vb7 May 13, 2019 8:13:36 AM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? May 13, 2019 8:13:40 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Pod is running: kube-system/jnlp-n3vb7 May 13, 2019 8:13:40 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (0/100): jnlp-n3vb7 May 13, 2019 8:13:41 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (1/100): jnlp-n3vb7 May 13, 2019 8:13:42 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (2/100): jnlp-n3vb7 Please help.
