Activity

From 12/11/2023 to 01/09/2024

09:21 AM Support #3303: make the automated deployment process fully production ready: Greg Shah wrote:
> > Note how easily it is to setup FWD so it can be made available:
> > [...]
> > Then it's just ... Roger Borrello
08:54 AM Support #3303: make the automated deployment process fully production ready: > May I suggest Docker should be the main basis for the build and runtime roles?
I do want to leverage Docker to ... Greg Shah

08:09 AM Support #3303: make the automated deployment process fully production ready: Branch 3303a was merged into trunk revision 14898 and archived. Roger Borrello

02:42 PM Support #3303: make the automated deployment process fully production ready: Greg Shah wrote:
> Code Review Task Branch 3303a Revision(s?) 14897 through 14899
>
> I'm not sure why it shows 3... Roger Borrello
02:32 PM Support #3303: make the automated deployment process fully production ready: Code Review Task Branch 3303a Revision(s?) 14897 through 14899
I'm not sure why it shows 3 revisions but the chang... Greg Shah
02:25 PM Support #3303: make the automated deployment process fully production ready: The incorrect branch name has been corrected to be *3303a* Roger Borrello
02:02 PM Support #3303: make the automated deployment process fully production ready: Roger Borrello wrote:
> Greg Shah wrote:
> > Could you have misnamed the branch on creation?
>
> Ugh... I must d... Constantin Asofiei
02:00 PM Support #3303: make the automated deployment process fully production ready: Greg Shah wrote:
> Could you have misnamed the branch on creation?
Ugh... I must dyslexic be... I created it as *... Roger Borrello
01:57 PM Support #3303: make the automated deployment process fully production ready: There is no branch at @~/secure/code/p2j_repo/p2j/active/3303a/@. Could you have misnamed the branch on creation? Greg Shah
01:49 PM Support #3303: make the automated deployment process fully production ready: Branch 3303a was rebased to trunk_14896 and is at revision 14899. Roger Borrello

12:00 AM Support #3303: make the automated deployment process fully production ready: Branch 3303a was rebased to trunk_14886 and is at revision 14889. Roger Borrello

08:38 AM Support #3303: make the automated deployment process fully production ready: The repository for @~/secure/code/p2j_repo/mgmt/@ is now also available on *xfer.goldencode.com* as @/opt/fwd/mgmt@
Roger Borrello
07:41 AM Support #3303: make the automated deployment process fully production ready: > After testing, I think I should remove at least *ncurses*, perhaps *jdk* as well. It all depends on how "thin" we w... Greg Shah

04:39 PM Support #3303: make the automated deployment process fully production ready: Right now I have the roles for building a Docker host as:
* base
* fwd_acct
* dev_tools
* jdk
* ncurses
* inter... Roger Borrello

08:38 PM Support #3303: make the automated deployment process fully production ready: The latest revision builds a FWD reference system utilizing Docker image to retrieve the FWD deployment. Right now it... Roger Borrello

10:19 AM Support #3303: make the automated deployment process fully production ready: May I suggest Docker should be the main basis for the build and runtime roles? This would allow us to pull "code" fro... Roger Borrello

07:07 AM Support #3303: make the automated deployment process fully production ready: I generally like this. Let's consider the idea that roles can be additive. By splitting these into "lego blocks" we... Greg Shah

06:33 PM Support #3303: make the automated deployment process fully production ready: Greg Shah wrote:
> The playbooks are 3 years old, were never 100% complete and we never got local execution running ... Roger Borrello
06:22 PM Support #3303: make the automated deployment process fully production ready: Branch 3303 was created from trunk_14870. I checked in an update to allow for locales to be included in the convert a... Roger Borrello

Also available in: Atom

FWD » Deployment