Boost version 0.2.0

Boost - v0.2.0

Features

• Implement boost context.
• Implement variable attributes.

Changes

• The vars section is not anymore a key-value pair, its a list of objects each one being a variable.
• Secret variable behavior is now applied by using secret variable attribute.
• The exec keyword on variables has been removed and now it is applied by using the exec attribute.

Considerations

Currently, the parse and validation process of boost file is very poorly implemented. If you try, you are going to break boost by modifying the boost.yaml file, and, to be honest, even without really trying you may encounter some errors. This is the reason behind settings this release as pre-release.

Version Yanked

Removed from PyPI as this release introduces the error where boost only uses the first define boost target even if manually specifying one.

Boost version 0.1.13

Boost - v0.1.13

Features

• Boost now does not exit itself when sending a SIGINT signal but the signal is still being sent to the process being run by boost. This allows users to only stop a single step.

Considerations

Currently, the parse and validation process of boost file is very poorly implemented. If you try, you are going to break boost by modifying the boost.yaml file, and, to be honest, even without really trying you may encounter some errors. This is the reason behind settings this release as pre-release.

Boost version 0.1.12

Boost - v0.1.12

Features

• Vars using exec keyword captures the output from the command executed, storing the output so it can be used on targets.
• Target commands does not capture output and simulates that they are being executed on a shell.

Considerations

Currently, the parse and validation process of boost file is very poorly implemented. If you try, you are going to break boost by modifying the boost.yaml file, and, to be honest, even without really trying you may encounter some errors. This is the reason behind settings this release as pre-release.

Boost version 0.1.11

Boost - v0.1.11

Features

• Removed new lines from console output.

Considerations

Currently, the parse and validation process of boost file is very poorly implemented. If you try, you are going to break boost by modifying the boost.yaml file, and, to be honest, even without really trying you may encounter some errors. This is the reason behind settings this release as pre-release.

Boost version 0.1.10

Boost - v0.1.9

Fixes

• Fixed an issue where the storage was executing command and interpreting an empty error as an error.

Considerations

Currently, the parse and validation process of boost file is very poorly implemented. If you try, you are going to break boost by modifying the boost.yaml file, and, to be honest, even without really trying you may encounter some errors. This is the reason behind settings this release as pre-release.

Boost version 0.1.9

Boost - v0.1.9

Features

• Errors returned from commands to not force an immediate exit.

Fixes

• Fixed an issue where a secret variable value was substituted with "*****" when sending to a command instead of the actual value.

Considerations

Currently, the parse and validation process of boost file is very poorly implemented. If you try, you are going to break boost by modifying the boost.yaml file, and, to be honest, even without really trying you may encounter some errors. This is the reason behind settings this release as pre-release.

Boost version 0.1.8

Boost - v0.1.7

Features

• If the variable name includes "secret" on its name, it will be replaced by "*****" when it is printed on the console.

Considerations

Currently, the parse and validation process of boost file is very poorly implemented. If you try, you are going to break boost by modifying the boost.yaml file, and, to be honest, even without really trying you may encounter some errors. This is the reason behind settings this release as pre-release.

Boost version 0.1.7

Boost - v0.1.7

Features

• YAML build files called boost.yaml, this file describes different build targets that can be run using boost TARGET and its required variables {VARIABLE} defined on vars section.
• Scalable multi-platform commands. Commands inside bootbuild.cmd that implements generic_exec or win_exec and posix_exec are automatically callable by their file name.
• Called commands which are not defined on bootbuild.cmd are passed to the system shell by the help of boostbuild.cmd.unkown command.
• Required variables that are not defined on vars section are searched on system environment variables.
• Calling boost without any especified target will trigger the first declared target.

Considerations

Currently, the parse and validation process of boost file is very poorly implemented. If you try, you are going to break boost by modifying the boost.yaml file, and, to be honest, even without really trying you may encounter some errors. This is the reason behind settings this release as pre-release.