Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to execute 'jx boot' from outside a boot repo #6798

Closed
hferentschik opened this issue Feb 25, 2020 · 0 comments · Fixed by #6802
Closed

Unable to execute 'jx boot' from outside a boot repo #6798

hferentschik opened this issue Feb 25, 2020 · 0 comments · Fixed by #6802
Assignees
Labels
area/boot issues in the `jx boot` command kind/bug Issue is a bug priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@hferentschik
Copy link

Summary

This is an side-effect of the changes merged for #6653

Steps to reproduce the behavior

From an empty directory execute jx boot:

jx --verbose boot
Creating boot config with defaults, as not in an existing boot directory with a git repository.
hello <nil>
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x199 pc=0x305bdd0]

goroutine 1 [running]:
github.com/jenkins-x/jx/pkg/cmd/opts.(*CommonOptions).ConfigureCommonOptions(0xc000458000, 0x0, 0x0, 0x0)
	/Users/hardy/work/go/src/github.com/jenkins-x/jx/pkg/cmd/opts/team_settings.go:169 +0x90
github.com/jenkins-x/jx/pkg/cmd/boot.(*BootOptions).Run(0xc00069aa00, 0x0, 0x0)
	/Users/hardy/work/go/src/github.com/jenkins-x/jx/pkg/cmd/boot/boot.go:158 +0x1bb
github.com/jenkins-x/jx/pkg/cmd/boot.NewCmdBoot.func1(0xc00069d900, 0xc0004f7940, 0x0, 0x1)
	/Users/hardy/work/go/src/github.com/jenkins-x/jx/pkg/cmd/boot/boot.go:92 +0x6f
github.com/spf13/cobra.(*Command).execute(0xc00069d900, 0xc0004f7930, 0x1, 0x1, 0xc00069d900, 0xc0004f7930)
	/Users/hardy/work/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:830 +0x2ae
github.com/spf13/cobra.(*Command).ExecuteC(0xc0001c0000, 0xc0002c5c80, 0x66c5e20, 0xc0000b8000)
	/Users/hardy/work/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914 +0x2fc
github.com/spf13/cobra.(*Command).Execute(...)
	/Users/hardy/work/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
github.com/jenkins-x/jx/cmd/jx/app.Run(0x0, 0x0, 0x0, 0xc000a37f88, 0xc00005c178)
	/Users/hardy/work/go/src/github.com/jenkins-x/jx/cmd/jx/app/jx.go:19 +0x185
main.main()
	/Users/hardy/work/go/src/github.com/jenkins-x/jx/cmd/jx/jx.go:11 +0x32
@hferentschik hferentschik self-assigned this Feb 25, 2020
@hferentschik hferentschik added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. kind/bug Issue is a bug area/boot issues in the `jx boot` command labels Feb 25, 2020
@hferentschik hferentschik changed the title Unable to execute 'jx boot' from outside a requirements/dev repo Unable to execute 'jx boot' from outside a boot repo Feb 25, 2020
hferentschik added a commit to hferentschik/jx that referenced this issue Feb 25, 2020
hferentschik added a commit to hferentschik/jx that referenced this issue Feb 25, 2020
hferentschik added a commit to hferentschik/jx that referenced this issue Feb 25, 2020
hferentschik added a commit to hferentschik/jx that referenced this issue Feb 25, 2020
hferentschik added a commit to hferentschik/jx that referenced this issue Feb 25, 2020
hferentschik added a commit to hferentschik/jx that referenced this issue Feb 25, 2020
hferentschik added a commit to hferentschik/jx that referenced this issue Feb 25, 2020
hferentschik added a commit to hferentschik/jx that referenced this issue Feb 25, 2020
daveconde pushed a commit to daveconde/jx that referenced this issue Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/boot issues in the `jx boot` command kind/bug Issue is a bug priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant