[JIRA] (JENKINS-55912) Forbidden OPTIONS request method for "input" step
Title: Message Title Dmitry Markelov updated an issue Jenkins / JENKINS-55912 Forbidden OPTIONS request method for "input" step Change By: Dmitry Markelov When I push any buttons button "Proceed" or "Abort" (picture 1). My browser send OPTIONS request, you can view in attachments.And after that I get 403 status code, but if I send POST request directly to same url - all is good and work.I have all privileges in my 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-55911) java lint warning about annotation processor is not recognized
Title: Message Title Piotrek Zygielo commented on JENKINS-55911 Re: java lint warning about annotation processor is not recognized Just to make it complete of all I know. My latest finding is: This warning is produced by javac, but it is not from compiler, but rather from annotation processor. Thus turning off a. processing (-proc:none) - if one does not need it - frees console from this message. I didn't find separate analysisTool for [non-existing today] apt (which functionality I guess was merged into javac in 1.8, and apt itself was removed from JDK). Maybe new tool could be created, to parse annotation processing results? Just idea. 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-55912) Forbidden OPTIONS request method for "input" step
Title: Message Title Dmitry Markelov updated an issue Jenkins / JENKINS-55912 Forbidden OPTIONS request method for "input" step Change By: Dmitry Markelov When I push any buttons "Proceed" or "Abort" (picture 1). My browser send OPTIONS request, how you can view in attachments.And after that I get 403 status code, but if I send POST request directly to same url - all is good and work.I have all privileges in my 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-55925) Building a job with CLI fails - CLI parameter not supported for PasswordParameterDefinition
Title: Message Title justanothercoder justanothercoder created an issue Jenkins / JENKINS-55925 Building a job with CLI fails - CLI parameter not supported for PasswordParameterDefinition Issue Type: Bug Assignee: Unassigned Components: cli Created: 2019-02-02 03:30 Priority: Minor Reporter: justanothercoder justanothercoder While running a job through CLI which has a non-stored password parameter - it failed with following error: ERROR: CLI parameter submission is not supported for the class com.michelin.cio.hudson.plugins.passwordparam.PasswordParameterDefinition type. Please file a bug report for this Add Comment
[JIRA] (JENKINS-55924) Require Autologin for Swarm client to launch for UI as well as non-UI test cases
Title: Message Title shailesh mitkari created an issue Jenkins / JENKINS-55924 Require Autologin for Swarm client to launch for UI as well as non-UI test cases Issue Type: Bug Assignee: Unassigned Components: jenkins-testswarm, swarm-plugin Created: 2019-02-02 03:29 Priority: Minor Reporter: shailesh mitkari We are facing issue running UI as well as non-UI test cases using Jenkins Swarm Client.This swarm client is launched by master remotely using psExec. Initially we thought only UI test cases require auto-login to make desktop available and we ran those test cases and the solution worked for us. But now we are facing issue with non-UI test cases as well. So the question is do we need auto-login or desktop available for non-UI test cases as well? or do we need any extra settings for it to run? Is this related to some registry accessing problem as we are not logged in? Add Comment
[JIRA] (JENKINS-55909) Build Log substring
Title: Message Title David van Laatum closed an issue as Not A Defect This is a bug tracker not a support channel. Ask your question on the mailing list or stack overflow Jenkins / JENKINS-55909 Build Log substring Change By: David van Laatum 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-55923) CpsFlowExecution writes to logs after compression
Title: Message Title Steven Williams updated an issue Jenkins / JENKINS-55923 CpsFlowExecution writes to logs after compression Change By: Steven Williams We've encountered occasional hung threads living far longer than their jobs, causing system instability. Root cause is that after build logs are compressed, an additional line is appended, 'Creating placeholder flownodes because failed loading originals.', which corrupts the gz archive. If we remove the appended line, the log could can be extracted.The workaround is to move the build folder on the master, kill any remaining threads, and often we must reboot the master. This has happened multiple times so far, and we've setup thread duration monitoring jobs to detect threads & builds over X ms. Advice on additional ways of capturing relevant log information would be appreciated.The only place I've found the offending line is: [https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L640]Closest existing issue was: https://issues.jenkins-ci.org/browse/JENKINS-50199?jql=text%20~%20%22Creating%20placeholder%20flownodes%20because%20failed%20loading%20originals.%22 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
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Vivek Pandey commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Nelson Wolf On running Jenkins, it might. Well, you have to disable the cache anyways, that needs setting this jvm property -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55923) CpsFlowExecution writes to logs after compression
Title: Message Title Steven Williams updated an issue Jenkins / JENKINS-55923 CpsFlowExecution writes to logs after compression Change By: Steven Williams We've encountered occasional hung threads living far longer than their jobs, causing system instability. Root cause is that after build logs are compressed, and an additional line is appended, 'Creating placeholder flownodes because failed loading originals.', which corrupts the gz archive. If we remove the appended line, the log could be extracted.The workaround is to move the build folder on the master, kill any remaining threads, and often we must reboot the master. This has happened multiple times so far, and we've setup thread duration monitoring jobs to detect threads & builds over X ms. Advice on additional ways of capturing relevant log information would be appreciated.The only place I've found the offending line is:[https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L640]Closest existing issue was: https://issues.jenkins-ci.org/browse/JENKINS-50199?jql=text%20~%20%22Creating%20placeholder%20flownodes%20because%20failed%20loading%20originals.%22 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
[JIRA] (JENKINS-55923) CpsFlowExecution writes to logs after compression
Title: Message Title Steven Williams created an issue Jenkins / JENKINS-55923 CpsFlowExecution writes to logs after compression Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-02-01 22:31 Environment: Will edit with additional details once authorized to disclose. Jenkins: 2.121.1 Pipeline 2.5 Priority: Critical Reporter: Steven Williams We've encountered occasional hung threads living far longer than their jobs, causing system instability. Root cause is that after build logs are compressed, and additional line is appended, 'Creating placeholder flownodes because failed loading originals.', which corrupts the gz archive. If we remove the appended line, the log could be extracted. The workaround is to move the build folder on the master, kill any remaining threads, and often we must reboot the master. This has happened multiple times so far, and we've setup thread duration monitoring jobs to detect threads & builds over X ms. Advice on additional ways of capturing relevant log information would be appreciated. The only place I've found the offending line is: https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L640 Closest existing issue was: https://issues.jenkins-ci.org/browse/JENKINS-50199?jql=text%20~%20%22Creating%20placeholder%20flownodes%20because%20failed%20loading%20originals.%22
[JIRA] (JENKINS-51170) Workflowstep-specific environment variables
Title: Message Title Devin Nusbaum updated JENKINS-51170 This extension point is now available as of Pipeline Step API 2.19, Pipeline Supporting APIs 3.2, and Pipeline Groovy 2.63. Jenkins / JENKINS-51170 Workflowstep-specific environment variables Change By: Devin Nusbaum Status: In Review Resolved Assignee: Sam Van Oort Thomas Weißschuh Resolution: Fixed Released As: workflow-step-api 2.19, workflow-support 3.2, workflow-cps 2.63 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Devin Nusbaum resolved as Fixed A fix for this issue was released in version 2.63 of Pipeline Groovy Plugin. Jenkins / JENKINS-52189 GraphListener does not receive FlowStartNode Change By: Devin Nusbaum Status: In Progress Resolved Resolution: Fixed Released As: workflow-cps 2.63 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-55922) Rebuild Last- password visible in browser Inspect
Title: Message Title Tim Slaton created an issue Jenkins / JENKINS-55922 Rebuild Last- password visible in browser Inspect Issue Type: Bug Assignee: ragesh_nair Attachments: visible_password.PNG Components: rebuild-plugin Created: 2019-02-01 21:54 Environment: Jenkins ver. 2.138.1; Rebuilder v1.29 Labels: security Priority: Major Reporter: Tim Slaton When using Rebuild Last on a job with "Remember Password Enabled" turned on in Jenkins config, the password is shown in plain-text when inspecting the page in a browser (see attached screenshot). The value should not be displayed. Add Comment
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title Jim Tilander commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time I believe I'm still running into this bug as of today with Jenkins 2.161 and git plugin 3.9.3. Any progress on this issue or is it effectively dead? This pretty much makes culprit emails not work in a PR workflow, and you are forced to email a well known email group instead which is less than ideal. Or have I missed some development? 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-55921) When SCM polling fails, the result is logged as "no changes"
Title: Message Title José Lamas created an issue Jenkins / JENKINS-55921 When SCM polling fails, the result is logged as "no changes" Issue Type: Improvement Assignee: José Lamas Components: genexus-plugin Created: 2019-02-01 21:14 Priority: Minor Reporter: José Lamas This was reported in BuildAndDeploy forum https://groups.google.com/a/genexus.com/forum/#!msg/buildanddeploy/mFdIsnRLQKE/MJjUrFD8AQAJ There's also a similar issue about git-client-plugin at https://issues.jenkins-ci.org/browse/JENKINS-32712 When a project uses SCM polling, if the polling fails (eg: bad credentials) although the plugin throws an exception, the engine takes that as "no changes", the build is not triggered and it's hard to note the problem. Add Comment
[JIRA] (JENKINS-55911) java lint warning about annotation processor is not recognized
Title: Message Title Ulli Hafner commented on JENKINS-55911 Re: java lint warning about annotation processor is not recognized When this option is part of javac then it is better suited for the javac parser. I think I need to add some tweaks to the regexp so it gets picked up as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55920) CasC compatibility with GitHub Plugin
Title: Message Title Oleg Nenashev started work on JENKINS-55920 Change By: Oleg Nenashev 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-55920) CasC compatibility with GitHub Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55920 CasC compatibility with GitHub Plugin Change By: Oleg Nenashev Labels: jcasc-compatibility 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-55920) CasC compatibility with GitHub Plugin
Title: Message Title Oleg Nenashev updated JENKINS-55920 Jenkins / JENKINS-55920 CasC compatibility with GitHub Plugin Change By: Oleg Nenashev 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-55920) CasC compatibility with GitHub Plugin
Title: Message Title Daniel Garzon created an issue Jenkins / JENKINS-55920 CasC compatibility with GitHub Plugin Issue Type: Improvement Assignee: Daniel Garzon Components: github-plugin Created: 2019-02-01 19:38 Priority: Major Reporter: Daniel Garzon As mentioned here: https://github.com/jenkinsci/configuration-as-code-plugin/issues/672, it is currently impossible to override the `hookUrl` through CasC. This PR fixes the issue: https://github.com/jenkinsci/github-plugin/pull/205 Add Comment
[JIRA] (JENKINS-55914) archived artifacts cannot be navigated to in subfolders
Title: Message Title Alexej Pissarev updated an issue Jenkins / JENKINS-55914 archived artifacts cannot be navigated to in subfolders Change By: Alexej Pissarev Summary: archived artifacts cannot be downloaded from navigated to in subfolders 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-55453) Github PR creating job but not building
Title: Message Title Kirill Merkushev commented on JENKINS-55453 Re: Github PR creating job but not building github plugin itself does nothing with PR webhooks, so it can be something wrong with other plugins. In case you use pipeline - thats full responsibility of Github Branch Source plugin 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-55919) Cannot install Pipeline / workflow-cps-global-lib plugin 2.13
Title: Message Title Peter LaValle created an issue Jenkins / JENKINS-55919 Cannot install Pipeline / workflow-cps-global-lib plugin 2.13 Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2019-02-01 19:32 Priority: Major Reporter: Peter LaValle Looks like a repeat of https://issues.jenkins-ci.org/browse/JENKINS-49123 workflow-cps-global-lib 2.13 is not available [http://archives.jenkins-ci.org/plugins/workflow-cps-global-lib/2.13/workflow-cps-global-lib.hpi I'm using |http://archives.jenkins-ci.org/plugins/workflow-cps-global-lib/2.13/workflow-cps-global-lib.hpi] Jenkins ver. 2.150.2 Add Comment
[JIRA] (JENKINS-55919) Cannot install Pipeline / workflow-cps-global-lib plugin 2.13
Title: Message Title Peter LaValle updated an issue Jenkins / JENKINS-55919 Cannot install Pipeline / workflow-cps-global-lib plugin 2.13 Change By: Peter LaValle Looks like a repeat of https://issues.jenkins-ci.org/browse/JENKINS-49123workflow-cps-global-lib 2.13 is not available [http://archives.jenkins-ci.org/plugins/workflow-cps-global-lib/2.13/workflow-cps-global-lib.hpiI'm using |http://archives.jenkins-ci.org/plugins/workflow-cps-global-lib/2.13/workflow-cps-global-lib.hpi] [Jenkins ver. 2.150.2|https://jenkins.io/] 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Oleg Nenashev Thank you. I will just look into it. And any suggestions in 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-55916) Performance: Rewriting RoleMap#RoleWalker such that it includes a breaking(aborting) logic, reducing the execution time in many cases and avoid creation of new collection for ro
Title: Message Title Deepansh Nagaria commented on JENKINS-55916 Re: Performance: Rewriting RoleMap#RoleWalker such that it includes a breaking(aborting) logic, reducing the execution time in many cases and avoid creation of new collection for roles every time RoleWalker is invoked, reducing the memory usage. I propose a fairly simple approach of both the problems listed: A class variable abort which when set to true terminates the loop and making the collection roles as global variable of outer class solves the issue of it being created on every call of walk(). https://github.com/jenkinsci/role-strategy-plugin/pull/56 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-55918) Add support for groovy sandbox mode in environmentVariables closure
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-55918
Add support for groovy sandbox mode in environmentVariables closure
Change By:
Alexander Komarov
The "*Prepare an Environment for the run*" (environmentVariables {}) section supports a "sandbox" mode for the Groovy Script. It would be useful for the DSL plugin to allow for setting the value of this checkbox.*Use case*: I generate a slightly different version of the same job every few months. The Groovy Script changes slightly, which makes Jenkins require in-process script approval and prevents the job from running. With sandbox mode, this would not happen. (Also, it would potentially be more secure) I'll try to submit a PR : https://github . com/jenkinsci/job-dsl-plugin/pull/1165
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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Oleg Nenashev commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Nisarg Shah https://github.com/jenkinsci/jenkins/blob/master/CONTRIBUTING.md#building-and-debugging 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-55915) Invalid refspec
Title: Message Title Kevin Johnsrud commented on JENKINS-55915 Re: Invalid refspec Sort of, I actually now think this is an issue with the multiple SCMs plugin that I'm using. It's auto-populating some advanced settings and/or reading config information. When I remove that it works fine. As soon as I add it back, even with correct settings it throws the same stack trace. I know this plugin in deprecated so I guess it's time to move to pipelines for some of these simple projects to support multiple SCMs. 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-55915) Invalid refspec
Title: Message Title Kevin Johnsrud commented on JENKINS-55915 Re: Invalid refspec Sort of, I actually now think this is an issue with the multiple SCMs plugin that I'm using. It's auto-populating some advanced settings and/or reading config information. When I remove that it works fine. As soon as I add it back, even with correct settings it throws the same stack trace. I know this plugin in deprecated so I guess it's time to move to pipelines for some of these simple projects to support multiple SCMs. 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Can you please provide me some guidance on how to compile and run this code on local and do these tests. As in test, error of "Restricted" is shown. So I can just check it on my local. And do you think that changes done(new getter method) are perfect or I need to work on that? 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-55101) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Gavin Mogan commented on JENKINS-55101 Re: Create official Java 11 Docker Packaging for BlueOcean I also like the idea of retiring the image. We have a lot of people show up in gitter blueocean channel asking about general pipeline issues. I think the docker image was great before blueocean made it cleanly into the update store, but its pretty stable these days, and can easily just get installed. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I just checked both of those builds and they both failed for this same reason. 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-55911) java lint warning about annotation processor is not recognized
Title: Message Title
Piotrek Zygielo edited a comment on JENKINS-55911
Re: java lint warning about annotation processor is not recognized
{quote}I see, the format is totally different{quote} Right, sadly it is. But it is emitted by javac, and only with `-Xlint` option used. The result from command line call: {code :java }$ javac -Xlint -Xlint:-processing -cp ../glassfish-embedded-all-5.1.0.jar:../jakarta.ejb-api-3.2.5.jar:../api.jar src/main/java/.../XXX.java warning: Supported source version 'RELEASE_7' from annotation processor 'org.netbeans.modules.schema2beansdev.Schema2BeansProcessor' less than -source '1.8'{code}Also - I could not find any way of explicitly disabling this check/warning, and have other still enabled. (After all the end result is as I want - it is effectively ignored...)It seems this warning was not fully _linted_/integrated to -Xlint option ([https://bugs.java.com/bugdatabase/view_bug.do?bug_id=7184902] and others).{quote}Shouldn’t it make more sense if such warnings will be rather catched by the maven parser only?{quote}I reported this, with expectation that {{e.h.h.a.p.JavacParser}} was supposed to catch it. My assumption could be wrong, or for any other reason it could be not feasible to add it to {{JavacParser}}.Unfortunately, with two tools configured (Java, Maven) or Maven alone - in *Maven Warnings* report, some other warnings are correctly collected, but not this one - it is not present at all.For example, from console {noformat}[INFO] --- buildnumber-maven-plugin:1.4:create (default) @ integration-tests ---[INFO] ShortRevision tag detected. The value is '8'.[INFO] Executing: /bin/sh -c cd '.../integration-tests' && 'git' 'rev-parse' '--verify' '--short=8' 'HEAD'[INFO] Working directory: .../integration-tests[INFO] Storing buildNumber: 20190201.183514-r369adafc at timestamp: 1549042514164[WARNING] Cannot get the branch information from the git repository: Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref[INFO] ShortRevision tag detected. The value is '8'.[INFO] Executing: /bin/sh -c cd '.../integration-tests' && 'git' 'rev-parse' '--verify' '--short=8' 'HEAD'[INFO] Working directory: .../integration-tests[INFO] Storing buildScmBranch: UNKNOWN[INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ integration-tests ---[INFO] Using 'UTF-8' encoding to copy filtered resources.[INFO] skip non existing resourceDirectory .../integration-tests/src/main/resources[INFO] [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ integration-tests ---[INFO] Changes detected - recompiling the module![INFO] Compiling 5 source files to .../target/classes[WARNING] Supported source version 'RELEASE_7' from annotation processor 'org.netbeans.modules.schema2beansdev.Schema2BeansProcessor' less than -source '1.8'[INFO] {noformat} the 1st warn (_Cannot get the branch..._) is present, and the 2nd (_Supported source..._) is not. Probably due to [https://github.com/jenkinsci/analysis-model/blob/0e953832b82e0f8d611b84a30146cbb00b9f0ea7/src/main/java/edu/hm/hafner/analysis/parser/MavenConsoleParser.java#L73]?
[JIRA] (JENKINS-55911) java lint warning about annotation processor is not recognized
Title: Message Title Piotrek Zygielo commented on JENKINS-55911 Re: java lint warning about annotation processor is not recognized I see, the format is totally different Right, sadly it is. But it is emitted by javac, and only with `-Xlint` option used. The result from command line call: $ javac -Xlint -Xlint:-processing -cp ../glassfish-embedded-all-5.1.0.jar:../jakarta.ejb-api-3.2.5.jar:../api.jar src/main/java/.../XXX.java warning: Supported source version 'RELEASE_7' from annotation processor 'org.netbeans.modules.schema2beansdev.Schema2BeansProcessor' less than -source '1.8' Also - I could not find any way of explicitly disabling this check/warning, and have other still enabled. (After all the end result is as I want - it is effectively ignored...) It seems this warning was not fully linted/integrated to -Xlint option (https://bugs.java.com/bugdatabase/view_bug.do?bug_id=7184902 and others). Shouldn’t it make more sense if such warnings will be rather catched by the maven parser only? I reported this, with expectation that e.h.h.a.p.JavacParser was supposed to catch it. My assumption could be wrong, or for any other reason it could be not feasible to add it to JavacParser. Unfortunately, with two tools configured (Java, Maven) or Maven alone - in Maven Warnings report, some other warnings are correctly collected, but not this one - it is not present at all. For example, from console [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ integration-tests --- [INFO] ShortRevision tag detected. The value is '8'. [INFO] Executing: /bin/sh -c cd '.../integration-tests' && 'git' 'rev-parse' '--verify' '--short=8' 'HEAD' [INFO] Working directory: .../integration-tests [INFO] Storing buildNumber: 20190201.183514-r369adafc at timestamp: 1549042514164 [WARNING] Cannot get the branch information from the git repository: Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref [INFO] ShortRevision tag detected. The value is '8'. [INFO] Executing: /bin/sh -c cd '.../integration-tests' && 'git' 'rev-parse' '--verify' '--short=8' 'HEAD' [INFO] Working directory: .../integration-tests [INFO] Storing buildScmBranch: UNKNOWN [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ integration-tests --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory .../integration-tests/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ integration-tests --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 5 source files to .../target/classes [WARNING] Supported source version 'RELEASE_7' from annotation processor 'org.netbeans.modules.schema2beansdev.Schema2BeansProcessor' less than -source '1.8' [INFO]
[JIRA] (JENKINS-43563) Git plugin does not set user in pipeline
Title: Message Title Mark Waite commented on JENKINS-43563 Re: Git plugin does not set user in pipeline Michael D I'm happy to receive a pull request with automated tests that show the problem and a code change that fixes the tests. Thanks for your interest in helping the Jenkins 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-55915) Invalid refspec
Title: Message Title Mark Waite commented on JENKINS-55915 Re: Invalid refspec The text in the stack trace is accurate, though not as helpful as it should be. Somewhere in your job definition (likely in the "Advanced" section of the repository definition) there is an invalid refspec. The help for the refspec field provides examples of valid refspecs, as does the command line git documentation. I'm leaving this bug report open because a stack trace from a user typed configuration error is ugly and should be replaced by much better message to the user. You can resolve the problem by using a valid refspec, but the user interface needs improvement so that others don't encounter the same problem. Thanks for the bug report. Reply with a comment if correcting the refspec is able to resolve the problem (or not). 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-55915) Invalid refspec
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-55915 Invalid refspec Change By: Mark Waite Assignee: Mark Waite 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Carlos Sanchez commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN what was the agent name of the build that failed? app-ui-build-common-b0b6518b-d72a-4826-a165-719aca99e295--9cgzg or app-ui-build-common-6bc9afa4-13cf-43a6-af59-338a80dda163--9h6d6 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-22328) ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1
Title: Message Title Heiko Böttger commented on JENKINS-22328 Re: ubuntu switch to jenkins debian distribution fails because: subprocess installed post-installation script returned error exit status 1 I am still facing this issue when adding variables myself. It seems like the script is executed by a different shell. I had several lines with "JAVA_ARGS+=" which did work when starting jenkins manually but not during update. Adding a shebang doesn't seem, may be the script is sourced or explicitly processed by a different interpreter. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I'm still not completely sure how to get the exact logs you want, but I ran into this issue again yesterday and grabbed all the logs that were available at the time. They are attached. If you need something else, please provide more instructions. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous updated an issue Jenkins / JENKINS-55392 java.util.concurrent.RejectedExecutionException AGAIN Change By: Daniel Watrous Attachment: connection-error-log.txt 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-43563) Git plugin does not set user in pipeline
Title: Message Title Daniel Beck commented on JENKINS-43563 Re: Git plugin does not set user in pipeline The documentation It's sourced from a wiki page linked in the sidebar, everyone with an account can edit it. Users frequently contribute to that, and the changes are of varying quality. I'm sure Mark would appreciate your help in improving the quality of the documentation. 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-43563) Git plugin does not set user in pipeline
Title: Message Title Michael D commented on JENKINS-43563 Re: Git plugin does not set user in pipeline Sorry this is not acceptable. The documentation in https://plugins.jenkins.io/git clearly states that the plugin will do the user and email configuration. Do you know how much hours developers waste to find out that something that should work out of the box needs workarounds? We have pipelines with more then 10 git checkouts where updates get pushed, so the pipeline scripts gets totally ugly. 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-55101) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev commented on JENKINS-55101 Re: Create official Java 11 Docker Packaging for BlueOcean As commented in WEBSITE-474, I agree with deprecating the image. JENKINS-52069 is also a good justification for not advertising it 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-55794) Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN
Title: Message Title Liora Milbaum commented on JENKINS-55794 Re: Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN the plugin is build with the spring rabbitmq version 2.0.2. There is a newer one if I am not mistaken. 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-55794) Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN
Title: Message Title Liora Milbaum edited a comment on JENKINS-55794 Re: Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN the plugin is build built with the spring rabbitmq version 2.0.2. There is a newer one if I am not mistaken. 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-55890) RocketChat notification (using proxy) fails since version 1.3.1
Title: Message Title Martin Reinhardt resolved as Fixed FIxed in Version 1.4.2 Jenkins / JENKINS-55890 RocketChat notification (using proxy) fails since version 1.3.1 Change By: Martin Reinhardt Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55911) java lint warning about annotation processor is not recognized
Title: Message Title Ulli Hafner commented on JENKINS-55911 Re: java lint warning about annotation processor is not recognized I see, the format is totally different. Shouldn’t it make more sense if such warnings will be rather catched by the maven parser only? 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-55226) Deadlock while running tests
Title: Message Title Adrien Lecharpentier commented on JENKINS-55226 Re: Deadlock while running tests Alex Earl I tried to work a bit on this. It's not a deadlock and it's not only related to java 11. It is a test environment issue. If you update jenkins.version to 2.60.1, the Pipeline related tests simply timeout. You could check that by updating Jenkinsfile with buildPlugin( configurations: [ [ platform: "linux" ], [ platform: "windows" ], [ platform: "linux", jdk: "8", jenkins: "2.60.1", javaLevel: "8" ], [ platform: "windows", jdk: "8", jenkins: "2.60.1", javaLevel: "8" ] ] ) (or similar, just test with a newer version of Jenkins core) The tests are supposed to trigger a job and see the result of run. The run is triggered but it doesn't go any further: nothing is truly executed and the tests timeout. 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-55101) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Baptiste Mathus commented on JENKINS-55101 Re: Create official Java 11 Docker Packaging for BlueOcean I think actually in the future, we can keep using Docker Hub, but on the new experimental Jenkins org there, cf. JEP-217 by Oleg. Because on this new home, people know already by design of the naming that things can be changed, breaking, etc. per its very experimental nature. 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-35237) Make "Build was started by" list expandable, because it is sometimes much too long
Title: Message Title Oleg Nenashev stopped work on JENKINS-35237 Change By: Oleg Nenashev 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-35237) Make "Build was started by" list expandable, because it is sometimes much too long
Title: Message Title Oleg Nenashev updated JENKINS-35237 Jenkins / JENKINS-35237 Make "Build was started by" list expandable, because it is sometimes much too long Change By: Oleg Nenashev Status: In Review 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-55101) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Jesse Glick commented on JENKINS-55101 Re: Create official Java 11 Docker Packaging for BlueOcean Agreed. We should not have separate official images which merely preinstall some arbitrary plugin selection. (A number of plugins build demo images showing the plugin being used in context on a sample project, which can be quite useful. Historically these have been uploaded to DockerHub, though I tend to regret this—in many cases you need special instructions to run the demo anyway, so it would be better to have people check out sources and make -C demo run.) 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-35237) Make "Build was started by" list expandable, because it is sometimes much too long
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35237 Make "Build was started by" list expandable, because it is sometimes much too long Change By: Oleg Nenashev Labels: stalled-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-55918) Add support for groovy sandbox mode in environmentVariables closure
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-55918
Add support for groovy sandbox mode in environmentVariables closure
Change By:
Alexander Komarov
The "*Prepare an Environment for the run*" (environmentVariables {}) section supports a "sandbox" mode for the Groovy Script. It would be useful for the DSL plugin to allow for setting the value of this checkbox.*Use case*: I generate a slightly different version of the same job every few months. The Groovy Script changes slightly, which makes Jenkins require in-process script approval and prevents the job from running. With sandbox mode, this would not happen. (Also, it would potentially be more secure) I'll try to submit a 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-55918) Add support for groovy sandbox mode in environmentVariables closure
Title: Message Title
Alexander Komarov created an issue
Jenkins / JENKINS-55918
Add support for groovy sandbox mode in environmentVariables closure
Issue Type:
Improvement
Assignee:
Daniel Spilker
Attachments:
Screenshot_2019-02-01_11-08-13.png, Screenshot_2019-02-01_11-12-05.png
Components:
job-dsl-plugin
Created:
2019-02-01 16:13
Labels:
plugin
Priority:
Minor
Reporter:
Alexander Komarov
The "Prepare an Environment for the run" (environmentVariables {}) section supports a "sandbox" mode for the Groovy Script. It would be useful for the DSL plugin to allow for setting the value of this checkbox. Use case: I generate a slightly different version of the same job every few months. The Groovy Script changes slightly, which makes Jenkins require in-process script approval and prevents the job from running. With sandbox mode, this would not happen. I'll try to submit a PR.
[JIRA] (JENKINS-55911) java lint warning about annotation processor is not recognized
Title: Message Title Piotrek Zygielo commented on JENKINS-55911 Re: java lint warning about annotation processor is not recognized Which parser? Java: "warnings-ng@2.1.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-55917) Syntax differs from "sh" call regarding shebang
Title: Message Title Zach LaCelle created an issue Jenkins / JENKINS-55917 Syntax differs from "sh" call regarding shebang Issue Type: Bug Assignee: Vicky Chijwani Components: labelled-steps-plugin Created: 2019-02-01 16:04 Environment: jenkinsci/blueocean labelled-pipeline-steps 1.0 Priority: Major Reporter: Zach LaCelle When using the labelledSteps plugin, I have part of my script which takes advantage of bash. In the unlabelled "sh" commands, I could do the following: sh ''' #!/bin/bash set -o pipefail ''' With labelledShell, this type of shebang notation doesn't work: labelledShell label: 'my bash', script: """ #!/bin/bash set -o pipefail """ Add Comment
[JIRA] (JENKINS-55916) Performance: Rewriting RoleMap#RoleWalker such that it includes a breaking(aborting) logic, reducing the execution time in many cases and avoid creation of new collection for ro
Title: Message Title Deepansh Nagaria created an issue Jenkins / JENKINS-55916 Performance: Rewriting RoleMap#RoleWalker such that it includes a breaking(aborting) logic, reducing the execution time in many cases and avoid creation of new collection for roles every time RoleWalker is invoked, reducing the memory usage. Issue Type: Improvement Assignee: Deepansh Nagaria Components: role-strategy-plugin Created: 2019-02-01 15:56 Priority: Minor Reporter: Deepansh Nagaria Current implementation of RoleMap does not have logic to abort or break the flow after a particular role, if there were such feature, running time can be reduced in a number of cases. Further every time RoleWalker is called, it invokes walk() which creates a new collection of roles every time, it can be avoided. Add Comment
[JIRA] (JENKINS-55911) java lint warning about annotation processor is not recognized
Title: Message Title Ulli Hafner commented on JENKINS-55911 Re: java lint warning about annotation processor is not recognized Which parser? 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-55915) Invalid refspec
Title: Message Title Kevin Johnsrud created an issue Jenkins / JENKINS-55915 Invalid refspec Issue Type: Bug Assignee: Mark Waite Attachments: System Information [Jenkins].pdf Components: git-plugin Created: 2019-02-01 15:54 Environment: Dockerized Jenkins 2.150.2 (pulled from docker repo) Browser: Chrome (mac) Version 72.0.3626.81 (see attached systeminfo) Priority: Minor Reporter: Kevin Johnsrud Just recently started seeing this when I attempt to edit projects. This thing is when I go into edit the configuration the git portion updates itself automatically briefly displaying some red text and then resetting one of my git entries in my project. I've tried clearing the wildcards in my entries and saving but it still won't apply and gives the same stack trace every time. I verified I was running the latest plugins and LTS version to make sure it wasn't a bug in older software. When I set everything back to how it was and hit save or if I just hit apply with making no changes I get this exception error. I tried reverting to an older build version in case some change made to the entry caused this but it continues to occur even if I revert to an older version. A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant
[JIRA] (JENKINS-55914) archived artifacts cannot be downloaded from subfolders
Title: Message Title Alexej Pissarev updated an issue Jenkins / JENKINS-55914 archived artifacts cannot be downloaded from subfolders Change By: Alexej Pissarev Attachment: Build Artifact page.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-55914) archived artifacts cannot be downloaded from subfolders
Title: Message Title Alexej Pissarev updated an issue Jenkins / JENKINS-55914 archived artifacts cannot be downloaded from subfolders Change By: Alexej Pissarev Attachment: folder link.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-55914) archived artifacts cannot be downloaded from subfolders
Title: Message Title
Alexej Pissarev updated an issue
Jenkins / JENKINS-55914
archived artifacts cannot be downloaded from subfolders
Change By:
Alexej Pissarev
If some of archived artifacts are located in subfolders they cannot be navigated to in the "Build Artifacts" view: the web browser gets a timeout.Steps to reproduce:1. create artifacts, some of them in subfolders. e.g.:sh "mkdir subdir" sh "echo 'bla' > file.txt" sh "echo 'bla' > subdir/file_in_folder.txt"2. archive artifacts, e.g.:archiveArtifacts '** ** /* * .*'3. navigate to the "Build Artifacts" page, e.g. /job/test/4/artifact/4. click on the link "subdir"Webbrowser is trying to connect and runs to a timeout.I guess the is a missing "/" in the link of "subdir":is: "/job/test/4/artifact/subdir"woud work: "/job/test/4/artifact/subdir{color:#de350b}/"{color}
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-55914) archived artifacts cannot be downloaded from subfolders
Title: Message Title
Alexej Pissarev updated an issue
Jenkins / JENKINS-55914
archived artifacts cannot be downloaded from subfolders
Change By:
Alexej Pissarev
If some of archived artifacts are located in subfolders they cannot be navigated to in the "Build Artifacts" view: the web browser gets a timeout.Steps to reproduce:1. create artifacts, some of them in subfolders. e.g.:sh "mkdir subdir" sh "echo 'bla' > file.txt" sh "echo 'bla' > subdir/file_in_folder.txt"2. archive artifacts, e.g.:archiveArtifacts ' \ * \ * ** / \ * * . \ *'3. navigate to the "Build Artifacts" page, e.g. /job/test/4/artifact/4. click on the link "subdir"Webbrowser is trying to connect and runs to a timeout.I guess the is a missing "/" in the link of "subdir":is: "/job/test/4/artifact/subdir"woud work: "/job/test/4/artifact/subdir{color:#de350b}/"{color}
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-55914) archived artifacts cannot be downloaded from subfolders
Title: Message Title
Alexej Pissarev updated an issue
Jenkins / JENKINS-55914
archived artifacts cannot be downloaded from subfolders
Change By:
Alexej Pissarev
If some of archived artifacts are located in subfolders they cannot be navigated to in the "Build Artifacts" view: the web browser gets a timeout.Steps to reproduce:1. create artifacts, some of them in subfolders. e.g.:sh "mkdir subdir" sh "echo 'bla' > file.txt" sh "echo 'bla' > subdir/file_in_folder.txt"2. archive artifacts, e.g.:archiveArtifacts '** * /* * .*'3. navigate to the "Build Artifacts" page, e.g. /job/test/4/artifact/4. click on the link "subdir"Webbrowser is trying to connect and runs to a timeout.I guess the is a missing "/" in the link of "subdir":is: "/job/test/4/artifact/subdir"woud work: "/job/test/4/artifact/subdir{color:#de350b}/"{color}
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-55914) archived artifacts cannot be downloaded from subfolders
Title: Message Title
Alexej Pissarev updated an issue
Jenkins / JENKINS-55914
archived artifacts cannot be downloaded from subfolders
Change By:
Alexej Pissarev
If some of archived artifacts are located in subfolders they cannot be navigated to in the "Build Artifacts" view: the web browser gets a timeout.Steps to reproduce:1. create artifacts, some of them in subfolders. e.g.:sh "mkdir subdir" sh "echo 'bla' > file.txt" sh "echo 'bla' > subdir/file_in_folder.txt"2. archive artifacts, e.g.:archiveArtifacts '** * /* * .*'3. navigate to the "Build Artifacts" page, e.g. /job/test/4/artifact/4. click on the link "subdir"Webbrowser is trying to connect and runs to a timeout.I guess the is a missing "/" in the link of "subdir":is: "/job/test/4/artifact/subdir"woud work: "/job/test/4/artifact/subdir{color:#de350b}/"{color}
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-55914) archived artifacts cannot be downloaded from subfolders
Title: Message Title Alexej Pissarev commented on JENKINS-55914 Re: archived artifacts cannot be downloaded from subfolders What works is download of all artifacts via "(all files in zip)": the created and downloaded zip archive contains all artifacts in their structure - with the subfolder "subdir" in this example. I checked the issue in an older jenkins instance (Jenkins ver. 2.152): the same behaviour. 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-40723) Built Dockerfile images are never removed
Title: Message Title Dwight Guth commented on JENKINS-40723 Re: Built Dockerfile images are never removed I definitely side with the people who think that this was resolved prematurely. We have been running docker image prune on our Jenkins node that we recently migrated to dockerfiles, and each time it ran it was freeing up less and less space. What we eventually realized is that because Jenkins is tagging every build with a tag corresponding to the hash of the dockerfile, when the dockerfile changes, it does not untag the old build (because the new tag is different from the old tag), so the old build is not marked as dangling, and you have to run the significantly more aggressive `docker image prune -a` to clean it up. I believe Jenkins should be tagging these builds with something that is deterministic across builds to the same job and branch, and deleting all the tags associated with change requests when the change request closes and the jenkins branch is deleted. 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-55914) archived artifacts cannot be downloaded from subfolders
Title: Message Title Alexej Pissarev created an issue Jenkins / JENKINS-55914 archived artifacts cannot be downloaded from subfolders Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-01 15:15 Environment: Jenkins ver. 2.161 Priority: Minor Reporter: Alexej Pissarev If some of archived artifacts are located in subfolders they cannot be navigated to in the "Build Artifacts" view: the web browser gets a timeout. Steps to reproduce: 1. create artifacts, some of them in subfolders. e.g.: sh "mkdir subdir" sh "echo 'bla' > file.txt" sh "echo 'bla' > subdir/file_in_folder.txt" 2. archive artifacts, e.g.: archiveArtifacts '*/.*' 3. navigate to the "Build Artifacts" page, e.g. /job/test/4/artifact/ 4. click on the link "subdir" Webbrowser is trying to connect and runs to a timeout. I guess the is a missing "/" in the link of "subdir": is: "/job/test/4/artifact/subdir" woud work: "/job/test/4/artifact/subdir/" Add Comment
[JIRA] (JENKINS-53393) Support for master-slave configuration
Title: Message Title José Lamas started work on JENKINS-53393 Change By: José Lamas 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-55913) Variable assignment in if condition is not working as expected
Title: Message Title
Hari Dara created an issue
Jenkins / JENKINS-55913
Variable assignment in if condition is not working as expected
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2019-02-01 15:06
Environment:
Jenkins 2.89.3 Pipeline 2.5
Priority:
Major
Reporter:
Hari Dara
The below code works as expected as a standalone Groovy script (the if condition doesn't enter and so script value remains the same:
def script = '''mvn -q -Dexec.executable=echo -Dexec.args=\\${project.version} --non-recursive exec:exec'''
def index
if ((index = script.indexOf('release:prepare')) != -1) {
script = script[0..' -DpushChanges=false ' + script[index..-1]
}
But the exact same code in a custom vars function misbehaves. The if condition enters anyway with an index value of -1 resulting in a script value of mvn -q -Dexec.executable=echo -Dexec.args=\${project.version} --non-recursive exec:ex -DpushChanges=false c If I pull the assignment out of the if condition, it works as expected:
def index = script.indexOf('release:prepare')
if (index != -1) {
[JIRA] (JENKINS-55101) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Baptiste Mathus commented on JENKINS-55101 Re: Create official Java 11 Docker Packaging for BlueOcean As I've expressed elsewhere, I tend to think this image should be discontinued. I would say the experimental one is actually enough. IMO, it's really not great that we're providing many variants of Jenkins images. I think the Jenkins Project already has enough work with providing quality-guaranteed and maintaining the jenkins/jenkins different tags/variants, to also have "plugins" specific images like jenkins/blueocean. So, as such, my recommendation would be to close this as WONTFIX. 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail commented on JENKINS-55896 Re: Jenkins is not triggering build on any pullrequest created in bitbucket repo Christian Del Monte I tried same your suggestion but it is not working. I am waiting from Bitbucket side if they answer because I am not receiving payload on pr but I am receiving on push. 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-55453) Github PR creating job but not building
Title: Message Title Stephen Schmidt commented on JENKINS-55453 Re: Github PR creating job but not building We're also experiencing this issue - Kirill Merkushev anything immediate come to mind that we might be able to do in order to mitigate the issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53393) Support for master-slave configuration
Title: Message Title José Lamas resolved as Fixed Jenkins / JENKINS-53393 Support for master-slave configuration Change By: José Lamas Status: In Progress Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/genexus-plugin/releases/tag/genexus-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-55911) java lint warning about annotation processor is not recognized
Title: Message Title Piotrek Zygielo created an issue Jenkins / JENKINS-55911 java lint warning about annotation processor is not recognized Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-01 14:29 Environment: jenkins: 2.162 warnings-ng-plugin: 2.1.2 analysis-model-api-plugin: 2.0.2 openjdk version "1.8.0_191" Priority: Minor Reporter: Piotrek Zygielo maven build warning: [INFO] - [WARNING] Supported source version 'RELEASE_7' from annotation processor 'org.netbeans.modules.schema2beansdev.Schema2BeansProcessor' less than -source '1.8' [INFO] 1 warning from javac -Xlint is not recognized/reported by plugin. Add
[JIRA] (JENKINS-55912) Forbidden OPTIONS request method for "input" step
Title: Message Title Dmitry Markelov created an issue Jenkins / JENKINS-55912 Forbidden OPTIONS request method for "input" step Issue Type: Bug Assignee: Unassigned Attachments: image001 (1).png, image001.png, image002.png, image003.png Components: pipeline-input-step-plugin Created: 2019-02-01 14:31 Environment: Jenkins ver. 2.138.2 Priority: Major Reporter: Dmitry Markelov When I push any buttons "Proceed" or "Abort" (picture 1). My browser send OPTIONS request, how you can view in attachments. And after that I get 403 status code, but if I send POST request directly to same url - all is good and work. I have all privileges in my project. Add Comment
[JIRA] (JENKINS-55812) Cannot use Incrementals from pom.xml
Title: Message Title Jesse Glick commented on JENKINS-55812 Re: Cannot use Incrementals from pom.xml This particular case is no longer relevant as of the plugin release (see jenkins-x-serverless-filerunner PR 11). 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-55890) RocketChat notification (using proxy) fails since version 1.3.1
Title: Message Title Martin Reinhardt started work on JENKINS-55890 Change By: Martin Reinhardt 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Christian Del Monte commented on JENKINS-55896 Re: Jenkins is not triggering build on any pullrequest created in bitbucket repo Yes, it matters... Actually I tested the payload you sent with I'm the mantainer of the https://plugins.jenkins.io/bitbucket-push-and-pull-request and I can see it coming. But, in this case, you are using the Bitbucket Pull request Builder, so, you need to configure the logger to see the logs of this plugin. Sorry for the misunderstandment 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-55904) Kubernetes pod template with persistance volume
Title: Message Title Carlos Sanchez commented on JENKINS-55904 Re: Kubernetes pod template with persistance volume Please ask questions in jenkins-users mailing list, jira is just for tracking bugs 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail commented on JENKINS-55896 Re: Jenkins is not triggering build on any pullrequest created in bitbucket repo ok thats cool. But once question you still didn't answer, is it matter to see payload of pull request in jenkins logs or not? Because I am only receiving on push, so most probably the problem should be at Bitbucket end, or it is not like that? 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Christian Del Monte commented on JENKINS-55896 Re: Jenkins is not triggering build on any pullrequest created in bitbucket repo all right, I understand... I'm the mantainer of the https://plugins.jenkins.io/bitbucket-push-and-pull-request plugin... I can help you only for this one. I would suggest, you could try to use it disabling the others and configuring it as described or you could send a issue to the mantainers of the plugin you are using: Bitbucket Pull request Builder. Please, let me know. 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Alex Earl commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Check the logs on the server and see if there is a connection attempt and if there are any errors. 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-55904) Kubernetes pod template with persistance volume
Title: Message Title Carlos Sanchez closed an issue as Not A Defect Jenkins / JENKINS-55904 Kubernetes pod template with persistance volume Change By: Carlos Sanchez Status: In Progress 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail commented on JENKINS-55896 Re: Jenkins is not triggering build on any pullrequest created in bitbucket repo I am not able to receive webhook on pull request creation or updation. I am just receiving webhook on push from Bitbucket and I can see this in my logs. I am answering your questions. Right now, I am jut using 1 plugin with the name of Bitbucket Pull request Builder and I am attaching SCM configurations and Build Trigger Configurations with you. 1: Image shows my SCM Configurations for Pull request --- 2: second image shows Build Trigger configurations. - 3: Third image shows Bitbucket webhook settings. --- 4: Last images shows the logs of Jenkins, Firstly I created pull request and check there were no logs in Jenkins but Bitbucket was saying that Bitbucket send the post request of webhook for pull request but in jenkins logs I am not able to see any receiving. Now I comit to our stagging branch and check if logs are generating and found that jenkins received post request from Bitbucket on which jenkins started build. Have a look in the picture. - 5: Now its your turn to identify where is the problem because I am not seeing logs on pull request but able to see while push. Let me know what kind of configurations I have to do or need to change. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to
[JIRA] (JENKINS-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail updated an issue Jenkins / JENKINS-55896 Jenkins is not triggering build on any pullrequest created in bitbucket repo Change By: Hassaan Sohail Attachment: Bitbucket-Webhook receive on push into specified branch.jpg 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Christian Del Monte commented on JENKINS-55896 Re: Jenkins is not triggering build on any pullrequest created in bitbucket repo please, use only the https://plugins.jenkins.io/bitbucket-push-and-pull-request plugin, disable all other Bitbucket related plugins and configure it as shown in the wiki page, only to be sure that it works as aspected 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-43563) Git plugin does not set user in pipeline
Title: Message Title Mark Waite edited a comment on JENKINS-43563 Re: Git plugin does not set user in pipeline [~leijiang ] please use the workaround [described in the comment|https://issues.jenkins-ci.org/browse/JENKINS-43563?focusedCommentId=310634=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-310634] prior to your request. Because there is an easy work around, this will not be investigated further by me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail updated an issue Jenkins / JENKINS-55896 Jenkins is not triggering build on any pullrequest created in bitbucket repo Change By: Hassaan Sohail Attachment: Bitbucket-Webhook Settings.jpg 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail updated an issue Jenkins / JENKINS-55896 Jenkins is not triggering build on any pullrequest created in bitbucket repo Change By: Hassaan Sohail Attachment: Bitbucket-Jenkins Build Trigger Settings.jpg 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail updated an issue Jenkins / JENKINS-55896 Jenkins is not triggering build on any pullrequest created in bitbucket repo Change By: Hassaan Sohail Attachment: Bitbucket-Jenkins SCM Settings.jpg 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-49833) getApiJson: (url=...) failed due to Http error #403
Title: Message Title Keith Sturkie commented on JENKINS-49833 Re: getApiJson: (url="" failed due to Http error #403 I am having the same issue as well. For the anonymous access, is that on the Jenkins side or the TFS side? 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-55893) Show build name instead of build number
Title: Message Title Gustaf Lundh started work on JENKINS-55893 Change By: Gustaf Lundh 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail updated an issue Jenkins / JENKINS-55896 Jenkins is not triggering build on any pullrequest created in bitbucket repo Change By: Hassaan Sohail Attachment: Bitbucket-Jenkins Build Trigger Settings.jpg 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-55896) Jenkins is not triggering build on any pullrequest created in bitbucket repo
Title: Message Title Hassaan Sohail updated an issue Jenkins / JENKINS-55896 Jenkins is not triggering build on any pullrequest created in bitbucket repo Change By: Hassaan Sohail Attachment: Bitbucket-Jenkins SCM Settings.jpg 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-43563) Git plugin does not set user in pipeline
Title: Message Title Mark Waite commented on JENKINS-43563 Re: Git plugin does not set user in pipeline [~leijiang please use the workaround described in the comment prior to your request. Because there is an easy work around, this will not be investigated further by me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-55905 Git Plugin 3.9.2 cannot clone remote repo Change By: Mark Waite Assignee: Mark Waite 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.
