Closed janette closed 6 years ago
@janette I think you have a better sense of what needs to happen here - want to create a PR for this and I'll review?
example output ga_gbpw https://jenkins.nuamsdev.com/view/Upgrades/job/Data%20-%20Create%20Site%20Point%20Release%20PRs/378/console
Seems like everything is in place for this to happen:
40 ahoy build update $tag
41 ahoy build config
update:
usage: Updates site USE THIS FOR ALL SITE UPDATES.
cmd: |
ARGS="{{args}}"
if [[ -z "$ARGS" ]]; then
echo "Please provide a Data Starter release (tag) as an argument. Exiting"
exit 0
fi
ahoy build update-dkan-starter "$ARGS"
ahoy build update-custom
update-custom:
hidde: true
usage: Runs all the custom build steps.
cmd: |
ahoy build custom
ahoy build custom-libs
ahoy build overrides
ahoy build config
if [ "$(ahoy custom | grep post-build)" != '' ]
then
ahoy custom post-build
fi
perhaps ahoy build update-custom
is being skipped for some reason
No longer relevant
Description
The config/overrides.make and config/custom.make files were not run on the 1.14 upgrades, need to run
ahoy build remake
to get those items into the build.ahoy custom post-build
on an upgrade...?