Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U033PU4NUJY> I think doc generation changes broke the build in several places. It’s breaking now for me locally as well.

This is <https://github.com/airbytehq/airbyte/pull/14369|the PR> that broke the build on master. I now have several tasks failing in CONNECTORS_BASE build because they cannot find the files that were deleted or moved in that PR

I’ve pinged <@U03AD1Q29NG>on Slack as well just now

we can probably revert this while i look if this is blocking the path to production.  that said i'm just looking now

my initial impression is that i can find/replace this in about an hour.  assuming my expectations around document generation are accurate

it looks like some tests and some document generation use hardcoded paths to things we moved.  I believe that fixing those will address this

<@U03407DC2P3> you need to read the commit message for the line i just fixed for when it was committed almost exactly a year ago <https://github.com/airbytehq/airbyte/pull/5080>

how long does this integration test take anyway, i think i have the bug fixed i'm just watching the test suite now

there is another build failure related to the same change (it failed on CI on your PR just now)

`chown: /airbyte/docs/integrations/*: No such file or directory` is the problem

just an update: the docs team doesn't like the changes overall anyway so we are reverting them wholesale

Amruta is double checking the revert and we'll get it up there

it's sad, but better now that 100 commits later

i think if you pull you should be set now greg

~i take it back greg, there is a new new failure that appears docs related~
i think it's actually green and i was looking at a tab from cloud.  give me a yell if i'm wrong

<@U03MNTVA6BA> Topher just fixed builds on master and I think that affects your feature branch for validating JDBC params, so you may want to rebase on master and push to your branch again

Thanks for heads up, I'll be sure to incorporate the changes into my branch. Just to clarify if there are some builds that are failing, would this channel be the right place to ask?

Usually, <#C02U2SSHP9S|dev> channel is better for these questions. In this case I found the PR that broke the build and started a thread from the automated notification of that build failure