Re: Bug Triage "Team"

2017-01-20 Thread Ullrich Hafner
I see, the discussion seems to indicate that we have (at least two) different kind of development processes. I’m not sure if I can summarize it properly: We have plugins with one main developer who takes the responsibility for all new issues. Even if the issue is not solved immediately these

[JENKINS-39873] Request to review/merge PR on matrix-auth-plugin

2017-01-20 Thread Wouter Hünd
I have created a pull request [0] to address JENKINS-39873 [1], JENKINS-36788 [2] and possibly JENKINS-4276 [3] This change adds a toggle to the project and folder configurations which will have that project/folder not inherit the permissions of its parent folder. It will still inherit from the

Re: Getting error in AWSEB Deployment Plugin Version 0.3.15

2017-01-20 Thread Aldrin Leal
This means the value of ROOT Object (the path of the artifact to upload) wasn't found. Check your workspace files, and if this doesn't make sense, file an issue on github.com/ingenieux/awseb-deployment-plugin/issues -- -- Aldrin Leal, / http://about.me/aldrinleal On Fri,

Getting error in AWSEB Deployment Plugin Version 0.3.15

2017-01-20 Thread Amrish Jain
Please find below the console log from Jenkins. Any help would be appreciated. Using AWSEB Deployment Plugin Version 0.3.15. I am getting below error when trying to deploy my war file from Jenkins to Elastic beanstalk.

Re: android-signing plugin build failed on jenkins.ci.cloudbees.com

2017-01-20 Thread Slide
Hi Robert, I don't think jenkins.ci.cloudbees.com supports JDK8 yet...but I could be wrong. You may want to talk to rtyler about having it hosting on ci.jenkins.io instead. It will not stop you from releasing a version of the plugin, or from it showing up in the management UI. Regards, Alex On

android-signing plugin build failed on jenkins.ci.cloudbees.com

2017-01-20 Thread Robert St. John
Hello, I noticed that the last (and only) build of the android-signing plugin failed on jenkins.ci.cloudbees.com . The problem appears to be that the job is using JDK 1.7, whereas the plugin

Current Stage name inside the SimpleBuildStep.perform(...) method?

2017-01-20 Thread Adakar
Hi All! I'm refactoring jenkins plugin to make it callable from Pipeline jobs. Do you have any suggestion how to get current Stage name inside the SimpleBuildStep.*perform

Re: Jobs creation on jenkins.ci.cloudbees.com restored

2017-01-20 Thread Arnaud Héritier
yes, but it is a freestyle project thus it should be something like : https://gist.github.com/aheritier/d568ca4a282ffb8759770e4c4e90411b I don't have commit rights on https://github.com/ jenkinsci/backend-jenkins-ci-cloudbees-com-filler

Re: Jobs creation on jenkins.ci.cloudbees.com restored

2017-01-20 Thread Slide
Arnaud, I'm guessing the maven template is the same as https://github.com/jenkinsci/backend-jenkins-ci-cloudbees-com-filler/blob/master/src/main/resources/org/jenkinsci/backend/cifiller/job.xml? If the gradle template content could be made available similarly, that would be nice. I'll open a

Re: Bug Triage "Team"

2017-01-20 Thread Stephen Connolly
On 20 January 2017 at 10:29, Ullrich Hafner wrote: > > Am 20.01.2017 um 08:16 schrieb Stephen Connolly < > stephen.alan.conno...@gmail.com>: > > I also would love if we cleared out the assignee setting entirely. > > > How do we identify who is responsible for the issue

Re: Bug Triage "Team"

2017-01-20 Thread Arnaud Héritier
On Fri, Jan 20, 2017 at 11:29 AM, Ullrich Hafner wrote: > > Am 20.01.2017 um 08:16 schrieb Stephen Connolly < > stephen.alan.conno...@gmail.com>: > > I also would love if we cleared out the assignee setting entirely. > > > How do we identify who is responsible for the

Re: Bug Triage "Team"

2017-01-20 Thread Stephen Connolly
Something like: NEW -> OPEN or TODO or INCOMPLETE INCOMPLETE -> NEW (when the creator added more details) OPEN -> TODO or RESOLVED TODO -> IN PROGRESS (or OPEN or RESOLVED) IN PROGRESS -> TODO or IN REVIEW or RESOLVED RESOLVED -> VERIFY or IN PROGRESS REOPENED -> TODO or RESOLVED VERIFY ->

Re: Bug Triage "Team"

2017-01-20 Thread Stephen Connolly
On 20 January 2017 at 10:29, Ullrich Hafner wrote: > > Am 20.01.2017 um 08:16 schrieb Stephen Connolly < > stephen.alan.conno...@gmail.com>: > > I also would love if we cleared out the assignee setting entirely. > > > How do we identify who is responsible for the issue

Re: Jobs creation on jenkins.ci.cloudbees.com restored

2017-01-20 Thread Arnaud Héritier
It's good. I edited our templates to allow to add a description for jobs and to disable them I manually commented/disabled in https://jenkins.ci. cloudbees.com/job/plugins/ all jobs already available on https://ci.jenkins.io/job/Plugins/ Alex, I had a look to allow you to view our templates but

Re: Bug Triage "Team"

2017-01-20 Thread Ullrich Hafner
> Am 20.01.2017 um 08:16 schrieb Stephen Connolly > : > > I also would love if we cleared out the assignee setting entirely. How do we identify who is responsible for the issue (or who is the owner)? If there is no assignee then nobody gets notified about new

Re: Bug Triage "Team"

2017-01-20 Thread Ullrich Hafner
> Am 20.01.2017 um 01:21 schrieb Mark Waite : > > > > On Thu, Jan 19, 2017 at 1:59 PM Ullrich Hafner > wrote: > I think this is not the common practice. Wouldn’t it be better to use the in > progress