[JIRA] (JENKINS-15952) Checkstyle project wont transfer all files from slave to master
Ulli Hafner commented on JENKINS-15952 Checkstyle project wont transfer all files from slave to master The workaround will not help to get the files correctly transmitted It only shows the exception as text in the file to see what actually is going wrong (typically a wrong filename). 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-16821) In Maven2 Jobs, parse POMs after successful build on some circumstances
Emilio Jose Mena Cebrian created JENKINS-16821 In Maven2 Jobs, parse POMs after successful build on some circumstances Issue Type: Improvement Assignee: Unassigned Components: maven2 Created: 15/Feb/13 8:42 AM Description: Add the possibility of parsing the poms after a successful build to reflect POMs' changes during the build. So plugins like M2 Release plugin migth take advantage of this and update Maven Versions (of dependencies and artifacts) for the next build Project: Jenkins Priority: Minor Reporter: Emilio Jose Mena Cebrian 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-14959) Proposed version number is not up-to-date when only releasing
Emilio Jose Mena Cebrian commented on JENKINS-14959 Proposed version number is not up-to-date when only releasing I suspect that the versions aren't the only information outdated. Maybe module dependencies should be updated as well after a successful build if the release task changes the pom in order to fix SNAPSHOTS versions (using the "prepare-with-pom" goal) Is it possible to reparse poms after releasing the version. I've seen MavenModuleSetBuildExecution.parsePoms method, but it isn't public. 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-14959) Proposed version number is not up-to-date when only releasing
Emilio Jose Mena Cebrian edited a comment on JENKINS-14959 Proposed version number is not up-to-date when only releasing I suspect that the versions aren't the only outdated information . Maybe module dependencies should be updated as well after a successful build if the release task changes the pom in order to fix SNAPSHOTS versions (using the "prepare-with-pom" goal) Is it possible to reparse poms after releasing the version. I've seen MavenModuleSetBuildExecution.parsePoms method, but it isn't public. 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-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
Zoltán Buza commented on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. I have created a pull request which fixes this issue: https://github.com/jenkinsci/jenkins/pull/709 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-16801) Claim Report don't list all jobs when Default View is set in Jenkins
Christian Åkerström commented on JENKINS-16801 Claim Report don't list all jobs when Default View is set in Jenkins That it only shows the jobs for the "Default view" would also be a feature for some users. I am thinking about making it configurable which view the claim report shows it information from. For your use case you would have to configure a view that lists all jobs and choose that view as your "Claim view". Is that an acceptable solution for 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-15965) Currently building links point to wrong downstream projects when concurent builds are active
Asmund olsen commented on JENKINS-15965 Currently building links point to wrong downstream projects when concurent builds are active looking at the fix I would believe that all use of project.getLastBuild() should be removed. Think of the case where project is accepts concurrent builds. Then last build may very well be wrong. I still do not understand this fully I may very well be wrong. 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-16822) Support for different scale values - our case 8273
Jes Struck created JENKINS-16822 Support for different scale values - our case 8273 Issue Type: New Feature Assignee: Praqma Support Components: memory-map Created: 15/Feb/13 9:51 AM Description: It should be possible to choose between kilo, Mega & Giga Bytes and Words in the grapg Due Date: 15/Feb/13 12:00 AM Environment: all Project: Jenkins Priority: Major Reporter: Jes Struck 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-12803) Installing plugin (without restarting) is broken with other non-refreshable extension.
Gavriil Konovalenko commented on JENKINS-12803 Installing plugin (without restarting) is broken with other non-refreshable extension. Hi evernat, A year has passed, but as I remember the issue – is that I'd try to install other plugin not this. And installation process failed due to non-refreshable extension was activated. So I expect that installation of one plugin shouldn't be affected with other extension. 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-16809) Plugins FSTrigger/Envinject, NPE while loading jobs
Riccardo Gorza commented on JENKINS-16809 Plugins FSTrigger/Envinject, NPE while loading jobs Thanks! Where can I find the 0.35 release? It's not showing up in the Jenkins updates list, nor here http://updates.jenkins-ci.org/download/plugins/fstrigger/ 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-16823) Successful even when it fails to delete files
wernight created JENKINS-16823 Successful even when it fails to delete files Issue Type: Bug Assignee: vjuranek Components: ws-cleanup Created: 15/Feb/13 10:57 AM Description: 1. Keep a file open (e.g., a zip) 2. Run clean workspace Expecting: Cannot delete file x.zip log message Build failure I'd hope there would be one or two retry after a few seconds (some coporate anti-virus, Symantec, like have a tendency to keep files open). Project: Jenkins Priority: Critical Reporter: wernight 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-16824) Builds aborting randomly
Ari Hyttinen created JENKINS-16824 Builds aborting randomly Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 15/Feb/13 11:04 AM Description: The issue has been discussed at user mailing list last summer: https://groups.google.com/forum/#!msg/jenkinsci-users/GN0N4mqaCa4/kPbSal5xc4YJ We started having this issue last week, in a system with one job named "thejob", and about 50 slaves, many of them executing it in parallel at any given time. This seems to happen very randomly, usually in the time-consuming part of the build: running an executable on the slave, in which case stack trace is like this: 12.2.2013 6:34:32 hudson.model.Run run INFO: thejob #443821 aborted java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:127) at hudson.remoting.Channel.call(Channel.java:646) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy33.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:861) at hudson.Proc.joinWithTimeout(Proc.java:168) ... N more This started to happen seemingly without any other cause except increasing load and slave count. Updating to 1.482.2. did not seem to have any effect. Jenkins master as well as slaves are running Windows, but that user mailing list thread suggests that this can happen on Linux too. We have not been able to identify anything special which might trigger this, but since it does not happen in small scale test setup, only in production, this complicates investigation. We tried -Xrs parameter for JVM, as suggested in that thread, and it seems to have reduced this, but has not stopped it completely. Environment: Master: Windows Server 2008 R2, Java 1.6.0_31, Java HotSpot(TM) 64-Bit Server VM. Slaves with diffrent OS versions, slave.jar running as service. Project: Jenkins Priority: Major Reporter: Ari Hyttinen 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-16825) Move graph labels for memory section of same size sideways - our case 8622
Jes Struck created JENKINS-16825 Move graph labels for memory section of same size sideways - our case 8622 Issue Type: New Feature Assignee: Praqma Support Attachments: Screenshot-787.png Components: memory-map Created: 15/Feb/13 11:14 AM Description: The easy way to solve this would be to check the max values, and see if there are 2 values which are identical, instead of drawing a marker for each, draw on marker, and concatanate the label for those two into on string, ie. "RAM1 & RAM2" for the label. Wouldn't solve the case where the sizes are so close they almost overlap. It also okay, not to handle, the issues with max values that are so close above each other that the labels overlap. Due Date: 15/Feb/13 12:00 AM Environment: Project: Jenkins Priority: Major Reporter: Jes Struck 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-16823) Successful even when it fails to delete files
wernight
commented on JENKINS-16823
Successful even when it fails to delete files
I saw the plugin uses ws.deleteContents() in PreBuildCleanup (I did a pre-build clean-up) which should be equivalent to:
new FilePath(new File('D:\\Jenkins\\workspace\\test')).deleteContents();
I'm not sure why this one doesn't use deleteRecursive() by default like the post-build clean-up. Running that command in Groovy throws a java.io.IOException which it should. It seems that the catching of the exception doesn't actually print anything in the log:
} catch (IOException e) {
Logger.getLogger(PreBuildCleanup.class.getName()).log(Level.SEVERE, null, e);
e.printStackTrace();
} ...
Possibly it should throw a AbortException and log properly the error.
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-16801) Claim Report don't list all jobs when Default View is set in Jenkins
Markus Hjerto commented on JENKINS-16801 Claim Report don't list all jobs when Default View is set in Jenkins I agree. And your proposed solution is acceptable. (Although "acceptable" and "not acceptable" is a bit strong for a plugin I/we use for free...) There is already a view called "All" so I can simply select that view and then the plugin works as I expected. I've noticed that the "Wall Display" plugin uses another approach: It uses the view you have active when you click "Wall Display" in the menu to the left. Although I did not find that approach very intuitive at first, it could be that this is the recommended approach in the Jenkins UI. 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-16824) Builds aborting randomly
Ari Hyttinen
updated JENKINS-16824
Builds aborting randomly
Fixed stack trace to show line numbers of correct version of Jenkins core, and added link to github.
Change By:
Ari Hyttinen
(15/Feb/13 12:29 PM)
Description:
The issue has been discussed at user mailing list last summer:https://groups.google.com/forum/#!msg/jenkinsci-users/GN0N4mqaCa4/kPbSal5xc4YJWe started having this issue last week, in a system with one job named "thejob", and about 50 slaves, many of them executing it in parallel at any given time. This seems to happen very randomly, usually in the time-consuming part of the build: running an executable on the slave, in which case stack trace is like this:{quote}12.2.2013 6:34:32 hudson.model.Run runINFO: thejob #443821 abortedjava.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:
127
146
) at hudson.remoting.Channel.call(Channel.java:
646
664
) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $
Proxy33
Proxy39
.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:861) at hudson.Proc.joinWithTimeout(Proc.java:168) ... N more{quote}
Link to source code of the wait getting interrupted in correct version of slave.jar: https://github.com/jenkinsci/remoting/blob/remoting-2.17/src/main/java/hudson/remoting/Request.java#L146
This started to happen seemingly without any other cause except increasing load and slave count. Updating to 1.482.2. did not seem to have any effect. Jenkins master as well as slaves are running Windows, but that user mailing list thread suggests that this can happen on Linux too. We have not been able to identify anything special which might trigger this, but since it does not happen in small scale test setup, only in production, this complicates investigation.We tried -Xrs parameter for JVM, as suggested in that thread, and it seems to have reduced this, but has not stopped it completely.
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-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Tomas Westling commented on JENKINS-15948 Analyzer Icons aren't displayed if Jenkins isn't installed at root context. Fixed in 6d05f69d02f6e3dae3c1e71dcb7afa44ecafe760 and 46e033dcedd3caf8b24b333f200f2aa59815fcca Released in 1.4.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-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Tomas Westling resolved JENKINS-15948 as Fixed Analyzer Icons aren't displayed if Jenkins isn't installed at root context. Released in 1.4.0 Change By: Tomas Westling (15/Feb/13 12:29 PM) Status: Reopened 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-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Tomas Westling edited a comment on JENKINS-15948 Analyzer Icons aren't displayed if Jenkins isn't installed at root context. Fixed in 6d05f69d02f6e3dae3c1e71dcb7afa44ecafe760 and 46e033dcedd3caf8b24b333f200f2aa59815fcca 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-15926) Build Failure Analyzer with Timestamper output ugly.
Tomas Westling resolved JENKINS-15926 as Fixed Build Failure Analyzer with Timestamper output ugly. Released in 1.4.0 Change By: Tomas Westling (15/Feb/13 12:31 PM) Status: Reopened 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-16596) Repeat/double logging issue due to Build failure Analyzer
Tomas Westling commented on JENKINS-16596 Repeat/double logging issue due to Build failure Analyzer Fixed in fd6d360840afec3cae00b1ded8f7b84b9fcdc295 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-15926) Build Failure Analyzer with Timestamper output ugly.
Tomas Westling commented on JENKINS-15926 Build Failure Analyzer with Timestamper output ugly. Fixed in fd6d360840afec3cae00b1ded8f7b84b9fcdc295 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-16596) Repeat/double logging issue due to Build failure Analyzer
Tomas Westling resolved JENKINS-16596 as Fixed Repeat/double logging issue due to Build failure Analyzer Released in 1.4.0 Change By: Tomas Westling (15/Feb/13 12:32 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-16104) Build Failure Analyzer: Ugly output from plugin
Tomas Westling commented on JENKINS-16104 Build Failure Analyzer: Ugly output from plugin Fixed in fd6d360840afec3cae00b1ded8f7b84b9fcdc295 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-16104) Build Failure Analyzer: Ugly output from plugin
Tomas Westling resolved JENKINS-16104 as Fixed Build Failure Analyzer: Ugly output from plugin Released in 1.4.0 Change By: Tomas Westling (15/Feb/13 12:32 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-16793) badges which appear in the build history, needs to be optional
Stefan Brausch assigned JENKINS-16793 to Kathi Stutz badges which appear in the build history, needs to be optional Change By: Stefan Brausch (15/Feb/13 12:48 PM) Assignee: Mirko Friedenhagen Kathi Stutz 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-16826) Blank Maven warnings
Jan Goyvaerts created JENKINS-16826 Blank Maven warnings Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Attachments: maven_warnings.png Components: warnings Created: 15/Feb/13 1:15 PM Description: The Warnings plugin generates blank Maven warnings. Which is probably not the intended behavior. See the included screenshot. Project: Jenkins Labels: plugin warnings Priority: Minor Reporter: Jan Goyvaerts 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-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Did you try both TLS and non-TLS? Also, can you enable debug mode in the email-ext plugin and debug mode in the JavaMail API (see http://www.oracle.com/technetwork/java/faq-135477.html#debug)? 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-8597) Deal with matrix builds better
Sven Appenrodt
edited a comment on JENKINS-8597
Deal with matrix builds better
I agree. Nice idea to sort the prio of jobs but we're handling with many axis-jobs which can run on a slave too, so reducing their prio will improve our builds because the slave will be used better.
To fix the problem the code has to be fixed in the following way.
In PrioritySorterQueue.java the method getPriority has to be changed
from:
[..]
AbstractProject project = (AbstractProject) buildable.task;
priority = project.getProperty(PrioritySorterJobProperty.class);
[..]
to:
[..]
AbstractProject project = (AbstractProject) buildable.task;
PrioritySorterJobProperty priority = null;
if (project instanceof MatrixConfiguration) {
ItemGroup parent = project.getParent();
if (parent instanceof AbstractProject){
priority = ((AbstractProject)(parent)).getProperty(PrioritySorterJobProperty.class);
}
} else {
priority = project.getProperty(PrioritySorterJobProperty.class);
}
[..]
Then the priority from the axises are resolved from the parent matrix because the axis itself does not have the property attached.
According to the higher number -> job starts first - problem the comparitor (same java-file) has to be changed
to:
[..]
public int compare(BuildableItem arg0, BuildableItem arg1) {
// Note that we sort these backwards because we want to return
// higher-numbered items first.
Integer priority1 = getPriority(arg0);
return priority1.compareTo(getPriority(arg1));
}
[..]
then the comment is correct - jobs with higher numbers are started first...
And also the adjusting-method has to be changed to adjustedPriority -= ... but this i've never tested
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-16823) Successful even when it fails to delete files
wernight started work on JENKINS-16823 Successful even when it fails to delete files Change By: wernight (15/Feb/13 1:57 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-16826) Blank Maven warnings
Ulli Hafner commented on JENKINS-16826 Blank Maven warnings Can you please also post a small snippet of your console log? Then I can use it for a small unit test 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-16823) Successful even when it fails to delete files
wernight started work on JENKINS-16823 Successful even when it fails to delete files Change By: wernight (15/Feb/13 1:57 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-16823) Successful even when it fails to delete files
wernight stopped work on JENKINS-16823 Successful even when it fails to delete files Change By: wernight (15/Feb/13 1:57 PM) Status: In Progress Open 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-16823) Successful even when it fails to delete files
wernight assigned JENKINS-16823 to wernight Successful even when it fails to delete files Change By: wernight (15/Feb/13 1:57 PM) Assignee: vjuranek wernight 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-8597) Deal with matrix builds better
Sven Appenrodt
edited a comment on JENKINS-8597
Deal with matrix builds better
I agree. Nice idea to sort the prio of jobs but we're handling with many axis-jobs which can run on a slave too, so reducing their prio will improve our builds because the slave will be used better.
To fix the problem the code has to be fixed in the following way.
In PrioritySorterQueue.java the method getPriority has to be changed
from:
[..]
AbstractProject project = (AbstractProject) buildable.task;
priority = project.getProperty(PrioritySorterJobProperty.class);
[..]
to:
[..]
AbstractProject project = (AbstractProject) buildable.task;
PrioritySorterJobProperty priority = null;
if (project instanceof MatrixConfiguration) {
ItemGroup parent = project.getParent();
if (parent instanceof AbstractProject){
priority = ((AbstractProject)(parent)).getProperty(PrioritySorterJobProperty.class);
}
} else {
priority = project.getProperty(PrioritySorterJobProperty.class);
}
[..]
Then the priority from the axises are resolved from the parent matrix because the axis itself does not have the property attached.
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-16826) Blank Maven warnings
Jan Goyvaerts updated JENKINS-16826 Blank Maven warnings There you are. Change By: Jan Goyvaerts (15/Feb/13 2:16 PM) Attachment: log.txt 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.
jenkins and selenium
Hi,I am pretty new with jenkins. What I would like to do is record some test by selenium IDE and run it via Jenkins. I am trying to do it all day but I am missing something :/Can you advise how it can be done ? do I need some plugin to junkins ?thank you in advance -- View this message in context: http://jenkins.361315.n4.nabble.com/jenkins-and-selenium-tp4655784.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15459) Job waiting for the completion other job that have finished
Jesse Glick commented on JENKINS-15459 Job waiting for the completion other job that have finished Reporter are you actually talking about the Build Flow Plugin as the “component” here indicates, or should it simply be core, i.e. stock Jenkins? 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-16600) NullPointerException Exception in AuthorizationMatrixProperty when saving job config
cforce updated JENKINS-16600 NullPointerException Exception in AuthorizationMatrixProperty when saving job config Change By: cforce (15/Feb/13 2:59 PM) Affects Version/s: current Environment: Jenkins 1. 5 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-16823) Successful even when it fails to delete files
wernight resolved JENKINS-16823 as Fixed Successful even when it fails to delete files I've sent a GitHub pull request with two patches. One to fix this issue, one that retries 3 times to delete at 3 seconds interval. The second one has only been applied to the pre-build yet. I'd suggest to refactor so that pre-build and post-build use the same class to do the actual job. Change By: wernight (15/Feb/13 3:06 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-14803) Better implementation of -noreconnect jnlp slaves
KK Kon commented on JENKINS-14803 Better implementation of -noreconnect jnlp slaves made implementation and sended pull request. https://github.com/jenkinsci/remoting/pull/11 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-16827) console display wrong build number when triggering a new build
Louis Roché created JENKINS-16827 console display wrong build number when triggering a new build Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: downstreambuildview.png Components: core Created: 15/Feb/13 3:23 PM Description: I have a build which can trigger another build. In the console, I have at the end of the log: Triggering a new build of Build Hoops 3DX 5_x Windows Samples #1758 Triggering a new build of Supervisor Test Windows Continuous #2831 But I have not the same informations in Downstream build view. The good informations are in the Downstream build view. Environment: Jenkins server on windows 7 64. Slaves on windows 7 32/64. Project: Jenkins Priority: Major Reporter: Louis Roché 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-14840) default graph values are not saved
SCM/JIRA link daemon commented on JENKINS-14840 default graph values are not saved Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/graph/DefaultGraphConfigurationView.java http://jenkins-ci.org/commit/analysis-core-plugin/235e180bca2a951c4914fc9791c75f8844bf1e83 Log: [FIXED JENKINS-14840] Use correct filename when saving graph config. 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-12342) [Compiler Warnings plugin] Compiler Warnings Trend not showing failed build results
SCM/JIRA link daemon resolved JENKINS-12342 as Fixed [Compiler Warnings plugin] Compiler Warnings Trend not showing failed build results Change By: SCM/JIRA link daemon (15/Feb/13 3:52 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-16826) Blank Maven warnings
SCM/JIRA link daemon resolved JENKINS-16826 as Fixed Blank Maven warnings Change By: SCM/JIRA link daemon (15/Feb/13 3:52 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-12342) [Compiler Warnings plugin] Compiler Warnings Trend not showing failed build results
SCM/JIRA link daemon commented on JENKINS-12342 [Compiler Warnings plugin] Compiler Warnings Trend not showing failed build results Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/BuildHistory.java src/test/java/hudson/plugins/analysis/core/BuildHistoryTest.java http://jenkins-ci.org/commit/analysis-core-plugin/e7ce3bc5e1c6c3b761c22fd5e240b46cf7ede41a Log: [FIXED JENKINS-12342] Show results of failed builds if the plugin caused the failure. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/b506c418b4b3...e7ce3bc5e1c6 – 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-14840) default graph values are not saved
SCM/JIRA link daemon resolved JENKINS-14840 as Fixed default graph values are not saved Change By: SCM/JIRA link daemon (15/Feb/13 3:52 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-16826) Blank Maven warnings
SCM/JIRA link daemon commented on JENKINS-16826 Blank Maven warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/MavenConsoleParser.java src/test/java/hudson/plugins/warnings/parser/MavenConsoleParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue16826.txt http://jenkins-ci.org/commit/warnings-plugin/cf89edc0fdc1c87be157f718a4b265d0045bda67 Log: [FIXED JENKINS-16826] remove blank warnings. Compare: https://github.com/jenkinsci/warnings-plugin/compare/9d7932c5df68...cf89edc0fdc1 – 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-16233) EnvInject plugin using a cached value for ${WORKSPACE}
Dave Hunt
commented on JENKINS-16233
EnvInject plugin using a cached value for ${WORKSPACE}
We have rolled back to version 1.61 and so far have not seen this issue since.
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-16828) NullPointerException in BooleanSlice.get
James Howe created JENKINS-16828 NullPointerException in BooleanSlice.get Issue Type: Bug Assignee: mdonohue Attachments: stacktrace.txt Components: configurationslicing Created: 15/Feb/13 4:07 PM Description: When attempting to slice "Block Build when Downstream/Upstream Building", the attached stack trace appears on submit. Environment: Jenkins 1.501, Configuration Slicing plugin 1.36 Project: Jenkins Priority: Major Reporter: James Howe 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-16829) Inject variable from a Groovy Script stored on filesystem.
Bertrand Latinville created JENKINS-16829 Inject variable from a Groovy Script stored on filesystem. Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 15/Feb/13 4:19 PM Description: In "Prepare an environment for the run" from the Envinject plugin it is possible to evaluate a Groovy Script in each job configuration. To use the same script with multiple jobs and avoid copy/paste between jobs, it would be more efficient to have an option to have groovy scripts stored on file system. The option is available for Script content and Properties file, but not for Groovy script. I 'd need to create new environment variables from values of axis in matrix job and this improvement would be appreciated. Project: Jenkins Priority: Minor Reporter: Bertrand Latinville 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-8818) PMD results history grap wipedout on build failure
Ulli Hafner resolved JENKINS-8818 as Cannot Reproduce PMD results history grap wipedout on build failure Please reopen if that happens again. Change By: Ulli Hafner (15/Feb/13 4:55 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-7178) Hudson Warning Plugin crash, java.lang.StackOverflowError
Ulli Hafner commented on JENKINS-7178 Hudson Warning Plugin crash, java.lang.StackOverflowError Ok, thanks for checking. I think the doxygen parser needs to be re-written in order to avoid that JDK bug. 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-12058) Failed to get revision check failed after updating to latest Subversion plugin
teilo commented on JENKINS-12058 Failed to get revision check failed after updating to latest Subversion plugin I believe this may be fixed in Subversion plugin 1.45 by the use of the updated SVNKit library. It could be that the downgrade of the plugin wasn't the fix for you but the restart of jenkins that the downgrade needed. (we hit an almost identical stack traces every time the svn server was rebooted - and restarting Jenkins always made it go away until the next 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.
Re: jenkins and selenium
I have no idea how to help you, but I have to say, that is the best typo ever! I'm giggling on my way to work, thank you! -Senthil Sent from my Verizon Wireless Sony Ericsson Xperia™ PLAY. driver wrote: >Hi,I am pretty new with jenkins. What I would like to do is record some test >by selenium IDE and run it via Jenkins. I am trying to do it all day but I >am missing something :/Can you advise how it can be done ? do I need some >plugin to junkins ?thank you in advance > > > >-- >View this message in context: >http://jenkins.361315.n4.nabble.com/jenkins-and-selenium-tp4655784.html >Sent from the Jenkins issues mailing list archive at Nabble.com. > >-- >You received this message because you are subscribed to the Google Groups >"Jenkins Issues" group. >To unsubscribe from this 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. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16802) Using Apache proxysettings breaks several GUI functions
Jesse Glick commented on JENKINS-16802 Using Apache proxysettings breaks several GUI functions Did you set the externally visible Jenkins URL in the /configure screen? 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-16830) RunnerAbortedException no longer workin in RunListener.onStartup()
Max Spring created JENKINS-16830 RunnerAbortedException no longer workin in RunListener.onStartup() Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 15/Feb/13 6:09 PM Description: Trying to abourt a build by throwing Run.RunnerAbortedException() in a RunListener.onStarted(). This used to work in older version 1.466. Use case: I want to enforce certain conventions in all the jobs. If a job doesn't follow the convention, it will always fail. This gives job owners a natural incentive to adhere to the convention. RunListener.fireStarted() seems to eat any exception (by just reporting it): https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/listeners/RunListener.java#L198 Run.execute() never sees the exception: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Run.java#L1574 Seems like a bug to me. RunListener.fireStarted() should somehow rethrow these exceptions. Environment: Linux Project: Jenkins Priority: Critical Reporter: Max Spring 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-16815) UpdateSite.updateDirectly fails to specify ID and version
SCM/JIRA link daemon commented on JENKINS-16815 UpdateSite.updateDirectly fails to specify ID and version Code changed in jenkins User: Ryan Campbell Path: core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/7fdd27f7bd83a8323e07df304bb4722116d852ff Log: JENKINS-16815 Specify ID and version in UpdateSite.updateDirectly 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-16815) UpdateSite.updateDirectly fails to specify ID and version
SCM/JIRA link daemon commented on JENKINS-16815 UpdateSite.updateDirectly fails to specify ID and version Code changed in jenkins User: Nicolas De loof Path: core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/cfd629d86682a38feb80c2feac8fcdec130b1df0 Log: Merge pull request #710 from recampbell/update-site-parameters JENKINS-16815 Specify ID and version in UpdateSite.updateDirectly Compare: https://github.com/jenkinsci/jenkins/compare/6270556267ce...cfd629d86682 – 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-16831) BuildHistoryWidget.getQueuedItems can block HTTP thread
Jesse Glick created JENKINS-16831 BuildHistoryWidget.getQueuedItems can block HTTP thread Issue Type: Bug Assignee: Jesse Glick Components: core Created: 15/Feb/13 6:57 PM Description: "Handling POST /job/.../buildHistory/ajax : ... java.lang.Thread.State: BLOCKED (on object monitor) at hudson.model.Queue.getItems(Queue.java:723) - waiting to lock <0xc11cf910> (a hudson.model.Queue) at hudson.widgets.BuildHistoryWidget.getQueuedItems(BuildHistoryWidget.java:63) at sun.reflect.GeneratedMethodAccessor335.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at hudson.widgets.HistoryWidget.doAjax(HistoryWidget.java:191) Environment: 1.466.x Project: Jenkins Labels: performance Priority: Major Reporter: Jesse Glick
[JIRA] (JENKINS-16832) Do not show failed builds in trend graph
Franta Mejta created JENKINS-16832 Do not show failed builds in trend graph Issue Type: Improvement Assignee: nalin_makar Components: testng Created: 15/Feb/13 7:13 PM Description: Do not show failed (and aborted) builds in trend graph or make it an option. It is likely that failed build did not run all tests hence the graph could be misleading. This does not mean the results should not be collected and available in individual builds. Project: Jenkins Priority: Major Reporter: Franta Mejta 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-16831) BuildHistoryWidget.getQueuedItems can block HTTP thread
Jesse Glick commented on JENKINS-16831 BuildHistoryWidget.getQueuedItems can block HTTP thread https://github.com/jenkinsci/jenkins/pull/711 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-16831) BuildHistoryWidget.getQueuedItems can block HTTP thread
Jesse Glick started work on JENKINS-16831 BuildHistoryWidget.getQueuedItems can block HTTP thread Change By: Jesse Glick (15/Feb/13 7:21 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-16815) UpdateSite.updateDirectly fails to specify ID and version
dogfood commented on JENKINS-16815 UpdateSite.updateDirectly fails to specify ID and version Integrated in jenkins_main_trunk #2278 JENKINS-16815 Specify ID and version in UpdateSite.updateDirectly (Revision 7fdd27f7bd83a8323e07df304bb4722116d852ff) Result = SUCCESS Ryan Campbell : 7fdd27f7bd83a8323e07df304bb4722116d852ff Files : core/src/main/java/hudson/model/UpdateSite.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-16833) Queue$BlockedItem.getCauseOfBlockage waiting for lock on Queue
Jesse Glick created JENKINS-16833 Queue$BlockedItem.getCauseOfBlockage waiting for lock on Queue Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Feb/13 7:52 PM Description: "Handling POST /job/.../ajaxBuildQueue : ... java.lang.Thread.State: BLOCKED (on object monitor) at hudson.model.ResourceController.getBlockingActivity(ResourceController.java:129) - waiting to lock <0xc11cf910> (a hudson.model.Queue) at hudson.model.Queue$BlockedItem.getCauseOfBlockage(Queue.java:1490) at hudson.model.Queue$Item.getWhy(Queue.java:1309) at sun.reflect.GeneratedMethodAccessor681.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) The cause of blockage is just informational; should not wait for the Queue lock just for this. Environment: 1.466.x Project: Jenkins Labels: performance Priority: Major Reporter: Jesse Glick 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-16830) RunnerAbortedException no longer workin in RunListener.onStartup()
kutzi assigned JENKINS-16830 to Kohsuke Kawaguchi RunnerAbortedException no longer workin in RunListener.onStartup() Change By: kutzi (15/Feb/13 8:07 PM) Assignee: Kohsuke Kawaguchi 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-16830) RunnerAbortedException no longer workin in RunListener.onStartup()
kutzi commented on JENKINS-16830 RunnerAbortedException no longer workin in RunListener.onStartup() Seems to be caused by https://github.com/jenkinsci/jenkins/commit/4942f66a1331b38c87866b156e026756d603d138. But actually I see nothing in RunListener's Javadoc which hints that a RunListener my throw this exception to make the build fail. So I'm not sure it this is a bug or was never supposed to work that way. 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-16830) RunnerAbortedException no longer workin in RunListener.onStartup()
kutzi edited a comment on JENKINS-16830 RunnerAbortedException no longer workin in RunListener.onStartup() Seems to be caused by https://github.com/jenkinsci/jenkins/commit/4942f66a1331b38c87866b156e026756d603d138. But actually I see nothing in RunListener's Javadoc which hints that a RunListener may throw this exception to make the build fail. So I'm not sure it this is a bug or was never supposed to work that way. 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-16833) Queue$BlockedItem.getCauseOfBlockage waiting for lock on Queue
Jesse Glick assigned JENKINS-16833 to Jesse Glick Queue$BlockedItem.getCauseOfBlockage waiting for lock on Queue Change By: Jesse Glick (15/Feb/13 8:14 PM) Assignee: Jesse Glick 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-16833) Queue$BlockedItem.getCauseOfBlockage waiting for lock on Queue
Jesse Glick started work on JENKINS-16833 Queue$BlockedItem.getCauseOfBlockage waiting for lock on Queue Change By: Jesse Glick (15/Feb/13 8:14 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-16833) Queue$BlockedItem.getCauseOfBlockage waiting for lock on Queue
Jesse Glick commented on JENKINS-16833 Queue$BlockedItem.getCauseOfBlockage waiting for lock on Queue It is possible that a fix of JENKINS-16831 would resolve this, since it appeared to be the call to Queue.getItems which was holding the lock for too long. Nonetheless it would be better to avoid even trying to acquire this monitor from an HTTP thread, so: pull #712 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-16809) Plugins FSTrigger/Envinject, NPE while loading jobs
Gregory Boissinot commented on JENKINS-16809 Plugins FSTrigger/Envinject, NPE while loading jobs I'm sorry there was an issue on the release process. For now, it is OK. You can download it manually at the following URL http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/fstrigger/0.35/fstrigger-0.35.hpi 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-16233) EnvInject plugin using a cached value for ${WORKSPACE}
Gregory Boissinot
commented on JENKINS-16233
EnvInject plugin using a cached value for ${WORKSPACE}
Is it possible for you to reproduce the problem within the last version in an isolated environment?
Thanks in advance.
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-12803) Installing plugin (without restarting) is broken with other non-refreshable extension.
evernat commented on JENKINS-12803 Installing plugin (without restarting) is broken with other non-refreshable extension. I understand your point of view now. It makes sense. But I think that the best solution is that this Persona plugin just upgrades its parent Jenkins dependency. And so that a "refresh()" method is added in hudson.plugins.persona.xml.XmlPersonaFinder It would make it compatible with installing a plugin without restarting. Anyway, this issue is probably valid and needs to be fixed one way or the other. (But I am not the author of the persona 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-12803) Installing plugin (without restarting) is broken with other non-refreshable extension.
evernat updated JENKINS-12803 Installing plugin (without restarting) is broken with other non-refreshable extension. Change By: evernat (15/Feb/13 9:12 PM) Component/s: persona 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
Gregory Boissinot commented on JENKINS-12832 check XSLT is not good enough Thanks Michael for your comment. Please could make a new issue with all XSLs and some 'Check' result reports. 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-12817) URL pointing to the workspace of a job is not working with a custom "Workspace Root Directory"
evernat resolved JENKINS-12817 as Cannot Reproduce URL pointing to the workspace of a job is not working with a custom "Workspace Root Directory" Change By: evernat (15/Feb/13 9:31 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-12817) URL pointing to the workspace of a job is not working with a custom "Workspace Root Directory"
evernat commented on JENKINS-12817 URL pointing to the workspace of a job is not working with a custom "Workspace Root Directory" After changing the custom "Workspace Root Directory" the link to the workspace does not work yet and it says to run a build. If you run that build, the link to the (custom) workspace works. (Jenkins v1.501 here) So resolving as "can not 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-12818) Fix Linux mouse paste in the description fields
evernat commented on JENKINS-12818 Fix Linux mouse paste in the description fields Is it reproduced with a recent Jenkins version? 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-16830) RunnerAbortedException no longer workin in RunListener.onStartup()
Max Spring commented on JENKINS-16830 RunnerAbortedException no longer workin in RunListener.onStartup() Yes, it looks like this commit did indeed introduce the behavior I'm complaining about. Run.RunnerAbortedException is a RuntimeException, that's why it's not declared. Run.execute() does handle Run.RunnerAbortedException which is some indication that this was actually supposed to be that way. https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Run.java#L1578 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-12133) need to use redeploy, or force deploy for glassfish
Leandro Freitas started work on JENKINS-12133 need to use redeploy, or force deploy for glassfish Change By: Leandro Freitas (15/Feb/13 10:01 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-12133) need to use redeploy, or force deploy for glassfish
Leandro Freitas resolved JENKINS-12133 as Fixed need to use redeploy, or force deploy for glassfish Adjustments to work with EAR files, and fix the problem – force. Upgrade 1.3.3 Change for LTS: org.jenkins-ci.plugins plugin 1.480 Is working perfectly. Change By: Leandro Freitas (15/Feb/13 10:02 PM) Status: In Progress Resolved Assignee: Leandro Freitas 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-15705) Redeploy of .ear files on glassfish don't work.
Leandro Freitas resolved JENKINS-15705 as Fixed Redeploy of .ear files on glassfish don't work. Resolved the issue JENKINS-12133. Change By: Leandro Freitas (15/Feb/13 10:04 PM) Status: In Progress Resolved Assignee: Leandro Freitas 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-15705) Redeploy of .ear files on glassfish don't work.
Leandro Freitas started work on JENKINS-15705 Redeploy of .ear files on glassfish don't work. Change By: Leandro Freitas (15/Feb/13 10:04 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-2443) Add glassfish support
Leandro Freitas resolved JENKINS-2443 as Fixed Add glassfish support Support exists in the current version. Change By: Leandro Freitas (15/Feb/13 10:09 PM) Status: Open Resolved Assignee: david_calavera 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-16772) NullPointerException in Postbuild action for matrix child
SCM/JIRA link daemon commented on JENKINS-16772 NullPointerException in Postbuild action for matrix child Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/postbuildscript/PostBuildScriptListener.java http://jenkins-ci.org/commit/postbuildscript-plugin/735c66001f7e890c29c62b270a2ceb66432df070 Log: Check publishers null for JENKINS-16772 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-9093) Deploy: Allow specification of Context Path
Leandro Freitas updated JENKINS-9093 Deploy: Allow specification of Context Path Change By: Leandro Freitas (15/Feb/13 10:13 PM) Status: Reopened Open 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-16772) NullPointerException in Postbuild action for matrix child
Gregory Boissinot commented on JENKINS-16772 NullPointerException in Postbuild action for matrix child I can't reproduce the issue. Please could you try to isolate the issue and send me your config.xml or a complete zip file. Waiting for it, I add a check to avoid NullPointerException. 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-9093) Deploy: Allow specification of Context Path
Leandro Freitas resolved JENKINS-9093 as Fixed Deploy: Allow specification of Context Path Solution for context already exists in the current version. Change By: Leandro Freitas (15/Feb/13 10:13 PM) Status: Open Resolved Assignee: Leandro Freitas 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-12808) cobertura-maven-plugin: cannot be deactivated + fails with NullPointerException + version 2.5.1 cannot be overwritten
evernat commented on JENKINS-12808 cobertura-maven-plugin: cannot be deactivated + fails with NullPointerException + version 2.5.1 cannot be overwritten Is it reproduced with a recent Jenkins version? 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] (TEST-35) Test Issue
Michael Clarke created TEST-35 Test Issue Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: test1 Created: 15/Feb/13 11:00 PM Project: test Priority: Major Reporter: Michael Clarke 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-16830) RunnerAbortedException no longer workin in RunListener.onStartup()
kutzi commented on JENKINS-16830 RunnerAbortedException no longer workin in RunListener.onStartup() Even RuntimeExceptions can be mentioned in Javadoc. IMHO they even should be mentioned in a case like you expect it - i.e. that throwing a RunnerAbortedException from RunListener will abort the build. In fact, the only usecase mentioned in RunListener is producing log messages which is a pure 'consuming' use case which is very different from a 'vetoing' usecase like you seem to expect. Note that I'm not generally saying that what you expect from RunListener is false. It's just that I can't see it in the interface as it is documented currently. 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-16830) RunnerAbortedException no longer workin in RunListener.onStartup()
kutzi commented on JENKINS-16830 RunnerAbortedException no longer workin in RunListener.onStartup() BTW: and just because Run#execute catches RunnerAbortedException doesn't mean that RunListener is allowed to throw them. There are dozen other places in Run#execute which could throw it. 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] (TEST-35) Test Issue
Michael Clarke commented on TEST-35 Test Issue The following fixes have been included in jenkins-1.500 for this issue:n * Merge pull request #660 from larshvile/mastern n[FIXED JENKINS-16215] Avoiding unnecessary downloads in FilePath.installIfNecessaryFrom\\nnThe following changes have also been included in jenkins-1.500 for this issuen * JENKINS-16215 Avoiding unnecessary downloads in FilePath.installIfNecessaryFrom.n n The updated version uses the locally cached timestamp, '.timestamp', to set then 'If-Modified-Since' header. 304 Not Modified responses are dealt with byn aborting the installation. * JENKINS-16215 : changelog 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] (TEST-35) Test Issue
Michael Clarke
commented on TEST-35
Test Issue
The following fixes have been included in jenkins-1.500 for this issue:n * Merge pull request #660 from larshvile/master
[FIXED JENKINS-16215] Avoiding unnecessary downloads in FilePath.installIfNecessaryFromUnknown macro: {/quote} \\nnThe following changes have also been included in jenkins-1.500 for this issuen * JENKINS-16215 Avoiding unnecessary downloads in FilePath.installIfNecessaryFrom.
The updated version uses the locally cached timestamp, '.timestamp', to set the
'If-Modified-Since' header. 304 Not Modified responses are dealt with by
aborting the installation.{/quote} * JENKINS-16215 : changelog{/quote}
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] (TEST-35) Test Issue
Michael Clarke
commented on TEST-35
Test Issue
The following fixes have been included in jenkins-1.500 for this issue:
Merge pull request #660 from larshvile/master
[FIXED JENKINS-16215] Avoiding unnecessary downloads in FilePath.installIfNecessaryFromUnknown macro: {/quote}
The following changes have also been included in jenkins-1.500 for this issue:
JENKINS-16215 Avoiding unnecessary downloads in FilePath.installIfNecessaryFrom.
The updated version uses the locally cached timestamp, '.timestamp', to set the
'If-Modified-Since' header. 304 Not Modified responses are dealt with by
aborting the installation.{/quote}
* JENKINS-16215 : changelog{/quote}
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] (TEST-35) Test Issue
Michael Clarke commented on TEST-35 Test Issue The following fixes for this issue have been included in jenkins-1.500: Merge pull request #660 from larshvile/master [FIXED JENKINS-16215] Avoiding unnecessary downloads in FilePath.installIfNecessaryFrom The following changes for this issue have also been included in jenkins-1.500: JENKINS-16215 Avoiding unnecessary downloads in FilePath.installIfNecessaryFrom. The updated version uses the locally cached timestamp, '.timestamp', to set the 'If-Modified-Since' header. 304 Not Modified responses are dealt with by aborting the installation. JENKINS-16215 : changelog 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] (TEST-35) Test Issue
Michael Clarke edited a comment on TEST-35 Test Issue Comment deleted * 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] (TEST-35) Test Issue
Michael Clarke edited a comment on TEST-35 Test Issue Comment deleted * 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] (TEST-35) Test Issue
Michael Clarke edited a comment on TEST-35 Test Issue Comment deleted * 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.
