[JIRA] (JENKINS-28253) Archiving hangs on named pipes
Title: Message Title Marc Benstein commented on JENKINS-28253 Re: Archiving hangs on named pipes This is still happening with Jenkins ver 2.176.3 OpenJDK 1.8.0_201 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.162682.143090000.3689.1569270300221%40Atlassian.JIRA.
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Marc Benstein commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log This seems similar to my issue with v0.6.2. This was working in v0.5.x I have a freestyle project where I have enabled ansi color with xterm. A single shell command with: echo "testing-1.2.300" | grep -E --color=always '[0-9]+.[0-9]+.[0-9]+' Results in: 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.196206.1544605559000.7501.1566430380434%40Atlassian.JIRA.
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Marc Benstein updated an issue Jenkins / JENKINS-55139 ansicolor 0.6.0 shows terminal escape sequences in console log Change By: Marc Benstein Attachment: image-2019-08-21-16-31-39-960.png 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.196206.1544605559000.7479.1566430320725%40Atlassian.JIRA.
[JIRA] (JENKINS-49173) Maximum Concurrent Builds Per Node option not respected for Declarative Pipeline
Title: Message Title Marc Benstein edited a comment on JENKINS-49173 Re: Maximum Concurrent Builds Per Node option not respected for Declarative Pipeline We would love to see this fixed. We kind of have a workaround using labels. But throttling with categories in the options section of a declarative pipeline would be best. 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.188010.1516904811000.5745.1566256440298%40Atlassian.JIRA.
[JIRA] (JENKINS-49173) Maximum Concurrent Builds Per Node option not respected for Declarative Pipeline
Title: Message Title Marc Benstein commented on JENKINS-49173 Re: Maximum Concurrent Builds Per Node option not respected for Declarative Pipeline We would love to see this fixed. We kind of have a workaround using labels. But throttling with categories would be best. 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.188010.1516904811000.5735.1566256320282%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Marc Benstein commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors I'm seeing this same behavior after updating to 2.176.1. They do not seem to be disappearing automatically. 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.199072.1556795988000.1797.1560783000167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47611) RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion
Title: Message Title Marc Benstein updated an issue Jenkins / JENKINS-47611 RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion Change By: Marc Benstein Labels: JEP-200 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43033) Suppress Sleep Step Output
Title: Message Title Marc Benstein updated an issue Jenkins / JENKINS-43033 Suppress Sleep Step Output Change By: Marc Benstein Summary: Suppress Sleep logging Step Output Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-40432) writeMavenPom throws class cast exception when creating a new pom file
Title: Message Title
Marc Benstein edited a comment on JENKINS-40432
Re: writeMavenPom throws class cast exception when creating a new pom file
Here's a workaround \ { \{ code:java} writeFile file: 'pom.xml', text: '4.0.0' def pom = readMavenPom() pom.artifactId = 'some.id' pom.groupId = 'org.something' pom.version = '1.0.0-SNAPSHOT' pom.packaging = 'zip'writeMavenPom model: pom {code } }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-40432) writeMavenPom throws class cast exception when creating a new pom file
Title: Message Title
Marc Benstein edited a comment on JENKINS-40432
Re: writeMavenPom throws class cast exception when creating a new pom file
Here's a workaround \ { \ { }} writeFile file: 'pom.xml', text: '4.0.0'def pom = readMavenPom() pom.artifactId = 'some.id' pom.groupId = 'org.something' pom.version = '1.0.0-SNAPSHOT' pom.packaging = 'zip'writeMavenPom model: pom }}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-40432) writeMavenPom throws class cast exception when creating a new pom file
Title: Message Title
Marc Benstein commented on JENKINS-40432
Re: writeMavenPom throws class cast exception when creating a new pom file
Here's a workaround {{}} writeFile file: 'pom.xml', text: '4.0.0' def pom = readMavenPom() pom.artifactId = 'some.id' pom.groupId = 'org.something' pom.version = '1.0.0-SNAPSHOT' pom.packaging = 'zip' writeMavenPom model: pom
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-42817) readTrusted Pipeline from SCM only works in */master
Title: Message Title Marc Benstein updated an issue Jenkins / JENKINS-42817 readTrusted Pipeline from SCM only works in */master Change By: Marc Benstein Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42817) readTrusted Pipeline from SCM only works in */master
Title: Message Title
Marc Benstein updated an issue
Jenkins / JENKINS-42817
readTrusted Pipeline from SCM only works in */master
Change By:
Marc Benstein
Using a branch with Pipeline from SCM breaks readTrusted. The following snippet only works from */master and not */bugfix/break-readTrusted. See [https://github.com/initialzero/jenkins-break-readtrusted.git] with branch and pipeline from scm.{code:java}#!groovynode { stage('test') { def trustedText = readTrusted 'foo.properties' echo trustedText }}{code} Error message from Jenkins is:ERROR: ‘readTrusted’ is only available when using “Multibranch Pipeline” or “Pipeline script from SCM”
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-43033) Sleep logging
Title: Message Title Marc Benstein created an issue Jenkins / JENKINS-43033 Sleep logging Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2017/Mar/22 3:10 PM Priority: Trivial Reporter: Marc Benstein An option to suppress sleep output from the sleep step is essential for readability of logs. I use sleep to wait for conditions within parallel steps and having the sleep step output sleep 5 seconds over and over in the logs makes reading them next to impossible. Please provide an option to suppress all output to logs. Add Comment
[JIRA] (JENKINS-42817) readTrusted Pipeline from SCM only works in */master
Title: Message Title
Marc Benstein created an issue
Jenkins / JENKINS-42817
readTrusted Pipeline from SCM only works in */master
Issue Type:
Bug
Assignee:
Denis Saponenko
Components:
pipeline-multibranch-defaults-plugin
Created:
2017/Mar/15 7:49 PM
Environment:
jenkins 2.50 Pipeline from SCM
Priority:
Minor
Reporter:
Marc Benstein
Using a branch with Pipeline from SCM breaks readTrusted. The following snippet only works from */master and not */bugfix/break-readTrusted. See https://github.com/initialzero/jenkins-break-readtrusted.git with branch and pipeline from scm.
#!groovy
node {
stage('test') {
def trustedText = readTrusted 'foo.properties'
echo trustedText
}
}
Add Comment
