Ticket #815 (closed task: invalid)

Opened 12 years ago

Last modified 11 years ago

[WG] Agree upon procedure for updating pylons code on glue

Reported by: domlowe Owned by: selatham
Priority: required Milestone: Reporting
Component: CSML Version:
Keywords: Cc:

Description

Now there are 4 of us (me, Stephen, Phil & Bryan) working on pylons we need to agree on a mechanism and procedure for keeping pylons/security/csml on glue up to date. It should just be a matter of updating eggs when we have sorted out the configuration (see tickets 812 and 814), but will need documenting so we're all doing the same thing.

Change History

comment:1 Changed 12 years ago by selatham

Dom said:- Anyway I think this documentaion can be kepy pretty simple now that we are only ever updating eggs on glue (and not hacking arround on source code). I suggest that whenever we update an egg we make a note of it in this file:

/var/www/ndg/logs/egg.log

I have started it off with some recent updates I did.

The only other type of change we might make is to the config files. I've created an empty log called; /var/www/ndg/logs/config.log

that I propose we use for now to document changes to config files (development.ini and ndgDiscovery.config) although perhaps we want to store copies of the (BADC) config files in subversion?

Any thoughts?

comment:2 Changed 12 years ago by domlowe

  • Owner changed from domlowe to selatham
  • Milestone changed from PROD Step2 to Reporting and Futures

Looks like these logs aren't a popular proposal - for development purposes relying on egg revision info seems like enough. Moved to Reporting & Futures for future consideration.

comment:3 Changed 12 years ago by selatham

Documentation required.

comment:4 Changed 11 years ago by lawrence

  • Status changed from new to closed
  • Resolution set to invalid

at least as posed ...

Note: See TracTickets for help on using tickets.