summaryrefslogtreecommitdiff
path: root/tasks
Commit message (Collapse)AuthorAgeFilesLines
* Update the announcement rake task with kitchen examplesannouncementTim Smith2018-08-243-1/+18
| | | | | | This was in DK before, but it made no sense there. This might convince some folks to test things when we cut a pre-release. Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove task to bump audit cookbook depsTim Smith2018-07-231-14/+0
| | | | | | This cookbook is gone and this causes this job to fail Signed-off-by: Tim Smith <tsmith@chef.io>
* fix Style/MutableConstantLamont Granquist2018-07-021-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fix Style/PreferredHashMethodsLamont Granquist2018-07-022-6/+6
| | | | | | | absolutely hard requirement on the fixes that went into chef-config 2.2.11, so the floor of that gem is bumped up. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fix Style/UnneededInterpolationLamont Granquist2018-07-021-2/+2
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fix Style/HashSyntaxLamont Granquist2018-07-024-9/+9
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Remove the existing acceptance testing frameworkkill-acceptanceTim Smith2018-06-261-2/+0
| | | | | | | | We haven't used this framework for 2 major releases of Chef and as time goes on it's more and more likely we'll build something very different for testing. We 100% do need acceptance testing, but between dokken testing in Travis and the potential for more complex integration testing with build-kite I think we should do the proper cleanup and remove this code now. Signed-off-by: Tim Smith <tsmith@chef.io>
* test chef-zero against chef_fs in the chef/chef checkoutLamont Granquist2018-04-231-2/+6
| | | | | | goes red because we're really red here Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* require bundlerLamont Granquist2018-02-281-1/+3
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Revert "splice git checkout of chef into external tests"Lamont Granquist2018-01-241-3/+0
| | | | This reverts commit 2865ca316e5b9512ffd8a7d784355e469a115717.
* splice git checkout of chef into external testsLamont Granquist2018-01-241-0/+3
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* prepping for rubocop 0.52.1lcg/rubocop-0.52.1Lamont Granquist2018-01-172-4/+4
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Remove the Gemfile.lock and Berksfile.lock for kitchen testsintegration_docsTim Smith2017-12-221-5/+0
| | | | | | We're probably going to see some more failures with this change, but that's a good thing. If we have a bad kitchen change or a bad cookbook change we'll know now earlier. Less impact == better. Signed-off-by: Tim Smith <tsmith@chef.io>
* Break out unit/integration/functional tests in travis and test chef-configTim Smith2017-12-201-1/+1
| | | | | | Add the chef-config unit tests to the unit testing group Signed-off-by: Tim Smith <tsmith@chef.io>
* Ensure that our maintainers are all syncedtm/update_maintainersThom May2017-08-311-3/+3
| | | | Signed-off-by: Thom May <thom@may.lt>
* Merge pull request #6287 from chef/tduffield/use-new-artifact-actionsTom Duffield2017-07-272-78/+0
|\ | | | | Update Expeditor config to use new Merge and Artifact Actions
| * Update Expeditor config to use new Merge and Artifact Actionstduffield/use-new-artifact-actionsTom Duffield2017-07-242-78/+0
| | | | | | | | | | | | | | | | | | | | Chef Expeditor now supports built in merge and artifact actions which allow us to reduce the burden of duplicating common processes across all our repositories. This change introduces several of these built_in functions, replacing functionality that was previously kept in our Rakefile. Signed-off-by: Tom Duffield <tom@chef.io>
* | Updating / fixing deps to fix acceptance (#6292)Bryan McLellan2017-07-241-1/+0
|/ | | | | | | | | | * Remove call to update_omnibus_overrides The rake tasks `update_omnibus_overrides` was removed in dafd5139338aed684410e311b9be906b346db678. * Update acceptance/Gemfile.lock to match Gemfile.lock for mixlib-shellout This should fix acceptance where we're seeing both mixlib-shellout 2.3.1 and 2.3.2.
* Remove bundle tasks, version_policy.rb and update READMELamont Granquist2017-06-012-115/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Update RELEASE_NOTES for 13.1tm/13_1_relnotesThom May2017-05-261-1/+3
| | | | Signed-off-by: Thom May <thom@chef.io>
* simplify omnibus config and greenify builds againLamont Granquist2017-05-093-500/+2
| | | | | | | | | | | | | | this is also necessary for bundler-1.14.x i'm still not entirely clear why we ever needed all the fussy software gem configs or what the build-chef / build-chef-gem infrastructure ever did for us. it seems to have been mostly micro-optimization around building the software gems before bundle installing the project in order to take advantage of git caching. i aggressively don't care about that, this is quite fast enough. we can install nokogiri and libgecode early and that should take care of 98% of the build optimization issue. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* major testing overhaullcg/simplify-external-testsLamont Granquist2017-04-253-52/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | See the PR comments for more philosophical background. This simplifies the external tests. The major feature here is that halite, poise, chefspec, etc are removed from the Gemfile.lock and the transitive Gemfile splicing is gone from the external tests. We're back to simply tracking master on external projects and bundle installing without locks and going red if the break. Those external projects should all similarly track master of chef/chef to reduce the possibility that they break us here. This also bumps bundler to 1.14.x and unblocks us there. It continues to simplify our use of bundler to be more mainstream and less impenetrable. There was some crazy shit that I found where I had to remove env vars like BUNDLE_ENABLE_TRAMPOLINE and the BUNDLE_IGNORE_CONFIG and BUNDLE_FROZEN env vars in appveyor along with the .bundle/config frozen setting were necessary to unbreak appveyor. We seem to have gotten very far afield of standard bundler usage and it was breaking in strange to debug ways. Oddly enough this exposed weird errors in the chef-config/spec/units/fips_spec.rb tests where we need to require the "win32/registry" file there now even though I can't figure out why that broke or how it was working previously. Also, adding x64-mingw32 to x86-mingw32 was necessary to test in appveyor on 64-bit windows (I tried universal-mingw32 and that failed) which seems obvious and is another case that I don't understand how it was working in bundler 1.12.x Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fetch latest stable version only if its requiredRanjib Dey2017-04-171-1/+3
|
* also remove now-unused binstubsLamont Granquist2017-04-034-86/+0
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fix and simplify rake bundle:* commandsLamont Granquist2017-04-033-146/+15
| | | | | | | | | | | | applies the same kinds of fixes that i applied to rake dependencies:* and mostly reverts to mainline usage of bundler. abandons all the trampolining, and uses the platforms that are already locked in the Gemfile.lock and unwinds the multi-platform stuff that bundler does natively now. removes the BundleUtil module entirely since it is no longer used. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* bumping everythingLamont Granquist2017-03-281-18/+22
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* simplify dependency bumping rake tasks and bump all depsLamont Granquist2017-03-101-47/+34
| | | | | | | this eliminates all the "run gem pristine" warning spam and i believe uses "bundle lock" correctly. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Revert "simplify dependency bumping rake tasks and bump all deps"Lamont Granquist2017-03-101-34/+47
| | | | | | This reverts commit 6628f708acdefe2fc6bff85a1edade89f0b4d8ee. oops.
* simplify dependency bumping rake tasks and bump all depsLamont Granquist2017-03-101-47/+34
| | | | | | | this eliminates all the "run gem pristine" warning spam and i believe uses "bundle lock" correctly. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Bump patch not minorTom Duffield2017-03-071-1/+1
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Better handle version bumpingtduffield/update-version-bumpingTom Duffield2017-02-221-0/+41
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Don't ignore issues when generating the changelogtduffield/reintroduce-issues-to-changelogTom Duffield2017-02-101-1/+0
| | | | | | We need them to sort the pull requests by type. Signed-off-by: Tom Duffield <tom@chef.io>
* Add back a few gems that are required (and document why)Tom Duffield2017-02-091-0/+6
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Make it so you can actually run rake:dependencies locallyTom Duffield2017-02-091-4/+14
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* ignore things properlytm/fix_changelog_generatorThom May2017-02-081-1/+2
| | | | Signed-off-by: Thom May <thom@chef.io>
* Pull kitchen language out of release announcementstduffield/use-dokken-in-announcementsTom Duffield2016-12-082-35/+0
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Show how to use chef/chef image in announcementsTom Duffield2016-12-072-0/+18
| | | | | | | Update the release announcements to show how to pull in the latest version of Chef using kitchen-dokken. Signed-off-by: Tom Duffield <tom@chef.io>
* Use new downloads.chef.io URLs for announcementstduffield/add-url-to-announcement-templateTom Duffield2016-12-072-2/+2
| | | | | | | The product download pages now leverage predictable URLS, so our generators can leverage those to improve the download experience. Signed-off-by: Tom Duffield <tom@chef.io>
* fix Style/SpaceInsideStringInterpolationLamont Granquist2016-12-061-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fix Style/SelfAssignmentLamont Granquist2016-12-061-2/+2
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Use badge in CHANGELOGtduffield/tweak-changelogTom Duffield2016-12-051-1/+1
| | | | | | | Use the badge in the changelog so the current stable version is shown regardless of when the CHANGELOG is viewed. Signed-off-by: Tom Duffield <tom@chef.io>
* Use tduffield branch of github-changelog-generatorTom Duffield2016-12-021-9/+12
| | | | | | | | | | | | This branch fixes a number of bugs in the changelog generator, and supports the type of behavior that we want when generating our changelog. There is a PR open against upstream (skywinder/github-changelog-generator#453) to merge this upstream. As part of this, we can now generate the changelog on every commit. Signed-off-by: Tom Duffield <tom@chef.io>
* Fix typo in release templatestduffield/add-announcement-generatorTom Duffield2016-11-212-2/+2
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Fix chefstyleTom Duffield2016-11-211-2/+2
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Make maj_minor version first class in announcement generatorTom Duffield2016-11-213-4/+5
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Add rake task for generator release annoucnementsTom Duffield2016-11-213-0/+126
| | | | | | | | | To ensure consistency, and to let users get the information they want/need at a glance, we're introducing release announcement templates. The Chef release team will use these tasks to generate the release announcements before posting them to Discourse. Signed-off-by: Tom Duffield <tom@chef.io>
* Use the `changelog` namespace for Rake tasksTom Duffield2016-11-091-22/+21
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Add gem release badge to the readme / changelog header (#5527)Tim Smith2016-11-081-0/+1
| | | | | When we update our changelog it’s a bit confusing since multiple days go by before we ship the new release. Adding a header to the changelog and a readme gem release badge should help clear up what our current release actually is. Signed-off-by: Tim Smith <tsmith@chef.io>
* Update changelog generator to better fill our pattern (#5515)Tom Duffield2016-11-041-2/+19
| | | | | | | | | | | | | | | | | | | | | * Update changelog generator to better fill our pattern Configure the changelog generator to better fit our current pattern of changelogs. By utilizing the HISTORY.md file, we can generate a combined changelog of the latest version from HISTORY.md to now. Then, when we cut a release we can simply move our current changelog into HISTORY.md (using the appropriate rake task) and start the process over again. This might even be a first step to having the Chef Versioner generate the changelog automatically for us each time it bumps the version, and then we just need to groom it as we go along. Signed-off-by: Tom Duffield <tom@chef.io> * Add HISTORY.md for the 12.15.19 release Signed-off-by: Tom Duffield <tom@chef.io>
* Merge pull request #5225 from chef/bundle_lock_fixMatt Wrock2016-08-222-0/+28
|\ | | | | Add monkey patch to fix bundle locks for platforms
View Lorry Controller Status