Buildtimetrend

Latest version: v0.3

Safety actively analyzes 619494 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

0.4

- use Keen.io API cache when retrieving project list
- issue 117 : Support Python 2/3
- move dashboard related functions from keenio to dashboard and rename them :
* keenio.get_dashboard_config() -> dashboard.get_config_string()
* keenio.get_dashboard_config_dict() -> dashboard.get_config_dict()
* keenio.generate_dashboard_config_file() -> dashboard.generate_config_file()
- issue 133 : rename deprecated unittest assertions
- move travis related functions and classes to seperate files in the travis submodule :
* connector :
* travis.TravisConnector -> travis.connector.TravisConnector
* travis.TravisOrgConnector -> travis.connector.TravisOrgConnector
* parser :
* travis.TravisData -> travis.parser.TravisData
* substage :
* travis.TravisSubstage -> travis.substage.TravisSubstage
* env_var :
* travis.load_travis_env_vars -> travis.env_var.load_all (calls all other functions)
-> travis.env_var.load_general_env_vars
* travis.load_build_matrix_env_vars -> travis.env_var.load_build_matrix_env_vars
* travis.load_travis_pr_env_vars -> travis.env_var.load_travis_pr_env_vars
* tools :
* travis.convert_build_result -> travis.tools.convert_build_result
* travis.process_notification_payload -> travis.tools.process_notification_payload
* travis.check_authorization -> travis.tools.check_authorization
- issue 124 : specify level of detail when storing build job data, with
`data_detail` and `repo_data_detail` config settings and BTT_DATA_DETAIL env var
- issue 140 : properly check if all required components exist in Travis job config
- rename methods :
* keenio.keen_io_generate_read_key() -> keenio.generate_read_key()
* keenio.keen_io_generate_write_key() -> keenio.generate_write_key()
* keenio.keen_has_project_id() -> keenio.has_project_id()
* keenio.keen_has_master_key() -> keenio.has_master_key()
* keenio.keen_has_write_key() -> keenio.has_write_key()
* keenio.keen_has_read_key() -> keenio.has_read_key()
* keenio.keen_is_readable() -> keenio.is_readable()
* keenio.keen_is_writable() -> keenio.is_writable()
* keenio.keen_add_event() -> keenio.add_event()
* keenio.keen_add_events() -> keenio.add_events()
- issue 38 : add keenio.get_days_since_fail()

0.3

- move buildtimetrend.tools.get_logger() to buildtimetrend.get_logger() and create buildtimetrend.logger shortcut
- issue 76 : check if build exists in Keen.io datastore
- TravisData.process_build_logs() returns a generator
- issue 85 : create a TravisConnector class and move methods json_request and download_job_log there
- move is_repo_allowed(), check_process_parameters() and format_duration() from service to library
- service.format_duration() rounds to full seconds
- check_list() renamed to is_list(), with 'name' as an optional parameter
- keenio.add_project_info_dict() : override project_name in event header with build_job repo
- check_process_parameters() is split into validate_travis_request() and validate_task_parameters()
- issue 69 : use Keen.io query caching to speed up badge generation
- issue 8 : add keen_io_generate_write_key()
- issue 91 : store pull_request related data
- issue 89 : add settings to configure batch mode to process multiple builds
- issue 96 : catch error when started_at or finished_at timestamp is invalid
- add get_items_with_summary() method to Collection class
- issue 23 : load Travis CI build matrix settings
- rename class Build to BuildJob, and file build.py to buildjob.py
- add is_string() test
- issue 126 : improve Keen.io API connection error handling

0.2

- issue 29 : run sync-buildtime-trend-with-gh-pages.sh in after_script
- issue 28 : improve documentation on assigning Keen.io access keys
- issue 30 : add timestamp event names that cause analysis to end
- issue 19 : update Keen.io charts using query request refresh function
- issue 26 : add chart displaying builds per time of day or day of week
- issue 44 : Display buildtime averages of different timeframes in the same chart
- replace print statements by logging methods
- issue 34 : Parse Travis CI logfile to retrieve timing info
- issue 24 : Assign Travis CI started and finished timestamps to build job
- method keenio.keen_io_writable() renamed to keenio.keen_is_writable()
- method keenio.keen_io_readable() renamed to keenio.keen_is_readable()
- issue 55 : get_logger() returns buildtimetrend logger object
- issue 15 : use Keen.io dashboard template for trends dashboard
- issue 58 : split project in a library (current project) and a client, see https://github.com/buildtimetrend/python-client
- change license to GNU Affero General Public License v3 or later (AGPLv3+)
- issue 6 : create Settings class
- issue 7 : populate Settings class with Travis CI environment variables
- issue 60 : check if API result contains builds
- issue 33 : add microseconds when logging a timestamp
- set loglevel with environment variable BTT_LOGLEVEL and config file setting
- issue 67 : check if Travis CI notification payload is unicode
- issue 17 : add status badges to dashboard
- [keenio] rename generate_overview_config_file to generate_dashboard_config_file
- issue 68 : catch KeenApiError
- issue 46 : use Travis CI build config to assign missing (sub)stage names
- [keenio] rename log_build_keen() to send_build_data()
- [keenio] add send_build_data_service()
- [keenio] schema change : save build job data in build_jobs.job (was builds.build)
- schema change : version is renamed to lib_version in project_info
- issue 50 : only check timing tags for builds after they were introduced on Travis CI

0.1.2

- improve Travis CI example : pull released version from git

0.1.1

- improve Travis CI example : fix issue extracting the github tarball

0.1

- Get timing data from each stage in a build process
- Store, analyse and create trends of the build process data
- keen mode : send timing data to Keen.io and use the Keen.io API for analysis and visualisation
- native mode : store data in xml format and use matplotlib to generate a chart (limited)
- Current charts and trends
- number of builds, succesful and failed
- average build duration
- chart with build stage durations
- builds per branch
- different time period can be selected

Links

Releases

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.