[JIRA] (JENKINS-58939) Allow skipping pull requests by labels
Title: Message Title Steven Foster commented on JENKINS-58939 Re: Allow skipping pull requests by labels I wrote a plugin to do this for myself a long time ago, never got to publishing it because I couldn't hook up an event subscriber thing for github pull request label events. My use case was for opting-in pull requets based on label but I think I wrote the excluding case as well. I can throw what I have on github tomorrow. https://issues.jenkins-ci.org/browse/JENKINS-50323 somewhat related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201283.1565801632000.3112.1565823720156%40Atlassian.JIRA.
[JIRA] (JENKINS-43194) Lightweight checkout for PR merge jobs
Title: Message Title Steven Foster commented on JENKINS-43194 Re: Lightweight checkout for PR merge jobs Is it feasible to apply this as an optimization, even if it only applies a certain percentage of time, with the current behavior as a fallback? I guess it depends on if the parents of merge_commit_sha are cheaper to inspect than cloning the repo. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55867) sh step termination is never detected if the wrapper process is killed
Title: Message Title Steven Foster assigned an issue to Steven Foster Jenkins / JENKINS-55867 sh step termination is never detected if the wrapper process is killed Change By: Steven Foster Assignee: Steven Foster Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Steven Foster commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I have just updated blue ocean from 1.5 (where this UI feature was originally introduced, and working fine) to 1.10.1 and no longer have links to downstream jobs in my parallel steps. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Steven Foster commented on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks Stefan Rystedt's PR also fixes JENKINS-54541 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54541) Unreserve doesn't set environment variable
Title: Message Title Steven Foster created an issue Jenkins / JENKINS-54541 Unreserve doesn't set environment variable Issue Type: Bug Assignee: Unassigned Components: lockable-resources-plugin Created: 2018-11-08 12:23 Environment: lockable-resources 2.3 Priority: Major Reporter: Steven Foster The manual reserve feature doesn't work well with the pipeline variable feature. When a user unreserves a resource and the plugin assigns the resource immediately to a queued build, the environment variable won't be correctly set. In LockableResourceManager.unreserve, there is a LockStepExecution.proceed call at the end with the variable left null. I have no idea how to retrieve a singular variable to use at this point in the code. Add Comment
[JIRA] (JENKINS-50323) PullRequestSCMHead and PullRequestSCMRevision external use
Title: Message Title Steven Foster resolved as Fixed Jenkins / JENKINS-50323 PullRequestSCMHead and PullRequestSCMRevision external use Change By: Steven Foster Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51225) Support for GitHub Checks API
Title: Message Title Steven Foster commented on JENKINS-51225 Re: Support for GitHub Checks API I'd love this too. It seems to require the use of Github Apps over OAuth, which means it needs a bigger change underneath. Github Apps have the advantage of not taking up a user seat in github enterprise though Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49050) I can view my sequential declarative pipeline stages in the pipeline visualization plugin
Title: Message Title
Steven Foster commented on JENKINS-49050
Re: I can view my sequential declarative pipeline stages in the pipeline visualization plugin
From the screenshot, I guess that the stage group name ('multiple-stages' in the example Jenkinsfile) won't be displayed anywhere?
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-52683) Allow flexible source definition in WorkflowBranchProjectFactories
Title: Message Title Steven Foster created an issue Jenkins / JENKINS-52683 Allow flexible source definition in WorkflowBranchProjectFactories Issue Type: New Feature Assignee: Stephen Connolly Components: branch-api-plugin, workflow-multibranch-plugin Created: 2018-07-20 22:51 Priority: Minor Reporter: Steven Foster I'd like to write an extension which allows a different script path to be set for Tag type heads. My use case is that my Branch type builds build, test and store artifacts ready for release/deploy. Only tag builds perform whatever is needed to release that artifact. Releasing can mean different things for different projects. For smaller projects, it's ok to have the entire pipeline run again with an additional release stage covered by a when directive checking for a tag. With a large project this is an unfortunate inefficiency. I would like to define a separate Jenkinsfile which just handles releasing the artifact previously built in the branch build. I figure this can be possible by defining a new BranchProjectFactory, and using the createDefinition method to pick one Jenkinsfile for branch/pr and one for tags. The method would need to expose information about the head being built though. Perhaps passing through the Branch object would be helpful?
[JIRA] (JENKINS-47366) Checkout in second stage sets SUCCESS on Github commit
Title: Message Title Steven Foster commented on JENKINS-47366 Re: Checkout in second stage sets SUCCESS on Github commit I have an open PR at https://github.com/jenkinsci/github-branch-source-plugin/pull/175 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title Steven Foster commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Does this only work on environment variables configured on the node in jenkins? and so wouldn't work for non-static agents i.e. launched from cloud provider? Or does it work on environment variables set on the agent itself? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Steven Foster commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Is there a way to aggregate the triggered builds within a parallel stage? I'm launching 12 or so builds as a parallel stage (the whole build is basically just a dummy/launchpad for other builds) and clicking each individual stage to get the downstream link is very slightly bothersome Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34539) The global "system message" appears in every folder
Title: Message Title Steven Foster commented on JENKINS-34539 Re: The global "system message" appears in every folder What's an acceptable approach for this? Was looking at taking it on. Adding a property to AbstractFolderDescriptor for disabling system message toggleable under the Appearance section of the configure page might work, but is that too prominent? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50323) PullRequestSCMHead and PullRequestSCMRevision external use
Title: Message Title Steven Foster created an issue Jenkins / JENKINS-50323 PullRequestSCMHead and PullRequestSCMRevision external use Issue Type: Task Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-03-21 16:34 Environment: Github Branch Source 2.3.3 Priority: Minor Reporter: Steven Foster While working on an extension filter plugin for GitHub PR labels which adds an SCMHeadEvent implementation I noticed that the constructors for PullRequestSCMHead and PullRequestSCMRevision were package private. Using more generic classes, the scm source rejects the heads returned by the event and so the subscriber cannot operate. A locally modified version of GHBS with public constructors allowed the new plugin to work correctly. Discussion at https://groups.google.com/forum/#!topic/jenkinsci-dev/bLoYi3munDw Add Comment
[JIRA] (JENKINS-50119) Dynamic DSL for workflowMultiBranchProjectFactory not working
Title: Message Title Steven Foster commented on JENKINS-50119 Re: Dynamic DSL for workflowMultiBranchProjectFactory not working Nevermind that, I checked out 1.68 instead and the same changes worked fine. I guess recent work on master has temporarily broken multibranchPipelineJobs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50119) Dynamic DSL for workflowMultiBranchProjectFactory not working
Title: Message Title Steven Foster commented on JENKINS-50119 Re: Dynamic DSL for workflowMultiBranchProjectFactory not working I think the issue is multibranchPipelineJob should be using workflowBranchProjectFactory rather than workflowMultiBranchProject factory. I tried to implement it in monkey-see monkey-do fashion by creating a BranchProjectFactory context based on MultiBranchProjectFactoryContext, changing all references to MultiBranchProjectFactory to BranchProjectFactory, updating MultibranchWorkflowJob to use BranchProjectFactory, and updating a test. It's a bit over my head though and I'm hitting issues testing it out. It shows in the api viewer (which 404s in ./gradlew server) but if I try to make any kind of multibranchPipelineJob I get groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method groovy.util.XmlParser#parse. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.io.File] [class java.io.InputStream] [class java.io.Reader] [class java.lang.String] [class org.xml.sax.InputSource] at groovy.lang.MetaClassImpl.chooseMostSpecificParams(MetaClassImpl.java:3263) at groovy.lang.MetaClassImpl.chooseMethodInternal(MetaClassImpl.java:3216) at groovy.lang.MetaClassImpl.chooseMethod(MetaClassImpl.java:3159) at groovy.lang.MetaClassImpl.getMethodWithCachingInternal(MetaClassImpl.java:1331) at groovy.lang.MetaClassImpl.createPojoCallSite(MetaClassImpl.java:3391) at org.codehaus.groovy.runtime.callsite.CallSiteArray.createPojoSite(CallSiteArray.java:132) at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(CallSiteArray.java:166) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125) at javaposse.jobdsl.dsl.Folder.getNodeTemplate(Folder.groovy:110) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.MethodMetaProperty$GetBeanMethodMetaProperty.getProperty(MethodMetaProperty.java:76) at org.codehaus.groovy.runtime.callsite.GetEffectivePogoPropertySite.callGroovyObjectGetProperty(GetEffectivePogoPropertySite.java:68) at javaposse.jobdsl.dsl.Item.getNode(Item.groovy:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at org.codehaus.groovy.runtime.metaclass.MethodMetaProperty$GetBeanMethodMetaProperty.getProperty(MethodMetaProperty.java:76) at org.codehaus.groovy.runtime.callsite.GetEffectivePogoPropertySite.callGroovyObjectGetProperty(GetEffectivePogoPropertySite.java:68) at javaposse.jobdsl.dsl.Item.getXml(Item.groovy:34) at javaposse.jobdsl
[JIRA] (JENKINS-50119) Dynamic DSL for workflowMultiBranchProjectFactory not working
Title: Message Title
Steven Foster created an issue
Jenkins / JENKINS-50119
Dynamic DSL for workflowMultiBranchProjectFactory not working
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-03-12 14:44
Environment:
Job DSL 1.68 Pipeline Multibranch 2.17
Priority:
Minor
Reporter:
Steven Foster
When trying to configure the script path for a multibranchPipelineJob using the Dynamic DSL
factory {
workflowMultiBranchProjectFactory {
scriptPath("test/Jenkinsfile")
}
}
The default script path of just "Jenkinsfile" is configured on the generated job. I was initially using the prescribed DSL for github branch source jobs and thought that might have been the problem, but when I moved the branch source configuration to the Dynamic DSL the problem persisted.
multibranchPipelineJob('testing/scriptpath') {
branchSources {
branchSource {
source {
github {
id("test")
// Github Enterprise
apiUri('https://*/api/v3/')
credentialsId('github_token')
repoOwner("sfoster")
repository("branch_filter_test")
}
}
}
}
factory {
workflowMultiBranchProjectFactory {
scriptPath("test/Jenkinsfile")
}
}
}
[JIRA] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Steven Foster commented on JENKINS-34150 Re: Pipeline Batch hangs just the .tmp Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Steven Foster commented on JENKINS-34150 Re: Pipeline Batch hangs returnStdout: true has the same result. confirmed the process is finished on the machine. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Steven Foster commented on JENKINS-34150 Re: Pipeline Batch hangs I'm encountering the same issue after updating to 1.20 from 1.18 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47366) Checkout in second stage sets SUCCESS on Github commit
Title: Message Title Steven Foster commented on JENKINS-47366 Re: Checkout in second stage sets SUCCESS on Github commit Actually, I see the bug now. My mistake. I'll try to fix it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47366) Checkout in second stage sets SUCCESS on Github commit
Title: Message Title Steven Foster commented on JENKINS-47366 Re: Checkout in second stage sets SUCCESS on Github commit From what I understand, the Multibranch (github-branch-source) pipeline only updates the Github Commit Status at 3 places: When the job is queued (pending) When the repo is checked out (in progress) and When the job finishes (result) I'm not sure where it would update the commit status in the middle of the build, that's why I asked about another plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47366) Checkout in second stage sets SUCCESS on Github commit
Title: Message Title Steven Foster commented on JENKINS-47366 Re: Checkout in second stage sets SUCCESS on Github commit do you have https://plugins.jenkins.io/github-autostatus plugin installed? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
