Shipyard dead?

[BC89]

Is shipyard a dead project? The last update was in 2019. What is the status of the project and current MS recommendation for adopting Batch? Please revisit documentation and make it clear.

Thx,
-BC

[BC89]

I have to say that the Batch service documentation and activity/responsiveness is quite pathetic. As MS fires more folks I'm sure this project will suffer along with the rest of Azure and general support. Shameful!

[staer]

Hi @BC89 - I apologize for the delay here. I do not know the status of the shipyard project, tagging @alfpark as he probably knows. My guess is that it is in maintenance mode and has been for some time.

[alfpark]

@BC89 apologies for the slow responses here. Batch Shipyard is currently not under active development. There are plans to do one fixup release addressing select backlog of bugs, dependency updates, and a README update indicating the status.

Batch Shipyard is considered an accelerator toolkit, and is by no means the sole mechanism for adopting Batch. Please review our documentation on using the Batch CLI, Portal or SDK.

Can you please expand on which part of our documentation is lacking? We can try to address these gaps.

[ltalirz]

The README update with the status would indeed be helpful guidance for new users.

[BC89]

Agreed. Also in azure batch I see references to ADAL and batch with C# examples are in an out of support .net framework, not .net core. Python references are all old too. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Leopold Talirz ***@***.***> Sent: Monday, January 30, 2023 6:33:05 PM To: Azure/Batch ***@***.***> Cc: Brendan Carroll ***@***.***>; Mention ***@***.***> Subject: [External Email] Re: [Azure/Batch] Shipyard dead? (Issue #147) ***From ***@***.*** 410-316-7820 *** This is an External Email from outside of KCI.***

________________________________ The README update with the status would indeed be helpful guidance for new users. — Reply to this email directly, view it on GitHub<#147 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAZFIM6JW5QIWWTJ4PGHSUDWVBFTDANCNFSM6AAAAAAT3O52ZM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[maroony]

We using shipyard to run docker container workloads for a few years now. It is the center of our calculations we have to do monthly. It was never clear to me that shipyard is only "an accelerator toolkit" and should not used for production environments. Who should use such a tool instead?

See also Run container applications on Azure Batch:

For easy deployment of container workloads on Azure Batch through Shipyard recipes, see the Batch Shipyard toolkit.

Shipyard is mentioned there as the "Go-to-Tool" for such a demand. We put in a lot of work to configure shipyard and build your tools around it. It seams to me, that we have to do this work again now...

Please update readme's and docs to inform (warn) your customers asap!

[alfpark]

Thanks for pointing out the additional links the docs; they have been removed.

Repository README and status has been updated.