========
funsizer is the client side for funsize project ( https://wiki.mozilla.org/ReleaseEngineering/Funsize )
It aims to automate the triggering and the retrieval of the partial MAR files.
Installation
============
Run `python setup.py install` to install the script as command-line tool.
Usage
=====
Run `funsizer.py -u *URL* -a *auth file* -b *branch name* *path to file*` to upload a file to the blobber server at *URL*.
Run `funsizer.py [--timeout T]
[--window-timeout wT]
[--server-url URL]
--from-url from-URL
--to-url to-URL
--from-has from-HASH
--to-has to-HASH
--channel CHANNEL
--version VERSION
--output OUTPUT
Where
=> T is timeout (in seconds) to wait for results
=> window-timeout is windows timeout sleep between client-to-server calls
=> server-url is the host where to send the files (defaults to localhost)
=> from-url is the complete mar url for `from` version'
=> to-url is the complete mar url for `to` version'
=> from-hash is the hash for `from` version mar'
=> to-hash is the hash for `to` version mar'
=> channel is the channel for the requested partial mar'
=> version is the version of the latter mar'
=> output is the file where to write the resulted partial mar'
Metadata
Release files for funsizer 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| funsizer-0.1.tar.gz | 2.7 kB | Without provenance | Details for funsizer-0.1.tar.gz |
Release files / funsizer-0.1.tar.gz
| Download URL | funsizer-0.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c38db378f5dbcf7eb68a18485b3e6d3fa8c5fb1b13e503a95937c68309eea7df
|
|
BLAKE2b-256 checksum How to use checksums |
5c2a67767d9b969474acbb9cd75e5c608d380e673964b76b9e5f5adcbcb5f2a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for funsizer 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.