You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, you can specify a custom startup script. This startup script may still be running when the agent starts and begins to process builds. Depending on how critical that script is, the build may be dependent on what that script does. For example, if that script rsyncs a gcs bucket, or even mounts an external drive with a git snapshot and is checked for consistency, the first build or two might fail.
Ideally, the agent wouldn't start until the google-startup-scripts has finished, but I would also be okay with just a configurable delay/sleep setting. If I could ask the plugin to wait 60 seconds or something before launching the agent, I'd be happy.
# systemctl status google-startup-scripts
● google-startup-scripts.service - Google Compute Engine user startup scripts
Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Tue 2022-06-28 02:34:54 UTC; 8min ago
Process: 9211 ExecStart=/usr/share/google/run-startup-scripts (code=exited, status=0/SUCCESS)
Main PID: 9211 (code=exited, status=0/SUCCESS)
Upstream changes
No response
The text was updated successfully, but these errors were encountered:
This would be a good feature as I use a startup script to install Java to the agent.
Agent provisioning is failing with WARNING: Java is not installed at java
What feature do you want to see added?
Currently, you can specify a custom startup script. This startup script may still be running when the agent starts and begins to process builds. Depending on how critical that script is, the build may be dependent on what that script does. For example, if that script rsyncs a gcs bucket, or even mounts an external drive with a git snapshot and is checked for consistency, the first build or two might fail.
Ideally, the agent wouldn't start until the
google-startup-scripts
has finished, but I would also be okay with just a configurable delay/sleep setting. If I could ask the plugin to wait 60 seconds or something before launching the agent, I'd be happy.Upstream changes
No response
The text was updated successfully, but these errors were encountered: