Re: is there any plugins that just sets up a Google cloud environment?

[Filippo Morelli]

I have not and as awesome as it may look I don't think we're in a position
to switch to it right now, thanks tho.

On Fri, Apr 12, 2019 at 7:28 PM Jenn Briden  wrote:

> Have you looked at using Jenkins X?
>
> On Fri, Apr 12, 2019 at 8:56 AM SpikeX 
> wrote:
>
>> Hello,
>>
>> I'm looking for a plugin that sets up the environment before a job is ran
>> so that the job can use gsuti/gcloud utilities and spin up instances/do
>> stuff on Google Cloud.
>>
>> Looking at the plugins on the registry none of them seems to do that
>> and/or work. The closest is the Oauth plugin, but that seems more oriented
>> to getting the service account set up than prepping an environment and I've
>> been unable to get it to work (no secret can even be selected from a
>> binding). Also this plugin doesn't work with pipelines and the
>> recommendation is to just upload the json key as a secret file. This is
>> what I'm doing, however it basically leaves to each build job to duplicate
>> the code necessary to set up the environment so that the google sdk works
>> with out project. The Google SDK plugin is outdated and when I tried I
>> could not get it to work either. All the other plugins seem to work with
>> specific subcomponents like storage or the GCE one is oriented to spinning
>> up slaves on GCE, not use GCE as part of the build process.
>>
>> any pointers?
>>
>> thanks,
>>
>> Spike
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/951ae074-811d-42a1-acbc-e2076857f268%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAOC%3D136Vg7DqsT6%2Bua5O4aoo%2BwCqY8s3ao40hdnBVS8SkdfB2Q%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Filippo "Spike" Morelli
Xcalar Technical Staff
(415)-727-7453

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CACqu10PGmK-_oNn-Wsxyjo3y_PqoNDceKcmvUGsn-SH4zokdxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: is there any plugins that just sets up a Google cloud environment?

[Jenn Briden]

Have you looked at using Jenkins X?

On Fri, Apr 12, 2019 at 8:56 AM SpikeX 
wrote:

> Hello,
>
> I'm looking for a plugin that sets up the environment before a job is ran
> so that the job can use gsuti/gcloud utilities and spin up instances/do
> stuff on Google Cloud.
>
> Looking at the plugins on the registry none of them seems to do that
> and/or work. The closest is the Oauth plugin, but that seems more oriented
> to getting the service account set up than prepping an environment and I've
> been unable to get it to work (no secret can even be selected from a
> binding). Also this plugin doesn't work with pipelines and the
> recommendation is to just upload the json key as a secret file. This is
> what I'm doing, however it basically leaves to each build job to duplicate
> the code necessary to set up the environment so that the google sdk works
> with out project. The Google SDK plugin is outdated and when I tried I
> could not get it to work either. All the other plugins seem to work with
> specific subcomponents like storage or the GCE one is oriented to spinning
> up slaves on GCE, not use GCE as part of the build process.
>
> any pointers?
>
> thanks,
>
> Spike
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/951ae074-811d-42a1-acbc-e2076857f268%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAOC%3D136Vg7DqsT6%2Bua5O4aoo%2BwCqY8s3ao40hdnBVS8SkdfB2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

is there any plugins that just sets up a Google cloud environment?

[SpikeX]

Hello,

I'm looking for a plugin that sets up the environment before a job is ran 
so that the job can use gsuti/gcloud utilities and spin up instances/do 
stuff on Google Cloud.

Looking at the plugins on the registry none of them seems to do that and/or 
work. The closest is the Oauth plugin, but that seems more oriented to 
getting the service account set up than prepping an environment and I've 
been unable to get it to work (no secret can even be selected from a 
binding). Also this plugin doesn't work with pipelines and the 
recommendation is to just upload the json key as a secret file. This is 
what I'm doing, however it basically leaves to each build job to duplicate 
the code necessary to set up the environment so that the google sdk works 
with out project. The Google SDK plugin is outdated and when I tried I 
could not get it to work either. All the other plugins seem to work with 
specific subcomponents like storage or the GCE one is oriented to spinning 
up slaves on GCE, not use GCE as part of the build process.

any pointers?

thanks,

Spike

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/951ae074-811d-42a1-acbc-e2076857f268%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.