Andrea Peruffo

Thanks for sharing openly your plans @baywet , I have found a few more edge cases and will try to report with minimal reproducers along.

Thanks a lot for adding so much context @baywet ! > I'm not sure this answers your question though? This gives me context, do you think that keeping a maintained...

The pipeline "per-se" is trivial and not an issue (it's basically a single command `dotnet publish ./src/kiota/kiota.csproj -c Release -p:PublishSingleFile=true -r ${{ matrix.architecture }} -o ./${{ matrix.architecture }}`), the problem...

When working on integration tools, like Maven plugins, `asdf` or similar scripts being able to test the entire E2E thing is pretty useful.

> in that context, why is it more useful than doing a local publish so you can test the integration tool quickly? (effectively what I do for the vscode extension)...

> aaahh I get it I think, that's because you want to be able to test the "install" part of the integration, correct? Yup, as well, that's the obvious initial...

> I'm not sure why would anymore need to test both at the same time? Because I'm connecting the dots of many moving pieces and being able to test everything...

I totally agree that this is a niche use-case, mostly for developers and integrators. E.g. you will be able to test out changes from a user's PR without having to...

please consider that those nightly builds can even be published to a different(e.g. non non-official) repository(even outside the Microsoft org), but it will be nice if it's somehow monitored/used by...

> Could we have a daily drop on a storage account somewhere that is available publicly? Sounds perfect to me. > Do we need to have all the APIs from...