kubectl apply failed for version 0.1.31 about kubernetestask HOT 8 CLOSED

On Mar 21, 2017 7:16 PM, "Tsuyoshi Ushio" ***@***.***> wrote: I tried on a hosted linux agent. I just update the task. Then I tried to create a release. The result was like that. One of the problem of the market place is we can't test in advance. :( I also try to identify why it happens. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADQphahiyYyVKsLthJrKJpHNDZe11ogfks5roIR-gaJpZM4MifXb> .

On Mar 21, 2017 11:55 PM, "Rakesh Kelkar" ***@***.***> wrote: You can test by making the version 0.x.x and marking it as preview... Customers should depend on 1.x.x versions... On Mar 21, 2017 7:16 PM, "Tsuyoshi Ushio" ***@***.***> wrote: > I tried on a hosted linux agent. I just update the task. Then I tried to > create a release. The result was like that. One of the problem of the > market place is we can't test in advance. :( I also try to identify why it > happens. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#8 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ADQphahiyYyVKsLthJrKJpHNDZe11ogfks5roIR-gaJpZM4MifXb> > . >

On Mar 21, 2017 11:57 PM, "Rakesh Kelkar" ***@***.***> wrote: Oh yeah... Download works for build scenario but fails for release... If you can publish as 0.** and give me a repro of the issue I can connect with the right guy in vsts support team... Maybe we could release different build and release tasks to mitigate? On Mar 21, 2017 11:55 PM, "Rakesh Kelkar" ***@***.***> wrote: > You can test by making the version 0.x.x and marking it as preview... > Customers should depend on 1.x.x versions... > > On Mar 21, 2017 7:16 PM, "Tsuyoshi Ushio" ***@***.***> > wrote: > >> I tried on a hosted linux agent. I just update the task. Then I tried to >> create a release. The result was like that. One of the problem of the >> market place is we can't test in advance. :( I also try to identify why it >> happens. >> >> — >> You are receiving this because you commented. >> Reply to this email directly, view it on GitHub >> <#8 (comment)>, >> or mute the thread >> <https://github.com/notifications/unsubscribe-auth/ADQphahiyYyVKsLthJrKJpHNDZe11ogfks5roIR-gaJpZM4MifXb> >> . >> >

On Mar 22, 2017 9:24 PM, "Tsuyoshi Ushio" ***@***.***> wrote: No problem. I appreciate your contribution. :) Let's tackle this problem together. Do I need to release current working version as 1.** then release 0.** as a preview? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADQphcYVhF8B1VY5ZrWi8sfL5ecgAGXZks5rofPwgaJpZM4MifXb> .