Thanks for the feedback @bootstraponline, weâll definitely keep this in mind!
@bootstraponline an update for the âabort API with statusâ - the API should be ready soon, so that youâll be able to abort builds with success (1) and error (2) codes in addition to the default âabortedâ (3) code, using the API.
Unfortunately the UI will also have to be tweaked for this a bit, and that most likely wonât be released this week, but if youâre interested just let me know and we can do a beta test. Technically it will work (on an API level) but the web UI will show those builds the same way as any other success/error build, e.g. wonât show the abort reason text; those will come a bit later.
It sounds like I should wait for the UI enhancement to land first. I think itâd be confusing to use without that. Thanks for the update!
Makes sense, weâll try to finish that as well as soon as possible
Iâm interested in a beta test now since Iâm migrating new jobs over. If you could send me the details when you have time, thatâd be great.
Thanks to bitrise, we now have a solution for building only changed code. In the future, the shell script will go away in favor of first class mono repo support.
Thanks for sharing @bootstraponline!
Just one note, this script uses the undocumented new abort
endpoint params, but should be safe to use / we donât expect to change that in the foreseeable future, and should be documented on the devcenter soon
First of all, thank you guys for this discussion!
So, I have a mono repo with the structure already described:
app1/
app2/
As far as I understand the script attached by @bootstraponline could be used if you have multi bitrise projects for the same repo. Is there any way to have one bitrise project with multiple workflows or even better to skip a certain step of the workflow if nothing changed?
@SoHotSoup sure it is possible, via custom scripts. In general the suggestion is that if you have 2 app projects in the repo then add it as 2 separate apps on bitrise.io
Skipping steps is definitely possible if youâd prefer that, but requires scripting. Related docs: https://devcenter.bitrise.io/tips-and-tricks/disable-a-step-by-condition/ - for scripting see the last section / the bottom of the page.
A related discussion with a script & run_if
example: How can I use variables stored with envman in the run_if check before a step is run?
@viktorbenei Thank you! I have opted for more bitrise apps already⌠I have achieved build skipping by using and modifying script provided by @bootstraponline.
I moved the script Iâm using to a step
Weâd love this feature as well.
Instead of calling apiâs wouldnât it be easier to check the git history itself in a step, and then supporting a skipped
build status? Or am I missing something?
Instead of calling apiâs wouldnât it be easier to check the git history itself in a step, and then supporting a skipped build status? Or am I missing something?
Iâve been using that approach for a while. There are problems since git clone fails for various reasons. Itâs also slow. Every change triggers all the builds and they must perform a full clone.
On buddybuild with native support, these builds arenât triggered at all. Thatâs helped dramatically with performance and build stability.
Quick update: this feature is scheduled in the current sprint and weâre working on it, should be available in the upcoming weeks. Will update you here once itâs ready!
I found out AppCenter also adopted a mono repo and used path triggers to improve build efficiency.
Hey @bootstraponline,
Weâve released the mono repo support feature as Selective Builds. You can find this option on the Settings
page of your application at the Enable Selective Builds
section. You just need to toggle the switch and then add your change paths to the list
Thank you for the feature request again!
Happy building
Please note that this it GitHub.com only right now!
If youâd need it for another git service please create a new #feature-request!
This topic was automatically closed after 14 days. New replies are no longer allowed.