[JIRA] [core] (JENKINS-7844) A Filter to sort jobs by last run time.
Vlad Aginsky commented on JENKINS-7844 A Filter to sort jobs by last run time. Hi, I see it useful as well. Please make it happen. 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] [core] (JENKINS-14405) When 'Discard old builds' is specified using 'Max # of builds to keep' in matrix job - all job history is deleted on master together with folder for the last label used
Eyal Edri commented on JENKINS-14405 When Discard old builds is specified using Max # of builds to keep in matrix job - all job history is deleted on master together with folder for the last label used in the job happens to me too on version 1.501 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] [managed-scripts] (JENKINS-17766) Support git(scm) revision control for managed files
Brian Aker created JENKINS-17766 Support git(scm) revision control for managed files Issue Type: Bug Assignee: domi Components: managed-scripts Created: 28/Apr/13 9:06 AM Description: This is a feature request. Make managed files pull from a git repository (or just build the repository into the plugin). Project: Jenkins Priority: Trivial Reporter: Brian Aker 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] [cobertura] (JENKINS-10532) Cobertura plugin should allow publishing the html version (more detailed than the xml) of the coverage reports
sogabe resolved JENKINS-10532 as Not A Defect Cobertura plugin should allow publishing the html version (more detailed than the xml) of the coverage reports You can use HTML Publisher plugin. Change By: sogabe (28/Apr/13 11:30 AM) Status: Open Resolved Assignee: stephenconnolly sogabe Resolution: NotADefect 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] [matrix] (JENKINS-7285) Allow the combination filter to accept parameter values
Oliver Gondža commented on JENKINS-7285 Allow the combination filter to accept parameter values Pull request: https://github.com/jenkinsci/jenkins/pull/58 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] [managed-scripts] (JENKINS-17766) Support git(scm) revision control for managed files
domi updated JENKINS-17766 Support git(scm) revision control for managed files Change By: domi (28/Apr/13 4:49 PM) Issue Type: Bug NewFeature 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] [infrastructure] (JENKINS-9494) Configure System hangs with LOADING gray div covering top half of settings
Jan Klass commented on JENKINS-9494 Configure System hangs with LOADING gray div covering top half of settings I have the same issue, however it seems to occure at random. I’m on Win7x64, Jenkins master on a remote Linux, using Firefox. I ssh-tunnel a port to the jenkins master, so I actually access it via localhost. I had the issue months ago when we first set up our system. The issue seemingly got fixed once I set the Jenkins base URL to the one I used. Just now I used Jenkins again, updating it and checking configurations etc, thus/then noticing the seemingly incomplete loading again. The frequency of it occuring seems to depend on the job I try to configure. Repeatedly hitting F5 for refreshing the page it occasionaly loads just fine. The HTTP requests seem to return 200 OK just fine. Just now, on one job configuration page I got the following JS errors: 20:08:07.704 SyntaxError: unterminated regular _expression_ literal @ http://localhost:8081/static/d6e090fb/scripts/yui/datasource/datasource-min.js:12 20:08:07.708 TypeError: YAHOO.util.DataSourceBase is undefined @ http://localhost:8081/static/d6e090fb/scripts/yui/autocomplete/autocomplete-min.js:7 20:08:08.010 TypeError: YAHOO.util.XHRDataSource is not a constructor @ http://localhost:8081/static/d6e090fb/scripts/hudson-behavior.js:1621 20:08:08.886 Use of getAttributeNode() is deprecated. Use getAttribute() instead. @ http://localhost:8081/static/d6e090fb/scripts/yui/button/button-min.js:7 20:08:09.075 TypeError: YAHOO.util.XHRDataSource is not a constructor @ http://localhost:8081/static/d6e090fb/scripts/hudson-behavior.js:663 20:08:12.363 SyntaxError: unterminated regular _expression_ literal @ http://localhost:8081/static/d6e090fb/scripts/yui/datasource/datasource-min.js:12 20:08:12.368 TypeError: YAHOO.util.DataSourceBase is undefined @ http://localhost:8081/static/d6e090fb/scripts/yui/autocomplete/autocomplete-min.js:7 20:08:12.518 SyntaxError: syntax error @ http://localhost:8081/static/d6e090fb/scripts/hudson-behavior.js:2132 20:08:12.522 ReferenceError: crumb is not defined @ http://localhost:8081/job/Symbolstore/configure:8 20:08:12.659 ReferenceError: createSearchBox is not defined @ http://localhost:8081/job/Symbolstore/configure:8 20:08:12.856 ReferenceError: updateBuildHistory is not defined @ http://localhost:8081/job/Symbolstore/configure:67 20:08:14.115 ReferenceError: isInsideRemovable is not defined @ http://localhost:8081/adjuncts/d6e090fb/lib/form/hetero-list/hetero-list.js:7 20:08:14.122 ReferenceError: iota is not defined @ http://localhost:8081/adjuncts/d6e090fb/lib/form/breadcrumb-config-outline/init.js:6 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] [clone-workspace] (JENKINS-6890) clone-workspace-scm doesn't work when source job is a matrix job.
Zaraki Kenpachi commented on JENKINS-6890 clone-workspace-scm doesnt work when source job is a matrix job. Any progress here? I see a pull request but the status "Resolution" is still "Unresolved". In jenkins v1.512 this issue is still present. 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] [core] (JENKINS-11564) Line number anchors for jobName/number/consoleFull
Evgeny Goldin commented on JENKINS-11564 Line number anchors for jobName/number/consoleFull Me too. Would ove to have this feature for being able to send a console log line pointer to my colleagues. Today I'm sending a link to console log accompanied with "Search for 'xyz' there". 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] [warnings] (JENKINS-17767) Unable to get warnings from all parsers
Maciej Nowak created JENKINS-17767 Unable to get warnings from all parsers Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 28/Apr/13 10:08 PM Description: I'm looking for way to get list of warnings detected in particular build via API. I found out that there is API for each parser separately and they're distinguished by id (e.g /warnings32result/api/json). However I don't see any option to get all warnings or list of configured parsers. This is a bit blocking for me, as I'm creating tool that gathers build info from Jenkins. Environment: Jenkins v1.512, Warnings plugins 4.52 Project: Jenkins Priority: Major Reporter: Maciej Nowak 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] [warnings] (JENKINS-17767) Unable to get warnings from all parsers via API
Maciej Nowak updated JENKINS-17767 Unable to get warnings from all parsers via API Change By: Maciej Nowak (28/Apr/13 10:08 PM) Summary: Unabletogetwarningsfromallparsers viaAPI 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] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
thetaphi commented on JENKINS-17566 Severe polling error when using script trigger Will do once installed! Thanks, Uwe 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] [grails] (JENKINS-16159) Add a post-build action to generate war file
Ramzi Maalej updated JENKINS-16159 Add a post-build action to generate war file Change By: Ramzi Maalej (29/Apr/13 12:25 AM) Priority: Major Minor 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] [cobertura] (JENKINS-13877) Cobertura plugin does not provide data to the REST API
SCM/JIRA link daemon commented on JENKINS-13877 Cobertura plugin does not provide data to the REST API Code changed in jenkins User: ssogabe Path: src/main/java/hudson/plugins/cobertura/targets/CoverageTreeElement.java http://jenkins-ci.org/commit/cobertura-plugin/bcc09dbcf541ecab95b68b5dfadd5bc70c9e974b Log: FIXED JENKINS-13877 Cobertura plugin does not provide data to the REST API 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] [cobertura] (JENKINS-13877) Cobertura plugin does not provide data to the REST API
SCM/JIRA link daemon resolved JENKINS-13877 as Fixed Cobertura plugin does not provide data to the REST API Change By: SCM/JIRA link daemon (29/Apr/13 12:49 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-8616) cannot use spot instances
Francis Upton updated JENKINS-8616 cannot use spot instances This was done by the folks at RTI. 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] [ec2] (JENKINS-8616) cannot use spot instances
SCM/JIRA link daemon commented on JENKINS-8616 cannot use spot instances Code changed in jenkins User: Francis Upton Path: src/main/java/hudson/plugins/ec2/EC2AbstractSlave.java src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/java/hudson/plugins/ec2/EC2Computer.java src/main/java/hudson/plugins/ec2/EC2OndemandSlave.java src/main/java/hudson/plugins/ec2/EC2Slave.java src/main/java/hudson/plugins/ec2/EC2SpotComputerLauncher.java src/main/java/hudson/plugins/ec2/EC2SpotRetentionStrategy.java src/main/java/hudson/plugins/ec2/EC2SpotSlave.java src/main/java/hudson/plugins/ec2/PluginImpl.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/java/hudson/plugins/ec2/SpotConfiguration.java src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly src/main/resources/hudson/plugins/ec2/EC2SpotComputerLauncher/main.jelly src/main/resources/hudson/plugins/ec2/EC2SpotComputerLauncher/main.properties src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/help-spotMaxBidPrice.html src/main/webapp/AMI-Scripts/ubuntu-ami-setup.sh src/main/webapp/AMI-Scripts/ubuntu-init.py src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java http://jenkins-ci.org/commit/ec2-plugin/f473c09f50f97ff485c0c2f33c3908f9bf9d1064 Log: Merge pull request #43 from bwall/ec2-spot-provision JENKINS-8616 Use spot instances Compare: https://github.com/jenkinsci/ec2-plugin/compare/c5df1a61caaf...f473c09f50f9 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] [ec2] (JENKINS-8616) cannot use spot instances
Francis Upton resolved JENKINS-8616 as Fixed cannot use spot instances Change By: Francis Upton (29/Apr/13 4:15 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17683) Incorrect hash calculated for custom SSH keys
SCM/JIRA link daemon commented on JENKINS-17683 Incorrect hash calculated for custom SSH keys Code changed in jenkins User: Francis Upton Path: src/main/java/hudson/plugins/ec2/EC2PrivateKey.java src/test/java/hudson/plugins/ec2/EC2PrivateKeyTest.java http://jenkins-ci.org/commit/ec2-plugin/f4661e86b66cbf9662752d900686c341584203ae Log: Merge pull request #45 from joekiller/public-finger-print JENKINS-17683 Incorrect hash calculated for custom SSH keys Compare: https://github.com/jenkinsci/ec2-plugin/compare/f473c09f50f9...f4661e86b66c 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] [ec2] (JENKINS-17683) Incorrect hash calculated for custom SSH keys
Francis Upton resolved JENKINS-17683 as Fixed Incorrect hash calculated for custom SSH keys Change By: Francis Upton (29/Apr/13 4:27 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
