Maven dependencies-ka waa la soo dejiyaa, ka dib Jib wuu fashilmaa marka uu la xiriiro registry. Tani waa tilmaan faa'iido leh: gelitaanka repository-ga Maven way shaqaynaysay, laakiin ma aanay shaqaysiin client-ka registry-ga ee Jib.

Ka bilow URL-ka fashilmay

Hawl fashilantayHabaynta proxy ee la baarayo
Plugin-ka Maven ama soo qaadashada dependencyProxy-ga repository-ga ee firfircoon ee settings.xml iyo ka-reebista.
Codsiga sawirka saldhigga ama token-ka registry ee JibSifooyinka shabakadda Java ee Jib u isticmaalo isgaarsiinta registry-ga.

Dhexdhexaadiye HTTP oo aan la xaqiijin, ku sheeg wadada Jib gelitaanka Maven:

mvn -Dhttp.proxyHost=proxy.example.net \
    -Dhttp.proxyPort=8080 \
    -Dhttps.proxyHost=proxy.example.net \
    -Dhttps.proxyPort=8080 \
    -Dhttp.nonProxyHosts='localhost|127.*|*.internal.example' \
    jib:buildTar

Isticmaal host-ka iyo port-ka dhabta ah ee proxy-ga adigoo haysta habaynta sawirka Jib ee mashruuca. Registry dadweyne iyo adeeg token oo ku yaal waddo proxy dadweyne oo la ogolaaday, liiska proxy-ga HTTP wuxuu bixiyaa musharaxiin kuwan qaybaha proxy ee aan la xaqiijin. Sifooyinka host waxay qaataan magacyada host, iyada oo aan lahayn horgalaha http://. Sifooyinka https waxay doortaan proxy-ga meelaha HTTPS; Java waxay sidoo kale u isticmaashaa http.nonProxyHosts liiska ka-gudubka HTTPS.

Kayd maxalli ah ayaa weli u baahan kara soo jiidasho

jib:buildTar wuxuu kaydka sawirka natiijada ku qoraa gudaha. Si kastaba ha ahaatee waxaa laga yaabaa inuu u baahdo gelitaan shabakadeed si uu marka hore u helo sawirka saldhigga. Doorashada wax-soo-saarkaas ma tirito codsiga registry-ga.

Ka dib beddelka habaynta, isbarbardhig URL-ka fashilmay mar kale. Hay habaynta repository-ga Maven ee shaqaynaysa, oo baar cillad kasta oo hadhay oo registry ama adeeg token ah oo ku taal wadada Jib.

Maqaallo la xiriira