<p>Jenkins supports scripted pipeline which can handle my every requirement.
Buildbot can handle these requirements with custom steps, i suppose, but it's too hard if compared to Jenkins' scripted pipeline.</p>

CC BY-SA 4.0
2020-05-26T14:00:58.460Z
2020-05-26T14:00:58.460Z
Daniil
<p>I need a tool/framework for CI/CD which can:</p>

<ol>
<li>Support multi-repository project</li>
<li>Build and ship only changed part (frontend/backend) using revison hashes to decide</li>
<li>Ship some branches (release candidate brances) to test environment and some to production (master)</li>
<li>Get version number from repository based on branch name for RC</li>
<li>Get version number from repository based on last merged branch in master for production</li>
<li>Create build version in bug tracker and mark issues as fixed in created version based on issue status and planned version</li>
<li>Notify about new version uploaded on test/production with issues list from bug tracker</li>
<li>Get new database migration scripts (based on diff with previously uploaded version using revison hashes) and notify about them &amp; (maybe) execute them </li>
</ol>

<p>I wrote a script to do this but it lacks interface to do manual build/ship or to monitor build status (only notification at the end of build/deploy)</p>

<p>I have found Bouldbot but not shure it can handle these requirements.</p>

<p>If you know a framework which can handle these requirements without pain, please, name it.</p>

CC BY-SA 4.0
2020-05-15T23:59:00.320Z
I'm building Reliza Hub to support those points. It's early stage and not everything is implemented yet, but it's progressing quickly. The tool is completely free until the end of 2020. Site - https://relizahub.com, tutorial video - https://www.youtube.com/watch?v=yDlf5fMBGuI 
If you like the concept, book a demo with me - would be happy to help with your use case - https://calendly.com/pavel_reliza/demo
taleodor
CC BY-SA 4.0
2020-05-26T14:07:58.323Z
@taleodor thanks, but i need a mature CI/CD tool with documentation and community. Maybe later.
Daniil
<continuous-integration><continuous-deployment><toolchain>
Does Buildbot support complicated build/deploy scenarios?
Daniil
# Does Buildbot support complicated build/deploy scenarios?

(Asked by: username_0 on 2020-05-15)

I need a tool/framework for CI/CD which can:

1. Support multi-repository project
2. Build and ship only changed part (frontend/backend) using revison hashes to decide
3. Ship some branches (release candidate brances) to test environment and some to production (master)
4. Get version number from repository based on branch name for RC
5. Get version number from repository based on last merged branch in master for production
6. Create build version in bug tracker and mark issues as fixed in created version based on issue status and planned version
7. Notify about new version uploaded on test/production with issues list from bug tracker
8. Get new database migration scripts (based on diff with previously uploaded version using revison hashes) and notify about them & (maybe) execute them

I wrote a script to do this but it lacks interface to do manual build/ship or to monitor build status (only notification at the end of build/deploy)

I have found Bouldbot but not shure it can handle these requirements.

If you know a framework which can handle these requirements without pain, please, name it.

**Tags:** continuous-integration, continuous-deployment, toolchain

> **Comments:**
> **username_1**: I'm building Reliza Hub to support those points. It's early stage and not everything is implemented yet, but it's progressing quickly. The tool is completely free until the end of 2020. Site - https://relizahub.com, tutorial video - https://www.youtube.com/watch?v=yDlf5fMBGuI  If you like the concept, book a demo with me - would be happy to help with your use case - https://calendly.com/pavel_reliza/demo  
> **username_0**: @username_1 thanks, but i need a mature CI/CD tool with documentation and community. Maybe later.  

---

## 1 answers

### Answer by username_0 on 2020-05-26. Score: 1 | Accepted answer

Jenkins supports scripted pipeline which can handle my every requirement.
Buildbot can handle these requirements with custom steps, i suppose, but it's too hard if compared to Jenkins' scripted pipeline.


---

