- Enabled support for Gerrit
- Enabled support for multiple platforms
- [ISSUE 391] Make execution summary times easier to read
- [ISSUE 338] Fixed
${{ env.VAR }}
not being substituted correctly
- [ISSUE 333] Fixed CLI ignoring the
--token
flag
- [ISSUE 331] Typo in
definitionFile
option for CLI which lead an invalid definition file location
- Complete refactor to typescript
- implemented end to end tests
- Prints system git version
- [issue 203] Prints execution summary
- additional-flags input
- [ISSUE 103] be able to access definition file from private repositories
- [ISSUE 216] remove -project flag from build branch command
- [ISSUE 217] add skip project execution (spe) feature
- [ISSUE 225] add secrets information for forked projects
- [ISSUE 315] improve message when token is wrong
- printLocalCommand definition-file wrong quotes
- the choosen definition file is not printed in case of all placeholders have default values
- [ISSUE 221]
hasForkPullRequest
head from${fromAuthor}:${branch}
to${sourceOwner}/${sourceRepo}:${sourceBranch}
@kie/build-chain-configuration-reader
upgraded to2.2.3
- definition version moved to 2.1
- targetExpression mapping
- branch flow from GA
- getForkedProjectName improved
- print execution plan
- --skipExecution flag to skip the command execution and artifacts archiving for all the flow types
- --skipCheckout to skip project checkout. Checkout information will be printed anyway
- print command: the tool will print the command to be copy pasted in order to execute in any environment
logger-level
input added.- debug log improved
- default value for placeholders
- important information posted to Annotations section
- annotations-prefix input to identify the annotations per job
- [issue 153] windows error on joining folder.
- [issue 158] definition file URL improvements GROUP/BRANCH placeholders.
- add starting-project CLI argument to single flow type option.
- starting-project argument missing documentation.
- [issue 176] look up both current and project triggering mappings.
- [issue 137] To avoid getting branches for already closed PRs.
- rename merging base branch to source branch name to avoid Sonar zero issues.
custom-command-treatment
CLI option@kie/build-chain-configuration-reader
upgraded to2.0.4
- error mapping branches solved
- allow to read definition files from private repositories
- pre/post sections
starting-project
input added- env variables treated from commands
- export command treated
- token not mandatory
- Error treating export commands like
export DROOLS_VERSION=mvn org.apache.maven.plugins:maven-help-plugin:evaluate -Dexpression=project.version | grep ^7
will executeexport DROOLS_VERSION=mvn org.apache.maven.plugins:maven-help-plugin:evaluate -Dexpression=project.version | grep ^7 -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B
. Fixed.
- token added to git commands to avoid private repositories problem from CLI execution
- clone option added
- command line ready
- full downstream flow added either for CLI and github action
- single flow added either for CLI and github action
- @kie/build-chain-configuration-reader dependency upgraded to ^2.0.2
- branch flow added for CLI
- skip build mechanism
- configuration file version <2.0 is no longer supported
- checkout mechanism improved
- @kie/build-chain-configuration-reader dependency upgraded to ^0.0.6
- artifacts in case of failure
- centralized flow definition file
- definition-file input added
- rest of inputs removed since they are not needed anymore
- default configuration for every project
- before and after commands added
- archive-artifacts-dependencies
- checkout info summary
Cannot read property 'artifactItems' of undefined
error fixed
- Mapping error solved
- Just contributors added
Github action build chain is a tool for github actions to build multiple projects from different repositories in a single action. This tool is trying to solve the problem when a project depends on another project (most probably from the same organization) and one change can/should be performed in different repositories. How can we assure one specific pull request will work with the latest changes from/in the dependant/dependency projects and it won't break something? This is what we call cross-repo pull requests and build-chain is the way we have to solve it.
- archive artifacts mechanism
- pull request flow
- cross-repo checkout