增强 Builder 发布流程
我想将自定义任务绑定到默认构建器发布周期中。我想在项目编译、打包、标记和部署之后但在增加版本号并提交之前运行此代码。
我将如何融入发布周期的这一部分?
I'd like to tie a custom task into the default buildr release cycle. I'd like to run this code after the project has been compiled, packaged, tagged and deployed but before it increments the version number and commits that.
How would I tie into this part of the release cycle?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
不幸的是,
release
任务并不由您可以使用自己的任务挂钩和扩展的子任务组成。引用当前的实现,
如您所见,Buildr 分叉了一个单独的进程,并且本质上运行
buildr clean upload
一种可能是增强
上传
> 任务并将您的任务添加为依赖项,例如,如果这不能满足您的需求,我建议在 https://issues.apache.org/jira/browse/BUILDR。
Unfortunately, the
release
task isn't composed of sub-tasks that you could potentially hook into and extend with your own task(s).To quote the current implementation,
As you can see, Buildr forks a separate process and essentially runs
buildr clean upload
One possibility would be toenhance
theupload
task and add your tasks as dependencies, e.g.,If this doesn't meet your needs, I'd recommend opening an enhancement request at https://issues.apache.org/jira/browse/BUILDR.