[JIRA] (JENKINS-60083) extended-choice-parameter, tag 0.79 is not available in jenkins

2019-11-07 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60083  
 
 
  extended-choice-parameter, tag 0.79 is not available in jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 vimil  
 
 
Components: 
 extended-choice-parameter-plugin  
 
 
Created: 
 2019-11-07 08:50  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Peter Niederlag  
 

  
 
 
 
 

 
 https://github.com/jenkinsci/extended-choice-parameter-plugin has a tag and release 0.79. However on our jenkins we can see only 0.78 as latest version. Is this intentional?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by

[JIRA] (JENKINS-49698) Show/Enable "Run" button in Jenkins Blue Ocean multibranch pipeline activity tab

2019-11-05 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-49698  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Show/Enable "Run" button in Jenkins Blue Ocean multibranch pipeline activity tab   
 

  
 
 
 
 

 
 would be nice to have something like this in order to unify the user experience across different job types  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188634.151930713.9228.1572955682189%40Atlassian.JIRA.

[JIRA] (JENKINS-58257) New secrets written to kubernetes store are not always loaded by Jenkins

2019-11-01 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-58257  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New secrets written to kubernetes store are not always loaded by Jenkins   
 

  
 
 
 
 

 
 ran into this as well, workaround needs a Singleton, wont work with Singletom.   

 

import com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.KubernetesCredentialProvider

def kp = ExtensionList.lookupSingleton(KubernetesCredentialProvider.class)
kp.stopWatchingForSecrets()
kp.startWatchingForSecrets()
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200321.1561744491000.6907.1572616020263%40Atlassian.JIRA.

[JIRA] (JENKINS-59698) file crippled during deploy

2019-10-10 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-59698  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: file crippled during deploy   
 

  
 
 
 
 

 
 nodejs, git deployment strategy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202398.1570524247000.4851.1570712940583%40Atlassian.JIRA.

[JIRA] (JENKINS-59698) file crippled during deploy

2019-10-08 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59698  
 
 
  file crippled during deploy   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-function-plugin  
 
 
Created: 
 2019-10-08 08:44  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Peter Niederlag  
 

  
 
 
 
 

 
 we have seen the azure-function-plugin to deploy broken/crippled files. We are quite sure they are fine inside our git/jenkins. After the deployment we found that two files had been stripped in the middle of a line. therefor the function-app broke with some files having bad content. Jenkins job went fine. git log -p on the azure scm "shado" repo uncovered a broken commit.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-59010) As User I would like to have control over the deployment mode

2019-08-22 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-59010  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: As User I would like to have control over the deployment mode   
 

  
 
 
 
 

 
 first of all, thx for getting back on this. Shouldn't it be possible to add another parameter "deploymentMode" (zip|git) to the plugin in here? https://github.com/jenkinsci/azure-function-plugin/tree/dev/src/main/resources/com/microsoft/jenkins/function/FunctionAppDeploymentRecorder And then override the isJava logic when this parameter is set to zip|git in here: https://github.com/jenkinsci/azure-function-plugin/blob/dev/src/main/java/com/microsoft/jenkins/function/FunctionAppDeploymentCommandContext.java Could this be a valid approach? Is there any further logic baked into the zip|git deployment strategies that makes them dependent on the type of the function app (java, nodejs, ...)?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201363.1566310082000.7635.1566458820131%40Atlassian.JIRA.

[JIRA] (JENKINS-59010) As User I would like to have control over the deployment mode

2019-08-20 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59010  
 
 
  As User I would like to have control over the deployment mode   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-function-plugin  
 
 
Created: 
 2019-08-20 14:08  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Peter Niederlag  
 

  
 
 
 
 

 
 currently it seems the azure-function-plugin has some super cow power and decides the deployment strategy based on: 
 
it's a java app, use zip deployment 
otherwise, use git deployment 
 It would be cool if the decision on the deployment mode could be made by the user. Also it would be important to drop a note somewhere on these decisions as - to my knowledge - the settings in the function app must correspond to the deployment mode used.  (WEBSITE_RUN_FROM_PACKAGE = "1")  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-58274) Function missing after deployment

