Releases: Metadrop/drupal-artifact-builder
2.0.2
2.0.1
This release fixes a Fatal error produced when the array configuration properties were not properly setup. Plus, the include
documentation has been improved for a better understanding about how to configure it.
2.0.0-rc1
2.0.0-alpha5
Fix a bug where author could not be configured through configuration file.
2.0.0-alpha4
First release that allow defining a map between branches. Still in testing phase.
2.0.0
This is a major upgrade that introduces new features. Those features have also implied some breaking changes in order to make the usage of drupal-artifact-builder more intuitive and easy.
Features and improvements
- Now all the parameters can be added through a YML file. It is recommended to use a configuration file so when the command is launched manually, it is not needed to manually write every parameter. Please look at README to know how to write the configuration file.
- Now it is possible to define the map between branches, in case it is needed to push artifact to different branches than the source branch.
- Performance of git command has been improved. Instead of cloning the entire repository, it makes a shallow clone (--depth 1).
Breaking changes
- The parameter to include extra folders, --extra-paths, has been changed to --include
- In order to recognize the git branch, the GIT_BRANCH environment variable is not used anymore. This is a too much specific variable added by Jenkins and it is not intuitive supporting it.
Migration from 1.x to 2.x
Please follow instructions at README
2.0.0-alpha3
Improve performance of git integration. Now a shallow clone is performed, so no additional revisions are downloaded into the git clone process. This should improve significantly the performance in big projects.
2.0.0-alpha1
This version changes the way artifacts parameters are included. Now, parameters are optional, and a config file should be included by default.
It is still in alpha as is being tested before fully introducing the change.
There is a breaking change: now the --extra-paths parameter is changed to --include. It also suggests a new default configuration. For that reasons, a major upgrade has been done.
Full Changelog: 1.8.0...2.0.0-alpha1
1.8.0
Full Changelog: 1.7.0...1.8.0
1.7.0
What's Changed
- Allow defining git branch through a bash argument by @omarlopesino in #15
New Contributors
- @omarlopesino made their first contribution in #15
Full Changelog: 1.6.1...1.7.0
IMPORTANT: At 1.7.1 a new release will be generated removing the usage of GIT_BRANCH environment variable. So it would be required to use the 1.7.0 version that supports the --branch parameter to adapt the sites where the script is used.