[JIRA] [core] (JENKINS-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Christopher Orr commented on JENKINS-27694 Re: Download update data immediately when installing a new tool installer plugin I can reproduce with that Docker command and with the `golang` plugin (which has that UI bug — JENKINS-27499), but it also happens with others, e.g. the `gradle` plugin. Though note that hitting "Check Now" fails, due to the signature error: https://groups.google.com/forum/#!topic/jenkinsci-users/vv3UAIE7-Mg So perhaps that's a reason why you see it failing with certain Jenkins versions — the metadata fetch process is failing in the background? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [google-oauth-plugin] (JENKINS-31638) p12 path not saving in credentials.xml
Title: Message Title Christopher Orr commented on JENKINS-31638 Re: p12 path not saving in credentials.xml Another Windows user on the mailing list also reported having this problem: https://groups.google.com/forum/#!msg/jenkinsci-users/7kj4UxDmFfU/oNfEx0JOBQAJ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-13751) Promoted Builds plugin should pass actual/"root" job to Git plublisher
Title: Message Title SCM/JIRA link daemon commented on JENKINS-13751 Re: Promoted Builds plugin should pass actual/"root" job to Git plublisher Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/promoted_builds/PromotionProcess.java http://jenkins-ci.org/commit/promoted-builds-plugin/350f706e3157e7b1a07778bfcb0e518bee4e3246 Log: Merge pull request #73 from spudfkc/fix-no-scm-in-promotion [FIXED JENKINS-13751] - PromotionProcess returns SCM of its owner Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/069d9fd258ec...350f706e3157 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-publish-plugin] (JENKINS-31717) docker-build-publish plugin no longer works with spaces in the workspace path
Title: Message Title Michael Neale commented on JENKINS-31717 Re: docker-build-publish plugin no longer works with spaces in the workspace path Carlos Sanchez looks like this was caused by this merge: https://github.com/jenkinsci/docker-build-publish-plugin/commit/73c8a2b0f2838df38b46e9b50f47b0133ffde35c#diff-a7c45f7e2ba80619b5aad549aadc5ef3R322 ie: https://github.com/jenkinsci/docker-build-publish-plugin/blob/master/src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java#L323 which won't work if the workspace has space in its name (probably common). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-plugin] (JENKINS-30874) Gitlab plugin should provide some environment variables with informations on merge request
Title: Message Title Illya Mazuriak assigned an issue to Illya Mazuriak Jenkins / JENKINS-30874 Gitlab plugin should provide some environment variables with informations on merge request Change By: Illya Mazuriak Assignee: Illya Mazuriak Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31732) Download all files from workspace ignores dotfiles
Title: Message Title Jesse Glick commented on JENKINS-31732 Re: Download all files from workspace ignores dotfiles DirectoryBrowserSupport.zip uses VirtualFile.list which currently provides no option to !useDefaultExcludes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [multiple-scms-plugin] (JENKINS-30667) poll scm always run even there is no changes with multiple scm plugin configured two branches in the same repo
Title: Message Title James Sandlin edited a comment on JENKINS-30667 Re: poll scm always run even there is no changes with multiple scm plugin configured two branches in the same repo The workaround: For your Branch Specifier, you must have an absolute path.EX:Branch Specifier (blank for 'any') refs/heads/feature/promotionscriptIf you do not include refs/heads/ as the prefix, the build will run continuously. Also note: I have only tested this via GIT Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [multiple-scms-plugin] (JENKINS-30667) poll scm always run even there is no changes with multiple scm plugin configured two branches in the same repo
Title: Message Title James Sandlin commented on JENKINS-30667 Re: poll scm always run even there is no changes with multiple scm plugin configured two branches in the same repo The workaround: For your Branch Specifier, you must have an absolute path. EX: Branch Specifier (blank for 'any') refs/heads/feature/promotionscript If you do not include refs/heads/ as the prefix, the build will run continuously. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xvfb-plugin] (JENKINS-28147) Xvfb not terminated when a Maven module rebuild fails inside a plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28147 Re: Xvfb not terminated when a Maven module rebuild fails inside a plugin Code changed in jenkins User: Zoran Regvart Path: src/main/java/hudson/maven/MavenBuild.java src/test/java/hudson/maven/MavenBuildTest.java http://jenkins-ci.org/commit/maven-plugin/8cec5cd889457e1d78aed033788d1b8872435d89 Log: JENKINS-28147 Perform Environment tearDown if BuildWrapper signals error Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xvfb-plugin] (JENKINS-28147) Xvfb not terminated when a Maven module rebuild fails inside a plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28147 Re: Xvfb not terminated when a Maven module rebuild fails inside a plugin Code changed in jenkins User: zregvart Path: src/main/java/hudson/maven/MavenBuild.java src/test/java/hudson/maven/MavenBuildTest.java http://jenkins-ci.org/commit/maven-plugin/f3f1f1123a727958b59ea3a731f9cae77b94ab0f Log: Merge pull request #42 from zregvart/master JENKINS-28147 Perform Environment tearDown if BuildWrapper fails Compare: https://github.com/jenkinsci/maven-plugin/compare/fbafb4d68218...f3f1f1123a72 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [console-column-plugin] (JENKINS-20724) MultiJob project console output link is broken if job is opened from a view
Title: Message Title Fred G assigned an issue to Fred G Jenkins / JENKINS-20724 MultiJob project console output link is broken if job is opened from a view Change By: Fred G Assignee: Fred G Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [console-column-plugin] (JENKINS-20724) MultiJob project console output link is broken if job is opened from a view
Title: Message Title Fred G commented on JENKINS-20724 Re: MultiJob project console output link is broken if job is opened from a view Should be fixed, once https://github.com/jenkinsci/console-column-plugin/pull/2 has been merged. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extended-choice-parameter-plugin] (JENKINS-31733) Extended Choice Parameter throw exception for Check Boxes type
Title: Message Title Nam Nguyen updated an issue Jenkins / JENKINS-31733 Extended Choice Parameter throw exception for Check Boxes type Change By: Nam Nguyen Attachment: Screen Shot 2015-11-24 at 4.27.40 PM.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-8783) Renamin promotion process doesn't remove the original promotion process
Title: Message Title Arnaud Héritier commented on JENKINS-8783 Re: Renamin promotion process doesn't remove the original promotion process This is not related to the usage of folders (the same problem exists without it). Workaround: Open you job configuration Add new promotion with the previous name before the renaming. They can be empty. Myself I just checked "Promote immediately once the build is complete" Save your configuration Open you job configuration a second time Remove the promotion with the old name Save your configuration Your job should now work correctly without breaking old promotions and the object model. The issue will be fixed by JENKINS-27716 in promotion plugin > 2.23.1 if you are running on Jenkins >= 1.585 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] [promoted-builds-plugin] (JENKINS-10423) Builds get double promotions after promotion has been renamed
Title: Message Title Arnaud Héritier resolved as Fixed This is not related to the usage of folders (the same problem exists without it). Workaround: Open you job configuration Add new promotion with the previous name before the renaming. They can be empty. Myself I just checked "Promote immediately once the build is complete" Save your configuration Open you job configuration a second time Remove the promotion with the old name Save your configuration Your job should now work correctly without breaking old promotions and the object model. The issue will be fixed by JENKINS-27716 in promotion plugin > 2.23.1 if you are running on Jenkins >= 1.585 Jenkins / JENKINS-10423 Builds get double promotions after promotion has been renamed Change By: Arnaud Héritier Status: Reopened Resolved Resolution: Fixed Add
[JIRA] [promoted-builds-plugin] (JENKINS-13751) Promoted Builds plugin should pass actual/"root" job to Git plublisher
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-13751 Promoted Builds plugin should pass actual/"root" job to Git plublisher Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-13751) Promoted Builds plugin should pass actual/"root" job to Git plublisher
Title: Message Title SCM/JIRA link daemon commented on JENKINS-13751 Re: Promoted Builds plugin should pass actual/"root" job to Git plublisher Code changed in jenkins User: Nick Caley Path: src/main/java/hudson/plugins/promoted_builds/PromotionProcess.java http://jenkins-ci.org/commit/promoted-builds-plugin/4624722341cf34cab83f00029ac9ddf7163e6be1 Log: [FIXED JENKINS-13751] Allow reference to base SCM in promotion process Previously, plugins such as the Git Publisher would not work in promotion processes because the SCM reference would be empty. This just makes a change to get the base job's SCM when getSCM is called on the promotion process, allowing the use of steps such as the Git Publisher in promotion processes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-12799) When project configuration is changed, Promoted Builds Plugin continues to use "old" configuration data
Title: Message Title Arnaud Héritier assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-12799 When project configuration is changed, Promoted Builds Plugin continues to use "old" configuration data Change By: Arnaud Héritier Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-plugin] (JENKINS-31121) Change log in wiki is not up to date
Title: Message Title Illya Mazuriak resolved as Fixed Jenkins / JENKINS-31121 Change log in wiki is not up to date Change By: Illya Mazuriak Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [google-oauth-plugin] (JENKINS-31638) p12 path not saving in credentials.xml
Title: Message Title Christopher Orr assigned an issue to Andrey Stroilov Jenkins / JENKINS-31638 p12 path not saving in credentials.xml Change By: Christopher Orr Assignee: Matthew Moore Andrey Stroilov Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31732) Download all files from workspace ignores dotfiles
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31732 Download all files from workspace ignores dotfiles Change By: Jesse Glick When I look at the workspace I see dotfiles (e.g. .git). When I go and download the entire workspace (e.g. https: … / /neustar.ci.cloudbees.com/ job/ nexgen whatever / job/nexgen-validate-gitlab/ ws/) I will not receive any dotfiles in the zip file. They are just ignored.A really ugly workaround is to I go into the specific .git folder and click on "all files in zip" I get the files inside of this .git folder. But with multiple such dotfiles its not a userfriendly procedure. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-plugin] (JENKINS-31121) Change log in wiki is not up to date
Title: Message Title Illya Mazuriak started work on JENKINS-31121 Change By: Illya Mazuriak Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xvfb-plugin] (JENKINS-26555) Workflow plugin support
Title: Message Title zregvart resolved as Fixed Workflow support has landed in version 1.1.0 Jenkins / JENKINS-26555 Workflow plugin support Change By: zregvart Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31732) Download all files from workspace ignores dotfiles
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-31732 Download all files from workspace ignores dotfiles Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Nov/15 11:00 PM Priority: Minor Reporter: Owen Wood When I look at the workspace I see dotfiles (e.g. .git). When I go and download the entire workspace (e.g. https://neustar.ci.cloudbees.com/job/nexgen/job/nexgen-validate-gitlab/ws/) I will not receive any dotfiles in the zip file. They are just ignored. A really ugly workaround is to I go into the specific .git folder and click on "all files in zip" I get the files inside of this .git folder. But with multiple such dotfiles its not a userfriendly procedure. Add Comment
[JIRA] [xvfb-plugin] (JENKINS-28928) Make XvfbBuildWrapper extend SimpleBuildWrapper
Title: Message Title zregvart commented on JENKINS-28928 Re: Make XvfbBuildWrapper extend SimpleBuildWrapper The 1.1.0 version is available with workflow support in the update center. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31732) Download all files from workspace ignores dotfiles
Title: Message Title Jesse Glick commented on JENKINS-31732 Re: Download all files from workspace ignores dotfiles My reading of this and this says that this behavior was not a regression in JENKINS-17236 . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extended-choice-parameter-plugin] (JENKINS-31733) Extended Choice Parameter throw exception for Check Boxes type
Title: Message Title
Nam Nguyen created an issue
Jenkins / JENKINS-31733
Extended Choice Parameter throw exception for Check Boxes type
Issue Type:
Bug
Assignee:
vimil
Attachments:
Screen Shot 2015-11-24 at 4.20.13 PM.png
Components:
extended-choice-parameter-plugin
Created:
25/Nov/15 12:22 AM
Environment:
Ubuntu 14.04.3 LTS x64 JDK 1.8.0_65 Jenkins 1.638
Priority:
Critical
Reporter:
Nam Nguyen
When I create Extended Choice Parameter, I got following error exception:
{{A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace
[JIRA] [core] (JENKINS-31649) SECURITY-186 regression: non-item tasks hidden
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31649 SECURITY-186 regression: non-item tasks hidden Change By: Jesse Glick Labels: 1.625.3-rejected permissions regression workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-plugin] (JENKINS-31121) Change log in wiki is not up to date
Title: Message Title Illya Mazuriak assigned an issue to Illya Mazuriak Jenkins / JENKINS-31121 Change log in wiki is not up to date Change By: Illya Mazuriak Assignee: Illya Mazuriak Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-8783) Renamin promotion process doesn't remove the original promotion process
Title: Message Title Michael Peters commented on JENKINS-8783 Re: Renamin promotion process doesn't remove the original promotion process I actually tried this work around multiple times with v2.22 and it did not fix it. Hopefully 2.23.1 fixes this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-publish-plugin] (JENKINS-31717) docker-build-publish plugin no longer works with spaces in the workspace path
Title: Message Title Michael Neale commented on JENKINS-31717 Re: docker-build-publish plugin no longer works with spaces in the workspace path Matthew Baggett so a path with no spaces is ok? this does seem like a regression. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-8783) Renamin promotion process doesn't remove the original promotion process
Title: Message Title Arnaud Héritier resolved as Fixed Jenkins / JENKINS-8783 Renamin promotion process doesn't remove the original promotion process Change By: Arnaud Héritier Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Radek Antoniuk commented on JENKINS-27694 Re: Download update data immediately when installing a new tool installer plugin I don't think that this is related to the signature bug, because the manual Check Now would not work either and it worked for me (see above logs). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [hp-application-automation-tools-plugin] (JENKINS-31617) Unable to build HP tests using HP Performance Center
Title: Message Title SuriyaNarayanan Kalidasan commented on JENKINS-31617 Re: Unable to build HP tests using HP Performance Center Hi Oren, Yes it is the same performance center where I am running the test as well. If you look at console output of the build, Login is succeeded but without test being started logout happens. I don't have access to the PC server machine. This is HP SasS server so I am not able to get the logs Thank you for your attention, Suriya Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [coverity-plugin] (JENKINS-30886) BUG: Could not find Coverity Analysis home directory
Title: Message Title Jeff Grimmett commented on JENKINS-30886 Re: BUG: Could not find Coverity Analysis home directory Same problem here. We have over a dozen build agents (we don't build on the master server). What I found out is that the parameter in the global config is being interpreted as for the master server, and if the master server does not have the designated directory, it will fail. Note, it only needs to have the DIRECTORY. It can be empty. On my build master, it IS empty. That was enough to get things moving. Version 1.6.0, upgraded from 1.4.something. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [junit-plugin] (JENKINS-31660) StackOverflowError when maximum number of builds archived
Title: Message Title kutzi commented on JENKINS-31660 Re: StackOverflowError when maximum number of builds archived Is there a way for the plugin to detect this scenario and make the -Xss suggestion to the user? I don't think that is a feasible approach. Changing the -Xss size should be only a last resort when all other things fail and - if there is really an indefinite loop and not only the large number of jobs is the problem - it wouldn't even solve anything at all. It would be great if you could make the jenkins builds folder of the job available, if it's possible. E.g. if it doesn't contain any sensitive data. So we could try to reproduce this problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gearman-plugin] (JENKINS-31730) OFFLINE_NODE_WHEN_COMPLETE not recognized on manual rebuild leaving node online
Title: Message Title Antoine Musso created an issue Jenkins / JENKINS-31730 OFFLINE_NODE_WHEN_COMPLETE not recognized on manual rebuild leaving node online Issue Type: Bug Assignee: ragesh_nair Components: gearman-plugin, rebuild-plugin Created: 24/Nov/15 8:35 PM Environment: Jenkins 1.625.2 gearman-plugin 1.3 rebuild-plugin 1.25 Priority: Minor Reporter: Antoine Musso When a job is triggered with additional parameters injected by the german-plugin, the rebuild-plugin does not populate them on rebuild. The Wikimedia setup has Zuul/Nodepool/Gearman-plugin. A parameter OFFLINE_NODE_WHEN_COMPLETE is set when the build is triggered via the gearman-plugin. It does not exist in the list of the jobs parameter but the build does show it up being set properly. When hitting [rebuild], previous parameters that are defined in the job configuration are populated from the previous build but the parameter OFFLINE_NODE_WHEN_COMPLETE that got injected is not.
[JIRA] [junit-plugin] (JENKINS-22747) Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files
Title: Message Title Paul Landolt commented on JENKINS-22747 Re: Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files There is a code solution for this. Oleg is reviewing the Pull request and should be accepting it into the plugin soon. (That's my take on it) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-20600) Build issues when folder name (or job name) contains spaces
Title: Message Title Jesse Glick commented on JENKINS-20600 Re: Build issues when folder name (or job name) contains spaces Gregory Fong I do not agree this is a bug at all. Jenkins uses the full name of the folder + job in the workspace path. If your projects have bugs in their build systems preventing them from being built in directories which contain certain characters such as spaces, you should not use those characters in folder or job names (and you should consider configuring Restrict project naming to make sure no one forgets); you can feel free to use any wild characters in display names. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-31731) Git-plugin duplicate builds & can theoretically infinitely build the same commit
Title: Message Title Brandon Jacklyn created an issue Jenkins / JENKINS-31731 Git-plugin duplicate builds & can theoretically infinitely build the same commit Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 24/Nov/15 9:45 PM Environment: git-plugin 2.4.0 Priority: Major Reporter: Brandon Jacklyn Summary There is a race condition when "Execute concurrent builds" is checked. When one or more builds are scheduled at the same time they all retrieve the same BuildData (linear search of previous builds until the first BuildData is found), and thus they all choose the same commit to build. If there are multiple branches to build each job also schedules another build. As long as the latest build has not yet determined what commit to build, the newly scheduled jobs will also use that same inaccurate BuildData which is infinitely passed along to newly scheduled jobs. To break this chain, the latest build must finish determining the commit to build before any new jobs perform "checkout()" which is where the previous build's BuildData is retrieved. I watched my instance with the environment below build the same commit ~50 times between 2 slaves before I turned it off. Minimum environment to reproduce
[JIRA] [core] (JENKINS-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Radek Antoniuk commented on JENKINS-27694 Re: Download update data immediately when installing a new tool installer plugin Update: This WORKS with jenkins:weekly image that is 1.596 (old for weekly though). Seems that it does not work with newer Jenkins 1.625.1... or another magic/race condition is happening - but I am consistently reproducing it with the above scenario. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Radek Antoniuk reopened an issue Jenkins / JENKINS-27694 Download update data immediately when installing a new tool installer plugin Change By: Radek Antoniuk Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gearman-plugin] (JENKINS-31730) OFFLINE_NODE_WHEN_COMPLETE not recognized on manual rebuild leaving node online
Title: Message Title Antoine Musso commented on JENKINS-31730 Re: OFFLINE_NODE_WHEN_COMPLETE not recognized on manual rebuild leaving node online Might be the same as: JENKINS-29671 JENKINS-27340 Seems to be a regression from 1.22 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-20600) Build issues when folder name (or job name) contains spaces
Title: Message Title Gregory Fong commented on JENKINS-20600 Re: Build issues when folder name (or job name) contains spaces I agree there's a straightforward workaround, but it's wrong to say this is "Not A Defect". This is still a bug, albeit a minor one. Could this be reopened, possibly with a much lower priority than before? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gearman-plugin] (JENKINS-31730) OFFLINE_NODE_WHEN_COMPLETE not recognized on manual rebuild leaving node online
Title: Message Title Antoine Musso edited a comment on JENKINS-31730 Re: OFFLINE_NODE_WHEN_COMPLETE not recognized on manual rebuild leaving node online Might be the same as:* JENKINS-29671* JENKINS-27340Seems to be a regression from 1.22 . Possibly introduced by the fix for JENKINS-20288 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [rebuild-plugin] (JENKINS-20288) The rebuild plugin doesn't support custom parameter types
Title: Message Title Antoine Musso commented on JENKINS-20288 Re: The rebuild plugin doesn't support custom parameter types Seems the patch causes rebuild plugin from 1.22 to no more inject parameters that might have been injected in addition to the parameters defined in the job. There is at least three issues mentioning that: JENKINS-29671 JENKINS-27340 JENKINS-31730 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-pipeline-plugin] (JENKINS-27238) Inject parameters on manual build trigger
Title: Message Title Ole Christian Langfjæran commented on JENKINS-27238 Re: Inject parameters on manual build trigger Not knowing the inner workings of the plugin, but is this doable in some way? Would be a an absolutely great feature. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-publish-plugin] (JENKINS-31717) docker-build-publish plugin no longer works with spaces in the workspace path
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31717 Re: docker-build-publish plugin no longer works with spaces in the workspace path Code changed in jenkins User: Michael Neale Path: src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java http://jenkins-ci.org/commit/docker-build-publish-plugin/fae73184f1e707868a2e8958ed11c62b258a8419 Log: fix for JENKINS-31717 allow spaces in workspace Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [stash-pullrequest-builder-plugin] (JENKINS-30558) Cron based jobs are no longer triggered
Title: Message Title Jonathan Strickland commented on JENKINS-30558 Re: Cron based jobs are no longer triggered james norman The Stash Pull Requester plugin was a great initial choice for us to get started. Check out https://marketplace.atlassian.com/plugins/se.bjurr.prnfs.pull-request-notifier-for-stash/server/overview for the push model; this has been serving us well for over a month now (less load on Jenkins and the stash server too). https://christiangalsterer.wordpress.com/2015/04/23/continuous-integration-for-pull-requests-with-jenkins-and-stash/ gives a good walk-through. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xvfb-plugin] (JENKINS-28147) Xvfb not terminated when a Maven module rebuild fails inside a plugin
Title: Message Title Sean Flanigan commented on JENKINS-28147 Re: Xvfb not terminated when a Maven module rebuild fails inside a plugin Thanks, zregvart. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-20600) Build issues when folder name (or job name) contains spaces
Title: Message Title Gregory Fong commented on JENKINS-20600 Re: Build issues when folder name (or job name) contains spaces Jesse Glick Our build system handles spaces just fine. The issue I was finding was when passing in the ``--strip-path $WORKSPACE`` with the coverity plugin. There doesn't seem to be any good way to quote or escape the contents of "$WORKSPACE" such that it will work properly, though thinking about it more I'm not quite sure this is an issue with how jenkins passes things to the coverity plugin or with the coverity plugin itself. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29547) "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section
Title: Message Title mdonohue commented on JENKINS-29547 Re: "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section And here is the pull request: https://github.com/jenkinsci/jenkins/pull/1881 I'm still working on getting it accepted. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [throttle-concurrent-builds-plugin] (JENKINS-31734) TCB plugin not working correctly in my environment
Title: Message Title Ramanjaneya Kumar Tummalapalli created an issue Jenkins / JENKINS-31734 TCB plugin not working correctly in my environment Issue Type: Bug Assignee: Oleg Nenashev Attachments: build_status.png, job_config.png Components: throttle-concurrent-builds-plugin Created: 25/Nov/15 4:55 AM Priority: Blocker Reporter: Ramanjaneya Kumar Tummalapalli Let us take a scenario.. Based on file parsing i need to launch a job multiple times with different arguments.. But my git server can allow parallel clones of 5 If file is giving set of 10 different arguments, i need to launch a job 10 times with different arguments In my job configuration, i set as below -> Throttle this project alone -> Maximum total concurrent builds : 3 -> Maximum concurrent builds per node : 1 So, when 10 jobs launched at a time, for the first time it worked correctly and took only 3 jobs into executors but after completion of 3 build, it is taking all other remaining 7 builds at a time because of which my jobs failing by skipping SCM step (skipped fetching source code). Attached scheenshots.. My
[JIRA] [remoting] (JENKINS-31735) Remoting : NioChannelHub is not currently running
Title: Message Title manohar joshi created an issue Jenkins / JENKINS-31735 Remoting : NioChannelHub is not currently running Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: remoting, vsphere-cloud-plugin, windows-slaves-plugin Created: 25/Nov/15 4:59 AM Environment: Master Jenkins slave on Ubuntu 12.04 Slave Windows 2008 R2 Server JRE 1.8 Labels: remoting niochanelhub windows Priority: Major Reporter: manohar joshi When We try to reconnect any windows slave it throws following exception. JNLP agent connected from /10.219.160.235 <===[JENKINS REMOTING CAPACITY]===>Failed to establish the connection with the slave IB-TC-5 java.io.IOException: NioChannelHub is not currently running at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:492) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:351) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:280) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:290) at
[JIRA] [email-ext-plugin] (JENKINS-31736) Failure in plugin due to execessive (log) output
Title: Message Title Rafere Gluyas created an issue Jenkins / JENKINS-31736 Failure in plugin due to execessive (log) output Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 25/Nov/15 5:31 AM Environment: java.version 1.7.0_85 email-ext 2.39 Jenkins ver. 1.631 Priority: Minor Reporter: Rafere Gluyas This only occurs during excessive log output, where a log is usually less than 1MB, in this failure the (text) log was in excess of 20GB. Exception raised during template rendering: null java.lang.NullPointerException at java.io.File.(File.java:277) at sun.reflect.GeneratedConstructorAccessor881.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77) at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:102) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:190) at SimpleTemplateScript39.run(SimpleTemplateScript39.groovy:58) at groovy.text.SimpleTemplateEngine$SimpleTemplate$1.writeTo(SimpleTemplateEngine.java:165) at
[JIRA] [workflow-plugin] (JENKINS-31721) Workflow depended jars not getting download
Title: Message Title Yogesh sharma reopened an issue Added comment above Jenkins / JENKINS-31721 Workflow depended jars not getting download Change By: Yogesh sharma Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31721) Workflow depended jars not getting download
Title: Message Title Yogesh sharma commented on JENKINS-31721 Re: Workflow depended jars not getting download Jesse, to download Workflow plugin we need to download all its Dependencies workflow-job (version:1.11) , workflow-api (version:1.11) etc.. but when we are trying to click on any Dependencies it is redirecting to Workflow plugin home page only. How do we download all required Dependencies for this WOrkflow plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xvfb-plugin] (JENKINS-28928) Make XvfbBuildWrapper extend SimpleBuildWrapper
Title: Message Title Timo Stollenwerk commented on JENKINS-28928 Re: Make XvfbBuildWrapper extend SimpleBuildWrapper Awesome! Thanks for your work! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [throttle-concurrent-builds-plugin] (JENKINS-31734) TCB plugin not working correctly in my environment
Title: Message Title Oleg Nenashev commented on JENKINS-31734 Re: TCB plugin not working correctly in my environment It's a known regression in Jenkins core. You should use 1.609.2 at least Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-dependency-update-trigger-plugin] (JENKINS-31729) maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also
Title: Message Title Sarit Sotangkur commented on JENKINS-31729 Re: maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also @alecharp, @victornoel, I believe that because this plugin is named "maven-dependency-update-trigger-plugin" then it should support all cases were the maven dependency was updated, not just the specific case where the dependency happens to be a snapshot dependency. That makes this feature request within the scope of this plugin. Now, implementation-wise, supporting this request might be a huge departure from the current snapshot-only implementation, however differences in implementation should not dictate scope definition. I suppose, if you really did not want this to be part of the scope, then the plugin should be renamed to "maven-snapshot-dependency-update-trigger-plugin" to avoid the implication that it can handle all types of dependencies. ...If at some point, Maven upgrade a dependency without your consent, you could have regression because of the new version of the dependency. This is not an issue for me as I can constrain which dependencies I choose to update based on criteria such as group id. The plugin should provide similar capabilities. If you look at the "Controlling which dependencies are processed" section of http://www.mojohaus.org/versions-maven-plugin/examples/advancing-dependency-versions.html you can see that simply combining your trigger plugin with non-snapshot support and this codehaus maven plugin, I can get exactly what I need. If you need code to figure out how to check for updated dependencies, that codehaus plugin already does it (we just need you to integrate it with the triggering logic in jenkins). Codehaus updated dependency checking -> http://www.mojohaus.org/versions-maven-plugin/examples/display-dependency-updates.html Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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
[JIRA] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs Code changed in jenkins User: Jesse Glick Path: changelog.html war/pom.xml http://jenkins-ci.org/commit/jenkins/d76ee3e5179dd50e96e6c8e1d67ffbdec7f88a7b Log: JENKINS-20327 Noting merge of #1922. Compare: https://github.com/jenkinsci/jenkins/compare/ab0198246c1c...d76ee3e5179d Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-20327 “Form too large” errors submitting view configurations with many jobs Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs Code changed in jenkins User: Jesse Glick Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/8f012d63d771b22d74eec8396b2895f0e45f0e6f Log: [FIXED JENKINS-20327] Integrate Winstone 2.9. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Jay Kah commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" We are having the same issue on Jenkins ver. 1.634 on Ubuntu Trusty. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31536) Jobs hanging in Build Executor even if it is finished
Title: Message Title Daniel Beck commented on JENKINS-31536 Re: Jobs hanging in Build Executor even if it is finished stephenconnolly Any idea what's going on here? Possibly related to your recent queue work? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-29935) Installing JDK on Windows Slave 8.1
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-29935 Installing JDK on Windows Slave 8.1 Change By: Daniel Beck Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31649) SECURITY-186 fix is too aggressive
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31649 SECURITY-186 fix is too aggressive Change By: Jesse Glick Labels: 1.625.3-rejected regression Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-31718) JNLP slaves can fail to correctly negotiate a transport
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31718 JNLP slaves can fail to correctly negotiate a transport Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Daniel Beck resolved as Fixed Cannot reproduce this not working, so resolving as fixed again. Jenkins / JENKINS-27694 Download update data immediately when installing a new tool installer plugin Change By: Daniel Beck Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-dependency-update-trigger-plugin] (JENKINS-31729) maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also
Title: Message Title Sarit Sotangkur commented on JENKINS-31729 Re: maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also victornoel commented 7 hours ago Maybe you could implement your need with more generic trigger plugins from Jenkins, but what you are talking about is out of the scope of this plugin I think. I understand your need, but here is the wrong place (anyway, the correct way to ask for feature is the jenkins jira, not here, the github issues for this project should be disabled I think, don't you think @alecharp). @alecharp Collaborator alecharp commented 3 hours ago I agree @victornoel, Github issues should not be used, only Jira. @ssotangkur, please create a ticket on Jira. However, I don't think you can really use this plugin for what you need. Maven don't detect new versions per say, as it download the metadata file for an artifact version and see if it's newer than the one in the current repository. But it does not look for newer versions. Even, you specifically put a release version on your pom to make sure this is the one you use in production. If at some point, Maven upgrade a dependency without your consent, you could have regression because of the new version of the dependency. I agree that for continuous deployment, you need to consider every deployed version as release, to be able to find the code and fix them. But I don't think this plugin will help you achieve that. Sorry. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-10547) Windows service can't start if Windows Application Event log is full
Title: Message Title Daniel Beck resolved as Fixed Should be fixed in Jenkins 1.630+ Jenkins / JENKINS-10547 Windows service can't start if Windows Application Event log is full Change By: Daniel Beck Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-12731) Reducing the steps required for initial lockdown of a Jenkins instance (open ports, default permissions, etc.)
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-12731 Reducing the steps required for initial lockdown of a Jenkins instance (open ports, default permissions, etc.) Change By: Daniel Beck Component/s: plugin-proposals Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-12731) Reducing the steps required for initial lockdown of a Jenkins instance (open ports, default permissions, etc.)
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-12731 Reducing the steps required for initial lockdown of a Jenkins instance (open ports, default permissions, etc.) Change By: Daniel Beck Labels: 2.0 security Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [dynamicparameter-plugin] (JENKINS-21071) Using Scriptlers in Dynamic Build Parameters AND Build-Steps executs the wrong Scriptler in the Build-Step
Title: Message Title Guy Matz commented on JENKINS-21071 Re: Using Scriptlers in Dynamic Build Parameters AND Build-Steps executs the wrong Scriptler in the Build-Step Bumping into this too . .. frustrating . . . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-31718) JNLP slaves can fail to correctly negotiate a transport
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31718 Re: JNLP slaves can fail to correctly negotiate a transport Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/Capability.java src/main/java/hudson/remoting/ChannelBuilder.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol1.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol2.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol3.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocol1Test.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocol2Test.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocol3Test.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocolTest.java http://jenkins-ci.org/commit/remoting/17aa60dd6c84499962a7117027da3e73e392ce46 Log: [FIXED JENKINS-31718] Preserve the BufferedInputStream when building the transport For now I do not have the energy to fix the tests to not need the 'null' backdoor. Most likely some non-mock based tests would be better and likely would have caught this regression sooner. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-31718) JNLP slaves can fail to correctly negotiate a transport
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31718 Re: JNLP slaves can fail to correctly negotiate a transport Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol1.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol2.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol3.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocol1Test.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocol2Test.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocol3Test.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocolTest.java http://jenkins-ci.org/commit/remoting/7a50cd2e8e8d40b243eab5584e5ae44d48215b2d Log: JENKINS-31718 Fix the tests The tests no longer pass in a null buffered input stream and thus we can remove the null handling from the protocols Unsure whether the buffer may affect JnlpProtocol3 performance, but leaving it there to highlight the potential stream corruption if the buffer gets thrown away. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31649) SECURITY-186 regression: non-item tasks hidden
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-31649
SECURITY-186 regression: non-item tasks hidden
Reproducible in 1.625.2 even with no security: create a Workflow job
node('whatever') {}
and build. You should see an entry in the queue widget, but you do not.
Change By:
Jesse Glick
Labels:
1.625.3-rejected regression workflow
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-31649) SECURITY-186 regression: non-item tasks hidden
Title: Message Title Jesse Glick commented on JENKINS-31649 Re: SECURITY-186 regression: non-item tasks hidden PR 1919 would not fix that. However I could make PlaceholderTask be AccessControlled, in which case a backport of this fix plus a plugin update would correct the regression. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-dependency-update-trigger-plugin] (JENKINS-31729) maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also
Title: Message Title Sarit Sotangkur created an issue Jenkins / JENKINS-31729 maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also Issue Type: New Feature Assignee: olamy Components: maven-dependency-update-trigger-plugin Created: 24/Nov/15 4:38 PM Priority: Major Reporter: Sarit Sotangkur For continuous deployment, one needs every build to have its own release version number (not SNAPSHOT). When one dependency is built it is necessary to trigger the build of dependent projects. We would like the plugin to trigger the build of dependent projects even if they are not SNAPSHOT dependencies. This functionality requested is very similar to what is available in the Ivy trigger (https://wiki.jenkins-ci.org/display/JENKINS/IvyTrigger+Plugin). Add Comment
[JIRA] [maven-dependency-update-trigger-plugin] (JENKINS-31729) maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also
Title: Message Title Sarit Sotangkur commented on JENKINS-31729 Re: maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also Here are the comments copied from the GItHub Issue where this originated (https://github.com/jenkinsci/maven-dependency-update-trigger-plugin/issues/5) ssotangk commented on Oct 22 In a continuous deployment environment, each build artifact should have a release number instead of a snapshot. Teams should have a choice to build when a dependency is built even if the dependency is not a snapshot dependency. @emoshaya-cognito emoshaya-cognito commented 13 days ago completely agree with @ssotangk we will also stop using snapshots in our builds in order to have every commit a potential release. It would be nice to have the update trigger support release dependencies too. @victornoel victornoel commented a day ago Well… if it's not a SNAPSHOT, you have to update the version in the dependant project for the latest version to be used, and then commit it, which should trigger a build: you don't need maven-dependency-update-trigger-plugin for that! @ssotangkur ssotangkur commented 22 hours ago Hi @victornoel, I'm saying that if we can trigger the dependent project to run, then the project can do the dependency check and update its own dependency's versions. You're right in that if we could know when a dependent project should update its dependencies, then we could update them and that would trigger a commit and then cause it to be built w/o maven-dependency-update-trigger-plugin. The one only thing that's missing, however, is we still need that thing that lets us know we should update a particular project (out of possibly many other projects) because its dependency(s) have been updated. An "update-trigger" is nice for this because, it not only let's us know which ones need updating, but also goes ahead and triggers them to start that process. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you
[JIRA] [core] (JENKINS-9802) Manage Plugins section should be more informative and User freindly
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-9802 Manage Plugins section should be more informative and User freindly Change By: Daniel Beck Component/s: core Component/s: plugin-proposals Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [delivery-pipeline-plugin] (JENKINS-25891) Ability to link to individual pipeline
Title: Message Title Patrice Matignon commented on JENKINS-25891 Re: Ability to link to individual pipeline Just a possible implementation idea: this could be done relatively simply, by generating html anchors for each pipeline instance, and probably some sort of visual highlighting of the designated pipeline (e.g., a backgroung color). As mentioned above, if the pipeline instance is not in the standard top-n view, then the view should be expanded automatically (there is also a pagination ticket that could be related). Alternatively, an individual pipeline link could represent only this one pipeline. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31691) add a step to determine if the current node is windows or not.
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31691 add a step to determine if the current node is windows or not. Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31691) add a step to determine if the current node is windows or not.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31691 Re: add a step to determine if the current node is windows or not. Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/IsUnixStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/IsUnixStep.java basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/IsUnixStep/config.jelly basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/IsUnixStep/help.html http://jenkins-ci.org/commit/workflow-plugin/3d60b260ee0c069aad72897fcce819923964ea69 Log: Merge pull request #256 from jglick/isUnix- JENKINS-31691 JENKINS-31691 isUnix step Compare: https://github.com/jenkinsci/workflow-plugin/compare/13a467c07203...3d60b260ee0c Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31691) add a step to determine if the current node is windows or not.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31691 Re: add a step to determine if the current node is windows or not. Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/IsUnixStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/IsUnixStep.java basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/IsUnixStep/config.jelly basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/IsUnixStep/help.html http://jenkins-ci.org/commit/workflow-plugin/bbd1e838533601139b6daf2f255d456b5090b329 Log: [FIXED JENKINS-31691] Added isUnix step. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-31718) JNLP slaves can fail to correctly negotiate a transport
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31718 JNLP slaves can fail to correctly negotiate a transport Change By: Jesse Glick Labels: lts-candidate regression Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31649) SECURITY-186 regression: non-item tasks hidden
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31649 SECURITY-186 regression: non-item tasks hidden Change By: Jesse Glick Summary: SECURITY-186 fix is too aggressive regression: non-item tasks hidden Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31721) Workflow depended jars not getting download
Title: Message Title Jesse Glick resolved as Incomplete Can you explain please? Jenkins / JENKINS-31721 Workflow depended jars not getting download Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [dry-plugin] (JENKINS-31421) Show the number of duplicate lines in the graph
Title: Message Title Chris Pepper commented on JENKINS-31421 Re: Show the number of duplicate lines in the graph Sorry, I didn't see your comment. I think the plugin should just have an option that instead of the number of issues, the number of total duplicate lines is used. The type of graph can be the same as before. In the "Duplicate code" details page in could be the same, instead of showing the number of issues per file/folder it would show the number of lines of duplicate code. I don't have time for developing this at the moment, sorry. I just thought I'd make to comment as it would be nice to have. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Radek Antoniuk commented on JENKINS-27694 Re: Download update data immediately when installing a new tool installer plugin Sorry for late answer, steps to reproduce on docker: 1. mkdir /tmp/jenkins && chmod 777 /tmp/jenkins && docker run --rm -v /tmp/jenkins:/var/jenkins_home -p 1:8080 jenkins:1.625.1 2. cd /tmp/jenkins/plugins && wget http://updates.jenkins-ci.org/latest/golang.hpi 3. restart Jenkins via /safeRestart Expected: Jenkins unpacks the .hpi file and runs UpdateCenter to populate GoLang data dropdown Actual: Jenkins unpacks the .hpi file but UpdateCenter is not run After hitting the "Check Now" on the UI, indeed I can see: Nov 24, 2015 7:28:16 PM hudson.model.UpdateSite updateData INFO: Obtained the latest update center data file for UpdateSource default Nov 24, 2015 7:28:16 PM hudson.model.DownloadService$Downloadable load INFO: Obtained the updated data file for hudson.tasks.Maven.MavenInstaller Nov 24, 2015 7:28:17 PM hudson.model.DownloadService$Downloadable load INFO: Obtained the updated data file for hudson.tasks.Ant.AntInstaller Nov 24, 2015 7:28:19 PM hudson.model.DownloadService$Downloadable load INFO: Obtained the updated data file for hudson.tools.JDKInstaller Nov 24, 2015 7:28:21 PM hudson.model.DownloadService$Downloadable load INFO: Obtained the updated data file for org.jenkinsci.plugins.golang.GolangInstaller However, seems that DownloadService is not invoked automatically during the restart phase - what makes sense if you think of it - but in this case it makes the UI unusable, so maybe the golang plugin itself is not registering something properly? Add Comment
[JIRA] [promoted-builds-plugin] (JENKINS-27716) Copying A Job With Promotions and Renaming New Promotion Causes Phantom Promotions
Title: Message Title Arnaud Héritier assigned an issue to Benjamin Heiskell Jenkins / JENKINS-27716 Copying A Job With Promotions and Renaming New Promotion Causes Phantom Promotions Change By: Arnaud Héritier Assignee: Benjamin Heiskell Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xvfb-plugin] (JENKINS-28147) Xvfb not terminated when a Maven module rebuild fails inside a plugin
Title: Message Title zregvart resolved as Fixed The pull request was merged against the maven plugin, it should be fixed with the release of version 2.13. Jenkins / JENKINS-28147 Xvfb not terminated when a Maven module rebuild fails inside a plugin Change By: zregvart Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jira-plugin] (JENKINS-31301) Jira Plugin - Rest Client add comment failures
Title: Message Title Radek Antoniuk commented on JENKINS-31301 Re: Jira Plugin - Rest Client add comment failures That's what I thought - regarding idempotent methods. Let try to see what the plugin is actually sending/receiving. Please configure additional logger in Jenkins and add the following loggers with level ALL: hudson.plugins.jira org.apache.http.impl.client org.apache.http.wire You should be able to see the full request send/received from JIRA then. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [acceptance-test-harness] (JENKINS-31648) ATH Tests for Folder Plugin: Folder creation
Title: Message Title Yariv Sheizaf commented on JENKINS-31648 Re: ATH Tests for Folder Plugin: Folder creation HI, I isntalled the new main.css code. The names and size of the jobs are now perfect. The problem is that the the main frame horizontal scroll does not exist anymore. So, navigation is possible or using internal scroll line (which is in the semi-hidden bottom of the frame) or using the left/right arrows in the keyboard Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31715) Slave Went Offline During Build - Invalid Stream Header 0b3caced
Title: Message Title Florian Doersch created an issue Jenkins / JENKINS-31715 Slave Went Offline During Build - Invalid Stream Header 0b3caced Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Nov/15 8:17 AM Environment: at least at jenkins 1.638 with sun jre 8 Priority: Critical Reporter: Florian Doersch I get a lot aborted builds lately, with the error "Slave went offline during build". On the slave machines (windows 7), the error java.io.StreamCorruptedException: invalid stream header 0b3caced appears. The same error 0b3caced appears for multiple machines. I already tried to set a fixed jnlp port, but it seems not to help Any ideas?
[JIRA] [deploy-plugin] (JENKINS-24594) [Deploy-Plugin] Support Tomcat 8
Title: Message Title Bob Kubista commented on JENKINS-24594 Re: [Deploy-Plugin] Support Tomcat 8 This has already been submitted for pull request. Please accept this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-31591) MasterKillSwitchConfiguration is not available when you have clouds but no fixed slaves
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-31591 MasterKillSwitchConfiguration is not available when you have clouds but no fixed slaves Change By: Oliver Gondža Labels: cloud lts 1.625.3 - candidate rejected cloud security Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [sqlplus-script-runner-plugin] (JENKINS-31597) SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-31597 SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level Change By: Raphaël UNIQUE Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [sqlplus-script-runner-plugin] (JENKINS-31597) SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level
Title: Message Title Raphaël UNIQUE commented on JENKINS-31597 Re: SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level Fernando, it's better, but should be perfect if i can use environment variables for example: attached snapshot my ORACLE_HOME is setted at slave level in my job configuration, i have setted the ORACLE_HOME value with the $ORACLE_HOME variable Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [sqlplus-script-runner-plugin] (JENKINS-31597) SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-31597 SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level Change By: Raphaël UNIQUE Attachment: screenshot-2.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
