-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support for Maven with GAR #111
base: main
Are you sure you want to change the base?
Conversation
This reverts commit 371b2a3.
- run: | ||
name: install gcloud | ||
command: | | ||
curl https://sdk.cloud.google.com > install.sh | ||
bash install.sh --disable-prompts | ||
export PATH=/home/circleci/google-cloud-sdk/bin/:${PATH} | ||
gcloud components install kubectl | ||
echo 'export PATH=/home/circleci/google-cloud-sdk/bin/:${PATH}' >> $BASH_ENV |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is the runtime for this? 😟
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hehe yep, I had the same worry... what we agreed with @robert-nemet was to first make it work, and then see how to optimize it.
IIRC the idea would be to have an executor that has the tooling already installed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my experience 20 months ago was
- pulling a custom executor image adds 1min to your build
- installing gcloud stuff adds >1min to your build
so either way im kinda worried, unless its an image replacing a custom image (in which case the additional time was already a reality)
https://www.notion.so/smgnet/From-JFrog-to-GAR-169a151798304c70a12792443379db55?pvs=4