[JIRA] (JENKINS-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes
Title: Message Title Michael Kriese commented on JENKINS-55517 Re: Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes Looks like the 'Ignore rebuilding merge branches when only the target branch changed' option is no longer working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-4865) Optional build start notification for Nabaztag plugin
Title: Message Title Owen Mehegan closed an issue as Won't Fix Jenkins / JENKINS-4865 Optional build start notification for Nabaztag plugin Change By: Owen Mehegan Status: In Progress Closed Resolution: Won't Fix 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-4866) Nabaztag validation with ajax
Title: Message Title Owen Mehegan closed an issue as Won't Fix Jenkins / JENKINS-4866 Nabaztag validation with ajax Change By: Owen Mehegan Status: In Progress Closed Resolution: Won't Fix 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-8182) When nabaztag is sleeping the build is failed
Title: Message Title Owen Mehegan closed an issue as Won't Fix Jenkins / JENKINS-8182 When nabaztag is sleeping the build is failed Change By: Owen Mehegan Status: Open Closed Resolution: Won't Fix 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-6325) Build status recovery when going from Unstable to Success
Title: Message Title Owen Mehegan closed an issue as Won't Fix Jenkins / JENKINS-6325 Build status recovery when going from Unstable to Success Change By: Owen Mehegan Status: Open Closed Resolution: Won't Fix 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-5939) The culprit names of a failed build should be sent for TTS
Title: Message Title Owen Mehegan closed an issue as Won't Fix Jenkins / JENKINS-5939 The culprit names of a failed build should be sent for TTS Change By: Owen Mehegan Status: Open Closed Resolution: Won't Fix 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-57136) Allow users to customize docker timeouts
Title: Message Title Keunhong Lee updated an issue Jenkins / JENKINS-57136 Allow users to customize docker timeouts Change By: Keunhong Lee Priority: Major Minor 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-57150) Need to connect to TFS online site through Jenkins
Title: Message Title Denys Digtiar assigned an issue to redsolo Jenkins / JENKINS-57150 Need to connect to TFS online site through Jenkins Change By: Denys Digtiar Assignee: Michael McCaskill redsolo 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-57150) Need to connect to TFS online site through Jenkins
Title: Message Title Denys Digtiar moved an issue Jenkins / JENKINS-57150 Need to connect to TFS online site through Jenkins Change By: Denys Digtiar Project: Jenkins Website Key: WEBSITE JENKINS - 524 57150 Issue Type: Improvement Bug Workflow: WEBSITE: Software Development Workflow JNJira + In-Review Status: To Do Open Component/s: tfs-plugin Component/s: administrative Component/s: content Component/s: core Component/s: design Component/s: plugin-site
[JIRA] (JENKINS-57149) Shell redirect causes exit code 0 on official docker Jenkins
Title: Message Title
Levi Blaney created an issue
Jenkins / JENKINS-57149
Shell redirect causes exit code 0 on official docker Jenkins
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-durable-task-step-plugin
Created:
2019-04-23 00:17
Environment:
Plugin v2.21 and 2.30. Also tested this on several Jenkins of various versions.
Priority:
Minor
Reporter:
Levi Blaney
When using the official Jenkins docker container `jenkins/jenkins` or `jenkins/jenkins:lts`, running a `sh()` step that has `&>` causes the command work even if the command should fail. It also doesn't appear that the command is running at all. So `sh('notacommand &> test.log')` outputs the `command not found` error to the console instead of the file. Creates an empty `test.log` and the build passes even though it should have failed.
Add Comment
[JIRA] (JENKINS-57148) hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck
Title: Message Title Alexey Grigorov closed an issue as Not A Defect Jenkins / JENKINS-57148 hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck Change By: Alexey Grigorov Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57148) hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck
Title: Message Title Alexey Grigorov commented on JENKINS-57148 Re: hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck after digging into a source code of a authorize-project plugin I actually found that exception handled there org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java:196 so this ticket is not valid I am closing it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57148) hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck
Title: Message Title Alexey Grigorov created an issue Jenkins / JENKINS-57148 hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-22 23:05 Environment: jenkins 2.164.1 Priority: Critical Reporter: Alexey Grigorov Hi Jenkins team We have a situation where we have few hundreds builds in the queue and one of them throws exception in queue.maintain (in our case job authentication is set to user which left and not exist in AD anymore). This exception is not handled inside the loop which iterates over buildable items and because of that all execution of queue.maintain fails, and next time if fails again and again. Other items in the queue which are healthy cannot run or have to wait for hours, because exception is thrown before their turn in queue.maintain and not handled. To my mind there should be exception handling inside a loop of hudson/model/Queue.java:1587 to avoid impact on other queue items processing if just one item is faulty. below is a message we see in the log with frequency of few dozens per second. WARNING: Invalid User someleftuser. Falls back to anonymous. org.acegisecurity.userdetails.UsernameNotFoundException: Authentication was successful but cannot locate the user information for someleftuser at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:392) at
[JIRA] (JENKINS-57145) Reduce noisy logs when using withMaven inside a Docker container
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-57145
Reduce noisy logs when using withMaven inside a Docker container
Change By:
Cyrille Le Clerc
withMaven issues the following warning message when used in a container:{noformat}[withMaven] WARNING: "withMaven(){...}" step running within a container. Since the Docker Pipeline Plugin version 1.14, you MUST:[withMaven] * Either prepend the 'MVN_CMD_DIR' environment variable to the 'PATH' environment variable in every 'sh' step that invokes 'mvn' (e.g. "sh 'export PATH=$MVN_CMD_DIR:$PATH && mvn clean deploy' ").[withMaven] * Or use 'MVN_CMD' instead of invoking 'mvn'" (e.g. \"sh \'$MVN_CMD clean deploy\' \").[withMaven] * Or use Takari's Maven Wrapper (e.g. "sh './mvnw clean deploy'")[withMaven] See "Pipeline Maven Plugin FAQ"{noformat}This message is frightening and way too verbose if the pipeline properly integrates withMaven with "docker.image("...").inside \ {... \ }"
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-57147) MissingPropertyException: $DEFAULT_CONTENT is not available in declarative pipeline.
Title: Message Title
Saurabh Tripathi created an issue
Jenkins / JENKINS-57147
MissingPropertyException: $DEFAULT_CONTENT is not available in declarative pipeline.
Issue Type:
Bug
Assignee:
David van Laatum
Components:
email-ext-plugin
Created:
2019-04-22 22:12
Priority:
Major
Reporter:
Saurabh Tripathi
$DEFAULT_CONTENT is not available in jenkins declarative pipeline. Attempt to access it
pipeline {
agent any
stages {
stage('one') {
agent any
steps {
script {
println 'Hello world'
}
}
}
}
post {
always {
println 'xx'
emailext body: """
Build Initiated by test
${DEFAULT_CONTENT}
"HOST">HOST
""",
subject: '$DEFAULT_SUBJECT',
to: "s...@gmail.com"
}
}
}
gives the follow error(line number are not correct as code omitted for brevity):
groovy.lang.MissingPropertyException: No such property: DEFAULT_CONTENT for class: WorkflowScript
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)
at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:290)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onGetProperty(GroovyInterceptor.java:68)
at
[JIRA] (JENKINS-57144) tempBinDir is added with value '' by the code snippet generator
Title: Message Title Cyrille Le Clerc updated JENKINS-57144 Jenkins / JENKINS-57144 tempBinDir is added with value '' by the code snippet generator Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57144) tempBinDir is added with value '' by the code snippet generator
Title: Message Title Cyrille Le Clerc started work on JENKINS-57144 Change By: Cyrille Le Clerc 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-57146) Read connection secret from file
Title: Message Title Jeff Thompson created an issue Jenkins / JENKINS-57146 Read connection secret from file Issue Type: Improvement Assignee: Jeff Thompson Components: remoting Created: 2019-04-22 22:04 Priority: Minor Reporter: Jeff Thompson When connecting an agent using an inbound connection mechanism (sometimes mistakenly called JNLP), a connection secret must be supplied. This is commonly provided on the command line via the "-secret" argument. Some users want a different mechanism, which would allow them to place the secret in a file and then instruct the agent to read the file to obtain the secret. A new optional argument needs to be provided to allow the user to specify this mechanism and the file to use. Add Comment
[JIRA] (JENKINS-57145) Reduce noisy logs when using withMaven inside a Docker container
Title: Message Title
Cyrille Le Clerc created an issue
Jenkins / JENKINS-57145
Reduce noisy logs when using withMaven inside a Docker container
Issue Type:
Improvement
Assignee:
Cyrille Le Clerc
Components:
pipeline-maven-plugin
Created:
2019-04-22 22:01
Priority:
Minor
Reporter:
Cyrille Le Clerc
withMaven issues the following warning message when used in a container:
[withMaven] WARNING: "withMaven(){...}" step running within a container. Since the Docker Pipeline Plugin version 1.14, you MUST:
[withMaven] * Either prepend the 'MVN_CMD_DIR' environment variable to the 'PATH' environment variable in every 'sh' step that invokes 'mvn' (e.g. "sh 'export PATH=$MVN_CMD_DIR:$PATH && mvn clean deploy' ").
[withMaven] * Or use 'MVN_CMD' instead of invoking 'mvn'" (e.g. \"sh \'$MVN_CMD clean deploy\' \").
[withMaven] * Or use Takari's Maven Wrapper (e.g. "sh './mvnw clean deploy'")
[withMaven] See "Pipeline Maven Plugin FAQ"
This message is frightening and way too verbose if the pipeline properly integrates withMaven with "docker.image("...").inside {...} "
[JIRA] (JENKINS-57144) tempBinDir is added with value '' by the code snippet generator
Title: Message Title
Cyrille Le Clerc created an issue
Jenkins / JENKINS-57144
tempBinDir is added with value '' by the code snippet generator
Issue Type:
Bug
Assignee:
Cyrille Le Clerc
Components:
pipeline-maven-plugin
Created:
2019-04-22 21:57
Priority:
Minor
Reporter:
Cyrille Le Clerc
tempBinDir is added with value '' by the code snippet generator. A code snippet wit default values look like
withMaven(tempBinDir: '') { // tempBinDir should NOT be displayed
// some block
}
Add Comment
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Cyrille Le Clerc updated JENKINS-56232 Jenkins / JENKINS-56232 Maven Local Repository is always seen as relative when it should be absolute Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Cyrille Le Clerc started work on JENKINS-56232 Change By: Cyrille Le Clerc 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-56666) Maven versioning extension produces warnings
Title: Message Title Cyrille Le Clerc commented on JENKINS-5 Re: Maven versioning extension produces warnings Michael D can we mark this issue as fixed by the bump of https://github.com/qoomon/maven-git-versioning-extension to version 4.0.3+ ? 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-56666) Maven versioning extension produces warnings
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-5 Maven versioning extension produces warnings Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title
Alexey Shein updated an issue
Jenkins / JENKINS-57143
JNLP4 error: "Connection closed before acknowledgement sent"
Change By:
Alexey Shein
Hello!We run JNLP-powered agents on 4 Mac machines, after Jenkins update to 2.164.2 (from 2.150.3), those machines are not able to connect using JNLP-4 (see exception below), although JNLP-3 connection works.Agent is run as: {{ /usr/bin/java -Djava.awt.headless=true -jar /Applications/Jenkins/agent.jar -jnlpUrl https:///computer//slave-agent.jnlp -secret -workDir /Users/jenkins/jenkins_root }} Exception on agent: {{ INFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sentat org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223)at hudson.remoting.Engine.innerRun(Engine.java:614)at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sentat org.jenkinsci.remoting.protocol.impl.AckFilterLayer.onRecvClosed(AckFilterLayer.java:280)at org.jenkinsci.remoting.protocol.FilterLayer.abort(FilterLayer.java:164)at org.jenkinsci.remoting.protocol.impl.AckFilterLayer.access$000(AckFilterLayer.java:43)at org.jenkinsci.remoting.protocol.impl.AckFilterLayer$1.run(AckFilterLayer.java:176)at org.jenkinsci.remoting.protocol.IOHub$DelayedRunnable.run(IOHub.java:964)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)at java.lang.Thread.run(Thread.java:748 )}} On jenkins master: {{ Apr 22, 2019 3:42:42 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #1512 failedjava.io.EOFExceptionat java.io.DataInputStream.readFully(DataInputStream.java:197)at java.io.DataInputStream.readFully(DataInputStream.java:169)at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:244)Apr 22, 2019 3:42:42 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #1,513 from /:58595Apr 22, 2019 3:42:54 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #1514 failedjava.io.EOFExceptionat java.io.DataInputStream.readFully(DataInputStream.java:197)at java.io.DataInputStream.readFully(DataInputStream.java:169)at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:244) }} Things that I checked:- agent.jar is up-to-date and matches the one on master- JNLP port on master is open and available from the agent
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title
Alexey Shein created an issue
Jenkins / JENKINS-57143
JNLP4 error: "Connection closed before acknowledgement sent"
Issue Type:
Bug
Assignee:
Jeff Thompson
Components:
remoting
Created:
2019-04-22 21:07
Environment:
Agent: OSX Mojave 10.14.4 Jenkins: Linux (Jenkins LTS 2.164.2) Java on agent: java version "1.8.0_162" Java(TM) SE Runtime Environment (build 1.8.0_162-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode) Java on master: openjdk version "1.8.0_201" OpenJDK Runtime Environment (build 1.8.0_201-b09) OpenJDK 64-Bit Server VM (build 25.201-b09, mixed mode)
Priority:
Blocker
Reporter:
Alexey Shein
Hello! We run JNLP-powered agents on 4 Mac machines, after Jenkins update to 2.164.2 (from 2.150.3), those machines are not able to connect using JNLP-4 (see exception below), although JNLP-3 connection works. Agent is run as: {{ /usr/bin/java -Djava.awt.headless=true -jar /Applications/Jenkins/agent.jar -jnlpUrl https:///computer//slave-agent.jnlp -secret -workDir /Users/jenkins/jenkins_root }} Exception on agent: {{INFO: Protocol JNLP4-connect encountered an unexpected exception java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474) Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent at org.jenkinsci.remoting.protocol.impl.AckFilterLayer.onRecvClosed(AckFilterLayer.java:280) at org.jenkinsci.remoting.protocol.FilterLayer.abort(FilterLayer.java:164) at
[JIRA] (JENKINS-57142) foundFailureCauses returning blank with new versions of Build Failure Analyzer
Title: Message Title Arnon Meshoulam created an issue Jenkins / JENKINS-57142 foundFailureCauses returning blank with new versions of Build Failure Analyzer Issue Type: Bug Assignee: lucamilanesio Components: statistics-gatherer-plugin Created: 2019-04-22 20:50 Environment: Jenkins 2.6.3 statistics Gatherer 2.1 Priority: Minor Reporter: Arnon Meshoulam foundFailureCauses returns empty list in all cases. Issue has been debugged to be a mixture of 3 causes: If Jenkins uses authorization, query to "/api/json?depth=2=actions[foundFailureCauses[categories,description,id,name]]" returns unauthorized addBuildFailureCauses function tried to parse JSON without an array convertBuildFailureToMap raises an exception when Category is set to empty
[JIRA] (JENKINS-47279) Full-duplex HTTP(S) transport with plain CLI protocol does not work with Apache reverse proxy in Jenkins >= 2.54
Title: Message Title Jesse Glick commented on JENKINS-47279 Re: Full-duplex HTTP(S) transport with plain CLI protocol does not work with Apache reverse proxy in Jenkins >= 2.54 If we want to maintain the CLI system in the long term (as opposed to guiding users toward REST), then we could offer the “plain” protocol over WebSocket transport rather than the full-duplex HTTP hack. 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-55477) Unable to delete files while cloning git repository
Title: Message Title Matt Sicker commented on JENKINS-55477 Re: Unable to delete files while cloning git repository Is this still an issue with recent versions of Jenkins? 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-57141) Multiple Build Duration Columns resets values when returning to Edit View
Title: Message Title Kurt Routley created an issue Jenkins / JENKINS-57141 Multiple Build Duration Columns resets values when returning to Edit View Issue Type: Bug Assignee: Fred G Components: extra-columns-plugin Created: 2019-04-22 20:06 Environment: Jenkins core 2.164.1 Extra Columns Plugin 1.20 Java: OpenJDK 1.8.0_161-b14 64-bit Labels: View Priority: Major Reporter: Kurt Routley If two Build Duration columns are included in a List View, returning to the Edit View page adjusts the value of the second Build Duration column configuration to match the first one instead of loading the previous configuration. Steps to reproduce the issue: Create a List View with two Build Duration Columns: Configure the first column to Show "Build Start" Configure the second column to Show "Average duration in minutes-compact" Click OK Click Edit View on the view page Check the value of both Build Duration Columns, they will both say
[JIRA] (JENKINS-54325) Support multiple SimplePageDecorators for login and signup page footers
Title: Message Title Matt Sicker closed an issue as Fixed Jenkins / JENKINS-54325 Support multiple SimplePageDecorators for login and signup page footers Change By: Matt Sicker Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54325) Support multiple SimplePageDecorators for login and signup page footers
Title: Message Title Matt Sicker updated JENKINS-54325 Released in 2.156, forgot to close this. Jenkins / JENKINS-54325 Support multiple SimplePageDecorators for login and signup page footers Change By: Matt Sicker Status: In Review Resolved Resolution: Fixed Released As: 2.156 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-50696) Evaluate impact on NetBeans workflows
Title: Message Title Jesse Glick updated JENKINS-50696 Jenkins / JENKINS-50696 Evaluate impact on NetBeans workflows Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50696) Evaluate impact on NetBeans workflows
Title: Message Title Jesse Glick updated JENKINS-50696 Jenkins / JENKINS-50696 Evaluate impact on NetBeans workflows Change By: Jesse Glick Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50696) Evaluate impact on NetBeans workflows
Title: Message Title Jesse Glick reopened an issue There was a problem in some circumstances loading projects whose .mvn/maven.config included -Pconsume-incrementals. Fixing. Jenkins / JENKINS-50696 Evaluate impact on NetBeans workflows Change By: Jesse Glick Resolution: Done Status: Resolved 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-50696) Evaluate impact on NetBeans workflows
Title: Message Title Jesse Glick started work on JENKINS-50696 Change By: Jesse Glick 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-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Andrew Lawrence commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I upgraded our jenkins masters from 2.150.1 to 2.164.2 a few days ago. The next day, we were intermittently seeing long page loads. Today, I have consistently seen pages take 15-20 seconds to load. This is from an instance of chrome 71 on Linux; this browser has been open for a very long time (weeks, at least). I did a service jenkins restart on one of the masters, and page loads became fast again from that same client browser, even after logging back into jenkins. If I open a new browser (I opened an instance of Firefox), it sees fast page loads on the server that was just restarted, and on the servers where the jenkins process was not restarted, even after logging into jenkins. If I turn on the AD cache on the jenkins masters, page loads become fast on all machines, even from the long-running client browser. I am unconvinced that AD server performance was the root cause, since page loads are fast from a newly-opened web browser to a jenkins server with the AD cache still turned off. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57074) Version 2.173 creates tmp-files and doesn't delete them
Title: Message Title Daniel Beck updated JENKINS-57074 Jenkins / JENKINS-57074 Version 2.173 creates tmp-files and doesn't delete them Change By: Daniel Beck Status: Fixed but Unreleased Closed Resolution: Won't Do Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56294) dockerfile: ARG in FROM breaks docker inspect
Title: Message Title Dwight Guth commented on JENKINS-56294 Re: dockerfile: ARG in FROM breaks docker inspect This has been fixed in my pull request: https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/311 It would be nice to see some action on this PR so I don't have to keep relying on a manually-built HPI file for this plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56772) Git branch with slashes are double encoded (Jenkins core and blue ocean)
Title: Message Title Gavin Mogan commented on JENKINS-56772 Re: Git branch with slashes are double encoded (Jenkins core and blue ocean) I tried to reproduce it on ci.blueocean and wasn't able to https://ci.blueocean.io/blue/organizations/jenkins/Gavin%20Folder%2Fmbtest/detail/slash%2Ftest/1/pipeline Can you give me a list of steps starting from https://ci.blueocean.io/job/Gavin%20Folder/ that reproduces the error? 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-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Tyler Pickett reopened an issue Additional info has been added, and we're willing to collect additional data as necessary. Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Tyler Pickett Resolution: Incomplete Status: Closed 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-56510) Provide generic issue parser for custom tools
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-56510
Provide generic issue parser for custom tools
Change By:
Ulli Hafner
I have a handful of custom tools to generate custom reports on my code base and/or the compiled results. Right now I am abusing the output format of PMD to get close to the output I want. However, it would be nice if I could generate a file that mapped directly to the fields used by the plugin.This might also be useful for people who do not have admin access to write groovy parsers. They could do some local analysis, then generate this file format.Current Serialization of an {{Issue}} instance using XStream:{code:xml} category type HIGH message 1 2 3 45 663d61b1f-0cac-4e31-8bb9-f390ed1acfe8 description reference origin module-name package-name file-name fingerprint{code} Current Serialization of a {{Report}} instance using XStream:{code :xml }category type HIGH 1 1 2 3 45 6c3b984a3-7f67-4332-953b-27d3943f232c description reference origin module-name package-name file-name fingerprint category type2 1 2 3 45 6fbf2fee0-292f-4991-bd06-d8c5b13ace93 description reference origin module-name package-name file-name fingerprintinfoerror0{code}
Add Comment
[JIRA] (JENKINS-56510) Provide generic issue parser for custom tools
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-56510
Provide generic issue parser for custom tools
Change By:
Ulli Hafner
I have a handful of custom tools to generate custom reports on my code base and/or the compiled results. Right now I am abusing the output format of PMD to get close to the output I want. However, it would be nice if I could generate a file that mapped directly to the fields used by the plugin.This might also be useful for people who do not have admin access to write groovy parsers. They could do some local analysis, then generate this file format. An example Current Serialization of the input file format an {{Issue}} instance using XStream :{code:xml}< issues ?xml version="1.1" encoding="UTF-8"? > Category 1 category Type 1 type WARNING_LOW HIGH Message 1 message 0 1 0 2 0 3 0 4 > 5< / start >< end>663d61b1f-0cac-4e31-8bb9-f390ed1acfe8 < description> Description 1 description < reference>reference origin < moduleName> Module 1 module-name package - name file - name < fingerprint>fingerprint< / fingerprint> issue> {code} Current Serialization of a {{Report}} instance using XStream:{code} < ?xml version="1.1" encoding="UTF-8"?> < issue> Category 2 category Type 2 type WARNING_HIGH HIGH Message 2 1 0 1 0 2 0 3 0 4 > 5< / start >< end>6c3b984a3-7f67-4332-953b-27d3943f232c < description> Description 2 description < reference>reference origin < moduleName> Module module-name package-name file-name fingerprint category type 2 message> 1 2 3 45 6fbf2fee0-292f-4991-bd06-d8c5b13ace93 description reference origin < moduleName> module-name package - name file - name < fingerprint>fingerprint< / fingerprint> issue> issues elements >< infoMessages>info< / code string > error0 {code} If this is of general interest I can post a PR.
Add
[JIRA] (JENKINS-57140) org.apache.commons.jelly.util.SAXParseException: NoClassDefFoundException
Title: Message Title AB S updated an issue Jenkins / JENKINS-57140 org.apache.commons.jelly.util.SAXParseException: NoClassDefFoundException Change By: AB S I am trying to setup jenkins in eclipse with Tomcat.I have followed steps from wiki resource for setting up jenkins with eclipse.But rather than using tomcat sysdeo plugin, I am using the one from sourceforge.net.The problem is when I start tomcat from eclipse, and try to check jenkins in browser, it crashes!!It works fine when run from cmd line.With following error: at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374)at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:613) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3132) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:852) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1140) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:655) at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:350) at org.apache.commons.jelly.JellyContext.compileScript(JellyContext.java:525) ... 117 moreCaused by: org.apache.commons.jelly.util.SAXParseException: Error at (26, 98) of [ file:/C:/Users/jenkins/core/target/classes/lib/form/submit.jelly |file : ///C:/Users/jenkins/core/target/classes/lib/form/submit.jelly] : Could not load class: core so taglib instantiation failed at org.apache.commons.jelly.parser.XMLParser.createSAXException(XMLParser.java:1245) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1029) ... 133 moreCaused by: java.lang.ClassNotFoundException: core at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1955) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1798) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1024) ... 133 moreApr 22, 2019 8:34:13 PM org.apache.commons.jelly.parser.XMLParser createSAXExceptionWARNING: Underlying
[JIRA] (JENKINS-57140) org.apache.commons.jelly.util.SAXParseException: NoClassDefFoundException
Title: Message Title AB S updated an issue Jenkins / JENKINS-57140 org.apache.commons.jelly.util.SAXParseException: NoClassDefFoundException Change By: AB S I am trying to setup jenkins in eclipse with Tomcat.I have followed steps from wiki resource for setting up jenkins with eclipse.But rather than using tomcat sysdeo plugin, I am using the one from sourceforge.net.The problem is when I start tomcat from eclipse, and try to check jenkins in browser, it crashes!! It works fine when run from cmd line.With following error: at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374)at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:613) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3132) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:852) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1140) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:655) at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:350) at org.apache.commons.jelly.JellyContext.compileScript(JellyContext.java:525) ... 117 moreCaused by: org.apache.commons.jelly.util.SAXParseException: Error at (26, 98) of [file:/C:/Users/jenkins/core/target/classes/lib/form/submit.jelly|file:///C:/Users/jenkins/core/target/classes/lib/form/submit.jelly] : Could not load class: core so taglib instantiation failed at org.apache.commons.jelly.parser.XMLParser.createSAXException(XMLParser.java:1245) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1029) ... 133 moreCaused by: java.lang.ClassNotFoundException: core at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1955) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1798) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1024) ... 133 more Apr 22, 2019 8:34:13 PM org.apache.commons.jelly.parser.XMLParser createSAXExceptionWARNING: Underlying exception:
[JIRA] (JENKINS-57140) org.apache.commons.jelly.util.SAXParseException: NoClassDefFoundException
Title: Message Title AB S created an issue Jenkins / JENKINS-57140 org.apache.commons.jelly.util.SAXParseException: NoClassDefFoundException Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-04-22 15:21 Environment: Jenkins 2.x Labels: jenkins Priority: Blocker Reporter: AB S I am trying to setup jenkins in eclipse with Tomcat. I have followed steps from wiki resource for setting up jenkins with eclipse. But rather than using tomcat sysdeo plugin, I am using the one from sourceforge.net. The problem is when I start tomcat from eclipse, and try to check jenkins in browser, it crashes!! It works fine when run from cmd line. With following error: at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374)at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:613) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3132) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:852) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112) at
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Gunter Grodotzki commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 FWIW: we doubled the RAM from 4GB to 8GB instance (with ~50% JVM allocation) - it lasted longer without a crash but ultimately gave in after a couple of days doubled the RAM again, from 8GB to 16GB instance (with ~50% JVM allocation) - so far its lasting So for us that was quite a bump on resource requirements. Doubling is something one might be expecting (also because we were growing with more repositories) - but a 4x bump seemed a bit out of the norm. As long as JVM has enough RAM, the CPU usage is kept relatively low - so for now we are not seeing any issues. 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-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Tyler Pickett commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 I was on vacation last week when Ryan Taylor commented or he would have included a set of thread traces I've attached one that I captured from our instance the week before last. 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-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Tyler Pickett updated an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Tyler Pickett Attachment: jenkinshangWithJstack.6.output.tar.gz 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-57139) Linux agent installer does not work on Java 11
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-57139 Linux agent installer does not work on Java 11 Change By: Baptiste Mathus Labels: java11 java11 -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-42365) Test Connection fails with Rocket.Chat API 0.46.0
Title: Message Title Semenin Ivan commented on JENKINS-42365 Re: Test Connection fails with Rocket.Chat API 0.46.0 0.74.0 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-42365) Test Connection fails with Rocket.Chat API 0.46.0
Title: Message Title Semenin Ivan edited a comment on JENKINS-42365 Re: Test Connection fails with Rocket.Chat API 0.46.0 Rocket.Chat 0.74.0 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-57139) Linux agent installer does not work on Java 11
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-57139 Linux agent installer does not work on Java 11 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-22 13:30 Labels: java11-compatibility Priority: Minor Reporter: Jesse Glick While testing JENKINS-57071 I noticed that the installers do not work at all when the agent is run on Java 11: SEVERE: Failed to load Jenkins.class java.lang.NoClassDefFoundError: Bootstrap pseudo-classloader disabled: java.sql.Date via null at org.apache.commons.beanutils.ConvertUtilsBean.class$(ConvertUtilsBean.java:157) at org.apache.commons.beanutils.ConvertUtilsBean.registerOther(ConvertUtilsBean.java:708) at org.apache.commons.beanutils.ConvertUtilsBean.deregister(ConvertUtilsBean.java:580) at org.apache.commons.beanutils.ConvertUtilsBean.(ConvertUtilsBean.java:164) at org.kohsuke.stapler.Stapler.(Stapler.java:1065) at hudson.model.Node$Mode.(Node.java:597) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.base/java.lang.Class.getEnumConstantsShared(Class.java:3554) at java.base/java.lang.Class.getEnumConstants(Class.java:3530) at jenkins.model.Jenkins.(Jenkins.java:5248) at
[JIRA] (JENKINS-57128) Builds array is not created in version 4
Title: Message Title Michael S commented on JENKINS-57128 Re: Builds array is not created in version 4 I see. How I can process 4.0.0-rc builds in my script to get the SHA1 of the commit? 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-57128) Builds array is not created in version 4
Title: Message Title Mark Waite commented on JENKINS-57128 Re: Builds array is not created in version 4 There is no way to put the data back for builds that ran with git plugin 4.0.0-rc. 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-57128) Builds array is not created in version 4
Title: Message Title Michael S commented on JENKINS-57128 Re: Builds array is not created in version 4 What I can do for the builds that were built with 4.0.0-rc? How I can put the data back? 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-57128) Builds array is not created in version 4
Title: Message Title Mark Waite updated JENKINS-57128 Jenkins / JENKINS-57128 Builds array is not created in version 4 Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate 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-57128) Builds array is not created in version 4
Title: Message Title Mark Waite commented on JENKINS-57128 Re: Builds array is not created in version 4 Rollback to git plugin 3.9.* and git client plugin 2.7.*. Refer to the following duplicates and pull requests: JENKINS-56010 JENKINS-55939 PR-689 to revert the BuildData change 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-57128) Builds array is not created in version 4
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-57128 Builds array is not created in version 4 Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57088) Optional load message content from file
Title: Message Title Anton Potsyus updated JENKINS-57088 Jenkins / JENKINS-57088 Optional load message content from file Change By: Anton Potsyus Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Eric Fontana edited a comment on JENKINS-57116 Re: Version 1.15.1 does not create pods I just tried 1.15.1 and it is broken for me, had to roll back I don't see 1.15.2 as an option yet? 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-57116) Version 1.15.1 does not create pods
Title: Message Title Eric Fontana edited a comment on JENKINS-57116 Re: Version 1.15.1 does not create pods I just tried 1.15. 2 1 and it is broken for me, had to roll back 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-57116) Version 1.15.1 does not create pods
Title: Message Title Eric Fontana commented on JENKINS-57116 Re: Version 1.15.1 does not create pods I just tried 1.15.2 and it is broken for me, had to roll back 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-57088) Optional load message content from file
Title: Message Title Anton Potsyus stopped work on JENKINS-57088 Change By: Anton Potsyus Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57088) Optional load message content from file
Title: Message Title Anton Potsyus started work on JENKINS-57088 Change By: Anton Potsyus 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-57138) Performance issue due to the bundle anonymization
Title: Message Title
Félix Belzunce Arcos updated an issue
Jenkins / JENKINS-57138
Performance issue due to the bundle anonymization
Change By:
Félix Belzunce Arcos
This is a follow-up of JENKINS-54999 In the latest release of the support-core plugin {{support-core:2.56:not-pinned}} we have seen performance issues{code:java}Without anonymization (I have launch 3 times) ~35seconds, and I see at max ~100% CPU usageWith anonymization (I have launch 1 time regarding the time) ~11 minutes, and I see at max ~360% CPU usage{code}The relevant stacktraces are:h4. ThreadDump 1{code:java}"Handling POST //support/generateAllBundles from X.X.X.X : qtp2007328737-1361430" #1361430 prio=5 os_prio=0 tid=0x7efcedfc nid=0x12c4 runnable [0x7efcb3de] java.lang.Thread.State: RUNNABLE at java.util.zip.Deflater.deflateBytes(Native Method) at java.util.zip.Deflater.deflate(Deflater.java:444) - locked <0x000719156578> (a java.util.zip.ZStreamRef) at java.util.zip.Deflater.deflate(Deflater.java:366) at org.apache.commons.compress.archivers.zip.StreamCompressor.deflate(StreamCompressor.java:246) at org.apache.commons.compress.archivers.zip.StreamCompressor.deflateUntilInputIsNeeded(StreamCompressor.java:241) at org.apache.commons.compress.archivers.zip.StreamCompressor.writeDeflated(StreamCompressor.java:222) at org.apache.commons.compress.archivers.zip.StreamCompressor.write(StreamCompressor.java:190) at org.apache.commons.compress.archivers.zip.ZipArchiveOutputStream.write(ZipArchiveOutputStream.java:900) at org.apache.commons.compress.archivers.ArchiveOutputStream.write(ArchiveOutputStream.java:109) at java.io.FilterOutputStream.write(FilterOutputStream.java:77) at java.io.FilterOutputStream.write(FilterOutputStream.java:125) at java.io.FilterOutputStream.write(FilterOutputStream.java:97) at org.apache.commons.io.IOUtils.write(IOUtils.java:1527) at org.apache.commons.io.IOUtils.write(IOUtils.java:1552) at com.cloudbees.jenkins.support.api.FileContent.writeTo(FileContent.java:122) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:314) at com.cloudbees.jenkins.support.SupportAction.doGenerateAllBundles(SupportAction.java:205) at java.lang.invoke.LambdaForm$DMH/695376641.invokeVirtual_L3_V(LambdaForm$DMH) at java.lang.invoke.LambdaForm$BMH/1360969330.reinvoke(LambdaForm$BMH) at java.lang.invoke.LambdaForm$MH/318927722.invoker(LambdaForm$MH) at java.lang.invoke.LambdaForm$MH/1073698081.invokeExact_MT(LambdaForm$MH) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:130) at
[JIRA] (JENKINS-57138) Performance issue due to the bundle anonymization
Title: Message Title
Félix Belzunce Arcos updated an issue
Jenkins / JENKINS-57138
Performance issue due to the bundle anonymization
Change By:
Félix Belzunce Arcos
This is a follow-up of JENKINS-54999 In the latest release of the support-core plugin {{support-core:2.56:not-pinned}} we have seen performance issues{code:java}Without anonymization (I have launch 3 times) ~35seconds, and I see at max ~100% CPU usageWith anonymization (I have launch 1 time regarding the time) ~11 minutes, and I see at max ~360% CPU usage{code}The relevant stacktraces are:h4. ThreadDump 1{code:java}"Handling POST //support/generateAllBundles from X.X.X.X : qtp2007328737-1361430" #1361430 prio=5 os_prio=0 tid=0x7efcedfc nid=0x12c4 runnable [0x7efcb3de] java.lang.Thread.State: RUNNABLE at java.util.zip.Deflater.deflateBytes(Native Method) at java.util.zip.Deflater.deflate(Deflater.java:444) - locked <0x000719156578> (a java.util.zip.ZStreamRef) at java.util.zip.Deflater.deflate(Deflater.java:366) at org.apache.commons.compress.archivers.zip.StreamCompressor.deflate(StreamCompressor.java:246) at org.apache.commons.compress.archivers.zip.StreamCompressor.deflateUntilInputIsNeeded(StreamCompressor.java:241) at org.apache.commons.compress.archivers.zip.StreamCompressor.writeDeflated(StreamCompressor.java:222) at org.apache.commons.compress.archivers.zip.StreamCompressor.write(StreamCompressor.java:190) at org.apache.commons.compress.archivers.zip.ZipArchiveOutputStream.write(ZipArchiveOutputStream.java:900) at org.apache.commons.compress.archivers.ArchiveOutputStream.write(ArchiveOutputStream.java:109) at java.io.FilterOutputStream.write(FilterOutputStream.java:77) at java.io.FilterOutputStream.write(FilterOutputStream.java:125) at java.io.FilterOutputStream.write(FilterOutputStream.java:97) at org.apache.commons.io.IOUtils.write(IOUtils.java:1527) at org.apache.commons.io.IOUtils.write(IOUtils.java:1552) at com.cloudbees.jenkins.support.api.FileContent.writeTo(FileContent.java:122) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:314) at com.cloudbees.jenkins.support.SupportAction.doGenerateAllBundles(SupportAction.java:205) at java.lang.invoke.LambdaForm$DMH/695376641.invokeVirtual_L3_V(LambdaForm$DMH) at java.lang.invoke.LambdaForm$BMH/1360969330.reinvoke(LambdaForm$BMH) at java.lang.invoke.LambdaForm$MH/318927722.invoker(LambdaForm$MH) at java.lang.invoke.LambdaForm$MH/1073698081.invokeExact_MT(LambdaForm$MH) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:130) at
[JIRA] (JENKINS-57138) Performance issue due to the bundle anonymization
Title: Message Title
Félix Belzunce Arcos created an issue
Jenkins / JENKINS-57138
Performance issue due to the bundle anonymization
Issue Type:
Bug
Assignee:
Emilio Escobar
Components:
support-core-plugin
Created:
2019-04-22 12:22
Priority:
Major
Reporter:
Félix Belzunce Arcos
This is a follow-up of JENKINS-54999 In the latest release of the support-core plugin {{support-core:2.56:not-pinned }} we have seen performance issues
Without anonymization (I have launch 3 times)
~35seconds, and I see at max ~100% CPU usage
With anonymization (I have launch 1 time regarding the time)
~11 minutes, and I see at max ~360% CPU usage
The relevant stacktraces are: ThreadDump 1
"Handling POST //support/generateAllBundles from X.X.X.X : qtp2007328737-1361430" #1361430 prio=5 os_prio=0 tid=0x7efcedfc nid=0x12c4 runnable [0x7efcb3de]
java.lang.Thread.State: RUNNABLE
at java.util.zip.Deflater.deflateBytes(Native Method)
at java.util.zip.Deflater.deflate(Deflater.java:444)
- locked <0x000719156578> (a java.util.zip.ZStreamRef)
at java.util.zip.Deflater.deflate(Deflater.java:366)
at org.apache.commons.compress.archivers.zip.StreamCompressor.deflate(StreamCompressor.java:246)
at org.apache.commons.compress.archivers.zip.StreamCompressor.deflateUntilInputIsNeeded(StreamCompressor.java:241)
at org.apache.commons.compress.archivers.zip.StreamCompressor.writeDeflated(StreamCompressor.java:222)
at
[JIRA] (JENKINS-47772) Docs on use of pipeline junit action should cover making results optional
Title: Message Title Mark Waite updated JENKINS-47772 Jenkins / JENKINS-47772 Docs on use of pipeline junit action should cover making results optional Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47772) Docs on use of pipeline junit action should cover making results optional
Title: Message Title Mark Waite updated JENKINS-47772 Confirmed that the web site now describes the parameter Jenkins / JENKINS-47772 Docs on use of pipeline junit action should cover making results optional Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57137) Add possibility to use environment variables in parameter definition
Title: Message Title
Paul Luchyn created an issue
Jenkins / JENKINS-57137
Add possibility to use environment variables in parameter definition
Issue Type:
Improvement
Assignee:
Boguslaw Klimas
Components:
git-parameter-plugin
Created:
2019-04-22 11:56
Priority:
Major
Reporter:
Paul Luchyn
It would be nice to have a possibility to use environment variables in the parameter definition, In my case I have a big number of jobs specifying the same git parameter (branch), but for all these jobs I want to specify the same default value. I have tried to do the following:
${MYPARAM}
and
$MYPARAM
but no luck.
Add Comment
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Martin Reinhardt commented on JENKINS-57116 Re: Version 1.15.1 does not create pods will give it tomorrow a try and provide feedback. Thanks for the fast fix 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-57116) Version 1.15.1 does not create pods
Title: Message Title Martin Reinhardt updated JENKINS-57116 Jenkins / JENKINS-57116 Version 1.15.1 does not create pods Change By: Martin Reinhardt Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Martin Reinhardt assigned an issue to Martin Reinhardt Jenkins / JENKINS-57116 Version 1.15.1 does not create pods Change By: Martin Reinhardt Assignee: Carlos Sanchez Martin Reinhardt 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-57116) Version 1.15.1 does not create pods
Title: Message Title Martin Reinhardt started work on JENKINS-57116 Change By: Martin Reinhardt 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-57116) Version 1.15.1 does not create pods
Title: Message Title Carlos Sanchez commented on JENKINS-57116 Re: Version 1.15.1 does not create pods try 1.15.2 just released 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-57116) Version 1.15.1 does not create pods
Title: Message Title Carlos Sanchez edited a comment on JENKINS-57116 Re: Version 1.15.1 does not create pods this must be caused by the same issue as JENKINS-57112 because it's the only change in 1. 5 15 .1Can you provide your pod definition? is it using yaml ? 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-57112) Version 1.15.1 will not persist raw yaml
Title: Message Title Carlos Sanchez updated JENKINS-57112 Jenkins / JENKINS-57112 Version 1.15.1 will not persist raw yaml Change By: Carlos Sanchez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Carlos Sanchez commented on JENKINS-57116 Re: Version 1.15.1 does not create pods this must be caused by the same issue as JENKINS-57112 because it's the only change in 1.5.1 Can you provide your pod definition? is it using yaml ? 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-57112) Version 1.15.1 will not persist raw yaml
Title: Message Title Carlos Sanchez updated JENKINS-57112 Jenkins / JENKINS-57112 Version 1.15.1 will not persist raw yaml Change By: Carlos Sanchez Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57112) Version 1.15.1 will not persist raw yaml
Title: Message Title Carlos Sanchez started work on JENKINS-57112 Change By: Carlos Sanchez 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-57129) java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd)
Title: Message Title werner hans updated an issue Jenkins / JENKINS-57129 java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd) Change By: werner hans Priority: Minor Trivial 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-57129) java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd)
Title: Message Title
werner hans updated an issue
Jenkins / JENKINS-57129
java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd)
Change By:
werner hans
Hi,following behaviour is very similar to JENKINS-56888, with another cgroup pattern. Change [https://github.com/jenkinsci/docker-workflow-plugin/pull/169] might be too restrictive.Szenario, cf. Field Environment with the following configuration in Jenkins:- pipeline script (tried both with groovy sandbox unchecked and checked):{code:java}pipeline {agent {docker {image 'xxx'}}stages {stage('Build') { steps {sh 'echo "abc"' }}}}{code} - console output of a build:{code:java}Started by user yyyRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/abcd[Pipeline] {[Pipeline] sh+ docker inspect -f . xxx.[Pipeline] withDockerContainer[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Unexpected cgroup syntax /docker/f334457e283784c7aac6cbf6245c135037a0c1cd36fd983a285f67ac7d1e0383/system.slice/jenkins.service at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:60) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:45) at org.jenkinsci.plugins.docker.workflow.client.ControlGroup.getContainerId(ControlGroup.java:37) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.getContainerIdIfContainerized(DockerClient.java:336) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:159) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176)...{code}Does jenkins check its own cgroup?{code:java}ps -xp 1310:1310 ?Ssl2:12 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib...cat
[JIRA] (JENKINS-57129) java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd)
Title: Message Title werner hans updated an issue Jenkins / JENKINS-57129 java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd) Change By: werner hans Environment: RHEL 8 betaJenkins 2.173 ( - rpm based installation, running Installation- started as service, Service- running as in docker container ) docker 18.09.2Jenkins container/Docker host on same machine - using shared binary, socket via bind mounts 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-57129) java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd)
Title: Message Title werner hans updated an issue Jenkins / JENKINS-57129 java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd) Change By: werner hans Summary: java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd) 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-42365) Test Connection fails with Rocket.Chat API 0.46.0
Title: Message Title Renat Zaripov commented on JENKINS-42365 Re: Test Connection fails with Rocket.Chat API 0.46.0 In my case versions are: Rocket.Chat 0.73.2 RocketChat notifier 1.4.2 Jenkins 2.164.2 Interesting fact, that notifications delivering. But connection test fails with error, described early. I'm set value of Webhook Token Credential ID field as - None - 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-56860) Rebuild plugin records incorrect "Started by user"
Title: Message Title lsb want commented on JENKINS-56860 Re: Rebuild plugin records incorrect "Started by user" I got this problem too 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-57136) Allow users to customize docker timeouts
Title: Message Title Keunhong Lee created an issue Jenkins / JENKINS-57136 Allow users to customize docker timeouts Issue Type: New Feature Assignee: Unassigned Components: docker-workflow-plugin, pipeline Created: 2019-04-22 08:04 Environment: Jenkins installed directly to a Debian LXC and docker is installed inside the LXC. Jenkins runs outside the docker but the user 'jenkins' has 'docker' group access. Labels: configuration pipeline Priority: Major Reporter: Keunhong Lee Though docker enables fast creation of containers, docker is still slow when being executed under legacy environment (e.g. dir file system). Though the timeout for docker commands has been increased to 180/300 seconds by https://issues.jenkins-ci.org/browse/JENKINS-42322, I think the timeout should be configurable. I sometimes get failure like this: ERROR: Timeout after 180 seconds [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline GitHub has been notified of this commit’s build result java.io.IOException: Failed to run image ''. Error: However, the same code just succeeded its build few minutes ago. That's because the execution time of a docker command varies depending on the system load. In my example, it
[JIRA] (JENKINS-56798) Container name validation doesn't work with env variables
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-56798 Container name validation doesn't work with env variables Change By: Jie Shen Status: In Progress Resolved Resolution: Fixed Released As: 0.1.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57135) Favorite Plugin causes Exception : Caught exception evaluating: h.getIconFilePath(action)
Title: Message Title Dimas Rizky created an issue Jenkins / JENKINS-57135 Favorite Plugin causes Exception : Caught exception evaluating: h.getIconFilePath(action) Issue Type: Bug Assignee: James Dumay Components: favorite-plugin Created: 2019-04-22 06:50 Environment: Favorite : 2.3.2 Jenkins : 2.173 Priority: Minor Reporter: Dimas Rizky I got this error after updating my favorite plugins to the latest version, any clue ? I got this after updating my jenkins version, and thats makes me update my favorite-plugins too. Thus, this does not causing anything harmful on the jenkins, it's just showed lot of warning on log whenever I try to open the jobs that previously had favorite activated to it Apr 22, 2019 1:41:09 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: h.getIconFilePath(action) in /jenkins/job/Insuretech/view/Build/job/insuretech%20Build%20-%20Production/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.plugins.favorite.user.FavoriteUserProperty.isJobFavorite(FavoriteUserProperty.java:106) at hudson.plugins.favorite.Favorites.isFavorite(Favorites.java:45) at hudson.plugins.favorite.project.FavoriteProjectAction.isFavorite(FavoriteProjectAction.java:94) at hudson.plugins.favorite.project.FavoriteProjectAction.getIconFileName(FavoriteProjectAction.java:30) at hudson.Functions.getIconFilePath(Functions.java:1071) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at
[JIRA] (JENKINS-57134) Passing test parameters from Jenkins to ALM for API tests
Title: Message Title Anda Sorina Laakso updated an issue Jenkins / JENKINS-57134 Passing test parameters from Jenkins to ALM for API tests Change By: Anda Sorina Laakso Summary: Passing test parameters from Jenkins to ALM does not work for API Tests tests 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-57134) Passing test parameters from Jenkins to ALM does not work for API Tests
Title: Message Title Anda Sorina Laakso updated an issue Jenkins / JENKINS-57134 Passing test parameters from Jenkins to ALM does not work for API Tests Change By: Anda Sorina Laakso Issue Type: Bug Story 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-57134) Passing test parameters from Jenkins to ALM does not work for API Tests
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57134 Passing test parameters from Jenkins to ALM does not work for API Tests Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:32 Labels: plugin UFT Priority: Major Reporter: Anda Sorina Laakso [Jenkins][Test Parameters][API] Passing test parameters from Jenkins to ALM does not work for API Tests Steps to reproduce the defect : 1. Add a parametrized API test in ALM 2. Create a job of type "Execute Micro Focus functional tests from Micro Focus ALM" 3. Add test parameters for the API tests e.g: Root\Jenkins_TestParameters\TestSet "ParamAPI1": "7", "RequestParam1" : "978910134" 4. Execute the job Expected Result : Parameters are not taken into account when running the test in ALM. Parameters set in Jenkins should override the actual values set in ALM. Actual Result : Actual parameters set in ALM are used instead Detected in build: ++ Jenkins 5.7 Regression from version\build (if applicable): Additional Notes: Only for API tests. API test used attached
[JIRA] (JENKINS-57133) Test result link to ALM is pointing to wrong module
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57133 Test result link to ALM is pointing to wrong module Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:31 Labels: plugin UFT Priority: Major Reporter: Anda Sorina Laakso Steps to reproduce the defect : 1. Run any test from ALM in Jenkins 2. Open Console and check run output 3. Find link to jenkins result Expected Result : The link should be able to open target result Actual Result : The link is point to Test lab but it should point to Test runs module. So it cannot open target result Detected in build: Add Comment
[JIRA] (JENKINS-57132) Not userfriendly grouping of test results for running from file system
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57132 Not userfriendly grouping of test results for running from file system Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:31 Labels: plugin UFT Priority: Minor Reporter: Anda Sorina Laakso Steps to reproduce the defect : 1. Create job, on build step select: "Execute HP tests from file system" 2. In field test put path to mtbx file, and direct pathes to tests 3. Build the job Detected in build: 4.5.0-SNAPSHOT (private-cd8b870c-kazaky) Expected Result : If confugured to run tests directly from file system, not group results to class Actual Result : Not userfriendly grouping of test results for running from file system (see attached snapshot) 4.5.0-SNAPSHOT (private-cd8b870c-kazaky) Add Comment
[JIRA] (JENKINS-57131) Unable to start second time execution API test from ALM side, in case if 1 run aborted by timeout
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57131 Unable to start second time execution API test from ALM side, in case if 1 run aborted by timeout Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:30 Labels: plugin UFT Priority: Major Reporter: Anda Sorina Laakso Steps to reproduce the defect : 1. Install plugin version 4.5 or 5.0 2. Create job for run test from ALM 3. Create simple API test and save in ALM 4. Add created test to test set 5. Run job 6. Now set up timeout to 1 second. 7. Run job 8. Remove timeout and try run job again Expected Result : job running Actual Result : UFT cant start and job failed ++ Add Comment
[JIRA] (JENKINS-57130) Multiple issues
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-57130 Multiple issues Issue Type: Bug Assignee: Anda Sorina Laakso Components: hp-application-automation-tools-plugin Created: 2019-04-22 06:20 Priority: Major Reporter: Anda Sorina Laakso [Jenkins][Test Parameters][API] Passing test parameters from Jenkins to ALM does not work for API Tests [Jenkins][UI] Configuration view issues when scrolling at the bottom of the page Jenkins plugin : Unable to start second time execution API test from ALM side, in case if 1 run aborted by timeout [Jenkins CI Plugin]: Not userfriendly grouping of test results for running from file system [Jenkins Plugin] Test result link to ALM is pointing to wrong module Add Comment
