[jira] [Commented] (GUMP-153) Gump Metadata: links no longer work
[ https://issues.apache.org/jira/browse/GUMP-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211566#comment-13211566 ] Konstantin Kolinko commented on GUMP-153: - As far as I enjoy reviewing Gump results, all metadata links do work. So this 7-year old issue is actually already resolved. However, it would be better if the meta data link pointed to the actual file used by Gump for that run, rather than the current SVN contents, as that may have been updated since the run. With current svn server version it is possible to do. It now supports URL syntax with revision numbers, e.g.: http://svn.apache.org/repos/asf/gump/metadata/project/lucene-java.xml?p=1234567 I am using syntax with a peg revision above (operative revision defaults to the peg one). The authoritative reference can be found in the Subversion book, see URL syntax section in httpd server chapter: http://svnbook.red-bean.com/en/1.7/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra Gump Metadata: links no longer work --- Key: GUMP-153 URL: https://issues.apache.org/jira/browse/GUMP-153 Project: Gump Issue Type: Bug Environment: http://vmgump.apache.org/gump/public/index.html Reporter: Sebb Priority: Minor The Gump meta data links no longer work, now that the metadata is in SVN. For example: http://cvs.apache.org/viewcvs.cgi/gump/project/jakarta-jmeter.xml should now be: http://svn.apache.org/repos/asf/gump/metadata/project/jakarta-jmeter.xml However, it would be better if the meta data link pointed to the actual file used by Gump for that run, rather than the current SVN contents, as that may have been updated since the run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Commented] (GUMP-116) Promote using html in description/ fields
[ https://issues.apache.org/jira/browse/GUMP-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211569#comment-13211569 ] Konstantin Kolinko commented on GUMP-116: - I think it is not needed. There is url element in a module [1] that links to the official web site of a project. That should be enough, because the official site is the authoritative source of information on a project. The site is always maintained better than Gump metadata. [1] http://gump.apache.org/metadata/module.html#url Promote using html in description/ fields --- Key: GUMP-116 URL: https://issues.apache.org/jira/browse/GUMP-116 Project: Gump Issue Type: Improvement Components: Object Model (GOM) Affects Versions: GOM-0.5 Reporter: Leo Simons Fix For: GOM-0.5 It would be cool if description/ fields contained more useful content. For example, it might make sense to provide links to a wiki page with developer information about debugging a particular project, or links to additional build functionality a project utilizes outside of gump (like nightly build download locations). This would mean the description/ content should get a prominent place in gump-generated docs, the GOM docs are updated to detail that one can, in fact, use HTML, and that we promote the practice in some way. Thinking of maven POMs, their description/ and longDescription/ contents might need to be extended to have that kind of information relevant for developers. One could have a developerInfo/ in addition to those, I dunno. Maybe the maven people have something plannen already :-D -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Commented] (GUMP-147) Complain if a project does not provide all the outputs it states
[ https://issues.apache.org/jira/browse/GUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211576#comment-13211576 ] Konstantin Kolinko commented on GUMP-147: - I think it is already implemented. The lucene-java project recently had the issue of missing outputs and that caused the project to be marked as failed. So this check is working. Notification email contains [1] (search for lucene-java): [[[ The current state of this project is 'Failed', with reason 'Missing Build Outputs'. ]]] The issue in lucene-java was [2] that their build configuration was changed and jars were produced in a different place. The built was successful (and link to build output was green), but the whole project was in the failed state. So this check actually works. I do not know whether the check iterates over all outputs, as lucene-java project has only one jar. For reference: [1] http://marc.info/?l=gumpm=132938480323353w=2 [2] http://svn.apache.org/viewvc?view=revisionrevision=1290917 Complain if a project does not provide all the outputs it states Key: GUMP-147 URL: https://issues.apache.org/jira/browse/GUMP-147 Project: Gump Issue Type: New Feature Components: Python-based Gump Affects Versions: Gump3-alpha-7 Reporter: Leo Simons Fix For: Gump3-alpha-7 We should have a post-processing plugin (maybe one-per-output-type) that looks for successfully built projects, then goes and peeks if each and every of the outputs it specifies now actually exists (probably os.exists() and sometimes os.isfile() and os.isdir() if appropriate). If not, the plugin should mark the failure on the output. The logreporter should be modified to include this information with each project (this is probably a METADATA FAILURE), eg loop over all outputs for all projects and check_failure on each of them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Commented] (GUMP-155) Gump complains that the HiveMind build failed, when it does not
[ https://issues.apache.org/jira/browse/GUMP-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211580#comment-13211580 ] Konstantin Kolinko commented on GUMP-155: - This 7 year old issue is already answered. It was configuration issue in a project, not a Gump bug. It is time to close it. BTW, hivemind is not built by Gump nowadays. Gump complains that the HiveMind build failed, when it does not --- Key: GUMP-155 URL: https://issues.apache.org/jira/browse/GUMP-155 Project: Gump Issue Type: Bug Reporter: Howard M. Lewis Ship I get emails from Gump all the time that claim there's an error, but there's no indication of what the error is (notice that all the tests passed): To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at general@gump.apache.org. Project jakarta-hivemind has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 61 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-hivemind : HiveMind is a services and configuration microkernel - jakarta-hivemind-library : HiveMind is a services and configuration microkernel - jakarta-tapestry : Component-based web application framework organized around i... Full details are available at: http://vmgump.apache.org/gump/public/jakarta-hivemind/jakarta-hivemind/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [hivemind-28092005.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-hivemind/jakarta-hivemind/gump_work/build_jakarta-hivemind_jakarta-hivemind.html Work Name: build_jakarta-hivemind_jakarta-hivemind (Type: Build) Work ended in a state of : Failed Elapsed: 42 secs Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djava.classes.dir=target/classes -Djunit-available=true -Djavacc.home=/usr/local/gump/packages/javacc-3.1 -Ddownload-warning-marker-displayed=true -Dtest.classes.dir=target/test-classes -Dproject.version=28092005 [Working Directory: /usr/local/gump/public/workspace/jakarta-hivemind/framework] CLASSPATH:
[jira] [Commented] (GUMP-161) Apache Gump Metadata does not show actual version used
[ https://issues.apache.org/jira/browse/GUMP-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13211583#comment-13211583 ] Konstantin Kolinko commented on GUMP-161: - See my comment to GUMP-153 Apache Gump Metadata does not show actual version used -- Key: GUMP-161 URL: https://issues.apache.org/jira/browse/GUMP-161 Project: Gump Issue Type: Bug Reporter: Sebb Priority: Minor The Apache Gump Metadata link points to SVN. As such, it may show a more recent version than was actually used. It would be helpful to show the actual metadata file, either in the workspace, or by including the SVN revision of the file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
