Updating Beatrice branch name & Enabling CD for testnet

rilesdun commented

2022-11-09 15:54:08 +00:00

(Migrated from gitlab.com)

Definition of Done

Updating Beatrice branch name to our testnet environment & Automatic deployments of witness node/cli wallet prior to merges into master

Acceptance Criteria

Create new testnet that is based off of ONLY the latest merge into the new testnet branch
Change name of Beatrice branch to - Testnet or something similar
Setup continuous deployment to deploy witness_node and cli_wallet to our testnet
Merges into the new testnet branch will automatically deploy the updated witness_node & cli_wallet
Automatic deployment will stop the current running witness_node, replace it with the new artifact & replay the chain

Resources

N/A

## Definition of Done Updating Beatrice branch name to our testnet environment & Automatic deployments of witness node/cli wallet prior to merges into master ## Acceptance Criteria * Create new testnet that is based off of **ONLY** the latest merge into the new testnet branch * Change name of Beatrice branch to - Testnet or something similar * Setup continuous deployment to deploy witness_node and cli_wallet to our testnet * Merges into the new testnet branch will automatically deploy the updated witness_node & cli_wallet * Automatic deployment will stop the current running witness_node, replace it with the new artifact & replay the chain ## Resources N/A

rilesdun commented

2022-11-09 15:54:08 +00:00

(Migrated from gitlab.com)

assigned to @rilesdun

rilesdun commented

2022-11-09 15:58:58 +00:00

(Migrated from gitlab.com)

cc: @elynch1 @bobinson @serkixenos

rilesdun commented

2022-11-15 13:47:25 +00:00

(Migrated from gitlab.com)

mentioned in issue PBSA/tools-libs/infrastructure/devops-misc-issues#19

bobinson commented

2022-11-15 14:28:29 +00:00

(Migrated from gitlab.com)

Comments:

Create new testnet that is based off of ONLY the latest merge into the new testnet branch

I think its better to use the same release process as other projects and create a "beta" release. We have been originally tagging the releases as semversion-test and the same can be continued. This will help to have a streamlined process and more over help us to align with the organizational objective of doing more releases (deployments).

Change name of Beatrice branch to - Testnet or something similar

Why not just keep it as we have been using this branch for test releases all these years ? :)

Comments: 1. > Create new testnet that is based off of **ONLY** the latest merge into the new testnet branch I think its better to use the same release process as other projects and create a "beta" release. We have been originally tagging the releases as `semversion-test` and the same can be continued. This will help to have a streamlined process and more over help us to align with the organizational objective of doing more releases (deployments). 2. > Change name of Beatrice branch to - Testnet or something similar Why not just keep it as we have been using this branch for test releases all these years ? :)

rilesdun commented

2022-11-15 14:43:11 +00:00

(Migrated from gitlab.com)

The point of merging to Beatrice was to deploy to the testnet prior to mainnet, without the Beatrice testnet running what is the point of this? It made sense when there was a running testnet named beatrice, but now it does not make much sense to anyone on the outside.

"I think its better to use the same release process as other projects and create a "beta" release. We have been originally tagging the releases as semversion-test and the same can be continued." - There hasn't been a tag with test in over a year.

If we merge into beatrice, it should be automatically deployed into our testnet as this is the only running testnet now. Lately no information is passed when merges to beatrice are done, as well as that it should be deployed for testing.

The only testing happening is by the core team themselves, and not with our applications in our testnet environment. To get to a more continous deployment environment, we should be deploying "some" branch to our testnet prior to it going to mainnet.

@bobinson

The point of merging to Beatrice was to deploy to the testnet prior to mainnet, without the Beatrice testnet running what is the point of this? It made sense when there was a running testnet named beatrice, but now it does not make much sense to anyone on the outside. "I think its better to use the same release process as other projects and create a "beta" release. We have been originally tagging the releases as `semversion-test` and the same can be continued." - There hasn't been a tag with `test` in over a year. If we merge into beatrice, it should be automatically deployed into our testnet as this is the only running testnet now. Lately no information is passed when merges to beatrice are done, as well as that it should be deployed for testing. The only testing happening is by the core team themselves, and not with our applications in our testnet environment. To get to a more continous deployment environment, we should be deploying "some" branch to our testnet prior to it going to mainnet. @bobinson

bobinson commented

