Re: Jenkins SAML with google

2020-10-14 Thread Gautam, Rishi 
Thank you Ivan for responding, but that didn't worked for me as well.

On Wed, Oct 14, 2020 at 10:33 PM Ivan Fernandez Calvo <
kuisathave...@gmail.com> wrote:

> Hi,
>
> you have how to do it in the documentation of the plugin
> https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md#configuring-groups-security
>
> El miércoles, 14 de octubre de 2020 a las 13:52:07 UTC+2, Rishi Gautam
> escribió:
>
>> Using role based strategy, is there any way to give default permission to
>> all logged in users?
>> I used authenticated group but it is not working and always forwarded to
>> logout.
>>
>> Also, how to enable permission for groups in google?
>>
> --
> 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/83dd4f84-8b73-4412-b3cf-ba2d64cde25fn%40googlegroups.com
> 
> .
>

-- 
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/CAF4beLiW3rScjEyt0M6fU3ARF0BuNDBAn7Wy3koy4Oh24m8ROw%40mail.gmail.com.

Re: Jenkins Git Init Fails

2020-10-14 Thread Mark Waite 
Several alternatives:

   - If the repository is a smaller repository (less than 50 MB), then you
   could enable JGit 
   in your installation and use JGit instead of command line git to perform
   the checkout.
   - Define a "git tool" for that target machine which will install and use
   a newer version command line git on that agent.
   - Compile a recent version of command line git on that target machine
   yourself so that it has the recent version available.
   - Replace 'checkout scm' by shell calls to perform the equivalent
   operation (git init, git config, git fetch, git checkout)

Command line git is now version 2.28.0, with 2.29.0 ready to release very
soon.  Using command line git versions prior to 2.0 will miss many, many
improvements that have been made to command line git.

On Wed, Oct 14, 2020 at 10:21 AM Sverre Moe  wrote:

> Cloning Git with an old version of Git now seems to fail
>
> Cloning the remote Git repository ERROR: Error cloning remote repo
> 'origin' hudson.plugins.git.GitException: Could not init
> /home/build/jenkins/workspace/rebuild-packages/base at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:990)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:748)
> at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161)
> at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154)
> at hudson.remoting.UserRequest.perform(UserRequest.java:211) at
> hudson.remoting.UserRequest.perform(UserRequest.java:54) at
> hudson.remoting.Request$2.run(Request.java:369) at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) Suppressed:
> hudson.remoting.Channel$CallSiteStackTrace: Remote call to
> sles11.0-x86_64_2 at
> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at
> hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
> at hudson.remoting.Channel.call(Channel.java:998) at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
> at sun.reflect.GeneratedMethodAccessor569.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
> at com.sun.proxy.$Proxy111.execute(Unknown Source) at
> hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1122) at
> hudson.plugins.git.GitSCM.checkout(GitSCM.java:1167) at
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:125)
> at
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)
> at
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)
> at
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> ... 4 more Caused by: hudson.plugins.git.GitException: Command "git init
> /home/build/jenkins/workspace/rebuild-packages/base" returned status code
> 129: stdout: stderr: usage: git init [-q | --quiet] [--bare]
> [--template=] [--shared[=]] at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2360)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2356)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1916)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:988)
> ... 11 more
>
> Is there any way to modify the git checkout to work around this problem?
>
>checkout(
> changelog: false,
> poll: false,
> scm: [$class: 'GitSCM',
> branches: [
> [name: "origin/" + releaseBranch]
> ],
> doGenerateSubmoduleConfigurations: false,
> extensions: [
> [$class: 'CloneOption', depth: 0, noTags:
> false, reference: '', shallow: false, timeout: 25],
> [$class: 'RelativeTargetDirectory',
> relativeTargetDir: projectName]
> ],
>

Re: Jenkins SAML with google

2020-10-14 Thread Ivan Fernandez Calvo 
Hi,

you have how to do it in the documentation of the plugin 
https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md#configuring-groups-security

El miércoles, 14 de octubre de 2020 a las 13:52:07 UTC+2, Rishi Gautam 
escribió:

> Using role based strategy, is there any way to give default permission to 
> all logged in users? 
> I used authenticated group but it is not working and always forwarded to 
> logout. 
>
> Also, how to enable permission for groups in google?
>

-- 
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/83dd4f84-8b73-4412-b3cf-ba2d64cde25fn%40googlegroups.com.

Jenkins Git Init Fails

2020-10-14 Thread Sverre Moe 
Cloning Git with an old version of Git now seems to fail

Cloning the remote Git repository ERROR: Error cloning remote repo 'origin' 
hudson.plugins.git.GitException: Could not init 
/home/build/jenkins/workspace/rebuild-packages/base at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:990) 
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:748) 
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161)
 
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154)
 
