[JIRA] (JENKINS-51097) Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance

2018-05-07 Thread michelene.c...@sony.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon commented on  JENKINS-51097  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
 Looks like this got recatagorized from pipeline to github-plugin, but just to be clear, I want the functionality inside Pipelines. Currently in Pipelines, I also don't have the ability to trigger based on github comment.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51097) Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance

2018-05-02 Thread michelene.c...@sony.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Change By: 
 M Chon  
 

  
 
 
 
 

 
 As a Jenkins user, I would like to be able to set up a Pipeline or Multibranch Pipeline job such that when a Github/(Enterprise) Pull Request is Approved, the job is triggered.A similar capability exists in the Github Pull Request Builder Plugin, where it communicates with the Github API and is able to trigger builds based off of specific text inside a Github comment. Screen shot attached. The screen shot illustrates a job which uses the GHPRB to trigger a build if a comment "Jenkins build this" is made in the PR, or skip the build if "Jenkins skip this" is found in the comment. In my use case, I don't want to scan the comment text, I want to trigger based on the state of the PR (i.e. "Approved " ).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Group

[JIRA] (JENKINS-51097) Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance

2018-05-02 Thread michelene.c...@sony.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Change By: 
 M Chon  
 
 
Attachment: 
 GHPRB Advanced options.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51097) Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance

2018-05-02 Thread michelene.c...@sony.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Change By: 
 M Chon  
 
 
Summary: 
 Ability to trigger Pipelines on Github /  (Enterprise) Pull Request Acceptance  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-51097) Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance

2018-05-02 Thread michelene.c...@sony.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Change By: 
 M Chon  
 

  
 
 
 
 

 
 As a Jenkins user, I would like to be able to set up a Pipeline or Multibranch Pipeline job such that when a Github /  (Enterprise) Pull Request is Approved, the job is triggered.A similar capability exists in the Github Pull Request Builder Plugin, where it communicates with the Github API and is able to trigger builds based off of specific text inside a Github comment. Screen shot attached. The screen shot illustrates a job which uses the GHPRB to trigger a build if a comment "Jenkins build this" is made in the PR, or skip the build if "Jenkins skip this" is found in the comment. In my use case, I don't want to scan the comment text, I want to trigger based on the state of the PR (i.e. "Approved).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Group

[JIRA] (JENKINS-51097) Ability to trigger Pipelines on Github (Enterprise) Pull Request Acceptance

2018-05-02 Thread michelene.c...@sony.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github (Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-05-03 03:18  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 M Chon  
 

  
 
 
 
 

 
 As a Jenkins user, I would like to be able to set up a Pipeline or Multibranch Pipeline job such that when a Github (Enterprise) Pull Request is Approved, the job is triggered. A similar capability exists in the Github Pull Request Builder Plugin, where it communicates with the Github API and is able to trigger builds based off of specific text inside a Github comment. Screen shot attached. The screen shot illustrates a job which uses the GHPRB to trigger a build if a comment "Jenkins build this" is made in the PR, or skip the build if "Jenkins skip this" is found in the comment. In my use case, I don't want to scan the comment text, I want to trigger based on the state of the PR (i.e. "Approved).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

[JIRA] (JENKINS-50342) Provide ability to disable creation of Github Organization jobs

2018-03-22 Thread michelene.c...@sony.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50342  
 
 
  Provide ability to disable creation of Github Organization jobs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-multibranch-plugin  
 
 
Created: 
 2018-03-22 15:17  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 M Chon  
 

  
 
 
 
 

 
 We are slowly rolling out Pipelines (to replace our hundreds of Freestyle jobs). A common mistake of some of our early adopters has been to create a GitHub Organization job, instead of either a Multibranch Pipeline or regular Pipeline. The problem with creating a GO job is that it can potentially (once we achieve a critical mass of Jenkinsfiles checked into our ~1000 repositories in our Github Enterprise organization) of it triggering hundreds of builds. We want to prevent users from being able to do this, by some type of global setting disabling that option (or even better, deinstalling a plugin, but that may not be feasible?)   Also as described here: https://stackoverflow.com/questions/48226276/disable-possibility-to-scan-github-organization-in-jenkins-github-branch-source/49142659#49142659  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

 

[JIRA] (JENKINS-45240) Remove organization folders

2018-03-06 Thread michelene.c...@sony.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon edited a comment on  JENKINS-45240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove organization folders   
 

  
 
 
 
 

 
 I would like to be able to globally disable Github Organization Projects altogether. I do not want end users to be able to create a GO project, but still allow them to create Multibranch Pipeline projects. Should I file a separate bug for this request? E.g. If all 1000+ repos in my  (GHE)  org one day have a Jenkinsfile added to them, I do NOT want a job which starts scanning them and automatically building.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-45240) Remove organization folders

2018-03-06 Thread michelene.c...@sony.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon commented on  JENKINS-45240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove organization folders   
 

  
 
 
 
 

 
 I would like to be able to globally disable Github Organization Projects altogether. I do not want end users to be able to create a GO project, but still allow them to create Multibranch Pipeline projects. Should I file a separate bug for this request? E.g. If all 1000+ repos in my org one day have a Jenkinsfile added to them, I do NOT want a job which starts scanning them and automatically building.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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