[JIRA] (JENKINS-54324) Notifications for the input directive

2018-10-29 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54324  
 
 
  Notifications for the input directive   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2018-10-29 20:28  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kurt Madel  
 

  
 
 
 
 

 
 The `input` directive allows pausing the Pipeline for input without tying up an agent/node. But a typical use case with the `input` directive is to send a notification to the audience that is intended to approve or abort the `input` directive, but this notification must be sent from the previous stage (could be as a post action). I would be nice to have notifications better integrated with the `input` directive.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 


[JIRA] (JENKINS-38220) Support for EC2 instance profile credentials

2018-10-09 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel commented on  JENKINS-38220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for EC2 instance profile credentials   
 

  
 
 
 
 

 
 This should have been resolved with https://github.com/jenkinsci/aws-credentials-plugin/pull/20 - fixed since version 1.22  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-34354) Custom Slack Notification is dropped when there is a combined Slack notification

2018-10-08 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34354  
 
 
  Custom Slack Notification is dropped when there is a combined Slack notification   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 2.3  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47711) Slack plugin unable to publish notifications during promotion process

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47711  
 
 
  Slack plugin unable to publish notifications during promotion process   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47711) Slack plugin unable to publish notifications during promotion process

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel commented on  JENKINS-47711  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slack plugin unable to publish notifications during promotion process   
 

  
 
 
 
 

 
 Nee more info, logs, etc...  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48827) Cannot set auth token Id programatically

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Use JCasC per https://github.com/jenkinsci/slack-plugin/pull/404  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48827  
 
 
  Cannot set auth token Id programatically   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51572) some user cannot open jenkins web interface

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated  JENKINS-51572  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 see https://github.com/jenkinsci/slack-plugin/pull/403  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51572  
 
 
  some user cannot open jenkins web interface   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50706) Non Administrator cannot configure credentials in the Slack Notifier step.

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated  JENKINS-50706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50706  
 
 
  Non Administrator cannot configure credentials in the Slack Notifier step.   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50706) Non Administrator cannot configure credentials in the Slack Notifier step.

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated  JENKINS-50706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 see https://github.com/jenkinsci/slack-plugin/pull/372  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50706  
 
 
  Non Administrator cannot configure credentials in the Slack Notifier step.   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 In Progress Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53450) Test failure in 'mvn test' on windows

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated  JENKINS-53450  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 see https://github.com/jenkinsci/slack-plugin/pull/394  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53450  
 
 
  Test failure in 'mvn test' on windows   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53602) Dashboard no Chart

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated  JENKINS-53602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 see https://github.com/jenkinsci/slack-plugin/pull/403  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53602  
 
 
  Dashboard no Chart   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53641) support Configuration as Code

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated  JENKINS-53641  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 see https://github.com/jenkinsci/slack-plugin/pull/404  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53641  
 
 
  support Configuration as Code   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53699) Slack plugin causes system problems

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated  JENKINS-53699  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 see https://github.com/jenkinsci/slack-plugin/pull/403  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53699  
 
 
  Slack plugin causes system problems   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41420) java.lang.NullPointerException trace bug following plugin installation

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated  JENKINS-41420  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Duplicate of JENKINS-37339   See https://github.com/jenkinsci/slack-plugin/pull/403  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41420  
 
 
  java.lang.NullPointerException trace bug following plugin installation   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37339) Global security throws NullPointerException after installing Slack Plugin

2018-10-07 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated  JENKINS-37339  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 https://github.com/jenkinsci/slack-plugin/pull/403  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37339  
 
 
  Global security throws NullPointerException after installing Slack Plugin   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-35503) Slack plugin reveals integration token

2016-11-19 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35503  
 
 
  Slack plugin reveals integration token   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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-35503) Slack plugin reveals integration token

2016-11-19 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 slack 2.1  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-35503  
 
 
  Slack plugin reveals integration token   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-35503) Slack plugin reveals integration token

2016-09-10 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel commented on  JENKINS-35503  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slack plugin reveals integration token   
 

  
 
 
 
 

 
 See https://github.com/jenkinsci/slack-plugin/pull/247 for initial fix. Still allows users to expose auth token but provides highly visible warning.  
 

  
 
 
 
 

 
 
 

 
 
 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-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes

