cliffmeyers the 404 is "normal" isn't it if there are no credentials? (ie that is how it knows that one doesn't exist?) - or is that only for the github case? 

Hrm no - the promise fails so it was not expecting that. 

wasungoni do you have security enabled on jenkins? 

https://issues.jenkins-ci.org/browse/JENKINS-43347 has a fix that is not in 1.0.1 (yet) to disable creation when security is disabled (as it can't work). 

Otherwise, will need a fair bit more information to help reproduce this. 

Yes I was able to reproduce this by disabling security and trying to create a git based pipeline. 

wasungoni if you enable security, this should work. If you can't enable secyrity, the creation flow won't work anyway and in a future version the button will be hidden in that case where it knows it can't work. 

This will be fixed in Blue Ocean 1.1 which is due next week. You will still have to enable security on your Jenkins instance.

wasungoni can you confirm your security config as much as possible? (in case this isn't actually a dupe of that other issue)

Just keeping this open to confirm it was actuallya dupe

michaelneale, the problem was resolved when I enabled security. thanks for the help

was actually security related. 

michaelneale thanks for helping clarify this. I could not recall if the 404 was normal in the event of security being disabled.