[JIRA] (JENKINS-61233) Do not activate the build discarder during version updates
Title: Message Title Andreas Nusser created an issue Jenkins / JENKINS-61233 Do not activate the build discarder during version updates Issue Type: Improvement Assignee: Unassigned Components: core Created: 2020-02-26 11:48 Environment: Jenkins 2.222 OpenJdk 1.8 CentOS Linux release 7.7.1908 (Core) Installed via YUM Plugins: org.jenkins-ci.main:jenkins-war:2.222 org.jenkins-ci:crypto-util:1.1 commons-httpclient:commons-httpclient:3.1-jenkins-1 aopalliance:aopalliance:1.0 com.google.code.findbugs:annotations:3.0.0 commons-beanutils:commons-beanutils:1.9.3 com.google.inject:guice:4.0 org.springframework:spring-dao:1.2.9 org.kohsuke.stapler:stapler-jrebel:1.258 org.codehaus.groovy:groovy-all:2.4.12 org.jenkins-ci:constant-pool-scanner:1.2 org.jenkins-ci.modules:windows-slave-installer:1.12 org.connectbot.jbcrypt:jbcrypt:1.0.0 org.ow2.asm:asm-commons:5.0.3 org.jenkins-ci:symbol-annotation:1.1 org.slf4j:slf4j-api:1.7.26 commons-digester:commons-digester:2.1 org.kohsuke:libpam4j:1.11 com.github.jnr:jnr-posix:3.0.45 org.jvnet.winp:winp:1.28 org.apache.commons:commons-compress:1.19 org.jenkins-ci.modules:instance-identity:2.2 org.kohsuke:asm6:6.2 net.sf.kxml:kxml2:2.3.0 org.kohsuke:libzfs:0.8 org.jenkins-ci.main:remoting:4.2 org.jenkins-ci.modules:sshd:2.6 org.kohsuke:access-modifier-annotation:1.16 org.jenkins-ci.modules:slave-installer:1.7 org.kohsuke.stapler:json-lib:2.4-jenkins-2 org.jfree:jfreechart:1.0.19 org.slf4j:slf4j-jdk14:1.7.26 org.jvnet.robust-http-client:robust-http-client:1.2 org.ow2.asm:asm:5.0.3 com.github.jnr:jnr-ffi:2.1.8 com.github.jnr:jnr-constants:0.9.9 org.kohsuke.stapler:stapler-adjunct-timeline:1.5 org.jvnet.hudson:commons-jelly-tags-define:1.0.1-hudson-20071021 commons-lang:commons-lang:2.6 org.springframework:spring-jdbc:1.2.9 org.codehaus.woodstox:wstx-asl:3.2.9 org.springframework:spring-core:2.5.6.SEC03 org.springframework:spring-aop:2.5.6.SEC03 org.jfree:jcommon:1.0.23 org.samba.jcifs:jcifs:1.3.17-kohsuke-1 net.java.dev.jna:jna:5.3.1 net.i2p.crypto:eddsa:0.3.0 org.jenkins-ci:winstone:5.8 com.sun.solaris:embedded_su4j:1.1 com.github.jnr:jffi:1.2.17 javax.inject:javax.inject:1 org.jenkins-ci.modules:upstart-slave-installer:1.1 args4j:args4j:2.33 org.fusesource.jansi:jansi:1.11 org.springframework:spring-beans:2.5.6.SEC03 net.java.sezpoz:sezpoz:1.13 javax.xml.stream:stax-api:1.0-2 org.jvnet.hudson:activation:1.1.1-hudson-1 commons-jelly:commons-jelly-tags-fmt:1.0 org.slf4j:log4j-over-slf4j:1.7.26 oro:oro:2.0.8 org.jenkins-ci:commons-jexl:1.1-jenkins-20111212 org.jenkins-ci.plugins.icon-shim:icon-set:1.0.5 org.apache.
[JIRA] (JENKINS-61233) Do not activate the build discarder during version updates
Title: Message Title Andreas Nusser updated an issue Jenkins / JENKINS-61233 Do not activate the build discarder during version updates Change By: Andreas Nusser After I upgraded Jenkins from 2.220 to 2.222, the build discarder started to delete a ton of old builds. This had the effect that Jenkins somehow lost track if a branch of a multi-branch-pipeline job was already built. Which resulted in all of these branches being triggered and subsequently causing a huge spike in load. Additionally, this triggerd a bug in the [ Gitlab plugin ( Plugin| [https://github.com/jenkinsci/gitlab-plugin/issues/1030 ) ] ] which caused almost all of these builds to fail. Please don't do this. Don't introduce global features (build discarder) which mess with projects/jobs. I believe that this feature is perfect for newly setup Jenkins servers but not for Jenkins servers which are already running for a long time. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message be
[JIRA] (JENKINS-61233) Do not activate the build discarder during version updates
Title: Message Title Andreas Nusser commented on JENKINS-61233 Re: Do not activate the build discarder during version updates I don't know how special our setup is, but it is quiet customized. If necessary I can provide you with more details later but the 1000m view is: (Almost) all our Jobs are defined by Seed-Jobs via the [Job DSL Plugin|https://jenkinsci.github.io/job-dsl-plugin/] (Almost) all Jobs are multi branch pipeline jobs I'm right now not 100% but I believe that these jobs use the "orphanedItemStrategy". But I would need to double check when I'm back at the office. The branches tend to get rather old. Because of reasons ... branches are created for a specific date and after this date left untouched for most of the time. This means that there are multi branch jobs with branches last changed and built 2018. Before the "incident" these jobs would still hold a build from 2018. Do you need/want more information? 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.co
[JIRA] (JENKINS-61233) Do not activate the build discarder during version updates
Title: Message Title Andreas Nusser updated an issue Jenkins / JENKINS-61233 Do not activate the build discarder during version updates Change By: Andreas Nusser Attachment: jenkins-script-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.204788.1582717704000.4524.1583308680145%40Atlassian.JIRA.
[JIRA] (JENKINS-61233) Do not activate the build discarder during version updates
Title: Message Title
Andreas Nusser commented on JENKINS-61233
Re: Do not activate the build discarder during version updates
The output of your script is attached as file. jenkins-script-output.txt The seed jobs looke similar to:
def createBuildPipeline(folderPath, projectName, pipelineName = BUILD_DIR) {
def repoGit = Constants.getSCMRepo(projectName)
def repoHttp = Constants.getHTTPRepo(projectName)folder(folderPath) {
description("Bla bla")
}// Build Jobs
multibranchPipelineJob(folderPath + pipelineName) {
description("Bla bla")
branchSources {
def uniqueId = "${folderPath}-${projectName}-${pipelineName}"
git {
id(uniqueId)
remote(repoGit)
credentialsId(JENKINS_CREDENTIALS_ID)
}
}
triggers {
periodicFolderTrigger{
interval(SCAN_REPO_AFTER_MINUTES)
}
}orphanedItemStrategy {
// Trims dead items by the number of days or the number of items.
discardOldItems {
// Sets the number of days to keep old items.
daysToKeep(DELETED_BRANCHES_KEEP_DAYS)
// Sets the number of old items to keep.
numToKeep(DELETED_BRANCHES_KEEP_NUMBER)
}
}configure { node ->
node / 'sources' / 'data' / 'jenkins.branch.BranchSource' {
source(class: 'jenkins.plugins.git.GitSCMSource') {
remote(repoGit)
credentialsId(JENKINS_CREDENTIALS_ID)
includes('*')
excludes()
ignoreOnPushNotifications('false')
}// this property prevents scanning the pipeline from triggering builds of all branches
strategy(class: 'jenkins.branch.DefaultBranchPropertyStrategy') {
properties(class: 'java.util.Arrays$ArrayList') {
a(class: 'jenkins.branch.BranchProperty-array') {
'jenkins.branch.NoTriggerBranchProperty'()
}
}
}
}}
}
}
I mean, there is the possibility that this was not the fault of the build discarder but some other feature (Gitlab cough). Still the fact remains that after the upgrade, where I upgraded Jenkins and the plugins, I had to rebuild all branches because the old builds where gone. Maybe there was even a bug in the old discarding handling and the fix caused this.
Add Com
[JIRA] (JENKINS-61233) Do not activate the build discarder during version updates
Title: Message Title Andreas Nusser commented on JENKINS-61233 Re: Do not activate the build discarder during version updates They have number like #22 or #27 If you like to close the issue, it is fine with me. I just wanted to raise awareness for a potential problem. 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.204788.1582717704000.4623.1583313060182%40Atlassian.JIRA.
[JIRA] (JENKINS-61661) Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided
Title: Message Title Andreas Nusser created an issue Jenkins / JENKINS-61661 Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided Issue Type: Improvement Assignee: Unassigned Components: jira-plugin Created: 2020-03-24 11:18 Environment: Jenkins 2.226 OpenJdk 1.8 CentOS Linux release 7.7.1908 (Core) Installed via YUM Plugins: Jira Plugin 3.0.13 Priority: Minor Reporter: Andreas Nusser When not configuring any credentials but a URL for the Jira Plugin, it still tries to connect to the URL. This results in a lot of InvalidCacheLoadException 2020-03-16 02:22:09.137+ [id=7306028] WARNING h.model.listeners.RunListener#report: RunListener failed com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key UCS-154. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2383) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at hudson.plugins.jira.JiraSite.getIssue(JiraSite.java:873) at hudson.plugins.jira.JiraJobAction.setAction(JiraJobAction.java:99) at hudson.plugins.jira.JiraJobAction$RunListenerImpl.onStarted(JiraJobAction.java:130) at hudson.plugins.jira.JiraJobAction$RunListenerImpl.onStarted(JiraJobAction.java:122) at hudson.model.listener
[JIRA] (JENKINS-61661) Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided
Title: Message Title Andreas Nusser commented on JENKINS-61661 Re: Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided Got the okay from my employer and will try to provide a Pull Request the next days. 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.205393.1585048689000.7201.1586203200275%40Atlassian.JIRA.
