[JIRA] (JENKINS-16568) Matrix job with 3 axis failed to load
Michael Wynne edited a comment on JENKINS-16568 Matrix job with 3 axis failed to load We recently setup a Jenkins server for the first time and just after getting everything configured this bug hit us. It is affecting all our matrix build jobs (each with 2 or 3 axis). On Windows Server 2008 R2. This basically renders Jenkins useless for us atm unfortunately. Any fixes or workarounds would be appreciated. Update: I have found that if I repeatedly "Reload Configuration from Disk" I will eventually end up with all jobs loaded. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds with parameters should be listed as downstream builds
Benjamin Kemper created JENKINS-16659 TriggerBuilder builds with parameters should be listed as downstream builds Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 06/Feb/13 9:25 AM Description: This is similar to issue #11082, issue #9263, issue #5184. The only difference is how the "Projects to build" value is set. In my case I build an environment variable "$TO_TRIGGER" dynamically and simply put it in the text box, "parameterized trigger" does the job of expanding it to the job names well. The only problem is that although the projects are triggered and in the console log it is listed as if they were triggered successfully, see log: Waiting for the completion of trigger1 trigger1 trigger1#2 completed. Result was SUCCESS Build step 'Trigger/call builds on other projects' changed build result to SUCCESS Finished: SUCCESS They still don't appear as downstream builds, nor do they upstream build appear as upstream build in the downstream build. Project: Jenkins Priority: Major Reporter: Benjamin Kemper This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds based on parameter value should be listed as downstream builds
Benjamin Kemper updated JENKINS-16659 TriggerBuilder builds based on parameter value should be listed as downstream builds Change By: Benjamin Kemper (06/Feb/13 9:28 AM) Summary: TriggerBuilder builds with parameters based on parameter value should be listed as downstream builds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16657) Wall Display JS Error: Cannot read property 'claimed' of null
SCM/JIRA link daemon commented on JENKINS-16657 Wall Display JS Error: Cannot read property 'claimed' of null Code changed in jenkins User: Yuri Buyanov Path: src/main/webapp/walldisplay.html http://jenkins-ci.org/commit/walldisplay-plugin/c41bf0cb063b69746596d419ce91463ead451433 Log: Fix for JENKINS-16657 Added null-check for `action` in `isBuildClaimed` This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16657) Wall Display JS Error: Cannot read property 'claimed' of null
SCM/JIRA link daemon commented on JENKINS-16657 Wall Display JS Error: Cannot read property 'claimed' of null Code changed in jenkins User: Pelle Pelster Path: src/main/webapp/walldisplay.html http://jenkins-ci.org/commit/walldisplay-plugin/26cb0dffecb233f9b87ab77552601f63ac74fe4d Log: Merge pull request #19 from digal/master Fix for JENKINS-16657 Compare: https://github.com/jenkinsci/walldisplay-plugin/compare/a2cfea5cafed...26cb0dffecb2 – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12619) "Failed to test the validity of the user name" on all security matrices since upgrade
Viktor Tarasov commented on JENKINS-12619 "Failed to test the validity of the user name" on all security matrices since upgrade It seems I have the same issue with jenkins-1.500 and ADplugin-1.30. Master on SLES-11. 50% of cli command fails due to the 'Failed to retrieve user information ...' error. The log from the client side: First attempt $ cat config.xml | java -jar jenkins-cli.jar -s Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:604) at hudson.cli.CLI._main(CLI.java:444) at hudson.cli.CLI.main(CLI.java:374) Second one $ cat config.xml | java -jar jenkins-cli.jar -s $ The logs from server: Feb 6, 2013 10:16:21 AM hudson.TcpSlaveAgentListener$ConnectionHandler run INFO: Accepted connection #33 from /172.28.16.3:33475 Feb 6, 2013 10:16:21 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser WARNING: Failed to retrieve user information for jenkins Throwable occurred: javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; Remaining name: 'DC=-sa,DC=local' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3093) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2999) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2806) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1838) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1761) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1778) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:406) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:388) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:370) at hudson.plugins.active_directory.LDAPSearchBuilder.search(LDAPSearchBuilder.java:52) at hudson.plugins.active_directory.LDAPSearchBuilder.searchOne(LDAPSearchBuilder.java:42) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:260) ... Feb 6, 2013 10:16:21 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser WARNING: Credential exception tying to authenticate against -sa.local domain Throwable occurred: org.acegisecurity.BadCredentialsException: Failed to retrieve user information for jenkins; nested exception is javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; Remaining name: 'DC=-sa,DC=local' at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:306) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:190) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:134) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:30) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadUserByUsername(ActiveDirectorySecurityRealm.java:582) at hudson.model.User.impersonate(User.java:255) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:44) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) Caused by: javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; Remaining name: 'DC=-sa,DC=local' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3093) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2999) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2806) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1838) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1761) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1778) at com.sun.jndi.toolkit.ct
[JIRA] (JENKINS-12619) "Failed to test the validity of the user name" on all security matrices since upgrade
Viktor Tarasov edited a comment on JENKINS-12619 "Failed to test the validity of the user name" on all security matrices since upgrade It seems I have the same issue with jenkins-1.500 and ADplugin-1.30. Master on SLES-11. 50% of cli command fails due to the 'Failed to retrieve user information ...' error. The log from the client side: First attempt $ cat config.xml | java -jar jenkins-cli.jar -s update-job Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:604) at hudson.cli.CLI._main(CLI.java:444) at hudson.cli.CLI.main(CLI.java:374) Second one $ cat config.xml | java -jar jenkins-cli.jar -s update-job $ The logs from server: Feb 6, 2013 10:16:21 AM hudson.TcpSlaveAgentListener$ConnectionHandler run INFO: Accepted connection #33 from /172.28.16.3:33475 Feb 6, 2013 10:16:21 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser WARNING: Failed to retrieve user information for jenkins Throwable occurred: javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; Remaining name: 'DC=-sa,DC=local' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3093) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2999) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2806) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1838) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1761) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1778) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:406) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:388) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:370) at hudson.plugins.active_directory.LDAPSearchBuilder.search(LDAPSearchBuilder.java:52) at hudson.plugins.active_directory.LDAPSearchBuilder.searchOne(LDAPSearchBuilder.java:42) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:260) ... Feb 6, 2013 10:16:21 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser WARNING: Credential exception tying to authenticate against -sa.local domain Throwable occurred: org.acegisecurity.BadCredentialsException: Failed to retrieve user information for jenkins; nested exception is javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; Remaining name: 'DC=-sa,DC=local' at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:306) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:190) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:134) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:30) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadUserByUsername(ActiveDirectorySecurityRealm.java:582) at hudson.model.User.impersonate(User.java:255) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:44) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) Caused by: javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; Remaining name: 'DC=-sa,DC=local' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3093) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2999) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2806) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1838) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1761) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1778)
[JIRA] (JENKINS-16656) slave agent fails to start: slave-agent.jnlp uses http while jenkins url is https
kutzi resolved JENKINS-16656 as Duplicate slave agent fails to start: slave-agent.jnlp uses http while jenkins url is https Change By: kutzi (06/Feb/13 9:33 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13021) Base Clearcase: Tracking changes on labels
Aki Hirvonen commented on JENKINS-13021 Base Clearcase: Tracking changes on labels How about if the labels were parsed from config spec? For us it would work perfectly, if all the labels in config spec were taken into account. That is, applying or removing any label included in config spec would trigger a build. In this case, listing the labels separately in job configuration would be redundant. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16660) Environment variable replacement/resolving
Sven Appenrodt created JENKINS-16660 Environment variable replacement/resolving Issue Type: Bug Assignee: Unassigned Components: core Created: 06/Feb/13 10:17 AM Description: The function hudson.Util.replaceMacro(String, ...) does not resolve properties with '.' E.g. many java properties or build parameters do/can have a dot in their names which cannot be expanded by this method which seems to be used by some plugins. Please add the dot to hudson.Util.VARIABLE pattern. Thx Environment: Jenkins ver. 1.500 Project: Jenkins Priority: Trivial Reporter: Sven Appenrodt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16637) problems exposing P4CLIENT and P4PASSWD to env
Mikko Tapaninen commented on JENKINS-16637 problems exposing P4CLIENT and P4PASSWD to env Both master and slave are Windows server 2008 (HPC edition) machines with jdk1.7.0_10. I also tested with Windows 7 + jdk1.6.0_29 combination, same results. We used "Windows batch" build step which simply echoed P4CLIENT. It's rather simple to reproduce. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16661) Rebuild plugin crashes when used in conjuction with Random String Parameter Plugin
Sven Appenrodt created JENKINS-16661 Rebuild plugin crashes when used in conjuction with Random String Parameter Plugin Issue Type: Bug Affects Versions: current Assignee: ragesh_nair Components: parameters, rebuild Created: 06/Feb/13 10:48 AM Description: Running a parameterized build containing a RandomStringParameter and hitting rebuild-action it fails with an exception: Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: file:/D:/Jenkins/plugins/rebuild/WEB-INF/classes/com/sonyericsson/rebuild/RebuildAction/parameterized.jelly:55:75: No page found 'RandomStringParameterValue.jelly' for class com.sonyericsson.rebuild.RebuildAction Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: file:/D:/Jenkins/plugins/rebuild/WEB-INF/classes/com/sonyericsson/rebuild/RebuildAction/parameterized.jelly:55:75: No page found 'RandomStringParameterValue.jelly' for class com.sonyericsson.rebuild.RebuildAction at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) ... Environment: Jenkins ver. 1.499 Project: Jenkins Priority: Major Reporter: Sven Appenrodt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16662) Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds
Geoff Cummings created JENKINS-16662 Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds Issue Type: Improvement Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 06/Feb/13 11:22 AM Description: I would like to be able to perform conditional logic after triggering a blocking build without changing the build status. Currenty the TRIGGERED_BUILD_NUMBER is exported as an environment variable. It would also be useful to export the TRIGGERED_BUILD_RESULT which could be used in later build steps. Project: Jenkins Priority: Major Reporter: Geoff Cummings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16662) Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds
Geoff Cummings commented on JENKINS-16662 Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds I have created the following pull request for this: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/34 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16663) Consider injected env variables in promotion
Eyal Zfira created JENKINS-16663 Consider injected env variables in promotion Issue Type: Improvement Assignee: Unassigned Components: promoted-builds Created: 06/Feb/13 11:42 AM Description: When using the EnvInject plugin, consider the properties/files/script configured in the job during the promotion process. Environment: Windows Project: Jenkins Priority: Major Reporter: Eyal Zfira This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds based on parameter value should be listed as downstream builds
cjo9900 updated JENKINS-16659 TriggerBuilder builds based on parameter value should be listed as downstream builds Change By: cjo9900 (06/Feb/13 11:50 AM) Description: This is similar to issue # JENKINS- 11082, issue # JENKINS- 9263, issue # JENKINS- 5184.The only difference is how the "Projects to build" value is set.In my case I build an environment variable "$TO_TRIGGER" dynamically and simply put it in the text box, "parameterized trigger" does the job of expanding it to the job names well. The only problem is that although the projects are triggered and in the console log it is listed as if they were triggered successfully, see log:Waiting for the completion of trigger1trigger1 trigger1#2 completed. Result was SUCCESSBuild step 'Trigger/call builds on other projects' changed build result to SUCCESSFinished: SUCCESSThey still don't appear as downstream builds, nor do they upstream build appear as upstream build in the downstream build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16552) Throttle plugin does not throttle sub jobs in matrix project
Fredrik Simonsson closed JENKINS-16552 as Duplicate Throttle plugin does not throttle sub jobs in matrix project Close - duplicate Change By: Fredrik Simonsson (06/Feb/13 11:56 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16664) No GUI for adding multiple update centers
Alexander Lindström created JENKINS-16664 No GUI for adding multiple update centers Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: update-center Created: 06/Feb/13 12:29 PM Description: There is possible to add multiple updates centers but there are no way in the GUI to do so. There should be either an add button to add another field of text or there should be a type of separator between update centers (ei ";"). Added in "1.333 (2009/11/09)" according to changelog. Environment: WIN7 Project: Jenkins Priority: Major Reporter: Alexander Lindström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16601) NPE when loading a Matrix Project
kutzi resolved JENKINS-16601 as Duplicate NPE when loading a Matrix Project Probably same as JENKINS-16499 Change By: kutzi (06/Feb/13 12:55 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15578) hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
Fred G
commented on JENKINS-15578
hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
This problem is not limited to LDAP authentication.
I'm getting almost the same error, with "Jenkins's own user database":
hudson.security.AccessDeniedException2: anonymous is missing the {1} permission
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16648) changes-since-last-success plugin doesn't work
Travis Burtrum updated JENKINS-16648 changes-since-last-success plugin doesn't work Change By: Travis Burtrum (06/Feb/13 1:19 PM) Summary: changes-since-last-success plugin doesn't work This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3262) Unexpected error in launching a slave (UnsupportedCharsetException: MacRoman)
Fred G commented on JENKINS-3262 Unexpected error in launching a slave (UnsupportedCharsetException: MacRoman) I can confirm jkxyz's workaround. Specifiying "-Dfile.encoding=UTF-8" as JVM option in the node configuration made it work for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16638) child builds going missing from matrix jobs
Arne Nordmann commented on JENKINS-16638 child builds going missing from matrix jobs I can confirm this behavior. On our machine (Jenkins ver. 1.499) builds and artifacts of multi-configuration jobs vanish every once in a while. My impression is, that this happens foremost to newer jobs resp. newer configurations in multi-configuration jobs (e. g. if we add more build nodes to a job configuration). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12619) "Failed to test the validity of the user name" on all security matrices since upgrade
Adam Wu commented on JENKINS-12619 "Failed to test the validity of the user name" on all security matrices since upgrade have you set DN name & DN password? and Try to user logging to find more info: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12619) "Failed to test the validity of the user name" on all security matrices since upgrade
Adam Wu edited a comment on JENKINS-12619 "Failed to test the validity of the user name" on all security matrices since upgrade have you set DN name & DN password? (you should better to use an admin user & password) and Try to user logging to find more info: If you think you've configured everything correctly but still not being able to login (or any other problems), please enable Logging and configure logging level for "hudson.plugins.active_directory" to ALL. Attempt a login and then file a ticket with the log output. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16638) child builds going missing from matrix jobs
Chris Withers commented on JENKINS-16638 child builds going missing from matrix jobs Interesting... I think some nodes were added to and removed from our pool around the time this happened... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16644) When using Perforce Plugin, P4_CHANGELIST variable gets incorrect value
Dmitriy Pupov commented on JENKINS-16644 When using Perforce Plugin, P4_CHANGELIST variable gets incorrect value Hi we don't have similar string Using master perforce client: BuildMachine_WS_SDFC [workspace] $ /home/user/p4/p4 workspace -o BuildMachine_WS_SDFC Clear workspace includes .repository ... Wiping workspace... Wiped workspace. Clean complete, took 52 ms Last build changeset: 88344 [workspace] $ /home/user/p4/p4 changes -s submitted -m 1 //... [workspace] $ /home/user/p4/p4 -s changes -s submitted //BuildMachine_WS_SDFC/...@88345,@88371 [workspace] $ /home/user/p4/p4 describe -s 88358 [workspace] $ /home/user/p4/p4 -G where //... Jenkins ver. 1.492 P4 plugin 1.3.17 P4 client Rev. P4/LINUX26X86/2011.1/393975 (2011/12/16). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16054) Add ability to mute test(s) in the build
Vladimir Kravets commented on JENKINS-16054 Add ability to mute test(s) in the build Guys, any update about this improvement? Since after moving from TeamCity this feature is lack. =( This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15442) email-ext plugin does not save configuration on job
Alex Earl resolved JENKINS-15442 as Cannot Reproduce email-ext plugin does not save configuration on job Change By: Alex Earl (06/Feb/13 1:57 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16665) should not show +0 when nothing has changed
Tomek Kaczanowski created JENKINS-16665 should not show +0 when nothing has changed Issue Type: Improvement Assignee: nalin_makar Components: testng Created: 06/Feb/13 2:05 PM Description: it makes no sense to show the number of changed items when nothing has changed now: Total Tests: 110 (+0) Failed Tests: 0 (+0) Skipped Tests: 0 (+0) Failed Configurations: 0 (+0) Skipped Configurations: 0 (+0) should be Total Tests: 110 Failed Tests: 0 Skipped Tests: 0 Failed Configurations: 0 Skipped Configurations: 0 Project: Jenkins Priority: Minor Reporter: Tomek Kaczanowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13742) Field validation does not pass required query parameters when some fields are specified in a nested Describable
SCM/JIRA link daemon commented on JENKINS-13742 Field validation does not pass required query parameters when some fields are specified in a nested Describable Code changed in jenkins User: jmcnally Path: src/main/java/com/collabnet/ce/webservices/CTFProject.java src/main/java/com/collabnet/ce/webservices/CollabNetApp.java src/main/java/hudson/plugins/collabnet/ConnectionFactory.java src/main/java/hudson/plugins/collabnet/auth/CNAuthProjectProperty.java src/main/java/hudson/plugins/collabnet/browser/TeamForge.java src/main/java/hudson/plugins/collabnet/tracker/CNTracker.java src/main/java/hudson/plugins/collabnet/util/CNFormFieldValidator.java src/main/java/hudson/plugins/collabnet/util/ComboBoxUpdater.java http://jenkins-ci.org/commit/collabnet-plugin/70070f6d7d3745e2af30756f1152eca690e1f60f Log: Merge pull request #1 from jmcnally/master JENKINS-13742 Errors in field validations Compare: https://github.com/jenkinsci/collabnet-plugin/compare/d13d8d2554c3...70070f6d7d37 – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13742) Field validation does not pass required query parameters when some fields are specified in a nested Describable
SCM/JIRA link daemon commented on JENKINS-13742 Field validation does not pass required query parameters when some fields are specified in a nested Describable Code changed in jenkins User: John McNally Path: src/main/java/com/collabnet/ce/webservices/CTFProject.java src/main/java/com/collabnet/ce/webservices/CollabNetApp.java src/main/java/hudson/plugins/collabnet/ConnectionFactory.java src/main/java/hudson/plugins/collabnet/auth/CNAuthProjectProperty.java src/main/java/hudson/plugins/collabnet/browser/TeamForge.java src/main/java/hudson/plugins/collabnet/tracker/CNTracker.java src/main/java/hudson/plugins/collabnet/util/CNFormFieldValidator.java src/main/java/hudson/plugins/collabnet/util/ComboBoxUpdater.java http://jenkins-ci.org/commit/collabnet-plugin/028c3cf91ffa39a544f98cb287d9554beead76e1 Log: JENKINS-13742 Field validation does not pass required query parameters when some fields are specified in a nested Describable On branch master Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git checkout – ..." to discard changes in working directory) src/main/java/com/collabnet/ce/webservices/CTFProject.java (getOrCreateDocumentFolder, verifyPath): strip file separators from beginning and end of path src/main/java/com/collabnet/ce/webservices/CollabNetApp.java (fromStapler): renamed overrideAuth to connectionFactory, the former is more descriptive, but the checkbox takes the name of the composite field. Added RelativeParameter annotations to the other arguments. Also the password field may contain the encrypted form, so using Secret to transform into plaintext. src/main/java/hudson/plugins/collabnet/ConnectionFactory.java Add a fromStapler method so this can be used in validations that are internal to the composite field, such as the modified doCheckPassword method. src/main/java/hudson/plugins/collabnet/auth/CNAuthProjectProperty.java (doFillProjectItems): simplified by using getProjectList method. src/main/java/hudson/plugins/collabnet/browser/TeamForge.java (doFillProjectItems, doFillRepoItems): Added code to logoff the CTF session src/main/java/hudson/plugins/collabnet/tracker/CNTracker.java (doFillTrackerItems): Add a null check to avoid NPE, if auth data is not found src/main/java/hudson/plugins/collabnet/util/CNFormFieldValidator.java Several methods are modified to add null checks for the CollabNetAuth arg and to ensure the session is logged off. Prior to this change some methods did one and others did the other and some did neither. src/main/java/hudson/plugins/collabnet/util/ComboBoxUpdater.java (getUsers): Add null check on CollabNetApp arg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16644) When using Perforce Plugin, P4_CHANGELIST variable gets incorrect value
Rob Petti commented on JENKINS-16644 When using Perforce Plugin, P4_CHANGELIST variable gets incorrect value Can you update to the latest perforce plugin and try again please? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
Ireneusz Makowski commented on JENKINS-16499 NPE when new job by copy from existing one when it will be available in latest release? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16637) problems exposing P4CLIENT and P4PASSWD to env
Rob Petti commented on JENKINS-16637 problems exposing P4CLIENT and P4PASSWD to env What plugin and Jenkins versions are you using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Jason Stanley commented on JENKINS-15156 Builds disappear from build history after completion I have encountered this same problem. Jenkins 1.499 Server CentOS 6.2 Restarting Jenkins shows missing builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
Laurentius Purba created JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 Issue Type: Bug Assignee: kutzi Components: jabber Created: 06/Feb/13 2:59 PM Description: After upgrading to Jenkins 1.499, and upgrading Jabber plugin from version 1.22 to 1.25, and instant message plugin with 1.25, chat notification stops working. Environment: OS: FreeBSD 7.2 Jenkins: 1.499 Project: Jenkins Labels: jabber Priority: Major Reporter: Laurentius Purba This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16667) UI provide a way to trigger batch task on project dashboard
Paul Mendelson created JENKINS-16667 UI provide a way to trigger batch task on project dashboard Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: batch-task Created: 06/Feb/13 3:14 PM Description: Many times I make a small change to one of my batch tasks and want to execute that task. Unfortunately instead of selecting "tasks" link and "build now" button next to my task I inadvertently click the "build now" link on the left. I would like to have a mechanism on the left to trigger arbitrary tasks. I could imagine it as a popup when mousing over tasks (this would be best for projects with many tasks) or just a build link for each tasks (this would be best for projects with < 5 tasks). I don't know the average # of batch tasks jenkins-wide but in my case I rarely have more than 5. Project: Jenkins Priority: Minor Reporter: Paul Mendelson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16128) Broken Jenkins Configuration page when Github SQS plugin is installed
Andrei Pozolotin commented on JENKINS-16128 Broken Jenkins Configuration page when Github SQS plugin is installed thank you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
kutzi commented on JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 Any error messages in the logfile or somewhere else? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16668) regression in 1.500: NullPointerException when creating new job as a copy of existing one
Viktor Tarasov created JENKINS-16668 regression in 1.500: NullPointerException when creating new job as a copy of existing one Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins.log Components: core Created: 06/Feb/13 3:33 PM Description: With jenkins version 1.500, when creating a new job as a copy of existing job, the 'Status Code: 500' page is presented. After coming back from the 'Error' page to the 'newJob' page the field 'Copy existing Job':'Copy from' is empty. A new empty job is nevertheless created, it has the type of the parent job, but have no parent's configuration. There is no such behavior with jenkins version 1.499 . Logs are in attachment. Environment: Master on virtual SLES-11 Fix Versions: current Project: Jenkins Labels: jenkins exception job configuration Priority: Major Reporter: Viktor Tarasov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
Laurentius Purba commented on JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 Hi kutzi, Thanks for your response. I forgot to paste it, when I opened this ticket. hudson/model/ResultTrend java.lang.NoClassDefFoundError: hudson/model/ResultTrend at hudson.plugins.im.build_notify.SummaryOnlyBuildToChatNotifier.buildCompletionMessage(SummaryOnlyBuildToChatNotifier.java:39) at hudson.plugins.im.build_notify.DefaultBuildToChatNotifier.buildCompletionMessage(DefaultBuildToChatNotifier.java:50) at hudson.plugins.im.IMPublisher.notifyChatsOnBuildEnd(IMPublisher.java:577) at hudson.plugins.im.IMPublisher.notifyOnBuildEnd(IMPublisher.java:304) at hudson.plugins.im.IMPublisher.perform(IMPublisher.java:291) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:630) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:608) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:584) at hudson.model.Build$RunnerImpl.post2(Build.java:159) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:553) at hudson.model.Run.run(Run.java:1391) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145) Thanks! -Laurent This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
kutzi updated JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 Change By: kutzi (06/Feb/13 3:35 PM) Due Date: 20/Feb/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6673) Should be able to filter out disabled builds
Dave Abrahams commented on JENKINS-6673 Should be able to filter out disabled builds If this is fixed, where is the UI for the feature? I can't find it anywhere, and I'm updated to 1.500! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16668) regression in 1.500: NullPointerException when creating new job as a copy of existing one
kutzi resolved JENKINS-16668 as Duplicate regression in 1.500: NullPointerException when creating new job as a copy of existing one Duplicate. Please search for existing issues before creating duplicates Change By: kutzi (06/Feb/13 3:37 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13193) Error injecting: org.jfrog.build.extractor.maven.BuildInfoRecorderLifecycleParticipant
elifarley started work on JENKINS-13193 Error injecting: org.jfrog.build.extractor.maven.BuildInfoRecorderLifecycleParticipant Change By: elifarley (06/Feb/13 3:38 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13193) Error injecting: org.jfrog.build.extractor.maven.BuildInfoRecorderLifecycleParticipant
elifarley resolved JENKINS-13193 as Duplicate Error injecting: org.jfrog.build.extractor.maven.BuildInfoRecorderLifecycleParticipant This is a duplicate of http://issues.jfrog.org/jira/browse/MAP-44 Change By: elifarley (06/Feb/13 3:39 PM) Status: In Progress Resolved Assignee: elifarley Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
kutzi commented on JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 Looks like there was some problem when updating your Jenkins core. The class should definitely be there, but it's not. Maybe some corruption in your Jenkins installation. Can you try to update it again? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13193) Error injecting: org.jfrog.build.extractor.maven.BuildInfoRecorderLifecycleParticipant
elifarley edited a comment on JENKINS-13193 Error injecting: org.jfrog.build.extractor.maven.BuildInfoRecorderLifecycleParticipant Same problem here: UnsupportedClassVersionError: org/jfrog/build/extractor/maven/BuildInfoRecorderLifecycleParticipant : unsupported classversion 50.0 Probably, the jar containing the class 'BuildInfoRecorderLifecycleParticipant' has been compiled to a newer bytecode version. To work around this problem, I selected JDK 6 for my project and it worked. To fix it, the build-info-extractor-maven3-2.0.12.jar should be re-compiled targeting JVM 5. See https://issues.jfrog.org/jira/browse/HAP-359 and http://issues.jfrog.org/jira/browse/MAP-44 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
Laurentius Purba commented on JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 Hi, When you said "update it again", does it mean that I have to go to (since I upgraded from hudson), "Manager Hudson" >> "Manage Plugins" >> "Adavanced" and click on "Submit" button in the "Update Site" section. Please advise. Thanks! -Laurent This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3417) Toggle on main page to hide/show disabled jobs
Dave Abrahams commented on JENKINS-3417 Toggle on main page to hide/show disabled jobs If this is fixed, where is the UI for the feature? I can't find it anywhere, and I'm updated to 1.500! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
kutzi commented on JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 No, I meant the Jenkins core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16669) GitHub SQS Plugin works only once after project config
Andrei Pozolotin created JENKINS-16669 GitHub SQS Plugin works only once after project config Issue Type: Bug Assignee: Unassigned Components: plugin Created: 06/Feb/13 3:47 PM Description: 1) plugin will detect change and trigger build only once after project was enabled for "Build when a message is published to an SQS Queue" 2) all following github changes are detected OK, but build is NOT triggered. jenkins and polling log shown below. jenkins.log INFO: Poked barchart-archon Feb 06, 2013 9:30:28 AM com.base2services.jenkins.github.GitHubTriggerProcessor processGitHubPayload INFO: Received Message for https://github.com/barchart/barchart-archon Feb 06, 2013 9:30:28 AM com.base2services.jenkins.github.GitHubTriggerProcessor processGitHubPayload INFO: Poked barchart-archon sqs-polling.log Started on Feb 6, 2013 9:30:28 AM Using strategy: Default [poll] Last Build : #185 [poll] Last Built Revision: Revision 090ca8c632f936c9cf4fc94f0f4d211f9f0ac341 (origin/master) Fetching changes from the remote Git repositories Fetching upstream changes from g...@github.com:barchart/barchart-archon.git Polling for changes in Done. Took 4.8 sec Changes found Environment: jenkins 1.500 GitHub SQS Plugin 1.4 Project: Jenkins Priority: Major Reporter: Andrei Pozolotin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16669) GitHub SQS Plugin works only once after project config
Andrei Pozolotin assigned JENKINS-16669 to Aaron Walker GitHub SQS Plugin works only once after project config Change By: Andrei Pozolotin (06/Feb/13 3:49 PM) Assignee: Aaron Walker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
Laurentius Purba commented on JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 Hi kutzi, Does it mean I need to download the jenkins.war files from http://mirrors.jenkins-ci.org/war/latest/jenkins.war and copy it to my apache directory, meaning setup in my end? Sorry for my "stupid" question. Thanks! -Laurent This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
kutzi commented on JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 Yes, that's basically what I meant. I don't know if you're just getting and copying the war or getting it from some package repository This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12619) "Failed to test the validity of the user name" on all security matrices since upgrade
Viktor Tarasov commented on JENKINS-12619 "Failed to test the validity of the user name" on all security matrices since upgrade It seems that in my case it's a v1.500 issue. With v1.499 it works as expected (as well as it worked a couple of months before). With v1.500 when same CLI command executed two times, it fails in one of them. I will try to get more logs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16670) Join trigger not kicking off end jobs after update to latest set of plugins.
Christopher Knowlton created JENKINS-16670 Join trigger not kicking off end jobs after update to latest set of plugins. Issue Type: Bug Assignee: mdonohue Attachments: config.xml Components: join Created: 06/Feb/13 4:07 PM Description: Our buildmeister updated all of our plugins to the latest versions (I can create a list if necessary) and the join trigger no longer reliably executes the end jobs. There are no error messages that we can see in any logs, the end job just does not run. I have attached the configuration of one of the top level job. Please let me know what other data I can supply. This has become a critical issue for us here. There were no intentional changes to configuration files associated with the upgrade of plugins, but there were two steps that jenkins forced us to do. 1) Clean up obsolete configuration 2) re-keying of something. (buildmeister did the upgrades, not me) We ran several instances of builds before doing the re-keying and the cleanup and the problem existed then as well. Project: Jenkins Priority: Critical Reporter: Christopher Knowlton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16670) Join trigger not kicking off end jobs after update to latest set of plugins.
Christopher Knowlton commented on JENKINS-16670 Join trigger not kicking off end jobs after update to latest set of plugins. crap, I just refreshed my search and this issue is already reported and still open: 16201 My apologies, I am not sure why it did not show up in my first search. Our issue appears to be exactly the same. ChrisK This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16671) Multiple Selective Claiming of Broken Builds
Ankur Goyal created JENKINS-16671 Multiple Selective Claiming of Broken Builds Issue Type: New Feature Assignee: Christian Åkerström Attachments: Sketch of Claim UI (modified).png Components: claim Created: 06/Feb/13 4:18 PM Description: This is an enhancement on the current claim plugin to support multiple claims of failed builds based on culprit selected. Suggested features to be added are:- 1. List of culprits appear as list in drop down pertaining to the current build failed 2. Scrollable panel that dynamically shows the list of other failed builds based on culprit selected from drop down 3. Select All and Clear selection buttons to either select all builds or clear the selections. Added a sketch diagram of how it looks. Pull request link: https://github.com/jenkinsci/claim-plugin/pull/6 Project: Jenkins Labels: plugin Priority: Major Reporter: Ankur Goyal This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16347) No images served to Anonymous users
Dave Abrahams commented on JENKINS-16347 No images served to Anonymous users Bump. I am really clueless on this one and would dearly like it to get a little bit of attention. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16617) Github SQS plugin not starting jobs on Jenkins 1.500
Barrett Strausser commented on JENKINS-16617 Github SQS plugin not starting jobs on Jenkins 1.500 I don't even get that logging output. The plugin seemed to work once. And then fails to detect any further changes in the repo. The sqs activity for my job looks like : Started on Feb 1, 2013 5:19:10 PM Using strategy: Default [poll] Last Build : #1 [poll] Last Built Revision: Revision 2ba24e8e3e7e84fac84831c2fc46a1d222be742f (origin/TacoBellyMigrationFix) Fetching changes from the remote Git repositories Fetching upstream changes from g...@github.com:bstrausser/blackbird.git Polling for changes in Done. Took 1.9 sec Changes found I forked/cloned the repo. Raven maven install. Dropped the hpi into the plugin directory. No joy. I could really use this plugin so I'll give it a more thorough look if I have time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16617) Github SQS plugin not starting jobs on Jenkins 1.500
Barrett Strausser commented on JENKINS-16617 Github SQS plugin not starting jobs on Jenkins 1.500 Hi everyone. I need this bug/feature so much that I'm willing to pay 40.00 bucks for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/153/github-sqs-plugin-not-starting-jobs-on-jenkins-1500). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds based on parameter value should be listed as downstream builds
cjo9900 commented on JENKINS-16659 TriggerBuilder builds based on parameter value should be listed as downstream builds The pull request[1] from wolfs will fix this at the build level, and list them on the build page, for the triggered downstream builds. And the triggered builds will have started by Upstream cause linking to the correct build. However the project page will not be able to display these links as the parameters do not exist so cannot be evaluated, which is why there are not shown in the upstream/downstream list. [1] https://github.com/jenkinsci/parameterized-trigger-plugin/pull/19 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16617) Github SQS plugin not starting jobs on Jenkins 1.500
Barrett Strausser edited a comment on JENKINS-16617 Github SQS plugin not starting jobs on Jenkins 1.500 I don't even get that logging output. The plugin seemed to work once and then fails to detect any further changes in the repo. The sqs activity for my job looks like : Started on Feb 1, 2013 5:19:10 PM Using strategy: Default [poll] Last Build : #1 [poll] Last Built Revision: Revision 2ba24e8e3e7e84fac84831c2fc46a1d222be742f (origin/TacoBellyMigrationFix) Fetching changes from the remote Git repositories Fetching upstream changes from g...@github.com:bstrausser/blackbird.git Polling for changes in Done. Took 1.9 sec Changes found My repo is no longer at the SHA 2ba24e8e3e7e84f I forked/cloned the repo. Ran maven install. Dropped the hpi into the plugin directory. No joy. I could really use this plugin so I'll give it a more thorough look if I have time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16672) Unprivileged view permissions for monitoring
Bart Bialek created JENKINS-16672 Unprivileged view permissions for monitoring Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: monitoring Created: 06/Feb/13 6:02 PM Description: I use authentication with Jenkins. I would like non-administrators to see performance stats. Unfortunately, when anonymous or read only users try to access /monitoring they get: "Access Denied: $USER is missing the Administer permission" Can you add permissions to the matrix so non-privileged users can browse stats? Project: Jenkins Priority: Major Reporter: Bart Bialek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14278) A parameterized buildstep in a matrix project causes IllegalArgumentException
SCM/JIRA link daemon commented on JENKINS-14278 A parameterized buildstep in a matrix project causes IllegalArgumentException Code changed in jenkins User: c3johnso Path: src/test/java/hudson/plugins/parameterizedtrigger/test/TriggerBuilderTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/f26766b3eca5ebdd3388b1a0ba2fdb86c338c9fc Log: Test cases to show JENKINS-14278 occuring. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13872) Counter Parameter Factory
SCM/JIRA link daemon commented on JENKINS-13872 Counter Parameter Factory Code changed in jenkins User: c3johnso Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildTriggerConfig.java src/main/java/hudson/plugins/parameterizedtrigger/CounterBuildParameterFactory.java src/main/resources/hudson/plugins/parameterizedtrigger/CounterBuildParameterFactory/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/CounterBuildParameterFactory/help-validationFail.html src/main/resources/hudson/plugins/parameterizedtrigger/Messages.properties src/test/java/hudson/plugins/parameterizedtrigger/test/CounterBuildParameterFactoryUnitTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/89a1d2365c6d6c750aeefb2a94de0ae2b96c8b93 Log: Add behaviour options for counter factory in case of invalid options. [FIXED JENKINS-13872] Add the possibility of skipping the triggering, or ignoring the parameters when the to, from and step elements do not form a contained set. Corrected an issue in the BuildTriggerConfig class where if a factory returned no parameters meant that no projects would be triggered in certain cases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
SCM/JIRA link daemon commented on JENKINS-14545 Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildInfoExporterAction.java src/main/resources/hudson/plugins/parameterizedtrigger/BlockableBuildTriggerConfig/help-block.html http://jenkins-ci.org/commit/parameterized-trigger-plugin/2a276922f90844924b1a32fd1fec7133e1db9311 Log: [FIXED JENKINS-14545] Correct Env variables Extend and correct Enviroment variables that are provided when using block until other projects are completed, in the trigger/call other projects buildstep. Extended vaiables to provide the full list of projects triggered, and the full list of builds triggered when using the parameter factories. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
SCM/JIRA link daemon resolved JENKINS-14545 as Fixed Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname Change By: SCM/JIRA link daemon (06/Feb/13 6:08 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15834) It's not possible to specify multiple property files in parametrised trigger
SCM/JIRA link daemon resolved JENKINS-15834 as Fixed It's not possible to specify multiple property files in parametrised trigger Change By: SCM/JIRA link daemon (06/Feb/13 6:08 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
SCM/JIRA link daemon commented on JENKINS-14545 Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildInfoExporterAction.java src/main/resources/hudson/plugins/parameterizedtrigger/BlockableBuildTriggerConfig/help-block.html src/test/java/hudson/plugins/parameterizedtrigger/test/BuildInfoExporterTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/ac43521d48e99eb0f441e9e89d810771791267fd Log: [FIXED JENKINS-14545] Correct and add testcases for Env variables This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15834) It's not possible to specify multiple property files in parametrised trigger
SCM/JIRA link daemon commented on JENKINS-15834 It's not possible to specify multiple property files in parametrised trigger Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/FileBuildParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-failTriggerOnMissing.html src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-propertiesFile.html src/test/java/hudson/plugins/parameterizedtrigger/test/FileBuildTriggerConfigTest.java src/test/resources/hudson/plugins/parameterizedtrigger/test/multiple_property_files.zip http://jenkins-ci.org/commit/parameterized-trigger-plugin/d8758e442287caebd244fc5fbbf7d06089aac377 Log: [FIXED JENKINS-15834] Allow multiple properties files Support the passing of multiple property files via a comma seperated list. Correct help messages and add behaviour to correctly skip triggering downstream if a file is missing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13852) Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter
SCM/JIRA link daemon resolved JENKINS-13852 as Fixed Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter Change By: SCM/JIRA link daemon (06/Feb/13 6:08 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16644) When using Perforce Plugin, P4_CHANGELIST variable gets incorrect value
Dmitriy Pupov commented on JENKINS-16644 When using Perforce Plugin, P4_CHANGELIST variable gets incorrect value yeah 1.3.19 resolve issue, thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16334) Define impllicit parameter: "build them on the same node"
SCM/JIRA link daemon resolved JENKINS-16334 as Fixed Define impllicit parameter: "build them on the same node" Change By: SCM/JIRA link daemon (06/Feb/13 6:08 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15920) Boolean parameter becomes string
SCM/JIRA link daemon commented on JENKINS-15920 Boolean parameter becomes string Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BooleanParameterConfig.java src/main/java/hudson/plugins/parameterizedtrigger/BooleanParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/BooleanParameterConfig/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/BooleanParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/BooleanParameters/help-configs.html http://jenkins-ci.org/commit/parameterized-trigger-plugin/0a66ecaf22c143a982c3a6a1c3c3ffd13fd7bd41 Log: [FIXED JENKINS-15920] Add boolean parameter option Add a parameter item to allow boolean parameters to be passed to down stream jobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16334) Define impllicit parameter: "build them on the same node"
SCM/JIRA link daemon commented on JENKINS-16334 Define impllicit parameter: "build them on the same node" Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/NodeAction.java src/main/java/hudson/plugins/parameterizedtrigger/NodeParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/NodeAction/badge.jelly src/main/resources/hudson/plugins/parameterizedtrigger/NodeParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/NodeParameters/help-current.html src/test/java/hudson/plugins/parameterizedtrigger/test/NodeParametersTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/1c15f7bc68c690dd0cab9ce05ec859bac0f3f05b Log: [FIXED JENKINS-16334] Add current node parameter Adds a current node parameter which forces the downstream builds to build on the same node as the triggering job. Will override any tie this job to node settings of the downstream job. Adds a build badge to indicate that a fixed node was used. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13852) Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter
SCM/JIRA link daemon commented on JENKINS-13852 Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/SubversionRevisionBuildParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/SubversionRevisionBuildParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/SubversionRevisionBuildParameters/help-includeUpstreamParameters.html src/main/resources/hudson/plugins/parameterizedtrigger/SubversionRevisionBuildParameters/help.html http://jenkins-ci.org/commit/parameterized-trigger-plugin/ff23938d9bf13944e398df8779ba3cb0b643c8a0 Log: [FIXED JENKINS-13852] Allow upstream SVN parameters to be passed downstream Added an option to allow upstream svn parameters to be passed to downstream builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15920) Boolean parameter becomes string
SCM/JIRA link daemon resolved JENKINS-15920 as Fixed Boolean parameter becomes string Change By: SCM/JIRA link daemon (06/Feb/13 6:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11669) Parameterized trigger from a multi-configuration project triggers downstream jobs twice
SCM/JIRA link daemon commented on JENKINS-11669 Parameterized trigger from a multi-configuration project triggers downstream jobs twice Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/0ca4cbd2b9456b853be57bf8410bb24ee387effc Log: [FIXED JENKINS-11669] Removed MatrixAggregator Removed MatrixAggregator as not required after Jenkins 1.387 as BuildTrigger is called from AbstractBuild.cleanup() in all cases and we require 1.424 at the minimum. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11669) Parameterized trigger from a multi-configuration project triggers downstream jobs twice
SCM/JIRA link daemon resolved JENKINS-11669 as Fixed Parameterized trigger from a multi-configuration project triggers downstream jobs twice Change By: SCM/JIRA link daemon (06/Feb/13 6:08 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14278) A parameterized buildstep in a matrix project causes IllegalArgumentException
SCM/JIRA link daemon commented on JENKINS-14278 A parameterized buildstep in a matrix project causes IllegalArgumentException Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildTriggerConfig.java src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java src/test/java/hudson/plugins/parameterizedtrigger/test/TriggerBuilderTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/046294a3d96872d5eb99f559e60e8e3ba1b2eb27 Log: Merge branch 'JENKINS-14278' of git://github.com/cjo9900/parameterized-trigger-plugin into 2.17-RC Resolved Conflicts: src/test/java/hudson/plugins/parameterizedtrigger/test/TriggerBuilderTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15920) Boolean parameter becomes string
SCM/JIRA link daemon commented on JENKINS-15920 Boolean parameter becomes string Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BooleanParameterConfig.java src/main/java/hudson/plugins/parameterizedtrigger/BooleanParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/BooleanParameterConfig/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/BooleanParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/BooleanParameters/help-configs.html http://jenkins-ci.org/commit/parameterized-trigger-plugin/af93a4194fc21edf49fa64bae287d9aa9f84d214 Log: Merge branch 'JENKINS-15920' of git://github.com/cjo9900/parameterized-trigger-plugin into 2.17-RC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16334) Define impllicit parameter: "build them on the same node"
SCM/JIRA link daemon commented on JENKINS-16334 Define impllicit parameter: "build them on the same node" Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/NodeAction.java src/main/java/hudson/plugins/parameterizedtrigger/NodeParameters.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/f0f493dfdf61a090f7109121db6613bf9363c70f Log: JENKINS-16334 Change to store label Get master label rather than fixed string This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15834) It's not possible to specify multiple property files in parametrised trigger
SCM/JIRA link daemon commented on JENKINS-15834 It's not possible to specify multiple property files in parametrised trigger Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/FileBuildParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-failTriggerOnMissing.html src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-propertiesFile.html src/test/java/hudson/plugins/parameterizedtrigger/test/FileBuildTriggerConfigTest.java src/test/resources/hudson/plugins/parameterizedtrigger/test/multiple_property_files.zip http://jenkins-ci.org/commit/parameterized-trigger-plugin/51ea12464663e35ebcfa4922efb65f2a64913daf Log: Merge branch 'JENKINS-15834' of git://github.com/cjo9900/parameterized-trigger-plugin into 2.17-RC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13852) Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter
SCM/JIRA link daemon commented on JENKINS-13852 Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/SubversionRevisionBuildParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/SubversionRevisionBuildParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/SubversionRevisionBuildParameters/help-includeUpstreamParameters.html src/main/resources/hudson/plugins/parameterizedtrigger/SubversionRevisionBuildParameters/help.html http://jenkins-ci.org/commit/parameterized-trigger-plugin/9a427db4900df58bb8f2aee3d81fbf3dbdda9d81 Log: Merge branch 'JENKINS-13852' of git://github.com/cjo9900/parameterized-trigger-plugin into 2.17-RC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16334) Define impllicit parameter: "build them on the same node"
SCM/JIRA link daemon commented on JENKINS-16334 Define impllicit parameter: "build them on the same node" Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/NodeAction.java src/main/java/hudson/plugins/parameterizedtrigger/NodeParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/NodeAction/badge.jelly src/main/resources/hudson/plugins/parameterizedtrigger/NodeParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/NodeParameters/help-current.html src/test/java/hudson/plugins/parameterizedtrigger/test/NodeParametersTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/16c37c12ef4f62b52fd8089038e015f427a2b300 Log: Merge branch 'JENKINS-16334' of git://github.com/cjo9900/parameterized-trigger-plugin into 2.17-RC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11669) Parameterized trigger from a multi-configuration project triggers downstream jobs twice
SCM/JIRA link daemon commented on JENKINS-11669 Parameterized trigger from a multi-configuration project triggers downstream jobs twice Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/86e296911721d42ccf0d03749002e753bb8ed514 Log: Merge branch 'JENKINS-11669' of git://github.com/cjo9900/parameterized-trigger-plugin into 2.17-RC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
SCM/JIRA link daemon commented on JENKINS-14545 Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildInfoExporterAction.java src/main/resources/hudson/plugins/parameterizedtrigger/BlockableBuildTriggerConfig/help-block.html src/test/java/hudson/plugins/parameterizedtrigger/test/BuildInfoExporterTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/fae74afa6b3f88ce184635079f766ee5ba91e2d7 Log: Merge branch 'JENKINS-14545' of git://github.com/cjo9900/parameterized-trigger-plugin into 2.17-RC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13872) Counter Parameter Factory
SCM/JIRA link daemon commented on JENKINS-13872 Counter Parameter Factory Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildTriggerConfig.java src/main/java/hudson/plugins/parameterizedtrigger/CounterBuildParameterFactory.java src/main/java/hudson/plugins/parameterizedtrigger/FileBuildParameterFactory.java src/main/resources/hudson/plugins/parameterizedtrigger/CounterBuildParameterFactory/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/CounterBuildParameterFactory/help-validationFail.html src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameterFactory/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameterFactory/help-noFilesFoundAction.html src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameterFactory/help.html src/main/resources/hudson/plugins/parameterizedtrigger/Messages.properties src/test/java/hudson/plugins/parameterizedtrigger/test/CounterBuildParameterFactoryUnitTest.java src/test/java/hudson/plugins/parameterizedtrigger/test/FileBuildParameterFactoryTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/e681c6924350457cd5db8c5e4c13aa1fda2a42ac Log: Merge branch 'JENKINS-13872' of git://github.com/cjo9900/parameterized-trigger-plugin into 2.17-RC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13872) Counter Parameter Factory
SCM/JIRA link daemon commented on JENKINS-13872 Counter Parameter Factory Code changed in jenkins User: cjo9900 Path: src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameterFactory/help-noFilesFoundAction.html http://jenkins-ci.org/commit/parameterized-trigger-plugin/89e0f19f5d8840badbb75121eba1638826077f29 Log: JENKINS-13872 Correct file factory help text This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13872) Counter Parameter Factory
SCM/JIRA link daemon resolved JENKINS-13872 as Fixed Counter Parameter Factory Change By: SCM/JIRA link daemon (06/Feb/13 6:08 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16644) When using Perforce Plugin, P4_CHANGELIST variable gets incorrect value
Rob Petti resolved JENKINS-16644 as Fixed When using Perforce Plugin, P4_CHANGELIST variable gets incorrect value Change By: Rob Petti (06/Feb/13 6:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16673) No alternate contact options
Bart Bialek created JENKINS-16673 No alternate contact options Issue Type: Improvement Assignee: Unassigned Components: jira Created: 06/Feb/13 6:26 PM Description: I had a problem creating an account in your jira. It seems there are no alternate ways of contacting Jenkins admins: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa Project: Jenkins Priority: Minor Reporter: Bart Bialek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11577) Matrix axis are not recognixed as parameter
cjo9900 commented on JENKINS-11577 Matrix axis are not recognixed as parameter Currently the AXIS parameters are not added the environment that the parameterized trigger uses in the trigger build step. They are missing when the plugin does build.getEnvironment()[0] as MatrixRun does not add them to this, so defaults to the ones added in AbstractBuild [1] But they are added to the build.getBuildVariables(), as the are added in the MatrixRun [2] So the solution might be to add these via a EnvironmentContributor [3] in the MatrixRun class. [0] https://github.com/jenkinsci/parameterized-trigger-plugin/blob/c04e84770dfab3459f01047be95888ecb353cbbd/src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java#L59 [1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractBuild.java#L935 [2] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/matrix/MatrixRun.java#L114 [3] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/EnvironmentContributor.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16674) TAP parser fails parsing output with messages
Jan Kopriva created JENKINS-16674 TAP parser fails parsing output with messages Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap Created: 06/Feb/13 6:56 PM Description: When tap output contains messages like: 17:14:06 ok 169 - SL_Chrome ListFilterConfiguration controller should be able to switch list filter mode' passed (357ms) 17:14:06 not ok 170 - SL_Chrome Module: ListFilterConfiguration content from controller is present through bindings in both tabs 17:14:06 — 17:14:06 message: ""Values should not be null. actual:undefined, expected: undefined"" 17:14:06 ... It fails with: :13 org.tap4j.parser.ParserException: Error parsing TAP Stream: Error parsing YAML [message: ""Values should not be null. actual:undefined, expected: undefined"" 17:14:13 ]: while parsing a block mapping; expected , but found Scalar; in 'string', line 1, column 16: 17:14:13 message: ""Values should not be null. actua ... 17:14:13^ 17:14:13 at org.tap4j.parser.Tap13YamlParser.parseFile(Tap13YamlParser.java:602) 17:14:13 at org.tap4j.plugin.TapParser.parse(TapParser.java:105) 17:14:13 at org.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:297) 17:14:13 at org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:239) 17:14:13 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) 17:14:13 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 17:14:13 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779) 17:14:13 at hudson.model.Build$BuildExecution.post2(Build.java:183) 17:14:13 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) 17:14:13 at hudson.model.Run.execute(Run.java:1568) 17:14:13 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 17:14:13 at hudson.model.ResourceController.execute(ResourceController.java:88) 17:14:13 at hudson.model.Executor.run(Executor.java:236) 17:14:13 Caused by: org.tap4j.parser.ParserException: Error parsing YAML [message: ""Values should not be null. actual:undefined, expected: undefined"" 17:14:13 ]: while parsing a block mapping; expected , but found Scalar; in 'string', line 1, column 16: 17:14:13 message: ""Values should not be null. actua ... 17:14:13^ 17:14:13 at org.tap4j.parser.Tap13YamlParser.checkAndParseTapDiagnostic(Tap13YamlParser.java:691) 17:14:13 at org.tap4j.parser.Tap13YamlParser.parseLine(Tap13YamlParser.java:232) 17:14:13 at org.tap4j.parser.Tap13YamlParser.parseFile(Tap13YamlParser.java:597) 17:14:13 ... 12 more 17:14:13 Caused by: while parsing a block mapping 17:14:13 in 'string', line 1, column 5: 17:14:13 message: ""Values should not be ... 17:14:13 ^ 17:14:13 expected , but found Scalar 17:14:13 in 'string', line 1, column 16: 17:14:13 message: ""Values should not be null. actua ... 17:14:13^ 17:14:13 17:14:13 at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:570) 17:14:13 at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:158) 17:14:13 at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:143) 17:14:13 at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230) 17:14:13 at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159) 17:14:13 at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122) 17:14:13 at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105) 17:14:13 at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120) 17:14:13 at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481) 17:14:13 at org.yaml.snakeyaml.Yaml.load(Yaml.java:400) 17:14:13 at org.tap4j.parser.Tap13YamlParser.checkAndParseTapDiagnostic(Tap13YamlParser.java:687) 17:14:13 ... 14 more 17:14:13 Processing '/var/lib/jenkins/jobs/Trunk_Client_Unit_tests_JK/builds/2013-02-06_17-07-47/tap-master-files/tap_out_sl_firefox.txt' 17:14:13 Parsing TAP test result [/va
[JIRA] (JENKINS-7813) Archiving artifacts very slow
Loren Keagle commented on JENKINS-7813 Archiving artifacts very slow I see this same slowness when archiving artifacts just on the master. Final output of our build sequence generates ISO images with our installers and tools, and archiving these files takes ages. No master/slave setup, same hard disk... Agonizingly slow. This would take only a minute or two if I were fingerprinting and copying the files manually. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16675) Includes and Excludes lists ignore basepath when checking for existence of files
Wesley Hirsch created JENKINS-16675 Includes and Excludes lists ignore basepath when checking for existence of files Issue Type: Bug Assignee: Gregory Boissinot Components: artifactdeployer Created: 06/Feb/13 8:02 PM Description: I've populated basepath with target/artifacts (as that's where my build process dumps artifacts), and I've entered *.rpm into the Files to deploy box. Once I click outside of the box, I get the following message underneath the box: '.rpm' doesn't match anything, but 'target/artifacts/.rpm' does. Perhaps that's what you mean? The actual deploy process works fine, and uses basepath, but apparently the check to determine whether it's a valid files list does not. The same exact error occurs with Excludes. Project: Jenkins Priority: Minor Reporter: Wesley Hirsch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12832) check XSLT is not good enough
Michael Wright edited a comment on JENKINS-12832 check XSLT is not good enough I just finished writing (and testing) a new XSLT for use with Check 0.9.9. Attached as check_unittest_to_xml.xslt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
