[JIRA] (JENKINS-56484) timestamper 1.9 breaks warnings-ng's ability to find source files
Title: Message Title
Steve Mokris updated an issue
Jenkins / JENKINS-56484
timestamper 1.9 breaks warnings-ng's ability to find source files
Change By:
Steve Mokris
In timestamper 1.9, the [log format was changed|https://plugins.jenkins.io/timestamper#Timestamper-1.9(2019-02-07)]. When I enable timestamper on a pipeline job, then scan it with warnings-ng, it detects errors but incorrectly parses the filename — it considers the timestamp to be part of the filename.To reproduce the issue, install both plugins and run this pipeline job:{code:java}node {timestamps {sh """echo '#error This is an error.' > test.cclang test.c || true"""recordIssues tools: [clang(id: 'clang', name: 'clang')]}}{code}and the console log says:{code:java}00:00:01.047 test.c:1:2: error: This is an error.…00:00:06.276 [clang] [ERROR] Can't resolve absolute paths for some files:00:00:06.276 [clang] [ERROR] - [2019-03-08T15:46:53.268Z] test.c00:00:06.276 [clang] [ERROR] Can't create fingerprints for some files:00:00:06.276 [clang] [ERROR] - '[2019-03-08T15:46:53.268Z] test.c', IO exception has been thrown: java.nio.file.NoSuchFileException: [2019-03-08T15:46:53.268Z] test.c{code}
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
[JIRA] (JENKINS-56484) timestamper 1.9 breaks warnings-ng's ability to find source files
Title: Message Title
Steve Mokris created an issue
Jenkins / JENKINS-56484
timestamper 1.9 breaks warnings-ng's ability to find source files
Issue Type:
Bug
Assignee:
Steven G Brown
Components:
timestamper-plugin, warnings-ng-plugin
Created:
2019-03-08 16:04
Environment:
Jenkins 2.166 timestamper-plugin 1.9 warnings-ng-plugin 3.0.3
Priority:
Major
Reporter:
Steve Mokris
In timestamper 1.9, the log format was changed. When I enable timestamper on a pipeline job, then scan it with warnings-ng, it detects errors but incorrectly parses the filename — it considers the timestamp part of the filename. To reproduce the issue, install both plugins and run this pipeline job:
node {
timestamps {
sh """
echo '#error This is an error.' > test.c
clang test.c || true
"""
recordIssues tools: [clang(id: 'clang', name: 'clang')]
}
}
and the console log says:
00:00:01.047 test.c:1:2: error: This is an error.
…
00:00:06.276 [clang] [ERROR] Can't resolve absolute paths for some files:
00:00:06.276 [clang] [ERROR] - [2019-03-08T15:46:53.268Z] test.c
00:00:06.276 [clang] [ERROR] Can't create fingerprints for some files:
00:00:06.276 [clang] [ERROR] - '[2019-03-08T15:46:53.268Z] test.c', IO exception has been thrown:
[JIRA] (JENKINS-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
Steve Mokris edited a comment on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
A workaround in the meantime: { { code} retry(5) { }} {{ ret = sh returnStatus: true, script: 'some-failure-prone-script' }} {{ if (ret) { }} {{ sleep time: 30, unit: 'SECONDS' }} {{ error ' }}{{ some-failure-prone-script failed' }} {{ } }} {{ } {code } } …but there's no way to know when we're on the last retry attempt (see JENKINS-49341), so it unnecessarily waits 30 seconds when after the last retry attempt fails.
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-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
Steve Mokris commented on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
A workaround in the meantime: retry(5) { ret = sh returnStatus: true, script: 'some-failure-prone-script' if (ret) { sleep time: 30, unit: 'SECONDS' error 'some-failure-prone-script failed' {{ }}} {{ }}} …but there's no way to know when we're on the last retry attempt (see JENKINS-49341), so it unnecessarily waits 30 seconds when the last retry attempt fails.
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-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title Steve Mokris created an issue Jenkins / JENKINS-54735 Pipeline retry clause: optionally delay between retries Issue Type: Improvement Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2018-11-20 17:24 Labels: pipeline Priority: Major Reporter: Steve Mokris I use a retry block to perform requests on a remote server that I don't control (e.g., Apple's Code Signing or Notarization service), and sometimes that remote server is offline. Currently retry immediately retries upon failure, so when the remote server is offline for an extended period of time, my pipeline project quickly retries and then the build fails. It would be nice to have the ability to make retry wait after each failure, with optional exponential backoff (doubling the wait time after each failure), to give these builds a greater chance of success. For example: retry(tries:5, waitSecondsBetweenFailures:30, doubleWaitTimeAfterEachFailure:true) Add Comment
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title Steve Mokris commented on JENKINS-39174 Re: Help text for projectName does not describe all permitted values I drafted a wiki page based on Jesse Glick's comments: https://wiki.jenkins.io/display/JENKINS/How+to+reference+another+project+by+name …and a PR: https://github.com/jenkinsci/copyartifact-plugin/pull/107 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-24900) Show the duration per build step / post-build action
Title: Message Title Steve Mokris closed an issue as Won't Do I've recreated my jobs as pipelines, which provide per-build-step timings. Closing this issue since I no longer have a need for it in freestyle builds as I initially proposed. Jenkins / JENKINS-24900 Show the duration per build step / post-build action Change By: Steve Mokris Status: Open Closed Resolution: Won't Do 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
[JIRA] (JENKINS-24904) Add option to archive artifacts in the background
Title: Message Title Steve Mokris closed an issue as Won't Do I've recreated my jobs as pipelines, with the archiveArtifacts build step wrapped in a parallel block, which is working nicely so far. Closing this issue since I no longer have a need for it in freestyle builds as I initially proposed. Jenkins / JENKINS-24904 Add option to archive artifacts in the background Change By: Steve Mokris Status: Open Closed Resolution: Won't Do 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"
[JIRA] (JENKINS-40198) allow scanning and retrieval of a pipeline job inside the pipeline
Title: Message Title Steve Mokris updated an issue Jenkins / JENKINS-40198 allow scanning and retrieval of a pipeline job inside the pipeline Change By: Steve Mokris It would be great if the BFA could be called in a pipeline to scan the current pipeline and get a current list of failure reasons. (as extra things can happen after the pipeline step - it would not be the final list of all failure reasons)This list of failure reasons could then be used to pass to a hipchat or mail step so that more information is available that than "Hey the build failed". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [build-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
Steve Mokris
commented on JENKINS-17658
Provide a token so that build failure causes can be included in build failure emails
I'm using the Email-ext plugin. In the "Editable Email Notification" post-build step, I added this to the "Default Content" box:
${BUILD_FAILURE_ANALYZER, includeTitle=true, includeIndications=true, useHtmlFormat=true}
…which works for me.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [timestamper] (JENKINS-24900) Show the duration per build step / post-build action
Steve Mokris created JENKINS-24900 Show the duration per build step / post-build action Issue Type: New Feature Assignee: stevengbrown Components: timestamper Created: 28/Sep/14 3:35 PM Description: Timestamper makes it easy to see details about how long individual commands take (thanks!). But some of my projects have many build steps, each with many commands that generate a ton of console log output, so it's time-consuming to wade through the console output to answer the big-picture question "why does this job take so long to build?". It would be handy if Timestamper could provide a summary table (maybe on the build overview page) showing the total duration of each build step and post-build action, so it's easy to see which steps to focus on when I need to improve the build speed. The table could link to the first console line of each build step. Project: Jenkins Labels: performance Priority: Major Reporter: Steve Mokris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-24904) Add option to archive artifacts in the background
Steve Mokris created JENKINS-24904 Add option to archive artifacts in the background Issue Type: Improvement Assignee: Unassigned Components: core Created: 28/Sep/14 8:33 PM Description: I have a job that takes about 2 hours to run — 15 minutes to build, 1 hour to run automated tests, and 45 minutes to archive the artifacts (the node's upstream internet connection isn't very fast). Would it make sense to add the option to start archiving the artifacts right after a certain build step completes, and archive in parallel with the remaining build steps? In a case like this, it could reduce the job from 2 hours to 1 hour 15 minutes. Project: Jenkins Labels: performance Priority: Major Reporter: Steve Mokris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
Steve Mokris commented on JENKINS-17658 Provide a token so that build failure causes can be included in build failure emails Works nicely. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ansicolor] (JENKINS-24378) Add support for 256-color and 24-bit-color ANSI escape sequences
Steve Mokris created JENKINS-24378 Add support for 256-color and 24-bit-color ANSI escape sequences Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: ansicolor Created: 21/Aug/14 7:29 PM Project: Jenkins Priority: Major Reporter: Steve Mokris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xunit] (JENKINS-20024) com.thoughtworks.xstream.converters.ConversionException: QTestLibType on Jenkins 1.524 and later
Steve Mokris commented on JENKINS-20024 com.thoughtworks.xstream.converters.ConversionException: QTestLibType on Jenkins 1.524 and later Yes, I just updated to version 1.81, and it's working nicely. Thanks, Gregory! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [image-gallery] (JENKINS-21109) Provide an option to show the image gallery on its own page
Steve Mokris created JENKINS-21109 Provide an option to show the image gallery on its own page Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: image-gallery Created: 20/Dec/13 4:07 PM Description: I love that the Image Gallery plugin allows me to easily see an overview of images generated by my build process. But my build process generates dozens of large images, and now the Build Status page takes a long time to load. Could the Image Gallery plugin provide an option to move the gallery to its own page (listed among the other build details links in the left navigation bar), to make the Build Status page smaller? Project: Jenkins Priority: Major Reporter: Steve Mokris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
