How to write deploy details to webserver while deploying

Hi,

I'm looking for a robust way of somehow be able to store the deploy-details on the target-webserver. This way testers/developers etc are able trace the edition that they are testing.

Details I'm thinking of are:
- source server
- source branch & edition
- timestamp of the deploy
- user who started the deploy

I'm thinking of executing a dnr on success on target-server that will write these params to a file.

Any help/tips are more then welcome.

Cheers, Ronald

Find more posts tagged with

Comments

Adam Stoller

Hi,

I'm looking for a robust way of somehow be able to store the deploy-details on the target-webserver. This way testers/developers etc are able trace the edition that they are testing.

Details I'm thinking of are:
- source server
- source branch & edition
- timestamp of the deploy
- user who started the deploy

I'm thinking of executing a dnr on success on target-server that will write these params to a file.

Any help/tips are more then welcome.

Cheers, Ronald

Are the branch and edition passed in as parameters to the deployment?
I'd suggest dumping the complete contents of the in-memory log, that is accessible on STDIN for your DNR, and looking through it to see how much of this information is in there - I believe most of it is, but I'm not sure (the timestamp you can generate on the fly in your DNR)

RonaldV

Cheers Fish,

my problem is not so much in how to pass the params to a dnr. Branch, edition, etc are already passed via params and thus can be added to a dnr-call.

Problem is more in questions like:
- is dnr the best solution for this?
- should dnr run on source or target?
- what would be the most appropriate language to write the dcr-script in? bat/perl/wscript?
- how to make it robust & fail-safe?
- how to avoid the installation of tool like perl on the target-webservers (out are windows, thus no perl by default)?
- how do other customers solve this issue?

What is the best-practice here?

Thanks, Ronald