[JIRA] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title Oleg Nenashev reopened an issue Pushed the branch to a wrong repo Jenkins / JENKINS-28656 Docker Traceability should support the creation of image fingerprints on-demand Change By: Oleg Nenashev 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] [fitnesse-plugin] (JENKINS-27938) Unable to expand collapsed SLIM tables
Title: Message Title Antoine Aumjaud assigned an issue to Antoine Aumjaud Jenkins / JENKINS-27938 Unable to expand collapsed SLIM tables Change By: Antoine Aumjaud Assignee: Antoine Aumjaud 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-traceability-plugin] (JENKINS-28706) Hide Docker Traceability Root Action by default
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28706 Hide Docker Traceability Root Action by default Issue Type: Improvement Assignee: Oleg Nenashev Components: docker-traceability-plugin Created: 03/Jun/15 6:14 AM Priority: Minor Reporter: Oleg Nenashev The root action is not very helpful in the current version. It makes sense to hide it by default in order to prevent the sidepanel pollution. Add Comment This message was
[JIRA] [fitnesse-plugin] (JENKINS-28316) Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again
Title: Message Title Antoine Aumjaud assigned an issue to Antoine Aumjaud Jenkins / JENKINS-28316 Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again Change By: Antoine Aumjaud Assignee: Antoine Aumjaud 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] [sauce-ondemand-plugin] (JENKINS-28651) Sauce Connect doesn't work using v4 but it works fine with v3
Title: Message Title Ross Rowe commented on JENKINS-28651 Re: Sauce Connect doesn't work using v4 but it works fine with v3 It looks like Sauce Connect is failing to start because of the 'Error opening sc_my-tun2.log: No such file or directory' error. The default location for the Sauce Connect log file is /tmp, and my guess is that Sauce Connect v4 can't write to this directory due to the permissions of the user which launched Jenkins. Can you try supply a different value for the log location for Sauce Connect? You can do this by including --logfile /path/to/sc.log in the Sauce Connect Options field within the Jenkins job configuration (under Sauce Connect Advanced Options) where /path/to is a location on the Jenkins server which the user has write access to. 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-tag-message-plugin] (JENKINS-28705) Plugin expose the actual tag name as enviroment variable
Title: Message Title Thomas Blitz created an issue Jenkins / JENKINS-28705 Plugin expose the actual tag name as enviroment variable Issue Type: New Feature Assignee: Thomas Blitz Components: git-tag-message-plugin Created: 03/Jun/15 6:06 AM Labels: plugin, feature git-tag git-tag-message Priority: Minor Reporter: Thomas Blitz The plugin should expose the actual tagname as an enviroment variable. The change is already made and a pull request has been issued on github. see the URL in this feature request. This feature is simply waiting for a github pull request merge. Add Comment
[JIRA] [fitnesse-plugin] (JENKINS-25010) NullPointerException running FitNesse-tests
Title: Message Title Antoine Aumjaud closed an issue as Fixed Jenkins / JENKINS-25010 NullPointerException running FitNesse-tests Change By: Antoine Aumjaud Status: Resolved Closed 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-21301) Jenkins stops responding to HTTP requests outside builds
Title: Message Title Antoine Aumjaud updated an issue Jenkins / JENKINS-21301 Jenkins stops responding to HTTP requests outside builds Change By: Antoine Aumjaud Component/s: fitnesse-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] [conditional-buildstep-plugin] (JENKINS-21636) When using Contional steps(multiple) plugin config the Fitnesse configuration values are getting null
Title: Message Title Antoine Aumjaud resolved as Fixed in version 1.13 Jenkins / JENKINS-21636 When using Contional steps(multiple) plugin config the Fitnesse configuration values are getting null Change By: Antoine Aumjaud 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] [conditional-buildstep-plugin] (JENKINS-21636) When using Contional steps(multiple) plugin config the Fitnesse configuration values are getting null
Title: Message Title Antoine Aumjaud closed an issue as Fixed Jenkins / JENKINS-21636 When using Contional steps(multiple) plugin config the Fitnesse configuration values are getting null Change By: Antoine Aumjaud Status: Resolved Closed 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] [sauce-ondemand-plugin] (JENKINS-28651) Sauce Connect doesn't work using v4 but it works fine with v3
Title: Message Title akash sharma assigned an issue to Ross Rowe Jenkins / JENKINS-28651 Sauce Connect doesn't work using v4 but it works fine with v3 Change By: akash sharma Assignee: Kohsuke Kawaguchi Ross Rowe 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] [unity3d-plugin] (JENKINS-16170) Ability for the plugin to auto-install Unity3d
Title: Message Title lacostej commented on JENKINS-16170 Re: Ability for the plugin to auto-install Unity3d I have scripts that I use to install unity3d from the command line: https://bitbucket.org/WeWantToKnow/unity3d_scripts works on mac os x, unfinalized on Windows. Please try them and see if that works for you. Now that I have stabilized this plugin, I am currently thinking of moving the running and intalling of unity3d into a command line tool, as a mix of shenzhen/ipa and https://github.com/neonichu/xcode-install. It would be better if this feature was completely outside jenkins for real CLI usage. 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] [matrix-auth-plugin] (JENKINS-23844) Matrix based security should apply to case insensitive user name.
Title: Message Title jothibasu k updated an issue Jenkins / JENKINS-23844 Matrix based security should apply to case insensitive user name. Change By: jothibasu k Issue Type: Improvement Bug 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] [matrix-auth-plugin] (JENKINS-23844) Matrix based security should apply to case insensitive user name.
Title: Message Title jothibasu k commented on JENKINS-23844 Re: Matrix based security should apply to case insensitive user name. Please check on 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] [matrix-auth-plugin] (JENKINS-23844) Matrix based security should apply to case insensitive user name.
Title: Message Title jothibasu k updated an issue Jenkins / JENKINS-23844 Matrix based security should apply to case insensitive user name. Change By: jothibasu k Priority: Major Blocker 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] [active-directory-plugin] (JENKINS-12607) Active directory user names should not be case sensitive.
Title: Message Title jothibasu k updated an issue Jenkins / JENKINS-12607 Active directory user names should not be case sensitive. Change By: jothibasu k Priority: Minor Blocker 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] [active-directory-plugin] (JENKINS-12607) Active directory user names should not be case sensitive.
Title: Message Title jothibasu k commented on JENKINS-12607 Re: Active directory user names should not be case sensitive. Guys any update on this issue... we facing this issue while trying to integrate with JIRA..Please check 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] [unity3d-plugin] (JENKINS-16170) Ability for the plugin to auto-install Unity3d
Title: Message Title Brantone commented on JENKINS-16170 Re: Ability for the plugin to auto-install Unity3d Now that Unity 5.x has command line licensing, this would be possible. Would also be handy to have option to specify directory to which it gets installed so as to have multiple versions of Unity installed simultaneously. 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-28704) [Regression] Ball on build in progress does not open console
Title: Message Title Thomas Suckow started work on JENKINS-28704 Change By: Thomas Suckow 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] [build-timeout-plugin] (JENKINS-28125) No e-mail is sent if build is aborted
Title: Message Title ikedam resolved as Won't Fix It is considered as an issue of maven-plugin. Jenkins / JENKINS-28125 No e-mail is sent if build is aborted Change By: ikedam Status: Open Resolved Resolution: Won't Fix 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-28704) [Regression] Ball on build in progress does not open console
Title: Message Title Thomas Suckow updated an issue Jenkins / JENKINS-28704 [Regression] Ball on build in progress does not open console Change By: Thomas Suckow URL: https://github.com/jenkinsci/jenkins/pull/1727 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] [flexible-publish-plugin] (JENKINS-28585) Flexible Publish no longer expands variables in multiconfiguration job
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-28585 Flexible Publish no longer expands variables in multiconfiguration job Change By: ikedam Assignee: bap ikedam 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-28425) UI: Build history overflows
Title: Message Title Thomas Suckow resolved as Fixed Regression documented at JENKINS-28704 Jenkins / JENKINS-28425 UI: Build history overflows Change By: Thomas Suckow 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-28704) [Regression] Ball on build in progress does not open console
Title: Message Title
Thomas Suckow created an issue
Jenkins / JENKINS-28704
[Regression] Ball on build in progress does not open console
Issue Type:
Bug
Assignee:
Thomas Suckow
Components:
core
Created:
02/Jun/15 11:13 PM
Labels:
core css build-history
Priority:
Major
Reporter:
Thomas Suckow
JENKINS-28425 created a regression where the ball on an build in progress does not open the console.
The selectors never should have been grouped together even though the spacing should be the same.
Fix:
.build-row-cell .pane.build-name .display-name {
margin-left: 20px;
}
.build-row-cell .indent-multiline {
padding-left: 20px !important; /* Sync changes with func expandControlsTo50Percent in hudson-behavior.js */
}
[JIRA] [windows-slaves-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title William Woodall commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave Yeah, I totally agree this is a bug or undocumented behavior or both and something should be done. I should have said restarting our master worked around the issue for us too. 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] [windows-slaves-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Nathan Neulinger commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave Just to be clear though, "restart master =~ clear cache" and not a permanent fix. 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] [windows-slaves-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title William Woodall commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave Restarting our master fixed this issue for me as well. 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] [support-core-plugin] (JENKINS-28703) add the pinned status of a plugin to the support bundle
Title: Message Title James Nord created an issue Jenkins / JENKINS-28703 add the pinned status of a plugin to the support bundle Issue Type: New Feature Assignee: Steven Christou Components: support-core-plugin Created: 02/Jun/15 10:07 PM Priority: Minor Reporter: James Nord It would be useful to be able to see which plugins are pinned in a support bundle. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [windows-slaves-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title William Woodall commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave I've also run into this. I thought I was going completely crazy. We're using Jenkins ver. 1.611 and Java version 1.7.0_79-b14. We do not have any environment variables set in the config for the master or the slave and the slave is running on Windows. I tried both as a service and from the cmd.exe prompt. We are not using the EnvInject 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] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
Title: Message Title Forest Handford commented on JENKINS-26519 Re: Build records not migrated due to “failed to rename” on Windows FYI: I ran into this same issue on CentOS 6.5. Old directories had symlinks like: lrwxrwxrwx. 1 jenkins jenkins 19 Apr 22 09:06 401 -> 2015-04-22_09-06-23 New directories looked like: drwxr-xr-x. 2 jenkins jenkins 4096 Mar 1 01:28 317 The UI showed the old builds as having run before I was born! In order to re-run the migration I did the following: sudo find /var/lib/jenkins/ -name legacyIds -delete sudo service jenkins restart Once this was done things looked correct. 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] [github-plugin] (JENKINS-28701) Script runs in Script Console but not with Job DSL groovy
Title: Message Title Sam Gleske commented on JENKINS-28701 Re: Script runs in Script Console but not with Job DSL groovy Do you have a donation button? This is the second time you've given me great advice and I'd like to buy you a coffee. 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-28348) Cannot use number from version number plugin as pipeline version
Title: Message Title Enrico Mills commented on JENKINS-28348 Re: Cannot use number from version number plugin as pipeline version This also applies to environment variables set by the EnvInject 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] [docker-commons-plugin] (JENKINS-28702) Clean up registry credentials
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-28702 Clean up registry credentials Issue Type: Bug Assignee: Unassigned Components: docker-commons-plugin Created: 02/Jun/15 8:50 PM Labels: security Priority: Major Reporter: Jesse Glick Currently DockerRegistryToken makes no attempt to log you out when KeyMaterial.close is called. This makes it inappropriate for environments in which access to the registry credentials must be tightly controlled. The problem is that ~/.dockercfg must be used to store the login globally for the user (typically, one slave agent), so if there are multiple executors on the slave, one log out while another is still using the login. If https://github.com/docker/docker/issues/10318 or similar is implemented, that would be ideal, so that the authentication between executors does not clash. Otherwise, it might be possible to use reference-counting. TBD if docker login/logout would preserve other fields, or if a separate file would be needed. There are potential locking issues there.
[JIRA] [github-plugin] (JENKINS-28701) Script runs in Script Console but not with Job DSL groovy
Title: Message Title
Daniel Spilker commented on JENKINS-28701
Re: Script runs in Script Console but not with Job DSL groovy
The Job DSL plugin can't access classes from other plugins.
But Groovy and the Jenkins API allow to avoid that by using reflection and dynamic access. In your case, use Jenkins.getExtensionList(String), e.g.
def credentials = Jenkins.instance.getExtensionList("com.cloudbees.jenkins.GitHubPushTrigger.DescriptorImpl")[0].getCredentials()
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] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier edited a comment on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication.Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works.If a service with the same name already exists, it will would display a message about it, but will would continue normally without overwriting it, since the case of resetting the services would be covered by the "Also delete bound services" checkbox. This way you can also make sure services are created if they don't exist, but without having to reset them if they don't.In case of a reset, this would also make sure the services are created after the app reset, but before the app re-creation.I'll keep looking into 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] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier edited a comment on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication.Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works.If a service with the same name already exists, it would display a message about it, but would continue normally without overwriting it, since the case of resetting the services would be covered by the "Also delete bound services" checkbox. This way you can also make sure services are created if they don't exist, but without having to reset them if they don't.In case of a complete reset, this would also make sure the services are created after the app reset, but before the app re-creation.I'll keep looking into 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] [github-plugin] (JENKINS-28701) Script runs in Script Console but not with Job DSL groovy
Title: Message Title Daniel Spilker resolved as Duplicate Duplicates JENKINS-27517. Jenkins / JENKINS-28701 Script runs in Script Console but not with Job DSL groovy Change By: Daniel Spilker Status: Open Resolved Resolution: Duplicate 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] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier edited a comment on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication.Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works. If a service with the same name already exists, it will display a message about it, but will continue normally without overwriting it, since the case of resetting the services would be covered by the "Also delete bound services" checkbox. This way you can also make sure services are created if they don't exist, but without having to reset them if they don't. In case of a reset, this would also make sure the services are created after the app reset, but before the app re-creation.I'll keep looking into 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] [job-dsl-plugin] (JENKINS-27721) Empty Elements different in Generated vs. Re-Generated projects
Title: Message Title Daniel Spilker resolved as Cannot Reproduce Jenkins / JENKINS-27721 Empty Elements different in Generated vs. Re-Generated projects Change By: Daniel Spilker Status: Open Resolved Resolution: Cannot Reproduce 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] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier edited a comment on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication.Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works. In case of a reset, this would also make sure the services are created after the app reset, but before the app re-creation. I'll keep looking into 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] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier commented on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication. Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works. I'll keep looking into 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] [github-plugin] (JENKINS-28701) Script runs in Script Console but not with Job DSL groovy
Title: Message Title
Sam Gleske created an issue
Jenkins / JENKINS-28701
Script runs in Script Console but not with Job DSL groovy
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
github-plugin, job-dsl-plugin
Created:
02/Jun/15 8:36 PM
Labels:
github-plugin
Priority:
Minor
Reporter:
Sam Gleske
The following script runs fine in the Script Console but not in a Job DSL script.
import jenkins.*
import jenkins.model.*
import hudson.*
import hudson.model.*
def credentials = Jenkins.instance.getExtensionList(com.cloudbees.jenkins.GitHubPushTrigger.DescriptorImpl.class)[0].getCredentials()
if(credentials.size() > 0) {
credentials.each {
if(it.apiUrl.length() > 0) {
println("apiUrl: " + it.apiUrl)
}
else {
println("apiUrl: https://api.github.com/")
}
println("username: " + it.username)
println("oauthAccessToken: " + it.oauthAccessToken)
}
}
I recall that the Job DSL plugin executes groovy scripts in the Jenkins runtime. I'm getting info out of the configured github plugin (specifically the automatically manage hooks section).
[JIRA] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title Kevin Phillips commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs Yes, the problem is related to submitting changes to view configurations. Was there some specific information you'd like me to provide that hasn't already been stated above? 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 Daniel Beck commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs Kevin Phillips Please be specific as to what you're seeing, and in which circumstances. Is this about submitting view configuration forms? 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-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title Daniel Beck commented on JENKINS-28698 Re: Update Jenkins to 1.616 results in a 1.615 version What happens when you restart Tomcat? 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-workflow-plugin] (JENKINS-28700) Extend demo with other plugins
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-28700 Extend demo with other plugins Issue Type: Task Assignee: Oleg Nenashev Components: docker-workflow-plugin Created: 02/Jun/15 8:09 PM Priority: Major Reporter: Jesse Glick The demo should include interoperation with docker-traceability and dockerhub-notification. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title jim jaeger reopened an issue Tomcat say it is redeployed. Jenkins / JENKINS-28698 Update Jenkins to 1.616 results in a 1.615 version Change By: jim jaeger Resolution: Cannot Reproduce 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] [core] (JENKINS-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title jim jaeger commented on JENKINS-28698 Re: Update Jenkins to 1.616 results in a 1.615 version The updates worked good before a long time and now it dies not work anymore. The only difference is the Jenkins war level 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 Kevin Phillips commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs I just noticed that this bug also affects the latest LTS edition as well - v1.596.3 at the current moment. I haven't compared the behavior with latest weekly builds, but assuming this defect has been successfully repaired on the master version it should probably be backported to the LTS branch as well. I added the lts-candidate label for reference as well. Not sure if that will make any difference seeing as how the issue has already been resolved but at least it's there. 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 Kevin Phillips updated an issue Jenkins / JENKINS-20327 “Form too large” errors submitting view configurations with many jobs Change By: Kevin Phillips Labels: 1.565.1-fixed jetty lts-candidate performance view 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-28425) UI: Build history overflows
Title: Message Title Daniel Beck commented on JENKINS-28425 Re: UI: Build history overflows Lars W Why did you reopen this issue? Is it not resolved? Note that if it caused a regression, that's a different issue. 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] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title windows refund commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins sure thing.. just want to let this version burn in for a bit. 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-step-plugin] (JENKINS-28646) Add support for removing volumes while removing a container
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28646 Re: Add support for removing volumes while removing a container Code changed in jenkins User: Niek Palm Path: src/main/java/org/jenkinsci/plugins/dockerbuildstep/DockerPostBuilder.java src/main/java/org/jenkinsci/plugins/dockerbuildstep/cmd/RemoveAllCommand.java src/main/java/org/jenkinsci/plugins/dockerbuildstep/cmd/RemoveCommand.java src/main/resources/org/jenkinsci/plugins/dockerbuildstep/DockerPostBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/dockerbuildstep/cmd/RemoveAllCommand/config-detail.jelly src/main/resources/org/jenkinsci/plugins/dockerbuildstep/cmd/RemoveCommand/config-detail.jelly http://jenkins-ci.org/commit/docker-build-step-plugin/fae73c34bc76116ef64d073427df21275e8e3025 Log: JENKINS-28646 - Add support for removing volumes while removing a container Add checkbox to remove volumes, default is unchecked Build steps: RemoveContainer and RemoveAllContainers Post build steps: Stop and remove container. 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] [job-dsl-plugin] (JENKINS-28695) job-dsl allocatePorts does not work
Title: Message Title Daniel Spilker commented on JENKINS-28695 Re: job-dsl allocatePorts does not work See https://github.com/jenkinsci/job-dsl-plugin/wiki/Frequently-Asked-Questions#why-isnt-my-generated-job-like-i-was-expecting-there-was-no-error-when-the-seed-job-ran. Have you tried to restart Jenkins? 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] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier commented on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Ah, you're right, I forgot that's not in the manifest anymore. In that case it seems your idea of making another post build action is probably the best, but that means in the case where you want to replace both the app and the services, service deletion and recreation will happen before the app deletion and recreation. This might be ok, but I will have to make sure nothing's wrong with that. 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] [parameterized-trigger-plugin] (JENKINS-28699) Password type parameterized fields get bogus auto-population of default value despite empty field on job save
Title: Message Title Gordon Pettey created an issue Jenkins / JENKINS-28699 Password type parameterized fields get bogus auto-population of default value despite empty field on job save Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 02/Jun/15 6:27 PM Environment: Jenkins 1.607 Priority: Major Reporter: Gordon Pettey Password type parameters on parameterized jobs are being automatically populated despite having the default value set blank. If I have not filled the field, then it should NOT be filling itself. This occurs in any browser regardless of auto-complete settings, and the value is some hash I've definitely never put in a field, so I am quite sure it isn't the browsers' fault. Add Comment
[JIRA] [core] (JENKINS-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title Daniel Beck resolved as Cannot Reproduce The provided URL points to Jenkins 1.616. Please make sure there's nothing wrong with Tomcat redeploy or other parts of your environment. Would be more of a Tomcat issue than Jenkins issue in any case. Jenkins / JENKINS-28698 Update Jenkins to 1.616 results in a 1.615 version Change By: Daniel Beck Status: Open Resolved Resolution: Cannot Reproduce 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] [klaros-testmanagement-plugin] (JENKINS-28659) Add proper migration of test result path settings for existing projects
Title: Message Title stolp resolved as Fixed Jenkins / JENKINS-28659 Add proper migration of test result path settings for existing projects Change By: stolp 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] [build-pipeline-plugin] (JENKINS-21422) Jenkins crashing due to out of memory when rebuilding jobs
Title: Message Title Daniel Beck commented on JENKINS-21422 Re: Jenkins crashing due to out of memory when rebuilding jobs My guess would be the excessive serialization in Build Pipeline's build cause. The affected job's build.xml files would be interesting. 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-traceability-plugin] (JENKINS-28643) timestamps in the UI are not correct
Title: Message Title Oleg Nenashev commented on JENKINS-28643 Re: timestamps in the UI are not correct confirmed on the test client 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-traceability-plugin] (JENKINS-28643) timestamps in the UI are not correct
Title: Message Title Oleg Nenashev started work on JENKINS-28643 Change By: Oleg Nenashev 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] [delivery-pipeline-plugin] (JENKINS-28582) MethodNotAllowed error when start new build
Title: Message Title Patrik Boström resolved as Fixed Will come in 0.9.3 release Jenkins / JENKINS-28582 MethodNotAllowed error when start new build Change By: Patrik Boström 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] [build-pipeline-plugin] (JENKINS-21422) Jenkins crashing due to out of memory when rebuilding jobs
Title: Message Title Clint Parham commented on JENKINS-21422 Re: Jenkins crashing due to out of memory when rebuilding jobs I'm also running into "OutOfMemoryError: Java heap space" errors using the Build Pipeline View. Jenkins was fine running our jobs using ~130MB of heap. But since adding the Build Pipeline plugin we see heap memory spike to over 1.5GB when opening a single job page belonging to a pipeline. As soon as we disabled the Pipeline plugin, we could open the same job page and saw no increase in heap usage. Running Jenkins 1.602 and Build Pipline 1.4.7 Partial stacktrace: Jun 2, 2015 1:39:25 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Error while serving http://192.168.2.85:8081/job/Pipeline_MAT_Build/test/trendMap java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) ... at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.OutOfMemoryError: Java heap space 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] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title kutzi commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins Can you confirm, that it was really the IRC plugin which lead to Jenkins shutdown? 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] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title kutzi commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins You can configure different notification styles (normal, short, ...) as far as I remember. On top of that there is currently no possibility to configure 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] [valgrind-plugin] (JENKINS-28670) Cannot set environment variables
Title: Message Title Johannes Ohlemacher commented on JENKINS-28670 Re: Cannot set environment variables Hi Stephen, have you tried the EnvInject plugin? https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin Does that solve your 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] [core] (JENKINS-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title jim jaeger updated an issue Jenkins / JENKINS-28698 Update Jenkins to 1.616 results in a 1.615 version Change By: jim jaeger I donwloaded the jenkins.war from the provided link in the jenkins UI http://updates.jenkins-ci.org/download/war/1.616/jenkins.war and redeploy the WAR via the auto redeploy from tomcat7. After it I restarted it too. But the version is still v. 1.615 and the information about new version is still available. 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-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title jim jaeger updated an issue Jenkins / JENKINS-28698 Update Jenkins to 1.616 results in a 1.615 version Change By: jim jaeger I donwloaded the jenkins.war from the provided link in the jenkins UI http://updates.jenkins-ci.org/download/war/1.616/jenkins.war and redeploy the WAR via the auto redeploy from tomcat7. After it I restarted it too. But the version is still v. 1.615 and the information about new version available. 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-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title jim jaeger created an issue Jenkins / JENKINS-28698 Update Jenkins to 1.616 results in a 1.615 version Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Jun/15 4:32 PM Environment: 1.616/1.615, Linux 64Bit, Tomcat 7 Priority: Minor Reporter: jim jaeger I donwloaded the jenkins.war from the provided link in the jenkins UI http://updates.jenkins-ci.org/download/war/1.616/jenkins.war and redeploy the WAR via the auto redeploy from tomcat7. After it I restarted it too. But the v. 1.615 and the information about new version available. Add Comment
[JIRA] [rundeck-plugin] (JENKINS-28697) Aborted job is marked as SUCCESS if "Wait for Rundeck" is used
Title: Message Title
Marcin Zajączkowski created an issue
Jenkins / JENKINS-28697
Aborted job is marked as SUCCESS if "Wait for Rundeck" is used
Issue Type:
Bug
Assignee:
Vincent Behar
Components:
rundeck-plugin
Created:
02/Jun/15 4:24 PM
Environment:
Rundeck plugin 3.4
Priority:
Major
Reporter:
Marcin Zajączkowski
Looking at the code (RundeckNotifier) if "sleep(5000)" is interupted ("Oops, interrupted !" is in a log) the while loop is finished and current Rundeck job execution status is RUNNING. It causes that switch..case hits "default" and the whole job is marked as SUCESS.
Add Comment
[JIRA] [email-ext-plugin] (JENKINS-28680) Email Extension Plugin throwing a NullPointerException at startup
Title: Message Title jim jaeger commented on JENKINS-28680 Re: Email Extension Plugin throwing a NullPointerException at startup I used the Advanced tab to install the provided version and restarted Now I get the following error: WARNING: Failed to instantiate Key[type=hudson.plugins.emailext.ExtendedEmailPublisherDescriptor, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Tried proxying hudson.plugins.emailext.ExtendedEmailPublisherDescriptor to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:428) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:390) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:381) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:386) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1197) at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.readResolve(ExtendedEmailPublisherDescriptor.java:458) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:66) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:229) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at hudson.XmlFile.unmarshal(XmlFile.java:163) at hudson.model.Descriptor.load(Descriptor.java:783) at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.(ExtendedEmailPublisherDescriptor.java:344) at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor$$FastClassByGuice$$5dfa54d0.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88) at com.google.inject.internal.ConstructorBindingImpl$Factory.ge
[JIRA] [git-plugin] (JENKINS-27625) Git submodules, option for reseting local changes on submodules
Title: Message Title Tomasz Śniatowski commented on JENKINS-27625 Re: Git submodules, option for reseting local changes on submodules This problem is still present in current git plugin master (06415b9b9d3dd46d11a620b78ff56b19847c141a) 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] [envinject-plugin] (JENKINS-28696) [EnvInject] - Loading node environment variables. FATAL: org.jenkinsci.plugins.envinject.EnvInjectPluginAction.overrideAll
Title: Message Title Sushma Kaniganti created an issue Jenkins / JENKINS-28696 [EnvInject] - Loading node environment variables. FATAL: org.jenkinsci.plugins.envinject.EnvInjectPluginAction.overrideAll Issue Type: Bug Assignee: Gregory Boissinot Components: envinject-plugin Created: 02/Jun/15 3:48 PM Environment: Jenkins ver. 1.609.1-SNAPSHOT (rc-05/20/2015 14:52 GMT-kohsuke) Master is Windows Unix Slave Priority: Major Reporter: Sushma Kaniganti Trying to run Maven goal on a Unix slave and it fails. Please help Started by user anonymous [EnvInject] - Loading node environment variables. FATAL: org.jenkinsci.plugins.envinject.EnvInjectPluginAction.overrideAll(Ljava/util/Set;Ljava/util/Map;)V java.lang.NoSuchMethodError: org.jenkinsci.plugins.envinject.EnvInjectPluginAction.overrideAll(Ljava/util/Set;Ljava/util/Map;)V at org.jenkinsci.plugins.envinject.service.EnvInjectActionSetter.addEnvVarsToEnvInjectBuildAction(EnvInjectActionSetter.java:41) at org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:84) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:574) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.ex
[JIRA] [email-ext-plugin] (JENKINS-28680) Email Extension Plugin throwing a NullPointerException at startup
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-28680 Email Extension Plugin throwing a NullPointerException at startup Actually, it looks like my full fix didn't get merged in from my work. Attached is a version of the plugin with the full fix. If you are willing, please give it a shot. Change By: Alex Earl Attachment: email-ext.hpi 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] [elastic-axis-plugin] (JENKINS-27420) Allow for "any node matching label", not just "all nodes matching label"
Title: Message Title Jo Shields commented on JENKINS-27420 Re: Allow for "any node matching label", not just "all nodes matching label" https://github.com/jenkinsci/elastic-axis-plugin/pull/4 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-9052) Git plugin needs a better error diagnosis when failing to check out
Title: Message Title Tomasz Śniatowski commented on JENKINS-9052 Re: Git plugin needs a better error diagnosis when failing to check out It is better now. I managed to do a quick test with a broken clone uri. Before: > git -c core.askpass=true fetch --tags --progress localhost.host:/home/BROKEN +refs/heads/*:refs/remotes/origin/* ERROR: Error fetching remote repo 'origin' ERROR: Error fetching remote repo 'origin' On master with the above change there's an ugly backtrace, but at the errror message is there: ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from localhost:/home/BROKEN at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:737) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:984) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1015) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress localhost:/home/BROKEN +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: '/home/BROKEN' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:325) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to test-2(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1360) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:753) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
[JIRA] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title windows refund edited a comment on JENKINS-28626 Re: IRC notification results in need to restart Jenkins Thanks! The newer plugin seems to be working nicely. Is Sorry to drift off topic, but is there any way to customize the summary message? For example, I'd likeProject This is a test #22: SUCCESS in 2.6 sec: http://jenkins.example.com:8080/job/This%20is%a% 20/ test/22/To simply be:Project This is a test #22: SUCCESS in 2.6 sec 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] [nunit-plugin] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title Flaviu S commented on JENKINS-27906 Re: Fail to read NUnit3 output xml I also stumbled across the same issue, seems like the test results xml structure has changed a lot in nunit3. I will try to provide a sample from both versions if that helps. 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] [deploy-plugin] (JENKINS-19256) [Deploy-Plugin] Support JBoss 6.x and 7.x
Title: Message Title Dhiren p commented on JENKINS-19256 Re: [Deploy-Plugin] Support JBoss 6.x and 7.x I am using jenkins 1.586 and deploy plugin 1.10 to deploy to jboss 6.1.1GA. Observing same issue with jboss 6 version as well. org.codehaus.cargo.container.ContainerException: Failed to create deployer with implementation class org.codehaus.cargo.container.jboss.JBoss51xRemoteDeployer for the para meters (container [id = [jboss6x]], deployer type [remote]). at org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementation(AbstractGenericHintFactory.java:154) at org.codehaus.cargo.generic.spi.AbstractIntrospectionGenericHintFactory.createImplementation(AbstractIntrospectionGenericHintFactory.java:93) at org.codehaus.cargo.generic.deployer.DefaultDeployerFactory.createDeployer(DefaultDeployerFactory.java:141) at org.codehaus.cargo.generic.deployer.DefaultDeployerFactory.createDeployer(DefaultDeployerFactory.java:161) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:61) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103) at hudson.FilePath.act(FilePath.java:919) at hudson.FilePath.act(FilePath.java:897) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:534) at org.codehaus.cargo.generic.deployer.DefaultDeployerFactory.createInstance(DefaultDeployerFactory.java:220) at org.codehaus.cargo.generic.deployer.DefaultDeployerFactory.createInstance(DefaultDeployerFactory.java:43) at org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementation(AbstractGenericHintFactory.java:150) ... 19 more Caused by: org.codehaus.cargo.util.CargoException: Cannot locate the JBoss connector classes! Make sure the required JBoss JARs (or Maven dependencies) are in CARGO's clas spath. More information on: http://cargo.codehaus.org/JBoss+Remote+Deployer at org.codehaus.cargo.container.jboss.JBoss5xRemoteDeployer.(JBoss5xRemoteDeployer.java:161) at org.codehaus.cargo.container.jboss.JBoss51xRemoteDeployer.(JBoss51xRemoteDeployer.java:41) ... 26 more Caused by: java.lang.ClassNotFoundException: org.jnp.interfaces.Nam
[JIRA] [ssh-agent-plugin] (JENKINS-27555) ssh-agent plugin leaking file descriptors leaving behind jenkinsXXXXXX.jnr socket files
Title: Message Title Yoann Dubreuil resolved as Fixed Jenkins / JENKINS-27555 ssh-agent plugin leaking file descriptors leaving behind jenkinsXX.jnr socket files Change By: Yoann Dubreuil 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] [ssh-agent-plugin] (JENKINS-27555) ssh-agent plugin leaking file descriptors leaving behind jenkinsXXXXXX.jnr socket files
Title: Message Title Yoann Dubreuil assigned an issue to Yoann Dubreuil Jenkins / JENKINS-27555 ssh-agent plugin leaking file descriptors leaving behind jenkinsXX.jnr socket files Change By: Yoann Dubreuil Assignee: Yoann Dubreuil 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-28425) UI: Build history overflows
Title: Message Title
Thomas Suckow commented on JENKINS-28425
Re: UI: Build history overflows
I missed the effect it had on the ball link. This is probably also why the console link broke the last time. These two selectors never should have been grouped.
A better fix would be:
.build-row-cell .pane.build-name .display-name {
margin-left: 20px;
}
.build-row-cell .indent-multiline {
padding-left: 20px !important; /* Sync changes with func expandControlsTo50Percent in hudson-behavior.js */
}
I don't have time to make a PR at the moment. If someone could do that it would be appreciated.
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] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title windows refund edited a comment on JENKINS-28626 Re: IRC notification results in need to restart Jenkins Thanks! The newer plugin seems to be working nicely. Is there any way to customize the summary message? For example, I'd like Project This is a test #22 : SUCCESS in 2.6 sec: http://jenkins.example.com:8080/job/This%20is%a%test/22/To simply be:Project This is a test #22: SUCCESS in 2.6 sec 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] [elastic-axis-plugin] (JENKINS-28694) "node label" tooltip fails to parse comma-separated list
Title: Message Title Jo Shields commented on JENKINS-28694 Re: "node label" tooltip fails to parse comma-separated list https://github.com/jenkinsci/elastic-axis-plugin/pull/3 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] [job-dsl-plugin] (JENKINS-28695) job-dsl allocatePorts does not work
Title: Message Title
Andreas Holzner created an issue
Jenkins / JENKINS-28695
job-dsl allocatePorts does not work
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin, port-allocator-plugin
Created:
02/Jun/15 2:44 PM
Environment:
Jenkins 1.596.3 LTS, job-dsl-plugin 1.34, port-allocator-plugin 1.8
Priority:
Minor
Reporter:
Andreas Holzner
I fail to create a job with an unique TCP port allocated via job-dsl. The following DSL
freeStyleJob('Test Port Allocation') {
wrappers {
allocatePorts 'WEBAPP_HOST_PORT'
}
steps {
shell 'env'
}
}
generates a Job but the TCP port is missing in the web gui configuration page. When running the generated job no port is allocated.
The generated config.xml, however, does contain a buildWrappers section about the port:
WEBAPP_HOST_PORT
[JIRA] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title windows refund commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins Thanks! The newer plugin seems to be working nicely. Is there any way to customize the summary message? For example, I'd like : http://jenkins.example.com:8080/job/This%20is%a%test/22/ To simply be: Project This is a test #22: SUCCESS in 2.6 sec 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] [elastic-axis-plugin] (JENKINS-28694) "node label" tooltip fails to parse comma-separated list
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-28694 "node label" tooltip fails to parse comma-separated list Issue Type: Bug Assignee: Unassigned Components: elastic-axis-plugin Created: 02/Jun/15 2:42 PM Priority: Minor Reporter: Jo Shields The help for the "node label" field states as its example: "label_1,label_2" This example will cause the following tooltip: "There’s no slave/cloud that matches this assignment. Did you mean ‘label_1’ instead of ‘label_1,label_2’?" I believe this is caused by a bug on https://github.com/jenkinsci/elastic-axis-plugin/blob/master/src/main/java/org/jenkinsci/plugins/elasticaxisplugin/ElasticAxis.java#L104 - the form validation is tokenized on " " not "," Add Comment
[JIRA] [ssh-agent-plugin] (JENKINS-27555) ssh-agent plugin leaking file descriptors leaving behind jenkinsXXXXXX.jnr socket files
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27555 Re: ssh-agent plugin leaking file descriptors leaving behind jenkinsXX.jnr socket files Code changed in jenkins User: Yoann Dubreuil Path: src/main/java/com/cloudbees/jenkins/plugins/sshagent/jna/AgentServer.java http://jenkins-ci.org/commit/ssh-agent-plugin/166ca5a34d0a16b2d826dff0215225edbd3f623f Log: JENKINS-27555: Fix selector loop exit condition 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] [ssh-agent-plugin] (JENKINS-27555) ssh-agent plugin leaking file descriptors leaving behind jenkinsXXXXXX.jnr socket files
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27555 Re: ssh-agent plugin leaking file descriptors leaving behind jenkinsXX.jnr socket files Code changed in jenkins User: Yoann Dubreuil Path: src/main/java/com/cloudbees/jenkins/plugins/sshagent/jna/AgentServer.java http://jenkins-ci.org/commit/ssh-agent-plugin/37c4469c144b705e7e5330c0d16f3bce5dfc11ce Log: JENKINS-27555: Re-implements JNA agent with non-blocking code Re-implements JNA agent with a non blocking socket acceptor to fix socket leak caused by blocking on accept() native call. 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] [ssh-agent-plugin] (JENKINS-27555) ssh-agent plugin leaking file descriptors leaving behind jenkinsXXXXXX.jnr socket files
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27555 Re: ssh-agent plugin leaking file descriptors leaving behind jenkinsXX.jnr socket files Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/jenkins/plugins/sshagent/jna/AgentServer.java http://jenkins-ci.org/commit/ssh-agent-plugin/23afe23d01ded11693a18249104a88e1f3d349a5 Log: Merge pull request #3 from ydubreuil/fix-socket-leak JENKINS-27555: Re-implements JNA agent with non-blocking code Compare: https://github.com/jenkinsci/ssh-agent-plugin/compare/f0dc141cc6d0...23afe23d01de 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-traceability-plugin] (JENKINS-28693) docker-java dependency should be shaded
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28693 docker-java dependency should be shaded Issue Type: Bug Assignee: Oleg Nenashev Components: docker-traceability-plugin Created: 02/Jun/15 2:27 PM Priority: Major Reporter: Oleg Nenashev Reasons: docker-java does not guarantee the backward compatibility across versions (there're binary compatibility violations in the latest releases) sharing of incompatible lib as a plugin is not safe, so we want to setup the shading of the entire docker-java lib Add Comment
[JIRA] [performance-plugin] (JENKINS-28692) Git repository is not tagged with 1.13 release
Title: Message Title St. John Johnson updated an issue Jenkins / JENKINS-28692 Git repository is not tagged with 1.13 release Change By: St. John Johnson Howdy! When building from source, I noticed that the latest release on the Wiki is 1.13, but your Git repository is only tagged as high as 1.12 : https://git.corp.yahoo.com/jenkinsci/performance-plugin/tags 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] [performance-plugin] (JENKINS-28692) Git repository is not tagged with 1.13 release
Title: Message Title St. John Johnson updated an issue Jenkins / JENKINS-28692 Git repository is not tagged with 1.13 release Change By: St. John Johnson URL: https:// git github . corp.yahoo. com/jenkinsci/performance-plugin/tags 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] [performance-plugin] (JENKINS-28692) Git repository is not tagged with 1.13 release
Title: Message Title St. John Johnson created an issue Jenkins / JENKINS-28692 Git repository is not tagged with 1.13 release Issue Type: Bug Assignee: Manuel Carrasco Components: performance-plugin Created: 02/Jun/15 2:09 PM Priority: Trivial Reporter: St. John Johnson Howdy! I noticed that the latest release is 1.13, but your Git repository is only tagged as high as 1.12: https://git.corp.yahoo.com/jenkinsci/performance-plugin/tags Add Comment
[JIRA] [performance-plugin] (JENKINS-28692) Git repository is not tagged with 1.13 release
Title: Message Title St. John Johnson updated an issue Jenkins / JENKINS-28692 Git repository is not tagged with 1.13 release Change By: St. John Johnson Howdy! When building from source, I noticed that the latest release on the Wiki is 1.13, but your Git repository is only tagged as high as 1.12: https://git.corp.yahoo.com/jenkinsci/performance-plugin/tags 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-28691) HP Automation Tools reports incorrect test results
Title: Message Title Tyler Hoffman created an issue Jenkins / JENKINS-28691 HP Automation Tools reports incorrect test results Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 02/Jun/15 1:56 PM Environment: Jenkins 1.615, HP ALM 11.00, Windows 7 Priority: Major Reporter: Tyler Hoffman When viewing test results in Jenkins, the standard output shows a series of steps that appear to be from a previous run. Example output from Jenkins: Test: [1]sampleTest, Id: 10, Execution status: Passed, Message: Test run passed. Step: Start Test Start Test secondTest Step: Start Global Iteration Start Global Iteration 1 Step: Start Action Start Action Action1 Step: Fail, Status: Failed ... These were the results form my first run, but subsequent runs have succeeded according to ALM. The standard output does show the current run id.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title Dave Hunt commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked We are seeing this too, but I'd like to avoid trying an unreleased plugin on our production Jenkins instance. We do have a staging instance that until today did not use the IRC plugin. I have it running now and if I manage to replicate the issue I'll try the unreleased plugin to see if that resolves 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] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Arnt Witteveen commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" Meanwhile, we have found another cause of these disconnects, which may help in reproducing it (if you happen to have this setup available) : this happens when the slave is on a VMWare ESXi virtual machine, and you have multiple hosts (physical machines running VMWare ESX) available, and you have set up VMotion with DRS: at the moment the current slave VM host gets overloaded (e.g. because it starts a build!) the load is rebalanced over the hosts, and the slave VM may move to another host. This movement should be transparent but seems to cause this issue (I'm not sure why, it might be a timeout, it might be the fact that the physical network card that receives the traffic changes, or something else still). 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-storage-plugin] (JENKINS-23670) Please add option to remove prefix from local path when performing Classic Upload
Title: Message Title Pedro Ribeiro commented on JENKINS-23670 Re: Please add option to remove prefix from local path when performing Classic Upload Steven Shipton, do you know what is the status of this issue? I am bumping into the same issue and would be very interested in seeing this 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] [walldisplay-plugin] (JENKINS-26036) Wall Display folder support
Title: Message Title Andy Pemberton commented on JENKINS-26036 Re: Wall Display folder support Thanks for merging... any plans to cut a release with this fix? 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.
