Codeberg-e.V./requests
Codeberg-e.V./requests
76
23
Fork 6
Code Issues17 Pull requests Activity

[CI] x86-codeblocks-builds #425

New issue
Closed
opened 2024-10-18 21:21:36 +00:00 by MichaelAgarkov · 14 comments
MichaelAgarkov commented 2024-10-18 21:21:36 +00:00

Projects

Expected Resource Usage

large

I would also like the following users to be added

No response

Additional Information

Testing if this build bot can work in codeberg, if yes, then I'll try to migrate it here.

Other Work

Original: https://github.com/MichaelAgarkov/x86-codeblocks-builds

Statement

  • I am aware of the licensing requirement mentioned earlier on this form.
  • I understand that Codeberg's CI might not always be available or stable, despite best efforts.
  • I understand that I can use the feedback repository to share feedback or report problems.
### Projects - [x86-codeblocks-builds](https://codeberg.org/MichaelAgarkov/x86-codeblocks-builds) ### Expected Resource Usage large ### I would also like the following users to be added _No response_ ### Additional Information Testing if this build bot can work in codeberg, if yes, then I'll try to migrate it here. ### Other Work Original: https://github.com/MichaelAgarkov/x86-codeblocks-builds ### Statement - [x] I am aware of the licensing requirement mentioned earlier on this form. - [x] I understand that Codeberg's CI might not always be available or stable, despite best efforts. - [x] I understand that I can use the [feedback repository](https://codeberg.org/Codeberg-CI/feedback) to share feedback or report problems.
MichaelAgarkov added the
ci
 label 2024-10-18 21:21:36 +00:00
MichaelAgarkov commented 2024-10-18 21:24:36 +00:00
Author

I'm migrating from GitHub to codeberg :)

I'm migrating from GitHub to codeberg :)
n0toose commented 2024-10-18 23:57:44 +00:00
Owner

This project builds Code::Blocks for different targets using the GitHub-hosted unofficial mirror of the project.

@fnetX What do you think?

This project builds Code::Blocks for different targets using the GitHub-hosted unofficial mirror of the project. @fnetX What do you think?
n0toose commented 2024-10-19 00:26:33 +00:00
Owner
  • For how long would the build artifacts be retained?
  • Is there anything you do to assure reproducibility?
  • Could you answer the following question clearly: What problems does your project fix that the upstream does not?
- For how long would the build artifacts be retained? - Is there anything you do to assure reproducibility? - Could you answer the following question clearly: What problems does your project fix that the upstream does not?
MichaelAgarkov commented 2024-10-19 07:32:57 +00:00
Author
  • For how long would the build artifacts be retained?
  • Is there anything you do to assure reproducibility?
  • Could you answer the following question clearly: What problems does your project fix that the upstream does not?
> - For how long would the build artifacts be retained? > - Is there anything you do to assure reproducibility? > - Could you answer the following question clearly: What problems does your project fix that the upstream does not? - Probably until a new version is built. - I personally don't. - AFAIK we are planning to move the C::B build process to CI/CD instead of it being manual (see https://forums.codeblocks.org/index.php/topic,25856.0.html). Because I'm not a fan of GitHub I want to see if it can work in codeberg.
MichaelAgarkov commented 2024-10-20 16:36:11 +00:00
Author

Nevermind, if it works on GitHub then it probably will work in any GitHub Actions' compatible CI/CD.

Nevermind, if it works on GitHub then it probably will work in any GitHub Actions' compatible CI/CD.
n0toose commented 2024-10-20 20:22:45 +00:00
Owner

Sorry for missing your reply. Wait, you're an officially affiliated developer with Code::Blocks? I was under the impression that you were not affiliated, hence the questions like "Is there anything you do to assure reproducibility?".

Sorry for missing your reply. Wait, you're an officially affiliated developer with Code::Blocks? I was under the impression that you were not affiliated, hence the questions like "Is there anything you do to assure reproducibility?".
n0toose commented 2024-10-20 20:25:40 +00:00
Owner

If you are planning to move C::B's build process, as in, this is a C::B effort (even if the affiliation is "loose") and not a personal effort, I'm sure we don't have a problem with the resource usage. I hope that it is understood why I was skeptical to begin with - we have a similar effort full of QEMU toolchains with build artifacts amounting to ~300 GBs on our system, and it's somewhat sketchy.

But that's your call.

If you are planning to move C::B's **build process**, as in, this is a **C::B** effort (even if the affiliation is "loose") and not a *personal* effort, I'm sure we don't have a problem with the resource usage. I hope that it is understood why I was skeptical to begin with - we have a similar effort full of QEMU toolchains with build artifacts amounting to ~300 GBs on our system, and it's somewhat sketchy. But that's your call.
MichaelAgarkov commented 2024-10-20 21:02:39 +00:00
Author

Wait, you're an officially affiliated developer with Code::Blocks?

Not really, I just work with them and wanted to test if the current GitHub build bot will work in Woodpecker CI and if improvements are needed.

If you are planning to move C::B's build process

No, I just wanted to test and make a version of the build bot that's compatible with a non-GitHub CI/CD, because I don't like GitHub.

> Wait, you're an officially affiliated developer with Code::Blocks? Not really, I just work with them and wanted to test if the current GitHub build bot will work in Woodpecker CI and if improvements are needed. > If you are planning to move C::B's build process No, I just wanted to test and make a version of the build bot that's compatible with a non-GitHub CI/CD, because I don't like GitHub.
MichaelAgarkov commented 2024-10-20 21:08:04 +00:00
Author

Also we are using an unofficial mirror of the C::B code because C::B is using a SVN repo, and I'm unsure if the build bot will work with that.

Also we are using an unofficial mirror of the C::B code because C::B is using a SVN repo, and I'm unsure if the build bot will work with that.
n0toose commented 2024-10-21 06:13:02 +00:00
Owner

LGTM!

Thanks for sharing more information about your situation and sorry for the extra trouble for you, I just really had to be extra sure that there was nothing "sketchy"-ish going on here. Feel free to experiment. (P.S. the SVN thing could potentially work, it's just that triggering the workflow itself may be a bit tricky)

LGTM! Thanks for sharing more information about your situation and sorry for the extra trouble for you, I just really had to be extra sure that there was nothing "sketchy"-ish going on here. Feel free to experiment. (P.S. the SVN thing could potentially work, it's just that triggering the workflow itself may be a bit tricky)
MichaelAgarkov commented 2024-11-04 10:50:05 +00:00
Author

Thanks for letting me use it.
But I'm getting "org_access_denied" when trying to login @ https://ci.codeberg.org/

Thanks for letting me use it. But I'm getting "org_access_denied" when trying to login @ https://ci.codeberg.org/
n0toose commented 2024-11-05 20:20:45 +00:00
Owner

lgtm!

lgtm!
codeberg-cibot commented 2024-11-05 20:20:53 +00:00
Owner

Access granted.

@MichaelAgarkov

Access granted. @MichaelAgarkov
n0toose commented 2024-11-05 20:21:07 +00:00
Owner

hi, i wrote LGTM which our bot doesn't respond to, apparently. sorry!

hi, i wrote `LGTM` which our bot doesn't respond to, apparently. sorry!
Sign in to join this conversation.
No labels
ci
ci
license
ci
private
meta
resources
limit
resources
private
resources
storage
stickers
username
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Codeberg-e.V./requests#425
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?