2016-09-01 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37491  
 
 
  Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Attachment: 
 screenshot-1.png  
 

  
 
 
 
 

 
 
 

 
 
 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-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes

2016-09-01 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel commented on  JENKINS-37491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes   
 

  
 
 
 
 

 
 I may not follow correctly, but I believe one more option may be to select the 'unmerged head' for all PRs - origin and fork - and then use the GitHub protected branch feature to force branches (PRs) to be up to date with the base branch before being allowed to merge: 
 

  
 
 
 
 

 
 
 

 
 
 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-26845) Security: HipChat Plugin can leak global hipchat server host name and token

2016-08-25 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel commented on  JENKINS-26845  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Security: HipChat Plugin can leak global hipchat server host name and token   
 

  
 
 
 
 

 
 I don't understand why this still isn't a security risk. First, the token is managed via a regular text field, second - regardless if it is stored at the global config or job level, it is still stored as plain text. This needs to be managed like a password or you should look at integrating with the credentials plugin and use a credential ID that points to a secret text credential.  
 

  
 
 
 
 

 
 
 

 
 
 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-35503) Slack plugin reveals integration token

2016-08-24 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel commented on  JENKINS-35503  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slack plugin reveals integration token   
 

  
 
 
 
 

 
 One more note, in regards to the Pipeline step - you may use the  

 
withCredentials 

  wrapper - see https://jenkins.io/doc/pipeline/steps/credentials-binding/#withcredentials-bind-credentials-to-variables  
 

  
 
 
 
 

 
 
 

 
 
 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-35503) Slack plugin reveals integration token

2016-08-24 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel commented on  JENKINS-35503  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slack plugin reveals integration token   
 

  
 
 
 
 

 
 There is a PR to integrate with credentials but still a bit of work to do.  
 

  
 
 
 
 

 
 
 

 
 
 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-37260) Add PATCH Mode

2016-08-08 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37260  
 
 
  Add PATCH Mode   
 

  
 
 
 
 

 
Change By: 
 Kurt Madel  
 
 
Issue Type: 
 Bug New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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-37260) Add PATCH Mode

2016-08-08 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel commented on  JENKINS-37260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add PATCH Mode   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/http-request-plugin/pull/19  
 

  
 
 
 
 

 
 
 

 
 
 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-37260) Add PATCH Mode

2016-08-08 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37260  
 
 
  Add PATCH Mode   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Janario Oliveira  
 
 
Components: 
 http-request-plugin  
 
 
Created: 
 2016/Aug/08 3:30 PM  
 
 
Environment: 
 Jenkins 1.651.3  http_request-1.8.11  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kurt Madel  
 

  
 
 
 
 

 
 Currently, the http-request plugin does not support PATCH as an HTTP mode. There are many APIs that require the use of PATCH to update entities (GitHub, Docker Cloud, etc).  One thing to note, it appears that the underlying Jenkins Rule HTTP server does not support PATCH, therefore it may not be possible to test it with existing tests.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[JIRA] (JENKINS-35033) Support for binding of port ranges

2016-06-21 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel edited a comment on  JENKINS-35033  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for binding of port ranges   
 

  
 
 
 
 

 
 This has been  release  released : https://github.com/docker-java/docker-java/releases/tag/docker-java-3.0.0  
 

  
 
 
 
 

 
 
 

 
 
 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-35033) Support for binding of port ranges

2016-06-21 Thread kma...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Madel commented on  JENKINS-35033  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for binding of port ranges   
 

  
 
 
 
 

 
 This has been release: https://github.com/docker-java/docker-java/releases/tag/docker-java-3.0.0  
 

  
 
 
 
 

 
 
 

 
 
 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] [slack-plugin] (JENKINS-30929) UnsupportedOperationException when "Notify Build Start" notification enabled and TFS SCM is used

2016-03-15 Thread kma...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Madel assigned an issue to Kurt Madel 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30929 
 
 
 
  UnsupportedOperationException when "Notify Build Start" notification enabled and TFS SCM is used  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Madel 
 
 
 

