[JIRA] [job-dsl-plugin] (JENKINS-31671) Add support for workflow multibranch
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.42. Jenkins / JENKINS-31671 Add support for workflow multibranch Change By: Daniel Spilker Status: In Progress Resolved Assignee: Daniel Spilker Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-31671) Add support for workflow multibranch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31671 Re: Add support for workflow multibranch Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Job-DSL-Commands.md job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/DslFactory/multibranchWorkflowJob.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/workflow/BranchSourcesContext/git.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/workflow/OrphanedItemStrategyContext/discardOldItems.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/DslFactory.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/JobParent.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/BranchSourcesContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/DefaultOrphanedItemStrategyContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/GitBranchSourceContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/OrphanedItemStrategyContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/jobs/MultibranchWorkflowJob.groovy job-dsl-core/src/main/resources/javaposse/jobdsl/dsl/jobs/MultibranchWorkflowJob-template.xml job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/JobParentSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/workflow/BranchSourcesContextsSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/workflow/OrphanedItemStrategyContextSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/jobs/MultibranchWorkflowJobSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/c8fe953421428fdaa533cfc56d0f78059b603d4a Log: Merge branch 'JENKINS-31671' Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/e44f0b5aae21...c8fe95342142 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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
[JIRA] [git-plugin] (JENKINS-29796) Multiple refspecs should be matched using OR, not AND
Title: Message Title Hannes Schmidt closed an issue as Fixed Confirmed fixed in 2.4.1 Jenkins / JENKINS-29796 Multiple refspecs should be matched using OR, not AND Change By: Hannes Schmidt Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat updated an issue Jenkins / JENKINS-31035 Introduce a policy for API deprecation Change By: evernat h1. Problem definitionCurrently, we have no backward compatibility policy besides ["compatibility matters"|https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Compatibilitymatters]. With 1000+ plugins and basically the entire core being available to plugins, a lot of difficult or impossible to remove cruft has accumulated over the last ten years. This limits both what can be changed in core, and makes documentation difficult to use for plugin developers.Elaborate solutions such as the bytecode compatibility transformer currently (Oct 2015) introduce difficult to investigate bugs that result in things breaking for users.h1. ProposalLimit the availability in APIs (classes, methods, fields, …) provided by core to a number of releases. Depending on the feature, this can range from a few months, to a few years (e.g. two years being about 100 releases of Jenkins and eight LTS baselines).This deprecation policy needs to be supported by tools that check publicly accessible plugins for access to deprecated (or to-be-deprecated) APIs and generate reports on them to inform deprecation policy decisions.Ideally, Jenkins core will be enhanced to include the capability to check both plugins for use of removed APIs, so it can refuse to load plugins considered incompatible with the running Jenkins version, and the update site generation should be improved to exclude plugins that are known incompatible with the core release downloading the plugin information.h1. ImpactThe impact of this change is not currently known both due to the large number of deprecated APIs and because we don't currently have the tooling above.Removal of APIs needs to be done carefully (rather than wholesale), and affected, open-source plugins hosted by the Jenkins project need to be fixed to no longer rely on those APIs. This will force users to update affected plugins when updating Jenkins itself (which may be inconvenient if the new plugin release not using deprecated APIs is not compatible with the previously installed version), but it should at least ensure continued operation of their plugins.This change may increase the frequency by which new plugin versions require newer core releases to run, as the replacement APIs may be new to the release that deprecated the existing API.h1. Open questions* How long is the deprecation period before an API gets removed?** Should the same duration be used for all deprecations, or should it depend on the specific API?*** If the latter, what are the lower/upper bounds, if any, of the deprecation period before removal?* What steps need to be followed to define a removal date for an API? Examples:*# Provide a list of affected plugins and propose how they can be fixed? ( 435 618 plugins are using a deprecated api among which a large number are only using Hudson.getInstance() or Plugin() , see [details here|https:// github ci . com jenkins-ci.org / evernat view / deprecated Infrastructure/job/infra_deprecated -usage-in-plugins/ blob lastSuccessfulBuild / master artifact / Output_example target/output . txt html ]. [~evernat])*# Provide a list of affected plugins and fix them (possibly including
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat edited a comment on JENKINS-31035 Re: Introduce a policy for API deprecation > Provide a list of affected plugins and propose how they can be fixed?There are at least 435 618 plugins using a deprecated Jenkins api , among which a large number are only using Hudson . getInstance() or Plugin(). 19 20 deprecated classes, 166 172 deprecated methods and 12 13 deprecated fields are used in plugins. 29 28 deprecated and public Jenkins classes, 312 318 deprecated methods, 58 deprecated fields are not used in the latest published plugins (and which may be removed as part of Jenkins 2.0 ?).You can see details for each plugin and of used or not deprecated api at https:// github ci . com jenkins-ci.org / evernat view / deprecated Infrastructure/job/infra_deprecated -usage-in-plugins/ blob lastSuccessfulBuild / master artifact / Output_example.txt(I will suggest to run this tool automatically at https: target / /ci output . jenkins-ci.org/ or https://jenkins.ci.cloudbees.com/) html Perhaps, some PR could be submitted to fix some of these plugins during [Jenkins Hacksgiving|https://wiki.jenkins-ci.org/display/JENKINS/Hacksgiving+2015] in the next few days ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-31653) readFileFromWorkspace doesn't not update the shell step if the referenced file content has changed
Title: Message Title Daniel Spilker resolved as Cannot Reproduce Jenkins / JENKINS-31653 readFileFromWorkspace doesn't not update the shell step if the referenced file content has changed Change By: Daniel Spilker Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [matrix-auth-plugin] (JENKINS-26917) Folders do not allow to "Block inheritance of global authorization matrix"
Title: Message Title Daniel Beck resolved as Duplicate This is actually an issue in the Folders Plugin, therefore resolving as duplicate of an issue that's filed against that. Jenkins / JENKINS-26917 Folders do not allow to "Block inheritance of global authorization matrix" Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-12032) Include SCM changes in environment variables
Title: Message Title Daniel Beck resolved as Fixed No response for over a month, so with the public release of the plugin source code I consider this issue resolved. Jenkins / JENKINS-12032 Include SCM changes in environment variables Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31768) dead lock while removing computer
Title: Message Title
Oliver Gondža updated an issue
Jenkins / JENKINS-31768
dead lock while removing computer
Change By:
Oliver Gondža
{noformat} "Handling POST /configSubmit from 10.160.255.74 : RequestHandlerThread[#17137]": waiting for ownable synchronizer 0x7f3a5d901708, (a java.util.concurrent.locks.ReentrantLock$NonfairSync), which is held by "Computer.threadPoolForRemoting [#31767]""Computer.threadPoolForRemoting [#31767]": waiting to lock monitor 0x7f38ce077bc8 (object 0x7f3a7c8a10c8, a hudson.plugins.ec2.EC2Computer), which is held by "Handling POST /configSubmit from 10.160.255.74 : RequestHandlerThread[#17137]""Handling POST /configSubmit from 10.160.255.74 : RequestHandlerThread[#17137]":at sun.misc.Unsafe.park(Native Method)- parking to wait for <0x7f3a5d901708> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)at hudson.model.Queue._withLock(Queue.java:1291)at hudson.model.Queue.withLock(Queue.java:1176)at hudson.model.Computer.setNumExecutors(Computer.java:837)- locked <0x7f3a7c8a10c8> (a hudson.plugins.ec2.EC2Computer)at hudson.model.Computer.kill(Computer.java:792)at hudson.slaves.SlaveComputer.kill(SlaveComputer.java:665)at hudson.model.AbstractCIBase.killComputer(AbstractCIBase.java:86)at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:205)at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1249)at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2924)- locked <0x7f3a5c073f20> (a hudson.model.Hudson)"Computer.threadPoolForRemoting [#31767]":at hudson.model.Computer.setNumExecutors(Computer.java:830)- waiting to lock <0x7f3a7c8a10c8> (a hudson.plugins.ec2.EC2Computer)at hudson.model.Computer.inflictMortalWound(Computer.java:809)at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:199)at hudson.model.Queue._withLock(Queue.java:1293)at hudson.model.Queue.withLock(Queue.java:1176)at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:169)at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1249)at jenkins.model.Nodes$2.run(Nodes.java:136)at hudson.model.Queue._withLock(Queue.java:1293)at hudson.model.Queue.withLock(Queue.java:1176)at jenkins.model.Nodes.addNode(Nodes.java:132)at jenkins.model.Jenkins.addNode(Jenkins.java:1744) {noformat}
[JIRA] [subversion-plugin] (JENKINS-25239) Subversion SCM plugin fails to do an svn update
Title: Message Title Martin Gainty commented on JENKINS-25239 Re: Subversion SCM plugin fails to do an svn update This looks to be a problem with the Windows Based Jenkins Slave: open a command line window cmd.exe sc qc "JenkinsSlave" (if that's what your service name is) select and copy the BINARY_PATH_NAME value change it, adding -Dsvnkit.http.sslProtocols=""TLSv1"" after the jar path - mind the double quote sc config "JenkinsSlave" binPath= Replace JenkinsSlave with your service name. then restart jenkins webapp with the following arg: -Dsvnkit.http.sslProtocols="TLSv1" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [artifactory-plugin] (JENKINS-17593) Artifactory Plugin Uses Incorrect Artifact Names
Title: Message Title Gil Collins commented on JENKINS-17593 Re: Artifactory Plugin Uses Incorrect Artifact Names I have the same issue, thank you for your response. This solved my issue for now. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