at hudson.remoting.UserRequest.perform(UserRequest.java:211) at 
hudson.remoting.UserRequest.perform(UserRequest.java:54) at 
hudson.remoting.Request$2.run(Request.java:369) at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 
at java.util.concurrent.FutureTask.run(FutureTask.java:266) at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
at java.lang.Thread.run(Thread.java:748) Suppressed: 
hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
sles11.0-x86_64_2 at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) 
at hudson.remoting.Channel.call(Channel.java:998) at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
 
at sun.reflect.GeneratedMethodAccessor569.invoke(Unknown Source) at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
at java.lang.reflect.Method.invoke(Method.java:498) at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
 
at com.sun.proxy.$Proxy111.execute(Unknown Source) at 
hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1122) at 
hudson.plugins.git.GitSCM.checkout(GitSCM.java:1167) at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:125) 
at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)
 
at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)
 
at 
org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
 
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
... 4 more Caused by: hudson.plugins.git.GitException: Command "git init 
/home/build/jenkins/workspace/rebuild-packages/base" returned status code 
129: stdout: stderr: usage: git init [-q | --quiet] [--bare] 
[--template=] [--shared[=]] at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430)
 
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2360)
 
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2356)
 
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1916)
 
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:988) 
... 11 more

Is there any way to modify the git checkout to work around this problem?

   checkout(
changelog: false,
poll: false,
scm: [$class: 'GitSCM',
branches: [
[name: "origin/" + releaseBranch]
],
doGenerateSubmoduleConfigurations: false,
extensions: [
[$class: 'CloneOption', depth: 0, noTags: 
false, reference: '', shallow: false, timeout: 25],
[$class: 'RelativeTargetDirectory', 
relativeTargetDir: projectName]
],
submoduleCfg: [],
userRemoteConfigs: [
[credentialsId: 'c9c2577f-f23', url: URI]
]
]
)

-- 
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/744aad86-7046-411e-9f40-cbd83f5954c8n%40googlegroups.com.

Jenkins - Kubernetes YAML Deployment - Api call failed with code 0

2020-10-14 Thread Enes Lanpir 
Hi,


I have been trying to deploy a yaml file to Kubernetes that I have pull 
from Github via Jenkins. At first I got an api version error, after plug in 
downgrades, when I started my pipeline, I got a different error.

I cannot find the solution to the problem below that I shared with you. 
Could you please help me with why I am getting this error and how to fix it?

Thanks,
Starting Kubernetes deployment Loading configuration: 
/var/lib/jenkins/workspace/k8sdeploy/k8sdeploy.yml Api call failed with 
code 0, detailed message: null ERROR: ERROR: java.lang.RuntimeException: 
io.kubernetes.client.openapi.ApiException: java.net.SocketException: Broken 
pipe (Write failed) hudson.remoting.ProxyException: 
java.lang.RuntimeException: io.kubernetes.client.openapi.ApiException: 
java.net.SocketException: Broken pipe (Write failed) at 
com.microsoft.jenkins.kubernetes.wrapper.ResourceManager.handleApiExceptionExceptNotFound(ResourceManager.java:180)
 
at 
com.microsoft.jenkins.kubernetes.wrapper.V1ResourceManager$DeploymentUpdater.getCurrentResource(V1ResourceManager.java:213)
 
at 
com.microsoft.jenkins.kubernetes.wrapper.V1ResourceManager$DeploymentUpdater.getCurrentResource(V1ResourceManager.java:201)
 
at 
com.microsoft.jenkins.kubernetes.wrapper.ResourceManager$ResourceUpdater.createOrApply(ResourceManager.java:93)
 
at 
com.microsoft.jenkins.kubernetes.wrapper.KubernetesClientWrapper.handleResource(KubernetesClientWrapper.java:289)
 
at 
com.microsoft.jenkins.kubernetes.wrapper.KubernetesClientWrapper.apply(KubernetesClientWrapper.java:256)
 
at 
com.microsoft.jenkins.kubernetes.command.DeploymentCommand$DeploymentTask.doCall(DeploymentCommand.java:172)
 