2019-08-20 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-58274  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Function missing after deployment   
 

  
 
 
 
 

 
 deploying azure function apps is a real terrible mess from my point of view :-< Are you aware there are some hidden Environment-Settings in the function-app that somehow seem to be important in relation to the deployment? For zip based deployments you might need to set something like this in your function app: WEBSITE_RUN_FROM_PACKAGE = "1"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200338.1561960792000.6165.1566309900342%40Atlassian.JIRA.

[JIRA] (JENKINS-55577) docker agent using a custom Dockerfile is broken with docker buildkit

2019-07-08 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-55577  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker agent using a custom Dockerfile is broken with docker buildkit   
 

  
 
 
 
 

 
 anyone in on this? As BUILDKIT provides way better handling of secrets it should really be possible to use this on jenkins.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196741.1547472484000.3971.1562577420633%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-55577) docker agent using a custom Dockerfile is broken with docker buildkit

2019-07-08 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55577  
 
 
  docker agent using a custom Dockerfile is broken with docker buildkit   
 

  
 
 
 
 

 
Change By: 
 Peter Niederlag  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196741.1547472484000.3952.1562577361542%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-44869) Activity tabs Run id column should expand to fit value

2019-07-04 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-44869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Activity tabs Run id column should expand to fit value   
 

  
 
 
 
 

 
 does anybody have a solution yet? I'd like to see the RUN column to take up more space (1.5x or 2x)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182935.1497419598000.1804.1562242201910%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57369) Docker build-args incorrectly rejected and successful build marked failed

2019-07-01 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-57369  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker build-args incorrectly rejected and successful build marked failed   
 

  
 
 
 
 

 
 Thx for your feedback Eli Treuherz I tried to reply yor comments in code. It seems IsMapWithSize is not available without further work (hamcrest 1.3 limit?). I'd suggest to keep changes on the tests in line with all tests in the class.  It'd be very great if someone with insight could check on handling the value on the argMap https://github.com/jenkinsci/docker-workflow-plugin/pull/178#pullrequestreview-256220189  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199150.1557317521000.12611.1561978440201%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57369) Docker build-args incorrectly rejected and successful build marked failed

2019-07-01 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-57369  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker build-args incorrectly rejected and successful build marked failed   
 

  
 
 
 
 

 
 Here is a PR that fixes the problem: https://github.com/jenkinsci/docker-workflow-plugin/pull/178  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199150.1557317521000.12557.1561971420988%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38995) Choice parameters cannot be used inside of Multibranch Pipelines

2017-02-16 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag edited a comment on  JENKINS-38995  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Choice parameters cannot be used inside of Multibranch Pipelines   
 

  
 
 
 
 

 
 This problem is really anoying and filling quite a bunch of places on the net.It seems that the array syntax of defining the choices is not supported and must be replaced by a string that is concatenated by \n. This snippet did the trick for me:  { { code:java} properties([parameters([choice(choices: "debug\nrelease\ndev",description: '', name: 'buildType')]), pipelineTriggers([])]) {code } }   
 

  
 
 
 
 

 
 
 

 
 
 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-38995) Choice parameters cannot be used inside of Multibranch Pipelines

2017-02-16 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag edited a comment on  JENKINS-38995  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Choice parameters cannot be used inside of Multibranch Pipelines   
 

  
 
 
 
 

 
 This problem is really anoying and filling quite a bunch of places on the net.It seems that the array syntax of defining the choices is not supported and must be replaced by a string that is concatenated by \n. This snippet did the trick for me:{{  properties([parameters([choice(choices: "debug\nrelease\ndev",description: '', name: 'buildType')]), pipelineTriggers([])])  }}  
 

  
 
 
 
 

 
 
 

 
 
 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-38995) Choice parameters cannot be used inside of Multibranch Pipelines

2017-02-16 Thread peter.nieder...@datenbetrieb.de (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-38995  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Choice parameters cannot be used inside of Multibranch Pipelines   
 

  
 
 
 
 

 
 This problem is really anoying and filling quite a bunch of places on the net. It seems that the array syntax of defining the choices is not supported and must be replaced by a string that is concatenated by \n. This snippet did the trick for me: {{ properties([parameters([choice(choices: "debug\nrelease\ndev", description: '', name: 'buildType')]), pipelineTriggers([])]) }}  
 

  
 
 
 
 

 
 
 

 
 
 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.