持續整合伺服器-luntbuild1.1釋出
luntbuild是一個開放原始碼的構建自動化和管理工具,可以用來方便的進行持續整合和每日構建,1.1版本具有如下功能:
* Supporting version control systems: cvs, visual sourcesafe, subversion
starteam, perforce, base clearcase, clearcase UCM. Build can be performed
from one or more repositories of the same or different vcs types.
* Easy setup. All tasks are done through a clean web interface. No any
configuration files.
* Build for parallel development are well supported by using notion
of project, view and module.
* History builds can be exactly re-produced
* Can perform clean build or increment build
* Build can be triggered in many ways, such as trigger build manually, trigger
build when changes are detected in source repository, trigger build rightaway
upon user checkin, or trigger build by user-defined conditions, etc
* Build success conditions can be defined by user, such as examine command return
code, pattern match on command outputs, etc.
* Source repository can get labeled after a build to record exact source
files compositing current build
* Email or MSN notification to specified users or checkin users upon build
completion.
* Build artifacts are published on web to provide a central download area
for whole team.
* Can add patch for particular build through file uploading.
* Builds are categorized, and can get promoted.
* Build can be searched and deleted.
* Build log, revision log and system log4j log can be directly accessed
through web interface.
* Different jdk, jdk options, ant, and ant options can be configured for
different project/views.
* Schedule can be periodically or cron like.
* API available to integrate your applications with luntbuild
* Flexible versioning strategy, such as automatically increase self-defined
version number, be able to embed dynamic fields such as build date, build iterations
into build version etc.
可以到http://www.luntsys.com/luntbuild/獲得更詳細資訊
* Supporting version control systems: cvs, visual sourcesafe, subversion
starteam, perforce, base clearcase, clearcase UCM. Build can be performed
from one or more repositories of the same or different vcs types.
* Easy setup. All tasks are done through a clean web interface. No any
configuration files.
* Build for parallel development are well supported by using notion
of project, view and module.
* History builds can be exactly re-produced
* Can perform clean build or increment build
* Build can be triggered in many ways, such as trigger build manually, trigger
build when changes are detected in source repository, trigger build rightaway
upon user checkin, or trigger build by user-defined conditions, etc
* Build success conditions can be defined by user, such as examine command return
code, pattern match on command outputs, etc.
* Source repository can get labeled after a build to record exact source
files compositing current build
* Email or MSN notification to specified users or checkin users upon build
completion.
* Build artifacts are published on web to provide a central download area
for whole team.
* Can add patch for particular build through file uploading.
* Builds are categorized, and can get promoted.
* Build can be searched and deleted.
* Build log, revision log and system log4j log can be directly accessed
through web interface.
* Different jdk, jdk options, ant, and ant options can be configured for
different project/views.
* Schedule can be periodically or cron like.
* API available to integrate your applications with luntbuild
* Flexible versioning strategy, such as automatically increase self-defined
version number, be able to embed dynamic fields such as build date, build iterations
into build version etc.
可以到http://www.luntsys.com/luntbuild/獲得更詳細資訊
相關文章
- 持續整合、持續部署、持續交付、持續釋出
- 對持續整合、 持續交付、持續部署和持續釋出的介紹
- 我們正在路上—從持續整合到持續釋出
- Cruise:持續整合及釋出管理系統UI
- vue + webpack 前端專案持續釋出整合部署VueWeb前端
- 持續整合持續部署持續交付_持續整合與持續部署之間的真正區別
- 持續整合、持續交付、持續部署簡介
- 整合持續整合工具
- iOS 持續整合iOS
- Jenkins2.65釋出,可擴充套件的持續整合引擎Jenkins套件
- 淺談持續整合(CI)、持續交付(CD)、持續部署(CD)
- Jenkins持續整合Jenkins
- 從持續整合到持續交付——DockerCloud概覽DockerCloud
- 談談持續整合,持續交付,持續部署之間的區別
- 超大流量電商平臺系統背後的持續整合與釋出
- 通過Docker容器執行持續整合/持續部署Docker
- 持續整合配置之Nuget
- Taro 小程式持續整合
- 持續整合JenkinsBlueOcean初探Jenkins
- Jenkins持續整合配置Jenkins
- 基於jenkins搭建一個持續整合伺服器Jenkins伺服器
- Jenkins持續整合(下)-Jenkins部署Asp.Net網站自動釋出JenkinsASP.NET網站
- 使用 Github Actions 持續釋出 Flutter 應用GithubFlutter
- 淺談持續整合的理解以及實現持續整合,需要做什麼?
- 使用流水線外掛實現持續整合、持續部署
- Flutter web 持續整合實踐FlutterWeb
- Jenkens+Docker+Git 持續整合DockerGit
- jenkins+docker 持續整合JenkinsDocker
- iOS持續整合(一)——fastlane 使用iOSAST
- 持續整合 Jenkins 簡介Jenkins
- 小程式的持續整合方案
- iOS 持續整合系列 – 開篇iOS
- Jenkins 持續整合使用教程Jenkins
- 持續整合(三):最佳實踐
- CI 持續整合 - 阿里云云效阿里
- 持續整合及部署利器:GoGo
- 使用GitLabCI持續整合Gitlab
- 持續整合開源軟體