at 
com.microsoft.jenkins.kubernetes.command.DeploymentCommand$DeploymentTask.call(DeploymentCommand.java:124)
 
at 
com.microsoft.jenkins.kubernetes.command.DeploymentCommand$DeploymentTask.call(DeploymentCommand.java:106)
 
at hudson.FilePath.act(FilePath.java:1163) at 
com.microsoft.jenkins.kubernetes.command.DeploymentCommand.execute(DeploymentCommand.java:68)
 
at 
com.microsoft.jenkins.kubernetes.command.DeploymentCommand.execute(DeploymentCommand.java:45)
 
at 
com.microsoft.jenkins.azurecommons.command.CommandService.runCommand(CommandService.java:88)
 
at 
com.microsoft.jenkins.azurecommons.command.CommandService.execute(CommandService.java:96)
 
at 
com.microsoft.jenkins.azurecommons.command.CommandService.executeCommands(CommandService.java:75)
 
at 
com.microsoft.jenkins.azurecommons.command.BaseCommandContext.executeCommands(BaseCommandContext.java:77)
 
at 
com.microsoft.jenkins.kubernetes.KubernetesDeploy.perform(KubernetesDeploy.java:42)
 
at 
com.microsoft.jenkins.azurecommons.command.SimpleBuildStepExecution.run(SimpleBuildStepExecution.java:54)
 
at 
com.microsoft.jenkins.azurecommons.command.SimpleBuildStepExecution.run(SimpleBuildStepExecution.java:35)
 
at 
org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
 
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
at java.util.concurrent.FutureTask.run(FutureTask.java:266) at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
at java.lang.Thread.run(Thread.java:748) Caused by: 
hudson.remoting.ProxyException: io.kubernetes.client.openapi.ApiException: 
java.net.SocketException: Broken pipe (Write failed) at 
io.kubernetes.client.openapi.ApiClient.execute(ApiClient.java:898) at 
io.kubernetes.client.openapi.apis.AppsV1Api.readNamespacedDeploymentWithHttpInfo(AppsV1Api.java:7299)
 
at 
io.kubernetes.client.openapi.apis.AppsV1Api.readNamespacedDeployment(AppsV1Api.java:7275)
 
at 
com.microsoft.jenkins.kubernetes.wrapper.V1ResourceManager$DeploymentUpdater.getCurrentResource(V1ResourceManager.java:210)
 
... 23 more Caused by: hudson.remoting.ProxyException: 
java.net.SocketException: Broken pipe (Write failed) at 
java.net.SocketOutputStream.socketWrite0(Native Method) at 
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111) at 
java.net.SocketOutputStream.write(SocketOutputStream.java:155) at 
sun.security.ssl.OutputRecord.writeBuffer(OutputRecord.java:431) at 
sun.security.ssl.OutputRecord.write(OutputRecord.java:417) at 
sun.security.ssl.SSLSocketImpl.writeRecordInternal(SSLSocketImpl.java:894) 
at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:865) at 
sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123) at 
okio.Okio$1.write(Okio.java:79) at 
okio.AsyncTimeout$1.write(AsyncTimeout.java:180) at 
okio.RealBufferedSink.flush(RealBufferedSink.java:224) at 
okhttp3.internal.http2.Http2Writer.settings(Http2Writer.java:185) at 
okhttp3.internal.http2.Http2Connection.start(Http2Connection.java:499) at 
okhttp3.internal.http2.Http2Connection.start(Http2Connection.java:489) at

Jenkins SAML with google

2020-10-14 Thread Rishi Gautam 
Using role based strategy, is there any way to give default permission to 
all logged in users? 
I used authenticated group but it is not working and always forwarded to 
logout. 

Also, how to enable permission for groups in google?

-- 
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/b9ff9414-cb06-41dd-be90-ec24fc830409n%40googlegroups.com.

Join organization jenkinsci

2020-10-14 Thread YanJun Shi 
Hi
Team
I want to join the organization ‘jenkinsci’ for GitHub. Who can invite
me to join? My GitHub ID is yJunS.
There are my pull requests:
https://github.com/pulls?q=user%3Ajenkinsci+author%3AyJunS
Thanks.

-- 
Shi Yanjun(yJunS)
Blog:https://github.com/yJunS

-- 
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/CALfBRDoMzonijaMG2HG%2BuOvZEU1%3D1h1fMW0KhNOovZbhNwU7eA%40mail.gmail.com.