Custom Query (22 matches)
Results (1 - 3 of 22)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #27 | fixed | Test ticket for ticket show details | eelco@… | eelco@… |
| Description |
This is a test ticket to see changes to ticket_show_details option in trac.ini |
|||
| #25 | fixed | As of april 21st, around 16:00 about 5 code revisions have been lost | david.vanenckevort@… | work@… |
| Description |
This afternoon we noticed our contiuous integration build was not updating properly after code commits, and more interestingly the continuous integration build was running revision 1790 (http://ci.nmcdsp.org) while the latest commit today was revision 1786 (https://trac.nbic.nl/gscf/log/trunk). As I know SVN + TRAC was migrated last week I assume that somehow a SVN state has been migrated which is lacking the last 5 commits: quote Dear all, Please note that the Trac server https://trac.nbic.nl/ will be migrated to a different compute center Thursday morning 21/4. This will result in a temporary service disruption. More details later. Rob -- Rob W.W. Hooft Chief Technology Officer BioAssist, Netherlands Bioinformatics Centre From our continuous integration build log we see the continuous integration works fine until 16:00 201104211445 newer version of gscf is available 201104211445 deploying revision 1788 (version 0.8.0 / Grails 1.3.7) and undeploying revision 1787... 201104211445 uninstalling webtest plugin 201104211445 uninstalling db-util plugin 201104211445 uninstalling grom plugin 201104211445 setting build information variables in application.properties 201104211445 current workdirectory: /home/tomcat/workspace/gscf 201104211445 building new ci war... 201104211446 project deployment is still happening 201104211445 stopping gscf-0.8.0-ci 201104211445 undeploying gscf-0.8.0-ci 201104211445 deploying new ci WAR 201104211445 updating apache virtual host configuration 201104211445 reloading Apache 201104211445 done deploying gscf revision 1788 (version 0.8.0) 201104211459 newer version of gscf is available 201104211459 deploying revision 1789 (version 0.8.0 / Grails 1.3.7) and undeploying revision 1788... 201104211459 setting build information variables in application.properties 201104211459 current workdirectory: /home/tomcat/workspace/gscf 201104211459 building new ci war... 201104211500 project deployment is still happening 201104211459 stopping gscf-0.8.0-ci 201104211459 undeploying gscf-0.8.0-ci 201104211459 deploying new ci WAR 201104211459 updating apache virtual host configuration 201104211459 reloading Apache 201104211459 done deploying gscf revision 1789 (version 0.8.0) 201104211550 newer version of gscf is available 201104211550 deploying revision 1790 (version 0.8.0 / Grails 1.3.7) and undeploying revision 1789... 201104211550 uninstalling webtest plugin 201104211550 uninstalling db-util plugin 201104211550 uninstalling grom plugin 201104211550 setting build information variables in application.properties 201104211550 current workdirectory: /home/tomcat/workspace/gscf 201104211550 building new ci war... 201104211551 project deployment is still happening 201104211550 stopping gscf-0.8.0-ci 201104211550 undeploying gscf-0.8.0-ci 201104211550 deploying new ci WAR 201104211550 updating apache virtual host configuration 201104211550 reloading Apache 201104211550 done deploying gscf revision 1790 (version 0.8.0) after which the svn state was broken: svn: No such revision 1790 201104211619 haven't got an svn revision? svn: No such revision 1790 svn: No such revision 1790 201104211620 haven't got an svn revision? I don't know what happened, but we:
I'm sure you are aware of the seriousness of this issue, so I hope this can be resolved ASAP |
|||
| #22 | fixed | Project admin page editable by logged in user, not just admins | support@… | tim.te.beek@… |
| Description |
Any logged in user can administrate any project, by altering the below URL in a predictable manner: https://trac.nbic.nl/admin/ProjectAdmin.php?mode=editproject&project=sandbox Currently the only requirement is that the user is logged in, not whether or not the user is an administrator for the project. This constitutes a mayor security project for every current Trac project. |
|||
