[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59096 Re: Mercurial plugin stops working after password change This on one still applies and blocks my work switching my repositories. 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.201516.1566893137000.11102.1584968580056%40Atlassian.JIRA.
[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change
Title: Message Title Christoph Fetzer commented on JENKINS-59096 Re: Mercurial plugin stops working after password change This on still applies and blocks my work switching my repositories. 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.201516.1566893137000.11101.1584966600047%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance after update
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance after update I noticed the msBuild warnings parser also does the job for me and thus removed one of the "grep"-layers. Unforunately the problem still persists. 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.201861.156818559.7517.1584345720046%40Atlassian.JIRA.
[JIRA] (JENKINS-61423) StackOverFlowException when using matrix jobs
Title: Message Title
Christoph Fetzer commented on JENKINS-61423
Re: StackOverFlowException when using matrix jobs
Hm, there seem to be additional correlations:
when I add an environment to another stage looking like this
stage( 'Build' ) {
environment {
MODULE_PATH = MODULE.replace( "/", "\\");
}
}
when I enable the credentials step again
the StackOverFlow is back again
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.205085.1583914012000.5122.1583922120200%40Atlassian.JIRA.
[JIRA] (JENKINS-61423) StackOverFlowException when using matrix jobs
Title: Message Title
Christoph Fetzer edited a comment on JENKINS-61423
Re: StackOverFlowException when using matrix jobs
OK, I had a 1:1 translation from matrix axis names to the environment with a different name, that caused the trouble. When accessing the axis names directly, everything started to work. Here the issue: {code:java} matrix {axes {axis {name 'PLATFORM'values 'win32vc9' }axis {name 'MODULE'values 'repo1/module1', 'repo2/module1' }axis {name 'VARIANT'values 'debug' } } stages { stage( 'Checkout' ) { environment {// removing the next line and accessing the content with %VARIANT% or ${VARIANT} directly or renaming the axis to "BUSY_VARIANT" solved the problem BUSY_VARIANT = "${VARIANT}" }... {code} I am not sure if this still is a bug or not. Though might be interesting for otherones to be able to find a solution.
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.205085.1583914012000.5055.1583916540138%40Atlassian.JIRA.
[JIRA] (JENKINS-61423) StackOverFlowException when using matrix jobs
Title: Message Title
Christoph Fetzer commented on JENKINS-61423
Re: StackOverFlowException when using matrix jobs
OK, I had a 1:1 translation from matrix axis names to the environment with a different name, that caused the trouble. When accessing the axis names directly, everything started to work. Here the issue: matrix { axes { axis { name 'PLATFORM' values 'win32vc9' } axis { name 'MODULE' values 'repo1/module1', 'repo2/module1' } axis { name 'VARIANT' values 'debug' } } stages { stage( 'Checkout' ) environment { // removing the next line and accessing the content with %VARIANT% or ${VARIANT} directly or renaming the axis to "BUSY_VARIANT" solved the problem BUSY_VARIANT = "${VARIANT}" } ... I am not sure if this still is a bug or not. Though might be interesting for otherones to be able to find a solution.
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.205085.1583914012000.5053.1583916360113%40Atlassian.JIRA.
[JIRA] (JENKINS-61423) StackOverFlowException when using matrix jobs
Title: Message Title
Christoph Fetzer updated an issue
Jenkins / JENKINS-61423
StackOverFlowException when using matrix jobs
Change By:
Christoph Fetzer
I am currently trying to set up a matrix build and whenever I have an axis with more than one values I run into a StackOverFlowException.This is my Pipeline (declarative):Comments: * I am not sure if customWorkspace will do what I want, that's currently only a try. Does anybody happen to have an idea how to use external-workspace-plugin from declarative pipelines? * the pipeline is edited for removing internal information, thus there might be unexpetced syntax issues * My feeling is there is a connection with another step used here like credentials or customworkspace because I can remember I've seen arunning pipeline in the past only with temporary workspaces on every build stage so missing all the checked out code. I'm trying to reproduce this and deliver that information later. {code:java}#!groovypipeline {agent { node { label '' customWorkspace "${JOB_NAME}/workspace" } }options { timestamps () }stages {stage('Build') { environment { BUSY_HOME = "${BUSYDIR}" BUSY_CMD = "${BUSYDIR}\\myBuildSystem.cmd" CVS_CREDENTIALS = credentials('BuildUser') } matrix { axes { axis { name 'PLATFORM' values 'win32vc9' } axis { name 'MODULE' values 'repo1/module1', 'repo2/ module2 module1 ' } axis { name 'VARIANT' values 'debug'} } stages { stage( 'Checkout' ) {environment {BUSY_VARIANT = "${VARIANT}"CVS_REPOSITORY = MODULE.substring( 0, MODULE.indexOf('/') )CVS_PATH = MODULE.substring( MODULE.indexOf('/') + 1 , MODULE.length() )CVS_CREDENTIALS = credentials('BuildUser')} steps {checkout changelog: true, poll: true, scm: [$class: 'CVSSCM', canUseUpdate: true, checkoutCurrentTimestamp: false , cleanOnFailedUpdate: false, disableCvsQuiet: false, forceCleanCopy: false, legacy: false, pruneEmptyDirectories: true , repositories: [[compressionLevel: -1, cvsRoot: ":pserver:${CVS_CREDENTIALS_USR}@MYCVS/${CVS_REPOSITORY}", excludedRegions: [[pattern: '']] , password: "${CVS_CREDENTIALS_PSW}", passwordRequired: true, repositoryItems: [[location: [$class: 'HeadRepositoryLocation'] , modules: [[localName: "${CVS_REPOSITORY}/${CVS_PATH}", remoteName: "${CVS_PATH}"]], skipChangeLog: false] } } stage( 'Build' ) { environment { BUSY_VARIANT = "${VARIANT}" CVS_REPOSITORY = MODULE.substring( 0,
[JIRA] (JENKINS-61423) StackOverFlowException when using matrix jobs
Title: Message Title
Christoph Fetzer commented on JENKINS-61423
Re: StackOverFlowException when using matrix jobs
This is the jenkins output:
Started by user USER
Lightweight checkout support not available, falling back to full checkout.
Checking out hudson.scm.CVSSCM into D:\workdir\build\Build-all\workspace@script to read Jenkins/Jenkinsfile-all
Using locally configured password for connection to :pserver:USER@SERVER:2401/build
cvs checkout -P -D 11 Mar 2020 08:28:22 +0100 -d Jenkins Jenkins
cvs server: Updating Jenkins
U Jenkins/Jenkinsfile-all
Using locally configured password for connection to :pserver:USER@SERVER:2401/build
cvs rlog -S -d10 Mar 2020 22:01:00 +0100<11 Mar 2020 08:28:22 +0100 Jenkins
cvs rlog: Logging Jenkins
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in D:\workdir\build\Build-all\workspace
[Pipeline] {
[Pipeline] ws
Running in D:\workdir\.jenkins\Build-all\workspace
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
Using locally configured password for connection to :pserver:USER@SERVER:2401/build
cvs checkout -P -D 11 Mar 2020 08:28:22 +0100 -d Jenkins Jenkins
cvs server: Updating Jenkins
U Jenkins/Jenkinsfile-all
Using locally configured password for connection to :pserver:USER@SERVER:2401/build
cvs rlog -S -d10 Mar 2020 22:01:00 +0100<11 Mar 2020 08:28:22 +0100 Jenkins
cvs rlog: Logging Jenkins
[Pipeline] }
[Pipeline] // stage
[Pipeline] timestamps
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] withCredentials
08:28:48 Masking supported pattern matches of %CVS_CREDENTIALS% or %CVS_CREDENTIALS_USR% or %CVS_CREDENTIALS_PSW%
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] parallel
[Pipeline] { (Branch: Matrix - MODULE = 'repo1/module1')
[Pipeline] { (Branch: Matrix - MODULE = 'repo2/module1')
[Pipeline] stage
[Pipeline] { (Matrix - MODULE = 'repo1/module1')
[Pipeline] stage
[Pipeline] { (Matrix - MODULE = 'repo2/module1')
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Checkout)
[Pipeline] stage
[Pipeline] { (Checkout)
[Pipeline] withCredentials
08:28:48 Masking supported pattern matches of %CVS_CREDENTIALS% or %CVS_CREDENTIALS_USR% or %CVS_CREDENTIALS_PSW%
[Pipeline] withCredentials
08:28:49 Masking supported pattern matches of %CVS_CREDENTIALS% or %CVS_CREDENTIALS_USR% or %CVS_CREDENTIALS_PSW%
[Pipeline] End of Pipeline
java.lang.StackOverflowError
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
[ removed a lot iterations of an endless loop ]
at
[JIRA] (JENKINS-61423) StackOverFlowException when using matrix jobs
Title: Message Title
Christoph Fetzer created an issue
Jenkins / JENKINS-61423
StackOverFlowException when using matrix jobs
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
matrix-project-plugin, pipeline
Created:
2020-03-11 08:06
Environment:
Jenkins ver. 2.204.5
Priority:
Critical
Reporter:
Christoph Fetzer
I am currently trying to set up a matrix build and whenever I have an axis with more than one values I run into a StackOverFlowException. This is my Pipeline (declarative): Comments:
I am not sure if customWorkspace will do what I want, that's currently only a try. Does anybody happen to have an idea how to use external-workspace-plugin from declarative pipelines?
the pipeline is edited for removing internal information, thus there might be unexpetced syntax issues
#!groovy
pipeline {
agent
{
node {
label ''
customWorkspace "${JOB_NAME}/workspace"
}
}
options { timestamps () }
stages {
stage('Build') {
environment {
BUSY_HOME = "${BUSYDIR}"
BUSY_CMD = "${BUSYDIR}\\myBuildSystem.cmd"
CVS_CREDENTIALS = credentials('BuildUser')
}
matrix {
axes {
axis {
name 'PLATFORM'
values 'win32vc9'
}
axis {
[JIRA] (JENKINS-61295) Illegal argument exception from warnings-ng plugin
Title: Message Title Christoph Fetzer commented on JENKINS-61295 Re: Illegal argument exception from warnings-ng plugin Works again. Thank you very much! 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.204872.158316597.3453.1583236206753%40Atlassian.JIRA.
[JIRA] (JENKINS-61295) Illegal argument exception from warnings-ng plugin
Title: Message Title Christoph Fetzer commented on JENKINS-61295 Re: Illegal argument exception from warnings-ng plugin Great! This was fast. I'll try it tomorrow. Thanks so far! 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.204872.158316597.3054.1583183820199%40Atlassian.JIRA.
[JIRA] (JENKINS-61295) Illegal argument exception from warnings-ng plugin
Title: Message Title Christoph Fetzer created an issue Jenkins / JENKINS-61295 Illegal argument exception from warnings-ng plugin Issue Type: Bug Assignee: Ulli Hafner Attachments: image-2020-03-02-17-19-27-817.png Components: warnings-ng-plugin Created: 2020-03-02 16:19 Environment: Jenkins ver. 2.204.3 warnings ng plugin 8.0.0 Priority: Critical Reporter: Christoph Fetzer Since the upgrade to warnings-ng 8.0.0 I am getting illegal-argument-exceptions in all my build jobs: ERROR: Build step failed with exception java.lang.IllegalArgumentException: 'other' has different root at sun.nio.fs.WindowsPath.relativize(Unknown Source) at sun.nio.fs.WindowsPath.relativize(Unknown Source) at edu.hm.hafner.util.PathUtil.getRelativePath(PathUtil.java:175) at edu.hm.hafner.util.PathUtil.getRelativePath(PathUtil.java:150) at edu.hm.hafner.analysis.FileNameResolver.makeRelative(FileNameResolver.java:61) at edu.hm.hafner.analysis.FileNameResolver.lambda$run$2(FileNameResolver.java:46) at java.util.stream.Collectors.lambda$toMap$58(Unknown Source) at java.util.stream.ReduceOps$3ReducingSink.accept(Unknown Source) at java.util.HashMap$KeySpliterator.forEachRemaining(Unknown Source) at java.util.stream.AbstractPipeline.copyInto(Unknown Source) at java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source) at java.util.stream.ReduceOps$ReduceTask.doLeaf(Unknown Source) at
[JIRA] (JENKINS-59311) Poor performance after update
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance after update Change By: Christoph Fetzer Attachment: Capture.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.201861.156818559.4123.1582275060068%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Environment: jenkins ver 2.176.3jenkins ver 2.190.1jenkins ver 2.190.3jenkins ver 2.204.1 jenkins ver 2.204.2 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.201861.156818559.7909.1581502080109%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance after update
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance after update Change By: Christoph Fetzer Summary: Poor performance when using 'grep' after update 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.201861.156818559.7910.1581502080147%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance when using 'grep' It still is present and restart of the service very reliably and repeatedly solves the issue. Could you please check the update procedure! 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.201861.156818559.9272.1580455500050%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Labels: performance update windows-service 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.201861.156818559.6200.1580110980081%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Environment: jenkins ver 2.176.3jenkins ver 2.190.1jenkins ver 2.190.3 jenkins ver 2.204.1 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.201861.156818559.6199.1580110920094%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance when using 'grep' The issue is still present. 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.201861.156818559.1026.1579260720060%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance when using 'grep' After the latest updates I got the problem again. Besides, all my automatic build weren't restartet The list of updates:Jira 3.0.10 -> 3.0.11 Oracle Java SE Development Kit Installer 1.3->1.4 Script Security 1.67->1.68 Warnings Next Generation 7.2.0->7.2.1Jenkins v2.190.3 Lat*'s see what happens It runs quickly again after a service restart. .. So I guess, it's an issue of the update procedure or the implementation as a windows service?Which components do these belong to for a correct assignment of the job? 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.201861.156818559.6202.1574681640065%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Component/s: core Component/s: pipeline 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.201861.156818559.6088.1574674320126%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Environment: jenkins ver 2.176.3jenkins ver 2.190.1 jenkins ver 2.190.3 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.201861.156818559.6087.1574674080260%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance when using 'grep' After the latest updates I got the problem again. Besides, all my automatic build weren't restartet The list of updates: Jira 3.0.10 -> 3.0.11 Oracle Java SE Development Kit Installer 1.3->1.4 Script Security 1.67->1.68 Warnings Next Generation 7.2.0->7.2.1 Jenkins v2.190.3 Lat*'s see what happens after a service restart... 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.201861.156818559.6086.1574674020060%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance when using 'grep' Arg - this issue doesn't like being chased.Every time I do a single action like update, reboot or restart behaviour stays the same.Whenever I do simultaneous actions, something changes.This time: update of Script security 166->1.67 and restart of jenkins (without reboot) due to hanging job fragments made the build fast again. Noticeable: I restarted jenkins by starting and stopping the jenkins service this time. BTW: really no support here? Where else can I get assistance? 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.201861.156818559.1214.1573747260208%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance when using 'grep' Arg - this issue doesn't like being chased.Every time I do a single action like update, reboot or restart behaviour stays the same.Whenever I do simultaneous actions, something changes.This time: update of Script security 166->1.67 and restart of jenkins (without reboot) due to hanging job fragments made the build fast again. BTW: really no support here? Where else can I get assistance? 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.201861.156818559.841.1573743540317%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance when using 'grep' Arg - this issue doesn't like being chased. Every time I do a single action like update, reboot or restart behaviour stays the same. Whenever I do simultaneous actions, something changes. This time: update of Script security 166->1.67 and restart of jenkins (without reboot) due to hanging job fragments made the build fast again. 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.201861.156818559.832.1573743360530%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance when using 'grep' A new finding: for a lot of sequential updates I aborted the running job after recognizing the build speed. That caused hanging processes in the back that made cleaning the workplace impossible. To recover from that I rebooted the machine (without having applied an update). After that the build ran slowly again. In the meantime the build got a little faste, it 'only' takes 5 hours instead of 8 previously. I can't find out the real time since when it happened because I had a number of failing builds in that time. 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.201861.156818559.12176.1573546800060%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance when using 'grep' The speed decrease dissappeared again. Maybe it got lost a little through the history of all the comments: the decrease happens only in one step, not distributed over all in case it runs slowly, removing a '| grep' from a makefile build rule immediately takes down the speed decrease I now started tracking all the plugin updates to maybe get a correlation between jenkins updates and speed impact 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.201861.156818559.10124.1571382060058%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Environment: jenkins ver 2.176.3 jenkins ver 2.190.1 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.201861.156818559.4482.1570700700212%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance when using 'grep' This jenkins installation is driving me nuts - the slow behaviour came back.The last quick run was on September, 27th. After that the build failed for some days due to issues with the code and the libraries used. The first completing build after that on Oct. 9th was slow again (same times - ~45min vs 3:40hours). OK, I noticed, there are failed builds with indicatino of slow behaviour since October, 2nd. The builds before failed after only 6mins.I implemented every updates in that time as soon as I realised them. There were a number of them in that time frame. Is there a log that shows the plugins updated and the version change? With that I could restore the state of September 27th and apply all the updates step by step until the build gets slower again. 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.201861.156818559.4478.1570700640113%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Summary: Poor performance of pipeline build compared to freestyle when using 'grep' 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.201861.156818559.4204.1570692420068%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer reopened an issue This jenkins installation is driving me nuts - the slow behaviour came back. The last quick run was on September, 27th. After that the build failed for some days due to issues with the code and the libraries used. The first completing build after that on Oct. 9th was slow again (same times - ~45min vs 3:40hours). I implemented every updates in that time as soon as I realised them. There were a number of them in that time frame. Is there a log that shows the plugins updated and the version change? With that I could restore the state of September 27th and apply all the updates step by step until the build gets slower again. Jenkins / JENKINS-59311 Poor performance of pipeline build compared to freestyle Change By: Christoph Fetzer Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer updated JENKINS-59311 Jenkins / JENKINS-59311 Poor performance of pipeline build compared to freestyle Change By: Christoph Fetzer Status: Fixed but Unreleased Resolved 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.201861.156818559.6777.1569589920206%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer updated JENKINS-59311 Was solved somewhere between V2.176.2 and v2.190.1. Relation to any plugin or module not clear. Solution is released. Jenkins / JENKINS-59311 Poor performance of pipeline build compared to freestyle Change By: Christoph Fetzer Status: Open Fixed but Unreleased Resolution: Fixed 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
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance of pipeline build compared to freestyle The problem seems to have disappeared after the latest LTS update to v2.190.1. At least at the first test build after that update. 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.201861.156818559.5729.1569487140050%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title
Christoph Fetzer edited a comment on JENKINS-59311
Re: Poor performance of pipeline build compared to freestyle
In fact, it is the grep. But that's in there for a longer time. Is there some real relation between a grep (from msys) and some components of jenkins that might explain the significant decrease in the speed? Second issue I observed with warnings-ng - for my tests I changed the use of recordIssued from:{code:java}recordIssues sourceCodeEncoding: 'ISO-8859-1', tools: [groovyScript(parserId: 'MSVC-Warning', pattern:'**/build-makedep.log', reportEncoding:'ISO-8859-1'), groovyScript(parserId: 'MSVC-Error', pattern:'**/build-makedep.log', reportEncoding:'ISO-8859-1') ]{code}to{code:java} recordIssues sourceCodeEncoding: 'ISO-8859-1',tools: [groovyScript(parserId: 'MSVC-Warning', reportEncoding:'ISO-8859-1'), groovyScript(parserId: 'MSVC-Error', reportEncoding:'ISO-8859-1') ]{code}(note the missing "pattern:") but that does not work as documented (scanning the console output without the need of an intermediate file). Ecuse me, that's not an issue, that's documented - but ugly!
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.201861.156818559.2693.1568371860091%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance of pipeline build compared to freestyle In fact, it is the grep. But that's in there for a longer time. Is there some real relation between a grep (from msys) and some components of jenkins that might explain the significant decrease in the speed? Second issue I observed with warnings-ng - for my tests I changed the use of recordIssued from: recordIssues sourceCodeEncoding: 'ISO-8859-1', tools: [groovyScript(parserId: 'MSVC-Warning', pattern:'**/build-makedep.log', reportEncoding:'ISO-8859-1'), groovyScript(parserId: 'MSVC-Error', pattern:'**/build-makedep.log', reportEncoding:'ISO-8859-1') ] to recordIssues sourceCodeEncoding: 'ISO-8859-1', tools: [groovyScript(parserId: 'MSVC-Warning', reportEncoding:'ISO-8859-1'), groovyScript(parserId: 'MSVC-Error', reportEncoding:'ISO-8859-1') ] (note the missing "pattern:") but that does not work as documented (scanning the console output without the need of an intermediate file). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance of pipeline build compared to freestyle I maybe got the point:My build deep inside makes use of a compiler | tee | grep,... and therefore is splitting the output into a file at one point.Not too far ago I switched from a formerly deprected warnings parser to the warnings next generation plugin and therefore had to insert another | tee - split. I'm not yet 100% sure if this exactly matches the point were buildtimes increased but at least it might be close to. I'll set up a test.At least my way quicker freestyle build do does not make use of the inner | tee | grep!On the other hand this | tee provides a list of other problems and I'd like to avoid it at any level - also for warnings next generation. Is there another way to split build output to a file and in the same step keep the return code? 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.201861.156818559.2045.1568298060421%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance of pipeline build compared to freestyle I maybe got the point:My build deep inside makes use of a compiler | tee | grep,... and therefore is splitting the output into a file at one point.Not too far ago I switched from a formerly deprected warnings parser to the warnings next generation plugin and therefore had to insert another | tee - split. I'm not yet 100% sure if this exactly matches the point were buildtimes increased but at least it might be close to. I'll set up a test. At least my way quicker freestyle build do not make use of the inner | tee | grep! On the other hand this | tee provides a list of other problems and I'd like to avoid it at any level - also for warnings next generation. Is there another way to split build output to a file and in the same step keep the return code? 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.201861.156818559.2041.1568297940323%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance of pipeline build compared to freestyle I maybe got the point: My build deep inside makes use of a compiler | tee | grep,... and therefore is splitting the output into a file at one point. Not too far ago I switched from a formerly deprected warnings parser to the warnings next generation plugin and therefore had to insert another | tee - split. I'm not yet 100% sure if this exactly matches the point were buildtimes increased but at least it might be close to. I'll set up a test. On the other hand this | tee provides a list of other problems and I'd like to avoid it at any level - also for warnings next generation. Is there another way to split build output to a file and in the same step keep the return code? 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.201861.156818559.2040.1568297820067%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer created an issue Jenkins / JENKINS-59311 Poor performance of pipeline build compared to freestyle Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-09-11 07:06 Environment: jenkins ver 2.176.3 Priority: Major Reporter: Christoph Fetzer I have a bunch of freestyle jobs, that compile and build an installer for my software on two compilers and in debug/release. Each of them takes aroung half an hour. Then I tried to switch the build to a pipeline build, integrated build of debug and release to one job and additionally integrated several other stuff (cppcheck,...). This build ended up in taking 3-4 hours for quite a while (which I did not expect and regard it as slow also). Since some weeks now my pipeline job suddenly started taking 8 hours while the freestyle jobs duration staid the same. Something about my environment: it's a jenkins-installation as service on a windows server 2016 machine. I am not aware of any changes on the machine installation or job configuration since the job got slower. It's not a single step in the pipeline that eats all the time. It's the overall performance and the time is distributed over all steps. E.g. the compile and build installer step (which is the entire job done by the freestyle job) alone takes 3 hours. Unfortunately I don't have the build history long enough to be able to identify plugin-versions from before and after the buildtime-increase. Please contact me in case I can help with any additional information.
[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change
Title: Message Title Christoph Fetzer commented on JENKINS-59096 Re: Mercurial plugin stops working after password change Addition: as soon as I synced once with the TortoiseHg GUI (and was asked for the password) the plugin started to work again. Unfortunately I now cannot test any impovements of modified plugins before the next password change. 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.201516.1566893137000.489.1568107561023%40Atlassian.JIRA.
[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change
Title: Message Title Christoph Fetzer commented on JENKINS-59096 Re: Mercurial plugin stops working after password change Anybody out there? I can't work with it currently Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201516.1566893137000.3103.1567153620068%40Atlassian.JIRA.
[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59096 Mercurial plugin stops working after password change Change By: Christoph Fetzer Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201516.1566893137000.3102.1567153560148%40Atlassian.JIRA.
[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change
Title: Message Title Christoph Fetzer created an issue Jenkins / JENKINS-59096 Mercurial plugin stops working after password change Issue Type: Bug Assignee: Unassigned Components: mercurial-plugin Created: 2019-08-27 08:05 Environment: Jenkins ver. 2.176.2 mercurial plugin 2.8 TortoiseHg 4.3.1 Mercurial 4.3.1 Labels: Mercurial Password-change Authentication Priority: Critical Reporter: Christoph Fetzer I have a pipeline-job with mercurial SCM working for some time now. Currently the password policy forced me to change the password. Since that time the job stopped working with the following output: Started by user xxx Checking out hg http://myserver/hg/product/ default into D:\workdir\build\mybuild\workspace@script to read Jenkins/Jenkinsfile Acquired master cache lock. [CE47F913B3A5D3AC403DD8A225DB0EACDEBF7619-myproduct-myuser] $ "C:\Program Files\TortoiseHg\hg.exe" --config auth.jenkins.prefix=* --config --config --config "auth.jenkins.schemes=http https" pull pulling from http://myserver/hg/myproduct/ abort: keyring: http authorization required but program used in non-interactive mode ERROR: Failed to update D:\workdir\.jenkins\hgcache\CE47F913B3A5D3AC403DD8A225DB0EACDEBF7619-myproduct-myuser Master cache lock released. ERROR: Failed to use repository cache for http://myserver/hg/myproduct/ [workspace@script] $ "C:\Program Files\TortoiseHg\hg.exe" --config
[JIRA] (JENKINS-57899) Jira site configuration lost after a restart
Title: Message Title Christoph Fetzer commented on JENKINS-57899 Re: Jira site configuration lost after a restart For me: '1.1' encoding='UTF-8'?> "jira@3.0.7"> "hudson.util.PersistedList"> http://myJira:8080/ myJira:8080/ false BuildUser false true false (JOB+-[1-9][0-9]*)([^.]|\.[^0-9]|\.$|$) false 10 30 10 true 2 But as noted: the workaround did not work for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.1963.1564156080786%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a restart
Title: Message Title Christoph Fetzer commented on JENKINS-57899 Re: Jira site configuration lost after a restart I can confirm missing updates of the config file. What my problems looked like: I had to change the configuration of the Jira server (moved to a new host). My first experience of the fault was, in some magic way the setting changed back to the old one. I tried to manually correct the setting in the config file, which was the place were I found the old settings. Since that, the settings entirely disappeared (but still lived in the config file). I can still not confirm the time points when the settings changed back: I intentionally restarted jenjkins several times due to jenkins - and/or plugin updates and I can't remember a correlation between those restarts and broken Jira settings. Unfortunately this is a production system. Therefore I reverted the plugin back to 3.0.6 and can't play around with it to find out more relations. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.845.1564060260247%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Christoph Fetzer commented on JENKINS-57899 Re: Jira site configuration lost after a reboot 1. didn't work for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.20257.1563971040646%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Christoph Fetzer commented on JENKINS-57899 Re: Jira site configuration lost after a reboot I cannot confirm this. For me the setting survived a number of restarts and got lost at a unknown time. I wanted to ask for machine reboot because the machine is maintained by someone else and I am not aware of every reboot. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.20146.1563968341030%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Christoph Fetzer commented on JENKINS-57899 Re: Jira site configuration lost after a reboot I had the same issue with jira-plugin 3.0.8 Question: what do you mean by "reboot"? - restart of jenkins or reboot of the machine? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.18844.1563886200441%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-57899 Jira site configuration lost after a reboot Change By: Christoph Fetzer Environment: jira-plugin 3.0.7 jira-plugin 3.0.8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.18547.1563869220615%40Atlassian.JIRA.
