[JIRA] (JENKINS-16630) Human readable file size method returns ,00 for files with byte length 0
SCM/JIRA link daemon resolved JENKINS-16630 as Fixed Human readable file size method returns ,00 for files with byte length 0 Change By: SCM/JIRA link daemon (17/Feb/13 9:53 AM) 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-16630) Human readable file size method returns ,00 for files with byte length 0
SCM/JIRA link daemon commented on JENKINS-16630 Human readable file size method returns ,00 for files with byte length 0 Code changed in jenkins User: Fred G Path: core/src/test/java/hudson/FunctionsTest.java http://jenkins-ci.org/commit/jenkins/6437fe2e7804371243aab0c19283063df8f61ea9 Log: Unit test for JENKINS-16630 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-16630) Human readable file size method returns ,00 for files with byte length 0
SCM/JIRA link daemon commented on JENKINS-16630 Human readable file size method returns ,00 for files with byte length 0 Code changed in jenkins User: Fred G Path: core/src/main/java/hudson/Functions.java http://jenkins-ci.org/commit/jenkins/f19f772322ab3645d4f0784f28acdccc5b8ea582 Log: FIXED JENKINS-16630 Human readable file size method returns ",00" for files with byte length 0 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-16630) Human readable file size method returns ,00 for files with byte length 0
SCM/JIRA link daemon commented on JENKINS-16630 Human readable file size method returns ,00 for files with byte length 0 Code changed in jenkins User: Christoph Kutzinski Path: core/src/main/java/hudson/Functions.java core/src/test/java/hudson/FunctionsTest.java http://jenkins-ci.org/commit/jenkins/ad64bcd61201a43d850fd5e6151d8503e659cffe Log: Merge pull request #691 from fredg02/JENKINS-16630 FIXED JENKINS-16630 Human readable file size method returns ",00" for files with byte length 0 Compare: https://github.com/jenkinsci/jenkins/compare/17fabea10cd9...ad64bcd61201 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-16630) Human readable file size method returns ,00 for files with byte length 0
SCM/JIRA link daemon commented on JENKINS-16630 Human readable file size method returns ,00 for files with byte length 0 Code changed in jenkins User: Christoph Kutzinski Path: changelog.html http://jenkins-ci.org/commit/jenkins/c98ca86b7d08f75244de0b1f209f13abd80a2002 Log: Changelog for JENKINS-16630 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-16846) hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file
KK Kon
created JENKINS-16846
hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
17/Feb/13 10:20 AM
Description:
hudson.tools.DownloadFromUrlInstaller#performInstallation
faild at call 'base.moveAllChildrenTo(expected)'
archived file example:
+- test
+- sub
+- sub
'test/sub'.moveAllChildrenTo('test') fail at hudson.FilePath
'test/sub/sub'.renameTo('test/sub') failed.
It caused by destination folder 'test/sub' that existed already.
Environment:
Windows
Project:
Jenkins
Labels:
jenkins
windows
Priority:
Major
Reporter:
KK Kon
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-16846) hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file
KK Kon
updated JENKINS-16846
hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file
Change By:
KK Kon
(17/Feb/13 10:24 AM)
Description:
hudson.tools.DownloadFromUrlInstaller#performInstallationfaildatcallbase.moveAllChildrenTo(expected)archivedfileexample:{
quote
noformat
}+-test+-sub+-sub{
quote
noformat
}test/sub.moveAllChildrenTo(test)failathudson.FilePathtest/sub/sub.renameTo(test/sub)failed.Itcausedbydestinationfoldertest/subthatexistedalready.
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-16846) hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file
KK Kon
updated JENKINS-16846
hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file
Change By:
KK Kon
(17/Feb/13 10:29 AM)
Description:
hudson.tools.DownloadFromUrlInstaller#performInstallationfaildatcallbase.moveAllChildrenTo(expected)archivedfileexample:{noformat}+-test+-sub+-sub{noformat}test/sub.moveAllChildrenTo(test)failathudson.FilePathtest/sub/sub.renameTo(test/
sub
)failed.Itcausedbydestinationfoldertest/subthatexistedalready.
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-16847) Support for copying artifacts from other builds being part of the same MultiJob (previous phases)
Krzysztof Trojan created JENKINS-16847 Support for copying artifacts from other builds being part of the same MultiJob (previous phases) Issue Type: New Feature Assignee: Unassigned Attachments: copyartifact-plugin-trojanbug.zip Components: copyartifact Created: 17/Feb/13 10:31 AM Description: Currently there is no easy way of selecting the right build to copy artifacts from if the project we want to copy from is part of MultiJob. The "Last Successful Build" is prone for selecting the wrong build if the project was build again in the meantime between the MultiJob start and current moment and "Upstream Project That Triggered this Build" does not work as previously executed builds in the same MultiJob are not considered "upstream" (are not listed as "causes"). A patch to TriggeredBuildSelector has been created to explicitly support MultiJob plugin pipelines and query it for builds already completed, treating them as if they were "causes". Somewhat dirty (for in for loop ), but works correctly and for the number of projects in a pipeline does not matter much. See attachment. Complete project as I did not have a decent diff on the machine I am writing this on (sorry!). Fix Versions: current Project: Jenkins Priority: Major Reporter: Krzysztof Trojan 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-16630) Human readable file size method returns ,00 for files with byte length 0
dogfood commented on JENKINS-16630 Human readable file size method returns ,00 for files with byte length 0 Integrated in jenkins_main_trunk #2285 FIXED JENKINS-16630 Human readable file size method returns ",00" for (Revision f19f772322ab3645d4f0784f28acdccc5b8ea582) Unit test for JENKINS-16630 (Revision 6437fe2e7804371243aab0c19283063df8f61ea9) Result = SUCCESS Fred G : f19f772322ab3645d4f0784f28acdccc5b8ea582 Files : core/src/main/java/hudson/Functions.java Fred G : 6437fe2e7804371243aab0c19283063df8f61ea9 Files : core/src/test/java/hudson/FunctionsTest.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-16848) Error when upgrading from version 1500
Sergey Grigoriev created JENKINS-16848 Error when upgrading from version 1500 Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Feb/13 11:11 AM Description: When upgrading version 1500 to a newer version I get errors Failed to resolve host name mirrors.karan.org. Perhaps you need to configure HTTP proxy? java.net.UnknownHostException: mirrors.karan.org at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at java.net.Socket.connect(Socket.java:478) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836) at sun.net.www.protocol.http.HttpURLConnection.followRedirect(HttpURLConnection.java:2124) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1367) at hudson.model.UpdateCenter$UpdateCenterConfiguration.testConnection(UpdateCenter.java:819) at hudson.model.UpdateCenter$UpdateCenterConfiguration.checkUpdateCenter(UpdateCenter.java:668) at hudson.model.UpdateCenter$ConnectionCheckJob.run(UpdateCenter.java:985) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Project: Jenkins Priority: Major Reporter: Sergey Grigoriev 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-16847) Support for copying artifacts from other builds being part of the same MultiJob (previous phases)
Krzysztof Trojan assigned JENKINS-16847 to Alan Harder Support for copying artifacts from other builds being part of the same MultiJob (previous phases) Could you please take a look if the contribution could be made part of the next version, I would prefer not to depend on branched code in my builds. Change By: Krzysztof Trojan (17/Feb/13 11:13 AM) Assignee: AlanHarder 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-14730) Support File Multi Extended Choice parameters
steven armstrong commented on JENKINS-14730 Support File Multi Extended Choice parameters Does this fix mean we can use the conditional buildstep plugin in a multijob job and not lose the nice job layout on the multijob page? When will this fix go in to a new release of the multijob plugin? 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-16630) Human readable file size method returns ,00 for files with byte length 0
dogfood commented on JENKINS-16630 Human readable file size method returns ,00 for files with byte length 0 Integrated in jenkins_main_trunk #2286 Changelog for JENKINS-16630 (Revision c98ca86b7d08f75244de0b1f209f13abd80a2002) Result = SUCCESS Christoph Kutzinski : c98ca86b7d08f75244de0b1f209f13abd80a2002 Files : changelog.html 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-16844) Triggering a build from the context menu produces a warning
Sami Salonen updated JENKINS-16844 Triggering a build from the context menu produces a warning Change By: Sami Salonen (17/Feb/13 12:06 PM) Component/s: ldap Component/s: 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-16844) Triggering a build from the context menu produces a warning
Sami Salonen commented on JENKINS-16844 Triggering a build from the context menu produces a warning Steps to reproduce: Start Jenkins (java -jar jenkins.war) Create a free-style project (default configuration is fine) Trigger a build from a context menu. Works fine. Add directory server based authentication: Click Enable security in global configuration From Access Control section, select LDAP under Security Realm Fill in Server, root DN, User search base, User search filter, Group search base, Manager DN, Manager Password (For Authorization, I tried both Anyone can do anything and Matrix-based security with same effect) Trigger a build from a context menu. Warning message is displayed. 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-16844) Triggering a build from the context menu produces a warning
Sami Salonen updated JENKINS-16844 Triggering a build from the context menu produces a warning Change By: Sami Salonen (17/Feb/13 12:23 PM) Environment: Jenkins1.480.3(WinstoneandTomcat) LDAPplugin1.1and1.2 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-4804) exceptions when submitting form in 1.333 with Winstone
Vlad Beffa
commented on JENKINS-4804
exceptions when submitting form in 1.333 with Winstone
My problem is more closely related to https://issues.jenkins-ci.org/browse/JENKINS-4833 but that is marked as a duplicate of this bug.
I just installed Jenkins 1.502 on RedHat CentOS 6.3. Because the server already has Apache on it I set JENKINS_PORT="8081" and JENKINS_AJP_PORT="-1" to avoid port conflicts. Jenkins starts up OK. When I go to Manage Plugins, though, the list is empty. In the log file I see the same exception described above.
I tried to update the site on the Advanced tab using the default URL http://updates.jenkins-ci.org/update-center.json but that didn't help.
WARNING: Untrapped servlet exception
javax.servlet.ServletException: net.sf.json.JSONException: Unterminated string at character 228525 of {"connectionCheckUrl": "http://www.google.com/", "core"
...
8-22T16:03:14.00Z", "requiredCore": "1.466", "scm": "github.com", "sha1": "uWryTtC4mZPwLfmZ8JjHHT1tZDo=", "title": "Groovy Postbuild Plugin", "url": "http://updates.jenkins-ci.org/download/plu
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
at org.kohsuke.stapler.Stapler.service(Stapler.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at
[JIRA] (JENKINS-16846) hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file
KK Kon commented on JENKINS-16846 hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file I made pull request https://github.com/jenkinsci/jenkins/pull/714 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
SCM/JIRA link daemon commented on JENKINS-16662 Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds Code changed in jenkins User: gcummings Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildInfoExporterAction.java src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java src/test/java/hudson/plugins/parameterizedtrigger/test/BuildInfoExporterTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/9cb8c3c1257d996e0a11304a6fe71a4f5e28cf15 Log: JENKINS-16662 : Add TRIGGERED_BUILD_RESULT_ to environment 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-16662) Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds
SCM/JIRA link daemon commented on JENKINS-16662 Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds Code changed in jenkins User: cjo9900 Path: src/main/java/hudson/plugins/parameterizedtrigger/BuildInfoExporterAction.java src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java src/test/java/hudson/plugins/parameterizedtrigger/test/BuildInfoExporterTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/adc3b5d8db148559de2728ab6bbd756883078e34 Log: Merge branch 'JENKINS-16662' of github.com:gcummings/parameterized-trigger-plugin into 2.17-RC Resolved Conflicts: src/main/java/hudson/plugins/parameterizedtrigger/BuildInfoExporterAction.java src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.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-16847) Support for copying artifacts from other builds being part of the same MultiJob (previous phases)
Krzysztof Trojan commented on JENKINS-16847 Support for copying artifacts from other builds being part of the same MultiJob (previous phases) Created a pull request (finally on my machine ): https://github.com/jenkinsci/copyartifact-plugin/pull/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-13678) Maven test failures hide more important errors
kutzi resolved JENKINS-13678 as Incomplete Maven test failures hide more important errors No feedback from reporter = Incomplete Change By: kutzi (17/Feb/13 2:27 PM) Status: Open Resolved Resolution: Incomplete 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-16846) hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file
KK Kon updated JENKINS-16846 hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file Change By: KK Kon (17/Feb/13 3:00 PM) Labels: jenkins windows Environment: Windows 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-16846) hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file
KK Kon commented on JENKINS-16846 hudson.tools.DownloadFromUrlInstaller#performInstallation faild when same named directory in archived file Linux occured. not only Windows. Running hudson.FilePathTest Tests run: 20, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 14.181 sec FAILURE! testMoveAllChildrenTo(hudson.FilePathTest) Time elapsed: 0.141 sec ERROR! java.io.IOException: Failed to rename /home/kkkon/jenkins/core/target/hudson524228362593606165tmp/test/sub/sub to /home/kkkon/jenkins/core/target/hudson524228362593606165tmp/test/sub at hudson.FilePath$32.invoke(FilePath.java:1666) at hudson.FilePath$32.invoke(FilePath.java:1658) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.moveAllChildrenTo(FilePath.java:1658) at hudson.FilePathTest.testMoveAllChildrenTo(FilePathTest.java:601) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) 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-7242) confusing error when report directory is empty
imtalmor commented on JENKINS-7242 confusing error when report directory is empty Hi. I get a similar error. why is my report directory empty? shouldn't the plugin create a report in there? I have a task which simply runs a windows batch (calling PHPUnit to run PHP code created with Selenium IDE) I would like to get an HTML report out. Am I missing anything here in the config? 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-13218) Can't add build step on current jenkins with manual installed buckminster 3.7
SCM/JIRA link daemon commented on JENKINS-13218 Cant add build step on current jenkins with manual installed buckminster 3.7 Code changed in jenkins User: Lorenzo Bettini Path: src/main/resources/hudson/plugins/buckminster/EclipseBuckminsterBuilder/config.jelly http://jenkins-ci.org/commit/buckminster-plugin/500720c65cd214fe4b4c518699fcdf5aff083650 Log: JENKINS-13218: Can't add build step on current jenkins https://issues.jenkins-ci.org/browse/JENKINS-13218 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-7242) confusing error when report directory is empty
mcrooney commented on JENKINS-7242 confusing error when report directory is empty Hi imtalmor. The plugin doesn't create any HTML Reports, it simply archives / aggregates them for you, so they need to already exist. You are probably better off using the xUnit plugin and pointing it at XML results that you configure PHPUnit to generate, or having PHPUnit generate HTML reports which I believe it can do if you look at its documentation. 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-16849) StackOverflowError involving findMailAddressFor
Kaspar Fischer created JENKINS-16849 StackOverflowError involving findMailAddressFor Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: postbuild-task Created: 17/Feb/13 5:20 PM Description: When my Play Framework 2.1 project runs its tests, it fails with the error given below. I verified that emails can be sent by using the "Test configuration by sending test e-mail" button in "Configure system". If I can provide any additional information, please let me know. info Passed: : Total 3, Failed 0, Errors 0, Passed 3, Skipped 0 success Total time: 58 s, completed Feb 17, 2013 5:50:12 PM info Generating Scala API documentation for main sources to /var/lib/jenkins/workspace/Athina-repo/repo/target/scala-2.10/api... model contains 17 documentable templates info Scala API documentation generation successful. success Total time: 11 s, completed Feb 17, 2013 5:50:23 PM Build step 'Build using sbt' changed build result to SUCCESS Publishing Javadoc Sending e-mails to: kaspar.fisc...@dreizak.com FATAL: null java.lang.StackOverflowError at java.lang.String$CaseInsensitiveComparator.compare(String.java:1170) at java.lang.String.compareToIgnoreCase(String.java:1220) at hudson.model.User$1.compare(User.java:397) at hudson.model.User$1.compare(User.java:395) at java.util.TimSort.countRunAndMakeAscending(TimSort.java:324) at java.util.TimSort.sort(TimSort.java:189) at java.util.TimSort.sort(TimSort.java:173) at java.util.Arrays.sort(Arrays.java:659) at java.util.Collections.sort(Collections.java:217) at hudson.model.User.getAll(User.java:395) at hudson.model.User$FullNameIdResolver.resolveCanonicalId(User.java:735) at hudson.model.User.get(User.java:326) at hudson.model.User.get(User.java:299) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:271) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:325) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:455) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1554) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:291) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:277) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:325) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:455) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1554) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:291) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:277) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:325) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:455) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1554) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:291) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:277) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:325) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:455) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1554) at hudson.model.User.getProjects(User.java:448) at
[JIRA] (JENKINS-16848) Error when upgrading from version 1500
Sergey Grigoriev closed JENKINS-16848 as Cannot Reproduce Error when upgrading from version 1500 Change By: Sergey Grigoriev (17/Feb/13 5:23 PM) 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-16848) Error when upgrading from version 1500
Sergey Grigoriev resolved JENKINS-16848 as Cannot Reproduce Error when upgrading from version 1500 Now the issue has gone Change By: Sergey Grigoriev (17/Feb/13 5:23 PM) Status: Open Resolved Resolution: CannotReproduce 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-16850) allow multiple Build other projects actions
Peter Eisentraut created JENKINS-16850 allow multiple Build other projects actions Issue Type: Improvement Assignee: Unassigned Components: postbuild-task Created: 17/Feb/13 7:27 PM Description: I would like to trigger some downstream builds only when the current job is stable and some other builds even when the current job is unstable. (Example: Build documentation even if tests fail, but don't run extra test suite when the tests of the current job fail.) Currently, you can only select one behavior or the other, and you cannot create two separate "Build other projects" actions. Project: Jenkins Priority: Major Reporter: Peter Eisentraut 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Sami Salonen
updated JENKINS-16844
Triggering a build from the context menu produces a warning when security is enabled
Change By:
Sami Salonen
(17/Feb/13 9:56 PM)
Summary:
Triggeringabuildfromthecontextmenuproducesawarning
whensecurityisenabled
Description:
Hoveringmouseoverajobnamebringsupacontextmenu.Clicking
BuildNow
_BuildNow_
fromthecontextmenuproducesthefollowingwarninganda
Proceed
_Proceed_
button.Buildstartsonlyif
Proceed
_Proceed_
buttonispressed.Contextmenuisaccessibleatleastinjoblistview(e.g.default
All
_All_
view)andfromthebreadcrumb.Clicking
BuildNow
_BuildNow_
ontheleftmenuonajobpageworksnormally
,i
.
e.withoutwarnings.
{{YoumustusePOSTmethodtotriggerbuilds.(Fromscriptsyoumayinsteadpassaper-projectauthenticationtoken,orauthenticatewithyourAPItoken.)Ifyouseethispage,itmaybebecauseapluginofferedaGETlink;fileabugreportforthatplugin.}}
Component/s:
core
Component/s:
security
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-16844) Triggering a build from the context menu produces a warning when security is enabled
Sami Salonen edited a comment on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Steps to reproduce: Start Jenkins (java -jar jenkins.war) Create a free-style project (just give a name, default configuration is fine) Trigger a build from a context menu. Works fine. Add directory server based authentication: Click Enable security in global configuration From Access Control section, select LDAP under Security Realm Fill in Server, root DN, User search base, User search filter, Group search base, Manager DN, Manager Password (For Authorization, I tried both Anyone can do anything and Matrix-based security with same effect) Trigger a build from a context menu. Warning message is displayed. 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-16847) Support for copying artifacts from other builds being part of the same MultiJob (previous phases)
Alan Harder assigned JENKINS-16847 to Unassigned Support for copying artifacts from other builds being part of the same MultiJob (previous phases) Please ask on the dev alias for someone to accept the pull request, or to get access so you can submit it yourself, thanks! Change By: Alan Harder (17/Feb/13 10:08 PM) Assignee: AlanHarder 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-13218) Can't add build step on current jenkins with manual installed buckminster 3.7
Lorenzo Bettini assigned JENKINS-13218 to Lorenzo Bettini Cant add build step on current jenkins with manual installed buckminster 3.7 Change By: Lorenzo Bettini (18/Feb/13 7:05 AM) Assignee: jutzig LorenzoBettini 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-13218) Can't add build step on current jenkins with manual installed buckminster 3.7
Lorenzo Bettini resolved JENKINS-13218 as Fixed Cant add build step on current jenkins with manual installed buckminster 3.7 This is fixed in version 1.1.1 Change By: Lorenzo Bettini (18/Feb/13 7:06 AM) Status: Open Resolved Fix Version/s: current 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-16844) Triggering a build from the context menu produces a warning when security is enabled
Sami Salonen updated JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Change By: Sami Salonen (18/Feb/13 7:27 AM) Component/s: gui 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-16851) Strategy GerritTrigger missing with plugin 1.1.28
Björn Pedersen created JENKINS-16851 Strategy GerritTrigger missing with plugin 1.1.28 Issue Type: Bug Assignee: rsandell Components: gerrit-trigger, git Created: 18/Feb/13 7:35 AM Description: After upgrading to git plugin 1.1.28 the GerritTrigger strategy is not available anymore, all gerrit trigger jobs fail. Project: Jenkins Priority: Critical Reporter: Björn Pedersen 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-16851) Strategy GerritTrigger missing with plugin 1.1.28
Björn Pedersen commented on JENKINS-16851 Strategy GerritTrigger missing with plugin 1.1.28 Changes in the BuildChooserDeafault/Inverse in git plugin: -import hudson.plugins.git.IGitAPI; +import hudson.plugins.git.client.IGitAPI; 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-16852) Promote on artifact download
Jakob Malm created JENKINS-16852 Promote on artifact download Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: promoted-builds Created: 18/Feb/13 7:45 AM Description: I would like to be able to start a promotion of a build when a user downloads any of its artifacts (i.e. through HTTP). With a large number of builds which are never really used by anyone, builds where a user actually downloads an artifact are special, and I would like to handle them differently (e.g. copy artifacts somewhere else). The feature should not start a promotion when some other build uses the Copy Artifact plugin. (If that plugin gets artifacts via HTTP, this could be a problem.) Project: Jenkins Priority: Minor Reporter: Jakob Malm 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.
