Topics created by marc.ledent_9164

Hi Marc, I'm not sure what you mean by 2024.8-r1 but the -ci.x and -rc.x images are prerelease versions. Sometimes they are the same as the release versions, sometimes they aren't. I wouldn't use prerelease versions unless we suggest them to you for a specific issue you're facing. -- Dean

Hi Marc, Thanks for the note! That file is actually a sort of cross-platform way of storing symbolic links. BuildMaster also includes all the binaries needed for agents on both Windows and Linux, including .net runtimes for all three. In order to save space we deduplicate identical binaries from the agents. We use a simple json file instead of proper symlinks because we use the same file on Windows/Linux and it's easier this way. All the paths in the file have historically used Windows path separators due to how we generate it, and we convert those in BuildMaster at runtime to the proper format.... or at least we were supposed to. At some point there was a regression added that caused this to not happen when updating from Linux. Anyway, this will be fixed as BM-3981 in the next release :)

Hi @marc-ledent_9164 , This is available in InedoCore-3.0.4, so if you go to Admin > Extensions, you should be bale to update. thanks, Alana

Hi @atripp , Thanks for the suggestions. Concerning the LogMessages table, we already have those messages displayed on the OpenShift console, but nothing suspect can be seen. What I'll try is to test a fresh install of the last BuildMaster version and see what difference we have with our "updated" version. I'll keep you in touch. Marc

@atripp Thanks for your reply... This is a good reason to planify an upgrade! Marc

Hi @marc-ledent_9164 , Are you referring to the Machine UID from Manual Activation? I'm not sure what the Machine UID looks like in BuildMaster 7 on Linux, but I do recall that early versions of our products sometimes couldn't generate the string on some hardware. I think that's fixed now. The code is supposed to be based on the CPU (vendor ID, model, family, and stepping info) and the and the major version of the Inedo software (e.g. 5.1, 5.3, 2022, 2023). Thanks, Alana

Hi @marc-ledent_9164 , That refers to our build server :) That part of the error message is the stack trace, and that shows us exactly where the error is occurring in the code, should we need to debug it. That said, if you're seeing those errors in your execution logs, then it's probably related to configuration of some kind..... we can help if we could see more context Cheers, Alana

I've seen your message yesterday. I will investigate as soon I have the correct environment. Thanks for the help!

Thanks Alana!

Replying to myself: This is due to chromium protection feature. I successfully downloaded it via Firefox. Solved then

OK, by selecting the correct version, I managed to upgrade manually the extensions. Many thanks for your time, Marc

Hi @marc-ledent_9164 , This isn't something that our LDAP/AD integration supports on Linux at this time. It's possible using the Windows-version, which has an LDAP integration that uses different libraries (that only work on Windows). We do plan on rewriting the LDAP/AD integration with a different library, as to allow this level of customization, but it's not something we can do right away. It'll be later this year. Cheers, Alana

Hi @marc-ledent_9164, There's really just one, and that's the artifacts (BuildMaster) or packages (ProGet). To configure server level shared storage, you'll want to configure: For BuildMaster, the Artifacts.BasePath value in Administration > Advanced Settings. For ProGet, the Storage.PackagesRootPath value in Administration > Advanced Settings. Do note that ProGet also allows configuration of storage at a feed level, which you can find on the Manage Feed page for each feed. Click change on the right side of the Disk Path property. This guide might be helpful: https://docs.inedo.com/docs/installation-high-availability-load-balancing

Hi @marc-ledent_9164, Thanks for letting us know this is now resolved. Thanks, Dan

OK, I got it. the servers are the ssh servers tha BM is connecting to while deploying. As this is a test env, there are a lot of faulty servers Thanks for the help, Marc

Hi @marc-ledent_9164, Thanks for following up and letting us know that fixed the issue. We are currently in the process of cleaning up our activation process in the v2022 versions of our products. This issue should be corrected in the next major version of our products. Thanks, Dan

Hi @marc-ledent_9164, Thanks for following up and letting everyone know that this fixed your issue! Thanks, Dan

@Dan_Woolf Thanks for the explanation. I'll try it as soon as I can re-activate my trial license...

Thanks for the answer, I'll ask the team!

Hi @marc-ledent_9164, BuildMaster requires SQL Server to run and cannot be replaced with PostgreSQL. But, you can use BuildMaster to manage the change scripts for a PostgreSQL database. You will just need to install the PostgreSQL extension and create a PostgreSQL database connection. You can learn more by reviewing our CI/CD for Databases documentation. Please let us know if you have any other questions! Thanks, Dan