2022-11-15 15:14:56 +00:00

(Migrated from gitlab.com)

New code will be available to Beatrice - it will be selected, nearly stable code from develop. That's why we have this branch.

We had stopped doing the releases as the attempt to run testnets on the bunker namely "Gladiator" failed and we moved onto create the docker environment. If you can work and get the automation done, it will be great. And we need to do the test releases and they can be deployed.

New code will be available to Beatrice - it will be selected, nearly stable code from `develop`. That's why we have this branch. We had stopped doing the releases as the attempt to run testnets on the bunker namely "Gladiator" failed and we moved onto create the docker environment. If you can work and get the automation done, it will be great. And we need to do the test releases and they can be deployed.

JeanMichelMoreau commented

2022-11-18 17:07:04 +00:00

(Migrated from gitlab.com)

@bobinson Hey, if I understand correctly, this issue results in us updating mainnet before testnet. Do I have that right?

@tai.sama FYI, this might affect the 3SPK testing plan.

@bobinson Hey, if I understand correctly, this issue results in us updating mainnet _before_ testnet. Do I have that right? @tai.sama FYI, this might affect the 3SPK testing plan.

bobinson commented

2022-11-21 15:02:17 +00:00

(Migrated from gitlab.com)

this issue results in us updating mainnet before testnet. Do I have that right?

No - we will not be updating the mainnet before testnet. We are talking about bringing back our older system of having a much formal testnet. Originally we used to have "beta" releases which used to run in a testnet. Then the testnet died down and since the attempts to run a testnet failed, we moved on with a docker based solution for most scenarios. Right now we are trying to bring back the formal testnet.

> this issue results in us updating mainnet *before* testnet. Do I have that right? No - we will not be updating the mainnet before testnet. We are talking about bringing back our older system of having a much formal testnet. Originally we used to have "beta" releases which used to run in a testnet. Then the testnet died down and since the attempts to run a testnet failed, we moved on with a docker based solution for most scenarios. Right now we are trying to bring back the formal testnet.

serkixenos commented

2022-11-28 02:11:45 +00:00

(Migrated from gitlab.com)

Info on stable testnet QA environment is here: https://gitlab.com/PBSA/peerplays/-/issues/435#note_1187065108

Its based on latest commits on beatrice branch in peerplays, peerplays-utils and peerplays-ethereum repos.

Info on stable testnet QA environment is here: https://gitlab.com/PBSA/peerplays/-/issues/435#note_1187065108 Its based on latest commits on beatrice branch in peerplays, peerplays-utils and peerplays-ethereum repos.

bobinson commented

2022-11-30 07:02:18 +00:00

(Migrated from gitlab.com)

Alpha release 1.5.20-alpha is available here https://gitlab.com/PBSA/peerplays/-/releases/1.5.20-alpha

Note that this release has known limitations to Ethereum settlement during withdraw process.

Alpha release `1.5.20-alpha` is available here https://gitlab.com/PBSA/peerplays/-/releases/1.5.20-alpha Note that this release has known limitations to Ethereum settlement during withdraw process.

rilesdun commented

2023-03-01 15:06:15 +00:00

(Migrated from gitlab.com)

mentioned in merge request !214

rilesdun commented

2023-04-27 19:11:30 +00:00

(Migrated from gitlab.com)

The following MR enables deployments of master branch to our devnet - https://gitlab.com/PBSA/peerplays/-/merge_requests/214

Ticket is out of scope with new running public testnet and branching strategy will be clearer moving forward on peerplays 2

The following MR enables deployments of master branch to our devnet - https://gitlab.com/PBSA/peerplays/-/merge_requests/214 Ticket is out of scope with new running public testnet and branching strategy will be clearer moving forward on peerplays 2

rilesdun (Migrated from gitlab.com) closed this issue

2023-04-27 19:11:31 +00:00

rilesdun commented

2023-05-16 08:20:59 +00:00

(Migrated from gitlab.com)

mentioned in commit 99bdea3d3fbbc51e3d493be8085f1eb851690973

vampik commented

2023-05-16 08:20:59 +00:00

(Migrated from gitlab.com)

mentioned in commit 69b1b85a4ea1e36c850297cdff5c984091cedbba

Updating Beatrice branch name & Enabling CD for testnet #480

Definition of Done

Acceptance Criteria

Resources