Incomplete Build Created Output

[sj26]

I did a bk build new today and it says build created but looks like it's meant to have some output - maybe a build link?

[sj26]

I tried one of these and it opened the current folder instead of my web browser 🙃

[sj26]

I think because it's not actually starting a build successfully 🤔

How do I debug this? I can't see a "verbose" mode or anything, to see the request/response cycle?

[mcncl]

Hmm, this seems to be the case if the --pipeline doesn't exist in the org that you're using. It should output an error instead of a blank URL.

[sj26]

I have a ~/.config/bk.yaml like:

Both have read_* and write_builds scopes. They were configured through bk configure ...

The problem happens even when I supply the org in the pipeline param:

[mcncl]

I think you may be using packagecloud and so it cannot find the pipeline buildkite, if you run bk use it should let you pick buildkite which should then allow the command to run.

[sj26]

Yeah, looks like that works:

That seems to have made a .bk.yaml in my local directory?

I would have expected --pipeline=buildkite/buildkite to figure out the org 🤔

I'd love see some documentation or in-cli hints to help me with this stuff.

[mcncl]

Appreciate the feedback @sj26! I'll write up some improvements we can make with regards to user feedback and general logic of the CLI

[mcncl]

@sj26 the lack of error should be fixed in #402; it won't output a blank URL, rather the API error

[mcncl]

We'll have to look in to correctly parsing the buildkite/buildkite --pipeline input.