[JIRA] (JENKINS-31801) Using Throttle Concurrent Builds in a Pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-31801 Using Throttle Concurrent Builds in a Pipeline Change By: Oleg Nenashev Summary: Using Throttle Concurrent Builds in a WorkFlow Pipeline 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-34294) Throttle Concurrent Builds plugin ignores builds on inheritance-projects.
Title: Message Title Oleg Nenashev commented on JENKINS-34294 Re: Throttle Concurrent Builds plugin ignores builds on inheritance-projects. Inheritance project larchitecture is different from classic job types. It uses a high-level abstraction (hudson.model.Job) instead of hudson.model.AbstractProject, which is being implemented by the most of job types. Many plugins support hudson.model.AbstractProject only. So the plugin just does not support Inheritance project now. It needs some coding to add this support properly (similar to JENKINS-31801) 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-32142) Possibility to add Gradle settings file
Title: Message Title Dominik Bartholdi closed an issue as Duplicate Jenkins / JENKINS-32142 Possibility to add Gradle settings file Change By: Dominik Bartholdi Status: Reopened Closed Resolution: Duplicate 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-32142) Possibility to add Gradle settings file
Title: Message Title Dominik Bartholdi reopened an issue Jenkins / JENKINS-32142 Possibility to add Gradle settings file Change By: Dominik Bartholdi Resolution: Duplicate Status: Resolved Reopened 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-36207) Make BluePipelne extensible
Title: Message Title Vivek Pandey resolved as Fixed Jenkins / JENKINS-36207 Make BluePipelne extensible Change By: Vivek Pandey Status: In Progress 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-30458) [Maven settings] "Replace All" does not work
Title: Message Title Steffen Breitbach commented on JENKINS-30458 Re: [Maven settings] "Replace All" does not work Well, that seems to be what I meant by saying: Either the mechanism is broken or the help text is wrong. So. This particular setting will not replace "even ones not found in the provided list of credentials" but rather remove all server credentials and then replace those stated explicitly. The help text in the corresponding help-isReplaceAll.html should be replaced, maybe to something like: Replace all servers in the Maven settings.xml file. If a server is not in the provided list of credentials, this servers credentials will be empty. Cheers Steffen 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-36208) Queued items are not showing up
Title: Message Title Vivek Pandey edited a comment on JENKINS-36208 Re: Queued items are not showing up [~jamesdumay] Its O \ (n \ ) cost in backend too. No easy way. Besides we can't serve queued items in run till Jenkins core makes projected build id as guaranteed id. For example, if a queued items is served in run, the id element is fake and if someone does GET using this id, it wont work. We can't use queueId because its not indexed and very expensive so should be avoided for frequently accessed APIs like run. 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-36208) Queued items are not showing up
Title: Message Title Vivek Pandey commented on JENKINS-36208 Re: Queued items are not showing up James Dumay Its O cost in backend too. No easy way. Besides we can't serve queued items in run till Jenkins core makes projected build id as guaranteed id. For example, if a queued items is served in run, the id element is fake and if someone does GET using this id, it wont work. We can't use queueId because its not indexed and very expensive so should be avoided for frequently accessed APIs like run. 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-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work well for blue oceans needs.The current API would work OK (not desirable to have two calls rather than one) for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - the requests 2+O\(n)!With thecurrent API rendering the Activity screen for multi-branch: * 1 call to fetch runs {{/runs}}* 1 call to fetch all branches {{/branches/}}* N calls to fetch all the queued items for all branches {{/branch/$branch/queue/}}We need to go back to the drawing board on this...It would be easier if you could always expect that {{/runs}} also returned the queue - regardless of the pipeline type so that the UI can avoid special casing and the problem described above.
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-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work well for blue ocean oceans needs . With this The current API /runs would work OK (not desirable to have two calls rather than one) for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its the requests 2+O\(n)! With the * 1 call to fetch runs {{/runs}} * 1 call to fetch all branches {{/branches/}} * N calls to fetch all the queued items for all branches {{/branch/$branch/queue/}} We need to go back to the drawing board on this. .. It would be easier if you could always expect that {{/runs}} also returned the queue - regardless of the pipeline type so that the UI can avoid special casing and the problem described above .
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-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its 2+O\(n)!* 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this.It would be easier if you could always expect that {{/runs}} also returned the queue - regardless of the pipeline information type .
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-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its 2+O\(n)!* 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this. It would be easier if you could always expect that {{/runs}} also returned the queue - regardless of the pipeline information.
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-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its {{ 2+O(n) }} :* 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this.
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-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its {{ 2+O \ ( n ) }}: ! * 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this.
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-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its {{2+O(n)}}:* 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this.
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-36208) Queued items are not showing up
Title: Message Title James Dumay commented on JENKINS-36208 Re: Queued items are not showing up Vivek Pandey Ivan Meredith it looks like this API could never work for blue ocean. With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue. For multi-branch this is dire - its 2+O: 1 call to fetch runs 1 call to fetch all branches N calls to fetch all the queued items for all branches We need to go back to the drawing board on this. 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-36208) Queued items are not showing up
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-36208
Queued items are not showing up
Change By:
James Dumay
I ran this job on blueocean.io !classic.png|thumbnail! It didn't show up as queued !blue.png|thumbnail! Calling the REST API there is nothing in the runs{code}charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/runs/ | json_pp[]{code}But there seems to be items in the queue{code}charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/queue/ | json_pp [ { "pipeline" : "freestyle", "id" : "545", "_class" : "io.jenkins.blueocean.service.embedded.rest.QueueItemImpl", "queuedTime" : "2016-06-24T04:53:33.867+", "_links" : { "self" : {"href" : "/blue/rest/organizations/jenkins/pipelines/freestyle/queue/545/","_class" : "io.jenkins.blueocean.rest.hal.Link" } }, "expectedBuildNumber" : 1 }]{ code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-36208
Queued items are not showing up
Change By:
James Dumay
I ran this job on blueocean.io !classic.png|thumbnail! It didn't show up as queued !blue.png|thumbnail! Calling the REST API there is nothing in the queue{code}charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/ runs queue / | json_pp [] {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-36208) Queued items are not showing up
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36208 Queued items are not showing up Change By: James Dumay Sprint: 1.0-m10 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-36208) Queued items are not showing up
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36208 Queued items are not showing up Issue Type: Bug Assignee: Vivek Pandey Attachments: blue.png, classic.png Components: blueocean-plugin Created: 2016/Jun/24 5:04 AM Priority: Blocker Reporter: James Dumay I ran this job on blueocean.io It didn't show up as queued Calling the REST API there is nothing in the queue charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/runs/ | json_pp [] Add Comment
[JIRA] (JENKINS-34469) robotframework pipeline-plugin compatibility
Title: Message Title
Mike Nicholson edited a comment on JENKINS-34469
Re: robotframework pipeline-plugin compatibility
+1 The pipeline plugin is critical to our workflow and good CI/CD practices in general. It would be great to see this plugin working within the build pipeline. I've attempted to add it to a Jenkinsfile as a general build step as follows: {code:groovy}step([$class: 'RobotPublisher', outputPath: '.', passThreshold: 0, unstableThreshold: 0]){code}This results in the following stack trace when that step is run:{noformat}java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:305) at org.jenkinsci.plugins.structs.describable.DescribableModel.buildArguments(DescribableModel.java:248) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:192) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15) at WorkflowScript.run(WorkflowScript:27) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79) at sun.reflect.GeneratedMethodAccessor434.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45) at sun.reflect.GeneratedMethodAccessor439.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at
[JIRA] (JENKINS-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Vivek Pandey commented on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints Michael Neale No way. Besides folder changes or any changes that has gone in has nothing to do with it. Its nothing to do with BO API, its more of how a job name is stored by jenkins that is its job.getName() is URL encoded. So the Job name is stored by jenkins as encoded, then while URL of job, generated by jenkins, the job name is url encoded as it knows the original job name is encoded of some form, so in effect the job name gets encoded twice. There is no other way to deal with it. for example if you navigate to a branch in classic UI, you will see the URL doubly encoded, e.g. https://ci.blueocean.io/job/jenkins-design-language/job/feature%252FUX-328/. 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-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Michael Neale edited a comment on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints [~vivek] I am pretty sure this did used to work with single encoding. It would use the same URI as you would see in classic when you browsed to a multibranch pipelines branch, that is how I knew it worked. Requiring double encoding for the api seems new , as we used git flow names since the start, and we were able to see logs of feature branches . This seems to have changed since the folders rework went in, I think. 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-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Michael Neale commented on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints Vivek Pandey I am pretty sure this did used to work with single encoding. It would use the same URI as you would see in classic when you browsed to a multibranch pipelines branch, that is how I knew it worked. Requiring double encoding for the api seems new. 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-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Michael Neale commented on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints Yes, I suspected some clever even double encoding may be required. Jenkins uses URL encoding for branch names as they are stored as a path on disk. Git flow typically has foo/bar style naming of branches, but there are rules about what is allowed: https://wincent.com/wiki/Legal_Git_branch_names however, multibranch is not just git, and who knows what other SCM uses for their branch equivalents. Basically, think of the branch name as not really a path, but some encoded value. It is an unfortunate co-incidence that it uses URL encoding (but it kind of has to). This is also used on disk (which has occasionally causes some problems as a side effect, so that may change). Basically the branch name is what the branch name is, and is likely needed to be encoded one way or another. If it is being encoded with other paths, then it will end up double encoded, yes. I am going cross eyed just thinking about this... 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-34469) robotframework pipeline-plugin compatibility
Title: Message Title Mike Nicholson commented on JENKINS-34469 Re: robotframework pipeline-plugin compatibility +1 The pipeline plugin is critical to our workflow and good CI/CD practices in general. It would be great to see this plugin working within the build pipeline. I've attempted to add it to a Jenkinsfile as a general build step as follows: Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml step([$class: 'RobotPublisher', outputPath: '.', passThreshold: 0, unstableThreshold: 0]) This results in the following stack trace when that step is run: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:305) at org.jenkinsci.plugins.structs.describable.DescribableModel.buildArguments(DescribableModel.java:248) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:192) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15) at WorkflowScript.run(WorkflowScript:27) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79) at sun.reflect.GeneratedMethodAccessor434.invoke(Unknown Source) at
[JIRA] (JENKINS-36207) Make BluePipelne extensible
Title: Message Title Vivek Pandey started work on JENKINS-36207 Change By: Vivek Pandey Status: Open In Progress 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-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated That has been a relatively common problem with that wiki page. The solution I've been told to use is to add a parameter to the end of the URL. I used https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin?foo=bar to read the correct page. The git client plugin 2.0.0-beta1 has been released to the experimental update center. It includes git submodule authentication, JGit 4.3, and requires JDK 7. It requires at least Jenkins 1.625 (the first version to mandate JDK 7). The process of preparing that release (with JGit 4.3) exposed an incompatibility which I haven't yet decided how to resolve. The incompatibility is described in a posting to the Jenkins developers mailing list. I need some more time to choose the best compromise. I really want JDK 7 because it makes the git client plugin cleaner and less susceptible to file leaks. I also want JGit 4, because JGit 4 is receiving active development, while JGit 3 is not. 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-36207) Make BluePipelne extensible
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-36207 Make BluePipelne extensible Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Jun/24 3:34 AM Priority: Major Reporter: Vivek Pandey At present BluePipeline implementations are hardcoded to be picked up based on inspecting Item type. What we want is for anyone to provide their implementation of BluePipeline and it gets plugged in. For example if a plugin defined their own implementation of AbstractProject and they provide their implementation of BluePipeline, their implementation of BluePipeline should be able to expose their project specific JSON response in addition whats required by BluePipeline contract. Add Comment
[JIRA] (JENKINS-36206) Add staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop java.lang.CharSequence int to generic-whiteliest
Title: Message Title
Owen Wood created an issue
Jenkins / JENKINS-36206
Add staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop java.lang.CharSequence int to generic-whiteliest
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
script-security-plugin
Created:
2016/Jun/24 3:28 AM
Priority:
Minor
Reporter:
Owen Wood
Pending review of course. Not sure what security implications there might be here. To reproduce:
node {
env.WORKSPACE = pwd()
test = env.WORKSPACE.drop(3)
}
Results in:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop java.lang.CharSequence int
at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectStaticMethod(StaticWhitelist.java:174)
Reproducible with Sandbox enabled (or using Jenkinsfile obviously)
[JIRA] (JENKINS-27668) Add support for multiple git repositories in a single workspace
Title: Message Title Mark Waite commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace Adding multiple independent repository support to the existing git plugin looks extremely difficult to me. You might investigate using a Jenkinsfile in the root directory of your starting repository. I believe that Jenkinsfile can then be used to define the set of repositories you would like to checkout. There is a stackoverflow article which provides an example. 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-35657) Support Multibranch Workflow from 2 different github repos
Title: Message Title Bryden Oliver commented on JENKINS-35657 Re: Support Multibranch Workflow from 2 different github repos The duplicate issue covers far more and seems to involve a far more complicated solution. Although the solution proposed here could probably cover the case mentioned in the other issue, or at least a significant subset of them. 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-35818) Developer sees a interstitial when tab data is being displayed
Title: Message Title James Dumay stopped work on JENKINS-35818 Change By: James Dumay Status: In Progress Open 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-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title James Dumay stopped work on JENKINS-35776 Change By: James Dumay Status: In Progress Open 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-35827) Developer sees a interstitial when pipeline result data is being loaded
Title: Message Title James Dumay stopped work on JENKINS-35827 Change By: James Dumay Status: In Progress Open 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-36169) Log does not match final style
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36169 Log does not match final style Change By: James Dumay Sprint: 1.0- m11 m10 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-36135) cannot get CHANGES BUILD_LOG BUILD_STATUS variables' value
Title: Message Title Xiangyan Li updated an issue Jenkins / JENKINS-36135 cannot get CHANGES BUILD_LOG BUILD_STATUS variables' value Change By: Xiangyan Li Component/s: email-ext-plugin Component/s: repo-plugin 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-36195) Pipeline polling ignores special polling rules
Title: Message Title Mark Waite commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules Since the git plugin doesn't read the contents of Jenkinsfile when performing polling, I'm not sure how it would honor the polling settings inside the Jenkinsfile in the repository. It seems like it would be even more challenging in a repository with more than one branch, since the polling settings might differ between branches within the same repository. I wonder if Jesse Glick has any ideas how to handle this case and JENKINS-35988 (and others like it). 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-36195) Pipeline polling ignores special polling rules
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-36195 Pipeline polling ignores special polling rules Change By: Mark Waite Assignee: Mark Waite 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-36167) Don't wait for busy nodes
Title: Message Title Ella Z updated an issue Jenkins / JENKINS-36167 Don't wait for busy nodes Change By: Ella Z Triggering a job with the Node parameter (with the Node eligibility is set to All Nodes )on Node1 and Node2If Node1 is busy, Node2 won't start unless the job will start on Node1 I want Node2 to start the job, and the job for Node1 to stay in the queue until Node1 is free 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-32481) git plugin does not retry when submodule update fails
Title: Message Title Scott Johnson commented on JENKINS-32481 Re: git plugin does not retry when submodule update fails This seems to still be broken in git-plugin 2.5.0 (the latest release). The pull request linked in the previous comment is still open. This bug, combined with github flakiness today, is killing all my builds. 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-36205) is it possible to set umask 002 so files after build got that permissions ?
Title: Message Title luis ramirez assigned an issue to Oleg Nenashev Jenkins / JENKINS-36205 is it possible to set umask 002 so files after build got that permissions ? Change By: luis ramirez Assignee: luis ramirez Oleg Nenashev 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-36175) Developer should be able to run a non-mutibranch pipeline job
Title: Message Title James Dumay assigned an issue to Tom FENNELLY Jenkins / JENKINS-36175 Developer should be able to run a non-mutibranch pipeline job Change By: James Dumay Assignee: James Dumay Tom FENNELLY 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-36175) Developer should be able to run a non-mutibranch pipeline job
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36175 Developer should be able to run a non-mutibranch pipeline job Change By: James Dumay Sprint: 1.0- m11 m10 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-36205) is it possible to set umask 002 so files after build got that permissions ?
Title: Message Title luis ramirez created an issue Jenkins / JENKINS-36205 is it possible to set umask 002 so files after build got that permissions ? Issue Type: Bug Assignee: luis ramirez Components: _unsorted Created: 2016/Jun/23 10:13 PM Priority: Minor Reporter: luis ramirez in every build using jenkins, group is not able to write on the files, I have been trying to set the umask to 002 with no luck. any advice please ? Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-36204) Role-Based: Users are not able to see new project on their views
Title: Message Title eric tang commented on JENKINS-36204 Re: Role-Based: Users are not able to see new project on their views Seems the user needed to enable auto refresh on his profile. He is now able to see the new project. 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-36201) Build Keeper not locking the downstream Job
Title: Message Title Vairavan Sockalingam closed an issue as Fixed Silly me..Just pass the ENV variable.. Jenkins / JENKINS-36201 Build Keeper not locking the downstream Job Change By: Vairavan Sockalingam Status: Open Closed 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
[JIRA] (JENKINS-35208) Unable to deploy the ear file using weblogic-deployer-plugin
Title: Message Title Raphael CHAUMIER closed an issue as Cannot Reproduce Jenkins / JENKINS-35208 Unable to deploy the ear file using weblogic-deployer-plugin Change By: Raphael CHAUMIER Status: Open Closed Resolution: Cannot Reproduce 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-36204) Role-Based: Users are not able to see new project on their views
Title: Message Title eric tang created an issue Jenkins / JENKINS-36204 Role-Based: Users are not able to see new project on their views Issue Type: Bug Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2016/Jun/23 9:53 PM Environment: Non Prod Priority: Minor Reporter: eric tang I created a view and added an existing project. The user is able to see the project fine. However, when I created a new project and updated his view to include the project, he is not able to see the new project. I'm using role based security. As an admin, I can see the job in the view. When I give admin rights to the user, he can also see the project in his view. Has anyone seen this before? Add Comment
[JIRA] (JENKINS-14042) Add timeout on tasks
Title: Message Title Raphael CHAUMIER closed an issue as Won't Do Using adavanced configuration to set a timeout parameter Jenkins / JENKINS-14042 Add timeout on tasks Change By: Raphael CHAUMIER Status: Open Closed Resolution: Won't 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-36128) Duration never live reloads for running pipelines
Title: Message Title James Dumay commented on JENKINS-36128 Re: Duration never live reloads for running pipelines @cliffmeyers yes please - any other place you know of would be great 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-36203) requestBody field is not available for Pipeline Step
Title: Message Title Isaac Cohen commented on JENKINS-36203 Re: requestBody field is not available for Pipeline Step https://github.com/jenkinsci/http-request-plugin/pull/15 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-34376) Cannot easily/safely catch exceptions without disrupting job abortion
Title: Message Title Clay Gerrard commented on JENKINS-34376 Re: Cannot easily/safely catch exceptions without disrupting job abortion Can we get the JIRA component tags inline with the project name? https://wiki.jenkins-ci.org/display/JENKINS/workflow+plugin 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-33090) Ease bundles management by the administrator
Title: Message Title Arnaud Héritier commented on JENKINS-33090 Re: Ease bundles management by the administrator Jesse Glick sub-tasks aren't activated on this instance. That's why I used Epic + Tasks.. 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-36128) Duration never live reloads for running pipelines
Title: Message Title Cliff Meyers commented on JENKINS-36128 Re: Duration never live reloads for running pipelines James Dumay I have fixes in place for the Activity grid and the Pipeline Result header. Should I add it for the "Completed" column in the Branches and Pull Requests tab as well? And Run Detail -> Changes -> Date column? I believe those are all the places in the app. 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-36203) requestBody field is not available for Pipeline Step
Title: Message Title Isaac Cohen created an issue Jenkins / JENKINS-36203 requestBody field is not available for Pipeline Step Issue Type: Bug Assignee: Janario Oliveira Components: http-request-plugin Created: 2016/Jun/23 8:45 PM Priority: Major Reporter: Isaac Cohen The new requestBody field is not available as an option for the Pipeline Step. It is also not visible in the Snippet Generator. This is important for POST requests requiring the body. Add Comment This message was sent by
[JIRA] (JENKINS-34216) Failed to reset the request input stream
Title: Message Title Joshua Spence commented on JENKINS-34216 Re: Failed to reset the request input stream Strangely, version 0.10.5 works fine for us on Jenkins 2.9. 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-34216) Failed to reset the request input stream
Title: Message Title Joshua Spence commented on JENKINS-34216 Re: Failed to reset the request input stream Ah sorry about that. I'm not a Java developer and I think that this was my first PR for a Java project too. 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-36152) Reference the upstream job by using CauseAction
Title: Message Title Oleg Nenashev commented on JENKINS-36152 Re: Reference the upstream job by using CauseAction Yep, good subject for discussion. Ideally the plugin could have a WorkspaceSelector extension point with different implementations. Unique IDs would be neat for Fingerprinting feature BTW. 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-36152) Reference the upstream job by using CauseAction
Title: Message Title Jesse Glick commented on JENKINS-36152 Re: Reference the upstream job by using CauseAction As noted elsewhere, I do not really recommend relying on UpstreamCause, which was mainly intended as informational (for human display), not an authoritative source. Better IMO for the upstream build to name a particular workspace somehow, and pass this information as a parameter to the downstream build. Explicit, debuggable, safe for concurrent use. 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-32631) ability to configure throttling of matrix parents and children
Title: Message Title Daniel Spilker resolved as Fixed Will be fixed in 1.48. Jenkins / JENKINS-32631 ability to configure throttling of matrix parents and children Change By: Daniel Spilker 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-36202) Listing tfs workspaces fails with 4.1.0
Title: Message Title Oleg N commented on JENKINS-36202 Re: Listing tfs workspaces fails with 4.1.0 Is there a way to see the exact command being called in the console log in the new 4.1.0 plugin, like it was possible in the 3.2 plugin? 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-33685) filter stacktrace in all cases
Title: Message Title Ivan Fernandez Calvo closed an issue as Won't Do Jenkins / JENKINS-33685 filter stacktrace in all cases Change By: Ivan Fernandez Calvo Status: In Progress Closed Resolution: Won't 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-33090) Ease bundles management by the administrator
Title: Message Title Jesse Glick commented on JENKINS-33090 Re: Ease bundles management by the administrator A Story plus Tasks would be more appropriate for this sort of thing. 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-33090) Ease bundles management by the administrator
Title: Message Title Jesse Glick started work on JENKINS-33090 Change By: Jesse Glick Status: Open In Progress 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-33090) Ease bundles management by the administrator
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-33090 Ease bundles management by the administrator Change By: Arnaud Héritier Summary: Ease the management bundles management by the administrator 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-26989) Inject env variables via stored script
Title: Message Title
Alexander Komarov edited a comment on JENKINS-26989
Re: Inject env variables via stored script
Agreed that it would be nice. In the meantime, I've worked around this by retrieving scripts via http from jenkins userContent, one (Scripts in that directory get auto - updated from scm via puppet).All scripts return a closure.One- liner for brevity: {code:java}evaluate("${jenkins.model.Jenkins.getInstance().getRootUrl()}/userContent/my-script-name.groovy".toURL().text)(){code}Script example:{code:java}return { ['something': 'someValue']}{code} (Scripts in that directory get auto-updated from scm via puppet). Scripts return a closure. Same with parameter passed to the shared script:{code:java}evaluate("${jenkins.model.Jenkins.getInstance().getRootUrl()}/userContent/my-script-name.groovy".toURL().text)('some-parameter-value'){code}Script example:{code:java}return { myParam -> [ 'something': myParam]}{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-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory
Title: Message Title Terry Ewing commented on JENKINS-32479 Re: multiple git repositories sometimes fail to checkout some of them into subdirectory I think this issue is the same as https://issues.jenkins-ci.org/browse/JENKINS-27668. 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-26989) Inject env variables via stored script
Title: Message Title
Alexander Komarov commented on JENKINS-26989
Re: Inject env variables via stored script
Agreed that it would be nice. In the meantime, I've worked around this by retrieving scripts via http from jenkins userContent, one-liner for brevity:
evaluate("${jenkins.model.Jenkins.getInstance().getRootUrl()}/userContent/my-script-name.groovy".toURL().text)()
Script example:
return {
['something': 'someValue']
}
(Scripts in that directory get auto-updated from scm via puppet). Scripts return a closure. Same with parameter passed to the shared script:
evaluate("${jenkins.model.Jenkins.getInstance().getRootUrl()}/userContent/my-script-name.groovy".toURL().text)('some-parameter-value')
Script example:
return { myParam ->
[ 'something': myParam]
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title
davidkarlsen edited a comment on JENKINS-34517
Re: Pipeline is unable to locate global libraries when build attempts to continue on restart
Even worse - the whole job can go into an illegal state. The job broke on startup with this issue 1), but the next is waiting for the previous one to complete1){noformat}18:57:11 Waiting for builds [717]Resuming build[Pipeline] End of Pipeline[Bitbucket] Notifying commit build result[Bitbucket] Build result notifiedjava.io.IOException: Failed to load pe{noformat}2){noformat}19:31:54 Waiting for builds [718]{noformat} so now we're totally stuck Update: I see this registered as https://issues.jenkins-ci.org/browse/JENKINS-28183
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-27668) Add support for multiple git repositories in a single workspace
Title: Message Title Terry Ewing commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace Found this thread after experiencing the same issue. My job is configured with two git repos. When the job runs it appears to check out both repos but the workspace only shows contents from the first. I believe this is a bug because the configuration in the UI isn't being produced in the workspace. I'm sure I can work around the issue and am hoping maintainers can find a solution soon. 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-29390) Parameterization for Docker Container configuration.
Title: Message Title Antonio Beyah commented on JENKINS-29390 Re: Parameterization for Docker Container configuration. Can we also make a similar consideration for volumes? I would like the volumes mounted for workspace and target paths to be configurable. The current (default) is great for most cases but there are areas where it falls apart, namely places where the same directories are used by the job running inside the container and are also mounted. For example, JENKINS_HOME is mounted inside the container, but I have an RPM that is building/installing a RPM that is creating those directories (the jenkins rpm), so in this case I would like the JENKINS_HOME to not match the paths in the rpm. In a sense, in some instances I want the file system to be completely isolated from the host machine. I'm thinking it would be nice if under 'volumes' the default was to have the ones that are currently hardcoded, but to allow the volumes to be completely configurable. I'm curious to your thoughts on that, if you are open to it I may be able to throw a PR together that adds that support. If you want I can open a separate issue to discuss configurable volumes, just let me know. 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-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title davidkarlsen commented on JENKINS-34517 Re: Pipeline is unable to locate global libraries when build attempts to continue on restart Even worse - the whole job can go into an illegal state. The job broke on startup with this issue 1), but the next is waiting for the previous one to complete 1) 18:57:11 Waiting for builds [717] Resuming build [Pipeline] End of Pipeline [Bitbucket] Notifying commit build result [Bitbucket] Build result notified java.io.IOException: Failed to load pe 2) 19:31:54 Waiting for builds [718] so now we're totally stuck 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-35911) CTest returning non-zero error code should not stop the build
Title: Message Title Martin Weber commented on JENKINS-35911 Re: CTest returning non-zero error code should not stop the build You will find a new text box labeled Ignore exit codes in the CMake/CPack/CTest build step now, which should satisfy your needs. 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-36202) Listing tfs workspaces fails with 4.1.0
Title: Message Title Oleg N created an issue Jenkins / JENKINS-36202 Listing tfs workspaces fails with 4.1.0 Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2016/Jun/23 5:30 PM Environment: Windows Server 2012, Jenkins 2.10, tfs-plugin 4.1.0, TFS Server 2015 update 2 Labels: plugin tfs-plugin tfs Priority: Minor Reporter: Oleg N I have full Visual Studio 2015 installed, to get its tf command, I had issues with TFS-CLC-14.0.3. When I try to connect to TFS in Jenkins with the 4.1.0 plug in, it fails like this: Listing workspaces from https://tfspro.x.net/tfs/TFS01... FATAL: com.microsoft.tfs.core.exceptions.TECoreException: TF14045: The identity b36238e8-6ac5-4f4a-bf3f-20005d3ed049 is not a recognized identity. java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TECoreException: TF14045: The identity b36238e8-6ac5-4f4a-bf3f-20005d3ed049 is not a recognized identity. When I go back to the 3.2 version of the plug in, it is ok. [workspace] $ "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\tf" history $/AMERICAS_/Branches/xxx-Test/Source/xxxPortals/InternalPortal -recursive -stopafter:1 -noprompt -version:D2016-06-23T17:06:21Z -format:brief -server:https://tfspro.xxx.net/tfs/TFS01 Changeset User Date Comment - - -- 1240594 xxx, Oleg 4/19/2016 Branched from $/AMERICAS_xxx [workspace] $ "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\tf" workspaces -format:brief -server:https://tfspro.xxx.net/tfs/TFS01 I have a custom
[JIRA] (JENKINS-36027) Build is failing
Title: Message Title Randy zolo assigned an issue to Stephen Morrison Jenkins / JENKINS-36027 Build is failing Change By: Randy zolo Assignee: Dror Banin Stephen Morrison 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-34476) Allow the workflowLibs.git to be hosted someplace else
Title: Message Title Michael Scharp commented on JENKINS-34476 Re: Allow the workflowLibs.git to be hosted someplace else Here is how I manage to get this functionality, though we are using Stash instead of GitHub: Create workflow-libs repo in SCM Navigate to JENKINS_HOME/workflow-libs directory on jenkins server Do git clone YOUR_REPO_URL The key here is to make sure the repo is cloned right into the directory, not into a sub directory. Create a freestyle jenkins job and point it to your workflow-libs repo Add "Execute Shell" step to navigate to the JENKINS_HOME/workflow-libs directory and execute a git pull e.g cd ../../workflow-libs git pull If your GitHub repo uses web-hooks, configure it to notify jenkins when the repo has been committed to Configure the jenkins job to build when notified of a commit to the repo Some of these steps may be a little different for GitHub as I am not familiar with the web-hook functionality there. I assume something similar could be achieved by a polling schedule from within the jenkins job. This has worked well for us, especially in making UPDATES to global scripts. The one issue we have is that when committing a NEW script to the repo. After the push to the repo and the jenkins job has run to update the workflow-libs repo on the jenkins server, the new global script won't be available until after a jenkins restart. Before a restart you'll get a "Global Script Not Found" or similar error. Hope this helps
[JIRA] (JENKINS-36200) Add count-driven by execution-time parallelism
Title: Message Title Andrew Bayer resolved as Not A Defect Actually, looks like it already works this way and I just misunderstood. whoops. Jenkins / JENKINS-36200 Add count-driven by execution-time parallelism Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect 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,
[JIRA] (JENKINS-35813) Developer can run a new build from the Branch tab and Pull request tab
Title: Message Title Tom FENNELLY resolved as Fixed Jenkins / JENKINS-35813 Developer can run a new build from the Branch tab and Pull request tab Change By: Tom FENNELLY 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-36200) Add count-driven by execution-time parallelism
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-36200 Add count-driven by execution-time parallelism Issue Type: New Feature Assignee: Andrew Bayer Components: parallel-test-executor-plugin Created: 2016/Jun/23 4:43 PM Priority: Minor Reporter: Andrew Bayer I'd like to be able to say "Give me X buckets of tests where the total execution time of each of those buckets is close to equal". So...gonna try to implement that! Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-36201) Build Keeper not locking the downstream Job
Title: Message Title Vairavan Sockalingam created an issue Jenkins / JENKINS-36201 Build Keeper not locking the downstream Job Issue Type: New Feature Assignee: bap Components: build-keeper-plugin Created: 2016/Jun/23 4:43 PM Labels: plugins build keep-this-build-forever Priority: Minor Reporter: Vairavan Sockalingam Is there any option to make the Build Keeper to save all the downstream jobs? I have a multiproject where I can use Build Keeper to keep the builds but I also want the linked down stream jobs to kept as well. The only option I can see is I have pass a variable to downstream jobs then save it... Not sure this is already sloved or solution to this problem exists Add Comment
[JIRA] (JENKINS-34519) A pipeline running build will stuck until jenkins restart if the job is removed
Title: Message Title Michael Scharp commented on JENKINS-34519 Re: A pipeline running build will stuck until jenkins restart if the job is removed Steps to reproduce ( for Multibranch Pipeline ) Provided that you have a MB pipeline job setup in jenkins: Create branch in repo Push branch to origin Verify build of new branch starts Delete branch from origin (this can happen because of manual deletion, or merge of a pull request ) Verify build of branch continues Click into build and verify 404 (or similar) error Executor is now unable to be killed and only recoverable after jenkins restart. 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-27552) If deleting older verions, provide option for sorting
Title: Message Title Patrick Kuijpers edited a comment on JENKINS-27552 Re: If deleting older verions, provide option for sorting I'd really love to see the issue to be resolved.It's a pain in the ass quite annoying if you build a new version to Hockeyapp, and it is directly deleted because it's an older "version". Why bother building an old version to hockey if it is deleted anyway?Sorting by date would also be my suggestion (feels more correct) , but of course having the option to choose which sorting is applied would be best!ps.My team's workaround for this issue:Delete 1 version on Hockeyapp, so your new build will be placed last in the version history.However, due to continues delivery we've got about 15 apps updated each 30 minutes (max 10 versions are saved). Manually deleting each of these, with the risk of having your new build being pushed away directly after an automatic build is pretty annoying.. 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-36087) Set stage result manually
Title: Message Title Sam Van Oort commented on JENKINS-36087 Re: Set stage result manually Let's look at the desired result from a broader context: I what you're looking for here is really the ability to programmatically add additional information about stage execution (besides pass/fail) and display it in the UI. Does that sound about right? The combination of https://issues.jenkins-ci.org/browse/JENKINS-26522 (annotated block status) and JENKINS-26107 (block-scoped stages, implemented in https://github.com/jenkinsci/pipeline-stage-step-plugin/pull/4) will give this result if a UI layer can be added on top of this (though it would require more complex analysis to generate this). I am imagine syntax like: https://issues.jenkins-ci.org/browse/JENKINS-26522?focusedCommentId=253869=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-253869 Then add some basic rules to allow custom coloring of stages based on whether some annotation is present (attached to either start or end node, stage view analyses by then will be smart enough to do what needs to be done). That approach fits with the execution model for pipelines - you can build up state as you go by attaching Actions to the nodes (which get carried to the overall block). Tagging Jesse Glick to see if he agrees or has a better notion here. 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
[JIRA] (JENKINS-26138) Better support for workspaces
Title: Message Title
Jesse Glick edited a comment on JENKINS-26138
Re: Better support for workspaces
Another thing to do: - show the {{@tmp}} variant of the workspace if it exists - (no, could be a security risk) .
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-26138) Better support for workspaces
Title: Message Title Jesse Glick commented on JENKINS-26138 Re: Better support for workspaces Another thing to do: show the @tmp variant of the workspace if it exists. 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-36199) "Toaster" for managing Toast instances
Title: Message Title Tom FENNELLY commented on JENKINS-36199 Re: "Toaster" for managing Toast instances Also see comments on https://github.com/jenkinsci/blueocean-plugin/pull/280 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-36199) "Toaster" for managing Toast instances
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-36199 "Toaster" for managing Toast instances Issue Type: Story Assignee: James Dumay Components: blueocean-plugin Created: 2016/Jun/23 4:17 PM Priority: Major Reporter: Tom FENNELLY Atm, the Toast component is standalone and has some little issues that could be resolved by having a separate/parent component that manages instance of Toast: Rendering with other components is a bit weird and results in the rendered Toast needing to be fixed positioned in order to stop it appearing in the middle of the page somewhere. It is currently unmounting itself, causing some react errors in the console. The Toaster would provide a fixed "docking" location for the Toast instances, removing the need for the user of the Toast to have to do weird CSS positioning etc. The Toaster would also handle the unmounting and hopefully fix the current react errors. The Toast message details could be sent to the Toaster via redux etc. Add Comment
[JIRA] (JENKINS-36056) When the estimated duration cannot be determined the wrong indicator is shown
Title: Message Title Cliff Meyers resolved as Fixed Jenkins / JENKINS-36056 When the estimated duration cannot be determined the wrong indicator is shown Change By: Cliff Meyers Status: In Progress 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-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Ryan Small updated an issue Jenkins / JENKINS-36197 java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Change By: Ryan Small Summary: java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2 - plugin from 1.33 to 1.34 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-36198) Toast component should define styles for wrapping and font color
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36198 Toast component should define styles for wrapping and font color Change By: Tom FENNELLY Sprint: 1.0-m10 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-36170) API to determine if a step has logs or not
Title: Message Title Vivek Pandey commented on JENKINS-36170 Re: API to determine if a step has logs or not Michael Neale There are different ways we can do it. I will get back with a proposal. 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-27552) If deleting older verions, provide option for sorting
Title: Message Title Patrick Kuijpers edited a comment on JENKINS-27552 Re: If deleting older verions, provide option for sorting I'd really love to see issue to be resolved.It's a pain in the ass if you build a new version to Hockeyapp, and it is directly deleted because it's an older "version".Why bother building an old version to hockey if it is deleted anyway?Sorting by date would also be my suggestion, but of course having the option to choose which sorting is applied would be best!ps. Our My team's workaround for this issue:Delete 1 version on Hockeyapp, so your new build will be placed last in the version history.However, due to continues delivery we've got about 15 apps updated each 30 minutes (max 10 versions are saved). Manually deleting each of these, with the risk of having your new build being pushed away directly after an automatic build is pretty annoying.. 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-36198) Toast component should define styles for wrapping and font color
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-36198 Toast component should define styles for wrapping and font color Issue Type: Bug Assignee: James Dumay Components: blueocean-plugin Created: 2016/Jun/23 4:08 PM Priority: Minor Reporter: Tom FENNELLY See how we had to redefine them in https://github.com/jenkinsci/blueocean-plugin/pull/280 in run-pipeline.less. Remove styles from run-pipeline.less once this is done. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2 plugin 1.33 to 1.34
Title: Message Title
Ryan Small updated an issue
Jenkins / JENKINS-36197
java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2 plugin 1.33 to 1.34
Change By:
Ryan Small
After updating from to ec2-plugin 1.34 from 1.33, I now get the following error when testing connection : . Downgrading back to 1.33 resolves the issue. {code:java}javax.servlet.ServletException: java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:44) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:106) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-27552) If deleting older verions, provide option for sorting
Title: Message Title Patrick Kuijpers edited a comment on JENKINS-27552 Re: If deleting older verions, provide option for sorting I'd really love to see issue to be resolved.It's a pain in the ass if you build a new version to Hockeyapp, and it is directly deleted because it's an older "version".Why bother building an old version to hockey if it is deleted anyway?Sorting by date would also be my suggestion, but of course having the option to choose which sorting is applied would be best! ps.Our workaround for this issue:Delete 1 version on Hockeyapp, so your new build will be placed last in the version history.However, due to continues delivery we've got about 15 apps updated each 30 minutes (max 10 versions are saved). Manually deleting each of these, with the risk of having your new build being pushed away directly after an automatic build is pretty annoying.. 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-34216) Failed to reset the request input stream
Title: Message Title Kevin Chen commented on JENKINS-34216 Re: Failed to reset the request input stream Installed it and ran a build. No errors and verified our S3 artifact got deployed. I hope the snapshot version above doesn't hinder us. 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-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2 plugin 1.33 to 1.34
Title: Message Title Ryan Small created an issue Jenkins / JENKINS-36197 java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2 plugin 1.33 to 1.34 Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Jun/23 4:03 PM Environment: centos 7, AWS using ec2 IAM profile for credentials Labels: plugin Priority: Minor Reporter: Ryan Small After updating from to ec2-plugin 1.34 from 1.33, I now get the following error when testing connection: javax.servlet.ServletException: java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at
[JIRA] (JENKINS-36196) Organization folder and multi-branch projects should support folder-level credentials
Title: Message Title Spike Washburn created an issue Jenkins / JENKINS-36196 Organization folder and multi-branch projects should support folder-level credentials Issue Type: Improvement Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin, github-branch-source-plugin Created: 2016/Jun/23 4:03 PM Priority: Minor Reporter: Spike Washburn As a pipeline administrator, I should be able to attach credentials for scanning my repositories directly to the Multi-branch or Organization Folder. Currently, I can only use globally-defined credentials for my repositories. Root issue: Folder-derived pipeline projects are not compatible with Folder-level credentials. Steps to reproduce : Create a GitHubOrganizationFolder (or another multi-branch) pipeline project Add a user/pass credential to the newly created folder-derived job type (not at the global Jenkins level) Attempt to select the newly added credential in the pulldown Expected results: global and folder-level credentials are shown in the drop-down and the new credential is selectable. Actual results: folder-level credentials are not displayed in the pulldown and are not selectable. Note: This improvement should be made to all multi-branch project types (GitHubOrgFolder, BitBucketOrgFolder, Multi-branch jobs, etc).
[JIRA] (JENKINS-27552) If deleting older verions, provide option for sorting
Title: Message Title Patrick Kuijpers commented on JENKINS-27552 Re: If deleting older verions, provide option for sorting I'd really love to see issue to be resolved. It's a pain in the ass if you build a new version to Hockeyapp, and it is directly deleted because it's an older "version". Why bother building an old version to hockey if it is deleted anyway? Sorting by date would also be my suggestion, but of course having the option to choose which sorting is applied would be best! 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.
