[JIRA] (JENKINS-49833) getApiJson: (url=...) failed due to Http error #403
Title: Message Title Henryk Paluch created an issue Jenkins / JENKINS-49833 getApiJson: (url="" failed due to Http error #403 Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2018-03-02 07:40 Environment: tfs-plugin 5.126.0, Jenkins 2.89.4, Oracle JDK 1.8.0_144-b01/amd64, Windows Server 2008 R2/amd64 Priority: Trivial Reporter: Henryk Paluch After job (which uses TFS plugin) completion we see following errors in jenkins.err.log: [timestamp omitted] hudson.plugins.tfs.JenkinsEventNotifier getApiJson WARNING: ERROR: getApiJson: (url="" failed due to Http error #403 Fortunately these errors seems to be harmless to us. Possible cause We have configured Jenkins Security to "Logged-in users can do anything" mode without "Allow anonymous read access" (so user must be logged-in to access anything in Jenkins). It seems that the getApiJson is calling Jenkins without needed authentication info in such case. Add Comment
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Danny Tamsen commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Dalmo Santos _> Another possible solution is to utilize the 'customWorkspace' element as mentioned earlier. It would look something like:
agent{
node{
label 'my-node-label'
customWorkspace "MyFixedLocation/MyPipelineName_${BRANCH_NAME}"
}
}
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-38452) imageName() drops registry prefix outside of withRegistry() block
Title: Message Title Christopher Bayliss commented on JENKINS-38452 Re: imageName() drops registry prefix outside of withRegistry() block Or may use case: Pull an image from one repository and publish it to another. You just can't do it without resorting to the shell. 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-49832) The hyperlink to a JUnit Test report subpage for a test group named "run" thinks it is the build information link
Title: Message Title retronym updated an issue Jenkins / JENKINS-49832 The hyperlink to a JUnit Test report subpage for a test group named "run" thinks it is the build information link Change By: retronym Summary: The hyperlink to a JUnit Test report subpage for a test group named "run" thinks it is the the build information link 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-49832) The hyperlink to a JUnit Test report subpage for a test group named "run" thinks it is the the build information link
Title: Message Title retronym commented on JENKINS-49832 Re: The hyperlink to a JUnit Test report subpage for a test group named "run" thinks it is the the build information link I should note that we're generating the XML files from a different testing tool, hence odd looking classname and name attributes. I haven't tried to reproduce this with analagously named Junit classes. 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-49832) The hyperlink to a JUnit Test report subpage for a test group named "run" thinks it is the the build information link
Title: Message Title retronym updated an issue Jenkins / JENKINS-49832 The hyperlink to a JUnit Test report subpage for a test group named "run" thinks it is the the build information link Change By: retronym Attachment: junit-run.png 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-49832) The hyperlink to a JUnit Test report subpage for a test group named "run" thinks it is the the build information link
Title: Message Title retronym created an issue Jenkins / JENKINS-49832 The hyperlink to a JUnit Test report subpage for a test group named "run" thinks it is the the build information link Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2018-03-02 05:55 Environment: Jenkins ver. 2.105 Version 64.0.3282.186 (Official Build) (64-bit) Mac OS 10.13.3 Labels: link UI Priority: Minor Reporter: retronym Given this build definition: cat < test.files.run.xml "iMac2016.local" name="test.files.run" tests="2" errors="0" failures="0" skipped="0" time="2.996"> "test.files.run" name="constant-optimization.scala" time="2.888"> "test.files.run" name="groupby.scala" time="2.996"> EOF cat < test.files.run2.xml "iMac2016.local" name="test.files.run2" tests="2" errors="0" failures="0" skipped="0" time="2.996"> "test.files.run2" name="constant-optimization.scala" time="2.888"> "test.files.run2" name="groupby.scala" time="2.996"> EOF
[JIRA] (JENKINS-48374) Pipeline parameters step allows duplicates
Title: Message Title suren pi edited a comment on JENKINS-48374 Re: Pipeline parameters step allows duplicates Param define duplicates is allowed in my many program language, I think it's ok. 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-48374) Pipeline parameters step allows duplicates
Title: Message Title suren pi commented on JENKINS-48374 Re: Pipeline parameters step allows duplicates Param define duplicates is allowed in my program language, I think it's ok. 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-46379) withEnv mess with Job parameter (not case sensitive)
Title: Message Title suren pi edited a comment on JENKINS-46379 Re: withEnv mess with Job parameter (not case sensitive) I thought it should be a issue, anyone will take care of it Can you give your plugin versioin ? Because it'is all right. My plugin version like bleow:Pipeline: Basic Steps 2.6[~shaiton] 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-46379) withEnv mess with Job parameter (not case sensitive)
Title: Message Title suren pi assigned an issue to suren pi Jenkins / JENKINS-46379 withEnv mess with Job parameter (not case sensitive) Change By: suren pi Assignee: suren pi 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-49774) NPE in Autofavorite plugin
Title: Message Title Vivek Pandey resolved as Cannot Reproduce kutzi No problem. It might have been fixed since reported. Anyways, reopen it if you find it reproducing. Thanks for reporting. Jenkins / JENKINS-49774 NPE in Autofavorite plugin Change By: Vivek Pandey Status: Open Resolved Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-46379) withEnv mess with Job parameter (not case sensitive)
Title: Message Title suren pi commented on JENKINS-46379 Re: withEnv mess with Job parameter (not case sensitive) I thought it should be a issue, anyone will take care of it? 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step It should be fine. It definitely won't work for classic upstream jobs tho. 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Michael Neale commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Steven Visagie good questoin, an experiment (if you have the ability to build it) would be worthwhile, but I expect it would work the same, as it doesn't necessarily care what is in the "build" step for things it triggers (ie what type it is) so ideally it would just work. 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-43866) Don't round up 99.x% coverage to 100%
Title: Message Title Share Cheng started work on JENKINS-43866 Change By: Share Cheng Status: Open In Progress 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-44195) Add timestamps to the log
Title: Message Title Michael Neale commented on JENKINS-44195 Re: Add timestamps to the log trejkaz interesting - yes they probably are large. Jared Kauppila log stash I don't think would see those timestamps from the timestamper plugin at all (it probably ads its own somehow...) 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-44195) Add timestamps to the log
Title: Message Title trejkaz commented on JENKINS-44195 Re: Add timestamps to the log This relates to another thing we noticed, which is that timestamps were being generated from Jenkins master, which meant they didn't really reflect the times the events were occurring on the slaves. Normally you'd think this wouldn't differ by much, but because of the already-mentioned ConsoleNote thing, our Jenkins was working so hard reading from sockets and writing to logs that it was being delayed in processing data coming from slaves. We currently pipe all our commands through an executable to add the timestamps to the raw output so that we can see the true timestamps irrespective of how long the master is taking to read and write the data. 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-44195) Add timestamps to the log
Title: Message Title Jared Kauppila commented on JENKINS-44195 Re: Add timestamps to the log Logstash definitely supports parsing existing timestamps and is generally the value you want to use vs just utilizing the received time like you mentioned. 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-44195) Add timestamps to the log
Title: Message Title trejkaz commented on JENKINS-44195 Re: Add timestamps to the log I'm fine with anything that gets the logs into the view in a more or less accurate way... As long as it doesn't fill our disk with inefficient ConsoleNote serialisations like the timestamper plugin does. But maybe that just means fixing how its ConsoleNote is serialised? When I looked at how much was stored in it, I wasn't able to account for the enormous size it was writing into the file. (People who claim they aren't noticing it probably aren't using it with pipeline. It turns out that if you use it for non-pipeline jobs, it stores the timestamps in a much more sensible way.) The comment about external logging systems seems a bit odd to me too actually, surely if you're going to store a timestamp, you'd want the time that it actually occurred, not the time at which the log event eventually entered something like logstash? Does logstash not support passing existing timestamps along? 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-46473) Error when connecting to ALM using HPE Application Automation Tools Plugin
Title: Message Title Marlene Macdonald commented on JENKINS-46473 Re: Error when connecting to ALM using HPE Application Automation Tools Plugin 1) On Jenkins -> configuration: enter the name and URL of the ALM server under Application Lifecycle Management/ALM server 2) On Jenkins -> Plugin Manager -> Advanced: enter proxy server and port, plus optionally user/password if needed (if your proxy requires authentication) under HTTP Proxy Configuration 3) Create Item(job), Configure Build step as Execute HPE tests using HPE ALM Lab Management. Select ALM Server. Enter ALM Credentials. (Use Add button to setup first time. This is the user/password that connects to ALM) Enter Domain. Check the box "Use proxy settings". Enter your proxy address and port, x.x.x.x:80. Add proxy credentials if your proxy requires authentication. Then enter the project name, select Run type as test set. Enter the Test Set ID and description from ALM and a timeslot duration in minutes. This should be all you need to setup. 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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Denys Digtiar commented on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
Hermann Schweizer As Mike and Jesse alluded to, the new Agent implementation was added which is based on the CLI ssh-agent. If you have a CLI available inside the docker container and use the `sshagent` inside the docker.inside() closure, your git clone should work. Looks for the message like "Exec ssh-agent (binary ssh-agent on a remote machine)" or any errors that mention ssh-agent
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-46473) Error when connecting to ALM using HPE Application Automation Tools Plugin
Title: Message Title Prakash AM commented on JENKINS-46473 Re: Error when connecting to ALM using HPE Application Automation Tools Plugin Marlene Macdonald Yes, I downgraded to 5.2 and tested it out as well. But, still I am getting the same error as you mentioned here. Can you please share the steps you tried here(like updating proxy(please share details), updateing ALM). 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald updated JENKINS-38339 Merged @ 203324c8913426d9a9fd6a7cfe82f40c157eacec Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Status: In Review Resolved Resolution: Fixed 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
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald updated JENKINS-38339 Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Status: In Progress Review 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-45334) REGRESSION "input parameter not support go to classic link" does not work
Title: Message Title Nicolae Pascu updated JENKINS-45334 Jenkins / JENKINS-45334 REGRESSION "input parameter not support go to classic link" does not work Change By: Nicolae Pascu Status: In Review Closed Resolution: Fixed 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-49573) Matrix Configuration Parameter Plugin is affected by JEP-200
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49573 Re: Matrix Configuration Parameter Plugin is affected by JEP-200 Code changed in jenkins User: ikedam Path: pom.xml http://jenkins-ci.org/commit/matrix-combinations-plugin/a314877620b1ba16be24d15e8f43d2dde294a3ee Log: JENKINS-49573 Depend on matrix-project 1.4.1 bundled with Jenkins-1.625.3 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-49573) Matrix Configuration Parameter Plugin is affected by JEP-200
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49573 Re: Matrix Configuration Parameter Plugin is affected by JEP-200 Code changed in jenkins User: ikedam Path: pom.xml http://jenkins-ci.org/commit/matrix-combinations-plugin/14a2368c9e40e5e39c0390520ae7648d33993152 Log: JENKINS-49573 Use matrix-project 1.7 which fixes SECURITY-170 for tests with latest cores 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-49573) Matrix Configuration Parameter Plugin is affected by JEP-200
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49573 Re: Matrix Configuration Parameter Plugin is affected by JEP-200 Code changed in jenkins User: ikedam Path: pom.xml http://jenkins-ci.org/commit/matrix-combinations-plugin/4058e9d766b08f7b27cfbfb5c9c36deabeeb9ba9 Log: Merge pull request #24 from ikedam/feature/JENKINS-49573 JENKINS-49573 core-1.651.3 + matrix-project-1.7 Compare: https://github.com/jenkinsci/matrix-combinations-plugin/compare/db3d32a84d50...4058e9d766b0 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-49573) Matrix Configuration Parameter Plugin is affected by JEP-200
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49573 Re: Matrix Configuration Parameter Plugin is affected by JEP-200 Code changed in jenkins User: ikedam Path: pom.xml http://jenkins-ci.org/commit/matrix-combinations-plugin/ef078ad88a822ff2639fa4b7f2d55b225e08fba2 Log: JENKINS-49573 Target Jenkins 1.651.3 with SECURITY-170 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Dalmo Santos edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Hi!I found a palliative solution to the problem. I added the Allocate Workspace. It works on multibranch pipeline, on any node. Ex.:def wsDir = "/some/path/$ \ {env.BRANCH_NAME}"ws (wsDir) \ {// some block}
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-44195) Add timestamps to the log
Title: Message Title Michael Neale commented on JENKINS-44195 Re: Add timestamps to the log So some more thoughts: Perhaps there is a way for timestamper to add data to the log in a way that blue ocean or other systems can use (that isn't classic UI specific markup that won't work) Perhaps a way to show/toggle timestamps for all logs in blue ocean would be easier (would mean not using time stamper) The timestamper output has to be scraped for the actual time data out of the embedded markup returned in the json (ugh) None are appealing really. 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-33925) Test framework for Jenkinsfile
Title: Message Title Jesse Glick commented on JENKINS-33925 Re: Test framework for Jenkinsfile Jenkinsfile Runner was recently published, which attacks the problem from the opposite end of the spectrum, literally using JenkinsRule internally. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Dalmo Santos commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Hi! I found a palliative solution to the problem. I added the Allocate Workspace. Ex.: def wsDir = "/some/path/$ {env.BRANCH_NAME} " ws (wsDir) { // some block }
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-49381) Need to update github-api on github-plugin
Title: Message Title Thiago Gomes commented on JENKINS-49381 Re: Need to update github-api on github-plugin We would need this PR to be merged: https://github.com/jenkinsci/github-api-plugin/pull/19 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-44195) Add timestamps to the log
Title: Message Title
Michael Neale edited a comment on JENKINS-44195
Re: Add timestamps to the log
[~jbochenski] oh good to know re size. Ah - Clarification: there is no *supressing* of the timestamps in the logs via blue ocean, the timestamps are not added to the log itself (directly), so it wouldn't be possible to supress it, they just aren't there. The timestamper doesn't ad to the text you get via an api. It has another API to fetch it the logs with the timestamps added as span/html fragments - so it must be possible. I can see the /wfapi used by the stage view shows it, so perhaps the best approach [~dragoonis] is to find a way to support it in the log api that blue ocean uses - then it would work the same as people use now. The data returned from it looks like the following, which would be messy/risky to inject into an alternate log viewer (see the html fragments - and explains why sometimes things look off in stage view). The URI: [http://localhost:8080/job/timestamper/3/execution/node/9/wfapi/log?_=151994778] Perhaps [~vivek] may have some ideas on how the blue api server side could use the timestamper endpoint to fetch it with the stamps added? Response: {code:java}{"nodeId": "18","nodeStatus": "SUCCESS","length": 8602,"hasMore": false,"text": "00:00:14.594 [timestamper] Running shell script\n00:00:14.857 + ping -c 15 www.apple.com\n00:00:14.857 PING e6858.dsce9.akamaiedge.net (104.84.9.174): 56 data bytes\n00:00:14.857 64 bytes from 104.84.9.174: icmp_seq=0 ttl=52 time=46.146 ms\n00:00:15.772 64 bytes from 104.84.9.174: icmp_seq=1 ttl=52 time=24.984 ms\n00:00:16.692 64 bytes from 104.84.9.174: icmp_seq=2 ttl=52 time=40.099 ms\n00:00:18.045 64 bytes from 104.84.9.174: icmp_seq=3 ttl=52 time=39.247 ms\n00:00:18.960 64 bytes from 104.84.9.174: icmp_seq=4 ttl=52 time=38.471 ms\n00:00:19.876 64 bytes from 104.84.9.174: icmp_seq=5 ttl=52 time=37.845 ms\n00:00:20.793 64 bytes from 104.84.9.174: icmp_seq=6 ttl=52 time=37.656 ms\n00:00:21.713 64 bytes from 104.84.9.174: icmp_seq=7 ttl=52 time=35.950 ms\n00:00:23.062 64 bytes from 104.84.9.174: icmp_seq=8 ttl=52 time=37.010 ms\n00:00:23.979 64 bytes from 104.84.9.174: icmp_seq=9 ttl=52 time=34.426 ms\n00:00:24.898 64 bytes from 104.84.9.174: icmp_seq=10 ttl=52 time=33.600 ms\n00:00:25.818 64 bytes from 104.84.9.174: icmp_seq=11 ttl=52 time=21.033 ms\n00:00:26.740 64 bytes from 104.84.9.174: icmp_seq=12 ttl=52 time=19.620 ms\n00:00:28.093 64 bytes from 104.84.9.174: icmp_seq=13 ttl=52 time=30.910 ms\n00:00:29.012 64 bytes from 104.84.9.174: icmp_seq=14 ttl=52 time=57.460 ms\n00:00:29.012 \n00:00:29.012 --- e6858.dsce9.akamaiedge.net ping statistics ---\n00:00:29.012 15 packets transmitted, 15 packets received, 0.0% packet loss\n00:00:29.012 round-trip min/avg/max/stddev = 19.620/35.630/57.460/9.128 ms\n","consoleUrl": "/job/timestamper/3/execution/node/18/log"}{code}
Add Comment
[JIRA] (JENKINS-44195) Add timestamps to the log
Title: Message Title
Michael Neale edited a comment on JENKINS-44195
Re: Add timestamps to the log
[~jbochenski] oh good to know re size. Ah - the timestamper doesn't ad to the text you get via an api. It has another API to fetch it - so it must be possible. I can see the /wfapi used by the stage view shows it, so perhaps the best approach [~dragoonis] is to find a way to support it in the log api that blue ocean uses - then it would work the same as people use now. The data returned from it looks like the following, which would be messy/risky to inject into an alternate log viewer (see the html fragments - and explains why sometimes things look off in stage view) . The URI : [http://localhost:8080/job/timestamper/3/execution/node/9/wfapi/log?_=151994778] Perhaps [~vivek] may have some ideas on how the blue api server side could use the timestamper endpoint to fetch it with the stamps added? Response: {code:java}{"nodeId": "18","nodeStatus": "SUCCESS","length": 8602,"hasMore": false,"text": "00:00:14.594 [timestamper] Running shell script\n00:00:14.857 + ping -c 15 www.apple.com\n00:00:14.857 PING e6858.dsce9.akamaiedge.net (104.84.9.174): 56 data bytes\n00:00:14.857 64 bytes from 104.84.9.174: icmp_seq=0 ttl=52 time=46.146 ms\n00:00:15.772 64 bytes from 104.84.9.174: icmp_seq=1 ttl=52 time=24.984 ms\n00:00:16.692 64 bytes from 104.84.9.174: icmp_seq=2 ttl=52 time=40.099 ms\n00:00:18.045 64 bytes from 104.84.9.174: icmp_seq=3 ttl=52 time=39.247 ms\n00:00:18.960 64 bytes from 104.84.9.174: icmp_seq=4 ttl=52 time=38.471 ms\n00:00:19.876 64 bytes from 104.84.9.174: icmp_seq=5 ttl=52 time=37.845 ms\n00:00:20.793 64 bytes from 104.84.9.174: icmp_seq=6 ttl=52 time=37.656 ms\n00:00:21.713 64 bytes from 104.84.9.174: icmp_seq=7 ttl=52 time=35.950 ms\n00:00:23.062 64 bytes from 104.84.9.174: icmp_seq=8 ttl=52 time=37.010 ms\n00:00:23.979 64 bytes from 104.84.9.174: icmp_seq=9 ttl=52 time=34.426 ms\n00:00:24.898 64 bytes from 104.84.9.174: icmp_seq=10 ttl=52 time=33.600 ms\n00:00:25.818 64 bytes from 104.84.9.174: icmp_seq=11 ttl=52 time=21.033 ms\n00:00:26.740 64 bytes from 104.84.9.174: icmp_seq=12 ttl=52 time=19.620 ms\n00:00:28.093 64 bytes from 104.84.9.174: icmp_seq=13 ttl=52 time=30.910 ms\n00:00:29.012 64 bytes from 104.84.9.174: icmp_seq=14 ttl=52 time=57.460 ms\n00:00:29.012 \n00:00:29.012 --- e6858.dsce9.akamaiedge.net ping statistics ---\n00:00:29.012 15 packets transmitted, 15 packets received, 0.0% packet loss\n00:00:29.012 round-trip min/avg/max/stddev = 19.620/35.630/57.460/9.128 ms\n","consoleUrl": "/job/timestamper/3/execution/node/18/log"}{code}
Add Comment
[JIRA] (JENKINS-44195) Add timestamps to the log
Title: Message Title Michael Neale edited a comment on JENKINS-44195 Re: Add timestamps to the log I note that timestamper lets you fetch the logs as text (ie you can choose what you want to see, and then it adds it to text) which implies it might be able to work. I think the idea of wrapping pipeline via a step to get this is very strange and a usability hassle though (wouldn't people want to see timestamps always as a base line?) One of the hard things is that the whole console note thing kind of doesn't work if you are working with logs as text, outside of the classic web UI (as everything comes back as markup with assumptions as to how it works). It would be a bit like expecting the timestamper to work with LogStash logs. 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-44195) Add timestamps to the log
Title: Message Title
Michael Neale commented on JENKINS-44195
Re: Add timestamps to the log
Jakub Bochenski oh good to know re size. Ah - the timestamper doesn't ad to the text you get via an api. It has another API to fetch it - so it must be possible. I can see the /wfapi used by the stage view shows it, so perhaps the best approach Paul Dragoonis is to find a way to support it in the log api that blue ocean uses - then it would work the same as people use now. The data returned from it looks like the following, which would be messy/risky to inject into an alternate log viewer (see the html fragments - and explains why sometimes things look off in stage view):
{"nodeId": "18","nodeStatus": "SUCCESS","length": 8602,"hasMore": false,"text": "timestamp\">00:00:14.594 [timestamper] Running shell script\ntimestamp\">00:00:14.857 + ping -c 15 www.apple.com\ntimestamp\">00:00:14.857 PING e6858.dsce9.akamaiedge.net (104.84.9.174): 56 data bytes\ntimestamp\">00:00:14.857 64 bytes from 104.84.9.174: icmp_seq=0 ttl=52 time=46.146 ms\ntimestamp\">00:00:15.772 64 bytes from 104.84.9.174: icmp_seq=1 ttl=52 time=24.984 ms\ntimestamp\">00:00:16.692 64 bytes from 104.84.9.174: icmp_seq=2 ttl=52 time=40.099 ms\ntimestamp\">00:00:18.045 64 bytes from 104.84.9.174: icmp_seq=3 ttl=52 time=39.247 ms\ntimestamp\">00:00:18.960 64 bytes from 104.84.9.174: icmp_seq=4 ttl=52 time=38.471 ms\ntimestamp\">00:00:19.876 64 bytes from 104.84.9.174: icmp_seq=5 ttl=52 time=37.845 ms\ntimestamp\">00:00:20.793 64 bytes from 104.84.9.174: icmp_seq=6 ttl=52 time=37.656 ms\ntimestamp\">00:00:21.713 64 bytes from 104.84.9.174: icmp_seq=7 ttl=52 time=35.950 ms\ntimestamp\">00:00:23.062 64 bytes from 104.84.9.174: icmp_seq=8 ttl=52 time=37.010 ms\ntimestamp\">00:00:23.979 64 bytes from 104.84.9.174: icmp_seq=9 ttl=52 time=34.426 ms\ntimestamp\">00:00:24.898 64 bytes from 104.84.9.174: icmp_seq=10 ttl=52 time=33.600 ms\ntimestamp\">00:00:25.818 64 bytes from 104.84.9.174: icmp_seq=11 ttl=52 time=21.033 ms\ntimestamp\">00:00:26.740 64 bytes from 104.84.9.174: icmp_seq=12 ttl=52 time=19.620 ms\ntimestamp\">00:00:28.093 64 bytes from 104.84.9.174: icmp_seq=13 ttl=52 time=30.910 ms\ntimestamp\">00:00:29.012 64 bytes from 104.84.9.174: icmp_seq=14 ttl=52 time=57.460 ms\ntimestamp\">00:00:29.012 \ntimestamp\">00:00:29.012 --- e6858.dsce9.akamaiedge.net ping statistics ---\ntimestamp\">00:00:29.012 15 packets transmitted, 15 packets received, 0.0% packet loss\ntimestamp\">00:00:29.012 round-trip min/avg/max/stddev = 19.620/35.630/57.460/9.128 ms\n","consoleUrl": "/job/timestamper/3/execution/node/18/log"}
Add Comment
[JIRA] (JENKINS-44195) Add timestamps to the log
Title: Message Title Michael Neale edited a comment on JENKINS-44195 Re: Add timestamps to the log [~jbochenski] timestamper with its use of console I note won't work with anything that isn't timestamper lets you fetch the classic UI, it assumes that all the rest of it is there, logs as text ( ie if you can choose what you want to get the logs out into another system see , and then it won't work with adds it (that is my understanding to text ) which implies it might be able to work . I think the idea of wrapping pipeline via a step to get this is very strange and a usability hassle though (wouldn't people want to see timestamps always as a base line?) 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-44195) Add timestamps to the log
Title: Message Title Michael Neale commented on JENKINS-44195 Re: Add timestamps to the log Jakub Bochenski timestamper with its use of console note won't work with anything that isn't the classic UI, it assumes that all the rest of it is there, ie if you want to get the logs out into another system, it won't work with it (that is my understanding). 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title Simon Wydooghe commented on JENKINS-47286 Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view I think people with scripted pipelines could benefit greatly from this. Scripted pipeline users run more advanced pipelines I'm guessing, so it feels weird to not support this feature there as it seems they will be the first ones to implement this functionality in their pipelines. 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-33126) unstash fails to overwrite read-only files
Title: Message Title Omit Rathore commented on JENKINS-33126 Re: unstash fails to overwrite read-only files Yes same issue I have also faced , recommend it to increase priority as some integration tools needs git meta 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-46473) Error when connecting to ALM using HPE Application Automation Tools Plugin
Title: Message Title Marlene Macdonald commented on JENKINS-46473 Re: Error when connecting to ALM using HPE Application Automation Tools Plugin Note that only v5.2 is currently supporting connecting to ALM from Jenkins when using a proxy. The current version (v5.3) is not working. Have you tried with v5.2? 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-48576) Blue ocean editor: no error message with truncated sh step
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-48576 Blue ocean editor: no error message with truncated sh step Change By: Karl Shultz Attachment: screenshot-1.png 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-49809) Create the Evergreen Status service data model
Title: Message Title R. Tyler Croy commented on JENKINS-49809 Re: Create the Evergreen Status service data model Attached a whiteboard of my first cut at the internal data model that the Status service is going to need. Some outstanding questions which I need to answer for myself are: Some tables (e.g. Instance, Versions, Connection, Capabilities) will exist for each install, and some will have heavy churn (e.g. Connection). At what point does this represent a scaling problem? In essence, if we had 180k installs, would that be okay? How would this data model work if we had two artifacts we needed to track in the evergreen distribution process, such as one artifact representing Jenkins core and plugins, and another track representing the evergreen-client and "evergreen tools" on the system? How useful are the JSON query mechanisms in PostgreSQL? I'm currently thinking that I can avoid lots of headache by using JSON in PostgreSQL where the data structure is a bit more fluid, but can I query into those data structures? 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
[JIRA] (JENKINS-49809) Create the Evergreen Status service data model
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49809 Create the Evergreen Status service data model Change By: R. Tyler Croy Attachment: 20180206_141046.jpg 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-49264) Prototype Evergreen distribution mechanism
Title: Message Title R. Tyler Croy commented on JENKINS-49264 Re: Prototype Evergreen distribution mechanism I'm going to close this ticket out because it's too high level and I have added some others in its place 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-49264) Prototype Evergreen distribution mechanism
Title: Message Title R. Tyler Croy closed an issue as Fixed Jenkins / JENKINS-49264 Prototype Evergreen distribution mechanism Change By: R. Tyler Croy Status: In Progress Closed Resolution: Fixed 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-49809) Create the Evergreen Status service data model
Title: Message Title R. Tyler Croy started work on JENKINS-49809 Change By: R. Tyler Croy Status: Open In Progress 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-49639) Sonar Gerrit plugin not posting comments when changedLinesOnly == true
Title: Message Title Tatiana Didik commented on JENKINS-49639 Re: Sonar Gerrit plugin not posting comments when changedLinesOnly == true Hi Maxim. You can e-mail developers (me) directly using the e-mail provided on the plugin wiki page. To help you with troubleshooting I need 1) your pipeline code or screenshot of your plugin settings; 2) name of the file with an issue ignored; 3) lines from your sonar-report file regarding this issue. 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-49830) Make possible to run the PCT for blueocean-autofavorite-plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49830 Re: Make possible to run the PCT for blueocean-autofavorite-plugin Code changed in jenkins User: Maria Isabel Vilacides Path: pom.xml http://jenkins-ci.org/commit/blueocean-autofavorite-plugin/e7a609b9f9ff05fa40b6f61725b017429842fbaf Log: JENKINS-49830 Fixing the urls in the poms to be able to execute the PCT (#15) 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-49830) Make possible to run the PCT for blueocean-autofavorite-plugin
Title: Message Title
Isa Vilacides updated an issue
Jenkins / JENKINS-49830
Make possible to run the PCT for blueocean-autofavorite-plugin
Change By:
Isa Vilacides
Currently it's not possible to get the PCT run with blueocean-autofavorite-plugin because the pom.xml url is wrong (it's failing with a problem in the git clone) . In order to make it work that needs to be fixed by replacing:\{code}scm:git:git://github.com/jenkinsci/$\{project.artifactId}-plugin.gitscm:git:g...@github.com:jenkinsci/$\{project.artifactId}-plugin.git\{code}with\{code}scm:git:[https://github.com/jenkinsci/$\|https://github.com/jenkinsci/$]\{project.artifactId}-plugin.gitscm:git:[https://github.com/jenkinsci/$\|https://github.com/jenkinsci/$]\{project.artifactId}-plugin.git\{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
[JIRA] (JENKINS-49830) Make possible to run the PCT for blueocean-autofavorite-plugin
Title: Message Title
Isa Vilacides updated an issue
Jenkins / JENKINS-49830
Make possible to run the PCT for blueocean-autofavorite-plugin
Change By:
Isa Vilacides
Currently it's not possible to get the PCT run with blueocean-autofavorite-plugin because the pom.xml url is wrong. In order to make it work that needs to be fixed by replacing:\{code} - scm:git:git://github.com/jenkinsci/$\{project.artifactId}-plugin.git - scm:git:g...@github.com:jenkinsci/$\{project.artifactId}-plugin.git\{code}with\{code} + scm:git: [ https://github.com/jenkinsci/$\ |https://github.com/jenkinsci/$]\ {project.artifactId}-plugin.git + scm:git: [ https://github.com/jenkinsci/$\ |https://github.com/jenkinsci/$]\ {project.artifactId}-plugin.git\{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
[JIRA] (JENKINS-49830) Make possible to run the PCT for blueocean-autofavorite-plugin
Title: Message Title Isa Vilacides updated JENKINS-49830 Jenkins / JENKINS-49830 Make possible to run the PCT for blueocean-autofavorite-plugin Change By: Isa Vilacides Status: In Progress Review 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-28022) Build description longer than 30 chars has hex zero width space added
Title: Message Title Giovanni Tirloni commented on JENKINS-28022 Re: Build description longer than 30 chars has hex zero width space added We've faced this issue on Jenkins 2.8.4 with the GitHub PR Builder plugin where we add the PR's URL to the description. People copy and paste it into their browser's window and, instead of going to the page, Chrome/Firefox won't consider it a URL and instead search for that value. 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-49831) Add Release Event
Title: Message Title Nicolas Siver created an issue Jenkins / JENKINS-49831 Add Release Event Issue Type: Improvement Assignee: Kirill Merkushev Components: github-plugin Created: 2018-03-01 20:17 Labels: webhook release github Priority: Minor Reporter: Nicolas Siver Currently, the plugin supports the only PUSH event (https://github.com/jenkinsci/github-plugin/blob/78167fd8a507ada4382c961c65539f7e1d9ba054/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java). There are automatizations and workflows which rely not only on a PUSH event. Ability to support an event for GitHub releases (X-GitHub-Event: release) would be highly appreciated. Add Comment
[JIRA] (JENKINS-25519) Rethrown NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check to retry indefinitely
Title: Message Title Jesse Glick commented on JENKINS-25519 Re: Rethrown NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check to retry indefinitely PR 65 is one attempt at this. 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-49830) Make possible to run the PCT for blueocean-autofavorite-plugin
Title: Message Title Isa Vilacides started work on JENKINS-49830 Change By: Isa Vilacides Status: Open In Progress 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-49830) Make possible to run the PCT for blueocean-autofavorite-plugin
Title: Message Title
Isa Vilacides created an issue
Jenkins / JENKINS-49830
Make possible to run the PCT for blueocean-autofavorite-plugin
Issue Type:
Task
Assignee:
Isa Vilacides
Components:
blueocean-autofavorite-plugin
Created:
2018-03-01 20:16
Priority:
Major
Reporter:
Isa Vilacides
Currently it's not possible to get the PCT run with blueocean-autofavorite-plugin because the pom.xml url is wrong. In order to make it work that needs to be fixed by replacing: {code} - scm:git:git://github.com/jenkinsci/${project.artifactId}-plugin.git - scm:git:g...@github.com:jenkinsci/${project.artifactId}-plugin.git {code} with {code} + scm:git:https://github.com/jenkinsci/$\{project.artifactId}-plugin.git + scm:git:https://github.com/jenkinsci/$\{project.artifactId}-plugin.git {code}
Add Comment
[JIRA] (JENKINS-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException
Title: Message Title syam yalamanchili commented on JENKINS-26257 Re: ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException Did anyone find the solution for this issue? 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-49829) Getting string index out of range error when using git 2.16.2+
Title: Message Title Igor Sarkisov created an issue Jenkins / JENKINS-49829 Getting string index out of range error when using git 2.16.2+ Issue Type: Bug Assignee: Unassigned Components: repo-plugin Created: 2018-03-01 19:42 Environment: Debian with git 2.16.2 Priority: Major Reporter: Igor Sarkisov I have system running Debian with git 2.16.2. REPO plugin fails to sync latest changes and throwing the following error: [devtools] $ git log --raw --first-parent --format="[[]]%H[[]%an[[]%ae[[]%aD[[]%cn[[]%ce[[]%cD[[]%s %b[[]" b8630400d4ebf2406f49e11e213c9ae12cf7605b..a1e314337f062b4dd15beab1aaf1206af6183f2a FATAL: String index out of range: 38 java.lang.StringIndexOutOfBoundsException: String index out of range: 38 at java.lang.String.substring(String.java:1963) at hudson.plugins.repo.ChangeLog.generateChangeLog(ChangeLog.java:203) at hudson.plugins.repo.ChangeLog.saveChangeLog(ChangeLog.java:249) at hudson.plugins.repo.RepoScm.checkout(RepoScm.java:718) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1212) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:566) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:491) at hudson.model.Run.execute(Run.java:1737) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421) However, on my other system (Ubuntu with git 1.9.1) it works as expected. Upon further investigation I discovered git log output different between git versions 1.9.1 and 2.16.2: Here is output with git 1.9.1: /usr/local/bin/git log --raw
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Bill Hamilton edited a comment on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
[~markewaite], I want to echo [~xxthunder] and [~robin_smith]. I too want to test PSL changes. The Jenkinsfile in my PSL PR does:_def utils_pkg=library("PSL@$\{branch}").ors.utils_where branch is determined at runtime, and could be a PR build. So I expanded the refspec in the PSL configuration to this:_+refs/pull/*/head:refs/remotes/@\{remote}/pr/*_so when the build for my PR111 executes it is calling:_def utils_pkg=library("PSL@pr/111").ors.utils_This fails, with this output: > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*/head:refs/remotes/origin/pr/* > git rev-parse origin/pr/111^\{commit} # timeout=30 > git branch -v --no-abbrev --contains f39b737d67b11218dad26756e7c4b1f5900ff037 # timeout=30Could not find a branch containing commit f39b737d67b11218dad26756e7c4b1f5900ff037 Also, I wouldnt consider this a minor bug. This is breaks our ability to unit test code changes to our PSL library, which is used by hundreds of customers in our organization. We have trained them to contribute to our PSL library via PRs. But all of the PRs they file fail because of this regression.
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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Bill Hamilton commented on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
Mark Waite, I want to echo Karsten Günther and Robin Smith. I too want to test PSL changes. The Jenkinsfile in my PSL PR does: def utils_pkg=library("PSL@${branch}").ors.utils where branch is determined at runtime, and could be a PR build. So I expanded the refspec in the PSL configuration to this: +refs/pull//head:refs/remotes/@{remote}/pr/ so when the build for my PR111 executes it is calling: def utils_pkg=library("PSL@pr/111").ors.utils This fails, with this output: > git fetch --tags --progress origin +refs/heads/:refs/remotes/origin/ +refs/pull//head:refs/remotes/origin/pr/ > git rev-parse origin/pr/111^{commit} # timeout=30 > git branch -v --no-abbrev --contains f39b737d67b11218dad26756e7c4b1f5900ff037 # timeout=30 Could not find a branch containing commit f39b737d67b11218dad26756e7c4b1f5900ff037
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-47624) Pipeline step "stash" hangs after plugin upgrade
Title: Message Title Kevin Phillips commented on JENKINS-47624 Re: Pipeline step "stash" hangs after plugin upgrade hmmm - actually in my case this was a red herring. Apparently the include pattern for the `stash` build step is `includes` (plural) not `include` (singular). So rather than throwing an error, Groovy ignored this small typo and assumed that I wasn't providing any pattern for the files to be stashed and it was packaging the entire workspace folder ... which took forever, which is why it looked like it was frozen. Perhaps the expectation here was that this defect wasn't actually a defect and the other reporter did something similar... and if the stash plugin had some sort of verbose output showing live what it was doing then perhaps the issue could have be solved quicker... not sure. Either way it's still not obvious how the linked task is a duplicate of this one. 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-47624) Pipeline step "stash" hangs after plugin upgrade
Title: Message Title Kevin Phillips commented on JENKINS-47624 Re: Pipeline step "stash" hangs after plugin upgrade Oh, and btw, I've reproduced this hanging build problem on the latest Jenkins core version (v2.108) so whatever the issue it looks to still be a problem. 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-47624) Pipeline step "stash" hangs after plugin upgrade
Title: Message Title Kevin Phillips commented on JENKINS-47624 Re: Pipeline step "stash" hangs after plugin upgrade Sorry for my naivite here, but this issue was resolved as a duplicate of JENKINS-40912... however this is a bug report where the `stash` build step hangs during the build where as the other is a feature request to have the `stash` build step show verbose output on what it's doing. The two don't seem obviously related. Have I missed something? 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-49828) Commit viewer in Blue Ocean
Title: Message Title Cédric Meuter created an issue Jenkins / JENKINS-49828 Commit viewer in Blue Ocean Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-03-01 18:52 Environment: jenkins 2.89 + blue ocean 1.4.2 Labels: blueocean changes Priority: Minor Reporter: Cédric Meuter In the blue ocean UI, attached to each build, there is a "changes" tab where one can view all the commits since the previous build, which is awesome. This is also available in the traditional UI. However, in the traditional UI, you can click on each commit to get some details which is not possible in the blue ocean UI. It would be nice to have this as well. Add Comment
[JIRA] (JENKINS-49827) Previous/Next Build in Blue Ocean
Title: Message Title Cédric Meuter created an issue Jenkins / JENKINS-49827 Previous/Next Build in Blue Ocean Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-03-01 18:47 Environment: jenkins 2.89 + blue ocean 1.4.2 Labels: blueocean navigation Priority: Minor Reporter: Cédric Meuter In the standard Jenkins view it is possible to navigate successive builds using the "next build" and "previous build" links in the column on the left. It's a feature I find extremely practical when trying to find when a build broke. I think this should be added in the blue ocean UI to navigate builds of the pipeline on the same branch. Add Comment
[JIRA] (JENKINS-49826) Incorrect and confusing compilation of sets with custom types
Title: Message Title
Mike Kobit created an issue
Jenkins / JENKINS-49826
Incorrect and confusing compilation of sets with custom types
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-03-01 18:35
Environment:
Jenkins version: 2.89.4 Pipeline (workflow-aggregator) => 2.5 Pipeline: API (workflow-api) => 2.26 Pipeline: Basic Steps (workflow-basic-steps) => 2.6 Pipeline: Groovy (workflow-cps) => 2.45 Pipeline: Job (workflow-job) => 2.17 Pipeline: Multibranch (workflow-multibranch) => 2.17 Pipeline: Nodes and Processes (workflow-durable-task-step) => 2.19 Pipeline: SCM Step (workflow-scm-step) => 2.6 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib) => 2.9 Pipeline: Step API (workflow-step-api) => 2.14 Pipeline: Supporting APIs (workflow-support) => 2.18
Priority:
Major
Reporter:
Mike Kobit
First, create a pipeline job with this pipeline that contains a class definition:
class Data implements Serializable {
final String string
Data(final String string) {
this.string = Objects.requireNonNull(string)
}
boolean equals(final other) {
if (this.is(other)) {
return true
}
if (getClass() != other.class) {
return false
}
final Data that = (Data) other
return string == that.string
}
int hashCode() {
return string.hashCode()
}
}
final d1 = new Data('a')
final d2 = new Data('b')
final d3 = new Data('c')
final s1 = 'a'
final s2 = 'b'
final s3 = 'c'
final s0 = [s1, s2, s3]
echo "s1: ${s0.getClass()}"
final ss1 = [s1, s2, s3].toSet()
echo "ss1: ${ss1.getClass()}"
final Set
[JIRA] (JENKINS-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Richard Wilkinson commented on JENKINS-49746 Re: Regex returns more matches than it should if errors are close together See the attached file, err.txt. 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-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Richard Wilkinson updated an issue Jenkins / JENKINS-49746 Regex returns more matches than it should if errors are close together Change By: Richard Wilkinson Attachment: err.txt 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-49705) EC2 plugin fails to launch agents after some time.
Title: Message Title Jason Reslock commented on JENKINS-49705 Re: EC2 plugin fails to launch agents after some time. I was able to work around/fix this by setting up an appropriate instance profile to allow the Jenkins master to launch build agents using the instance profile instead of using credentials. If anyone else experiences similar behavior, try the instance profile method to see if it resolves the problem. 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-49803) Connection with Testlink-Problem
Title: Message Title Douglas Velho updated an issue Jenkins / JENKINS-49803 Connection with Testlink-Problem Change By: Douglas Velho Attachment: Test_link_result.txt 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-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title bentoi updated an issue Jenkins / JENKINS-49686 NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Change By: bentoi Attachment: build.xml.gz Attachment: flowNodeStore.xml.gz Attachment: jenkins.log.gz 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-49798) Scan Organization Folder not detecting code changes
Title: Message Title Kevin Ford commented on JENKINS-49798 Re: Scan Organization Folder not detecting code changes Tried that first on earlier versions, with errors so this approach fixed. Trying it again and attaching the error. Maybe i can get some direction on how to fix, no luck so far from my research. 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-49798) Scan Organization Folder not detecting code changes
Title: Message Title Kevin Ford updated an issue Jenkins / JENKINS-49798 Scan Organization Folder not detecting code changes Change By: Kevin Ford Attachment: Screen Shot 2018-03-01 at 8.49.32 AM.png 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-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title bentoi commented on JENKINS-49686 Re: NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Thanks for your response, here's my answers to your questions. We use: org.jenkins-ci.plugins.workflow:workflow-job:2.17 org.jenkins-ci.plugins.workflow:workflow-cps:2.45 We started using PERFORMANCE_OPTIMIZED recently to see if it helped working around JENKINS-49646. That's also when we started seeing this problem which now occurs quite frequently. We usually don't restart Jenkins while JOBs are running. We either use "systemctl restart jenkins" or a "plugin update + restart". This problem causes our job queue to hang frequently because some invalid jobs appear to consume executors. When this occurs we restart jenkins and it usually allows the pending job to start but then the problem eventually shows up again requiring to restart jenkins again. The NPE does indeed appear to occur after the restart. I've attached build.xml / flownodeStore.xml for the latest NPE from jenkins.log (build 233). 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-49405) Create jenkins/evergreen Docker package
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49405 Create jenkins/evergreen Docker package Change By: R. Tyler Croy Flagged: Impediment 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-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title bentoi updated an issue Jenkins / JENKINS-49686 NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Change By: bentoi Attachment: jenkins.log.gz Attachment: flowNodeStore.xml.gz Attachment: build.xml.gz 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-11760) Failed SCM poll does not notify admin/anyone of failure.
Title: Message Title Andrew Barber commented on JENKINS-11760 Re: Failed SCM poll does not notify admin/anyone of failure. Any hope of this issue getting fixed? It causes issues for us after password changes. 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-49770) publish-over-ssh not saving settings
Title: Message Title Vadim Yeshchenko commented on JENKINS-49770 Re: publish-over-ssh not saving settings Hello! I had the same issue as described in the ticket, after updating to 1.19.1 Remove prefix can be saved. 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-49062) Warning graph(s) are not drawn on dashboard
Title: Message Title Ben Spoor commented on JENKINS-49062 Re: Warning graph(s) are not drawn on dashboard Thanks, 1.9.5 works for me! 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-48622) Relentless log spam with GerritMissedEventsPlaybackEnabledChecker
Title: Message Title Scott Hebert resolved as Fixed Jenkins / JENKINS-48622 Relentless log spam with GerritMissedEventsPlaybackEnabledChecker Change By: Scott Hebert Status: Open Resolved Resolution: Fixed 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-49774) NPE in Autofavorite plugin
Title: Message Title kutzi commented on JENKINS-49774 Re: NPE in Autofavorite plugin Sorry, I don't see that error anymore and the build logs of the builds, where it happened, are already gone. You can close the issue if you like to and I'll reopen it if I encounter the issue, again. 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-48622) Relentless log spam with GerritMissedEventsPlaybackEnabledChecker
Title: Message Title Will Saxon commented on JENKINS-48622 Re: Relentless log spam with GerritMissedEventsPlaybackEnabledChecker We upgraded to 2.27.4 and I'm not seeing the logging like before. From my perspective this can be closed. 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-44195) Add timestamps to the log
Title: Message Title Jakub Bochenski commented on JENKINS-44195 Re: Add timestamps to the log PS. We use timestamper on all our Jenkins jobs with 150 days retention. Some of the logs are quite big (~20 MB raw text). I haven't noticed any issues related to console notes like the ones trejkaz reported 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-48968) Move tests ClassFilter consistency checks from GitHub API Plugin to JTH Embedded tests
Title: Message Title Jesse Glick commented on JENKINS-48968 Re: Move tests ClassFilter consistency checks from GitHub API Plugin to JTH Embedded tests I recommend this be closed. 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-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
Title: Message Title Saad Azam updated an issue Jenkins / JENKINS-49797 IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM Change By: Saad Azam 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-44195) Add timestamps to the log
Title: Message Title Jakub Bochenski edited a comment on JENKINS-44195 Re: Add timestamps to the log Timestamer already works with pipeline, the problem is that blueocean is suppressing the output.If you open the logs in the old console view it will show you the timestamps.I'd vote against "baking this in", I think reusing a build wrapper is much better architecture when you consider plugins like [https://wiki.jenkins.io/display/JENKINS/Logstash+Plugin] I'd hate to have to have to remove those baked in timestamps with regex when sending log lines to an external system. 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-44195) Add timestamps to the log
Title: Message Title Jakub Bochenski commented on JENKINS-44195 Re: Add timestamps to the log Timestamer already works with pipeline, the problem is that blueocean is suppressing the output. If you open the logs in the old console view it will show you the timestamps. I'd vote against "baking this in", I think reusing a build wrapper is much better architecture when you consider plugins like https://wiki.jenkins.io/display/JENKINS/Logstash+Plugin I'd hate to have to have to remove those baked in timestamps with regex when sending to an external system. 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-49525) Rare exception sync'ing global pipeline library with new project
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49525 Rare exception sync'ing global pipeline library with new project Change By: Karl Wirth Labels: P4_C P4_SUPPORT P4_VERIFY 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-49525) Rare exception sync'ing global pipeline library with new project
Title: Message Title Karl Wirth commented on JENKINS-49525 Re: Rare exception sync'ing global pipeline library with new project Cannot reproduce the problem but I do see we use the same workspace name to sync the libarries but different locations: $ p4 print -a //spec/client/jenkins-library.p4s | grep Root | grep -v "#" Root: /var/lib/jenkins/workspace/FirstJob%40libs/my-shared-library Root: /var/lib/jenkins/workspace/AnotherJob%40libs/my-shared-library Note in the above the same client 'jenkins-library' is used by both jobs to sync the shared library but the workspace 'Root:' is being changed to be a variation on the job name. This could in theorey cause a problem so should be changed. FYI - My global library configuration: Possible resolutions: Plugin uses one global location workspace rooted in the same place based on Library Name (although Paul may have said Jenkins does not expose this information). Plugin uses one global library directory per library per job (don't know what the jenkins sync rules are for global libraries). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49525) Rare exception sync'ing global pipeline library with new project
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49525 Rare exception sync'ing global pipeline library with new project Change By: Karl Wirth Attachment: image-2018-03-01-14-14-09-360.png 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-49825) Raise messages in Error log for Publish
Title: Message Title Paul Allen created an issue Jenkins / JENKINS-49825 Raise messages in Error log for Publish Issue Type: Improvement Assignee: Paul Allen Components: p4-plugin Created: 2018-03-01 14:10 Labels: P4_C Priority: Minor Reporter: Paul Allen This in the Jenkins log: ... p4 submit -i + Unable to publish workspace: com.perforce.p4java.exception.P4JavaException: Unable to submit change. The reason it failed was a trigger which output a message. It would be really helpful to have that message in Jenkins output - doable?? Add Comment
[JIRA] (JENKINS-49824) Add bucket directory listing as parameter
Title: Message Title John Travolta created an issue Jenkins / JENKINS-49824 Add bucket directory listing as parameter Issue Type: Improvement Assignee: Alexandra Goultiaeva Components: google-storage-plugin Created: 2018-03-01 14:04 Priority: Minor Reporter: John Travolta Please, add posibility to choose directory (or file) as build parameter from configured bucket/s. This feature is like from Git plugin, which lists branches to build from. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-49785) Add param for export changelog filename.
Title: Message Title Jesse Glick started work on JENKINS-49785 Change By: Jesse Glick Status: Open In Progress 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-49785) Add param for export changelog filename.
Title: Message Title Jesse Glick updated JENKINS-49785 Jenkins / JENKINS-49785 Add param for export changelog filename. Change By: Jesse Glick Status: In Progress Review 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-49770) publish-over-ssh not saving settings
Title: Message Title Alex Earl resolved as Fixed Fixed in 1.19.1 Jenkins / JENKINS-49770 publish-over-ssh not saving settings Change By: Alex Earl Status: Open Resolved Resolution: Fixed 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-49062) Warning graph(s) are not drawn on dashboard
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-49062 Warning graph(s) are not drawn on dashboard Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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.
