Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Config validation error in build.os. Value os not found #11173

Closed
derks opened this issue Feb 29, 2024 · 7 comments
Closed

Config validation error in build.os. Value os not found #11173

derks opened this issue Feb 29, 2024 · 7 comments
Labels
Needed: more information A reply from issue author is required Support Support question

Comments

@derks
Copy link

derks commented Feb 29, 2024

Any help would be much appreciated... using pretty stock .readthedocs.yaml from the docs.

Details

Expected Result

Successful build.

Actual Result

Error
Config validation error in build.os. Value os not found.
Screenshot 2024-02-29 at 9 53 23 AM
@stsewd
Copy link
Member

stsewd commented Feb 29, 2024

Hi, you are missing using the build.os config value, see our docs for a quick start of a valid config file https://docs.readthedocs.io/en/stable/config-file/v2.html.

We should probably link to our docs when such errors appear.

@humitos humitos added Support Support question Needed: more information A reply from issue author is required labels Feb 29, 2024
@derks
Copy link
Author

derks commented Feb 29, 2024

@stsewd thank you for the quick reply. Can you elaborate on what is not right in the .readthedocs.yaml configuration in the repo?

@stsewd
Copy link
Member

stsewd commented Feb 29, 2024

@derks looks like you have two cofig files https://github.com/datafolklabs/cement/blob/main/readthedocs.yml, you should delete the other one.

@derks
Copy link
Author

derks commented Feb 29, 2024

Geeeeeeeeze.... not sure how I missed that :/. Thank you for the help... I'll try that now.

@humitos humitos mentioned this issue Feb 29, 2024
Closed
@derks
Copy link
Author

derks commented Feb 29, 2024

@humitos thank you again for your help. I was able to fix main (latest) now... however I have having issues with building the 3.0 version (this is a Git tag). I tag 3, 3.0 every time I make a 3.0.x release, and this is the source for the 3.0 version. It seems that RTD is not pulling down the latest 3.0 tag, and therefore continues to fail.

Any insights? Is this a cache issue that will resolve itself, or is there anything we/I can do to force it along?

@stsewd
Copy link
Member

stsewd commented Feb 29, 2024

@derks if you forced push the tag, you need to first build any other version for the commit to be updated first, after that you can trigger a build for it to pick the correct commit. See #10838.

@MaGering MaGering mentioned this issue Mar 11, 2024
Merged
MaGering added a commit to rl-institut/oemof-B3 that referenced this issue Mar 11, 2024
@MaGering
Fix build of docs
79565d8 
Fix Error 'Config validation error in build.os. Value build not found.'
Building docs errors out:
Build # 23712488
latest
Build fehlgeschlagen
Error
Config validation error in build.os. Value build not found.

git clone --depth 1 https://github.com/rl-institut/oemof-B3 .
git fetch origin --force --prune --prune-tags --depth 50 refs/heads/dev:refs/remotes/origin/dev
git checkout --force origin/dev
git clean -d -f -f
cat .readthedocs.yml

With this PR the solution proposed according to issue readthedocs/readthedocs.org#11173
-> https://docs.readthedocs.io/en/stable/config-file/v2.html
mristin added a commit to aas-core-works/aas-core3.0-python that referenced this issue Mar 23, 2024
@mristin
Fix readthedocs config for missing os
1bd6541 
We received the error:

```
Config validation error in build.os. Value build not found.
```

This patch fixes the error by specifying the `build.os` as written in
the example linked from the [readthedocs issue 11173].

[readthedocs issue 11173]: readthedocs/readthedocs.org#11173
@mristin mristin mentioned this issue Mar 23, 2024
Merged
mristin added a commit to aas-core-works/aas-core3.0-python that referenced this issue Mar 23, 2024
@mristin
Fix readthedocs config for missing os
a8944aa 
We received the error:

```
Config validation error in build.os. Value build not found.
```

This patch fixes the error by specifying the `build.os` as written in
the example linked from the [readthedocs issue 11173].

[readthedocs issue 11173]: readthedocs/readthedocs.org#11173
mristin added a commit to aas-core-works/aas-core3.0-python that referenced this issue Mar 23, 2024
@mristin
Fix readthedocs config for missing os (#25)
1955550 
We received the error:

```
Config validation error in build.os. Value build not found.
```

This patch fixes the error by specifying the `build.os` as written in
the example linked from the [readthedocs issue 11173].

[readthedocs issue 11173]: readthedocs/readthedocs.org#11173
@humitos humitos closed this as completed Mar 26, 2024
abe-101 added a commit to abe-101/dj-stripe that referenced this issue Apr 28, 2024
@abe-101
fix(docs): add os build to readthedocs config
45d3ed3 
the build error on message on:
https://beta.readthedocs.org/projects/dj-stripe/builds/24185540/
is:
> Config file validation error
> Config validation error in build.os. Value build not found.

Per issue:
readthedocs/readthedocs.org#11173
and the proejct docs:
https://docs.readthedocs.io/en/stable/config-file/v2.html
the solution should be to add the build step
@abe-101 abe-101 mentioned this issue Apr 28, 2024
Merged
jleclanche pushed a commit to dj-stripe/dj-stripe that referenced this issue Apr 28, 2024
@abe-101 @jleclanche
fix(docs): add os build to readthedocs config
e45f374 
the build error on message on:
https://beta.readthedocs.org/projects/dj-stripe/builds/24185540/
is:
> Config file validation error
> Config validation error in build.os. Value build not found.

Per issue:
readthedocs/readthedocs.org#11173
and the proejct docs:
https://docs.readthedocs.io/en/stable/config-file/v2.html
the solution should be to add the build step
christianspecht added a commit to christianspecht/scm-backup-docs that referenced this issue May 18, 2024
@christianspecht
add missing config value
51b89d3 
readthedocs/readthedocs.org#11173
https://blog.readthedocs.com/use-build-os-config/
@riley-brady riley-brady mentioned this issue Aug 5, 2024
Open
chipitsine added a commit to chipitsine/wal-g that referenced this issue Nov 26, 2024
@chipitsine
fix readthedocs build definition
f4bdd11 
for the reference: readthedocs/readthedocs.org#11173
@chipitsine chipitsine mentioned this issue Nov 26, 2024
Merged
@jordansissel
Copy link

Would it be possible to make build.os have a default value? I have a project with released versions that cannot have the docs built because build.os was missing (and unknown to me) at the time I created the git tag (and for policy reasons, I am unable to commit a change and point the git tag to a new commit)

This was referenced Dec 12, 2024
Draft
Open
x4m pushed a commit to wal-g/wal-g that referenced this issue Dec 21, 2024
@chipitsine
fix readthedocs build definition (#1847)
20b3a19 
for the reference: readthedocs/readthedocs.org#11173
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needed: more information A reply from issue author is required Support Support question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@derks @jordansissel @humitos @stsewd