Activity
From 2012-07-01 to 2012-07-01
2012-07-01
- 23:07 Revision 942123e4 (rudder-techniques): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Fix condition for deleting users on Windows. Refs #2554
s/managAment/managEment/ in userMa... - 23:07 Revision 08884ed5 (rudder-techniques): Merge branch 'branches/rudder/2.3' into branches/rudder/2.4
- * branches/rudder/2.3:
Fix condition for deleting users on Windows. Refs #2554
s/managAment/managEment/ in userMa... - 23:06 Revision 9647f5ed (rudder-packages): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Trivial: restore original URL to make it easier to find - 23:06 Revision 43a701ae (rudder-packages): Merge branch 'branches/rudder/2.3' into branches/rudder/2.4
- * branches/rudder/2.3:
Trivial: restore original URL to make it easier to find - 20:56 Revision f9fc0572 (rudder): Trivial: fix English in webapp
- 20:56 Revision dd1b6599 (rudder): Trivial: fix English in webapp
- 18:38 Revision b73571ee (rudder-packages): Trivial: restore original URL to make it easier to find
- 18:30 User story #1971: Impossible to manage rudder server via web interface
- Matthieu CERDA wrote:
> Here is what I was suggesting in order to have a complying packaging:
>
> * Adjust the ru... - 18:10 User story #1971: Impossible to manage rudder server via web interface
- Here is what I was suggesting in order to have a complying packaging:
* Adjust the rudder-server-root dependencies... - 17:41 Bug #2611 (Discussion): Use configuration.properties.sample for reference configuration
- François, I'll leave it to you to actually remove the old file - I don't know what consequences that might have on de...
- 17:40 Bug #2611 (Pending technical review): Use configuration.properties.sample for reference configuration
- OK, that's http://www.rudder-project.org/redmine/projects/packages/repository/revisions/2c73de2837c940dedc1a3c6aa3f4b...
- 17:40 Bug #2611: Use configuration.properties.sample for reference configuration
- Hmmm, the ticket didn't get updated for some reason, but I commited this here: commit:2c73de28c
- 17:38 Bug #2611 (In progress): Use configuration.properties.sample for reference configuration
- I'm on it
- 17:38 Revision bc7f664a (rudder-packages): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Use sample properties file from ldap-inventory. Fixes #2611
Fixes #2603 Add migration scri... - 17:38 Revision 2c73de28 (rudder-packages): Use sample properties file from ldap-inventory. Fixes #2611
- 17:32 Bug #2618 (Pending technical review): Default log level should be INFO not DEBUG
- Applied in changeset commit:6f14fc8049de6d19a2bcd2fd14e8145af95e76ca.
- 17:31 Bug #2618 (Released): Default log level should be INFO not DEBUG
- Commit commit:22eac6d5 introduced a change to the default loglevel in logback.xml (commited for #2295).
This is no... - 17:32 Revision 855d30e4 (rudder): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Change default loglevel back to INFO (not DEBUG). Fixes #2618 - 17:32 Revision 1237021b (rudder): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Change default loglevel back to INFO (not DEBUG). Fixes #2618 - 17:32 Revision 24189c76 (rudder): Change default loglevel back to INFO (not DEBUG). Fixes #2618
- 17:32 Revision 6f14fc80 (rudder): Change default loglevel back to INFO (not DEBUG). Fixes #2618
- 17:27 Revision 60ac72b8 (rudder-techniques): s/log_error/result_error/ in networkCheck. Fixes #2606
- 17:24 Revision f99d972e (rudder-techniques): s/log_error/result_error/ in apacheServer. Fixes #2606
- 17:18 Bug #2303: The modification of the Distribute Policy PT have not been integrated in the rootServerInitialPromises
- All commits up to here look good to me.
But I've just made another commit to clean things up and make these promis... - 17:17 Revision d5546da2 (rudder-techniques): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
More initial promise sync'ing and cleanup for root server initial promises. Refs #2303
Fix... - 17:09 Revision a8abcd4e (rudder-techniques): More initial promise sync'ing and cleanup for root server initial promises. Refs #2303
- 15:21 Bug #2599: The version of the cfengine_stdlib used contains many old/buggy body and bundle
- There was a separate commit here by Nicolas Charles to remove an incompatible body. However, that commit was only mad...
- 15:20 Revision b2a682d3 (rudder-techniques): Fixes #2599 : removing body uncompatible with our version of CFEngine
- 13:29 Revision 1ae8c02c (rudder): Trivial : removing println that shouldn't be there
- 13:29 Revision 926c517a (rudder): Trivial : removing println that shouldn't be there
- 13:26 User story #2616: Display reporting with a drill down to the component level on the Node page
- Just a small remark : the table was previously a DataTables, sortable. With this new implementation, it's not sortabl...
- 13:20 User story #2616 (Pending technical review): Display reporting with a drill down to the component level on the Node page
- Applied in changeset commit:c883cf9ca505f49912facb686e8585d887e4dc2b.
- 12:53 User story #2616 (Released): Display reporting with a drill down to the component level on the Node page
- On the Node detail page, we should show the reporting with in-depth details about each rule : the directive complianc...
- 13:25 User story #2598: When compliance is displayed, allow to look for details about the compliance
- Most of the back office has been done; there just lacks the logs in the syslog format when an unexpected reports come...
- 13:00 Revision 19dc6511 (rudder): Fixes #2616 : display reporting with a drill down to the component level on the Node detail page
- 13:00 Revision c883cf9c (rudder): Fixes #2616 : display reporting with a drill down to the component level on the Node detail page
- 12:59 Revision bca23345 (rudder): Refs #2598 : fixes some error and improve the data available about the detailed reporting
- 12:59 Revision 3353168e (rudder): Refs #2598 : fixes some error and improve the data available about the detailed reporting
- 12:55 User story #2617 (Released): On the rule page, display the reporting with a browsable view of details (directive, component, component value)
- As per #2616, we should display on the rule page all the details we have about the reporting.
Also available in: Atom