> Then it is easy to use our own Jenkins-stored creds > (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.jenkins.io_doc_book_using_using-2Dcredentials_&d=DwIFaQ&c=adz96Xi0w1RHqtPMowiL2g&r=42Z7FyMoAS1DbvgKNjU8zxi7xTPVAGalPzk7bfmRVgw&m=Oa7qm3rmqlXgK8wUUTEnADpIgZT18tE6W-ghG1QUspU&s=vRKVrs-iZa60eTjfvdc1aggzj_-CyObd2xs70PdN1rs&e= > ), or Infra can > give us a pair to use instead. >
Ahh! Do we have rights to store credentials in the ASF jenkins? I was under the impression INFRA had to do this for us. This goes to the crux of the problem raised: the original request on INFRA, i.e. to have "credentials stored in an appropriate manner". Gavin, is it an acceptable approach to have projects create their own dockerhub accounts and to store those credentials in jenkins themselves as a way to solve the rate-limiting of apache/* namespace images?
