Use Windows runner in GitHub Actions, use python/invoke instead of ruby/rake. #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- experimenting on setting `VIRTUAL_ENV` environment variable to point into environment rcc created environment - made OS and architecture visible in rcc "Progress 2" marker
- fixing codeql-analysis settings and problems - no codeql analysis for ruby or python in this repo
- retry on fixing codeql-analysis problem
- holotree share enabling now uses "icals" in Windows to set default properties - added marker file "shared.yes" when shared has been executed
- added `--once` flag to holotree shared enabling, in cases where costly sharing is required only once
- micromamba upgrade to v0.24.0
- fixed table of contents links to match Github generated ones - also tried to make toc.py more OS neutral (was failing on Windows)
- refactoring module dependencies to help reusing parts of rcc in other apps
- micromamba upgrade to v0.25.1 - template upgrade of python to 3.9.13 - template upgrade of pip to 22.1.2 - template upgrade of rpaframework to 15.6.0 - upgraded tests to match above version changes and their effects
- fix started: adding missing symbolic link handling of files and directories - this will be UNSTABLE, work in progress, for now
- fix continued: adding missing symbolic link handling of files and directories
- bugfix: adding missing symbolic link handling of files and directories - hololib catalogs now have rcc version information included - added timeout to account deletion, to speed up unit tests
- new cleanup option `--downloads` to remove downloads caches (conda, pip, and templates) - change: now conda pkgs is cleaned up also in quick cleanup (which now includes all "downloads" cleanups) - robot cache is now part of full cleanup - run commands now cleanup their temp folders immediately
- new global flag `--no-build` which prevents building environments, and only allows using previously cached, prebuild or imported holotrees - there is also "no-build" option in "settings.yaml" options section - added "no-build" information to diagnostics output
- bug: empty entry on ignoreFiles caused unclear error - fix: now empty entries are diagnosed and noted - fix: also non-existing ignore files are diagnosed
- feature: allow holotree exporting using robot.yaml file.
- added support to tracking when catalog blueprints are used - if there is no tracking info on existing catalog, first reporting will reset it to zero (and report it as -1) - added catalog age in days, and days since last used to catalog listing - fixed bug on shared hololib location on catalog listing
- new command `rcc holotree remove` added, and this will remove catalogs from holotree library (hololib) - added repeat count to holotree check command (used also from remove command)
- fix: using wrong file for age calculation on holotree catalogs
- fix: holotree check failed to recover on corrupted files; now failure
leads to removal of broken file
- fix: empty hololib directories are now removed on holotree check
- added unused option to holotree catalog removal command - added maintenance related robot test suite - minor documentation updates
- refactoring some utility functions to more common locations - adding rcc and micromamba binary locations to diagnostics - added `RCC_EXE` environment variable available for robots - added `RCC_NO_BUILD` environment variable support (in addition to previous settings options and CLI flag; see v11.19.0) - some documentation updates - added support for toplevel `--version` option
- flag to show identity.yaml (conda.yaml) in holotree catalogs listing and functionality then just show it as part of output, both human readable and machine readable (JSON)
- fix: symbolic link restoration, when target is actually non-symlink
- experiment: pyvenv.cfg file written into created holotree before lifting - update: cloud-linking in setting.yaml now points to new default location: https://cloud.robocorp.com/link/ - bugfix: settings.yaml version updated to 2022.09 (because options section)
- minor documentation improvement, highlighting configuration settings help, that plain commands are showing vanilla rcc setting by default.
- compression flag is now globally accessible - compression flag also switches using siphash as identity hasher - dirtyness stats also now lists duplicates and linked files
- cleanup improvement with option `--caches` to remove conda/pip/uv/hololib caches but leave holotree available - also environment building now cleans up "building" space both before and after environment is build
* Fixed link to long paths documentation * Removed Automation Studio mention
- micromamba upgrade to v1.5.8
- bug: when first build failed, original layers were expected to still be there - fix: now second build always builds all layers (since failure needs that)
- feature: `--no-retry-build` flag for tools to prevent rcc doing retry environment build in case of first build fails
- when pip dependencies has `--use-feature=truststore` those environments are identified as cacheable - removed some robot.yaml file diagnostic checks since those are not valid anymore
- adding support for `package.yaml` as replacement for `conda.yaml`
- bugfix: when exporting prebuild environments, include layer catalogs also - bugfix: exporting was not adding all environments correctly to .zip file
- bugfix: more places are now using package/conda YAML loading
- bugfix: when there is "rcc point of view" message, it was not showing who was controller, so now controller is visible
- bugfix: when taking locks, some of those need to be in shared directory, while others should not; code was making too much directories shared
- MAJOR breaking change: rcc will now live in two product domains, Robocorp and Sema4.ai - feature: initial support for `--sema4ai` strategy selection - robot tests to test Sema4.ai support
- added company name as strategy name (dynamic name handling for user messages) - replaced static "Robocorp" references with strategy name - renamed some Robocorp functions to more generic Product functions
- default `settings.yaml` is now behind product strategy (each product can have their own default settings)
- Windows bugfix: icacls now applied on shared holotree location from product strategy (was hardcoded before)
- Additional `--robocorp` product flag added. To match `--sema4ai` flag. - Now using `%ProgramData%` instead of hard coded `c:\ProgramData\` in code. - Update on default `settings.yaml` for Sema4.ai products.
- MAJOR breaking change: now command `rcc configuration settings` will require `--defaults` flag to show defaults template. Without it, default functionality now is to show effective/active settings in YAML format.
- new command `feedback batch` for applications to send many metrics at once - disabling rcc internal metrics based on product strategy - bug fix: journal appending as more atomic operation (just one write)
- bug fix: too many commands were only visible with `--robocorp` product strategy, but they are needed also in `--sema4ai` strategy
- updated default settings.yaml for Sema4.ai products. - templates location also back in Sema4.ai settings.yaml. - documentation updates
- bugfix: tlsCheck was giving nil TLS information without error - CONTRIBUTING.md -- things to note when developing rcc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.