[JIRA] (JENKINS-58457) Not able to open JenkinsUI from slave machine when jenkins is installed via war package on master
Title: Message Title Gurmanjot Singh updated an issue Jenkins / JENKINS-58457 Not able to open JenkinsUI from slave machine when jenkins is installed via war package on master Change By: Gurmanjot Singh Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200590.1562913451000.8470.1562914980112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58457) Not able to open JenkinsUI from slave machine when jenkins is installed via war package on master
Title: Message Title Gurmanjot Singh commented on JENKINS-58457 Re: Not able to open JenkinsUI from slave machine when jenkins is installed via war package on master Hi Team, I am really hoping to get a solution on this forum. Please help me with this issue. I never faced such an issue before. Recently, our existing Jenkins server machine had to be decommissioned. I am facing this issue while setting up jenkins on a new machine. Thanks, Gurman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200590.1562913451000.8485.1562915220540%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58458) Add CI for Java 11 to the Folder Auth Plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-58458 Add CI for Java 11 to the Folder Auth Plugin Issue Type: Improvement Assignee: Abhyudaya Sharma Components: folder-auth-plugin Created: 2019-07-12 07:25 Priority: Minor Reporter: Oleg Nenashev Example of a recommended buildPlugin() configuration: https://github.com/jenkinsci/label-verifier-plugin/blob/master/Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58373) Restore "all" gates to version 5
Title: Message Title James Howe commented on JENKINS-58373 Re: Restore "all" gates to version 5 If the total of all issues >= threshold then make the build unstable. It was the same as putting the same number for each separate severity. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200494.1562587793000.8489.1562916660471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58459) Add User documentation to Folder Auth README
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-58459 Add User documentation to Folder Auth README Issue Type: Improvement Assignee: Abhyudaya Sharma Components: folder-auth-plugin Created: 2019-07-12 07:30 Priority: Minor Reporter: Oleg Nenashev It would be great to have some user documentation for the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Attachment: image-2019-07-12-08-35-27-798.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200589.1562912637000.8493.1562916960121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58461) Configure the Release Drafter for Folder Auth
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-58461 Configure the Release Drafter for Folder Auth Issue Type: Improvement Assignee: Abhyudaya Sharma Components: folder-auth-plugin Created: 2019-07-12 07:39 Priority: Minor Reporter: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200595.1562917198000.8497.1562917200320%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/
[JIRA] (JENKINS-58460) Add Gitter chat for Folder Auth Plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-58460 Add Gitter chat for Folder Auth Plugin Issue Type: Improvement Assignee: Abhyudaya Sharma Components: folder-auth-plugin Created: 2019-07-12 07:39 Priority: Minor Reporter: Oleg Nenashev We will be using https://gitter.im/jenkinsci/role-strategy-plugin The plugin still uses the Role model under the hood, so it is fine. We will also need to document relations between plugins in READMEs for both repos Add Comment This mes
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth commented on JENKINS-58456 Re: explain polling per change Yes if you check the Pipeline Syntax snippet generator that checkbox controls incremental (true): This is described in: https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/chapter-polling-build-filters.html?Highlight=poll%20per Polling per Change: A build is carried out for every change that is submitted. The polling event will only return the oldest unbuilt change, resulting in incremental builds. Therefore when enabled you should see: CL 1 submitted. 5 minute poll builds CL1 CL2 submitted CL3 submitted 5 minute poll builds CL2 CL4 submitted 5 minute poll builds CL3 As you can see for every change to be built the polling has to occur more frequently than the submits. If you really want on demand builds for every changelist a 'change-submit' Perforce trigger that explicitly calls the Jenkins job URL passing the changelist as a parameter is the recommended mechanism. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200589.1562912637000.8499.1562917500508%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title
Karl Wirth edited a comment on JENKINS-58456
Re: explain polling per change
Hi [~luckyhorang], Yes if you check the Pipeline Syntax snippet generator that checkbox controls incremental (true):!image-2019-07-12-08-35-27-798.png!This is described in: [https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/chapter-polling-build-filters.html?Highlight=poll%20per] *Polling per Change:* A build is carried out for every change that is submitted. The polling event will only return the oldest unbuilt change, resulting in incremental builds. Therefore when enabled you should see: {code:java}CL 1 submitted.5 minute poll builds CL1CL2 submittedCL3 submitted5 minute poll builds CL2CL4 submitted5 minute poll builds CL3{code}As you can see for every change to be built the polling has to occur more frequently than the submits. If you really want on demand builds for every changelist a 'change-submit' Perforce trigger that explicitly calls the Jenkins job URL passing the changelist as a parameter is the recommended mechanism.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200589.1562912637000.8501.1562917560159%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200589.1562912637000.8507.1562917620383%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200589.1562912637000.8503.1562917620325%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth resolved as Not A Defect Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200589.1562912637000.8505.1562917620355%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58265) Add tags support
Title: Message Title Parichay Barpanda started work on JENKINS-58265 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200329.1561856688000.8508.1562920260091%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Alessio Moscatello commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Hello, this is causing troubles also on my company...I think that a solution could be moving bash commands to an external file or using groovy libraries, but during initial development phase of pipeline I usually put all the code in the a single file: it is not maintainable, but it is what I need to quickly develop and test new pipelines. I'll be really grateful to Jenkins developers if they can solve this issue BR, Alessio Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.8510.1562920921492%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Susovan Ghosh commented on JENKINS-57796 Re: Checkmarx affected by JEP-200 We are encountering the same issue on checkmarx-plugin version 8.90.1. Is there any update, any plan to fix 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199746.1559317468000.8569.1562921100229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Florian Wilhelm commented on JENKINS-31314 Re: Running asynchronous code inside a @NonCPS method should fail cleanly Hi Devin Nusbaum, I’m afraid this change broke our Jenkinsfile runner based testing because the warnings will be thrown as an exception there. Reproducer here https://github.com/fwilhe/repro-cps-issue I know we have to fix this in a proper way, but is there some way to turn it into warnings also on Jenkinsfile runner and not have it throw an exception? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166049.1446212529000.8576.1562922540860%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58462) Allow Jenkins Pipeline job config to be refreshed without running a build
Title: Message Title Dan Strong created an issue Jenkins / JENKINS-58462 Allow Jenkins Pipeline job config to be refreshed without running a build Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2019-07-12 09:20 Priority: Minor Reporter: Dan Strong Currently, when a Jenkins pipeline is created, job config such as parameters, cron triggers, etc. are not populated before the first build is run. For example, when a parameter is added to a pipeline, the Jenkins UI will not allow the user to input the parameter until the job has been built with that parameter missing. In many cases this leads to a failed build, but it may cause more subtle problems depending on how the pipeline is written. This is particularly frustrating when using the seed job pattern along with Jenkins pipelines; at the moment we seed our jenkins jobs nightly to ensure that our Jenkins configuration doesn't drift from source controlled job definitions. Every time a parametrized Pipeline job is seeded, the first run after the seed will not accept parameters and fail, forcing us to re-run the job. Functionality should be available to force jenkins to pull the latest Pipeline script and update job configuration in line with that script without running a build. This would allow us to trigger this "config refresh" from our seed job and avoid confusing and disruptive build failures.
[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title He Bihong created an issue Jenkins / JENKINS-58463 Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-07-12 09:53 Environment: Plugin version: 1.16.3, Centos; Jenkins start with java ops: -Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=2592000 Priority: Major Reporter: He Bihong Job will failed randomly by message "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API". The metrics total requests reached 64 when the issue happen. It seems in Kubernetes-plugin codes, the k8s client maxRequests is set to 64 by hard code. No configuration can change it. This java parameter also can not change it: kubernetes.max.concurrent.requests. This issue will happen even set MaxConcurrentRequestsPerHost to a big number. Once change MaxConcurrentRequestsPerHost in jenkins, the issue will disappear some times, but will occur again after running for a period. It seems it due to that the k8s API client recreated when change the configuration. Is it possible add a configuration for k8s client maxRequests?
[JIRA] (JENKINS-56865) Password to access InfluxDB is stored unencrypted on disk
Title: Message Title An Nguyen commented on JENKINS-56865 Re: Password to access InfluxDB is stored unencrypted on disk Do we have a ticket for making this plugin uses Jenkins credentials instead? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198532.1554301515000.8617.1562925540163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title Carlos Sanchez commented on JENKINS-58463 Re: Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" where do you see the hardcoded 64 number ? if you set the k8s cloud parameter max Requests Per Host to a value it will be used every time the client is recreated Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200597.1562925236000.8619.1562925900169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53360) Add ability to send list of data to InfluxDB
Title: Message Title An Nguyen commented on JENKINS-53360 Re: Add ability to send list of data to InfluxDB Pavel Vasilevich you can take a look this plugin https://wiki.jenkins.io/display/JENKINS/Job+and+Stage+Monitoring+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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193444.1535681232000.8624.1562925960319%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58464) UFT - Micro Focus Build - Timeout
Title: Message Title Ricardo Nazareth created an issue Jenkins / JENKINS-58464 UFT - Micro Focus Build - Timeout Issue Type: Bug Assignee: Kevin Lee Attachments: image-2019-07-12-11-03-47-413.png Components: microfocus-da-plugin Created: 2019-07-12 10:05 Labels: plugin Priority: Major Reporter: Ricardo Nazareth Recently the Timeout box keep assuming and filling the box whit google credentials. The workaround is to disable user´s and password recording or by filling the box whit a specific number. Add Comment
[JIRA] (JENKINS-47827) Support passing a user/uid into containerTemplate
Title: Message Title Valentin Delaye commented on JENKINS-47827 Re: Support passing a user/uid into containerTemplate Ohhh so cool to see it's in progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186329.1509818749000.8628.1562926320422%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19320) Add support of user macros
Title: Message Title Constantin Bugneac commented on JENKINS-19320 Re: Add support of user macros Having issues with case-sensitivity of AD LDAP group match for users using role strategy plugin. It would be nice to be case-insensitive. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150768.1377230987000.8640.1562926680168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58465) installing the plugin lead to many uneeded plugins
Title: Message Title James Nord created an issue Jenkins / JENKINS-58465 installing the plugin lead to many uneeded plugins Issue Type: Task Assignee: Unassigned Components: parallel-test-executor-plugin Created: 2019-07-12 10:27 Priority: Minor Reporter: James Nord When installing the plugin in a clean instance many other uneeded plugins are also pulled in as they are detached since the jenkins version that the plugin targets. (or some plugins are not using optional extensions and pulling in the kitchen sink) These are likely due to transitive deps on plugins, but there is no need at all to ever install PAM auth, or windows agents without an explicit opt in (Javadoc and ANT are also not reallyneeded). It may also be possible to make some of the requirements for the code to be optional given that if you are using pipeline for the splitTests you do not even have/need any maven jobs) Javadoc Plugin Success Maven Integration plugin Success WMI Windows Agents Plugin Success
[JIRA] (JENKINS-58466) GitLabPipeline Status cannot transition via run from running
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58466 GitLabPipeline Status cannot transition via run from running Issue Type: Improvement Assignee: Parichay Barpanda Attachments: Screenshot from 2019-07-12 10-44-23.png Components: gitlab-branch-source-plugin Created: 2019-07-12 10:56 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58265) Add tags support
Title: Message Title Parichay Barpanda updated JENKINS-58265 Jenkins / JENKINS-58265 Add tags support Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200329.1561856688000.8650.1562929800082%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58265) Add tags support
Title: Message Title Parichay Barpanda commented on JENKINS-58265 Re: Add tags support Added `GitLabTagSCMHead` and `TagDiscoveryTrait` and more. See https://github.com/baymac/gitlab-branch-source-plugin/pull/24 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200329.1561856688000.8651.1562929920044%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58467) NPE during Tag fetching
Title: Message Title Parichay Barpanda started work on JENKINS-58467 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200601.1562929965000.8653.1562929980151%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58467) NPE during Tag fetching
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58467 NPE during Tag fetching Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-12 11:12 Labels: gsoc-2019 Priority: Blocker Reporter: Parichay Barpanda See https://github.com/baymac/gitlab-branch-source-plugin/pull/24#issue-297019727 Add Comment
[JIRA] (JENKINS-58309) Branch indexing doesn't work on closed mrs branches
Title: Message Title Parichay Barpanda commented on JENKINS-58309 Re: Branch indexing doesn't work on closed mrs branches Fixed it in https://github.com/baymac/gitlab-branch-source-plugin/pull/24 by adding all merge requests and not just opened merge requests to GitLabSCMSourceRequest. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200417.1562134171000.8654.1562930160173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58309) Branch indexing doesn't work on closed mrs branches
Title: Message Title Parichay Barpanda started work on JENKINS-58309 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200417.1562134171000.8655.1562930160239%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58309) Branch indexing doesn't work on closed mrs branches
Title: Message Title Parichay Barpanda updated JENKINS-58309 Jenkins / JENKINS-58309 Branch indexing doesn't work on closed mrs branches Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200417.1562134171000.8656.1562930160252%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56073) Configuration-as-Code compatibility
Title: Message Title Joseph Petersen commented on JENKINS-56073 Re: Configuration-as-Code compatibility WIP: jfrog/jenkins-artifactory-plugin #169 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197499.1549833378000.8669.1562931720152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58198) JIRA plugin passes configuration test but does nothing
Title: Message Title Aaron Sua commented on JENKINS-58198 Re: JIRA plugin passes configuration test but does nothing We are still unable to use this plugin. Has anyone had a chance to look into this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200254.1561502874000.8670.1562932320048%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58455) NPE when processing MR branches in subprojects
Title: Message Title Parichay Barpanda updated JENKINS-58455 Jenkins / JENKINS-58455 NPE when processing MR branches in subprojects Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200588.1562907495000.8671.1562934060477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58455) NPE when processing MR branches when source project doesn't exist anymore
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58455 NPE when processing MR branches when source project doesn't exist anymore Change By: Parichay Barpanda Summary: NPE when processing MR branches in subprojects when source project doesn't exist anymore Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200588.1562907495000.8672.1562934180078%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58455) NPE when processing MR branches when source project doesn't exist anymore
Title: Message Title Parichay Barpanda commented on JENKINS-58455 Re: NPE when processing MR branches when source project doesn't exist anymore Fixed in 585f115. See https://github.com/baymac/gitlab-branch-source-plugin/pull/23#issuecomment-510865749, Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200588.1562907495000.8673.1562934240045%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57468) scm/SubversionSCM/enterCredential link is obsolete
Title: Message Title Jesse Glick updated JENKINS-57468 Jenkins / JENKINS-57468 scm/SubversionSCM/enterCredential link is obsolete Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.12.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199328.1557857142000.8675.1562934540236%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27079) ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title Jesse Glick commented on JENKINS-27079 Re: ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState There are several distinct exception messages here, which are likely unrelated: java.lang.ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState cannot be cast to hudson.scm.SVNRevisionState sounds like a bug in the Multiple SCMs plugin. Please file separately with steps to reproduce from scratch if you have them. java.lang.ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to hudson.scm.SVNRevisionState might be a bug in this plugin, or in Jenkins core. Smells like an upgrade problem, or a problem with the first build of a job, or something like that. Please file separately with steps to reproduce from scratch if you have them. The originally reported java.lang.ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState which suggests a problem in class loading—two copies of the Subversion plugin being loaded under different names, or some other plugin copying classes from this one for unknown reasons. To begin diagnosis, try bisecting your $JENKINS_HOME/plugins/ directory, or it may be possible to use /script to inspect resources multiply available from UberClassLoader. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160869.1424
[JIRA] (JENKINS-58468) Unable to checkout git repo from agents
Title: Message Title g hs1 created an issue Jenkins / JENKINS-58468 Unable to checkout git repo from agents Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-07-12 12:43 Environment: Jenkins ver. 2.162 Git plugin 3/10.0 RHEL7 git versions 1.8 and 2.16 tried Priority: Minor Reporter: g hs1 We are unable to get any agent to check out a repo from git (GitLab in our case). We have configured the certs and verified that both the jenkins user and the user in the credential we use to access GitLab can check out locally on the agent. When we run a build which checks out using that same credential on the same agent, the fetch fails with Peer's Certificate issuer is not recognized. We have also configured the Jenkins master with the certs and that can check out from a build run on the master without problems. As soon as we attempt to run on an agent, we hit the same issue. We have sslVerify=false set for all users. The cert is self-signed. It seems somehow that the authentication isn't crossing the master-agent boundary. Since git is the default RCS for Jenkins and so widely used we might be missing something but we're at a loss to know how to proceed. Thanks.
[JIRA] (JENKINS-58154) Enhance usability when choosing time range.
Title: Message Title Jack Shen updated JENKINS-58154 Jenkins / JENKINS-58154 Enhance usability when choosing time range. Change By: Jack Shen Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200201.1561291297000.8698.1562935800558%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58363) Add backend API for fetching date presets.
Title: Message Title Jack Shen started work on JENKINS-58363 Change By: Jack Shen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200478.1562338782000.8701.1562935800630%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58347) Complete exclude function
Title: Message Title Jack Shen started work on JENKINS-58347 Change By: Jack Shen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200462.1562252859000.8700.1562935800617%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58469) Not able to generate the coverage report with jenkins jacoco plugin 1.0.19 and jacoco 0.7.4
Title: Message Title
Satya yamanuri created an issue
Jenkins / JENKINS-58469
Not able to generate the coverage report with jenkins jacoco plugin 1.0.19 and jacoco 0.7.4
Issue Type:
Bug
Assignee:
Unassigned
Components:
jacoco-plugin
Created:
2019-07-12 12:56
Priority:
Minor
Reporter:
Satya yamanuri
What went wrong: Execution failed for task ':CoreServices:testCoverage'. > Unable to read execution data file C:\p4\nemo\ce\sw\4.0\team\services\CoreServices\build\jacoco\testDebugUnitTest.exec Code base: task testCoverage(type: JacocoReport) { reports { xml.enabled = true html.enabled = true } def mainSrc = "${project.projectDir}/src" sourceDirectories = files([mainSrc]) def fileFilter = ['**/R.class', '**/R$*.class', '**/BuildConfig.*', '**/Manifest*.*', '**/*Test*.*', 'android/**/*.*'] def debugTree = fileTree(dir: "${project.buildDir.getPath()}/intermediates/classes/debug", excludes: fileFilter) classDirectories = files([debugTree]) // executionData = files("${project.buildDir.getPath()}/jacoco/testDebugUnitTest.exec") executionData = fileTree(dir: project.projectDir, includes: ['**/*.exec']) testCoverage.dependsOn('testDebugUnitTest') }
Add Comment
[JIRA] (JENKINS-48334) GIT with Jenkins failed with error "self signed certificate in certificate chain"
Title: Message Title Mark Waite edited a comment on JENKINS-48334 Re: GIT with Jenkins failed with error "self signed certificate in certificate chain" Please request help from the places which more people read rather than using a bug report to request help.There are far fewer people who read git client plugin bug reports than read * [chat|https://jenkins.io/chat/] on the [Jenkins internet relay channel|http://webchat.freenode.net/?channels=jenkins], the [jenkins channel on gitter| https:// gitter.im/jenkinsci/jenkins], and * [mailing lists|https://jenkins.io/mailing-lists/] like [Jenkins users|https://groups.google.com/forum/#!forum/jenkinsci-users].On this specific issue, I'm opposed to self-signed certificates, especially over commercial products like Atlassian Stash. Your company has purchased Atlassian Stash. You'll be much better served by also purchasing and installing an SSL certificate for the server, rather than fighting with self-signed certificates. Yes, it is possible in some cases to make self-signed certificates work, but they are brittle and hard to maintain. You'll spend more maintaining self-signed certificates than the cost of the SSL certificate. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186926.1512110637000.8706.1562936940153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58468) Unable to checkout git repo from agents
Title: Message Title Mark Waite updated JENKINS-58468 Please don't use bug reports to request help with configuration issues. Git plugin bug reports are reviewed by very few people. They are the same people that spend their time maintaining the plugin, investigating bug reports, and fixing those bugs. There are many more people that monitor the Jenkins user mailing list and the Jenkins chat channels. You're much more likely to receive help from that larger group of people than from the much smaller group that watches Jenkins bug reports. In your specific case, there are some alternatives you might try, including: Use Let's Encrypt to apply a certificate to your git server HTTP end point Purchase a certificate for your git server HTTP end point Enable JGit on your Jenkins server and clone with JGit instead of command line git Use ssh instead of https to clone the repository Refer to the "how to disable ssl certificate validation" on stackoverflow Refer to the "Git with Jenkins fails with self-signed certificate error" article on stackoverflow Jenkins / JENKINS-58468 Unable to checkout git repo from agents Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-58468) Unable to checkout git repo from agents
Title: Message Title Mark Waite updated JENKINS-58468 Jenkins / JENKINS-58468 Unable to checkout git repo from agents Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200602.1562935438000.8710.1562937000436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Jesse Glick commented on JENKINS-31314 Re: Running asynchronous code inside a @NonCPS method should fail cleanly Florian Wilhelm JFR is being tracked in JENKINS-58407. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166049.1446212529000.8736.1562937062194%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58470) After test case failed, on console logs continuously test suites status is getting displayed and execution is still preceding.
Title: Message Title Bhagyashri Jagdale created an issue Jenkins / JENKINS-58470 After test case failed, on console logs continuously test suites status is getting displayed and execution is still preceding. Issue Type: Bug Assignee: Katalon Studio Attachments: BuildIsExecutingsameStatement.PNG Components: katalon-plugin Created: 2019-07-12 13:18 Environment: Windows 10 Labels: user-experience windows pipeline Priority: Minor Reporter: Bhagyashri Jagdale Pre-requisite: 1. Katalon Studio's plugin must be installed. 2. In Katalon studio test suite must be created with few test cases (which should fail). Actual: When user adds build step as Execute katalon test suite and specify the local katalon directory and enter the command to execute the test suite and execute the job, then after failing test cases continuously test cases status is getting display on console logs. Expected: Whenever user executes any job from which includes katalon test suite executions step by option windows batch command/ katalon test suite execution, then after test suite execution and specified actions build should get stop and status should get reflected. Steps: 1. Login to Jenkins. 2. Create a freestyle job. 3. Select configure option of the created job. 4. Add build step as Execute katalon studio test. 5. Enter path of the katalon.exe directory to into " Use pre-in
[JIRA] (JENKINS-58471) Git SCM polling does not work with "honor refspec"
Title: Message Title
Antoine Tran created an issue
Jenkins / JENKINS-58471
Git SCM polling does not work with "honor refspec"
Issue Type:
Improvement
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-07-12 13:27
Environment:
Jenkins 2.60.3 Git client 2.7.1
Priority:
Minor
Reporter:
Antoine Tran
Actual behavior When setting refspec like this: +refs/heads/${GIT_REF}:refs/remotes/origin/${GIT_REF} And after building a branch, the SCM polling does not find a match with git ls-remote and the built branch:
[poll] Last Built Revision: Revision ce9cc0a298fc94cafa4cc87e0bb1544b359ee752 (feature/20190711-FVE-test_job_scm)
> git --version # timeout=10
...
Ignoring refs/heads/feature/20190711-FVE-test_job_scm as it doesn't match any of the configured refspecs
No changes
Expected behavior: The SCM poll should keep the source refspec of the last build, in this case "refs/heads/feature/20190711-FVE-test_job_scm", and do a comparison with that, with git ls-remote:
[poll] Last Built Revision: Revision ce9cc0a298fc94cafa4cc87e0bb1544b359ee752 (feature/20190711-FVE-test_job_scm)
> git --version # timeout=10
...
[poll] Latest remote head revision on refs/heads/feature/20190711-FVE-test_job_scm is: 4a598524b56af4493027828d7e2a5f1b3179ec82
Done. Took 0.4 sec
Changes found
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Change By: Ulli Hafner See details here [https://superuser.com/questions/1458345/history-only-seems-to-be-pointing-to-the-current-build-when-using-warnings-ng-je] History only seems to be pointing to the current build when using Warnings NG jenkin plugin and JenkinsFile pipeline.Here is some sudo code from our JenkinsFile [Jenkinsfile Part1|https://i.stack.imgur.com/jrw0N.png] [Jenkinsfile Part2|https://i.stack.imgur.com/nIi8P.png] What we are seeing is that our history graph only seems to be depicting what was caught on the current build and is missing the info from previous builds.Does anyone has any idea on why this is..[Even when we have multiple builds that were run before we introduced warnings ng plugin|https://i.stack.imgur.com/JjKyX.png]!image-2019-07-11-14-03-35-746.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.156
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ulli Hafner commented on JENKINS-58448 Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Are the builds < #161 still available? Did you enable the reports for some builds < #161? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.8744.1562938320153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58455) NPE when processing MR branches when source project doesn't exist anymore
Title: Message Title Parichay Barpanda edited a comment on JENKINS-58455 Re: NPE when processing MR branches when source project doesn't exist anymore Fixed in 585f115 ddc1c0b . See https Seehttps ://github.com/baymac/gitlab-branch-source-plugin/pull/23#issuecomment- 510865749, 510874429 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200588.1562907495000.8745.1562938560069%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58455) NPE when processing MR branches when source project doesn't exist anymore
Title: Message Title Parichay Barpanda edited a comment on JENKINS-58455 Re: NPE when processing MR branches when source project doesn't exist anymore Fixed in ddc1c0b. Seehttps See https ://github.com/baymac/gitlab-branch-source-plugin/pull/23#issuecomment-510874429 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200588.1562907495000.8746.1562938560113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58455) NPE when processing MR branches when source project doesn't exist anymore
Title: Message Title Parichay Barpanda updated JENKINS-58455 Jenkins / JENKINS-58455 NPE when processing MR branches when source project doesn't exist anymore Change By: Parichay Barpanda Status: In Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200588.1562907495000.8747.1562938620206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58269) Fix projectOwner for group or subgroup
Title: Message Title Parichay Barpanda updated JENKINS-58269 Jenkins / JENKINS-58269 Fix projectOwner for group or subgroup Change By: Parichay Barpanda Status: In Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200333.1561859562000.8748.1562938620312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58266) Remove depending on projectOwner field in SCMHeads
Title: Message Title Parichay Barpanda updated JENKINS-58266 Jenkins / JENKINS-58266 Remove depending on projectOwner field in SCMHeads Change By: Parichay Barpanda Status: In Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200330.1561857089000.8749.1562938680230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57737) Publish blog post
Title: Message Title Jack Shen updated JENKINS-57737 Jenkins / JENKINS-57737 Publish blog post Change By: Jack Shen Status: In Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199681.1559138155000.8760.1562938800631%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58347) Complete exclude function
Title: Message Title Jack Shen updated JENKINS-58347 Jenkins / JENKINS-58347 Complete exclude function Change By: Jack Shen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200462.1562252859000.8762.1562938860157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58472) Jenkins show no such file in console output for pom.xml file in Mac
Title: Message Title Hima MOhan created an issue Jenkins / JENKINS-58472 Jenkins show no such file in console output for pom.xml file in Mac Issue Type: Bug Assignee: Unassigned Components: pom2config-plugin Created: 2019-07-12 13:42 Priority: Major Reporter: Hima MOhan Jenkins show unsuccessful build with console output as 'no such file' for pom.xml even when providing correct path of pom.xml file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58333) Implement Param Validation in Plugin Service
Title: Message Title Jack Shen updated JENKINS-58333 Jenkins / JENKINS-58333 Implement Param Validation in Plugin Service Change By: Jack Shen Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200445.1562219609000.8764.1562938980287%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit updated an issue Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Change By: Ankush Pandit History only seems to be pointing to the current build when using Warnings NG jenkin plugin and JenkinsFile pipeline.Here is some sudo code from our JenkinsFile [Jenkinsfile Part1|https://i.stack.imgur.com/jrw0N.png] [Jenkinsfile Part2|https://i.stack.imgur.com/nIi8P.png] What we are seeing is that our history graph only seems to be depicting what was caught on the current build and is missing the info from previous builds.Does anyone has any idea on why this is..[Even when we have multiple builds that were run before we introduced with warnings ng plugin|https://i.stack.imgur.com/JjKyX.png]!image-2019-07-11-14-03-35-746.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.8781.1562939700335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit updated an issue Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Change By: Ankush Pandit Attachment: image-2019-07-12-08-55-51-376.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.8792.1562939760303%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58473) The RESTful API for "Warnings Next Generation" plugin doesn't work
Title: Message Title
Alexander Obuhovich created an issue
Jenkins / JENKINS-58473
The RESTful API for "Warnings Next Generation" plugin doesn't work
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-07-12 13:55
Priority:
Minor
Reporter:
Alexander Obuhovich
When using "Warnings" plugin I was able to get JSON result of checkstyle warnings using this URL: http://\{jenkins-host}/job/{job-name}/{build-number}/checkstyleResult/api/json (values in {...} are different for each install. After installing "Warnings Next Generation" plugin and removing "Warnings" plugin (as it's being deprecated) the above URL will redirect back to http://\{jenkins-host}/job/{job-name}/{build-number}/ page and of course won't return any JSON. I'm doing a POST request. Any idea why it stopped working?
Add Comment
[JIRA] (JENKINS-58473) The RESTful API for "Warnings Next Generation" plugin doesn't work
Title: Message Title
Alexander Obuhovich updated an issue
Jenkins / JENKINS-58473
The RESTful API for "Warnings Next Generation" plugin doesn't work
Change By:
Alexander Obuhovich
When using "Warnings" plugin I was able to get JSON result of checkstyle warnings using this URL (values in \{...} are different for each install : {noformat} http: //\ {jenkins-host}/job/ \ {job-name}/ \ {build-number}/checkstyleResult/api/json (values in \ { ... noformat } are different for each install. After installing "Warnings Next Generation" plugin and removing "Warnings" plugin (as it's being deprecated) the above URL will redirect back to [ http://\ |http:] {jenkins-host} /job/\{job-name}/\{build-number}/ page and of course won't return any JSON.I'm doing a POST request. Any idea why it stopped working?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200608.1562939704000.8794.1562939820259%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58473) The RESTful API for "Warnings Next Generation" plugin doesn't work
Title: Message Title
Alexander Obuhovich updated an issue
Jenkins / JENKINS-58473
The RESTful API for "Warnings Next Generation" plugin doesn't work
Change By:
Alexander Obuhovich
When using "Warnings" plugin I was able to get JSON result of checkstyle warnings using this URL (values in \{...} are different for each install: {noformat}http: // {jenkins-host}/job/{job-name}/{build-number}/checkstyleResult/api/json{noformat}After installing "Warnings Next Generation" plugin and removing "Warnings" plugin (as it's being deprecated) the above URL will redirect back to [http://\|http:] {jenkins-host}/job/\{job-name}/\{build-number}/ page and of course won't return any JSON.I'm doing a POST request. Any idea why it stopped working?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200608.1562939704000.8796.1562939820291%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit updated an issue Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Change By: Ankush Pandit Attachment: image-2019-07-12-08-58-15-290.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.8798.1562939940128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58468) Unable to checkout git repo from agents
Title: Message Title g hs1 commented on JENKINS-58468 Re: Unable to checkout git repo from agents Firstly, as stated, I have taken most of those actions and I don't actually know if there is a bug here. It's hard to imagine what else is going wrong, given the situation described. I did try and look at your mailing lists but they require logins to Google, which I don't want to deal with, before I can even see the archive. Thanks for the suggestions, though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200602.1562935438000.8800.156294241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit updated an issue Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Change By: Ankush Pandit Attachment: image-2019-07-12-08-59-14-528.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.8802.156294301%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58474) Port not reachable while creating a slave agent in windows for a linux master
Title: Message Title Niranjani Venkatesan created an issue Jenkins / JENKINS-58474 Port not reachable while creating a slave agent in windows for a linux master Issue Type: Bug Assignee: Karl-Heinz Marbaise Attachments: image-2019-07-12-08-57-59-825.png Components: java-client-api Created: 2019-07-12 14:00 Priority: Major Reporter: Niranjani Venkatesan I have configured a master jenkins in Linux environment(centos 7 server) and I am trying to create a Windows 10 slave agent. When I try using "Launch agent by connecting it to the master" option and running the command javaws in windows command prompt, I get the following error. java.io.IOException:http://localhost:8080/ provided port:37583 is not reachable at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:287) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474) Add Comment
[JIRA] (JENKINS-58474) Port not reachable while creating a slave agent in windows for a linux master
Title: Message Title Niranjani Venkatesan updated an issue Jenkins / JENKINS-58474 Port not reachable while creating a slave agent in windows for a linux master Change By: Niranjani Venkatesan Attachment: image-2019-07-12-08-57-59-825.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200609.1562940037000.8806.1562940120184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title
Ankush Pandit commented on JENKINS-58448
Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Looks like these are available. Can you please explain what you mean by available? We do clean up our workspaces each time after the build using the following code.
cleanWs()
dir("${env.WORKSPACE}@tmp")
{| |deleteDir()| |}| |dir("${env.WORKSPACE}@script")| |{| |deleteDir()| |}
dir("${env.WORKSPACE}@script@tmp")
{| |deleteDir()| }
Also you can see that warnings ng config change was introduced in build 159. Also here are the snapshots from build 160 And 159
[JIRA] (JENKINS-58473) The RESTful API for "Warnings Next Generation" plugin doesn't work
Title: Message Title Ulli Hafner commented on JENKINS-58473 Re: The RESTful API for "Warnings Next Generation" plugin doesn't work Did you try the new URLs? See: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#remote-apis Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200608.1562939704000.8810.1562940240129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58471) Git SCM polling does not work with "honor refspec"
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-58471 Git SCM polling does not work with "honor 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200606.1562938023000.8812.1562940300146%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58083) Draft blog post for Coding Phase 1
Title: Message Title Long Nguyen updated JENKINS-58083 Jenkins / JENKINS-58083 Draft blog post for Coding Phase 1 Change By: Long Nguyen Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200108.1560879654000.8813.1562940420292%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit commented on JENKINS-58448 Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Question, where is the data for these graphs being pulled off? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.8815.1562940420359%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ulli Hafner commented on JENKINS-58448 Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline The data is derived from the Jenkins objects. So if you have an analysis action for #159 and #160, then they should appear in the chart as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.8817.1562940840126%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49918) Carriage return "\r" treated as newline
Title: Message Title Gaba Gaba commented on JENKINS-49918 Re: Carriage return "\r" treated as newline This issue highly affects readability of logs from python, when progressbar library is used (eg. tqdm). If processing is not lasting very long it is quite ok: 0%| | 0/19040 [00:00 But it processing takes some time, then this progressbar-lines can flood all the console output - so the scrolling from the beginning to the end can last up to one minute... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188908.1520251722000.8819.1562940960212%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58473) The RESTful API for "Warnings Next Generation" plugin doesn't work
Title: Message Title
Alexander Obuhovich commented on JENKINS-58473
Re: The RESTful API for "Warnings Next Generation" plugin doesn't work
I had no idea they exist. Since all URLs within a job (where I can see nice graphs and issues) remained the same I thought API URLs were also brought back from "Warnings" plugin. The URL I was looking for turned out to be this one (even though output format isn't the same):
http://{jenkins-host}/job/{job-name}/{build-number}/checkstyle/new/api/json
Thank you.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200608.1562939704000.8822.1562942040112%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57602) NPE in Support Core Plugin when reporting agents
Title: Message Title Ramon Leon commented on JENKINS-57602 Re: NPE in Support Core Plugin when reporting agents It only happens with JCasC because the node configured ha the field to null instead of "" (empty string). Not sure whether it's a bug in JCasC or not because the field is mandatory anyway. Why can you leave it empty in the UI? If we consider that JCasC should do the same as the UI then it's a bug in the UI. Oleg Nenashev WDYT? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199526.1558523885000.8824.1562942580173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57602) NPE in Support Core Plugin when reporting agents
Title: Message Title Ramon Leon edited a comment on JENKINS-57602 Re: NPE in Support Core Plugin when reporting agents It only happens with JCasC because the node configured ha the field to *null* instead of *""* (empty string). Not sure whether it's a bug in JCasC or not because the field is mandatory anyway. Why can you leave it empty in the UI?If we consider that JCasC should do the same as the UI then it's a bug in the UI.[~oleg_nenashev] WDYT? https://github.com/jenkinsci/support-core-plugin/pull/179#issuecomment-510910195 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199526.1558523885000.8827.1562942640134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50898) Computer can be removed when the channel is still connected
Title: Message Title James Nord updated an issue Jenkins / JENKINS-50898 Computer can be removed when the channel is still connected Change By: James Nord Still not entirely sure how this happens but it is possible with cloud provided agents that the Computer is removed from Jenkins whilst the CHannel is still open.This causes leaks of Threads and ultimately the death of Jenkins as it can not longer create threads. (2 threads are leaked for every agent provisioned - the "Channel Ping thread" and the "Channel Reader").This only occurs if the cloud provider (a proprietary one in this case) was provisioning agents with > 1 executor. The provider updates the executrors executors to remove them once they have been used but eventually when the agent is removed the channel as not been closed. It is my understanding that Jenkins should close the channel when a node/computer is removed as it the case when the number of agents is 1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190023.1524135719000.8836.156294282058
[JIRA] (JENKINS-50898) Computer can be removed when the channel is still connected
Title: Message Title James Nord assigned an issue to Unassigned Jenkins / JENKINS-50898 Computer can be removed when the channel is still connected Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190023.1524135719000.8838.1562942880159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50898) Computer can be removed when the channel is still connected
Title: Message Title James Nord updated an issue Jenkins / JENKINS-50898 Computer can be removed when the channel is still connected Change By: James Nord Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190023.1524135719000.8837.1562942880134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54930) withEnv should accept Map as well as List
<<< text/html; charset="UTF-8": Unrecognized >>>
[JIRA] (JENKINS-58475) GitHub Plugin fails during handshake with Github server
Title: Message Title Dennis Behm created an issue Jenkins / JENKINS-58475 GitHub Plugin fails during handshake with Github server Issue Type: Bug Assignee: Kirill Merkushev Attachments: githubPlugin_Jenkins.log Components: github-plugin Created: 2019-07-12 15:12 Environment: Jenkins ver. 2.150.2 Github-Plugin 1.29.4 Ubuntu or RedHat Linux Labels: plugins Priority: Major Reporter: Dennis Behm Connecting the Github Plugin in Jenkins to our Github server fails with an Handshake issue "Unable to find acceptable protocols" when running Jenkins with the IBM Java SDK (https://developer.ibm.com/javasdk/downloads/sdk8/) Please see the attached Jenkins.log for the stacktrace.
[JIRA] (JENKINS-52554) pipeline failure if when tag expression is contained
Title: Message Title
Larry Schiefer commented on JENKINS-52554
Re: pipeline failure if when tag _expression_ is contained
This appears to be a problem with the default way the tag comparison works. I found you can work around this by specifying a pattern and comparator:
pipeline {
...
stages {
...
stage('Build Release') {
when {
tag pattern: '^release-*', comparator: "REGEXP"
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192395.1531514992000.8852.1562946540221%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit commented on JENKINS-58448 Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Follow up questions. So these Jenkins objects, do they get deleted if we delete the workspace? Where are they stored? If there were any errors while deriving them, where would we see them? How else can I help in figuring out this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.8855.1562946960174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Mark Waite updated JENKINS-50886 Jenkins / JENKINS-50886 Declarative pipeline with pollSCM triggers 2 builds Change By: Mark Waite Status: Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190011.1524103101000.8861.1562947020851%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44343) Inverse build strategy is building when there are no changes on a branch
Title: Message Title Mark Waite updated JENKINS-44343 Jenkins / JENKINS-44343 Inverse build strategy is building when there are no changes on a branch Change By: Mark Waite Status: Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182152.1495119384000.8869.1562947021074%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45771) Disable shallow clone when we know a merge will take place
Title: Message Title Mark Waite updated JENKINS-45771 Jenkins / JENKINS-45771 Disable shallow clone when we know a merge will take place Change By: Mark Waite Status: Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183978.1500974294000.8867.1562947020913%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41830) SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Title: Message Title Mark Waite updated JENKINS-41830 Jenkins / JENKINS-41830 SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job Change By: Mark Waite Status: Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178677.1486515524000.8872.1562947260650%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34426) Changing project-based settings for AD-Groups shows error
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-34426 Changing project-based settings for AD-Groups shows error Change By: Mark Waite Component/s: git-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170013.1461581177000.8881.1562947440794%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28976) windows master, mac slave, polling fails trying to launch windows GIT_SSH program
Title: Message Title Mark Waite updated JENKINS-28976 Jenkins / JENKINS-28976 windows master, mac slave, polling fails trying to launch windows GIT_SSH program Change By: Mark Waite Status: Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163434.1434661276000.8904.1562947500241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58476) findFiles has recursion error when passed a method call for the value of the glob parameter
Title: Message Title Coltrey Mather created an issue Jenkins / JENKINS-58476 findFiles has recursion error when passed a method call for the value of the glob parameter Issue Type: New Feature Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2019-07-12 16:07 Priority: Trivial Reporter: Coltrey Mather I get the following error when running the following script in a pipeline job. Jenkins ver. 2.121.3 pipeline-utility-steps-plugin 2.1.0 java.lang.StackOverflowError: Excessively nested closures/functions at WorkflowScript.getPath(WorkflowScript:3) - look for unbounded recursion - call depth: 1025 at com.cloudbees.groovy.cps.impl.CpsFunction.invoke(CpsFunction.java:28) at com.cloudbees.groovy.cps.impl.CpsCallableInvocation.invoke(CpsCallableInvocation.java:40) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:62) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixName(FunctionCallBlock.java:77) at sun.reflect.GeneratedMethodAccessor136.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxConti
[JIRA] (JENKINS-58467) NPE during Tag fetching
Title: Message Title Parichay Barpanda updated JENKINS-58467 Jenkins / JENKINS-58467 NPE during Tag fetching Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200601.1562929965000.8915.1562949180101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58467) NPE during Tag fetching
Title: Message Title Parichay Barpanda commented on JENKINS-58467 Re: NPE during Tag fetching Fixed in a06cfe5 of https://github.com/baymac/gitlab-branch-source-plugin/pull/24 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200601.1562929965000.8916.1562949240059%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58477) No automatic builds for tags
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58477 No automatic builds for tags Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-12 16:37 Labels: gsoc-2019 Priority: Blocker Reporter: Parichay Barpanda All tags are not fetched only the latest tag is fetched. The build on the tags all not done. Add Comment
