.gitdirectory is found at the orderly root (vimc-4866)
rm(list = ls())(or similar) at the top of scripts as this leads to hard-to-track errors, modifies the global environment and is generally poor practice (vimc-4810)
orderly_workflowin favour of supporting workflows through orderly.server (mrc-2275)
orderly_remote_statusto return details of currently running and queued reports on the remote queue.
max_depthnow truncates depth of the tree instead of throwing error and arg
recursion_limitadded which works how
orderly_infowhich returns details from report runs, both successful and failed (VIMC-4619)
bundle_runwill now save a
orderly_fail.rdsif run fails containing metadata and info about failure reason (VIMC-4037)
orderly_cleanupwill now sanitise the report name passed to it
orderly_cleanupwill now print summary of how many items will be deleted (#265)
use_draftand fixed ID dependency works (#259)
orderly_pull_archiveis now more tolerant of trailing slashes (#260)
orderly_bundle_import_remotewhich create a bundle from a remote and return the completed bundle back to the remote (VIMC-4457)
orderly_bundle_importto accept a filename that has been renamed from
<id>.zip. While this is not generally desirable, it may be needed for some workflows (VIMC-4382)
orderly_bundle_packfailed when the orderly tree and temporary directory were on different filesystems (VIMC-4354)
orderly_bundle_runfailed when using a relative path for a working directory (VIMC-4337)
orderly::orderly_new()works in an orderly repo that does not (yet) have a
orderly::orderly_runnerwhich has been moved to
orderly::orderly_configto return an object representing the config (VIMC-4048)
orderly::orderly_bundle_import. This interface will be expanded and the interface may change somewhat (VIMC-3825)
get_report_parametersto list parameters for a report at a particular commit id (VIMC-3953)
get_reportsto list reports available for a particular branch and commit from orderly_runner (VIMC-3945)
git_commitsto list commits for a particular branch from orderly_runner (VIMC-3941)
git_branches_no_mergedto get unmerged branches from orderly_runner (VIMC-3857)
orderly.logafter a failed run; this primarily impacts the cli runner and then primarily when being run in parallel where the log is not printed to screen (VIMC-3841)
orderly::orderly_workflowallows users to run a “workflow” - a list of reports which to be run in order. Workflows are configured via a yml file in
orderly::orderly_data()has been removed as do not believe anyone was using it, and it is superseded by
fetch). These were not intended for direct use by users (VIMC-3539)
orderly::orderly_run_remote()takes an instance argument to allow users to specify the source DB (VIMC-3698)
orderly::orderly_rebuild()creates a dated backup of the database before running, allowing this potentially destructive operation to be recovered from (VIMC-3702)
orderly batchusing a csv file via
orderly::orderly_remote()for getting an “orderly remote” object, as declared in the
orderly::orderly_batchand with the CLI as
orderly::orderly_searchor when declaring dependencies (VIMC-3538)
orderly_envir.ymlare available during report run (#180, VIMC-3530)
orderly::orderly_develop_*functions are now permissive and allow some invalid
orderly.ymlto continue - in particular, the partially complete template generated by
orderly::orderly_newcan be directly used (VIMC-3510)
orderly::orderly_use_package()which can add a resource, source or packages into the orderly.yml (VIMC-3503)
orderly_develop_clean. These largely supersede
orderly_test_start, though the latter remains for now (VIMC-3404)
use_draft = "newer", no longer pulls in failed drafts (VIMC-3467, reported by @sangeetabhatia03)
pullsub command for pulling dependencies from remote orderly servers (VIMC-3466)
orderly_run.rds. This is not yet reflected in the database and might be tweaked before being added.
orderly_test_start. This will replace the use of explicitly specifying
draft: truein the depends section of
orderly::orderly_dataall get an
instanceargument to support this (VIMC-3302).
.Random.seed, if present (VIMC-3375)
orderly::orderly_test_checkis no longer case sensitive with paths, preventing issues when used from directories that do not have canonical casing (VIMC-3205)
orderly::orderly_test_startand related functions has been severely reduced. Functions
orderly::orderly_test_restarthave been removed and
orderly::orderly_test_startno longer directly provides a useable environment for testing reports (VIMC-3178).
orderly.yml, and the format has altered slightly (VIMC-2413, #8).
set_default_remotehave been removed (VIMC-2946, deprecated in VIMC-2944 / 0.7.2).
orderly_migratecan now clean up old migration backup files. These should generally be quite safe to delete, but it would be better to do this directly from
orderly_runnow checks for sink imbalance, in the same way that device imbalances are currently checked for, preventing odd errors when sinks are left open or too many are closed (VIMC-3129)
orderlydb, and also pulls all dependent reports (VIMC-2855, VIMC-3054).
orderly_config.ymlnow has an “args” section, rather than guessing arguments. Old configurations are valid, with a warning to update (VIMC-1986).
unzip_archivehas been removed in preparation for release.
push_archive(previously marked as experimental and not implemented for anything other than file remotes) has been removed. We may reconsider this again in the future.
pull_dependencieshave been deprecated in favour of
orderly_runas these were not widely used (VIMC-2945)
custom_fields(holding metadata about the fields) and
report_version_custom_fields(linking these to the report versions) (VIMC-2768)
orderly_runner) will now periodically backup the destination database, which will be useful in cases where other applications store information in it (VIMC-2882)
configargument to exported functions has been renamed to
rootto better reflect what is expected to be passed in (VIMC-2919)
orderly_run.ymlscript has now been removed and
orderly_run.rdsis the sole source of truth for the
orderlyrun metadata (VIMC-2873).
README.mdfiles are automatically copied as resources from source folder. Additionally it is an error to include
README.mdas an artefact (VIMC-2230)
timeoutthrough to remote runners when using the
master_onlyconfiguration option and can prevent running reports with references other than
master. This is now enforced entirely on the server (VIMC-2642)
changelogtable includes the attributable public report version attributable to each changelog entry
orderlynow prompts to install missing packages and offers code to help with this (VIMC-2384)
orderly runon the command line accepts message entries (VIMC-2363, VIMC-1797)
orderlychecks that the resources were not modified during running a report (VIMC-2137)
README.mdis automatically treated as resource if present (VIMC-2230)
montagupackage is no longer used directly by
orderly(VIMC-2453) - instead we use a similar “driver” approach to the database connections. This paves the way for an eventual CRAN release (VIMC-2421).
orderlynow indicates the version that failed to run, and can move failed versions aside to complete migration of the rest of an archive.
orderlyworks with report repository clones that lack an
descriptionfields are correctly copied into the new
connectioncolumn in the
orderly’s database (VIMC-2327)
orderly_rebuild) only on a schema change (VIMC-2280)
orderly_test_startfails on startup (VIMC-1870)
orderlyroot if available, then falling back on the version in the package.
push_archive, the inverse of
pull_archivefor copying an archive report elsewhere (VIMC-1811). Currently only supported for
remoteas a path.
orderly::orderly_run_info()can return information about the current run, including information on dependencies.
--fetchargument, used when
--refis specified to run
git fetchbefore resolving
orderlyrunner looks up the
refat the point of queuing, rather than the point of running
remote. The structure here will probably change a little further in a future version.