[JIRA] (JENKINS-42028) Enable human to assume ownership of a held lock

2017-02-14 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42028  
 
 
  Enable human to assume ownership of a held lock   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 lockable-resources-plugin  
 
 
Created: 
 2017/Feb/14 6:31 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Christopher Eck  
 

  
 
 
 
 

 
  Add an option on the Lockable Resource page that enables a human to take control of a currently locked resource without releasing it first.  — We are using lockable resources in our CD pipeline to protect each of our environments: head, staging, and production while performing a push + running automated integration testing. As part of our staging -> production push, we perform a manual test pass. I'd like to be able to take ownership of the "staging" lock while performing the manual test pass so I can prevent other commits from pushing to the environment while I'm testing. Today, if the staging lock isn't already held, I can go to the Lockable Resource page and take ownership of the lock and everything is great. However, if the lock is held by a commit currently pushing or running automated testing in staging, then I have to wait. Worse is if there are multiple other commits backed up waiting on the lock as well. There's no opportunity for me to take the lock for potentially hours. I could forcibly release the lock, but that allows the next queued job to take it before I can. I really want an option where I can take control of the lock without releasing it to any waiters.

[JIRA] (JENKINS-27039) Option for input or stage step to cancel older executions

2017-02-09 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck commented on  JENKINS-27039  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Option for input or stage step to cancel older executions   
 

  
 
 
 
 

 
 This arguably makes the input step dangerous for declarative pipeline users...is there a way to make this experience better for users out of the box?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-27039) Option for input or stage step to cancel older executions

2017-02-09 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck commented on  JENKINS-27039  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Option for input or stage step to cancel older executions   
 

  
 
 
 
 

 
 Unless I'm missing something, I don't believe this feature/plugin addresses the original request? Imagine my pipeline looks like: ... milestone 100 input "Should I proceed? milestone 200 ... Commit A for my master branch comes along, the pipeline runs, and I hang waiting on the input. Commit B comes up 30 minutes later, runs through the pipeline, and is now hung waiting on the input. With a busy master branch, this ends up wasting a lot of nodes as each input step sits on the node it's running on. Ideally, I would mark the input with a milestone tag (or something similar) such that when commit B gets to the input, commit A is aborted automatically.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-33632) docker.inside broken

2016-09-06 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck commented on  JENKINS-33632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.inside broken   
 

  
 
 
 
 

 
 Nice! Looking forward to trying it out. Is there a timeline for the next release?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-33632) docker.inside broken

2016-08-29 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck commented on  JENKINS-33632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.inside broken   
 

  
 
 
 
 

 
 Jesse, the problem seems to be that the plugin isn't issuing --volumes-from in this case. It's still attempting to use -v.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-33632) docker.inside broken

2016-08-16 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck commented on  JENKINS-33632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.inside broken   
 

  
 
 
 
 

 
 In my environment, we're running the jenkins master and slaves as containers within kubernetes. I'm passing /var/run/docker.sock into each slave container so it connects to the local host's docker daemon. On a slave, I'm attempting to run docker.inside on a newly built container and seeing this behavior. I expect, based on what I read of the demo, that this should work properly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-33632) docker.inside broken

2016-08-15 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck edited a comment on  JENKINS-33632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.inside broken   
 

  
 
 
 
 

 
 Also seeing this issue - blocking us from migrating our build to Jenkins.I expect we're supposed to be seeing --volumes-from instead of -vJenkins: 2.17Docker: 1.10.3The demo doesn't mount /var/lib/jenkins or any other host path into the jenkins host container, and it doesn't appear to use slave containers to run the workflow steps, so I'm not sure how this works in the demo case either... I'd like to reopen this issue as it doesn't appear to be working properly and there are no good docs that I can find on how to set up the Jenkins master and slave containers.  I'll give it a day or two and re-open if I don't hear anything.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-33632) docker.inside broken

2016-08-15 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck edited a comment on  JENKINS-33632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.inside broken   
 

  
 
 
 
 

 
 Also seeing this issue - blocking us from migrating our build to Jenkins.I expect we're supposed to be seeing --volumes-from instead of -vJenkins: 2.17Docker: 1.10.3 The demo doesn't mount /var/lib/jenkins or any other host path into the jenkins host container, and it doesn't appear to use slave containers to run the workflow steps, so I'm not sure how this works in the demo case either...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-33632) docker.inside broken

2016-08-15 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck commented on  JENKINS-33632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.inside broken   
 

  
 
 
 
 

 
 Also seeing this issue - blocking us from migrating our build to Jenkins. I expect we're supposed to be seeing --volumes-from instead of -v Jenkins: 2.17 Docker: 1.10.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-36483) Unable to login with google-login plugin with 401 error

2016-07-06 Thread chrisl...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Eck created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36483  
 
 
  Unable to login with google-login plugin with 401 error   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 recampbell  
 
 
Components: 
 google-login-plugin  
 
 
Created: 
 2016/Jul/06 7:59 PM  
 
 
Environment: 
 Jenkins 2.11 running in docker, google-login-plugin 1.2.1  
 
 
Labels: 
 login  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Christopher Eck  
 

  
 
 
 
 

 
 Attempting to use the plugin with no domain or specifying a domain, I see the following stack trace. com.google.api.client.auth.oauth2.TokenResponseException: 401 Unauthorized at com.google.api.client.auth.oauth2.TokenResponseException.from(TokenResponseException.java:105) at com.google.api.client.auth.oauth2.TokenRequest.executeUnparsed(TokenRequest.java:287) at com.google.api.client.auth.openidconnect.IdTokenResponse.execute(IdTokenResponse.java:120) at org.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm$2.onSuccess(GoogleOAuth2SecurityRealm.java:173) at org.jenkinsci.plugins.googlelogin.OAuthSession.doFinishLogin(OAuthSession.java:99) at org.jenkinsci.plugins.googlelogin.GoogleOAuth2SecurityRealm.doFinishLogin(GoogleOAuth2SecurityRealm.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at