Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate Testrunner and Hyper-V Modules #453

Closed
pauby opened this issue Oct 20, 2020 · 6 comments
Closed

Deprecate Testrunner and Hyper-V Modules #453

pauby opened this issue Oct 20, 2020 · 6 comments

Comments

@pauby
Copy link
Member

pauby commented Oct 20, 2020

Describe the solution you'd like
The Hyper-V and Testrunner modules don't appear to be used much at all. So we should look at deprecating them in a future version.

@pauby pauby added Improvement Issues that enhances existing functionality, or adds new features 0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue labels Oct 20, 2020
@alias86
Copy link

alias86 commented Oct 27, 2020

What do you guys test with?

About 6 weeks into choco and trying to come up with a basic test frame work

@kirannhegde
Copy link

Hello, @pauby I don't think these modules have to be deprecated. I just started using them and deprecating something which works flawlessly would be not in the larger interest of the Boxstarter community. Unless there is a reliable alternative which can work both Onprem as well as in the cloud, we should continue to keep these modules.

I maintain about 150 chocolatey packages, i am currently updating these packages to be automatic and the ability to test these packages and make them as part of a CI pipeline is extremely important to me.

If there is a strong reason for deprecating these modules, please provide an alternative to these modules. I would like something which scales the underlying infrastructure depending upon the number of choco packages waiting in the queue to be tested as well.

@alias86 If you have come with an alternative mechanism, please let me know. I have explored a few and I did be happy to share them with you as well.

Thanks,
Kiran Hegde

@pauby
Copy link
Member Author

pauby commented Jan 12, 2021

@kirannhegde Thanks for that.

As I said in the original message, the reason we were looking at deprecating them (and this has been a long running thought) is that the modules were not being used and therefore the cost of supporting them wasn't worth it.

However, given your comments perhaps we need to rethink that.

@alias86
Copy link

alias86 commented Jan 12, 2021

@kirannhegde

Hey, thanks for your reply to the thread.

I'm just getting started with Boxstarter, this week.
Just working with a basic script and a HyperV box.

I would be very grateful if you could share some details around your set.

Feel free to PM me

The only other option that I've seen, might be KitchenTest but I'd not tried it

@kirannhegde
Copy link

Hello, @alias86 I am back to my old project of testing Chocolatey packages. Were you able to put together a test framework for testing Choco packages? I am currently also using the Chocolatey Auto updater module to update my Choco packages. So ideally, I would like the testing to be integrated with the Chocolatey auto-update module.

@pauby
Copy link
Member Author

pauby commented Jul 15, 2021

We're getting off-topic on this. The purpose of this thread is to discuss deprecating the Hyper-V and Testrunner modules. As it looks like these are still used then I think we should keep them as part of Boxstarter. However, we may not be able to provide as much support around these.

@pauby pauby closed this as completed Jul 15, 2021
@pauby pauby added Discussion and removed Improvement Issues that enhances existing functionality, or adds new features 0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue labels Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants