Downloads:

167

Downloads of v 0.0.1:

127

Last Update:

24 Apr 2018

Package Maintainer(s):

Software Author(s):

  • bcurran3

Tags:

bcurran3 unofficial choco upgrade all abort cup config schtasks scheduled task

(unofficial) Choco Upgrade All at Abort (Task)

Downloads:

167

Downloads of v 0.0.1:

127

Maintainer(s):

Software Author(s):

  • bcurran3

(unofficial) Choco Upgrade All at Abort (Task)

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

This package was rejected on 07 May 2018. The reviewer gep13 has listed the following reason(s):

bcurran3 (maintainer) on 23 Apr 2018 13:29:08 +00:00:

User 'bcurran3' (maintainer) submitted package.

chocolatey-ops (reviewer) on 23 Apr 2018 14:04:54 +00:00:

choco-upgrade-all-at-abort has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Package contains dependencies with no specified version. You should at least specify a minimum version of a dependency. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 23 Apr 2018 14:16:02 +00:00:

choco-upgrade-all-at-abort has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/f1c2f390d96492ed74c89a9ae9b45abc for details.
This is an FYI only. There is no action you need to take.

bcurran3 (maintainer) on 23 Apr 2018 21:44:52 +00:00:

User 'bcurran3' (maintainer) submitted package.

chocolatey-ops (reviewer) on 23 Apr 2018 22:20:53 +00:00:

choco-upgrade-all-at-abort has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Package contains dependencies with no specified version. You should at least specify a minimum version of a dependency. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 23 Apr 2018 22:21:47 +00:00:

choco-upgrade-all-at-abort has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/4b9472313f15b40eb9fedbcfa24491b4 for details.
This is an FYI only. There is no action you need to take.

bcurran3 (maintainer) on 24 Apr 2018 04:27:14 +00:00:

User 'bcurran3' (maintainer) submitted package.

chocolatey-ops (reviewer) on 24 Apr 2018 05:02:08 +00:00:

choco-upgrade-all-at-abort has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Package contains dependencies with no specified version. You should at least specify a minimum version of a dependency. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 24 Apr 2018 05:12:24 +00:00:

choco-upgrade-all-at-abort has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/bad29c0d0b688fd1cf34ef83d0b10609 for details.
This is an FYI only. There is no action you need to take.

bcurran3 (maintainer) on 24 Apr 2018 10:46:14 +00:00:

User 'bcurran3' (maintainer) submitted package.

chocolatey-ops (reviewer) on 24 Apr 2018 11:17:46 +00:00:

choco-upgrade-all-at-abort has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Package contains dependencies with no specified version. You should at least specify a minimum version of a dependency. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 24 Apr 2018 11:29:21 +00:00:

choco-upgrade-all-at-abort has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/25809261fef3cf754ac41e78216c02c2 for details.
This is an FYI only. There is no action you need to take.

bcurran3 (maintainer) on 25 Apr 2018 09:43:11 +00:00:

In hindsight now I'm wondering if I should just add an ABORTTASK option right into choco-upgrade-all-at. Thoughts?

gep13 (reviewer) on 25 Apr 2018 10:08:38 +00:00:

You mean to allow for overriding/removing of an existing task during the installation?

bcurran3 (maintainer) on 25 Apr 2018 10:56:24 +00:00:

I mean to add the 2nd task (the kill task) as an option in the main script. Shouldn't be to hard. Just complicates installation.

bcurran3 (maintainer) on 25 Apr 2018 11:07:44 +00:00:

I mean to add the 2nd task (the kill task) as an option in the main script. Shouldn't be to hard. Just complicates installation.

gep13 (reviewer) on 26 Apr 2018 08:00:31 +00:00:

Sounds like a good idea to me.

bcurran3 (maintainer) on 06 May 2018 11:31:06 +00:00:

Please reject, choco-upgrade-all-at has been upgraded with this feature.

gep13 (reviewer) on 07 May 2018 08:50:23 +00:00:

Rejecting as per maintainer request.
Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

IF YOU USE choco-upgrade-all-at, YOU WANT THIS TOO!

...BECAUSE SOMETIMES PACKAGE INSTALLATIONS GO WRONG.

This is a companion package for choco-upgrade-all-at.

This package creates a Windows Scheduled Task to run "taskkill /im choco.exe /f /t" at a time you specify. The command "taskkill /im choco.exe /f /t" will stop the Chocolatey (choco.exe) process and all child processes.

"Um, why do I want this?" you're thinking. You want this because sometimes background package installations go wrong. "Go wrong?" you're thinking. Yes, there are a couple scenarios where a Chocolatey package installation/upgrade can hang: if a package needs input, if an AutoHotKey or AutoIt script fails, and all those times a program installer pops up a browser window to tell you "Thank you." These scenarios leave hung processes in the background with no way for you to easily interact with them (They're in the background!). This means they are taking up memory resources for no reason and might cause problems installing other packages or programs. If you knew there was a hung process, you could manually stop the task, but who wants to check every day? This will automate checking and stopping any Chocolatey package hung tasks at the time you specify. I recommend setting it to a time an hour or two after you run choco-upgrade-all-at.

INSTRUCTIONS:

You can set the time by running choco install choco-upgrade-all-at-abort --params "'/ABORTTIME:XX:XX'" where XX:XX equals the "Military Time" to stop Chocolatey updates. Not entering the correct format will fail the install. Please see the examples.

INSTALL EXAMPLES:

  • choco install choco-upgrade-all-at-abort --params "'/ABORTTIME:03:00'" - stops Chocolaty updates at 3 AM
  • choco install choco-upgrade-all-at-abort --params "'/ABORTTIME:06:30'" - stops Chocolaty updates at 6:30 AM
  • choco install choco-upgrade-all-at-abort --params "'/ABORTTIME:20:00'" - stops Chocolaty updates at 8 PM
  • choco install choco-upgrade-all-at-abort --params "'/ABORTTIME:23:30'" - stops Chocolaty updates at 11:30 PM

A NOTE ON DEFAULTS:

  • If you don't specify any parameters, choco-upgrade-all-at-abort defaults to running daily at 4 AM. (My preference!) This was chosen since the default runtime for choco-upgrade-all-at is 2 AM which gives 2 hours for updates to run before aborting if necessary.

PACKAGE NOTES


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'
$packageName = 'choco-upgrade-all-at-abort'
$pp          = Get-PackageParameters
   
Write-Host "" 
Write-Host "choco-upgrade-all-at-abort Summary:" -foreground magenta

if ($pp["ABORTTIME"] -eq $null -or $pp["ABORTTIME"] -eq ''){
      Write-Host " * ABORTTIME NOT specified, defaulting to 04:00." -foreground magenta
	  $AbortTime = "04:00"
    } else {
	  $AbortTime = $pp["ABORTTIME"]
	  Write-Host " * ABORTTIME specified as $AbortTime." -foreground magenta
    } 
SchTasks /CREATE /SC DAILY /RU SYSTEM /RL HIGHEST /TN choco-upgrade-all-at-abort /TR "taskkill /im choco.exe /f /t" /ST $AbortTime /F
SchTasks /query /tn "choco-upgrade-all-at-abort"
tools\chocolateyuninstall.ps1
$packageName = 'choco-upgrade-all-at-abort'

SchTasks /Delete /TN choco-upgrade-all-at-abort /F

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Discussion for the (unofficial) Choco Upgrade All at Abort (Task) Package

Ground Rules:

  • This discussion is only about (unofficial) Choco Upgrade All at Abort (Task) and the (unofficial) Choco Upgrade All at Abort (Task) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or (unofficial) Choco Upgrade All at Abort (Task), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus