Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View GCloud SDK on the plugin site for more information.

Allows users to invoke gcloud tools with jenkins credentials

2 Comments

  1. Unknown User (duckworth)

    Has anyone been able to get this to work? No matter what I try it doesn't add the correct path to the gcloud installation. 

    [workspace] $ gcloud help
    FATAL: Cannot run program "gcloud" (in directory "/var/lib/jenkins/jobs/johntest/workspace"): error=2, No such file or directory
    java.io.IOException: Cannot run program "gcloud" (in directory "/var/lib/jenkins/jobs/johntest/workspace"): error=2, No such file or directory
    	at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047)
    	at hudson.Proc$LocalProc.<init>(Proc.java:240)
    	at hudson.Proc$LocalProc.<init>(Proc.java:212)
    	at hudson.Launcher$LocalLauncher.launch(Launcher.java:815)
    	at hudson.Launcher$ProcStarter.start(Launcher.java:381)
    	at hudson.Launcher$ProcStarter.join(Launcher.java:388)
    	at com.byclosure.jenkins.plugins.gcloud.GCloudSDKBuilder.executeGCloudCLI(GCloudSDKBuilder.java:45)
    	at com.byclosure.jenkins.plugins.gcloud.GCloudSDKBuilder.perform(GCloudSDKBuilder.java:37)
    	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
    	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
    	at hudson.model.Build$BuildExecution.build(Build.java:205)
    	at hudson.model.Build$BuildExecution.doRun(Build.java:162)
    	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
    	at hudson.model.Run.execute(Run.java:1741)
    	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    	at hudson.model.ResourceController.execute(ResourceController.java:98)
  2. Unknown User (gaccardo)

    We've got exactly the same issue.  If I run gcloud via Windows batch command, it works as expected.  If I do it with this plugin, I get the same error shown above.  Perhaps there is some configuration that needs to be done, but I'm not sure why the plugin would try to run this from the job's workspace rather than a defined tool location.  Any fix would be greatly appreciated.