deployer: Release name is not so useful more like a random number

Q	A
Issue Type	Question
Deployer Version	4.2.1
Local Machine OS	Ubuntu 14.04.5 LTS
Remote Machine OS	Ubuntu 16.04.2 LTS

➜  fam git:(simplify-deployment) ✗ dep current production
➤ Executing task current
Current release: 16
Current release: 15
Current release: 4
✔ Ok

is there a option to make them timestamp at least or something that I could identify that they are she same releases and also would like to know what release server has. Because now I can just gues what is 16? 4? or on with server it is.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 3
Comments: 23 (13 by maintainers)

Most upvoted comments

You can override it really simple:

set('release_name', function () {
    return date('YmdHis');
});

antonmedv on Mar 22, 2017

No, keep everything is ok

antonmedv on Nov 19, 2018

Before release itself - yes.

Not sure I 100% understand. This is what my releases/ directory looks like right now:

[releases]# ls -1
./
../
1/
2/
2018.11.18-075735/
20181118.090400-convers/
20181118.090623-leho/
20181118.092924-leho/

I started to understand how to change {{release_name}} in the middle of the learning process (not deploy process), updated release_name and ran dep deploy again.

It seems to understand this change fine, because it keeps separate .dep/ metadata records.

Or should I delete everything and start fresh?

lkraav on Nov 18, 2018