Skip to content

Unable to promote to dev #401

Description

@chrislovecnm

I am trying to run jx promote command I am getting error: failed to lazy load the EnvironmentContext: no dev environment in namespace foo.

Do a need unique environments for each namespace I am deploying applications to? Do I need to edit jx requirements to add a different namespace, or the .jx/gitops/source-config.yaml file?

Some examples or more info is appreciated. I read through the documentation for jx promote, and I am confused a bit by the helmfile examples as well, and I am wondering if using a helmfile or other configuration would help.

I am running

jx promote -e dev -n apps --timeout 1h --no-poll --interactive -a jx-python-demo -v 0.0.2

My environments (which I think I need to change)

$ k get environments.jenkins.io
NAME         NAMESPACE       KIND          PROMOTION   ORDER   GIT URL                                          GIT BRANCH
demo         jx-demo         Permanent     Manual      500     https://gitlab.com/foo/foo-demo.git    master
dev          jx              Development   Never               https://gitlab.com/foo/foo-dev.git     master
production   jx-production   Permanent     Manual      500     https://gitlab.com/foo/foo-prod.git    master
staging      jx-staging      Permanent     Manual      100     https://gitlab.com/foo/foo.git   master

Can I run different environments off of the same repo? Also dev, demo, stage and production are on different clusters.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions