You are viewing a plain text version of this content. The canonical link for it is here.

Posted to builds@apache.org by Daniel Gruno <hu...@apache.org> on 2023/07/11 05:41:06 UTC

[Notice] Issues with credentials on ephemeral jenkins nodes

Hi folks,

This is a note in the margin that we are seeing issues with builds running on our ephemeral jenkins nodes that require credentials (for example for dockerhub, nexus, etc).

To mitigate any issues, we've set a label called "nocredentials" on these nodes for the time being, while we sort this out. Builds that require credentials for publishing or otherwise interacting with protected resources can add "!nocredentials" to their build labels to avoid using these nodes.

Once the issue has been sorted, we will remove the labels as applicable.

With regards,
Daniel.

Re: [Notice] Issues with credentials on ephemeral jenkins nodes

Posted by Daniel Gruno <hu...@apache.org>.

To be very explicit here, additional label conditions should be AND'ed together.
Thus, if your previous label was "ubuntu", then the new one should be "ubuntu && !nocredentials" in order to avoid using a non-credentialed build node.

On 2023/07/11 05:41:06 Daniel Gruno wrote:
> Hi folks,
> 
> This is a note in the margin that we are seeing issues with builds running on our ephemeral jenkins nodes that require credentials (for example for dockerhub, nexus, etc).
> 
> To mitigate any issues, we've set a label called "nocredentials" on these nodes for the time being, while we sort this out. Builds that require credentials for publishing or otherwise interacting with protected resources can add "!nocredentials" to their build labels to avoid using these nodes.
> 
> Once the issue has been sorted, we will remove the labels as applicable.
> 
> With regards,
> Daniel.
>