[JIRA] (JENKINS-59966) Prometheus Plugin: Causes StackOverFlowerError
Title: Message Title Marcel Hillmann commented on JENKINS-59966 Re: Prometheus Plugin: Causes StackOverFlowerError hi, any updates, facing the same issue. Thx Marcel Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202770.1572283306000.5392.1574406720405%40Atlassian.JIRA.
[JIRA] (JENKINS-60013) Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration.
Title: Message Title Aish R commented on JENKINS-60013 Re: Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration. Jason Vorpahl As a work around,I have written a groovy script to fetch version from the metadata.xml. For now it solves my requirement. I'm still waiting for a fix with repository connector plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202834.1572594308000.5389.1574405940201%40Atlassian.JIRA.
[JIRA] (JENKINS-60236) git parameter plugin does not apply remote setting changes
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60236 git parameter plugin does not apply remote setting changes Change By: Mark Waite Component/s: git-parameter-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203212.1574290206000.5384.1574400780202%40Atlassian.JIRA.
[JIRA] (JENKINS-57754) [FUTURE] Advanced button should align with delete button
Title: Message Title Allan C commented on JENKINS-57754 Re: [FUTURE] Advanced button should align with delete button Oleg Nenashev Hi Oleg. I noticed that this issue is still unresolved and wonder if I can take this as my first trial contribution to the Jenkins Community? Do you mind showing me where this is located in the codebase? Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199699.1559162932000.5373.1574390280222%40Atlassian.JIRA.
[JIRA] (JENKINS-60232) Add AppCenter API models for error responses for used APIs
Title: Message Title Mez Pahlan updated JENKINS-60232 Jenkins / JENKINS-60232 Add AppCenter API models for error responses for used APIs Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203208.157426942.5370.1574379540105%40Atlassian.JIRA.
[JIRA] (JENKINS-60236) git parameter plugin does not apply remote setting changes
Title: Message Title Mark Waite commented on JENKINS-60236 Re: git parameter plugin does not apply remote setting changes The old address or hostname must be stored somewhere in the Jenkins system. If you have access to the JENKINS_HOME directory and can safely search it, you might search for it and use that location to make a guess about what needs to be changed to correct the problem. It seems to me that the repository URL must be stored somewhere, otherwise Jenkins would not be able find the Jenkinsfile which contains the scm step. Where ever that is (job definition if a Pipeline job, multi-branch job definition if a multi-branch pipeline, organization folder if an Org Folder), assure it is the correct URL. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203212.1574290206000.5369.1574374680253%40Atlassian.JIRA.
[JIRA] (JENKINS-57940) readJSON from pipeline-utility-steps-plugin swallows keys named 'class'
Title: Message Title Tobin Davis commented on JENKINS-57940 Re: readJSON from pipeline-utility-steps-plugin swallows keys named 'class' Apparently this is because Jenkins uses a patched json-lib to remove "class", "declaringClass", and "metaClass" from json files. See https://github.com/jenkinsci/json-lib/blob/16052d1f74908fb59430eddd73f42aec2469b313/src/main/java/net/sf/json/JsonConfig.java#L49. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199915.1560178567000.5367.1574370240223%40Atlassian.JIRA.
[JIRA] (JENKINS-60214) Plugin installation manager does not work with other update sites
Title: Message Title leemeador updated an issue Jenkins / JENKINS-60214 Plugin installation manager does not work with other update sites Change By: leemeador I've found that jenkins-plugin-manager-1.0.1 fails when not used against updates.jenkins.io. For example, the Cloudbees update center fails because that site has no update-center.actual.json file available there. There seems to be is an update-center.json for all of the update centers .The actual file has pure json content while the non-actual file has a wrapper around the json which is "updateCenter.post( ... json goes here ... );" Someone said that has to do with allowing the file to be more easily compatible with browsers use of _javascript_. I don't know if the best thing is to get Cloudbees to add the non-actual file or change the code to remove the wrapper text in in the non-actual file and use it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to t
[JIRA] (JENKINS-60214) Plugin installation manager does not work with other update sites
Title: Message Title leemeador updated an issue Jenkins / JENKINS-60214 Plugin installation manager does not work with other update sites Change By: leemeador Summary: Plugin installation manager does not work with Cloudbees other update site sites Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203187.1574190061000.5363.1574368500073%40Atlassian.JIRA.
[JIRA] (JENKINS-60220) Multibranch pipeline with Helix Swarm source doesn't sync to latest
Title: Message Title William Brode commented on JENKINS-60220 Re: Multibranch pipeline with Helix Swarm source doesn't sync to latest Thanks for being so diligent Karl Wirth! Your options and notes look good to me. I will say that I've seen some teams use an option like "Pin at a good build label" before (this was a custom built system using shelved CLs - not going through swarm). It is another viable way to think of the problem (verify their change was good at some point in time) - but I'm not really sure how you would implement that for multibranch pipelines with helix swarm source. I'm also not convinced that way of approaching the problem is really that useful - I think its just a way of getting around your master branch being broken for way too long (the real problem). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203193.1574213884000.5361.1574367540243%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Jesse Glick commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login My second test was using local port 8090 so I doubt it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203169.1574080196000.5352.1574364480292%40Atlassian.JIRA.
[JIRA] (JENKINS-60246) The issue is very pressing
Title: Message Title jonny appleseed started work on JENKINS-60246 Change By: jonny appleseed Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203228.1574363115000.5345.1574363400291%40Atlassian.JIRA.
[JIRA] (JENKINS-60246) The issue is very pressing
Title: Message Title RAT thx commented on JENKINS-60246 Re: The issue is very pressing wow cool issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203228.1574363115000.5342.1574363220183%40Atlassian.JIRA.
[JIRA] (JENKINS-60246) The issue is very pressing
Title: Message Title jonny appleseed created an issue Jenkins / JENKINS-60246 The issue is very pressing Issue Type: Task Assignee: Unassigned Components: _unsorted Created: 2019-11-21 19:05 Environment: I dont know Labels: jenkins Priority: Minor Reporter: jonny appleseed This issue is such a pain that I had to create this just to send myself an email. Add Comment
[JIRA] (JENKINS-60013) Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration.
Title: Message Title Jason Vorpahl commented on JENKINS-60013 Re: Maven Artifact Repository Parameter fetches artifact from all the repositories mentioned in the global configuration. I was going to submit this issue as I also ran into this. Repository Connector version: 1.2.6 Jenkins version: 2.131 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202834.1572594308000.5339.1574362920135%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Charles Jones reopened an issue Jenkins / JENKINS-59503 Plugin does not save settings Change By: Charles Jones Resolution: Fixed Status: Resolved Reopened Assignee: Martin Reinhardt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202124.1569316263000.5332.1574361060849%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Charles Jones edited a comment on JENKINS-59503 Re: Plugin does not save settings Just adding a data point that I am experiencing the exact same issue as Nikolay. I have also upgraded the plugin 1.4.7 and running Jenkins 2.205. My issue manifests if I add any sort of custom message in the RocketChat Notifier plugin settings, after which I am not able to save the job. I note that if I do NOT populate the "Custom Message" field, I am able to save the job without an error. I note this issue is marked as "Resolved". If it stays in this state it will not be addressed :) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202124.1569316263000.5323.1574361000457%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Charles Jones commented on JENKINS-59503 Re: Plugin does not save settings Just adding a data point that I am experiencing the exact same issue as Nikolay. I have also upgraded the plugin 1.4.7 and running Jenkins 2.205. My issue manifests if I add any sort of custom message in the RocketChat Notifier plugin settings, after which I am not able to save the job. I note that if I do NOT populate the "Custom Message" field, I am able to save the job without an error. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202124.1569316263000.5315.1574360880339%40Atlassian.JIRA.
[JIRA] (JENKINS-60236) git parameter plugin does not apply remote setting changes
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60236 git parameter plugin does not apply remote setting changes Change By: Mark Waite Summary: git parameter plugin does not apply remote setting changes Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203212.1574290206000.5312.1574359320230%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Ben Cooksley commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login I wonder if this is due to the non-standard port for Jenkins itself - that configuration uses 8080, whereas my setup uses 8100/8200 (for each of the two impacted instances respectively), and Olli above uses 8180. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203169.1574080196000.5310.1574359200729%40Atlassian.JIRA.
[JIRA] (JENKINS-60245) @Library annotation does not work in load()'d scripts
Title: Message Title Austin commented on JENKINS-60245 Re: @Library annotation does not work in load()'d scripts Potential solution submitted in https://github.com/jenkinsci/workflow-cps-global-lib-plugin/pull/87 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203227.1574357617000.5301.1574358900050%40Atlassian.JIRA.
[JIRA] (JENKINS-54043) Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error
Title: Message Title W. Jiang commented on JENKINS-54043 Re: Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error same error with testlink plugin 3.16 on windows: ''' org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/plugins/testlink/WEB-INF/lib/testlink.jar!/hudson/plugins/testlink/TestLinkResult/index.jelly:6:57: No page found 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResultorg.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/plugins/testlink/WEB-INF/lib/testlink.jar!/hudson/plugins/testlink/TestLinkResult/index.jelly:6:57: No page found 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResult at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) 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.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.impl.ScriptBlock.run(ScriptBlock.java:95) ''' Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60236) git plugin does not apply remote setting changes
Title: Message Title Tim Bretz commented on JENKINS-60236 Re: git plugin does not apply remote setting changes For clarification, the new Bitbucket server was working for at least a week at the new IP address before this became an issue, and there are other jobs using the same configuration as this, but without the git parameters plugin. I don't think this has to do with the git plugin given that it is functioning correctly on the same jenkins instance in other jobs, although having the ability to configure the git plugin beyond what is given in the pipeline may alleviate the issue that causes other plugins to break. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203212.1574290206000.5297.1574358060128%40Atlassian.JIRA.
[JIRA] (JENKINS-60160) Text Parameter input field displayed as single string
Title: Message Title Michael Kostukov commented on JENKINS-60160 Re: Text Parameter input field displayed as single string Ping? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203112.157368348.5295.1574357760054%40Atlassian.JIRA.
[JIRA] (JENKINS-60245) @Library annotation does not work in load()'d scripts
Title: Message Title
Austin updated an issue
Jenkins / JENKINS-60245
@Library annotation does not work in load()'d scripts
Change By:
Austin
h1. Problem StatementOn a Jenkins master with global definition of a Shared Library named {{shared-library}}, And the following files in a repository:{{Jenkinsfile}}{code :java }node { stage( "setup" ) { checkout scm } stage( "pipeline" ) { load( "Pipeline.groovy" ).run_pipeline() }}{code}{{Pipeline.groovy}}{code :java }@Library( 'shared-library@master' ) _ def run_pipeline() { someMethodFromSharedLibrary()}return this{code}Where {{someMethodFromSharedLibrary()}} is a Global Variable in the {{vars/someMethodFromSharedLibrary.groovy}} file in the shared library,The pipeline errors on the {{load(...)}} step of the {{Jenkinsfile}} with a "no definition of libraries found" error:{code:java}ERROR: Could not find any definition of libraries [shared-library@master]{code}h1. AnalysisThis is because of the algorithm in {{LibraryAdder}} here:{quote}{code:java}LibrariesAction action = "">if (action != null) {{code}– [https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/f371b987a3e79928962043f18a5d95aef7397b76/src/main/java/org/jenkinsci/plugins/workflow/libs/LibraryAdder.java#L88-L89]{quote}After the main {{Jenkinsfile}} script is processed, a {{LibrariesAction}} is added to the build with no library definitions. When the new script {{Pipeline.groovy}} is processed during {{load(..)}}, it sees the action from the previous script and uses the empty set of library definitions to match against actual library requests that are correctly detected in the {{@Library}} annotation in the {{load()}}'d script.This causes the "no definition for libraries" error message. The library definitions in the {{load()}}'d script are never considered.
Add Comment
[JIRA] (JENKINS-60245) @Library annotation does not work in load()'d scripts
Title: Message Title
Austin created an issue
Jenkins / JENKINS-60245
@Library annotation does not work in load()'d scripts
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin
Created:
2019-11-21 17:33
Priority:
Minor
Reporter:
Austin
Problem Statement On a Jenkins master with global definition of a Shared Library named shared-library, And the following files in a repository: Jenkinsfile
node {
stage( "setup" ) {
checkout scm
}
stage( "pipeline" ) {
load( "Pipeline.groovy" ).run_pipeline()
}
}
Pipeline.groovy
@Library( 'shared-library@master' )
def run_pipeline() {
someMethodFromSharedLibrary()
}
return this
Where someMethodFromSharedLibrary() is a Global Variable in the vars/someMethodFromSharedLibrary.groovy file in the shared library, The pipeline errors on the load(...) step of the Jenkinsfile with a "no definition of libraries found" error:
ERROR: Could not find any definition of libraries [shared-library@master]
Analysis This is because of the algorithm in LibraryAdder here:
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Jesse Glick commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login These directives look like they are properly mirrored to me. I also tried the same without the context path (/jenkins → /) and with nocanon replaced with retry=0 as in your example. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203169.1574080196000.5285.1574357100274%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Ben Cooksley commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Could you provide the ProxyPass / ProxyPassReverse statements from your test image? If they mirror the fix I mentioned above already, then this would explain why it works for you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203169.1574080196000.5277.1574356861021%40Atlassian.JIRA.
[JIRA] (JENKINS-60220) Multibranch pipeline with Helix Swarm source doesn't sync to latest
Title: Message Title Karl Wirth commented on JENKINS-60220 Re: Multibranch pipeline with Helix Swarm source doesn't sync to latest Hi William Brode -I agree. I've been trying to get my head around the basic scenario's and the edge cases to those. I'll discuss with the developers and get back to you. My notes for me and devs. Options: Pin at good build label? - A possible option but paramaterized builds or code in jenkinsfile could be used to implement this if really needed (not multibranch). Pin at current head? - Valid for the time the review is created updated and committed (pre-commit). Cannot see a negative. Pin at review CL? - What if the code has moved on and the review is then updated. Need to sync to the later code. Pin at head when review created/updated/comitted? - Would allow for delayed builds but why is this better than current head? Reproduction steps for sync at review CL (1) Create a multibranch job with a known Swarm project with branches defined that contain a Jenkinsfile as the branch sources. (2) Create a review. (3) Use 'Scan Multibranch Pipeline Now' to build review. (4) Submit 5 seperate changelists to move the changelist counter on. (5) Update the review with a new version of the file: p4 unshelve -s REVIEWNUMBER echo test >> FileInReview p4 shelve FileInReview Use the text #review-REVIEWNUMBER in the shelve description text. (6) Use 'Scan Multibranch Pipeline Now' to build review. (7) The review will sync to the REVIEWNUMBER. For example my review number was '2138' but my head changelist was 2224 for this branch (and whole server). P4 Task: syncing files at change: 2138 ... p4 sync /var/lib/jenkins/workspace/SwarmMultiBranch_2138-ABD46HS2B5QL7YUAEOKK7ZF263___ -p4 sync /var/lib/jenkins/workspace/SwarmMultiBranch_2138-ABD46HS2B5QL7YUAEOKK7ZF263QXSASZ4PXEGIEWBMTBRK3QG5AQ/...@2138 /var/lib/jenkins/workspace/SwarmMultiBranch_2138-ABD46HS2B5QL7YUAEOKK7ZF263QXSASZ4PXEGIEWBMTBRK3QG5AQ/...@2138 - file(s) up-to-date. duration: (3ms) P4 Task: unshelve review: 2138 ... p4 unshelve -f -s2138 -cdefault +//depot/Project1/f2136
[JIRA] (JENKINS-60220) Multibranch pipeline with Helix Swarm source doesn't sync to latest
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-60220 Multibranch pipeline with Helix Swarm source doesn't sync to latest Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203193.1574213884000.5282.1574356861325%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI daniel zhang Your suggestion fixed our issue ! Thank you so very much, this issue was very annoying to us. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.5268.1574356620394%40Atlassian.JIRA.
[JIRA] (JENKINS-60236) git plugin does not apply remote setting changes
Title: Message Title Tim Bretz updated an issue Jenkins / JENKINS-60236 git plugin does not apply remote setting changes Change By: Tim Bretz Summary: git plugin does not apply remote setting changes to existing workspaces Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203212.1574290206000.5260.1574351280177%40Atlassian.JIRA.
[JIRA] (JENKINS-60236) git plugin does not apply remote setting changes to existing workspaces
Title: Message Title Tim Bretz commented on JENKINS-60236 Re: git plugin does not apply remote setting changes to existing workspaces deleting the workspace did not resolve this issue Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203212.1574290206000.5258.1574351160140%40Atlassian.JIRA.
[JIRA] (JENKINS-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title
Lucas Cimon edited a comment on JENKINS-44924
Re: pipeline groovy script - Sort a list with custom comparator or closure not sorting
I found bit of helpful context about this issue : [https://wiki.jenkins.io/display/JENKINS/Pipeline+CPS+method+mismatches#PipelineCPSmethodmismatches-Callingnon-CPS-transformedmethodswithCPS-transformedarguments]Edit: captain obvious... I did not notice the link to this exact issue on the wiki :)Here is the workaround I used to sort a list of maps base Map objects, based on a String field:{code:java}pipeline {stages {stage("Test") {steps {script {def propList = [[name: 'B'], [name: 'A']]sortByField(propList, 'name')propList.eachWithIndex { entry, i -> println "${i}: ${entry}"}}}}}}@NonCPSstatic sortByField(list, fieldName) {list.sort{ it[fieldName] }} {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182995.1497544785000.5219.1574350261418%40Atlassian.JIRA.
[JIRA] (JENKINS-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title
Lucas Cimon edited a comment on JENKINS-44924
Re: pipeline groovy script - Sort a list with custom comparator or closure not sorting
I found bit of helpful context about this issue : [https://wiki.jenkins.io/display/JENKINS/Pipeline+CPS+method+mismatches#PipelineCPSmethodmismatches-Callingnon-CPS-transformedmethodswithCPS-transformedarguments] Edit: captain obvious... I did not notice the link to this exact issue on the wiki :) Here is the workaround I used to sort a list of maps base on a String field:{code:java}pipeline {stages {stage("Test") {steps {script {def propList = [[name: 'B'], [name: 'A']]sortByField(propList, 'name')propList.eachWithIndex { entry, i -> println "${i}: ${entry}"}}}}}}@NonCPSstatic sortByField(list, fieldName) {list.sort{ it[fieldName] }} {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182995.1497544785000.5179.1574350201680%40Atlassian.JIRA.
[JIRA] (JENKINS-60236) git plugin does not apply remote setting changes to existing workspaces
Title: Message Title Tim Bretz commented on JENKINS-60236 Re: git plugin does not apply remote setting changes to existing workspaces Mark Waite The repository URL is only specified in the `scm` step and is not a paramter. Neither plugin has configurations available in the UI related to the remote URL. My only possible solution at this point is to change the IP of the new Bitbucket server, which amazes me that we can never change the IP because these plugins are not configurable on level beyond what is entered in the pipeline, and even then the configuration in the pipeline doesn't apply to the plugins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203212.1574290206000.5169.1574349480342%40Atlassian.JIRA.
[JIRA] (JENKINS-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title Lucas Cimon edited a comment on JENKINS-44924 Re: pipeline groovy script - Sort a list with custom comparator or closure not sorting I found bit of helpful context about this issue : [ https://wiki.jenkins.io/display/JENKINS/Pipeline+CPS+method+mismatches#PipelineCPSmethodmismatches-Callingnon-CPS-transformedmethodswithCPS-transformedarguments ] Edit: captain obvious... I did not notice the link to this exact issue on the wiki :) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182995.1497544785000.5130.1574348940941%40Atlassian.JIRA.
[JIRA] (JENKINS-58353) New jenkins job doesn't get added to the Dashboard view using Python Jenkins
Title: Message Title Vineeth Karkad commented on JENKINS-58353 Re: New jenkins job doesn't get added to the Dashboard view using Python Jenkins Hi Máté! Thanks for chiming in. We haven't come up with any solution as yet. Hopefully this ticket gets attention of the right folks and prioritised to get fixed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200468.1562310678000.5126.1574348700364%40Atlassian.JIRA.
[JIRA] (JENKINS-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title Lucas Cimon commented on JENKINS-44924 Re: pipeline groovy script - Sort a list with custom comparator or closure not sorting I found bit of helpful context about this issue : https://wiki.jenkins.io/display/JENKINS/Pipeline+CPS+method+mismatches#PipelineCPSmethodmismatches-Callingnon-CPS-transformedmethodswithCPS-transformedarguments Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182995.1497544785000.5087.1574348581099%40Atlassian.JIRA.
[JIRA] (JENKINS-60236) git plugin does not apply remote setting changes to existing workspaces
Title: Message Title Mark Waite commented on JENKINS-60236 Re: git plugin does not apply remote setting changes to existing workspaces Tim Bretz that may indicate an issue in the git parameter plugin. Are you providing the repository URL as a parameter to the job? If so, then you might try redefining the job temporarily to not parameterize the repository URL, run it with the corrected URL, then add the repository URL parameter to the job again. There may be some internal storage of the repository URL in the git parameter plugin which is not being adjusted when you change the repository URL elsewhere. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203212.1574290206000.5084.1574348220265%40Atlassian.JIRA.
[JIRA] (JENKINS-60236) git plugin does not apply remote setting changes to existing workspaces
Title: Message Title Tim Bretz commented on JENKINS-60236 Re: git plugin does not apply remote setting changes to existing workspaces Mark Waite I can't reach the `deleteDir` step even though it is the first step, because I can't get passed the required parameters. I tried copying the pipeline into a new job and it was unable to read any configuration at all. No Git repository configured in SCM configuration or plugin is configured wrong Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203212.1574290206000.5082.1574347500608%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Jesse Glick commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login setting ProxyPreserveHost to On doesn't appear to be a recommendation currently as it isn't mentioned in the default HTTP configuration in your own documentation for this type of setup. It appears under HTTPS ProxyPreserveHost On is suggested in the initial section, before any mention of HTTPS. Beware however that wiki.jenkins.io is just a collection of random edits made over many years with little oversight, not formal documentation. The demo container is what I actually verified five years ago (tracking down some more subtle issues with AllowEncodedSlashes), but ultimately the Jenkins project does not document and test a specific reverse proxy configuration—this is left either to individual administrators, or to a third-party packaging such as a Helm chart. At any rate, I retried my test with ProxyPreserveHost On commented out, using HTTPS, and redirects still worked. This is from a local development environment, which necessarily differs from a production network in various ways, so it may be more fruitful to discuss a particular HTTP response from Jenkins that could be reproduced without actually running a reverse proxy: given a specific minimal set of request headers (mixture of browser-provided and proxy-provided/amended), whether a specific response header (Location I suppose) has one value in Jenkins 2.204 and a different value in 2.205. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title
Jesse Glick commented on JENKINS-59788
Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Adam Gabryś just tried your example and could not reproduce. Fresh installation of Jenkins 2.190.2, with pipeline-model-definition, timestamper, ansicolor, pipeline-model-definition, mock-slave, after configuring a Mock Agent and using that label:
Started by user unknown or anonymous
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on mock in …/mock-agents/mock/workspace/p
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] stage
[Pipeline] { (loop)
[Pipeline] sh
09:00:24 + true
09:00:24 + echo line
09:00:24 line
09:00:24 + sleep 3
09:00:27 + true
09:00:27 + echo line
…
Not sure what other conditions are required to trigger this. Freestyle projects use a completely unrelated mechanism for timestamp annotation, so that is not relevant here.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.157113
[JIRA] (JENKINS-60244) Jenkins performance is slow while running Automation scripts .
Title: Message Title Ranjan Bhuyan created an issue Jenkins / JENKINS-60244 Jenkins performance is slow while running Automation scripts . Issue Type: Bug Assignee: Unassigned Attachments: Log.txt Components: jenkinsfile-runner, jenkinsfile-runner-test-framework Created: 2019-11-21 13:59 Priority: Critical Reporter: Ranjan Bhuyan Hi All Recently we migrated jenkins master to new jenkins master machine. after migrating to new jenkins master, Test script execution is taking lot of time compared to old jenkins. In old jenkins we were using .Net 4.5 and in new jenkins master we are using .Net 4.6.1 this is the only difference in old and new jenkins master. please suggest to make the machine fast to run the test automation scripts. Console Out Put for one scripts has been attached for reference . Add Comment
[JIRA] (JENKINS-58353) New jenkins job doesn't get added to the Dashboard view using Python Jenkins
Title: Message Title Csanády Máté edited a comment on JENKINS-58353 Re: New jenkins job doesn't get added to the Dashboard view using Python Jenkins Hi Vineeth!I am suffering from the same problem.Have you come up with a solution since july?Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200468.1562310678000.5002.1574344680328%40Atlassian.JIRA.
[JIRA] (JENKINS-58353) New jenkins job doesn't get added to the Dashboard view using Python Jenkins
Title: Message Title Csanády Máté commented on JENKINS-58353 Re: New jenkins job doesn't get added to the Dashboard view using Python Jenkins Vineeth! I am suffering from the same problem. Have you come up with a solution since july? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200468.1562310678000.4999.1574344680255%40Atlassian.JIRA.
[JIRA] (JENKINS-60243) Blue Ocean Input Step Json Error
Title: Message Title Ugur G updated an issue Jenkins / JENKINS-60243 Blue Ocean Input Step Json Error Change By: Ugur G Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203225.1574343655000.4996.1574344501094%40Atlassian.JIRA.
[JIRA] (JENKINS-60243) Blue Ocean Input Step Json Error
Title: Message Title Ugur G started work on JENKINS-60243 Change By: Ugur G Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203225.1574343655000.4995.157430254%40Atlassian.JIRA.
[JIRA] (JENKINS-59466) Nested Views are incompatible with Config as Code
Title: Message Title Alex Taylor commented on JENKINS-59466 Re: Nested Views are incompatible with Config as Code After testing out the PR, I have found that Nested views just pretty much doesnt work with Config as code. This stops if from breaking but the views dont actually work which means either nested views needs to ensure that it is following Config as Code practices or CasC needs to change so that this plugin works with it. I am assuming the former is going to be easiest. Technically, this defect is "done" but the plugin still doesnt work with CasC Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202064.1569007172000.4994.1574344082831%40Atlassian.JIRA.
[JIRA] (JENKINS-60243) Blue Ocean Input Step Json Error
Title: Message Title
Ugur G created an issue
Jenkins / JENKINS-60243
Blue Ocean Input Step Json Error
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
issue.jpg
Components:
blueocean-plugin
Created:
2019-11-21 13:40
Environment:
Jenkins 2.190.3 Blue Ocean 1.21.0
Priority:
Minor
Reporter:
Ugur G
Hello Today I've upgraded my blue ocean to 1.21.0 and I've started seeing json parse error on the input stage for a moment when I click to 'Proceed' then it dissapers and works well. Also classic ui works well too. Here is the sample code and error screenshot. Is there anyone facing with same issue.
pipeline {
agent none
options {
timestamps()
skipDefaultCheckout()
}
stages {
stage ("Promotion") {
steps {
timeout(time: 1, unit: 'HOURS') {
input 'Deploy to Production?'
}
milestone(ordinal: 1, label: "PROD_DEPLOYMENT_START_MILESTONE")
}
}
stage ("Deployment") {
agent any
steps {
echo 'Deploy to prod'
}
}
}
}
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title
Adam Gabryś edited a comment on JENKINS-59788
Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1
This is the simplest possible pipeline to reproduce (I could try to get the docker image used to create the pod):{code:java}pipeline { agent { label 'tiny' } options { timestamps() } stages { stage('loop') { steps { sh '''while true;do echo 'line' sleep 3done ''' } } }}{code}I see no timestamps in logs:{noformat}Started by user Gabrys, AdamRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeAgent zjs-agabrys-tiny-qtc0t is provisioned from template Kubernetes Pod TemplateRunning on zjs-agabrys-tiny-qtc0t in /var/lib/jenkins/workspace/test[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] stage[Pipeline] { (loop)[Pipeline] sh+ true+ echo lineline+ sleep 3+ true+ echo lineline+ sleep 3+ true{noformat}Luckily, we found the new option available {{Manage Jenkins → Configure System → Timestamper}}: *{{Enabled for all Pipeline builds}}*. I enabled it, removed {{options}} block from Jenkinsfile and this is the result:{noformat}14:12:42 Started by user Gabrys, Adam14:12:42 Running in Durability level: MAX_SURVIVABILITY14:12:42 [Pipeline] Start of Pipeline14:12:42 [Pipeline] node14:12:57 Still waiting to schedule task14:12:57 All nodes of label ‘tiny’ are offline14:13:07 Agent zjs-agabrys-tiny-xlmd4 is provisioned from template Kubernetes Pod Template14:13:07 Running on zjs-agabrys-tiny-xlmd4 in /var/lib/jenkins/workspace/test14:13:07 [Pipeline] {14:13:07 [Pipeline] stage14:13:07 [Pipeline] { (loop)14:13:07 [Pipeline] sh14:13:09 + true14:13:09 + echo line14:13:09 line14:13:09 + sleep 314:13:12 + true14:13:12 + echo line14:13:12 line14:13:12 + sleep 314:13:14 + true{noformat}We want activate timestamps activated for all our jobs. so we don't have this problem anymore (even though {{timestamps}} option doesn't work).One more interesting thing. Free style jobs never have problems with timestamps. When I add Timestamp wrapper and execute the job on agent I see:{noformat}14:20:07 Started by user Gabrys, Adam14:20:07 Running as SYSTEM14:20:07 Agent zjs-agabrys2-tiny-zfbqr is provisioned from template Kubernetes Pod Template14:20:07 Building remotely on zjs-agabrys2-tiny-zfbqr (tiny) in workspace /var/lib/jenkins/workspace/test214:20:08 [test2] $ /bin/bash -xe /tmp/jenkins1316037729727606180.sh14:20:08 + true14:20:08 + echo line14:20:08 line14:20:08 + sleep 314:20:11 + true14:20:11 + echo line{noformat}
Add Comment
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title
Adam Gabryś edited a comment on JENKINS-59788
Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1
This is the simplest possible pipeline to reproduce (I could try to get the docker image used to create the pod):{code:java}pipeline { agent { label 'tiny' } options { timestamps() } stages { stage('loop') { steps { sh '''while true;do echo 'line' sleep 3done ''' } } }}{code}I see no timestamps in logs:{noformat}Started by user Gabrys, AdamRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeAgent zjs-agabrys-tiny-qtc0t is provisioned from template Kubernetes Pod TemplateRunning on zjs-agabrys-tiny-qtc0t in /var/lib/jenkins/workspace/test[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] stage[Pipeline] { (loop)[Pipeline] sh+ true+ echo lineline+ sleep 3+ true+ echo lineline+ sleep 3+ true{noformat}Luckily, we found the new option available {{Manage Jenkins → Configure System → Timestamper}}: *{{Enabled for all Pipeline builds}}*. I enabled it, removed \ {{options { timestamps() }} } block from Jenkinsfile and this is the result:{noformat}14:12:42 Started by user Gabrys, Adam14:12:42 Running in Durability level: MAX_SURVIVABILITY14:12:42 [Pipeline] Start of Pipeline14:12:42 [Pipeline] node14:12:57 Still waiting to schedule task14:12:57 All nodes of label ‘tiny’ are offline14:13:07 Agent zjs-agabrys-tiny-xlmd4 is provisioned from template Kubernetes Pod Template14:13:07 Running on zjs-agabrys-tiny-xlmd4 in /var/lib/jenkins/workspace/test14:13:07 [Pipeline] {14:13:07 [Pipeline] stage14:13:07 [Pipeline] { (loop)14:13:07 [Pipeline] sh14:13:09 + true14:13:09 + echo line14:13:09 line14:13:09 + sleep 314:13:12 + true14:13:12 + echo line14:13:12 line14:13:12 + sleep 314:13:14 + true{noformat}We want timestamps activated for all our jobs. so we don't have this problem anymore (even though {{timestamps}} option doesn't work).One more interesting thing. Free style jobs never have problems with timestamps. When I add Timestamp wrapper and execute the job on agent I see:{noformat}14:20:07 Started by user Gabrys, Adam14:20:07 Running as SYSTEM14:20:07 Agent zjs-agabrys2-tiny-zfbqr is provisioned from template Kubernetes Pod Template14:20:07 Building remotely on zjs-agabrys2-tiny-zfbqr (tiny) in workspace /var/lib/jenkins/workspace/test214:20:08 [test2] $ /bin/bash -xe /tmp/jenkins1316037729727606180.sh14:20:08 + true14:20:08 + echo line14:20:08 line14:20:08 + sleep 314:20:11 + true14:20:11 + echo line{noformat}
Add Comment
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title
Adam Gabryś edited a comment on JENKINS-59788
Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1
This is the simplest possible pipeline to reproduce (I could try to get the docker image used to create the pod) :{code:java}pipeline { agent { label 'tiny' } options { timestamps() } stages { stage('loop') { steps { sh '''while true;do echo 'line' sleep 3done ''' } } }}{code}I see no timestamps in logs:{noformat}Started by user Gabrys, AdamRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeAgent zjs-agabrys-tiny-qtc0t is provisioned from template Kubernetes Pod TemplateRunning on zjs-agabrys-tiny-qtc0t in /var/lib/jenkins/workspace/test[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] stage[Pipeline] { (loop)[Pipeline] sh+ true+ echo lineline+ sleep 3+ true+ echo lineline+ sleep 3+ true{noformat}Luckily, we found the new option available {{Manage Jenkins → Configure System → Timestamper}}: *{{Enabled for all Pipeline builds}}*. I enabled it, removed \ {{options \ { timestamps() }}} from Jenkinsfile and this is the result:{noformat}14:12:42 Started by user Gabrys, Adam14:12:42 Running in Durability level: MAX_SURVIVABILITY14:12:42 [Pipeline] Start of Pipeline14:12:42 [Pipeline] node14:12:57 Still waiting to schedule task14:12:57 All nodes of label ‘tiny’ are offline14:13:07 Agent zjs-agabrys-tiny-xlmd4 is provisioned from template Kubernetes Pod Template14:13:07 Running on zjs-agabrys-tiny-xlmd4 in /var/lib/jenkins/workspace/test14:13:07 [Pipeline] {14:13:07 [Pipeline] stage14:13:07 [Pipeline] { (loop)14:13:07 [Pipeline] sh14:13:09 + true14:13:09 + echo line14:13:09 line14:13:09 + sleep 314:13:12 + true14:13:12 + echo line14:13:12 line14:13:12 + sleep 314:13:14 + true{noformat}We want timestamps activated for all our jobs. so we don't have this problem anymore (even though {{timestamps}} option doesn't work).One more interesting thing. Free style jobs never have problems with timestamps. When I add Timestamp wrapper and execute the job on agent I see:{noformat}14:20:07 Started by user Gabrys, Adam14:20:07 Running as SYSTEM14:20:07 Agent zjs-agabrys2-tiny-zfbqr is provisioned from template Kubernetes Pod Template14:20:07 Building remotely on zjs-agabrys2-tiny-zfbqr (tiny) in workspace /var/lib/jenkins/workspace/test214:20:08 [test2] $ /bin/bash -xe /tmp/jenkins1316037729727606180.sh14:20:08 + true14:20:08 + echo line14:20:08 line14:20:08 + sleep 314:20:11 + true14:20:11 + echo line{noformat}
Add Comment
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title
Adam Gabryś commented on JENKINS-59788
Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1
This is the simplest possible pipeline to reproduce:
pipeline {
agent {
label 'tiny'
}
options {
timestamps()
}
stages {
stage('loop') {
steps {
sh '''
while true;
do
echo 'line'
sleep 3
done
'''
}
}
}
}
I see no timestamps in logs:
Started by user Gabrys, Adam
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Agent zjs-agabrys-tiny-qtc0t is provisioned from template Kubernetes Pod Template
Running on zjs-agabrys-tiny-qtc0t in /var/lib/jenkins/workspace/test
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] stage
[Pipeline] { (loop)
[Pipeline] sh
+ true
+ echo line
line
+ sleep 3
+ true
+ echo line
line
+ sleep 3
+ true
Luckily, we found the new option available Manage Jenkins → Configure System → Timestamper: Enabled for all Pipeline builds. I enabled it, removed {{options { timestamps() }}} from Jenkinsfile and this is the result:
14:12:42 Started by user Gabrys, Adam
14:12:42 Running in Durability level: MAX_SURVIVABILITY
14:12:42 [Pipeline] Start of Pipeline
14:12:42 [Pipeline] node
14:12:57 Still waiting to schedule task
14:12:57 All nodes of label ‘tiny’ are offline
14:13:07 Agent zjs-agabrys-tiny-xlmd4 is provisioned from template Kubernetes Pod Template
14:13:07 Running on zjs-agabrys-tiny-xlmd4 in /var/lib/jenkins/workspace/test
14:13:07 [Pipeline] {
14:13:07 [Pipeline] stage
14:13:07 [Pipeline] { (loop)
14:13:07 [Pipeline] sh
14:13:09 + true
14:13:09 + echo line
14:13:09 line
14:13:09 + sleep 3
14:13:12 + true
14:13:12 + echo line
14:13:12 line
14:13:12 + sleep 3
14:13:14 + true
We want timestamps activated for all our jobs. so we don't have this problem anymore (even though timestamps option doesn't work). One more interesting thing. Free style jobs never have problems with timestamps. When I add Timestamp wrapper and execute the job on agent I see:
14:20:07 Started by user Gabrys, Adam
14:20:07 Running as SYSTEM
14:20:07 Agent zjs-agabrys2-tiny-zfbqr is provisioned from template Kubernetes Pod Template
14:20:07 Building remotely on zjs-agabrys2-tiny-zfbqr (tiny) in workspace /var/lib/jenkins/workspace/test2
14:20:08 [test2] $ /bin/bash -xe /tmp/jenkins1316037729727606180.sh
14:20:08 + true
14:20:08 + echo line
14:20:08 line
14:20:08 + slee
[JIRA] (JENKINS-60242) tty is not allocated for `sh` step in `docker` agent
Title: Message Title
Bartosz Rempuszewski updated an issue
Jenkins / JENKINS-60242
tty is not allocated for `sh` step in `docker` agent
Change By:
Bartosz Rempuszewski
With test pipeline:{code:java}pipeline {agent { docker { image 'alpine' } }stages {stage('test tty') {steps {sh "tty"}}}}{code} I can see in logs: {code:java}docker run -t -d [ ... other options ... ] cat{code}so the container is started with tty but output from `sh` command is:{code:java}+ ttynot a tty{code}It looks like shell command is executed with `docker exec somename somecommand` instead of `docker exec -t somename somecommand`Is there a way to start `sh` step with tty enabled? Note: in case of some commands it is important to run with `tty`, for example [https://mustache.github.io/mustache.1.html]`mustache --error params template` will fail with error. I am not sure if JENKINS-39013 is related - in my case container is run with tty but 'sh' step inside the container are not.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60242) tty is not allocated for `sh` step in `docker` agent
Title: Message Title
Bartosz Rempuszewski updated an issue
Jenkins / JENKINS-60242
tty is not allocated for `sh` step in `docker` agent
Change By:
Bartosz Rempuszewski
With test pipeline:{code:java}pipeline { agent { docker { image 'alpine' } } stages {stage('test tty') { agent { docker { image 'alpine'; alwaysPull true; reuseNode true } } steps {sh "tty"}}}}{code} I can see in logs: {code:java}docker run -t -d [ ... other options ... ] cat{code}so the container is started with tty but output from `sh` command is:{code:java}+ ttynot a tty{code}It looks like shell command is executed with `docker exec somename somecommand` instead of `docker exec -t somename somecommand`Is there a way to start `sh` step with tty enabled? Note: in case of some commands it is important to run with `tty`, for example [https://mustache.github.io/mustache.1.html]`mustache --error params template` will fail with error.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60242) tty is not allocated for `sh` step in `docker` agent
Title: Message Title
Bartosz Rempuszewski created an issue
Jenkins / JENKINS-60242
tty is not allocated for `sh` step in `docker` agent
Issue Type:
Bug
Assignee:
Unassigned
Components:
jenkinsfile-runner
Created:
2019-11-21 13:00
Priority:
Minor
Reporter:
Bartosz Rempuszewski
With test pipeline:
pipeline {
stages {
stage('test tty') {
agent { docker { image 'alpine'; alwaysPull true; reuseNode true } }
steps {
sh "tty"
}
}
}
}
I can see in logs:
docker run -t -d [ ... other options ... ] cat
so the container is started with tty but output from `sh` command is:
+ tty
not a tty
It looks like shell command is executed with `docker exec somename somecommand` instead of `docker exec -t somename somecommand` Is there a way to start `sh` step with tty enabled? Note: in case of some commands it is important to run with `tty`, for example https://mustache.github.io/mustache.1.html `mustache --error params template` will fail with error.
[JIRA] (JENKINS-60238) Warnings plugin "export your issues into a supported format" not useable
Title: Message Title Ulli Hafner resolved as Not A Defect Jenkins / JENKINS-60238 Warnings plugin "export your issues into a supported format" not useable Change By: Ulli Hafner Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203218.1574333603000.4944.1574340180702%40Atlassian.JIRA.
[JIRA] (JENKINS-60238) Warnings plugin "export your issues into a supported format" not useable
Title: Message Title Ulli Hafner commented on JENKINS-60238 Re: Warnings plugin "export your issues into a supported format" not useable I improved the documentation, see https://github.com/jenkinsci/warnings-ng-plugin/pull/275. The format is listed with the correct ID In the file SUPPORTED-FORMATS as well. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203218.1574333603000.4942.1574340180481%40Atlassian.JIRA.
[JIRA] (JENKINS-60238) Warnings plugin "export your issues into a supported format" not useable
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60238 Warnings plugin "export your issues into a supported format" not useable Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/275 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203218.1574333603000.4940.1574340120502%40Atlassian.JIRA.
[JIRA] (JENKINS-60241) Dynamic messages in build failure causes
Title: Message Title Gajanan Mahajan created an issue Jenkins / JENKINS-60241 Dynamic messages in build failure causes Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-11-21 12:36 Priority: Major Reporter: Gajanan Mahajan I'm using Build Failure Analyzer plugin of Jenkins to highlight failures. But while creating new failure cause, there are fields like Name and Description where we can mention about failure causes. We can have hard coded message there but can we please have support to add dynamic message there using build parameters or reading some values from console output? Add Comment
[JIRA] (JENKINS-60240) crash XML parser crash
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-60240 crash XML parser crash Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2019-11-21 12:27 Environment: latest Priority: Critical Reporter: Ronny Borchert We tried today to cancel a unit test then jenkins crashed with error. Unit test is xUnit Cpp1.12.1 plugin. 2019-11-21 11:36:46.158+ [id=5247] INFO hudson.model.Run#execute: xxx_RunUnitTest #60 main build action completed: SUCCESS2019-11-21 11:36:46.158+ [id=5247] INFO hudson.model.Run#execute: SRPFwk_Dev_RunUnitTest #60 main build action completed: SUCCESSRecoverable error on line 2 column 9 SXXP0003: Error reported by XML parser: Document is invalid: no grammar found.Recoverable error on line 2 column 9 SXXP0003: Error reported by XML parser: Document root element "TestRun", must match DOCTYPE root "null".Warning The XML parser reported two validation errors. Processing continues, because recovery from validation errors was requested Add Comment
[JIRA] (JENKINS-60238) Warnings plugin "export your issues into a supported format" not useable
Title: Message Title Jelle van Geel commented on JENKINS-60238 Re: Warnings plugin "export your issues into a supported format" not useable Thanks this indeeds resolves the issue. It would be helpful to make a reference in the documentation to use this tool. https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#export-your-issues-into-a-supported-format Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203218.1574333603000.4933.1574338021757%40Atlassian.JIRA.
[JIRA] (JENKINS-60238) Warnings plugin "export your issues into a supported format" not useable
Title: Message Title Ulli Hafner commented on JENKINS-60238 Re: Warnings plugin "export your issues into a supported format" not useable The correct ID is issues: recordIssues( enabledForFailure: true, aggregatingResults: true, tool: issues() ) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails 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.203218.1574333603000.4931.1574336040591%40Atlassian.JIRA.
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title
Daniel Puiu updated an issue
Jenkins / JENKINS-60239
Aborted catchError sets build result to ABORTED if fail fast is true
Change By:
Daniel Puiu
Hello, I have the following declarative pipeline:{code:java}pipeline { agent anyoptions { parallelsAlwaysFailFast() } stages {stage('A') {parallel {stage('A1') {steps { error 'fail' }}stage('A2') {steps { script { catchError(stageResult: 'FAILURE') { println 'a2' sleep 10 } }}}}}}}{code}The result is ABORTED instead of FAILURE.I think that somehow aborting a stage that contains a `catchError` _catchError_ affects the build result. For me the expected result is FAILURE
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title
Daniel Puiu updated an issue
Jenkins / JENKINS-60239
Aborted catchError sets build result to ABORTED if fail fast is true
Change By:
Daniel Puiu
Hello, I have the following declarative pipeline:{code:java}pipeline { agent anyoptions { parallelsAlwaysFailFast() } stages {stage('A') {parallel {stage('A1') {steps { error 'fail' }}stage('A2') {steps { script { catchError(stageResult: 'FAILURE') { println 'a2' sleep 10 } }}}}}}}{code}The result is ABORTED instead of FAILURE. I think that somehow aborting a stage that contains a `catchError` affects the build result.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title
Daniel Puiu updated an issue
Jenkins / JENKINS-60239
Aborted catchError sets build result to ABORTED if fail fast is true
Change By:
Daniel Puiu
Hello, I have the following declarative pipeline: {code:java}pipeline { agent anyoptions { parallelsAlwaysFailFast() } stages {stage('A') {parallel {stage('A1') {steps { error 'fail' }}stage('A2') {steps { script { catchError(stageResult: 'FAILURE') { println 'a2' sleep 10 } }}}}}}}{code}The result is ABORTED instead of FAILURE.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Grou
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title
Daniel Puiu updated an issue
Jenkins / JENKINS-60239
Aborted catchError sets build result to ABORTED if fail fast is true
Change By:
Daniel Puiu
Hello, I have the following declarative pipeline: {code:java}pipeline { agent anyoptions { parallelsAlwaysFailFast() } stages {stage('A') {parallel {stage('A1') {steps { error 'fail' }}stage('A2') {steps { script { catchError(stageResult: 'FAILURE') { println 'a2' sleep 10 } }}}}}}}{code}The result is ABORTED instead of FAILURE.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Gr
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title Daniel Puiu updated an issue Jenkins / JENKINS-60239 Aborted catchError sets build result to ABORTED if fail fast is true Change By: Daniel Puiu Environment: Jenkins: 2.198 Pipeline: Basic Steps: 2.16 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203219.1574333797000.4908.1574334000120%40Atlassian.JIRA.
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title
Daniel Puiu updated an issue
Jenkins / JENKINS-60239
Aborted catchError sets build result to ABORTED if fail fast is true
Change By:
Daniel Puiu
If I have a stage with a step in it:{noformat} ... catchError(buildResult: hudson.model.Result.SUCCESS, message: 'RPM build failed, but allowing job to continue', stageResult: hudson.model.Result.FAILURE) { sh label: env.STAGE_NAME, script: 'exit 2' }{noformat}With a {{post}} block for the stage:{noformat}post { always { archiveArtifacts artifacts: 'artifacts/**' } success { println "${env.STAGE_NAME}: SUCCESS" } unstable { println "${env.STAGE_NAME}: UNSTABLE" } failure { println "${env.STAGE_NAME}: FAILED" }}{noformat} I actually get the:{noformat}My Test Stage: SUCCESS{noformat}telling me that the stage was a SUCCESS, not a FAILURE like the:{{catchError(..., stageResult: hudson.model.Result.FAILURE)}} is supposed to be making it.In both the stage view and the Blue Ocean view, it does show as a failed stage. The {{post}} processing block just doesn't see it that way.As an aside, is there a variable set for the stage that I could use in my {{println}} above so that I could just do a single {{println}} in the {{always}} block rather than having to repeat it through the {{success}}, {{unstable}} and {{failure}} blocks?
Add Comment
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title Daniel Puiu updated an issue Jenkins / JENKINS-60239 Aborted catchError sets build result to ABORTED if fail fast is true Change By: Daniel Puiu Environment: Jenkins: 2. 164.3 198 Pipeline: Basic Steps: 2.16 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203219.1574333797000.4904.1574333880227%40Atlassian.JIRA.
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title Daniel Puiu assigned an issue to Unassigned Jenkins / JENKINS-60239 Aborted catchError sets build result to ABORTED if fail fast is true Change By: Daniel Puiu Assignee: Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203219.1574333797000.4906.1574333880258%40Atlassian.JIRA.
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title
Daniel Puiu created an issue
Jenkins / JENKINS-60239
Aborted catchError sets build result to ABORTED if fail fast is true
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2019-11-21 10:56
Environment:
Jenkins: 2.164.3 Pipeline: Basic Steps: 2.16
Labels:
pipeline
Priority:
Critical
Reporter:
Daniel Puiu
If I have a stage with a step in it:
...
catchError(buildResult: hudson.model.Result.SUCCESS,
message: 'RPM build failed, but allowing job to continue',
stageResult: hudson.model.Result.FAILURE) {
sh label: env.STAGE_NAME,
script: 'exit 2'
}
With a post block for the stage:
post {
always {
archiveArtifacts artifacts: 'artifacts/**'
}
success {
println "${env.STAGE_NAME}: SUCCES
[JIRA] (JENKINS-60238) Warnings plugin "export your issues into a supported format" not useable
Title: Message Title
Jelle van Geel updated an issue
Jenkins / JENKINS-60238
Warnings plugin "export your issues into a supported format" not useable
Change By:
Jelle van Geel
My goal is to import a generic JSON file that contains the result of a static analyzer tool that is not supported native.As described in the documentation it should be able to use JSON log files with the Warnings Plugin: [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#export-your-issues-into-a-supported-format]From the documentation I expect that the following file would be parsed without problems: [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/test/resources/io/jenkins/plugins/analysis/warnings/json-issues.log]Creating a Jenkinsfile with the following content:recordIssues( enabledForFailure: true, aggregatingResults: true, tools: [warningsPlugin()] )Using this into the Jenkinsfile results in the following output:Could not instantiate \ {enabledForFailure=true, aggregatingResults=true, tools=[@warningsPlugin()]} for io.jenkins.plugins.analysis.core.steps.RecordIssuesStep: java.lang.UnsupportedOperationException: no known implementation of class io.jenkins.plugins.analysis.core.model.Tool is using symbol 'warningsPlugin'So the bug is that I am enable unable to parse native JSON files as described in the documentation.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60238) Warnings plugin "export your issues into a supported format" not useable
Title: Message Title
Jelle van Geel created an issue
Jenkins / JENKINS-60238
Warnings plugin "export your issues into a supported format" not useable
Issue Type:
Bug
Assignee:
Ulli Hafner
Attachments:
log.txt
Components:
warnings-ng-plugin
Created:
2019-11-21 10:53
Environment:
org.jenkins-ci.main:jenkins-war:2.204 Warnings Next Generation Plugin 7.2.0
Priority:
Minor
Reporter:
Jelle van Geel
My goal is to import a generic JSON file that contains the result of a static analyzer tool that is not supported native. As described in the documentation it should be able to use JSON log files with the Warnings Plugin: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#export-your-issues-into-a-supported-format From the documentation I expect that the following file would be parsed without problems: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/test/resources/io/jenkins/plugins/analysis/warnings/json-issues.log Creating a Jenkinsfile with the following content: recordIssues( enabledForFailure: true, aggregatingResults: true, tools: [warningsPlugin()] ) Using this into the Jenkinsfile results in the following output: Could not instantiate {enabledForFailure=true, aggregatingResults=true, tools=[@warningsPlugin()]} for io.jenkins.plugins.analysis.core.steps.RecordIssuesStep: java.lang.UnsupportedOperationException: no known implementation of class io.jenkins.plugins.analysis.core.model.Tool is using symbol 'warningsPlugin' So the bug is that I am enable to parse native JSON files as described in the documentation.
[JIRA] (JENKINS-6798) applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses
Title: Message Title Vincent Latombe updated JENKINS-6798 Jenkins / JENKINS-6798 applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136893.1276972785000.4893.1574333220430%40Atlassian.JIRA.
[JIRA] (JENKINS-6798) applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses
Title: Message Title
Vincent Latombe updated an issue
Jenkins / JENKINS-6798
applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses
Change By:
Vincent Latombe
When Jenkins is set up behind a reverse proxy (such as IIS, nginx, etc.), when restarting, the page reloads too early.This seems to boil down to the proxy HTTP error, 502, not being considered by {{ applySafeRedirector() }} in {{ hudson-behavior.js }} and {{loading . js}}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136893.1276972785000.4884.1574332991647%40Atlassian.JIRA.
[JIRA] (JENKINS-6798) applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses
Title: Message Title Vincent Latombe started work on JENKINS-6798 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136893.1276972785000.4887.1574332992550%40Atlassian.JIRA.
[JIRA] (JENKINS-6798) applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-6798 applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses Change By: Vincent Latombe I've When Jenkins is set up Hudson to run as behind a service and be available through the IIS web server using its reverse proxy extension; everything works great apart from (such as IIS, nginx, etc.), when restarting - it reloads , the page way reloads too early.This seems to boil down to the proxy HTTP error, 502, not being considered by applySafeRedirector() in hudson-behavior.js. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136893.1276972785000.4875.157433
[JIRA] (JENKINS-6798) applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses
Title: Message Title Vincent Latombe commented on JENKINS-6798 Re: applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses Also affects the new loading.js for the login screen. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136893.1276972785000.4869.1574332920513%40Atlassian.JIRA.
[JIRA] (JENKINS-48315) Add env variable LAST_STAGE_NAME which will persist when stage ends prematurely
Title: Message Title Hokwang Lee commented on JENKINS-48315 Re: Add env variable LAST_STAGE_NAME which will persist when stage ends prematurely when unstable result (fail or abort, etc), I should send email about which commit, which job, which status, which stage. only thing I can not know for now is stage. Andrew Bayer Please consider this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186904.1512040368000.4857.1574332620400%40Atlassian.JIRA.
[JIRA] (JENKINS-6798) applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-6798 applySafeRedirector (e.g. on Hudson restarting page) reloads on 502 responses Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136893.1276972785000.4852.1574330700716%40Atlassian.JIRA.
[JIRA] (JENKINS-60237) How can I check none value for credentials parameter in pipeline?
Title: Message Title
Ariel Man created an issue
Jenkins / JENKINS-60237
How can I check none value for credentials parameter in pipeline?
Issue Type:
Bug
Assignee:
Unassigned
Components:
credentials-binding-plugin
Created:
2019-11-21 09:40
Priority:
Critical
Reporter:
Ariel Man
I saw many threads on empty fields, but how does it work with credentials parameter where the field is none? currently, when it's NONE, it fails with this error: org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: ${GPG_PASSPHRASE}
Add Comment
