summaryrefslogtreecommitdiff
path: root/.expeditor/update_dep.sh
Commit message (Collapse)AuthorAgeFilesLines
* Make sure we can run dep update on 2+ branchesTim Smith2021-05-211-1/+1
| | | | | | | | We need to make sure we create pr release branches. Right now the chef-16 one gets the branch and then the master one uses that same branch and the PR is busted. Signed-off-by: Tim Smith <tsmith@chef.io>
* Update update_dep to allow passing in the dep to updateTim Smith2021-03-011-5/+8
| | | | | | | We need to know the dep we're updating throughout this script and if it's not a gem we don't know the name. Allow passing in the name via arg Signed-off-by: Tim Smith <tsmith@chef.io>
* Switch expeditor gem updating to use bundle lockTim Smith2019-05-081-3/+1
| | | | | | This should still get us an update without removing the lockfile first which resulted in the new file being written out as a Bundler 2.x file. Signed-off-by: Tim Smith <tsmith@chef.io>
* Attempt a convervative bundle update when bumpin chef versionsTim Smith2019-03-191-3/+0
| | | | | | This should keep out other deps. Signed-off-by: Tim Smith <tsmith@chef.io>
* Pin expeditor to ruby 2.5.3 and bump train to 1.7.6Tim Smith2019-03-191-0/+3
| | | | | | Expeditor keeps incorrectly bumping addressable to 2.5.2, which seems like some sort of ruby/bundler bug, which is breaking builds. We're attempting to switch back to ruby 2.5.3. in expeditor to see if that resolves the bumping issues. Signed-off-by: Tim Smith <tsmith@chef.io>
* Open the PR against the appropriate release branchTom Duffield2019-02-191-1/+1
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Update scripts to use new EXPEDITOR_ environment variablestduffield/new-envvarsTom Duffield2019-02-191-5/+5
| | | | Signed-off-by: Tom Duffield <tom@chef.io>
* Pull in the gem update retry logic from DKTim Smith2019-01-161-6/+15
| | | | | | | | Pulls in the logic that tyler wrote in DK that performs retries and validates that the gem was actually updated. This preventts empty PRs from being opened and shortens the time the job takes to run. Signed-off-by: Tim Smith <tsmith@chef.io>
* Update the sleep to 240 secondsexpeditor_fixTim Smith2018-09-071-1/+1
| | | | | | | 120 seconds wasn't enough for some jobs. Let's give Rubygems plenty of tim to have the correct information. Signed-off-by: Tim Smith <tsmith@chef.io>
* cleanup old rake taskslcg/nuke-shitty-rake-tasksLamont Granquist2018-08-291-1/+2
| | | | | | | | 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>
* Add a 120 second sleep to the dependency bumpingsleep_expeditorTim Smith2018-08-231-0/+5
| | | | | | See if waiting 2 minutes gives rubygems time to catch up. Signed-off-by: Tim Smith <tsmith@chef.io>
* More wording updatesTim Smith2018-08-231-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Explain what our expeditor scripts are doingTim Smith2018-08-231-1/+13
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Use obvious fix in the dep update scriptTim Smith2018-08-221-1/+1
| | | | | | This is probably a better idea legally vs. having a bot sign off the DCO. Same change was done in DK already. Signed-off-by: Tim Smith <tsmith@chef.io>
* DCO sign off the version bumpTim Smith2018-08-221-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Fix how dep bumping worksTim Smith2018-08-221-2/+3
| | | | | | Update this to the same script we use in DK Signed-off-by: Tim Smith <tsmith@chef.io>
* Fix bundle update syntax in update_dep.shTim Smith2018-08-091-1/+1
| | | | | | Don't confuse gem and bundler flags. Signed-off-by: Tim Smith <tsmith@chef.io>
* bundle update the exact version we wantTim Smith2018-08-081-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Automatically open PRs on dep gem updatesTim Smith2018-08-081-0/+17
This uses expeditor subscriptions to automatically cut a PR to update gems when a dependent Chef managed gem is pushed to rubygems. Signed-off-by: Tim Smith <tsmith@chef.io>
View Lorry Controller Status