Dealing with multiple Omnis 10.22 VCSs

[Phil (OmnisList)]

Happy New year Malkishtini.

We only use a single VCS, but we do use labels to identify a set of 
objects that create a release version...

This allows us to build any released version we have ever done!

Dev and QA just grab the latest versions of the objects directly, but 
only once it is considered safe to release is a label assigned, and a 
version number given...

Have you looked at or considered the label option in the VCS?

regards
Phil Potter
Based in Chester in the UK.

On 04/01/2023 16:10, malkishtini at gmail.com wrote:
> Hello all,
>
>   
>
> Happy new Year everyone!
>
>   
>
> We have a need to maintain different code versions, which means we need to
> have different VCSs, Dev, QA and production.
>
> We are trying to find a way to automate building the QA and production VCSs
> from Dev VCS based on certain criteria.
>
> We use Omnis VCS (studio 10.22) and PostgreSQL database.
>
>   
>
> I would like to see if others have dealt with this scenario (deploying
> different versions of code) before and what solutions they use to achieve
> it.
>
> We are trying to build a new process, so I'm looking for ideas and
> suggestions.
>
> As usual, all your ideas and feedback are welcomed and highly appreciated.
>
>   
>
> Thank you and best regards,
>
> Mayada
>
>   
>
>   
>
> _____________________________________________________________
> Manage your list subscriptions athttps://lists.omnis-dev.com
> Start a new message ->mailto:omnisdev-en at lists.omnis-dev.com