You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the current solution and the documentation that I have seen so far, the handling of environments is not yet clear for me.
The repo contains params.<env>.json for dev, test, prod.
Describe the solution you'd like
I would hope for a build pipeline to build the code on any commit and creating an artifact and then a release pipeline that deploys this release to certain environments.
Did I miss any documentation or idea in the code so far?
The text was updated successfully, but these errors were encountered:
This enhancement will include deploy pipelines to test and prod environments. Once this is done for one repository, we will implement the same across all the other repositories. We will close this once this is merged.
Any other feedback or expectations from your side regarding the pipelines?
We would like to move towards workflow templates to fully showcase this, but sadly, this will break all workflows as soon as users fork the repo because of this https://github.community/t/ref-head-in-reusable-workflows/203690/22
Once this gets fixed, we will add this.
I will work on repository templates itself for the time being to simplify this for customers.
Looking at the current solution and the documentation that I have seen so far, the handling of environments is not yet clear for me.
The repo contains
params.<env>.json
fordev
,test
,prod
.Describe the solution you'd like
I would hope for a build pipeline to build the code on any commit and creating an artifact and then a release pipeline that deploys this release to certain environments.
Did I miss any documentation or idea in the code so far?
The text was updated successfully, but these errors were encountered: