dotMemoryUnit & cake-contrib

[mgnslndh]

I'm considering open sourcing my Cake tool for JetBrain's dotMemoryUnit .

Is this a good fit for the cake-contrib organization or should I host it in my own repository? What are requirement or process for submitting repositories to be part of the cake-contrib organization?

[pascalberger]

Yes, that's definitely a fit.

The process is documented at https://cakebuild.net/community/cake-contrib and https://github.com/cake-contrib/Home/blob/master/CONTRIBUTING.md for details.

Do you prefer to implement the addin first in our own repo and move it to cake-contrib when ready, or have the repo available in cake-contrib org from the beginning?

[mgnslndh]

Great! Thanks for the links. I think that the first step would be to migrate the existing code to a new public repo under my user. When that is done we could move it to cake-contrib. At that point I will probably need some help or guidance on all the CI/publishing stuff required. Never done that on GitHub before and I guess there are some conventions to follow for cake-contrib.

[pascalberger]

Perfect 👍 Let us know here when you're ready to move the repo the cake-contrib organisation and we can walk with you through the process.

[mgnslndh]

I've made the migration from my private repo to a public repo https://github.com/mgnslndh/Cake.DotMemoryUnit. It is not much original work since I based the tool on the DotCover tool from Cake.Common. They are very similar in the way they need to intercept & control another tool execution. At some point the tool might be ready for the Cake repo instead.

So, what is left to do?

• Building and publishing according to Cake conventions
• Fix missing XML docs and generated documentation
• Add support for additional command line options
  • Only 2/11 are supported since that was all I needed for my scenario

Should I add more command line options and fix XML docs now or are we ready to move to another repo?

[pascalberger]

@mgnslndh You're free to use whatever you prefer. Historically a lot of repos used AppVeyor, but we also have an Azure Pipelines tenant or some projects are using GitHub Actions (e.g. https://github.com/cake-contrib/Cake.ESLint) or a combination of all of them (e.g. https://github.com/cake-contrib/Cake.Issues.Recipe)

[mgnslndh]

@pascalberger I settled on GitHub Actions for CI. However, I'm having some trouble when the build runs the recipe target "Publish-PreRelease-Packages". It tries to upload a preview package to a NuGet source on Azure but accessing that source is denied because of an authorization issue. The recipe/action is based on Cake.ESLint. Do you have any pointers on how to proceed?

https://github.com/cake-contrib/Cake.DotMemoryUnit/actions/runs/11304629640/job/31443989411

[nils-a]

@mgnslndh it seems I'm having the same problem in Cake.ESLint, currently:

https://github.com/cake-contrib/Cake.ESLint/actions/runs/11354870042/job/31583028599#step:6:1179

I'm guessing the PAT used to access the feed has expired.
I'll see if I can find some time tonight to update it.

[nils-a]

@mgnslndh can you try re-running that failed build?

[mgnslndh]

@nils-a it looks like you solved the problem. The package is now pushed but rejected because it is a duplicate. I need to look into versioning. Thanks!