[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title Janis Balodis commented on JENKINS-54187 Re: EC2 Plugin deadlock leaving Jenkins unresponsive I am facing a similar issue, but in our case, I used the latest version of ec2 plug-in (1.41) with Jenkins 2.135.1 for a few days without any issues. The problems started after I updated Jenkins to 2.138.2. Downgrade to 2.138.1 solved the problem with deadlocks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54444) Update supported Jenkins version
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-5 Update supported Jenkins version Change By: Daniel Gront Summary: Update Jenkins supported Jenkins version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54444) Update Jenkins supported version
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-5 Update Jenkins supported version Issue Type: Task Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2018-11-05 07:26 Labels: Infrastructure Priority: Critical Reporter: Daniel Gront Since Jenkins no longer supports old update centers, we are supporting the same versions that Jenkins does. See the list here: http://updates.jenkins-ci.org/ Currently, the update is from to 2.60.3 to 2.73.3 Add Comment
[JIRA] (JENKINS-54333) Projects are triggered twice by "build with parameters"
Title: Message Title wang ying edited a comment on JENKINS-54333 Re: Projects are triggered twice by "build with parameters" Yes, the steps are correct.Regarding the previous question, 2. 150 and 2. 148 and 2.149 have this issue.I'm using IE version 11.0.9600.19100 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54333) Projects are triggered twice by "build with parameters"
Title: Message Title wang ying updated an issue Jenkins / JENKINS-54333 Projects are triggered twice by "build with parameters" Change By: wang ying Environment: Jenkins ver.2. 150, Jenkins ver.2. 149 and Jenkens ver.2.148Parameterized Trigger plugin 2.35.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Steve Graham edited a comment on JENKINS-54261 Re: Submit ( go ) on Email Template Testing produces blank screen Exactly as you described above but with an existing job, # Select *Email Template Testing* from the side panel # Enter the *Jelly/Groovy Template File Name* # Select a build ( or use the default already selected ) # Hit *Go*with 2.147 the results of the template can be seen.with 2.148 the results are visible for a millisecond then the Template File Name field is empty and the results are no longer visible.( it does not matter if Auto Refresh is enabled or not, the results are the same ) I'll try it on 2.150 .. ... exactly the same results - also happens with a new freestyle project Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Steve Graham edited a comment on JENKINS-54261 Re: Submit ( go ) on Email Template Testing produces blank screen Exactly as you described above but with an existing job, # Select *Email Template Testing* from the side panel # Enter the *Jelly/Groovy Template File Name* # Select a build ( or use the default already selected ) # Hit *Go*with 2.147 the results of the template can be seen.with 2.148 the results are visible for a millisecond then the Template File Name field is empty and the results are no longer visible.( it does not matter if Auto Refresh is enabled or not, the results are the same ) I'll try it on 2.150 .. ... exactly the same results Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Steve Graham commented on JENKINS-54261 Re: Submit ( go ) on Email Template Testing produces blank screen Exactly as you described above but with an existing job, Select Email Template Testing from the side panel Enter the Jelly/Groovy Template File Name Select a build ( or use the default already selected ) Hit Go with 2.147 the results of the template can be seen. with 2.148 the results are visible for a millisecond then the Template File Name field is empty and the results are no longer visible. ( it does not matter if Auto Refresh is enabled or not, the results are the same ) I'll try it on 2.150 .. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54361) Plugin name doesn't match UI, docs stale
Title: Message Title Craig Ringer commented on JENKINS-54361 Re: Plugin name doesn't match UI, docs stale Created pull for the github repo : https://github.com/jenkinsci/antisamy-markup-formatter-plugin/pull/8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54399) Configuration page no longer loads
Title: Message Title Frank Shimizu commented on JENKINS-54399 Re: Configuration page no longer loads Also fixed with 3.4.1 here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54380) Private repository authentication
Title: Message Title Marcos Vallim commented on JENKINS-54380 Re: Private repository authentication Hi Philipp Garbe thanks for your fast response. I've made all the requested changes. See code on the PR. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54441) Display class and plugin for workflow steps
Title: Message Title
Craig Ringer updated an issue
Jenkins / JENKINS-54441
Display class and plugin for workflow steps
Change By:
Craig Ringer
The "/pipeline-syntax/ ("Pipeline Syntax Snippet Generator") view exposed by workflow-cps-plugin, and the related "/pipeline-syntax/html" ("Steps Reference") don't expose any information about where a step comes from - the plugin, class, etc.This makes it awfully hard to track things down when trying to debug an issue.It'd be a big improvement if steps were annotated in the help with their implementing class in both places. So in the snippet generator when you choose a "Sample Step" it loads the step descriptor and shows: * Step description if any * Implementing class * "Friendly name" of plugin containing implementing class and its actual plugin-id too, with a link to the plugins wikiI've spent *way* too long trying to find a step's implementation in a sub-sub-sub plugin of a plugin, which has two different display names, a different internal plugin name, and a different-again git repo name.For the bigger picture of "how do I identify where X came from in Jenkins" see JENKINS-26565. See also JENKINS-54442 for the related issue with globals. ~~~For Google: this issue is about workflow-cps-plugin a.k.a workflow-cps a.k.a. "Pipeline: Groovy" a.k.a "Pipeline Groovy Plugin", i.e. the "/pipeline-syntax/" page, the "Pipeline Syntax: Snippet Generator".
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54441) Display class and plugin for workflow steps
Title: Message Title
Craig Ringer updated an issue
Jenkins / JENKINS-54441
Display class and plugin for workflow steps
Change By:
Craig Ringer
The "/pipeline-syntax/ ("Pipeline Syntax Snippet Generator") view exposed by workflow-cps-plugin, and the related "/pipeline-syntax/html" ("Steps Reference") don't expose any information about where a step comes from - the plugin, class, etc.This makes it awfully hard to track things down when trying to debug an issue.It'd be a big improvement if steps were annotated in the help with their implementing class in both places. So in the snippet generator when you choose a "Sample Step" it loads the step descriptor and shows: * Step description if any * Implementing class * "Friendly name" of plugin containing implementing class and its actual plugin-id too, with a link to the plugins wikiI've spent *way* too long trying to find a step's implementation in a sub-sub-sub plugin of a plugin, which has two different display names, a different internal plugin name, and a different-again git repo name. For the bigger picture of "how do I identify where X came from in Jenkins" see JENKINS-26565. ~~~For Google: this issue is about workflow-cps-plugin a.k.a workflow-cps a.k.a. "Pipeline: Groovy" a.k.a "Pipeline Groovy Plugin", i.e. the "/pipeline-syntax/" page, the "Pipeline Syntax: Snippet Generator".
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-7887) Inconsistency regarding plugin names inside pluginManger pages
Title: Message Title Craig Ringer commented on JENKINS-7887 Re: Inconsistency regarding plugin names inside pluginManger pages See also JENKINS-26565 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26565) Show both 'names' of plugins
Title: Message Title Craig Ringer commented on JENKINS-26565 Re: Show both 'names' of plugins I find it utterly bewildering, and it slows me down a lot with Jenkins. The "Safe HTML" formatter is probably the worst culprit, as noted above. It is: "Safe HTML" - name in Global Security configuration, "OWASP Markup Formatter Plugin" - name in "Plugin Manager" UI antisamy-markup-formatter - name in "Plugins" list in "/jenkins/systemInfo", i.e. Maven artifact name ... and none of these are remotely connected. In something that's security-sensitive that's pretty significant. There's no indication at all in the global security UI that the formatter is from a plugin at all (that's kinda bad from a security PoV), let alone which one. The plugin's display name doesn't mention "HTML" or "Safe". The plugin's internal name is unrelated again. Clicking the plugin's name in the Plugin Manager takes you to a a wiki page that (until I edited it) didn't mention "Safe HTML" at all, and its "plugin site" link takes you to https://plugins.jenkins.io/antisamy-markup-formatter but has the title "OWASP Markup Formatter 1.5". If you click the plugin's version in plugin manager you get taken to a confusingly named "thirdPartyLicenses" URL that is really a dependency map. The first "dependency" is actually the plugin itself, but that's not clearly indicated at all. What should happen is: The "Plugin Manager" UI should have a less prominent suffix on the plugin name with the maven artifact name or full co-ordinates, labeled something like "plugin id" The "systemInfo" view should list plugin display-names too The "systemInfo" view should probably also list the contained package(s) or offer a class browser, since they often differ again ... and in the case of formatters, the formatter selector should show the plugin info there. Another example is pretty much any plugin in the Pipeline / Workflow suite. For example, we have: Pipeline: Groovy (jenkins "Plugin Manager" UI) workflow-cps (name in "Plugins" list in "/jenkins/systemInfo", i.e. Maven artifact name) jenkinsci/workflow-cps-plugin (git repo name, note -plugin suffix absent from artifact name) Pipeline Groovy Plugin (github README) org.jenkins-ci.plugins.workflow:workflow-cps:2.60 (full Maven co-ordinates) org.jenkinsci.plugins.workflow.cps.* (package name) Finding things is very hard.
[JIRA] (JENKINS-54443) Loadrunner controller not displayed while running the test from Jenkins
Title: Message Title santhosh nair created an issue Jenkins / JENKINS-54443 Loadrunner controller not displayed while running the test from Jenkins Issue Type: Bug Assignee: Daniel Danan Components: micro-focus-performance-center-integration-plugin Created: 2018-11-05 05:11 Priority: Major Reporter: santhosh nair While triggering the loadrunner test from Jenkins master via build/pipeline, the load test is getting kicked off in the background in the jenkin slave machine even after enabling the "display controller" option in the [Loadrunner specific settings]. Plugin version : Micro Focus Application Automation Tools 5.5 Jenkins version : Jenkins ver. 2.142 Operating system : Windows Loarunner version : 12.55 Expected result : By enabling the "display controller" option , the controller should be displayed in the jenkins slave machine where the test is configured to be executed. Actual result : The test is running fine , however the controller is not displayed. The controller instance can be seen running via the Task manager in the background. Add Comment
[JIRA] (JENKINS-54442) Show origin class, repository, plugin of globals
Title: Message Title
Craig Ringer created an issue
Jenkins / JENKINS-54442
Show origin class, repository, plugin of globals
Issue Type:
New Feature
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin, workflow-cps-plugin
Created:
2018-11-05 04:49
Environment:
Jenkins ver. 2.138.2, org.jenkins-ci.plugins.workflow:workflow-cps:2.60
Priority:
Minor
Reporter:
Craig Ringer
The "/pipeline-syntax/globals" ("Global Variable Reference") view exposed by workflow-cps-plugin as part of the snippet generator doesn't offer any information about where a global came from. This makes it hard for users and even admins to figure out a source location when there's a problem. Is it a pipeline builtin, and if so, which pipeline plugin? Is it part of another plugin? Is it from a global pipeline library? etc. Like for steps in JENKINS-54441 it'd be great to identify the variable more clearly, using its class name, originating plugin if any, originating global library if any, etc.
Add Comment
[JIRA] (JENKINS-54441) Display class and plugin for workflow steps
Title: Message Title
Craig Ringer created an issue
Jenkins / JENKINS-54441
Display class and plugin for workflow steps
Issue Type:
New Feature
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-11-05 04:45
Environment:
Jenkins ver. 2.138.2, org.jenkins-ci.plugins.workflow:workflow-cps:2.60
Priority:
Minor
Reporter:
Craig Ringer
The "/pipeline-syntax/ ("Pipeline Syntax Snippet Generator") view exposed by workflow-cps-plugin, and the related "/pipeline-syntax/html" ("Steps Reference") don't expose any information about where a step comes from - the plugin, class, etc. This makes it awfully hard to track things down when trying to debug an issue. It'd be a big improvement if steps were annotated in the help with their implementing class in both places. So in the snippet generator when you choose a "Sample Step" it loads the step descriptor and shows:
Step description if any
Implementing class
"Friendly name" of plugin containing implementing class and its actual plugin-id too, with a link to the plugins wiki
I've spent way too long trying to find a step's implementation in a sub-sub-sub plugin of a plugin, which has two different display names, a different internal plugin name, and a different-again git repo name. ~~~ For Google: this issue is about workflow-cps-plugin a.k.a workflow-cps a.k.a. "Pipeline: Groovy" a.k.a "Pipeline Groovy Plugin", i.e. the "/pipeline-syntax/" page, the "Pipeline Syntax: Snippet Generator".
[JIRA] (JENKINS-54086) Define audit events for user auth-related events
Title: Message Title Latha Sekar assigned an issue to Unassigned Jenkins / JENKINS-54086 Define audit events for user auth-related events Change By: Latha Sekar Assignee: Latha Sekar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54086) Define audit events for user auth-related events
Title: Message Title Latha Sekar assigned an issue to Latha Sekar Jenkins / JENKINS-54086 Define audit events for user auth-related events Change By: Latha Sekar Assignee: Latha Sekar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54233) Pipeline Script textarea missing
Title: Message Title Andrew Gray commented on JENKINS-54233 Re: Pipeline Script textarea missing Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53080) Jenkins bitbucket plugin not building tags, if not other changes happened
Title: Message Title Nikolas Falco edited a comment on JENKINS-53080 Re: Jenkins bitbucket plugin not building tags, if not other changes happened This is not a defect. By design the plugin does not trigger build if has already built the hash code. Moreover by default (of the branch-ap plugin) a build is not trigger on tag events unless you get a specific plugin that implements a new default logic.https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/139#issuecomment-433684917 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53080) Jenkins bitbucket plugin not building tags, if not other changes happened
Title: Message Title Nikolas Falco commented on JENKINS-53080 Re: Jenkins bitbucket plugin not building tags, if not other changes happened By design the plugin does not trigger build if has already built the hash code. Moreover by default (of the branch-ap plugin) a build is not trigger on tag events unless you get a specific plugin that implements a new default logic. https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/139#issuecomment-433684917 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Nikolas Falco commented on JENKINS-54401 Re: NPE when parsing scm git revision date on PR branches let me know if this HPI resolve. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22547) Git timeout setting does not work for checkout
Title: Message Title
yang z edited a comment on JENKINS-22547
Re: Git timeout setting does not work for checkout
Seems resolved by this way: set timeout by "CloneOption" {code:java}checkout scm: [$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', timeout: 240]], // CheckoutOption -> CloneOption gitTool: 'Default', submoduleCfg: [], userRemoteConfigs: [[ credentialsId: '981cbff3-3a30-4a61-be40-99f441ea0559',url: 'git@server:project.git']]]{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22547) Git timeout setting does not work for checkout
Title: Message Title
yang z edited a comment on JENKINS-22547
Re: Git timeout setting does not work for checkout
Seems resolved by this way: {code:java} checkout scm: [$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', timeout: 240]], // CheckoutOption -> CloneOption gitTool: 'Default', submoduleCfg: [], userRemoteConfigs: [[ credentialsId: '981cbff3-3a30-4a61-be40-99f441ea0559', url: 'git@server:project.git']]] {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22547) Git timeout setting does not work for checkout
Title: Message Title yang z commented on JENKINS-22547 Re: Git timeout setting does not work for checkout Seems resolved by this way: checkout scm: [$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', timeout: 240]], // CheckoutOption -> CloneOption gitTool: 'Default', submoduleCfg: [], userRemoteConfigs: [[ credentialsId: '981cbff3-3a30-4a61-be40-99f441ea0559', url: 'git@server:project.git' ]]] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47882) Unable to connect MongoDB with MONGODB-CR authentication
Title: Message Title Kingsley Chan commented on JENKINS-47882 Re: Unable to connect MongoDB with MONGODB-CR authentication Thanks Tim. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Nikolas Falco started work on JENKINS-54401 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-54401 NPE when parsing scm git revision date on PR branches Change By: Nikolas Falco Summary: java.lang.NullPointerException NPE when parsing target scm git revision date on PR branches Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54440) Bump PostgreSQL driver
Title: Message Title Cyrille Le Clerc commented on JENKINS-54440 Re: Bump PostgreSQL driver PR https://github.com/jenkinsci/database-postgresql-plugin/pull/1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54440) Bump PostgreSQL driver
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-54440 Bump PostgreSQL driver Issue Type: Improvement Assignee: David van Laatum Components: database-postgresql-plugin Created: 2018-11-05 00:23 Priority: Minor Reporter: Cyrille Le Clerc Bump PostgreSQL driver to v 42.2.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-54401 java.lang.NullPointerException when parsing target revision date Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34274) Duration testsuite is not read from report.
Title: Message Title Nikolas Falco closed an issue as Cannot Reproduce Jenkins / JENKINS-34274 Duration testsuite is not read from report. Change By: Nikolas Falco Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54434) Bump MySql driver to v8.x
Title: Message Title Cyrille Le Clerc commented on JENKINS-54434 Re: Bump MySql driver to v8.x Fixed in the MySql Database Plugin 1.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54434) Bump MySql driver to v8.x
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-54434 Re: Bump MySql driver to v8.x Fixed in the MySql Database Plugin 1.3 . Thanks [~davidvanlaatum] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54439) Support configuration as code plugin
Title: Message Title Tim Jacomb started work on JENKINS-54439 Change By: Tim Jacomb Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54439) Support configuration as code plugin
Title: Message Title Tim Jacomb assigned an issue to Tim Jacomb Jenkins / JENKINS-54439 Support configuration as code plugin Change By: Tim Jacomb Assignee: Tomas Westling Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54439) Support configuration as code plugin
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-54439 Support configuration as code plugin Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2018-11-04 21:41 Labels: jcasc-compatibility Priority: Minor Reporter: Tim Jacomb Many plugins support configuration as code See https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/PLUGINS.md Add Comment
[JIRA] (JENKINS-54380) Private repository authentication
Title: Message Title Philipp Garbe commented on JENKINS-54380 Re: Private repository authentication See comments on the PR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53470) Pods are not terminating properly
Title: Message Title Alex Medvedev commented on JENKINS-53470 Re: Pods are not terminating properly Fix already arrived: https://github.com/jenkinsci/kubernetes-plugin/commit/c6d31c0e95fbf82bca791cfb23cb005f182bd952 Closed as duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53470) Pods are not terminating properly
Title: Message Title Alex Medvedev closed an issue as Duplicate Jenkins / JENKINS-53470 Pods are not terminating properly Change By: Alex Medvedev 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49305) view-job-filters-plugin regex filter fails to match any jobs from folders
Title: Message Title Sven Schoenung resolved as Fixed Problem is most likely that the "Recurse in subfolders" checkbox is not checked as Joshua already pointed out. The 2.1.0 release now also includes options to match the full path and folder name of jobs, so that might help as well. If the problem still persists, please reopen ticket with instructions to reproduce. Jenkins / JENKINS-49305 view-job-filters-plugin regex filter fails to match any jobs from folders Change By: Sven Schoenung Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/view-job-filters-plugin/releases/tag/view-job-filters-2.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed
[JIRA] (JENKINS-53881) aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs
Title: Message Title Rik Turnbull commented on JENKINS-53881 Re: aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs Thanks David, I've released v1.2.1 which I hope should resolve 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54060) Compatibility with Jenkins 2.x
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54060 Compatibility with Jenkins 2.x Change By: Oleg Nenashev Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Joseph Petersen assigned an issue to Nikolas Falco Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Joseph Petersen Assignee: Joseph Petersen Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Jon Starbird commented on JENKINS-54286 Re: Unable to use variable tokens as build property values in Create Package in Declarative Script I see the issue. I didn't catch the change from SetBuildVariables to PackageVariables. I've updated it and now it is working. Thanks! Sorry for the extra work but much appreciated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49229) BFA description URLs are not clickable
Title: Message Title Tim Jacomb commented on JENKINS-49229 Re: BFA description URLs are not clickable This functionality works, you need to use a markup formatter: https://wiki.jenkins.io/display/JENKINS/Markup+formatting Set it in configure security and then use html / markdown to format your result.Not sure when the support was initially added, but support on another view was added as part of this commit: https://github.com/jenkinsci/build-failure-analyzer-plugin/commit/3af17d65ccbdc5a9576e2dd5fa717c6f3b300ecd Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49229) BFA description URLs are not clickable
Title: Message Title Tim Jacomb closed an issue as Not A Defect Jenkins / JENKINS-49229 BFA description URLs are not clickable Change By: Tim Jacomb 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49229) BFA description URLs are not clickable
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-49229 BFA description URLs are not clickable Change By: Tim Jacomb Attachment: screenshot-1.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53834) rocketchat notifier plugin needing internet access to push notification to rocketchat
Title: Message Title Martin Reinhardt commented on JENKINS-53834 Re: rocketchat notifier plugin needing internet access to push notification to rocketchat another option is to just add the rocketchat server to the non-proxy hosts So from my side nothing to add here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date
Title: Message Title dan tran commented on JENKINS-54401 Re: java.lang.NullPointerException when parsing target revision date same here, PR is from the same repo, PR job created with NPE, no notification form Jenkins to BB for status update Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title
dan tran updated an issue
Jenkins / JENKINS-54331
Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Change By:
dan tran
Comment:
actually PR does get receive, but jenkins has error{code:java}// code placeholder{code}Branch event java.lang.NullPointerException at com.fasterxml.jackson.databind.util.ISO8601Utils.parseInt(ISO8601Utils.java:329) at com.fasterxml.jackson.databind.util.ISO8601Utils.parse(ISO8601Utils.java:161) at com.fasterxml.jackson.databind.util.ISO8601DateFormat.parse(ISO8601DateFormat.java:52) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketGitSCMRevision.(BitbucketGitSCMRevision.java:60) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:843) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:288) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title dan tran updated an issue Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: dan tran Comment: Torsten Kleiber does 2.2.14 work out for you?It is not for me.With 2.2.14, new submitted PR does not get built, no build for subsequence commits to the branch. ended up to revert back to 2.2.13, delete the PR and create new one For my production build, we stick with 2.2.12 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title dan tran commented on JENKINS-54331 Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 actually PR does get receive, but jenkins has error // code placeholder Branch event java.lang.NullPointerException at com.fasterxml.jackson.databind.util.ISO8601Utils.parseInt(ISO8601Utils.java:329) at com.fasterxml.jackson.databind.util.ISO8601Utils.parse(ISO8601Utils.java:161) at com.fasterxml.jackson.databind.util.ISO8601DateFormat.parse(ISO8601DateFormat.java:52) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketGitSCMRevision.(BitbucketGitSCMRevision.java:60) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:843) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:288) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title dan tran edited a comment on JENKINS-54331 Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Torsten Kleiber does 2.2.14 work out for you? It is not for me. With 2.2.14, new submitted PR does not get built, no build for subsequence commits to the branch. ended up to revert back to 2.2.13, delete the PR and create new one For my production build, we stick with 2.2.12 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54438) Documentation is not generating for wait parameter in build job
Title: Message Title corey morris created an issue Jenkins / JENKINS-54438 Documentation is not generating for wait parameter in build job Issue Type: Bug Assignee: Unassigned Components: pipeline-build-step-plugin Created: 2018-11-04 14:54 Labels: documentation Priority: Minor Reporter: corey morris On this page https://jenkins.io/doc/pipeline/steps/pipeline-build-step/ , the wait parameter doesn't have documentation of what it does. From my understanding, it appears that the documentation should be generated from here https://github.com/jenkinsci/pipeline-build-step-plugin/blob/19f0118c04a0e68773e7dd6c89796605d5492bdc/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-wait.groovy . I am not sure if there is a reason why this uses groovy to generate the HTML rather than HTML like the other documentation. It appears to not be working in the way it is intended though. Add Comment
[JIRA] (JENKINS-53834) rocketchat notifier plugin needing internet access to push notification to rocketchat
Title: Message Title java sabin commented on JENKINS-53834 Re: rocketchat notifier plugin needing internet access to push notification to rocketchat rocketchat plugin shouldnt take proxy connection as first priority to access rocketchat server hosted locally. what is the meaning of setting up rocketchat server ip if the it takes the proxy setting of the jenkins as first priority. the work around solution i found out is to remove the proxy setting saved in the jenkins setting in 'manage plugins' and rocketchat plugin can send alert to locally hosted rocket chat server. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52280) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev commented on JENKINS-52280 Re: Create official Java 11 Docker Packaging for BlueOcean Unofficial one is here: https://github.com/oleg-nenashev/jenkins-blueocean-experimental Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54434) Bump MySql driver to v8.x
Title: Message Title Cyrille Le Clerc commented on JENKINS-54434 Re: Bump MySql driver to v8.x Proposed with https://github.com/jenkinsci/database-mysql-plugin/pull/1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54434) Bump MySql driver to v8.x
Title: Message Title Cyrille Le Clerc started work on JENKINS-54434 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54437) Add support for MySql database
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-54437 Add support for MySql database Issue Type: Improvement Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-11-04 14:00 Priority: Major Reporter: Cyrille Le Clerc Add support for MySql database as an alternative to H2 database. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-43302) JaCoCo plugin 2.2.0 changeBuildStatus not work in pipeline
Title: Message Title centic updated JENKINS-43302 No response for a long time, thus closing for now. Jenkins / JENKINS-43302 JaCoCo plugin 2.2.0 changeBuildStatus not work in pipeline Change By: centic Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50357) Garbled in picture
Title: Message Title centic commented on JENKINS-50357 Re: Garbled in picture Can you save the html-page where this happens in your browser and attach it here? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50479) Complexity coverage result does not get written to console
Title: Message Title centic updated JENKINS-50479 Added via 2c5b43822b4621c3d770aa4d929024a5901d9cda Jenkins / JENKINS-50479 Complexity coverage result does not get written to console Change By: centic Status: Open Fixed but Unreleased Resolution: Fixed Released As: 3.0.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54436) change environment variable name: HP_RUN_ID
Title: Message Title Daniel Danan created an issue Jenkins / JENKINS-54436 change environment variable name: HP_RUN_ID Issue Type: Bug Assignee: Daniel Danan Components: hp-application-automation-tools-plugin Created: 2018-11-04 12:37 Environment: 5.5.3-beta-SNAPSHOT Labels: PerformanceCenter Priority: Minor Reporter: Daniel Danan log console providing this output: ... Sun 2018 Nov 04 at 13:59:10.552 PM IST - Set Environment Variable: HP_RUN_ID = 130 ... environment variable name should be modified: HP should be replaced by PC or MF. Add Comment
[JIRA] (JENKINS-54397) Microfocus Health Analyzer all checks are executed on Master instead of Slave
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54397 Microfocus Health Analyzer all checks are executed on Master instead of Slave Change By: Daniel Gront Summary: Microfocus Health Analyzer check LR scenario all checks are executed on Master (Jenkins Server) only instead of Slave Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54397) Microfocus Health Analyzer check LR scenario on Master(Jenkins Server) only
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54397 Microfocus Health Analyzer check LR scenario on Master(Jenkins Server) only Change By: Daniel Gront Comment: [~kenanom], Could you provide additional information on what's 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54435) Add tests to HealthAnalyzerCommon
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54435 Add tests to HealthAnalyzerCommon Change By: Daniel Gront Labels: Infrastructure Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54431) Error with Java 11 and jacoco-plugin 3.0.3
Title: Message Title centic closed an issue as Not A Defect This is not related to jacoco-plugin/Jenkins itself, it seems to be rather caused by core JaCoCo running as part of your Gradle build. So you should update JaCoCo there to the latest version which should to fix this. Jenkins / JENKINS-54431 Error with Java 11 and jacoco-plugin 3.0.3 Change By: centic 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53411) Jacoco Plugin 3.0.3 fails build when no Jacoco exec files are available
Title: Message Title centic updated JENKINS-53411 Jenkins / JENKINS-53411 Jacoco Plugin 3.0.3 fails build when no Jacoco exec files are available Change By: centic Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53411) Jacoco Plugin 3.0.3 fails build when no Jacoco exec files are available
Title: Message Title centic updated JENKINS-53411 Released via JENKINS-49823 Jenkins / JENKINS-53411 Jacoco Plugin 3.0.3 fails build when no Jacoco exec files are available Change By: centic Status: Open Fixed but Unreleased Resolution: Duplicate Released As: 3.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49823) Jacoco Plugin 3.0.1 fails build as basedir now incorrect
Title: Message Title centic updated JENKINS-49823 This is available now with release 3.0.4 Jenkins / JENKINS-49823 Jacoco Plugin 3.0.1 fails build as basedir now incorrect Change By: centic Status: Fixed but Unreleased Resolved Released As: 3.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54435) Add tests to HealthAnalyzerCommon
Title: Message Title
Daniel Gront updated an issue
Jenkins / JENKINS-54435
Add tests to HealthAnalyzerCommon
Change By:
Daniel Gront
In order to properly test if it is executed on a slave, it requires end-to-end tests (using JenkinsRule). The tests should as well integrate this tests back:{code:java}@Testpublic void ifCheckedPerformOsCheck_shouldThrowException_withCorrectValue() throws Exception {initializeOperatingSystemOs("windows");try {healthAnalyzerCommon.ifCheckedPerformOsCheck(OperatingSystem.LINUX, true);fail();} catch (AbortException e) {assertEquals(e.getMessage(), String.format("Your operating system: %s is not %s.", "linux",OperatingSystem.getOs()));}}@Testpublic void ifCheckedPerformOsCheck_doesNotThrowException() throws Exception {initializeOperatingSystemOs("windows");healthAnalyzerCommon.ifCheckedPerformOsCheck(OperatingSystem.WINDOWS, true);} @Testpublic void isCheckedPerformWindowsInstallationCheck_throwsCorrectExceptionValue() throws Exception { if (OperatingSystem.IS_WINDOWS) {try {healthAnalyzerCommon.isRegistryExist(NON_EXISTING_REGISTRY);fail();} catch (AbortException e) {assertEquals(e.getMessage(), DUMMY_PRODUCT_NAME + " is not installed. Please install it first.");}}}{ code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54435) Add tests to HealthAnalyzerCommon
Title: Message Title
Daniel Gront created an issue
Jenkins / JENKINS-54435
Add tests to HealthAnalyzerCommon
Issue Type:
Task
Assignee:
Daniel Gront
Components:
hp-application-automation-tools-plugin
Created:
2018-11-04 11:20
Priority:
Major
Reporter:
Daniel Gront
In order to properly test if it is executed on a slave, it requires end-to-end tests (using JenkinsRule). The tests should as well integrate this tests back:
@Test
public void ifCheckedPerformOsCheck_shouldThrowException_withCorrectValue() throws Exception {
initializeOperatingSystemOs("windows");
try {
healthAnalyzerCommon.ifCheckedPerformOsCheck(OperatingSystem.LINUX, true);
fail();
} catch (AbortException e) {
assertEquals(e.getMessage(), String.format("Your operating system: %s is not %s.", "linux",
OperatingSystem.getOs()));
}
}
@Test
public void ifCheckedPerformOsCheck_doesNotThrowException() throws Exception {
initializeOperatingSystemOs("windows");
healthAnalyzerCommon.ifCheckedPerformOsCheck(OperatingSystem.WINDOWS, true);
}
[JIRA] (JENKINS-54397) Microfocus Health Analyzer check LR scenario on Master(Jenkins Server) only
Title: Message Title Daniel Gront updated JENKINS-54397 Jenkins / JENKINS-54397 Microfocus Health Analyzer check LR scenario on Master(Jenkins Server) only Change By: Daniel Gront 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54397) Microfocus Health Analyzer check LR scenario on Master(Jenkins Server) only
Title: Message Title Daniel Gront stopped work on JENKINS-54397 Change By: Daniel Gront Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54397) Microfocus Health Analyzer check LR scenario on Master(Jenkins Server) only
Title: Message Title Daniel Gront started work on JENKINS-54397 Change By: Daniel Gront Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner edited a comment on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
Not sure what's going on here. I've created a sample deployment using jenkins buildmaster plugin 2.1.1. Can you: # Confirm which version of the plugin you are using. Ideally you'll need to upgrade to 2.1.1 if you're not already using this. Note that this version has renamed {color:#172b4d}setBuildVariables{color} from buildMasterCreatePackage to packageVariables. # Echo out your {color:#009100}gitprops{color} variable and ensure it is populated correctly # Show how {color:#009100}gitprops{color} is being populated {color:#172b4d}I've created a sample deployment using jenkins buildmaster plugin 2.1.1 to attempt to duplicate your issue. {color} As you can see in the log output below that the two variables (commit and fred) appear in the logs, but I cannot see the same for your output. All I can think is that you're using an early release of the plugin that contains a bug or that somehow the variables not not getting passed to the plugin correctly. Code:{code:java}node {scmVars = git(credentialsId: 'andrew-git', url: 'https://github.com/andrew-sumner/Accounts.git')echo "$scmVars"buildMasterWithApplicationRelease(applicationId: '2', packageNumberSource: 'BUILDMASTER') {BUILDMASTER_PACKAGE_NUMBER = buildMasterCreatePackage(applicationId: BUILDMASTER_APPLICATION_ID, releaseNumber: BUILDMASTER_RELEASE_NUMBER, packageNumber: BUILDMASTER_PACKAGE_NUMBER, deployToFirstStage: true, waitTillBuildCompleted: [printLogOnFailure: true], packageVariables: [preserveVariables: false, variables: "fred=one\ncommit=${scmVars.GIT_COMMIT}"])}}{code}Log: {code:java}[Pipeline] echo (hide)[GIT_BRANCH:origin/master, GIT_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_LOCAL_BRANCH:master, GIT_PREVIOUS_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_PREVIOUS_SUCCESSFUL_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_URL:https://github.com/andrew-sumner/Accounts.git][Pipeline] buildMasterWithApplicationRelease (hide)[BuildMaster] Sending POST to http://inedo:8622/api/releases[BuildMaster] With application/x-www-form-urlencoded content:[BuildMaster] key=xxx&applicationId=2&status=active[BuildMaster] Sending POST to http://inedo:8622/api/releases[BuildMaster] With application/x-www-form-urlencoded content:[BuildMaster] key=xxx&applicationId=2&releaseNumber=0.0.0[BuildMaster] Inject environment variable BUILDMASTER_APPLICATION_ID=2[BuildMaster] Inject environment variable BUILDMASTER_RELEASE_NUMBER=0.0.0[BuildMaster] Inject environment variable BUILDMASTER_PACKAGE_NUMBER=9, sourced from BuildMaster[Pipeline] { (hide)[Pipeline] buildMasterCreatePackage (hide)[BuildMaster] Sending GET to http://inedo:8622/api/json/Applications_GetApplication?API_Key=xxx&Application_Id=2[BuildMaster] Create BuildMaster package with PackageNumber=9[BuildMaster] Sending PUT to http://inedo:8622/api/releases/packages/create[BuildMaster] With application/x-www-form-urlencoded content:[BuildMaster] key=xxx&applicationId=2&releaseNumber=0.0.0&packageNumber=9&$commit=b9f3e9741ea20e767ddbc7d6087ba7afc09221e7&$fred=one[BuildMaster] Wait for any active deployments to complete{code}{color:#33} {color}
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
Not sure what's going on here. I've created a sample deployment using jenkins buildmaster plugin 2.1.1. Can you:
Confirm which version of the plugin you are using. Ideally you'll need to upgrade to 2.1.1 if you're not already using this. Note that this version has renamed setBuildVariables from buildMasterCreatePackage to packageVariables.
Echo out your gitprops variable and ensure it is populated correctly
Show how gitprops is being populated
As you can see in the log output below that the two variables (commit and fred) appear in the logs, but I cannot see the same for your output. All I can think is that you're using an early release of the plugin that contains a bug or that somehow the variables not not getting passed to the plugin correctly. Code:
node {
scmVars = git(credentialsId: 'andrew-git', url: 'https://github.com/andrew-sumner/Accounts.git')
echo "$scmVars"
buildMasterWithApplicationRelease(applicationId: '2', packageNumberSource: 'BUILDMASTER') {
BUILDMASTER_PACKAGE_NUMBER = buildMasterCreatePackage(applicationId: BUILDMASTER_APPLICATION_ID, releaseNumber: BUILDMASTER_RELEASE_NUMBER, packageNumber: BUILDMASTER_PACKAGE_NUMBER, deployToFirstStage: true, waitTillBuildCompleted: [printLogOnFailure: true], packageVariables: [preserveVariables: false, variables: "fred=one\ncommit=${scmVars.GIT_COMMIT}"])
}
}
Log:
[Pipeline] echo (hide)
[GIT_BRANCH:origin/master, GIT_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_LOCAL_BRANCH:master, GIT_PREVIOUS_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_PREVIOUS_SUCCESSFUL_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_URL:https://github.com/andrew-sumner/Accounts.git]
[Pipeline] buildMasterWithApplicationRelease (hide)
[BuildMaster] Sending POST to http://inedo:8622/api/releases
[BuildMaster] With application/x-www-form-urlencoded content:
[BuildMaster] key=xxx&applicationId=2&status=active
[BuildMaster] Sending POST to http://inedo:8622/api/releases
[BuildMaster] With application/x-www-form-urlencoded content:
[BuildMaster] key=xxx&applicationId=2&releaseNumber=0.0.0
[BuildMaster] Inject environment variable BUILDMASTER_APPLICATION_ID=2
[BuildMaster] Inject environment variable BUILDMASTER_RELEASE_NUMBER=0.0.0
[BuildMaster] Inject environment variable BUILDMASTER_PACKAGE_NUMBER=9, sourced from BuildMaster
[Pipeline] { (hide)
[Pipeline] buildMasterCreatePackage (hide)
[BuildMaster] Sending GET to http://inedo:8622/api/json/Applications_GetApplication?API_Key=xxx&Application_Id=2
[BuildMaster] Create BuildMaster package with PackageNumber=9
[BuildMaster] Sending PUT to http://inedo:8622/api/releases/packages/create
[BuildMaster] With application/x-www-form-urlencoded content:
[Build
[JIRA] (JENKINS-54397) Microfocus Health Analyzer check LR scenario on Master(Jenkins Server) only
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-54397 Microfocus Health Analyzer check LR scenario on Master(Jenkins Server) only Change By: Daniel Gront Microfocus Micro Focus Health Analyzer check LR scenario build step: all checks are executed on Master (Jenkins Server) only instead of Slave . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54397) Microfocus Health Analyzer check LR scenario on Master(Jenkins Server) only
Title: Message Title Daniel Gront started work on JENKINS-54397 Change By: Daniel Gront Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44947) NPE for jenkins.queue values
Title: Message Title Marky Jackson assigned an issue to Marky Jackson Jenkins / JENKINS-44947 NPE for jenkins.queue values Change By: Marky Jackson Assignee: Lars Sjostrom Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49222) Summaries doesn't contain _sum metrics
Title: Message Title Marky Jackson assigned an issue to Marky Jackson Jenkins / JENKINS-49222 Summaries doesn't contain _sum metrics Change By: Marky Jackson Assignee: Lars Sjostrom Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44513) Request to GET /prometheus takes a huge amount of time (and memory)
Title: Message Title Marky Jackson assigned an issue to Marky Jackson Jenkins / JENKINS-44513 Request to GET /prometheus takes a huge amount of time (and memory) Change By: Marky Jackson Assignee: Lars Sjostrom Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44259) Jenkins is hanged due to plugin prometheus
Title: Message Title Marky Jackson assigned an issue to Marky Jackson Jenkins / JENKINS-44259 Jenkins is hanged due to plugin prometheus Change By: Marky Jackson Assignee: Lars Sjostrom Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
