Re: Jenkinsfile building from PR

I believe we are experiencing the same issue that others are in this PR and are just waiting for it to merge: https://github.com/jenkinsci/github-branch-source-plugin/pull/134 On Friday, June 9, 2017 at 4:13:48 PM UTC-4, David Brooks wrote: > > Hey all, > > We currently h

Re: Jenkinsfile building from PR

Doing GET /repos/:owner/:repo/collaborators/:username/permission on the user account the api token was generated from reveals "permission": "admin" which would signify push access :/ On Monday, June 12, 2017 at 10:26:58 AM UTC-4, Jesse Glick wrote: > > On Mon, Jun 12, 2017 at 10:10 AM, Stephen C

Re: Jenkinsfile building from PR

Hi Stephen, Our API token currently has repo, read:org, admin:repo_hook, user:email. What else are we missing? I don't see an explicit option for repo:admin On Monday, June 12, 2017 at 8:32:16 AM UTC-4, Stephen Connolly wrote: > > > On Mon 12 Jun 2017 at 13:15, David Brooks &g

Re: Jenkinsfile building from PR

So the only way for Jenkins to use a Jenkinsfile to build/test a PR is by having that Jenkinsfile already merged into master? How do you test updates to your Jenkinsfile? On Saturday, June 10, 2017 at 8:18:58 AM UTC-4, Stephen Connolly wrote: > > > On Fri 9 Jun 2017 at 21:13, Dav

Jenkinsfile building from PR

Hey all, We currently have a GitHub Organization Folder that is told to build projects that have a Jenkinsfile in their root. However, when I create a branch with a brand new Jenkinsfile on a repo that never had a Jenkinsfile before, the PR is not being built using the Jenkinsfile in the PR. I

Install Private Plugin

I have a private Jenkins plugin, in that it lives within a private GitHub repo under my company's organization. I was wondering what the best way to install it onto our Jenkins would be that would allow for updates made to the plugin being recognized by Jenkins. I did come across juseppe

Re: Plugin Pipeline Environment Variables

; > I had exactly the same problem(it seems to me). > Try to follow this discussion > <https://groups.google.com/forum/#!msg/jenkinsci-dev/gZQjSaVtluU/ixAA9Bt8BAAJ>, > > it can be useful. > > On Monday, March 27, 2017 at 4:47:10 PM UTC+3, David Brooks wrote: >> &

Re: Plugin Pipeline Environment Variables

working under both project types just using Step? On Monday, March 27, 2017 at 9:50:59 AM UTC-4, Daniel Beck wrote: > > > > On 27.03.2017, at 15:47, David Brooks > > wrote: > > > > However, I do not see any documentation around Step and BuildStep has > been depre

Re: Plugin Pipeline Environment Variables

Thanks Daniel, I will take a crack at it! On Monday, March 27, 2017 at 9:50:59 AM UTC-4, Daniel Beck wrote: > > > > On 27.03.2017, at 15:47, David Brooks > > wrote: > > > > However, I do not see any documentation around Step and BuildStep has > been deprecat

Plugin Pipeline Environment Variables

Hey all, I have been working on an internal plugin for our company and currently having it working for Freestyle projects. However, I would like to update it to support Pipelines and have a question about Environment Variables. I implemented SimpleBuildStep, but according to a fellow dev (here