summaryrefslogtreecommitdiff
path: root/ci
Commit message (Collapse)AuthorAgeFilesLines
* Add some additonal RPM db cleanup steps missed in #7845Seth Chisamore2018-11-011-1/+3
| | | | Signed-off-by: Seth Chisamore <schisamo@chef.io>
* Automatically rebuild RPM database on EL6 testersschisamo/cleanup-rpmdbSeth Chisamore2018-11-011-0/+12
| | | | | | | | Our tests hammer YUM pretty hard and the EL6 testers get corrupted after some period of time. Rebuilding the RPM database clears up the underlying corruption. We'll do this each test run just to be safe. Signed-off-by: Seth Chisamore <schisamo@chef.io>
* cleanup old rake taskslcg/nuke-shitty-rake-tasksLamont Granquist2018-08-291-9/+0
| | | | | | | | we're calling scripts to call rake tasks to call scripts to call rake tasks to mostly execute shellcodes. this gets rid of at least 2 levels of indirection. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Make sure dep updater has rakeTim Smith2018-08-221-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove the old CI version bump / show scriptsTim Smith2018-08-222-14/+0
| | | | | | We do this all in Expeditor now Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove the existing acceptance testing frameworkkill-acceptanceTim Smith2018-06-261-25/+2
| | | | | | | | 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>
* Revert "Run all tests in CI"Thom May2018-05-011-1/+1
|
* Run all tests in CItm/run_all_tests_in_ciThom May2018-04-251-1/+1
| | | | | | | | | | Previously, we ran only integration tests. But many of our unit tests are constrained by rootyness and platform, and this means the first time they get run is during the ChefDK verification stage, which uses the released Chef build. So we have no way of fixing test failures short of a new Chef release. Signed-off-by: Thom May <thom@chef.io>
* Kill any orphaned testsshain/test_killerScott Hain2018-02-201-0/+3
| | | | Signed-off-by: Scott Hain <shain@chef.io>
* Force deletion of tmpdir with sudoshain/force_delete_tmpdirScott Hain2018-01-161-1/+1
| | | | | | This makes sure we don't fail on the very slim chance that an OS generated file (lookin' at you, AIX) ends up in this directory and blocks deletion. Signed-off-by: Scott Hain <shain@chef.io>
* remove bundle_install.shLamont Granquist2017-05-103-14/+2
| | | | | | | doesn't matter, and if it did we should use the actual bundler trampolining. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* add note to hacklcg/ominbus-bundle-configLamont Granquist2017-05-091-0/+5
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* simplify omnibus config and greenify builds againLamont Granquist2017-05-095-26/+54
| | | | | | | | | | | | | | 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>
* Don't futz with bundle configThom May2017-04-282-4/+0
| | | | Signed-off-by: Thom May <thom@chef.io>
* Replace changelog group with ci groupTom Duffield2017-03-071-1/+1
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Better handle version bumpingtduffield/update-version-bumpingTom Duffield2017-02-222-4/+2
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Bundle with changelog group for version bumpTom Duffield2017-02-101-1/+2
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Make it so you can actually run rake:dependencies locallyTom Duffield2017-02-091-1/+1
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Cleanup Gemfiles, Berksfiles, and update Gemfile groupsTom Duffield2017-02-091-1/+1
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Dont fail the version bump if changelog failsafiune/dont-fail-if-changelog-failsSalim Afiune2016-12-131-1/+1
| | | | Signed-off-by: Salim Afiune <afiune@chef.io>
* Make sure Dockerfile is kept up to dateTom Duffield2016-12-071-0/+1
| | | | | | | | The build system passes in the necessary build arguments, buts its beneficial to have the Dockerfile keep up to date with what the latest stable version is in case people want to build their own. Signed-off-by: Tom Duffield <tom@chef.io>
* Use tduffield branch of github-changelog-generatorTom Duffield2016-12-021-0/+1
| | | | | | | | | | | | 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>
* Disable the automatic changelog generationTom Duffield2016-11-101-1/+0
| | | | | | | | The feature that we thought existed in the changelog generator doesn't work exactly as expected. Until that functionality can be added, we're disabling the automatic changelog generation. Signed-off-by: Tom Duffield <tom@chef.io>
* Add UTF-8 environment var to version bumperTom Duffield2016-11-091-0/+2
| | | | | | | | The Github Changelog Generator threw an error about invalid encoding. This never happened locally, and indications are that its because of this environment variable. Signed-off-by: Tom Duffield <tom@chef.io>
* Update the changelog when the version is bumped by CITom Duffield2016-11-092-1/+2
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Reenable non-windows testsKartik Null Cating-Subramanian2016-07-211-2/+2
|
* Turn all those blasted acceptance tests offstupid1ksubrama/new_acceptanceKartik Null Cating-Subramanian2016-07-131-2/+2
|
* Make chef-config Rakefile run without rspecjk/chef-config-no-rspecJohn Keiser2016-06-061-1/+1
|
* Ensure we install rake in CI (version bump)jk/install-rakeJohn Keiser2016-06-061-1/+1
|
* Install fewer binary dependencies and dependencies in generaljk/install-less-stuffJohn Keiser2016-06-064-5/+6
| | | | when bumping version and updating dependencies
* Use --user-install to allow gem install to happenjk/set-evxJohn Keiser2016-06-011-1/+2
|
* Use desired bundler to bundle installJohn Keiser2016-06-011-3/+3
|
* Add set -evx to shell scriptsJohn Keiser2016-06-014-0/+8
|
* adding shell scripts for the bump bot that will ensure the correct bundler ↵Matt Wrock2016-06-014-0/+20
| | | | version is installed
* copy chef-acceptance suites into $WORKSPACESeth Chisamore2016-05-171-6/+8
| | | | | | | | | | | | | This will ensure the path to the suites can be fully resolved, it prevents errors like: ``` STDERR: /home/jenkins/workspace/chefdk-test/architecture/x86_64/platform/acceptance/project/chefdk/role/tester/vendor/bundle/ruby/2.1.0/gems/mixlib-shellout-2.2.6/lib/mixlib/shellout/unix.rb:183:in `chdir': No such file or directory @ dir_chdir - /home/jenkins/workspace/chefdk-test/architecture/x86_64/platform/acceptance/project/chefdk/role/tester/opscode-ci/.acceptance/acceptance-cookbook (Errno::ENOENT) ```
* Revert "exit 0 -- its how acceptance works"Seth Chisamore2016-05-171-20/+19
| | | | This reverts commit aac62e28ae3112c586f223c48ef7fe360f98e56a.
* exit 0 -- its how acceptance worksMatt Wrock2016-05-171-19/+20
|
* Execute chef-acceptance without elevated privilegesSeth Chisamore2016-05-131-5/+7
| | | | | | | | | | | | We output all data generated during a chef-acceptance run to the workspace of the executing Jenkins job using chef-acceptance's `--data-path` option. If the `chef-acceptance` commands are executed with elevated privileges (using `sudo`) the generated files are owned by `root`: https://gist.github.com/schisamo/7ce7262813f2bc81b7314d9eab53afa0 This is an issue as the generated data cannot be properly archived OR cleaned up when the next job runs: https://gist.github.com/schisamo/b7246987d49534b27b8a4ad72f9ad965
* Add `KITCHEN_CHEF_CHANNEL` value now `ARTIFACTORY_USERNAME` that was removedSeth Chisamore2016-05-101-1/+1
| | | See https://github.com/chef/chef/blob/master/acceptance/.shared/kitchen_acceptance/libraries/kitchen.rb#L19
* Write chef-acceptance data to the Jenkins `$WORKSPACE`Seth Chisamore2016-05-101-1/+1
| | | | | | | | Previously data was being written to the Chef package install path of `/opt/chef/*/acceptance/*` which is bad for numerous reasons. Now that chef/chef-acceptance#39 has been merged we can take advantage of Chef Acceptance's new `--data-path` option which allows us to relocate this directory into the Jenkins job's workspace for easy archiving.
* Remove legacy `ARTIFACTORY_*` env variablesSeth Chisamore2016-05-101-4/+4
| | | | These have not been needed since: chef/mixlib-install#90
* Run the intergration tests in FIPS modeKartik Null Cating-Subramanian2016-04-251-7/+1
|
* Turn off GIT_SSL_NO_VERIFYjk/use-ssl-againJohn Keiser2016-04-191-3/+1
|
* Just use the actual installed bundle instead of reusing the Gemfile to run ↵John Keiser2016-04-182-2/+2
| | | | Chef tess
* Don't update bundler when running acceptance testJohn Keiser2016-04-181-1/+3
|
* Install only core chef plus test when testingJohn Keiser2016-04-182-5/+2
|
* Don't bundle install on testsJohn Keiser2016-04-181-1/+1
|
* Run acceptance from the acceptance dir in the Chef gemJohn Keiser2016-04-181-1/+1
|
* Remove Gemfile.windows and put both platforms in Gemfile.lockJohn Keiser2016-04-182-8/+26
|
* Add --force-destroy to chef-acceptancedanielsdeleo2016-03-221-1/+1
|
View Lorry Controller Status