[JIRA] (JENKINS-53320) Job fails because JiraSCMListener times out on too many changes
Title: Message Title Olivier Lamy commented on JENKINS-53320 Re: Job fails because JiraSCMListener times out on too many changes corresponding Jira plugin pr is here https://github.com/jenkinsci/jira-plugin/pull/166 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51716) Blueocean stuck in loading
Title: Message Title Aman Osman commented on JENKINS-51716 Re: Blueocean stuck in loading I updated to the latest BlueOcean (1.8.3) and it still happens Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51716) Blueocean stuck in loading
Title: Message Title
Aman Osman commented on JENKINS-51716
Re: Blueocean stuck in loading
blueocean-core-js.js:51793 Error: Must call ExtensionStore.init({ extensionData: array, typeInfoProvider: (type, cb) => ... }) first at ExtensionStore._initExtensionPointList (blueocean-core-js.js:996) at ExtensionStore.init (blueocean-core-js.js:821) at Object.init (blueocean-core-js.js:1543) at Object.execute (blueocean-core-js.js:52840) at APromise. (blueocean-core-js.js:51791) at Object.exports.make (blueocean-core-js.js:2834) at __$$$__exec (blueocean-core-js.js:51788) at __$$$__doBundleInit (blueocean-core-js.js:51865) at Function. (blueocean-core-js.js:51877) at doFulfill (blueocean-core-js.js:2860) (anonymous) @ blueocean-core-js.js:51793 blueocean-core-js.js:51870 Error initializing Jenkins _javascript_ bundle "blueocean-core-js" Error: Unexpected error executing startup module "../tstemp/js/bundleStartup.js": Error: Must call ExtensionStore.init({ extensionData: array, typeInfoProvider: (type, cb) => ... }) first at APromise. (blueocean-core-js.js:51794) at Object.exports.make (blueocean-core-js.js:2834) at __$$$__exec (blueocean-core-js.js:51788) at __$$$__doBundleInit (blueocean-core-js.js:51865) at Function. (blueocean-core-js.js:51877) at doFulfill (blueocean-core-js.js:2860) at APromise.onFulfilled (blueocean-core-js.js:2872) at Object.295.../tstemp/js/bundleStartup.js (blueocean-core-js.js:51876) at o (blueocean-core-js.js:1) at r (blueocean-core-js.js:1) __$$$__doBundleInit @ blueocean-core-js.js:51870 blueocean.js:2876 Module load failure: Timed out waiting on module 'mobx:mobx' to load. (anonymous) @ blueocean.js:2876 blueocean.js:2876 Module load failure: Timed out waiting on module 'jenkins-cd-js-extensions:jenkins-cd-js-extensions' to load. (anonymous) @ blueocean.js:2876 blueocean.js:2876 Module load failure: Timed out waiting on module 'jenkins-cd-blueocean-core-js:jenkins-cd-blueocean-core-js' to load.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You
[JIRA] (JENKINS-51716) Blueocean stuck in loading
Title: Message Title Aman Osman updated JENKINS-51716 Jenkins / JENKINS-51716 Blueocean stuck in loading Change By: Aman Osman Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53786) Flake8 found 0 issues, which should find some issues
Title: Message Title Ulli Hafner commented on JENKINS-53786 Re: Flake8 found 0 issues, which should find some issues In your pipeline you don't actually call flake8. The warnings plugin only scans the report files and visualizes the results. You need to start the tool on your own. Or is your pipeline just a snippet? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53786) Flake8 found 0 issues, which should find some issues
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-53786
Flake8 found 0 issues, which should find some issues
Change By:
Ulli Hafner
Jenkinsfile: {noformat} pipeline { agent anystages { stage('checkout'){ steps{ git branch: 'static_analysis', url: 'https://github.com/lioramilbaum/devopsloft.git' } } } post { always { recordIssues enabledForFailure: true, aggregatingResults : true, tools: [ [tool: [$class: 'Flake8'], pattern: '**/*.py'] ] } } } {noformat} Console log: {noformat} Started by user [jenkins|http://localhost:8080/user/jenkins]Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on [Jenkins|http://localhost:8080/computer/(master)/] in /var/jenkins_home/workspace/devopsloft[Pipeline] {[Pipeline] stage[Pipeline] { (checkout)[Pipeline] git > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url [https://github.com/lioramilbaum/devopsloft.git] # timeout=10Fetching upstream changes from [https://github.com/lioramilbaum/devopsloft.git] > git --version # timeout=10 > git fetch --tags --progress [https://github.com/lioramilbaum/devopsloft.git] +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/static_analysis^\{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/static_analysis^\{commit} # timeout=10Checking out Revision 61cff2d8f616561c1129acbcaa3439ce984d88d1 (refs/remotes/origin/static_analysis) > git config core.sparsecheckout # timeout=10 > git checkout -f 61cff2d8f616561c1129acbcaa3439ce984d88d1 > git branch -a -v --no-abbrev # timeout=10 > git branch -D static_analysis # timeout=10 > git checkout -b static_analysis 61cff2d8f616561c1129acbcaa3439ce984d88d1Commit message: "Experimenting Warnings plugin 5.0 beta2" > git rev-list --no-walk 61cff2d8f616561c1129acbcaa3439ce984d88d1 # timeout=10[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] recordIssues[Flake8] Searching for all files in '/var/jenkins_home/workspace/devopsloft' that match the pattern '**/*.py'[Flake8] -> found 4 files[Flake8] Successfully parsed file /var/jenkins_home/workspace/devopsloft/application.py[Flake8] -> found 0 issues (skipped 0 duplicates)[Flake8] Successfully parsed file /var/jenkins_home/workspace/devopsloft/config.py[Flake8] -> found 0 issues (skipped 0 duplicates)[Flake8] Successfully parsed file /var/jenkins_home/workspace/devopsloft/mod_auth/forms.py[Flake8] -> found 0 issues (skipped 0 duplicates)[Flake8] Successfully parsed file /var/jenkins_home/workspace/devopsloft/mod_auth/models.py[Flake8] -> found 0 issues (skipped 0 duplicates)[Flake8] No filter has been set, publishing all 0 issues[Flake8] Attaching ResultAction with ID 'flake8' to run 'devopsloft #4'.[Flake8] No valid reference build found that meets the criteria (IGNORE_JOB_RESULT - SUCCESSFUL_QUALITY_GATE)[Flake8] All reported issues will be considered outstanding[Flake8] No quality gates have been set - skipping[Flake8] Health report is disabled -
[JIRA] (JENKINS-53844) Each new HTTP query starts an infinite loop, burning CPU
Title: Message Title Attila Nagy updated an issue Jenkins / JENKINS-53844 Each new HTTP query starts an infinite loop, burning CPU Change By: Attila Nagy Not (yet) sure what has triggered this, but from now on every HTTP request to jenkins start a new never ending thread which burns CPU (one query: 100%, another one: 200% etc).After acquring a thread dump, all threads have the same signature (the web URL doesn't seem to matter, it's the same even with getting /threadDump):"Handling GET / from 1.2.3.4 : qtp849460928-26 View/index.jelly View/sidepanel.jelly NextExecutionsWidget/index.jelly" #26 prio=5 os_prio=0 tid=0x7f5258559800 nid=0x18b75 runnable [0x7f5228804000] java.lang.Thread.State: RUNNABLE at java.util.GregorianCalendar.computeTime(GregorianCalendar.java:2657) at java.util.Calendar.updateTime(Calendar.java:3393) at java.util.Calendar.getTimeInMillis(Calendar.java:1782) at java.util.Calendar.getMillisOf(Calendar.java:3410) at java.util.Calendar.compareTo(Calendar.java:2784) at hudson.scheduler.CronTab.ceil(CronTab.java:338) at hudson.scheduler.CronTab.ceil(CronTab.java:322) at hudson.plugins.nextexecutions.utils.NextExecutionsUtils.getNextBuild(NextExecutionsUtils.java:56) at hudson.plugins.nextexecutions.NextExecutionsWidget.getBuilds(NextExecutionsWidget.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:94) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at
[JIRA] (JENKINS-46253) Support subPath for volumes in the slave PodTemplates
Title: Message Title Steve Collins commented on JENKINS-46253 Re: Support subPath for volumes in the slave PodTemplates though its possible with yaml syntax but isn't that only on a per job config basis. If I have a number of caches I want to setup for all jobs (without changing each job to use a PodTemplate) and I would like to do that using subpaths in the UI config, I don't see an option but I'm new to this so I may be missing something. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53844) Each new HTTP query starts an infinite loop, burning CPU
Title: Message Title Attila Nagy created an issue Jenkins / JENKINS-53844 Each new HTTP query starts an infinite loop, burning CPU Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-09-29 19:33 Environment: Jenkins: 2.141 OS: Ubuntu 16.04.5 LTS OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-0ubuntu0.16.04.1-b13) Priority: Minor Reporter: Attila Nagy Not (yet) sure what has triggered this, but from now on every HTTP request to jenkins start a new never ending thread which burns CPU (one query: 100%, another one: 200% etc). After acquring a thread dump, all threads have the same signature (the web URL doesn't seem to matter, it's the same even with getting /threadDump): "Handling GET / from 1.2.3.4 : qtp849460928-26 View/index.jelly View/sidepanel.jelly NextExecutionsWidget/index.jelly" #26 prio=5 os_prio=0 tid=0x7f5258559800 nid=0x18b75 runnable [0x7f5228804000] java.lang.Thread.State: RUNNABLE at java.util.GregorianCalendar.computeTime(GregorianCalendar.java:2657) at java.util.Calendar.updateTime(Calendar.java:3393) at java.util.Calendar.getTimeInMillis(Calendar.java:1782) at java.util.Calendar.getMillisOf(Calendar.java:3410) at java.util.Calendar.compareTo(Calendar.java:2784) at hudson.scheduler.CronTab.ceil(CronTab.java:338) at hudson.scheduler.CronTab.ceil(CronTab.java:322) at hudson.plugins.nextexecutions.utils.NextExecutionsUtils.getNextBuild(NextExecutionsUtils.java:56) at hudson.plugins.nextexecutions.NextExecutionsWidget.getBuilds(NextExecutionsWidget.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at
[JIRA] (JENKINS-53834) rocketchat notifier plugin needing internet access to push notification to rocketchat
Title: Message Title Martin Reinhardt commented on JENKINS-53834 Re: rocketchat notifier plugin needing internet access to push notification to rocketchat I don't get the point. When you disable the proxy and both apps still try to use the proxy obviously the connection will fail, or? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53841) no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53841 no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep Change By: Oleg Nenashev Labels: newbie-friendly pipeline-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53320) Job fails because JiraSCMListener times out on too many changes
Title: Message Title Vivek Pandey commented on JENKINS-53320 Re: Job fails because JiraSCMListener times out on too many changes Olivier Lamy AFAIK, these listeners are async process, running in separate thread, a runtime exception can fail that listener, shouldn’t fail the build thought. cc: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53843) can you please send me "scm sync configuration" plugin installation for subversion i need step by step process
Title: Message Title gopi ksng created an issue Jenkins / JENKINS-53843 can you please send me "scm sync configuration" plugin installation for subversion i need step by step process Issue Type: Task Assignee: Hiroshi Ujishi Components: scm-sync-configuration-plugin Created: 2018-09-29 16:04 Environment: i am using subversion can you please give me an idea how to do this step by step process Priority: Critical Reporter: gopi ksng 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
[JIRA] (JENKINS-53842) Upgrade Maven version used for Blue Ocean CI
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53842
Upgrade Maven version used for Blue Ocean CI
Change By:
Baptiste Mathus
I just filed a [PR|https://github.com/jenkinsci/blueocean-plugin/pull/1818] to be able to publish incremental releases in Blue Ocean, but got an error showing that https://ci.blueocean.io/ actually runs Maven 3.3.3{noformat}[INFO] --- maven-enforcer-plugin:3.0.0-M1:display-info (display-info) @ jenkins-design-language --- [INFO] Maven Version: 3.3.3 [INFO] JDK Version: 1.8.0_181 normalized as: 1.8.0-181 [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 4.4.0-1048-aws [INFO] [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @ jenkins-design-language --- [WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion failed with message: 3.5.0+ required to use Incrementals. {noformat}I would be nice to upgrade both for making it compatible with Incrementals, and well also in general because upgrading is a good thing nay? :-)Thanks!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-53842) Upgrade Maven version used for Blue Ocean CI
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53842 Upgrade Maven version used for Blue Ocean CI Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-09-29 12:56 Labels: technical-debt evergreen-triggered Priority: Minor Reporter: Baptiste Mathus I just filed a PR to be able to publish incremental releases in Blue Ocean, but got an error showing that https://ci.blueocean.io/ actually runs Maven 3.3.3 [INFO] --- maven-enforcer-plugin:3.0.0-M1:display-info (display-info) @ jenkins-design-language --- [INFO] Maven Version: 3.3.3 [INFO] JDK Version: 1.8.0_181 normalized as: 1.8.0-181 [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 4.4.0-1048-aws [INFO] [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @ jenkins-design-language --- [WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion failed with message: 3.5.0+ required to use Incrementals. I would be nice to upgrade both for making it compatible with Incrementals, and well also in general because upgrading is a good thing nay? Thanks!
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Nicolas De Loof commented on JENKINS-36776 Re: Support Windows Server Containers I just got a PR merged on this plugin, I don't think that makes me a maintainer, does it ? I have no experience with windows container, and no personal interest for them, so won't be a great support for such a feature - whenever I fully understand the interest for others. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53743) Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse.
Title: Message Title Jie Shen commented on JENKINS-53743 Re: Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse. Upgrade azure-commons-plugin to version 0.2.8 when it is available should fix this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53743) Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse.
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-53743 Azure-VM-Agents: LinkageError: loader constraint violation: when resolving method "com.nimbusds.openid.connect.sdk.OIDCAccessTokenResponse. Change By: Jie Shen Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53841) no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep
Title: Message Title suren pi created an issue Jenkins / JENKINS-53841 no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep Issue Type: Task Assignee: suren pi Components: badge-plugin Created: 2018-09-29 06:30 Environment: badge-plugin-1.5 Labels: newbie-friendly Priority: Blocker Reporter: suren pi When I use pipeline script generator in pipeline syntax, got these error tips. `no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep ` Add Comment
[JIRA] (JENKINS-53697) git validate with requiredPush always return 428
Title: Message Title Olivier Lamy updated JENKINS-53697 Jenkins / JENKINS-53697 git validate with requiredPush always return 428 Change By: Olivier Lamy 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53697) git validate with requiredPush always return 428
Title: Message Title Olivier Lamy started work on JENKINS-53697 Change By: Olivier Lamy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53320) Job fails because JiraSCMListener times out on too many changes
Title: Message Title Olivier Lamy started work on JENKINS-53320 Change By: Olivier Lamy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-53816 [Blue Ocean] Completed stages appear to be skipped instead of finished Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53832) Jenkins 2.138.1 unable to start on CentOS 5
Title: Message Title Durgadas Kamath commented on JENKINS-53832 Re: Jenkins 2.138.1 unable to start on CentOS 5 Oleg Nenashev Glibc 2.7 is a must and CentOS 5 won't support it as its EOL this year . I don't think revert is the option here as newer things will have dependencies and that would stall everything. We probably add to documentation that CentOS 5 won't be supported 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. For more options, visit https://groups.google.com/d/optout.
