[JIRA] (JENKINS-61115) Boost test schema wrongfully rejects testsuite-scope exceptions
Title: Message Title Nikolas Falco commented on JENKINS-61115 Re: Boost test schema wrongfully rejects testsuite-scope exceptions You can create an ad hoc cpp test case to that produce the report like you have. Mathias Gaunard: FooException should do I suppose? I would not suppose, Something generated by the tool is used to also map testsuite exception by XSLT Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204628.1581946506000.498.1582789740192%40Atlassian.JIRA.
[JIRA] (JENKINS-61249) Reduce bootstrap plugin time by asyncronious initial loading of Octane configurations
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-61249 Reduce bootstrap plugin time by asyncronious initial loading of Octane configurations Issue Type: Improvement Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2020-02-27 07:05 Priority: Major Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You
[JIRA] (JENKINS-61249) Reduce bootstrap plugin time by asyncronious initial loading of Octane configurations
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-61249 Reduce bootstrap plugin time by asyncronious initial loading of Octane configurations Change By: Radi Berkovich Labels: 6.1.2-BETA Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204816.1582787125000.496.1582787160203%40Atlassian.JIRA.
[JIRA] (JENKINS-61248) fix integration of ALM Octane - CloudBees Role-Based Access Control plugin
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-61248 fix integration of ALM Octane - CloudBees Role-Based Access Control plugin Change By: Radi Berkovich Labels: 6.1.2-BETA Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204815.1582786917000.494.1582786980070%40Atlassian.JIRA.
[JIRA] (JENKINS-61248) fix integration of ALM Octane - CloudBees Role-Based Access Control plugin
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-61248 fix integration of ALM Octane - CloudBees Role-Based Access Control plugin Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2020-02-27 07:01 Priority: Critical Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this
[JIRA] (JENKINS-61108) ALM Octane Sonar integration does not support folders
Title: Message Title Radi Berkovich updated JENKINS-61108 Jenkins / JENKINS-61108 ALM Octane Sonar integration does not support folders Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204620.1581933005000.492.1582786860278%40Atlassian.JIRA.
[JIRA] (JENKINS-61108) ALM Octane Sonar integration does not support folders
Title: Message Title Radi Berkovich updated JENKINS-61108 Jenkins / JENKINS-61108 ALM Octane Sonar integration does not support folders Change By: Radi Berkovich Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204620.1581933005000.491.1582786860207%40Atlassian.JIRA.
[JIRA] (JENKINS-61247) Partial Login Issue with Crowd2 plugin.
Title: Message Title Ravindra Kumar created an issue Jenkins / JENKINS-61247 Partial Login Issue with Crowd2 plugin. Issue Type: Bug Assignee: Martin Spielmann Components: crowd2-plugin Created: 2020-02-27 06:45 Environment: Production Labels: jenkins crowd2 Priority: Blocker Reporter: Ravindra Kumar Hi Team, we have 2 Jenkins authenticating from same crowd server via Crowd 2 plugin. lets say jenkins1 and jenkins2. Jenkins2 is having login issue with some of the users. but at same time these user can login to the Jenkins1. The users facing issue are already members of group on crowd side that are allowed on jenkins. When trying to add these user directly in project matrix user, it is strike through and say user not found. Note: Crowd is using LDAP connection for syncing user directory. Add Comment
[JIRA] (JENKINS-61220) plugin version 2.1.0 can not parse output.xml any more
Title: Message Title Aleksi Simell updated JENKINS-61220 Fix released as 2.1.1 (will be available in update-center in several hours). Jenkins / JENKINS-61220 plugin version 2.1.0 can not parse output.xml any more Change By: Aleksi Simell Status: Fixed but Unreleased Resolved Released As: 2.1.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-61220) plugin version 2.1.0 can not parse output.xml any more
Title: Message Title Aleksi Simell updated JENKINS-61220 Jenkins / JENKINS-61220 plugin version 2.1.0 can not parse output.xml any more Change By: Aleksi Simell Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204774.1582633578000.465.1582785120439%40Atlassian.JIRA.
[JIRA] (JENKINS-61220) plugin version 2.1.0 can not parse output.xml any more
Title: Message Title Aleksi Simell updated JENKINS-61220 Jenkins / JENKINS-61220 plugin version 2.1.0 can not parse output.xml any more Change By: Aleksi Simell Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204774.1582633578000.461.1582784460379%40Atlassian.JIRA.
[JIRA] (TEST-198) bug occured
Title: Message Title Jagriti Singh created an issue test / TEST-198 bug occured Issue Type: Bug Assignee: Jagriti Singh Components: foo10 Created: 2020-02-27 05:34 Priority: Trivial Reporter: Jagriti Singh Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group
[JIRA] (JENKINS-61232) Getting :org.apache.commons.jelly.JellyTagException || Java heap issue
Title: Message Title Rupam Kumari commented on JENKINS-61232 Re: Getting :org.apache.commons.jelly.JellyTagException || Java heap issue .dmp, .phd, .trc files with huge size are getting created in folder where jenkins.war is kept. Also, I updated memory to 1024 instead of 256 in jenkins.xml as: -Xrs -Xmx1024m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080 --webroot="%BASE%\war" Still getting this exception. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204787.1582714853000.451.1582779420123%40Atlassian.JIRA.
[JIRA] (JENKINS-61246) withMaven is not picking mavenOpts: '-Xmx2048m'
Title: Message Title Sadguru Chikkam commented on JENKINS-61246 Re: withMaven is not picking mavenOpts: '-Xmx2048m' mavenOpts: '-Xmx2048m' is not being passed through withMaven Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204812.1582778807000.449.1582778940241%40Atlassian.JIRA.
[JIRA] (JENKINS-61246) withMaven is not picking mavenOpts: '-Xmx2048m'
Title: Message Title
Sadguru Chikkam created an issue
Jenkins / JENKINS-61246
withMaven is not picking mavenOpts: '-Xmx2048m'
Issue Type:
Bug
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2020-02-27 04:46
Priority:
Major
Reporter:
Sadguru Chikkam
I am getting an error "java.lang.OutOfMemoryError: Java heap space" when i am trying to build my code. And I am trying to pass JAVA_OPTIONS as below but for some reason it is not being passed. stage('Build') { steps { script { withMaven(mavenOpts: '-Xmx2048m') { sh("mvn package -DskipTests=true") } } } } Could see in the logs as below: [withMaven] Options: [] [withMaven] Available options: [withMaven] using JDK installation provided by the build agent $ /bin/sh -c "which mvn" [withMaven] using Maven installation provided by the build agent with executable /apps/pcehr/tools/apache-maven-3.3.9/bin/mvn [Pipeline] {
Add Comment
[JIRA] (JENKINS-50864) kubernetes-cli-plugin is not working.
Title: Message Title ipleten commented on JENKINS-50864 Re: kubernetes-cli-plugin is not working. On 1.8.2 issue has gone. Thank you! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.189987.1524057644000.445.1582777680206%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Olivier Lamy commented on JENKINS-60409 Re: Cloud Configuration Length Cap Raihaan Shouhell why? we do not need a Jetty release. Jetty has his own default (a bit low to prevent DOS attack and this probably will not be changed in Jetty code). But we can our own higher default here in Winstone. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203466.1575915955000.430.1582775460351%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Raihaan Shouhell commented on JENKINS-60409 Re: Cloud Configuration Length Cap https://github.com/eclipse/jetty.project/blob/65a22e5e809ecbd20b3475cd8644fdf7aa5e8490/jetty-server/src/main/java/org/eclipse/jetty/server/handler/ContextHandler.java#L148 This looks like where the default size is set. Even if we do bump it, we would require that jetty releases and we then update winstone. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203466.1575915955000.417.1582775100341%40Atlassian.JIRA.
[JIRA] (JENKINS-29206) Enhancement: put list of resources into a config-file
Title: Message Title Tobias Gruetzmacher closed an issue as Not A Defect I don't consider this in scope for this plugin. See the Configuration-as-Code plugin (which lockable-resources supports since 2.6) for a different approach. If you disagree, please reopen with additional arguments. Jenkins / JENKINS-29206 Enhancement: put list of resources into a config-file Change By: Tobias Gruetzmacher Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-29207) Enhancement: make recources addressable in build-flow plugin
Title: Message Title Tobias Gruetzmacher closed an issue as Won't Do Since build-flow is basically dead nowadays and replaced with pipeline, I don't think implementing this is worthwhile. Reopen/comment to disagree Jenkins / JENKINS-29207 Enhancement: make recources addressable in build-flow plugin Change By: Tobias Gruetzmacher Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-34960) Add a PauseAction to the node
Title: Message Title Tobias Gruetzmacher resolved as Fixed Should have been fixed in 2.2, see the old changelog. Jenkins / JENKINS-34960 Add a PauseAction to the node Change By: Tobias Gruetzmacher Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/lockable-resources-plugin/blob/master/CHANGELOG.old.md#release-22-2018-03-06 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60761) Plugin manager fails to load while navigating to the manage plugins view
Title: Message Title Mark Waite commented on JENKINS-60761 Re: Plugin manager fails to load while navigating to the manage plugins view Ashok K the original submitter says that restarting the server resolved the issue. Since restarting the server does not resolve it for you, I assume you have a different issue at the root of the problem. Can you duplicate the problem on another computer? Can you duplicate the problem on the same computer when running Jenkins with a different JENKINS_HOME directory (see the wiki for JENKINS_HOME setting)? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204021.1579001055000.399.1582757881369%40Atlassian.JIRA.
[JIRA] (JENKINS-54346) tee keeps file open
Title: Message Title Glenn Herbert commented on JENKINS-54346 Re: tee keeps file open Just running into this today. For I workaround i switched to use powershell as follows: bat ''' powershell "cmd /c '.\your.bat' | tee output.txt" ''' Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.195001.1540906753000.392.1582757881273%40Atlassian.JIRA.
[JIRA] (JENKINS-60761) Plugin manager fails to load while navigating to the manage plugins view
Title: Message Title Ashok K commented on JENKINS-60761 Re: Plugin manager fails to load while navigating to the manage plugins view Got the same _javascript_ error while trying to navigate to Manage Plugins as mentioned on the screenshots. Restarted both jenkins service and jenkins server multiple times. Current jenkins version is 2.222 .Also tried to with other versions but No luck. Has any concrete reason of this error been for previous issue ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204021.1579001055000.369.1582756920180%40Atlassian.JIRA.
[JIRA] (JENKINS-60761) Plugin manager fails to load while navigating to the manage plugins view
Title: Message Title Ashok K assigned an issue to Unassigned Jenkins / JENKINS-60761 Plugin manager fails to load while navigating to the manage plugins view Change By: Ashok K Assignee: Ashok Kafle Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204021.1579001055000.364.1582756320417%40Atlassian.JIRA.
[JIRA] (JENKINS-60761) Plugin manager fails to load while navigating to the manage plugins view
Title: Message Title Ashok K assigned an issue to Ashok K Jenkins / JENKINS-60761 Plugin manager fails to load while navigating to the manage plugins view Change By: Ashok K Assignee: Ashok Kafle Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204021.1579001055000.362.1582756320367%40Atlassian.JIRA.
[JIRA] (JENKINS-61242) No emails were triggered even with triggers set to Always
Title: Message Title Alex Earl commented on JENKINS-61242 Re: No emails were triggered even with triggers set to Always Did you add the project configuration before or after changing the defaults to Always? It's possible the job is setup with the default default trigger, which only occurs on failure. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204799.1582735388000.357.1582756140115%40Atlassian.JIRA.
[JIRA] (JENKINS-60761) Plugin manager fails to load while navigating to the manage plugins view
Title: Message Title Ashok Kafle reopened an issue Jenkins / JENKINS-60761 Plugin manager fails to load while navigating to the manage plugins view Change By: Ashok Kafle Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204021.1579001055000.352.1582756080408%40Atlassian.JIRA.
[JIRA] (JENKINS-34960) Add a PauseAction to the node
Title: Message Title Tobias Gruetzmacher assigned an issue to Tobias Gruetzmacher Jenkins / JENKINS-34960 Add a PauseAction to the node Change By: Tobias Gruetzmacher Assignee: Antonio Muñiz Tobias Gruetzmacher Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.170629.1463672374000.347.1582754760245%40Atlassian.JIRA.
[JIRA] (JENKINS-49623) Resource list stored in env variable empty when label is used in locking
Title: Message Title Tobias Gruetzmacher resolved as Fixed Should have been fixed in 2.7 Jenkins / JENKINS-49623 Resource list stored in env variable empty when label is used in locking Change By: Tobias Gruetzmacher Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/lockable-resources-plugin/releases/tag/lockable-resources-2.7 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-49623) Resource list stored in env variable empty when label is used in locking
Title: Message Title Tobias Gruetzmacher assigned an issue to Tobias Gruetzmacher Jenkins / JENKINS-49623 Resource list stored in env variable empty when label is used in locking Change By: Tobias Gruetzmacher Assignee: Tobias Gruetzmacher Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.188548.1519038537000.339.1582751940228%40Atlassian.JIRA.
[JIRA] (JENKINS-52638) Lockable Resource Plugin returns null resource after saving system configuration
Title: Message Title Tobias Gruetzmacher commented on JENKINS-52638 Re: Lockable Resource Plugin returns null resource after saving system configuration This is a problem with how the plugin is designed, since the plugin uses the same classes to manage configured and locked resources. The "easiest" solution would be to implement a custom save function which carefully merges "new" and "old" resources... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.192490.1531941372000.328.1582751520351%40Atlassian.JIRA.
[JIRA] (JENKINS-61242) No emails were triggered even with triggers set to Always
Title: Message Title NM OF commented on JENKINS-61242 Re: No emails were triggered even with triggers set to Always Hello Alex, I understand that I need to setup it on te job/project itself, which I did, I added the "Editable Email Notification" as a post build action but the email is never triggered, as you can se from the bit of log I posted it always says No emails were triggered. Please reopen this ticket, I am not saying I am not doing something wrong but I can't understand what, thw documentation or Google searches are not helping. Thanka Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204799.1582735388000.323.1582749720125%40Atlassian.JIRA.
[JIRA] (JENKINS-61245) Nested node blocks referring to the same node take two (or more) executors
Title: Message Title
Ryan Fenton-Garcia updated an issue
Jenkins / JENKINS-61245
Nested node blocks referring to the same node take two (or more) executors
Change By:
Ryan Fenton-Garcia
We have a pipeline wherein there is a function that needs to be called from multiple places, where the code within that function needs to run on the node "master". So we have:{code:java}def someFunction() { // maybe do some stuff node("master") {// definitely do some stuff that needs master }}{code}Now what we have recently found out, is that if/when this function is called from code already running on master it will actually lock not just the current executor it is using on master but an additional executor as well. To further investigate this, we found out that even doing something as simple as...{code:java}node("master") { node("master") {sleep(600) }}{code} ...in a test job, actually locks two executors on master, if you have more than one executor, or hangs indefinitely "Waiting for next available executor on 'master'" even though the only thing using the only executor on master is already this block of code. I'd suspect that this isn't just the case for master, but actually the case for any code specifying that it needs run on a label that it's possible already running on. I think a possible work around for code that needs to execute in this fashion is to write all these blocks of code like this:{code:java}if ("${NODE_NAME}" != "master") { node("master") {// do my code }} else { // do my code}{code}Or else wrap this into a closure of some sort of it's own... and call nodeIfNotAlreadyOn("master") instead or something... but this isn't exactly very nice, and not exactly the behaviour I was initially expecting. Furthermore, I honestly can't think of a use case where you would ever want to use two of the exact same label on an explicitly different executor at the exact same time (especially when the first executor with that label is only going to be locked waiting for the code on the second executor to execute), which is why this really feels like more of a bug than anything else to me.
Add Comment
[JIRA] (JENKINS-61245) Nested node blocks referring to the same node take two (or more) executors
Title: Message Title
Ryan Fenton-Garcia updated an issue
Jenkins / JENKINS-61245
Nested node blocks referring to the same node take two (or more) executors
Change By:
Ryan Fenton-Garcia
We have a pipeline wherein there is a function that needs to be called from multiple places, where the code within that function needs to run on the node "master". So we have:{code:java}def someFunction() { // maybe do some stuff node("master") {// definitely do some stuff that needs master }}{code}Now what we have recently found out , is that if/when this function is called from code already running on master it will actually lock not just the current executor it is using on master but an additional executor as well. To further investigate this, we found out that even doing something as simple as...{code:java}node("master") { node("master") {sleep(600) }}{code} ...in a test job, actually locks two executors on master, if you have more than one executor, or hangs indefinitely "Waiting for next available executor on 'master'" even though the only thing using the only executor on master is already this block of code. I'd suspect this isn't just the case for master, but actually the case for any code specifying that it needs run on a label that it's possible already running on. I think a possible work around for code that needs to execute in this fashion is to write all these blocks of code like this:{code:java}if ("${NODE_NAME}" != "master") { node("master") {// do my code }} else { // do my code}{code}Or else wrap this into a closure of some sort of it's own... and call nodeIfNotAlreadyOn("master") instead or something... but this isn't exactly very nice, and not exactly the behaviour I was initially expecting.
Add Comment
[JIRA] (JENKINS-61245) Nested node blocks referring to the same node take two (or more) executors
Title: Message Title
Ryan Fenton-Garcia updated an issue
Jenkins / JENKINS-61245
Nested node blocks referring to the same node take two (or more) executors
Change By:
Ryan Fenton-Garcia
We have a pipeline wherein there is a function that needs to be called from multiple places, where the code within that function needs to run on the node "master". So we have:{code:java}def someFunction () { // maybe do some stuff node("master") {// definitely do the some stuff that needs master }}{code}Now what we recently found out is that if/when this function is called from code already running on master it will actually lock not just the current executor it is using on master but an additional executor as well. To further investigate this, we found out that even doing something as simple as...{code:java}node("master") { node("master") {sleep(600) }}{code} ...in a test job, actually locks two executors on master, if you have more than one executor, or hangs indefinitely "Waiting for next available executor on 'master'" even though the only thing using the only executor on master is already this block of code. I'd suspect this isn't just the case for master, but actually the case for any code specifying that it needs run on a label that it's possible already running on. I think a possible work around for code that needs to execute in this fashion is to write all these blocks of code like this:{code:java}if ("${NODE_NAME}" != "master") { node("master") {// do my code }} else { // do my code}{code}Or else wrap this into a closure of some sort of it's own... and call nodeIfNotAlreadyOn("master") instead or something... but this isn't exactly very nice, and not exactly the behaviour I was initially expecting.
Add Comment
[JIRA] (JENKINS-61245) Nested node blocks referring to the same node take two (or more) executors
Title: Message Title
Ryan Fenton-Garcia updated an issue
Jenkins / JENKINS-61245
Nested node blocks referring to the same node take two (or more) executors
Change By:
Ryan Fenton-Garcia
We have a pipeline wherein there is a function that needs to be called from multiple places, where the code within that function needs to run on the node "master". So we have:{code:java}def someFunction { node("master") {// do the stuff that needs master }}{code}Now what we recently found out is that if/when this function is called from code already running on master it will actually lock not just the current executor it is using on master but an additional executor as well. To further investigate this, we found out that even doing something as simple as...{code:java}node("master") { node("master") {sleep(600) }}{code} ...in a test job, actually locks two executors on master, if you have more than one executor, or hangs indefinitely "Waiting for next available executor on 'master'" even though the only thing using the only executor on master is already this block of code. I'd suspect this isn't just the case for master, but actually the case for any code specifying that it needs run on a label that it's possible already running on. I think a possible work around for code that needs to execute in this fashion is to write all these blocks of code like this:{code:java}if ("${NODE_NAME}" != "master") { node("master") {// do my code }} else { // do my code}{code}Or else wrap this into a closure of some sort of it's own... and call nodeIfNotAlreadyOn("master") instead or something. But .. but this isn't exactly very nice, and not exactly the behaviour I was initially expecting.
Add Comment
[JIRA] (JENKINS-61245) Nested node blocks referring to the same node take two (or more) executors
Title: Message Title
Ryan Fenton-Garcia updated an issue
Jenkins / JENKINS-61245
Nested node blocks referring to the same node take two (or more) executors
Change By:
Ryan Fenton-Garcia
We have a pipeline wherein there is a function that has needs to may need to be called from multiple places . The , where the code in this within that function needs to run on the node " master " . So we have:{code:java}def someFunction { node("master") {// do the stuff that needs master }}{code}Now what we recently found out is that if/when this function is called from code already running on master it will actually lock not just the current executor it is using on master but an additional executor as well. To further investigate this, we found out that even doing something as simple as...{code:java}node("master") { node("master") {sleep(600) }}{code} ...in a test job, actually locks two executors on master, if you have more than one executor, or hangs indefinitely "Waiting for next available executor on 'master'" even though the only thing using the only executor on master is already this block of code. I'd suspect this isn't just the case for master, but actually the case for any code specifying that it needs run on a label that it's possible already running on. I think a possible work around for code that needs to execute in this fashion is to write all these blocks of code like this:{code:java}if ("${NODE_NAME}" != "master") { node("master") {// do my code }} else { // do my code}{code}Or else wrap this into a closure of some sort of it's own... and call nodeIfNotAlreadyOn("master") instead or something.But this isn't exactly very nice, and not exactly the behaviour I was initially expecting.
Add Comment
[JIRA] (JENKINS-61245) Nested node blocks referring to the same node take two (or more) executors
Title: Message Title
Ryan Fenton-Garcia created an issue
Jenkins / JENKINS-61245
Nested node blocks referring to the same node take two (or more) executors
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-02-26 20:07
Environment:
Jenkins 2.204.2 Pipeline 2.6 Windows Server 2016
Labels:
scripted pipeline
Priority:
Minor
Reporter:
Ryan Fenton-Garcia
We have a pipeline wherein there is a function that has to may need to be called from multiple places. The code in this function needs to run on master. So we have:
def someFunction {
node("master") {
// do the stuff that needs master
}
}
Now what we recently found out is that if/when this function is called from code already running on master it will actually lock not just the current executor it is using on master but an additional executor as well. To further investigate this, we found out that even doing something as simple as...
node("master") {
node("master") {
sleep(600)
}
}
[JIRA] (JENKINS-61244) Jira issue: getting error while assigning issue to a assginee
Title: Message Title
indu ch created an issue
Jenkins / JENKINS-61244
Jira issue: getting error while assigning issue to a assginee
Issue Type:
Task
Assignee:
Unassigned
Components:
jira-plugin
Created:
2020-02-26 20:05
Priority:
Major
Reporter:
indu ch
Hello everyone, I am implementing Jira plugin into jenkins. Based on below link and guideline i am able to create a bug from jenkins in Jira (https://jenkinsci.github.io/jira-steps-plugin/steps/issue/jira_assign_issue/), but i am facing issues while assigning to a person that bug in jira. here it is i am using following command to assign to a person jiraAssignIssue site: 'LOCAL', idOrKey: 'TEST-1', userName: 'Jenkins' here is the error i am getting Error Message: {"errorMessages":["'accountId' must be the only user identifying query parameter in GDPR strict mode."],"errors":{}} Please help me out if anyone knows. I appreciate your help. Thanks Indu {{}}
Add Comment
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Very nice. Using jdk-8 server / agent I can now use an AWS ALB for all Jenkins server ingress server-UI / CLI / Agents. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204765.1582603216000.309.1582747320231%40Atlassian.JIRA.
[JIRA] (JENKINS-47051) Per step "View as plain text" not working
Title: Message Title Basil Crow updated JENKINS-47051 Per Steven's comment I am marking this as resolved in 1.8.10. Kayvan Sylvan, if you are still experiencing problems, could you please open a new issue with more details? Jenkins / JENKINS-47051 Per step "View as plain text" not working Change By: Basil Crow Status: Fixed but Unreleased Resolved Released As: 1.8.10 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-47051) Per step "View as plain text" not working
Title: Message Title Basil Crow updated JENKINS-47051 Jenkins / JENKINS-47051 Per step "View as plain text" not working Change By: Basil Crow Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.185441.1506080644000.296.1582745820568%40Atlassian.JIRA.
[JIRA] (JENKINS-12512) Text Finder plugin help could be more informative
Title: Message Title Basil Crow updated JENKINS-12512 Released in Text Finder 1.12. Jenkins / JENKINS-12512 Text Finder plugin help could be more informative Change By: Basil Crow Status: Fixed but Unreleased Resolved Assignee: drlewis Basil Crow Released As: https://github.com/jenkinsci/text-finder-plugin/pull/28 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) --
[JIRA] (JENKINS-5228) TextFinder should be able to set the build description
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-5228 TextFinder should be able to set the build description Change By: Basil Crow Assignee: drlewis Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.135317.1263196332000.280.1582745460429%40Atlassian.JIRA.
[JIRA] (JENKINS-10126) Text-finder plugin incompatible with timestamper plugin
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-10126 Text-finder plugin incompatible with timestamper plugin Change By: Basil Crow Assignee: drlewis Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.140314.1309252021000.288.1582745460535%40Atlassian.JIRA.
[JIRA] (JENKINS-7829) Textfinder plugin fails intermittently
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-7829 Textfinder plugin fails intermittently Change By: Basil Crow Assignee: drlewis Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.137930.1287405108000.285.1582745460491%40Atlassian.JIRA.
[JIRA] (JENKINS-31693) Jenkins Text Finder is waiting for a checkpoint
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-31693 Jenkins Text Finder is waiting for a checkpoint Change By: Basil Crow Assignee: drlewis Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.166623.1448048163000.271.1582745400348%40Atlassian.JIRA.
[JIRA] (JENKINS-4529) Problem with Text-finder and Warnings plugin order execution
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-4529 Problem with Text-finder and Warnings plugin order execution Change By: Basil Crow Assignee: drlewis Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.134602.1253691227000.277.1582745400424%40Atlassian.JIRA.
[JIRA] (JENKINS-3160) http 403 on config page with matrix based security
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-3160 http 403 on config page with matrix based security Change By: Basil Crow Assignee: drlewis Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.133233.1235628111000.274.1582745400385%40Atlassian.JIRA.
[JIRA] (JENKINS-42944) Text Finder does not evaluate user defined axis of matrix build variable in path
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-42944 Text Finder does not evaluate user defined axis of matrix build variable in path Change By: Basil Crow Assignee: drlewis Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.179955.1490029342000.268.1582745340177%40Atlassian.JIRA.
[JIRA] (JENKINS-57080) Cannot hide Pipeline output when using Timestamps
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-57080 Cannot hide Pipeline output when using Timestamps Change By: Basil Crow Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.198823.100703000.262.1582745220602%40Atlassian.JIRA.
[JIRA] (JENKINS-57163) Using timestamps prevents parallel thread's catch block from executing sleep
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-57163 Using timestamps prevents parallel thread's catch block from executing sleep Change By: Basil Crow Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.198913.155606902.259.1582745220510%40Atlassian.JIRA.
[JIRA] (JENKINS-55908) Xvfb does not work when wrap([$class: 'Xvfb']) is defined inside timestamps
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-55908 Xvfb does not work when wrap([$class: 'Xvfb']) is defined inside timestamps Change By: Basil Crow Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.197310.1549016484000.265.1582745280181%40Atlassian.JIRA.
[JIRA] (JENKINS-57212) Global setting to change the default for browser time zone
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-57212 Global setting to change the default for browser time zone Change By: Basil Crow Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.198969.1556525294000.255.1582745220426%40Atlassian.JIRA.
[JIRA] (JENKINS-58087) Text Finder Plugin Console log results in wrong Failure Cause
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-58087 Text Finder Plugin Console log results in wrong Failure Cause Change By: Basil Crow Assignee: Tomas Westling Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.200128.1560924617000.249.1582745160323%40Atlassian.JIRA.
[JIRA] (JENKINS-57809) Default timestamp formats should not be boldfaced
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-57809 Default timestamp formats should not be boldfaced Change By: Basil Crow Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.199760.1559396337000.252.1582745160366%40Atlassian.JIRA.
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title Basil Crow updated JENKINS-59636 Fixed as of jenkinsci/timestamper-plugin#52 (and previous dependent changes). Jenkins / JENKINS-59636 timestamper shows wrong time on [View as plain text] link Change By: Basil Crow Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-59730) text-finder sets whole matrix job to "not built" even if only one configuration matched
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-59730 text-finder sets whole matrix job to "not built" even if only one configuration matched Change By: Basil Crow Assignee: Basil Crow Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202448.1570712752000.242.1582744140136%40Atlassian.JIRA.
[JIRA] (JENKINS-60889) Add example global config to Readme and wiki pages
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-60889 Add example global config to Readme and wiki pages Change By: Basil Crow Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204277.1580207843000.230.1582744080851%40Atlassian.JIRA.
[JIRA] (JENKINS-60726) Print two lines to each line if use Timestamper and Color Ansi Console Output
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-60726 Print two lines to each line if use Timestamper and Color Ansi Console Output Change By: Basil Crow Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203975.1578651011000.236.1582744080932%40Atlassian.JIRA.
[JIRA] (JENKINS-60942) swarm plugin requires anonymous/overall/read if not started with user/password
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-60942 swarm plugin requires anonymous/overall/read if not started with user/password Change By: Basil Crow Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204343.158066135.226.1582744080797%40Atlassian.JIRA.
[JIRA] (JENKINS-60672) Timestamper plugin causes chrome frozen when there are too many console logs
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-60672 Timestamper plugin causes chrome frozen when there are too many console logs Change By: Basil Crow Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203915.1578386867000.239.1582744080983%40Atlassian.JIRA.
[JIRA] (JENKINS-60888) allProjects flag in config file not respected
Title: Message Title Basil Crow assigned an issue to Unassigned Jenkins / JENKINS-60888 allProjects flag in config file not respected Change By: Basil Crow Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204276.1580207457000.233.1582744080885%40Atlassian.JIRA.
[JIRA] (JENKINS-40501) Reactive Reference Parameter not working with "List Subversion Tags" parameter
Title: Message Title Hoa Nguyen commented on JENKINS-40501 Re: Reactive Reference Parameter not working with "List Subversion Tags" parameter Hi was looking into it as I want a solution to this. I notice that when looking at the Subversion tag parameter field, it is getting the value before the field pulls data from SVN for list of tags. So probably why it gets an empty string. I think if it waited after the load, it would work. I'll see if I can play with it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.177176.1481881922000.200.1582742400231%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Stuart Rowe edited a comment on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I've been looking into this as well. What I've found so far: - The downstream runs have an associated [BuildUpstreamNodeAction|https://github.com/jenkinsci/pipeline-build-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildUpstreamNodeAction.java] contributed by the build step. - The BuildUpstreamNodeAction action has an upstreamNodeId pointing back to the build step that triggered the downstream run. - This [DownstreamJobListener|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/listeners/DownstreamJobListener.java] adds a [NodeDownstreamBuildAction|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/listeners/NodeDownstreamBuildAction.java] to the node pointed to by the upstreamNodeId . - This upstreamNodeId doesn't match the id of the node typically selected when viewing the Blue Ocean pipeline graph (that node is typically a stage or parallel branch node) - There's code in [PipelineNodeGraphVisitor.java|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/rest/impl/pipeline/PipelineNodeGraphVisitor.java] that accumulates actions from nodes within a branch or stage and then adds them to the node for that branch or stage. I believe this is the source of the issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Stuart Rowe commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I've been looking into this as well. What I've found so far: The downstream runs have an associated BuildUpstreamNodeAction contributed by the build step. The BuildUpstreamNodeAction action has an upstreamNodeId pointing back to the build step that triggered the downstream run. This upstreamNodeId doesn't match the id of the node typically selected when viewing the Blue Ocean pipeline graph (that node is typically a stage or parallel branch node) There's code in PipelineNodeGraphVisitor.java that accumulates actions from nodes within a branch or stage and then adds them to the node for that branch or stage. I believe this is the source of the issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.174511.1474269026000.30.1582739821725%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Matt Sicker commented on JENKINS-61224 Re: "Monitors" terminology should not be used in GUI Warnings could work, too. Or if someone can think of a good butler pun: I'd love that. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204778.158264254.28.1582739460281%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Jeff Thompson commented on JENKINS-61224 Re: "Monitors" terminology should not be used in GUI I've had the same concerns with naming on these things before. The API name isn't a good term for users, but it got picked up and used in UI a number of places. I think the best term is "alert". I don't have much of an opinion on Jesse's latter suggestion of removing the word entirely. I guess I would have a slight, soft preference for retaining text with better wording. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204778.158264254.21.1582739160227%40Atlassian.JIRA.
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title William Brode commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs I and another colleague have installed 1.10.10 and the triggering still seems to be working as expected for us. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204686.158215634.14.1582738980427%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Matt Sicker commented on JENKINS-61224 Re: "Monitors" terminology should not be used in GUI Using the word "alert" instead of "monitor" might work. Or there might be some vocabulary that can be lifted from observability frameworks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204778.158264254.17.1582739040446%40Atlassian.JIRA.
[JIRA] (JENKINS-61242) No emails were triggered even with triggers set to Always
Title: Message Title Alex Earl closed an issue as Not A Defect You showed an image from the global configuration for the plugin which specifies the default set of triggers enabled when you add the plugin to a job. In order for emails to occur, you need to configure the plugin in the job itself. Jenkins / JENKINS-61242 No emails were triggered even with triggers set to Always Change By: Alex Earl Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title Adam Butler commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs Hi Matthew Smeeth apologies if this has caused a regression. I'm unable to reproduce the issue on our instance of Jenkins (version 2.190.3) and am not in a position to upgrade it at the moment to do further testing due to it being a corporate instance, so it's going to be difficult for me to come up with alternatives at this time. I think that your only option is to back this change out for the time being. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204686.158215634.2.1582738386550%40Atlassian.JIRA.
[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 Sergio Merino reopened an issue I am reopening the ticket because I am having this issue and He Bihong is right. You can change the max requests per host, but given that the default max requests is 64, there is no way of going over that Jenkins / JENKINS-58463 Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" Change By: Sergio Merino Resolution: Duplicate Status: Resolved Reopened Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61243) Artifactory plugin to fall active-choice plugin
Title: Message Title Владислав Ненашев created an issue Jenkins / JENKINS-61243 Artifactory plugin to fall active-choice plugin Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin, artifactory-plugin Created: 2020-02-26 17:03 Priority: Critical Reporter: Владислав Ненашев Active-choice plugin steps ceased to be executed, a trace was displayed in the jenkins.log, after removing the Artifactory plugin, the active-choice plugin was restored SEVERE: Error executing script for dynamic parameter java.lang.NullPointerException at org.jfrog.hudson.gradle.ArtifactoryGradleConfigurator.getReleaseRepositories(ArtifactoryGradleConfigurator.java:626) at sun.reflect.GeneratedMethodAccessor2235.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:193) at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:178) at org.biouno.unochoice.util.Utils.read(Utils.java:343) at org.biouno.unochoice.util.Utils.addParameterDefinitionsTo(Utils.java:323) at org.biouno.unochoice.util.Utils.getBuildWrapperParameterDefinitions(Utils.java:302) at org.biouno.unochoice.util.Utils.isParameterDefinitionOf(Utils.java:227) at org.biouno.unochoice.util.Utils.findProjectByParameterUUID(Utils.java:209) at org.biouno.unochoice.AbstractScriptableParameter.getHelperParameters(AbstractScriptableParameter.java:189) at org.biouno.unochoice.AbstractScriptableParameter.eval(AbstractScriptableParameter.java:257) at
[JIRA] (JENKINS-60653) Don't treat requested and dependency plugins the same for download
Title: Message Title Ganghui Hu assigned an issue to Natasha Stopa Jenkins / JENKINS-60653 Don't treat requested and dependency plugins the same for download Change By: Ganghui Hu Assignee: leemeador Natasha Stopa Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203895.1578334517000.7363.1582736461316%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Luis Roalter commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Sometimes it works. but not always. For some reasons the NodeDownstreamBuildAction is missing when using the api /blue/rest/organizations/jenkins/pipelines/ When going closer into /blue/rest/organizations/jenkins/pipelines//runs/x/nodes/y/ the information is missing in this endpoint too. Funny fact, I've debugged it with the Script console by replaying the code from https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/listeners/DownstreamJobListener.java. This works and all the triggered builds are there. But for me it's too complex to dig into the blue-ocean rest and debug there. Any suggestion from anyone how to debug it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174511.1474269026000.7295.1582736161375%40Atlassian.JIRA.
[JIRA] (JENKINS-61242) No emails were triggered even with triggers set to Always
Title: Message Title
NM OF updated an issue
Jenkins / JENKINS-61242
No emails were triggered even with triggers set to Always
Change By:
NM OF
I have recently installed the Email Extension Plugin on where I have setup the triggers to always. !image-2020-02-26-16-44-55-177.png! However it always says the following:{color:#e9eded}*16:42:03* {color}Checking for post-build{color:#e9eded}*16:42:03* {color}Performing post-build step{color:#e9eded}*16:42:03* {color}Checking if email needs to be generated{color:#e9eded}*16:42:03* {color}No emails were triggered. I don't understand why of this is a bug. Thank you advance.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-61242) No emails were triggered even with triggers set to Always
Title: Message Title NM OF updated an issue Jenkins / JENKINS-61242 No emails were triggered even with triggers set to Always Change By: NM OF Attachment: image-2020-02-26-16-44-55-177.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204799.1582735388000.7291.1582735500182%40Atlassian.JIRA.
[JIRA] (JENKINS-61242) No emails were triggered even with triggers set to Always
Title: Message Title NM OF created an issue Jenkins / JENKINS-61242 No emails were triggered even with triggers set to Always Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 2020-02-26 16:43 Environment: DEV or PROD Priority: Minor Reporter: NM OF I have recently installed the Email Extension Plugin on where I have setup the triggers to always. However it always says the following: 16:42:03 Checking for post-build16:42:03 Performing post-build step16:42:03 Checking if email needs to be generated16:42:03 No emails were triggered. I don't understand why of this is a bug. Thank you advance. Add Comment
[JIRA] (JENKINS-61241) After upgrading to version 2.222 jobs are stuck in the queue
Title: Message Title Duane Morris created an issue Jenkins / JENKINS-61241 After upgrading to version 2.222 jobs are stuck in the queue Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-02-26 16:35 Environment: windows server 2016 openjdk 8 java Priority: Major Reporter: Duane Morris Yesterday we upgraded to version 2.222 and when I came in this morning. All the jobs that should have run overnight were stuck in the job queue. I rolled back to version 2.221 and everything is fine again. Add Comment
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title Basil Crow commented on JENKINS-59636 Re: timestamper shows wrong time on [View as plain text] link which version of the plugin stands for 52? jenkinsci/timestamper-plugin#52 has been merged but not yet released. I am planning to release a new version of Timestamper soon, at which point I will update this bug. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202318.1570086045000.7284.1582734660169%40Atlassian.JIRA.
[JIRA] (JENKINS-61134) Unable to select all plugins for update
Title: Message Title Allan C commented on JENKINS-61134 Re: Unable to select all plugins for update I think it might be more useful to add these to the floating pane perhaps at the bottom? Daniel Beck Thank you for the idea. I agree that moving the Select before "Download now and install after restart" button may make it more obvious. I will try looking into it. Do you know about any documentation about the core UI? Or should I reach out to someone? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204656.1582055073000.7282.1582733520182%40Atlassian.JIRA.
[JIRA] (JENKINS-60968) role-strategy-Submit fails with version 2.209. Not able to save new user.
Title: Message Title brian odriscoll commented on JENKINS-60968 Re: role-strategy-Submit fails with version 2.209. Not able to save new user. Hi Oleg, So we used the workaround advised in JENKINS-60409. First our senior picked it up to 400k but it didn't fix the issue.- (still too small for the POST size we are doing), then picked it up to 1M and it began to work properly. Kind Regards Brian Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204431.1580889821000.7267.1582733340533%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title brian odriscoll commented on JENKINS-60409 Re: Cloud Configuration Length Cap Hi Oleg, So we used the workaround advised in JENKINS-60409. First our senior picked it up to 400k but it didn't fix the issue.- (still too small for the POST size we are doing), then picked it up to 1M and it began to work properly. Kind Regards Brian Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203466.1575915955000.7270.1582733340631%40Atlassian.JIRA.
[JIRA] (JENKINS-61134) Unable to select all plugins for update
Title: Message Title Daniel Beck commented on JENKINS-61134 Re: Unable to select all plugins for update Would it be nice to add a "select all" checkbox on top of the menu though? Potentially nontrivial from a UI standpoint, given how the tabs flow into the table header (I'm not much of a designer anyway). I think it might be more useful to add these to the floating pane perhaps at the bottom? If you want to try your hand at a proposal here, go for it Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204656.1582055073000.7263.1582732560181%40Atlassian.JIRA.
[JIRA] (JENKINS-60985) org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9 is not serializable causing hudson.remoting.RemotingSystemException
Title: Message Title
Andrew Potter updated an issue
Jenkins / JENKINS-60985
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9 is not serializable causing hudson.remoting.RemotingSystemException
Change By:
Andrew Potter
{code:java}ERROR: Processing failed due to a bug in the code. Please report this to the issue tracker (https://jenkins.io/redirect/report-an-issue).hudson.remoting.RemotingSystemException: java.lang.ClassCastException: class org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9 is returned from public abstract org.jenkinsci.plugins.gitclient.CheckoutCommand org.jenkinsci.plugins.gitclient.GitClient.checkout() on class hudson.plugins.git.GitAPI but it's not serializable at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:938) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:905) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:857) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117) at java.lang.Thread.run(Thread.java:745) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from vtplat-jenkinsdockerslave01.int.dealer.com/10.12.4.53:55335 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:951) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285) at com.sun.proxy.$Proxy99.checkout(Unknown Source) at org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkout(RemoteGitImpl.java:309) at org.jfrog.hudson.release.scm.git.GitManager.checkoutBranch(GitManager.java:72) at org.jfrog.hudson.release.scm.git.GitCoordinator.beforeReleaseVersionChange(GitCoordinator.java:93) at org.jfrog.hudson.release.maven.MavenReleaseWrapper.setUp(MavenReleaseWrapper.java:178) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:667) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1853) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)Caused by: java.lang.ClassCastException: class org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9 is returned from public abstract org.jenkinsci.plugins.gitclient.CheckoutCommand
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title Matthew Smeeth commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs I have just checked this. In P4Hook we use an anonymous thread to run the job. If we call getAllItems(to find the list of Jobs) inside the thread it seems to ignore your credentials and return no jobs. We may need to back out https://github.com/jenkinsci/p4-plugin/pull/116/files to fix this. Adam Butler, are there alternatives for this fix? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204686.158215634.7250.1582732200420%40Atlassian.JIRA.
[JIRA] (JENKINS-12548) Read-only system configuration browsing
Title: Message Title Tim Jacomb commented on JENKINS-12548 Re: Read-only system configuration browsing yeah not useful at all Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142914.1327605395000.7252.1582732200484%40Atlassian.JIRA.
[JIRA] (JENKINS-12548) Read-only system configuration browsing
Title: Message Title Daniel Beck commented on JENKINS-12548 Re: Read-only system configuration browsing Someone reported this issue in the changelog feedback, but it's unclear what's wrong. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142914.1327605395000.7240.1582732082312%40Atlassian.JIRA.
[JIRA] (JENKINS-61235) User/people disclosure
Title: Message Title Christian Zagrodnick commented on JENKINS-61235 Re: User/people disclosure Right, that's JENKINS-18884. Didn't find that before. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204790.1582723332000.7237.1582731480863%40Atlassian.JIRA.
[JIRA] (JENKINS-61134) Unable to select all plugins for update
Title: Message Title Allan C closed an issue as Not A Defect Jenkins / JENKINS-61134 Unable to select all plugins for update Change By: Allan C Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Taylor Nelson commented on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command I pulled the latest changes from your pull request 213 and built the plugin. Unfortunately it did not work. It looks like you merged David France's changes into your PR (David's changes solved the freezing problem for me before these GDPR problems) so I'm not sure why it's not working now. Maybe 213 is still using the "default" apache dependencies instead of the custom Jira plugin ones? Here are the details before I reboot the server again: The BLOCKED thread: The WAITING thread: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.7233.1582731480710%40Atlassian.JIRA.
[JIRA] (JENKINS-61134) Unable to select all plugins for update
Title: Message Title Allan C updated an issue Jenkins / JENKINS-61134 Unable to select all plugins for update Change By: Allan C Attachment: image-2020-02-26-10-36-41-292.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204656.1582055073000.7223.1582731420393%40Atlassian.JIRA.
[JIRA] (JENKINS-61134) Unable to select all plugins for update
Title: Message Title Allan C commented on JENKINS-61134 Re: Unable to select all plugins for update Daniel Beck Appreciate the instruction and sorry for not checking carefully. I am attaching a screenshot and closing this issue. Would it be nice to add a "select all" checkbox on top of the menu though? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204656.1582055073000.7225.1582731420415%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Taylor Nelson updated an issue Jenkins / JENKINS-60536 Jenkins job hangs in Jira call after git rev-list command Change By: Taylor Nelson Attachment: image-2020-02-26-08-29-32-302.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.7200.1582731001446%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Taylor Nelson updated an issue Jenkins / JENKINS-60536 Jenkins job hangs in Jira call after git rev-list command Change By: Taylor Nelson Attachment: image-2020-02-26-08-29-08-607.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.7195.1582731001068%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Taylor Nelson updated an issue Jenkins / JENKINS-60536 Jenkins job hangs in Jira call after git rev-list command Change By: Taylor Nelson Attachment: image-2020-02-26-08-29-59-154.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.7216.1582731001675%40Atlassian.JIRA.
[JIRA] (JENKINS-61235) User/people disclosure
Title: Message Title Daniel Beck closed an issue as Not A Defect Has nothing to do with this plugin, it cannot offer options that don't exist. (And is a duplicate of an existing issue in the general case, no time to look right now.) Jenkins / JENKINS-61235 User/people disclosure Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Taylor Nelson updated an issue Jenkins / JENKINS-60536 Jenkins job hangs in Jira call after git rev-list command Change By: Taylor Nelson Attachment: image-2020-02-26-08-28-37-010.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.7179.1582730940372%40Atlassian.JIRA.