Assignee:
 
 Sam Gleske Kurt Madel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [slack-plugin] (JENKINS-32348) Jenkins not starting on slave

2016-03-15 Thread kma...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Madel commented on  JENKINS-32348 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins not starting on slave  
 
 
 
 
 
 
 
 
 
 
Not clear how this is a slack-plugin issue. Did this specifically start happening after the slack plugin was installed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [slack-plugin] (JENKINS-32348) Jenkins not starting on slave

2016-03-15 Thread kma...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Madel assigned an issue to Kurt Madel 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32348 
 
 
 
  Jenkins not starting on slave  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Madel 
 
 
 

Assignee:
 
 Sam Gleske Kurt Madel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [slack-plugin] (JENKINS-27652) Workflow support for Slack Notifications (Pre and Post build)

2016-03-14 Thread kma...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Madel resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
slack-2.0 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-27652 
 
 
 
  Workflow support for Slack Notifications (Pre and Post build)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Madel 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-organization-folder-plugin] (JENKINS-32155) Recognize new repositories automatically

2016-03-10 Thread kma...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Madel commented on  JENKINS-32155 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Recognize new repositories automatically  
 
 
 
 
 
 
 
 
 
 
This does not appear to work with the 1.0 release of github-organization-folder-plugin (on Jenkins core 1.625.3). 
The Jenkins logs do contain the following, but the org repos are not rescanned:  
Mar 10, 2016 7:56:27 PM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent Received POST for https://github.beescloud.com/sa-team/repo-scan-test 
Here is what was sent from GitHub (enterprise, v 2.5.1): Headers {{Request URL: http://sa-team-beescloud.jenkins-latest.beedemo.net/github-webhook/ Request method: POST content-type: application/x-www-form-urlencoded Expect:  User-Agent: GitHub-Hookshot/35ff2c9 X-GitHub-Delivery: 21537c00-e6fa-11e5-98ed-cdbdb66a9a74 X-GitHub-Event: repository}} 
Payload (partial) {{{ "action": "created", "repository": { "id": 6, "name": "repo-scan-test", "full_name": "sa-team/repo-scan-test", "owner": {}} 
Nothing happens in the GitHub Org folder in Jenkins. 
A manual re-scan will find and add the new repo. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [docker-workflow-plugin] (JENKINS-28821) Docker Workflow demos: sh step on Docker image hangs if workspace is not writable

2015-12-15 Thread kma...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Madel commented on  JENKINS-28821 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Docker Workflow demos: sh step on Docker image hangs if workspace is not writable  
 
 
 
 
 
 
 
 
 
 
Kris Musard I have tried configuring the build node (with the mapped docker socket) to have a jenkins user with the same uid:gid as used by the plugin i(1000:1001) to no avail. What do you mean by: 
In my case I was able to get sh commands working inside the container by adding a user to the docker image with the uid/gid that was bieng specified on the docker run command executed by the plugin (the local jenkins userid and group). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [slack-plugin] (JENKINS-27652) Workflow support for Slack Notifications (Pre and Post build)

2015-12-13 Thread kma...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Madel commented on  JENKINS-27652 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workflow support for Slack Notifications (Pre and Post build)  
 
 
 
 
 
 
 
 
 
 
See https://github.com/jenkinsci/slack-plugin/pull/167 
This just is a very basic Workflow step, when and what gets sent must be configured in workflow. For example 'pre' would require one of the first steps to be 'slackSend' and then for 'Post' the last step to be 'slackSend'. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [hipchat-plugin] (JENKINS-27202) Workflow compatibility for HipChatNotifier

2015-12-11 Thread kma...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Madel commented on  JENKINS-27202 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workflow compatibility for HipChatNotifier  
 
 
 
 
 
 
 
 
 
 
See https://github.com/jenkinsci/hipchat-plugin/pull/60 Note the workaround mentioned at https://github.com/jenkinsci/hipchat-plugin/issues/43 will not work when using the Groovy Sandbox (so that includes loading Workflow scripts from SCM). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.