[JIRA] (JENKINS-35223) Allow configurable date/time format for all temporal fields in output
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35223 Allow configurable date/time format for all temporal fields in output Change By: James Dumay Attachment: alt.png 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-34005) Make WorkflowJob.triggers into a JobProperty
Title: Message Title Dan Jasek edited a comment on JENKINS-34005 Re: Make WorkflowJob.triggers into a JobProperty I implemented a solution to this, for the reason Greg describes.This is the step: https://gist.github.com/oillio/14cb6621877ecfb3a1d711e0f31ace90It is not the same solution as you describe. It is a new step which allows setting the scmTrigger for the job, instead of rewriting the job to use JobProperty for the triggers.If this is an acceptable fix, I would be happy to flesh this out and generalize it to other triggers , and submit it as a pull request . 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-34005) Make WorkflowJob.triggers into a JobProperty
Title: Message Title Dan Jasek commented on JENKINS-34005 Re: Make WorkflowJob.triggers into a JobProperty I implemented a solution to this, for the reason Greg describes. This is the step: https://gist.github.com/oillio/14cb6621877ecfb3a1d711e0f31ace90 It is not the same solution as you describe. It is a new step which allows setting the scmTrigger for the job, instead of rewriting the job to use JobProperty for the triggers. If this is an acceptable fix, I would be happy to flesh this out and generalize it to other triggers. 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-35686) Make multibranch jobs share workspace
Title: Message Title Eli White updated an issue Jenkins / JENKINS-35686 Make multibranch jobs share workspace Change By: Eli White Environment: Jenkins: 2.1 git-client-plugin: 1.19.6 Pipeline: SCM Step: 2.1 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-35686) Make multibranch pipeline jobs share workspace
Title: Message Title Eli White updated an issue Jenkins / JENKINS-35686 Make multibranch pipeline jobs share workspace Change By: Eli White Summary: Make multibranch pipeline jobs share workspace 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-35686) Make multibranch jobs share workspace
Title: Message Title Eli White created an issue Jenkins / JENKINS-35686 Make multibranch jobs share workspace Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Jun/14 12:28 AM Priority: Minor Reporter: Eli White We have a large repo (3+ gigs) and when using multibranch pipeline jobs, each branch gets its own workspace and is cloned fresh. We would like to have each of these branches share the same workspace (or @2, @3, etc if it is in use). Add Comment
[JIRA] (JENKINS-35669) email-ext-plugin shows HTML entities as plaintext in HTML email output
Title: Message Title David van Laatum commented on JENKINS-35669 Re: email-ext-plugin shows HTML entities as plaintext in HTML email output Will try to take a look when I get home from work do you have a previous jira? 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-33980) Document (List) Pipeline features of email-ext-plugin
Title: Message Title David van Laatum closed an issue as Fixed Updated the wiki last night Jenkins / JENKINS-33980 Document (List) Pipeline features of email-ext-plugin Change By: David van Laatum 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-35685) Auto-generate help for RunWrapperBinder/RunWrapper
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-35685 Auto-generate help for RunWrapperBinder/RunWrapper Issue Type: Task Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Jun/14 12:09 AM Priority: Minor Reporter: Andrew Bayer RunWrapper has a lot more @Whitelisted methods on it than are covered in the help doc - it'd be great if we could inspect Javadoc on those methods and spit out help from that automatically. Might even be something we could extend to other GlobalVariable use cases like Docker's - some sort of annotation on functions that lets us know to inspect them... Jesse Glick, thoughts? Add Comment
[JIRA] [git-plugin] (JENKINS-35684) No option to set clone timeout for multi branch pipeline
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-35684 No option to set clone timeout for multi branch pipeline Change By: Mark Waite Component/s: git-client-plugin 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] [git-client-plugin] (JENKINS-35684) No option to set clone timeout for multi branch pipeline
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-35684 No option to set clone timeout for multi branch pipeline Change By: Mark Waite Assignee: Mark Waite 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] [git-client-plugin] (JENKINS-35684) No option to set clone timeout for multi branch pipeline
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-35684 No option to set clone timeout for multi branch pipeline Change By: Mark Waite Component/s: git-plugin 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] [junit-attachments-plugin] (JENKINS-28784) junit-attachments plugin not compatible with Pipeline
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-28784
junit-attachments plugin not compatible with Pipeline
Change By:
Jesse Glick
The JUnit-attachments-plugin doesn appear to be compatible with Workflow jobs.Test for reproducing the issue:Create the following Workflow job:{code :groovy }node ('master') { sh ''' mkdir -p test cd test wget http://lazerbrody.typepad.com/photos/uncategorized/2007/03/22/mammy_yokum_broigges.jpg cat << EOF > test.xml [[ATTACHMENT|test/mammy_yokum_broigges.jpg]] For no good reason!EOF''' // step([$class: 'JUnitResultArchiver', testResults: 'test/*.xml']) step([$class: 'JUnitResultArchiver', testDataPublishers: [[$class: 'AttachmentPublisher']], testResults: 'test/*.xml'])}{code}Observed result:{noformat}Started by user thomasRunning: Allocate node : StartRunning on master in /var/lib/jenkins/workspace/WFJUnitPostBuildRunning: Allocate node : Body : StartRunning: Shell Script[WFJUnitPostBuild] Running shell script+ mkdir -p test+ cd test+ wget http://lazerbrody.typepad.com/photos/uncategorized/2007/03/22/mammy_yokum_broigges.jpg--2015-06-07 13:07:51-- http://lazerbrody.typepad.com/photos/uncategorized/2007/03/22/mammy_yokum_broigges.jpgResolving lazerbrody.typepad.com (lazerbrody.typepad.com)... 190.93.247.9, 141.101.115.9, 190.93.245.9, ...Connecting to lazerbrody.typepad.com (lazerbrody.typepad.com)|190.93.247.9|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 18510 (18K) [image/jpeg]Saving to: ‘mammy_yokum_broigges.jpg’ 0K .. 100% 787K=0,02s2015-06-07 13:07:52 (787 KB/s) - ‘mammy_yokum_broigges.jpg.1’ saved [18510/18510]+ catRunning: General Build StepRunning: Allocate node : Body : EndRunning: Allocate node : EndRunning: End of Workflowjava.lang.ClassCastException: sun.reflect.generics.reflectiveObjects.WildcardTypeImpl cannot be cast to java.lang.Class at org.jenkinsci.plugins.workflow.structs.DescribableHelper.coerce(DescribableHelper.java:224) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.mapList(DescribableHelper.java:263) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.coerce(DescribableHelper.java:248) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.buildArguments(DescribableHelper.java:186) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.injectSetters(DescribableHelper.java:308) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.instantiate(DescribableHelper.java:93) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.coerce(DescribableHelper.java:236) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.buildArguments(DescribableHelper.java:186) at org.jenkinsci.plugins.workflow.structs.DescribableHelper.instantiate(DescribableHelper.java:91) at
[JIRA] [structs-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26535 DescribableHelper does not handle wildcards well Change By: Jesse Glick Component/s: structs-plugin Component/s: workflow-plugin 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] [structs-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26535 DescribableHelper does not handle wildcards well Change By: Jesse Glick Labels: workflow 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] [git-client-plugin] (JENKINS-35684) No option to set clone timeout for multi branch pipeline
Title: Message Title Eli White updated an issue Jenkins / JENKINS-35684 No option to set clone timeout for multi branch pipeline Change By: Eli White Labels: git-plugin workflow 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] [git-client-plugin] (JENKINS-35684) No option to set clone timeout for multi branch pipeline
Title: Message Title Eli White created an issue Jenkins / JENKINS-35684 No option to set clone timeout for multi branch pipeline Issue Type: Bug Assignee: Mark Waite Attachments: Screen Shot 2016-06-13 at 3.21.17 PM.png Components: git-client-plugin, workflow-multibranch-plugin Created: 2016/Jun/13 10:25 PM Environment: Jenkins: 2.1 git-client-plugin: 1.19.6 Pipeline: SCM Step: 2.1 Priority: Minor Reporter: Eli White With my single branch pipeline builds and freestyle builds, I'm able to set clone and checkout timeouts on my SCM source. With a multi branch pipeline job, that option isn't available. See the screenshot for more info
[JIRA] [delivery-pipeline-plugin] (JENKINS-35683) Manual Trigger isn't detected when previous upstream job doesn't have manual trigger
Title: Message Title Thomas Brezinski created an issue Jenkins / JENKINS-35683 Manual Trigger isn't detected when previous upstream job doesn't have manual trigger Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2016/Jun/13 10:13 PM Priority: Minor Reporter: Thomas Brezinski When a job with multiple upstream jobs is checked for a manual trigger, only the first upstream job is checked. This is resulting in missing manual triggers in my pipelines. In my case: jobA -> downstreamTrigger -> jobC jobB -> manualTrigger -> jobC isManualTrigger(jobC) wouldn't evaluate to true and a manual trigger wouldn't be added to the pipeline view. Add Comment
[JIRA] [core] (JENKINS-35666) Regular 404s for running builds that get better after build is finished.
Title: Message Title
Ben Clifford edited a comment on JENKINS-35666
Re: Regular 404s for running builds that get better after build is finished.
Here are the headers from a multibranch project that i) I got to show this error, and then ii) shows itself getting better at the end of the run build :i) not working after a few minutes:{{< Stapler-Trace-001: -> evaluate( :hudson.model.Hudson,"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-002: -> evaluate(((StaplerProxy)).getTarget(),"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-003: -> evaluate(.getJob("beautilytics"),"/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-004: -> evaluate( :com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleMultiBranchProject,"/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-005: -> evaluate(.getBranch("benc-tmp-debug-jenkins-1"),"/1/console")< Stapler-Trace-006: -> evaluate( :hudson.model.FreeStyleProject,"/1/console")< Stapler-Trace-007: -> evaluate(.getDynamic("1",...),"/console")< Stapler-Trace-008: hudson.model.FreeStyleProject@736075be[beautilytics/benc-tmp-debug-jenkins-1].getDynamic("1",...)==null. Back tracking.and}}ii) working after the job build has finished:{{< Stapler-Trace-001: -> evaluate( :hudson.model.Hudson,"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-002: -> evaluate(((StaplerProxy)).getTarget(),"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-003: -> evaluate(.getJob("beautilytics"),"/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-004: -> evaluate( :com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleMultiBranchProject,"/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-005: -> evaluate(.getBranch("benc-tmp-debug-jenkins-1"),"/1/console")< Stapler-Trace-006: -> evaluate( :hudson.model.FreeStyleProject,"/1/console")< Stapler-Trace-007: -> evaluate(.getDynamic("1",...),"/console")< Stapler-Trace-008: -> evaluate( :hudson.model.FreeStyleBuild,"/console")< Stapler-Trace-009: -> hudson/model/Run/console.jelly on }}
Add Comment
[JIRA] [core] (JENKINS-35666) Regular 404s for running builds that get better after build is finished.
Title: Message Title
Ben Clifford edited a comment on JENKINS-35666
Re: Regular 404s for running builds that get better after build is finished.
Here are the headers from a multibranch project that i) I got to show this error, and then ii) shows itself getting better at the end of the run:i) not working after a few minutes: {{ < Stapler-Trace-001: -> evaluate( :hudson.model.Hudson,"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-002: -> evaluate(((StaplerProxy)).getTarget(),"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-003: -> evaluate(.getJob("beautilytics"),"/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-004: -> evaluate( :com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleMultiBranchProject,"/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-005: -> evaluate(.getBranch("benc-tmp-debug-jenkins-1"),"/1/console")< Stapler-Trace-006: -> evaluate( :hudson.model.FreeStyleProject,"/1/console")< Stapler-Trace-007: -> evaluate(.getDynamic("1",...),"/console")< Stapler-Trace-008: hudson.model.FreeStyleProject@736075be[beautilytics/benc-tmp-debug-jenkins-1].getDynamic("1",...)==null. Back tracking. }} and }} ii) working after the job has finished: {{ < Stapler-Trace-001: -> evaluate( :hudson.model.Hudson,"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-002: -> evaluate(((StaplerProxy)).getTarget(),"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-003: -> evaluate(.getJob("beautilytics"),"/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-004: -> evaluate( :com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleMultiBranchProject,"/branch/benc-tmp-debug-jenkins-1/1/console")< Stapler-Trace-005: -> evaluate(.getBranch("benc-tmp-debug-jenkins-1"),"/1/console")< Stapler-Trace-006: -> evaluate( :hudson.model.FreeStyleProject,"/1/console")< Stapler-Trace-007: -> evaluate(.getDynamic("1",...),"/console")< Stapler-Trace-008: -> evaluate( :hudson.model.FreeStyleBuild,"/console")< Stapler-Trace-009: -> hudson/model/Run/console.jelly on }}
Add Comment
[JIRA] [core] (JENKINS-35666) Regular 404s for running builds that get better after build is finished.
Title: Message Title
Ben Clifford commented on JENKINS-35666
Re: Regular 404s for running builds that get better after build is finished.
Here are the headers from a multibranch project that i) I got to show this error, and then ii) shows itself getting better at the end of the run:
i) not working after a few minutes:
{{< Stapler-Trace-001: -> evaluate( :hudson.model.Hudson,"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console") < Stapler-Trace-002: -> evaluate(((StaplerProxy)).getTarget(),"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console") < Stapler-Trace-003: -> evaluate(.getJob("beautilytics"),"/branch/benc-tmp-debug-jenkins-1/1/console") < Stapler-Trace-004: -> evaluate( :com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleMultiBranchProject,"/branch/benc-tmp-debug-jenkins-1/1/console") < Stapler-Trace-005: -> evaluate(.getBranch("benc-tmp-debug-jenkins-1"),"/1/console") < Stapler-Trace-006: -> evaluate( :hudson.model.FreeStyleProject,"/1/console") < Stapler-Trace-007: -> evaluate(.getDynamic("1",...),"/console") < Stapler-Trace-008: hudson.model.FreeStyleProject@736075be[beautilytics/benc-tmp-debug-jenkins-1].getDynamic("1",...)==null. Back tracking. }}
and
ii) working after the job has finished:
{{ < Stapler-Trace-001: -> evaluate( :hudson.model.Hudson,"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console") < Stapler-Trace-002: -> evaluate(((StaplerProxy)).getTarget(),"/job/beautilytics/branch/benc-tmp-debug-jenkins-1/1/console") < Stapler-Trace-003: -> evaluate(.getJob("beautilytics"),"/branch/benc-tmp-debug-jenkins-1/1/console") < Stapler-Trace-004: -> evaluate( :com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleMultiBranchProject,"/branch/benc-tmp-debug-jenkins-1/1/console") < Stapler-Trace-005: -> evaluate(.getBranch("benc-tmp-debug-jenkins-1"),"/1/console") < Stapler-Trace-006: -> evaluate( :hudson.model.FreeStyleProject,"/1/console") < Stapler-Trace-007: -> evaluate(.getDynamic("1",...),"/console") < Stapler-Trace-008: -> evaluate( :hudson.model.FreeStyleBuild,"/console") < Stapler-Trace-009: -> hudson/model/Run/console.jelly on }}
Add Comment
[JIRA] [ghprb-plugin] (JENKINS-34762) PR status cannot be updated due to filtered parameters
Title: Message Title Yoann Dubreuil commented on JENKINS-34762 Re: PR status cannot be updated due to filtered parameters Christopher Orr The fix was rolled back in 1.32.2 and re-introduced in 1.32.3. I updated the wiki page to reflect this. 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-34060) Unstable a build when DSL scripts pattern doesn't list any files
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-34060 Unstable a build when DSL scripts pattern doesn't list any files Change By: SCM/JIRA link daemon 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-35666) Regular 404s for running builds that get better after build is finished.
Title: Message Title Ben Clifford edited a comment on JENKINS-35666 Re: Regular 404s for running builds that get better after build is finished. (the The previous paste is from a working build that is not a multi-branch project build, but on the same relevant jenkins install ) . Most of our builds are under multi-branch projects, though I haven't particularly paid attention to whether this happens only on those or not. 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-34060) Unstable a build when DSL scripts pattern doesn't list any files
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34060 Re: Unstable a build when DSL scripts pattern doesn't list any files Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/User-Power-Moves.md job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/ExecuteDslScripts.java job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/ScriptRequestGenerator.groovy job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/ExecuteDslScripts/config.jelly job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/ExecuteDslScripts/help-ignoreMissingFiles.html job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/ExecuteDslScriptsSpec.groovy job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/ScriptRequestGeneratorSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/9c85e7f87c5379bedb53e72f7edd038bb8f0fb16 Log: added option to ignore missing files (#866) [FIXES JENKINS-34060] 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-35666) Regular 404s for running builds that get better after build is finished.
Title: Message Title Ben Clifford commented on JENKINS-35666 Re: Regular 404s for running builds that get better after build is finished. (the previous paste is from a working build that is not a multi-branch project build, but on the same jenkins install) 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] [analysis-core-plugin] (JENKINS-13056) Obtain reference build from SCM/Trigger
Title: Message Title Ulli Hafner commented on JENKINS-13056 Re: Obtain reference build from SCM/Trigger Currently the computation of the reference build is hard-coded in BuildHistory (there are two options available). I think this class should be modified, so that the actual computation is delegated to a strategy. The two current implementations will then be the first two strategies. A SCM trigger could be the third one. In the UI rather than two checkboxes the strategy should be selected. 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-35666) Regular 404s for running builds that get better after build is finished.
Title: Message Title
Ben Clifford commented on JENKINS-35666
Re: Regular 404s for running builds that get better after build is finished.
For a working, finished build:
{{> GET /job/benc-master-db/47/console HTTP/1.1 > Host: loris.beautifuldestinations.com:2000 > Accept-Encoding: deflate, gzip > User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Iceweasel/44.0.2 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 > Accept-Language: en-US,en;q=0.5 > DNT: 1 > Referer: http://loris.beautifuldestinations.com:2000/job/benc-master-db/47/ > Cookie: *ELIDED BY benclifford* > Connection: keep-alive > Cache-Control: max-age=0 > < HTTP/1.1 200 OK < Date: Mon, 13 Jun 2016 21:20:15 GMT < X-Content-Type-Options: nosniff < Stapler-Trace-001: -> evaluate( :hudson.model.Hudson,"/job/benc-master-db/47/console") < Stapler-Trace-002: -> evaluate(((StaplerProxy)).getTarget(),"/job/benc-master-db/47/console") < Stapler-Trace-003: -> evaluate(.getJob("benc-master-db"),"/47/console") < Stapler-Trace-004: -> evaluate( :hudson.model.FreeStyleProject,"/47/console") < Stapler-Trace-005: -> evaluate(.getDynamic("47",...),"/console") < Stapler-Trace-006: -> evaluate( :hudson.model.FreeStyleBuild,"/console") < Stapler-Trace-007: -> hudson/model/Run/console.jelly on < Content-Encoding: gzip < Expires: 0 < Cache-Control: no-cache,no-store,must-revalidate < X-Hudson-Theme: default < Content-Type: text/html;charset=UTF-8 < X-Hudson: 1.395 < X-Jenkins: 2.8 < X-Jenkins-Session: 7ae07cb4 < X-Frame-Options: sameorigin < X-Instance-Identity: *ELIDED BY benclifford* < X-SSH-Endpoint: loris.beautifuldestinations.com:43014 < X-ConsoleAnnotator: *ELIDED BY benclifford* < Content-Length: 9165 < Server: Jetty(9.2.z-SNAPSHOT) }}
I'll get some from a failing case when I can poke it into happening.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [parallel-test-executor-plugin] (JENKINS-35682) Update documentation to show "inclusions" feature.
Title: Message Title Liam Newman commented on JENKINS-35682 Re: Update documentation to show "inclusions" feature. Jesse Glick Any chance we could get this updated? 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] [parallel-test-executor-plugin] (JENKINS-35682) Update documentation to show "inclusions" feature.
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-35682 Update documentation to show "inclusions" feature. Change By: Liam Newman This a great plugin! It is super easy to get working with maven projects. The addition of "includesFile" feature works well, but the documentation doesn't show how to use it. The demo shows it working, but it requires reading and understanding of the demo. Documentation on the plugin's main page (https://wiki.jenkins-ci.org/display/JENKINS/Parallel+Test+Executor+Plugin) doesn't mention it. I'm working on a blog post that will show the includesFile being used, it would be great if the documentation were up-to-date, so I could point to it. 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] [parallel-test-executor-plugin] (JENKINS-35682) Update documentation to show "inclusions" feature.
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-35682 Update documentation to show "inclusions" feature. Change By: Liam Newman This a great plugin! It is super easy to get working with maven projects. The addition of "includesFile" feature works well, but the documentation doesn't show how to use it. The demo shows it working, but it requires reading and understanding of the demo. Documentation on the plugin's main page doesn't mention it. I'm working on a blog post that will show the includesFile being used, it would be great if the documentation were up-to-date, so I could point to it. 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] [parallel-test-executor-plugin] (JENKINS-35682) Update documentation to show "inclusions" feature.
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-35682 Update documentation to show "inclusions" feature. Change By: Liam Newman This a great plugin! It is super easy to get 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] [parallel-test-executor-plugin] (JENKINS-35682) Update documentation to show "inclusions" feature.
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-35682 Update documentation to show "inclusions" feature. Issue Type: Bug Assignee: Unassigned Components: parallel-test-executor-plugin Created: 2016/Jun/13 9:06 PM Priority: Minor Reporter: Liam Newman Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received
[JIRA] [pipeline-view-plugin] (JENKINS-35681) Scripts not permitted to use staticMethod DefaultGroovyMethods each java.util.List Closure
Title: Message Title
Kevin Brightwell updated an issue
Jenkins / JENKINS-35681
Scripts not permitted to use staticMethod DefaultGroovyMethods each java.util.List Closure
Change By:
Kevin Brightwell
Within a Pipeline script, the `each` method can not be used on a List. e.g. { { code:java} ['clang', 'gcc'].each { compiler -> echo "compiler = ${compiler}" } {code } } Error: { { code} org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods each java.util.List groovy.lang.Closure at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectStaticMethod(StaticWhitelist.java:174) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:95) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15) at WorkflowScript.run(WorkflowScript:68) 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.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 com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:40) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:276) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:78) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:185) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:183) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) ... {code } } I apologize as I'm sure the component is incorrect.
[JIRA] [pipeline-view-plugin] (JENKINS-35681) Scripts not permitted to use staticMethod DefaultGroovyMethods each java.util.List Closure
Title: Message Title
Kevin Brightwell created an issue
Jenkins / JENKINS-35681
Scripts not permitted to use staticMethod DefaultGroovyMethods each java.util.List Closure
Issue Type:
Bug
Assignee:
Sergei Egorov
Components:
pipeline-view-plugin
Created:
2016/Jun/13 8:50 PM
Environment:
OS: Ubuntu 16.04 Jenkins: 2.8 java Version: openjdk version "1.8.0_91" OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode) Groovy Version: Included
Labels:
pipeline security
Priority:
Minor
Reporter:
Kevin Brightwell
Within a Pipeline script, the `each` method can not be used on a List.
e.g. {{['clang', 'gcc'].each { compiler -> echo "compiler = $ {compiler}
" }}}
Error: {{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods each java.util.List
[JIRA] [gitlab-plugin] (JENKINS-34700) parameters are not "overwritten"
Title: Message Title Chris Russell commented on JENKINS-34700 Re: parameters are not "overwritten" Owen Mehegan: Fantastic background on the issue, thank you very much. Pipeline support is paramount, in my opinion; as far as I'm concerned, that alone justifies this change. I highly recommend including a very brief explanation of why this changed when you finish updating the docs – it is not obvious to end users, and the change can have real impact on the way some craft their workflows. Thank you for your hard work on maintaining this plugin. (Robin Müller you too, of course!) 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] [dashboard-view-plugin] (JENKINS-35414) Folders don't show up in dashboard view after upgrade
Title: Message Title Nick Jones commented on JENKINS-35414 Re: Folders don't show up in dashboard view after upgrade Same problem here with Dashboard View 2.9.10. It doesn't seem to be related to how the jobs are chosen for the view (regular _expression_ or explicitly chosen list via checkboxes) – neither works. I downgraded to 2.9.7, which I'd been running previously, and Folders reappeared. 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-35666) Regular 404s for running builds that get better after build is finished.
Title: Message Title Daniel Beck commented on JENKINS-35666 Re: Regular 404s for running builds that get better after build is finished. This is a Workflow Multibranch project, right? Go to the Jenkins script console, and run this command: org.kohsuke.stapler.Dispatcher.TRACE = true Now, when requesting a build related URL, check the HTTP response headers sent by Jenkins. There will be headers named X-Stapler-Trace-001 or similar. Please provide all of them. CC Jesse Glick 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] [vsphere-cloud-plugin] (JENKINS-28930) Make VSphereBuildStepContainer implement SimpleBuildStep
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28930 Re: Make VSphereBuildStepContainer implement SimpleBuildStep Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/49774c5ef2460b9435311b02d32b45d1091a66f0 Log: Merge pull request #394 from witokondoria/patch-1 JENKINS-28930 Noting release of vsphere-cloud-plugin including pipelines support Compare: https://github.com/jenkinsci/pipeline-plugin/compare/15dbf7093031...49774c5ef246 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] [nexus-artifact-uploader-plugin] (JENKINS-34943) Add support for Jenkins Pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34943 Re: Add support for Jenkins Pipeline Code changed in jenkins User: Sverre Moe Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/fbb0b831764b9fa1206dbc55419178bab9da887d Log: JENKINS-34943 Add nexus to COMPATIBLITY.md 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] [nexus-artifact-uploader-plugin] (JENKINS-34943) Add support for Jenkins Pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34943 Re: Add support for Jenkins Pipeline Code changed in jenkins User: Sverre Moe Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/7251c2d835227bd30ba67f010eb0c69d3d3d0ec6 Log: JENKINS-34943 Update nexus in COMPATIBLITY.md Supported as of 2.2 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] [nexus-artifact-uploader-plugin] (JENKINS-34943) Add support for Jenkins Pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34943 Re: Add support for Jenkins Pipeline Code changed in jenkins User: Sverre Moe Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/d3107677ecaf93d4dc42c0eacf684b2f44fa4c63 Log: JENKINS-34943 Add cppcheck to COMPATIBLITY.md 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] [gitlab-plugin] (JENKINS-34700) parameters are not "overwritten"
Title: Message Title Owen Mehegan commented on JENKINS-34700 Re: parameters are not "overwritten" Chris Russell The change was required for two reasons. First, in order to support the Pipeline project type. See https://github.com/jenkinsci/gitlab-plugin/issues/271 for the discussion around this. Second, a security issue in Jenkins was fixed (see https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170), but the fix prevents plugins from defining arbitrary job parameters; parameters must be explicitly configured in the Jenkins job. So, going forward, unless you define every parameter you want to use in your job config, the plugin can't change their values. At least with environment variables, you can use all of them in shell script steps and Pipeline job types. We need to update the documentation to provide a complete example of how to use the EnvInject plugin to work around this. 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] [deploy-plugin] (JENKINS-35214) Unable to deploy the ear file using weblogic-deployer-plugin
Title: Message Title Raphael CHAUMIER commented on JENKINS-35214 Re: Unable to deploy the ear file using weblogic-deployer-plugin Hi Brian Wu OK. For weblogic version later than 10 It is recommended to replace weblogic.jar by wlfullclient. If you didn't build it, here is a link that explain how to do https://docs.oracle.com/cd/E12840_01/wls/docs103/client/jarbuilder.html Can you try to deploy with wlfullclient.jar Regards 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] [metrics-plugin] (JENKINS-35630) Building on an executor for Pipeline job is incorrect
Title: Message Title Jesse Glick assigned an issue to Unassigned This text is contributed by the Metrics plugin, it seems. Probably TimeInQueueAction should be restricted to AbstractBuild; it makes little sense for other Run types. Jenkins / JENKINS-35630 Building on an executor for Pipeline job is incorrect Change By: Jesse Glick Component/s: metrics-plugin Component/s: workflow-plugin Labels: workflow Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title Jesse Glick commented on JENKINS-33596 Re: Disable DNSMultiCast & UDPBroadcastThread by default Linking some apparently related issues which should be moved to the new component when the split is complete. 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-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title Jesse Glick commented on JENKINS-33596 Re: Disable DNSMultiCast & UDPBroadcastThread by default Keith Zantow is this really in progress? 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-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33596 Disable DNSMultiCast & UDPBroadcastThread by default Change By: Jesse Glick Labels: 2.0 community-bee split-plugins-from-core 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] [junit-attachments-plugin] (JENKINS-28784) junit-attachments plugin not compatible with Pipeline
Title: Message Title Andrew Bayer started work on JENKINS-28784 Change By: Andrew Bayer Status: Open In Progress 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] [credentials-plugin] (JENKINS-28407) Create Credentials through CLI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28407 Re: Create Credentials through CLI Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/da2b063c2eda791e36827c0a70fdb6ad4a8a4373 Log: JENKINS-28407 Findbugs! 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-35666) Regular 404s for running builds that get better after build is finished.
Title: Message Title Ben Clifford updated an issue Jenkins / JENKINS-35666 Regular 404s for running builds that get better after build is finished. Change By: Ben Clifford For some large (50%?) number of builds (across several projects): * The build starts.As expected: * build related URLs work ok. (for example, http://loris.beautifuldestinations.com:2000/job/beautilytics/branch/benc-typo/1/console provides a working progressive console. * The build appears in the LHS "build history" pane on the project page, as an in-progress build. * The build appears on the list of workers, as occupying a worker. * The build is correctly linked on github as an in-progress build.After running for several minutes , : * all build related URLs for that particular build start returning 404 (in the above url example , but everything beginning: http://loris.beautifuldestinations.com:2000/job/beautilytics/branch/benc-typo/1) * and the project page ceases to show this build as existing. It displays previously finished builds.However: * the list of workers still shows the build as occupying the worker (and provides a link which goes to the now 404-ing build page) , and * the build runs to completion successfully. * Build-related URLs for other builds still work ok at this point.After the build has run to completion, all of the build related URLs which started 404ing work again (for example the complete console output can be seen).A screenshot of progressive console output breaking part way due to this is attached - to be clear, this happens for all URLs related to the build, not just the progressive console.This has happened in all of the weekly releases that I've tried (three or four over the past two months); previous to that I was not using Jenkins on this codebase/machine. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [bitbucket-branch-source-plugin] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Mark Ottaviani commented on JENKINS-33507 Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications Is https://marketplace.atlassian.com/plugins/com.atlassian.stash.plugin.stash-web-post-receive-hooks-plugin/server/overview a viable option? 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] [gitlab-plugin] (JENKINS-34700) parameters are not "overwritten"
Title: Message Title Chris Russell edited a comment on JENKINS-34700 Re: parameters are not "overwritten" (edited for grammar)Why the shift to environment variables over parameters? I am interested in the motivation so that we can see if there is a way to meet that need and avoid the following issues:h3. This makes it much harder to create a Jenkins job which can be triggered by GitLab *or* by manual execution. *Before*, you simply defined the job with appropriate parameters, then filled them out in the case of a manual execution. *Now* you need to define parameters, then write a groovy script to conditionally overwrite environment variables. If you want to use defaults, this is even harder:1. Define parameters without defaults. 2. Write groovy script to write environment vars using the following order or precedence: Parameter if not empty; else environment if not empty; else defaultThis creates a tedious setup which is difficult to maintain across several projects. Such an implementation also hides defaults from the end user when they start the build. The only viable work-around to that is to write the defaults into the helper-text for each parameter. This means that if your defaults change, you must update the groovy script and the documentation , further adding to the maintenance cost.h3. This change makes it is much harder to now determine what the execution parameters of a specific build were. *Before*, you could just inspect the build parameters. The values which are relevant to the build operations are clearly visible. *Now*, you must sift through the very cluttered list of environment variables. All gitlab values show up in the environment list instead of just the ones which were used by the build; this further obfuscates the meaningful values. 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] [gitlab-plugin] (JENKINS-34700) parameters are not "overwritten"
Title: Message Title Chris Russell edited a comment on JENKINS-34700 Re: parameters are not "overwritten" (edited for grammar) Why the shift to environment variables over parameters? I am interested in the motivation so that we can see if there is a way to meet that need and avoid the following issues:h3. This makes it much harder to create a Jenkins job which can be triggered by GitLab *or* by manual execution. *Before*, you simply defined the job with appropriate parameters, then filled them out in the case of a manual execution. *Now* you need to define parameters, then write a groovy script to conditionally overwrite environment variables. If you want to use defaults, this is even harder:1. Define parameters without defaults. 2. Write groovy script to write environment vars using the following order or precedence: Parameter if not empty; else environment if not empty; else defaultThis creates a tedious setup which is difficult to maintain across several projects. Such an implementation also hides defaults from the end user when they start the build. The only viable work-around to that is to write the defaults into the helper-text for each parameter. This means that if your defaults change, you must update the groovy script and the documentation further adding to the maintenance cost.h3. This change makes it is much harder to now determine what the execution parameters of a specific build were. *Before*, you could just inspect the build parameters. The values which are relevant to the build operations are clearly visible. *Now*, you must sift through the very cluttered list of environment variables. Even if a All gitlab -value is irrelevant for the build operations it shows values show up in the environment list further obfuscating what was instead of just the ones which were used as by the build parameters ; this further obfuscates the meaningful values . 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] [workflow-plugin] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title Andrew Bayer commented on JENKINS-26535 Re: DescribableHelper does not handle wildcards well Jesse Glick - so does that mean we'd need to do something similar in junit to handle the TestDataPublisher use case? 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] [ec2-plugin] (JENKINS-35680) Implement an optional shutdown script parameter that runs before the slaves terminate
Title: Message Title Tristan Cole created an issue Jenkins / JENKINS-35680 Implement an optional shutdown script parameter that runs before the slaves terminate Issue Type: Improvement Assignee: Francis Upton Components: ec2-plugin Created: 2016/Jun/13 6:03 PM Priority: Trivial Reporter: Tristan Cole When running an ephemeral slave on EC2 via Jenkins, there's a possibility there may be things left on the slave (logs, artifacts, etc) that one may want to copy before the instance gets terminated. In my case, I have a monitoring tool that monitors every instance I bring up and would like to be able to make an API call and allow the Jenkins slave to remove itself at shutdown. If the instance were to go into disconnect/shutdown mode and then initiate that script before it is finally terminated, this would allow users to run any final cleanup tasks that are required (if any). Add Comment
[JIRA] [gitlab-plugin] (JENKINS-34700) parameters are not "overwritten"
Title: Message Title Chris Russell commented on JENKINS-34700 Re: parameters are not "overwritten" Why the shift to environment variables over parameters? I am interested in the motivation so that we can see if there is a way to meet that need and avoid the following issues: This makes it much harder to create a Jenkins job which can be triggered by GitLab or by manual execution. Before, you simply defined the job with appropriate parameters, then filled them out in the case of a manual execution. Now you need to define parameters, then write a groovy script to conditionally overwrite environment variables. If you want to use defaults, this is even harder: 1. Define parameters without defaults. 2. Write groovy script to write environment vars using the following order or precedence: Parameter if not empty; else environment if not empty; else default This creates a tedious setup which is difficult to maintain across several projects. Such an implementation also hides defaults from the end user when they start the build. The only viable work-around to that is to write the defaults into the helper-text for each parameter. This means that if your defaults change, you must update the groovy script and the documentation further adding to the maintenance cost. This change makes it is much harder to now determine what the execution parameters of a specific build were. Before, you could just inspect the build parameters. The values which are relevant to the build operations are clearly visible. Now, you must sift through the very cluttered list of environment variables. Even if a gitlab-value is irrelevant for the build operations it shows up in the list further obfuscating what was used as build parameters. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-35666) Regular 404s for running builds that get better after build is finished.
Title: Message Title Ben Clifford updated an issue Jenkins / JENKINS-35666 Regular 404s for running builds that get better after build is finished. Change By: Ben Clifford Summary: Regular 404s for running jobs builds that get better after job build is finished. 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-35666) Regular 404s for running jobs that get better after job is finished.
Title: Message Title Ben Clifford commented on JENKINS-35666 Re: Regular 404s for running jobs that get better after job is finished. updated 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-35666) Regular 404s for running jobs that get better after job is finished.
Title: Message Title Ben Clifford updated an issue Jenkins / JENKINS-35666 Regular 404s for running jobs that get better after job is finished. Change By: Ben Clifford For some large (50%?) number of build jobs builds (across several projects) : * The job build starts. As expected: * Job build related URLs work ok. (for example, http://loris.beautifuldestinations.com:2000/job/beautilytics/branch/benc-typo/1/console /job/beautilytics/branch/benc-typo/1/console provides a working progressive console. * The job build appears in the LHS "build history" pane on the project page, as an in-progress job build . * The job build appears on the list of workers, as occupying a worker. * The job build is correctly linked on github as an in-progress job build .After running for several minutes, all job build related URLs for that particular build start returning 404, but the list of workers still shows the job build as occupying the worker (and provides a link which goes to the now 404-ing build page) , and the job build runs to completion successfully. Build-related URLs for other builds still work ok at this point. After the job build has run to completion, all of the job build related URLs which started 404ing work again (for example the complete console output can be seen).A screenshot of progressive console output breaking part way due to this is attached - to be clear, this happens for all URLs related to the job build , not just the progressive console.This has happened in all of the weekly releases that I've tried (three or four over the past two months); previous to that I was not using Jenkins on this project codebase/machine . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-12017) Seriously slow rendering/loading times for the job/foo/configure page
Title: Message Title Daniel Beck edited a comment on JENKINS-12017 Re: Seriously slow rendering/loading times for the job/foo/configure page This issue isn't actionable, and it's its age means comments may even be unrelated to each other. *Please do not reopen, file a new issue instead*.In the case of long loading times, https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump usually helps identify the issue. 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-35666) Regular 404s for running jobs that get better after job is finished.
Title: Message Title Daniel Beck commented on JENKINS-35666 Re: Regular 404s for running jobs that get better after job is finished. Project/Job is the thing you configure. Run/Build is the thing that has a start time and duration. I'm pretty sure at least some uses of "job" in the issue description should be "build", but it's not clear whether it's all of them. 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-12017) Seriously slow rendering/loading times for the job/foo/configure page
Title: Message Title Daniel Beck resolved as Not A Defect This issue isn't actionable, and it's age means comments may even be unrelated to each other. Please do not reopen, file a new issue instead. In the case of long loading times, https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump usually helps identify the issue. Jenkins / JENKINS-12017 Seriously slow rendering/loading times for the job/foo/configure page Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect 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-35425) Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet
Title: Message Title Daniel Beck assigned an issue to Eyal Ben Moshe HAP-699 strikes again. Jenkins / JENKINS-35425 Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet Change By: Daniel Beck Component/s: artifactory-plugin Component/s: core Assignee: Eyal Ben Moshe 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-35425) Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet
Title: Message Title Daniel Beck commented on JENKINS-35425 Re: Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet This looks like the usual Artifactory plugin issue with not declaring dependencies correctly: https://www.jfrog.com/jira/browse/HAP-699 Originally, it was mostly Gradle Plugin, but since 2.x no longer installs Maven Integration Plugin by default, it seems this is another facet of this bug. 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] [ghprb-plugin] (JENKINS-35658) Re-built plugin does not work: webhook - No valid crumb
Title: Message Title Jens Elkner closed an issue as Fixed JDK related Jenkins / JENKINS-35658 Re-built plugin does not work: webhook - No valid crumb Change By: Jens Elkner Status: Open Closed 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] [ghprb-plugin] (JENKINS-35658) Re-built plugin does not work: webhook - No valid crumb
Title: Message Title Jens Elkner commented on JENKINS-35658 Re: Re-built plugin does not work: webhook - No valid crumb Hmmm, switching from JDK 1.8.0_77-b03 to 1.8.0_92-b14 seems to solve the problem - really strange. 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] [github-branch-source-plugin] (JENKINS-33161) Allow merge commits to be built from origin PRs
Title: Message Title Bill Hamilton commented on JENKINS-33161 Re: Allow merge commits to be built from origin PRs The original description of this seems to mix the issues at hand. One issue is that origin PRs should be allowed, via an option. The second issue, completely unrelated, is that any PR (from remote or origin) should expose options to build either or both of HEAD and MERGE. 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] [bitbucket-oauth-plugin] (JENKINS-35678) Unlimited number of exceptions when login.
Title: Message Title Ahmed AbouZaid closed an issue as Not A Defect Jenkins / JENKINS-35678 Unlimited number of exceptions when login. Change By: Ahmed AbouZaid Status: Open Closed Assignee: Ahmed AbouZaid Resolution: Not A Defect 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] [bitbucket-oauth-plugin] (JENKINS-35678) Unlimited number of exceptions when login.
Title: Message Title Ahmed AbouZaid commented on JENKINS-35678 Re: Unlimited number of exceptions when login. OK, the problem isn't in bitbucket oauth plugin, it's actually in version 2.3.0 of Role-based Authorization Strategy plugin. After update from 2.2.0 to 2.3.0, only admins (bitbucket admins) could login to Jenkins using bitbucket-oauth. Thanks. 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] [junit-attachments-plugin] (JENKINS-28784) junit-attachments plugin not compatible with Pipeline
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Renamed the JIRA, assigned it to me - I don't know about the wildcard errors, but I do know the other compatibility errors, so I'll work on that. Jenkins / JENKINS-28784 junit-attachments plugin not compatible with Pipeline Change By: Andrew Bayer Summary: JUnitResultArchiver testDataPublishers junit-attachments plugin not compatible with Workflow Pipeline Component/s: junit-attachments-plugin Component/s: junit-plugin Assignee: Jesse Glick Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [deploy-plugin] (JENKINS-35214) Unable to deploy the ear file using weblogic-deployer-plugin
Title: Message Title Brian Wu edited a comment on JENKINS-35214 Re: Unable to deploy the ear file using weblogic-deployer-plugin Hi [~raphc]I found that there's nothing in weblogic.jar, instead, the weblogic.Deployer.class is located in weblogic-classess.jar. I then switch from weblogic.jar to weblogic-classess.jar. However, some other class classes is missing again when I try to trigger the deployment (see below deployment logs). seems weblogic jars are always missing relative dependencies, do you happen to know how to solve this issue?*FYI*: I'm deploying my application to Weblogic 12c. TASK EXECUTION Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/utils/Debug at weblogic.Deployer.(Deployer.java:24)Caused by: java.lang.ClassNotFoundException: weblogic.utils.Debug at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 1 more 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] [deploy-plugin] (JENKINS-35214) Unable to deploy the ear file using weblogic-deployer-plugin
Title: Message Title Brian Wu edited a comment on JENKINS-35214 Re: Unable to deploy the ear file using weblogic-deployer-plugin Hi [~raphc]I found that there's nothing in weblogic.jar, instead, the weblogic.Deployer.class is located in weblogic-classess.jar. I then switch from weblogic.jar to weblogic-classess.jar. However, some other classes is are missing again when I try to trigger the deployment (see below deployment logs). seems weblogic jars are always missing relative dependencies, do you happen to know how to solve this issue?*FYI*: I'm deploying my application to Weblogic 12c. TASK EXECUTION Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/utils/Debug at weblogic.Deployer.(Deployer.java:24)Caused by: java.lang.ClassNotFoundException: weblogic.utils.Debug at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 1 more 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] [git-parameter-plugin] (JENKINS-15235) Trailing space in Git branch name causes build failures
Title: Message Title aflat commented on JENKINS-15235 Re: Trailing space in Git branch name causes build failures Looks like a regression, this popped up again. Should I create a new bug, or shoudl this one be re-opened? git plugin: 2.4.4 git client plugin: 1.19.6 jenkins: 2.6 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Luis Silva edited a comment on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials Faced this same issue today with this plugin today .Configuring ECR in us-east-1 region ( ***.dkr.ecr.us-east-1.amazonaws.com/*** ) the push succeeds.But using ECR in eu-west-1 ( ***.dkr.ecr.eu-west-1.amazonaws.com/*** ) it fails: with an error:error parsing HTTP 403 response body: unexpected end of JSON input: ""Build step 'Docker Build and Publish' marked build as failureIt's the exact same job and settings, only changing the registry endpoint in the job.Using the command line to issue a push with the token obtained by the jenkins job (set in ~/.docker/config.json) also fails, but using the aws cli to get the token, issuing a docker login and then push works fine regardless of the region.That leads to me to believe the problem is somewhere in the token / credentials issue code as you mentioned.Any ETA on the fix for this problem?Docker version 1.11.1, build 5604cbe/1.11.1Amazon ECR plugin: 1.3CloudBees Docker Build and Publish plugin: 1.2.2Docker Commons Plugin: 1.3.1 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Luis Silva commented on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials Faced this same issue today with this plugin today. Configuring ECR in us-east-1 region ( **.dkr.ecr.us-east-1.amazonaws.com/** ) the push succeeds. But using ECR in eu-west-1 ( **.dkr.ecr.eu-west-1.amazonaws.com/** ) it fails: with an error: error parsing HTTP 403 response body: unexpected end of JSON input: "" Build step 'Docker Build and Publish' marked build as failure It's the exact same job and settings, only changing the registry endpoint in the job. Using the command line to issue a push with the token obtained by the jenkins job (set in ~/.docker/config.json) also fails, but using the aws cli to get the token, issuing a docker login and then push works fine regardless of the region. That leads to me to believe the problem is somewhere in the token / credentials issue code as you mentioned. Any ETA on the fix for this problem? Docker version 1.11.1, build 5604cbe/1.11.1 Amazon ECR plugin: 1.3 CloudBees Docker Build and Publish plugin: 1.2.2 Docker Commons Plugin: 1.3.1 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-35425) Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet
Title: Message Title Guy Pascarella commented on JENKINS-35425 Re: Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet Installing the Maven Integration Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Maven+Project+Plugin) resolved all stack traces when trying to create a Freestyle project 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] [drupal-developer-plugin] (JENKINS-35544) coder review
Title: Message Title Feng Tan commented on JENKINS-35544 Re: coder review Which version of Drupal do you use ? What is the full output of drush --yes --nocolor --root=/var/lib/jenkins/workspace/Drupal/src pm-list --pipe --format=json --type=module ? 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] [external-workspace-manager-plugin] (JENKINS-35281) Implement the exwsAllocate step for the downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35281 Re: Implement the exwsAllocate step for the downstream job Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/steps/model/ExternalWorkspace.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/8adc8cf60bca987b9377c063a3a24d2f9b597dd0 Log: JENKINS-35281 Store String instead of UUID object. 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] [ec2-plugin] (JENKINS-35679) EC2-plugin not provisioning new slaves if slaves of same template but different label exist
Title: Message Title Jeff Gaston created an issue Jenkins / JENKINS-35679 EC2-plugin not provisioning new slaves if slaves of same template but different label exist Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Jun/13 4:12 PM Priority: Minor Reporter: Jeff Gaston Our Jenkins has several pools (SlaveTemplates) of servers that are scaled up and down by the EC2 plugin. Different jobs generate different state (including downloading Maven dependencies or deploying to Tomcat) that could be recreated on other servers but that take more time to recreate from scratch. So, we have a separate SlaveTemplate for each job. Each SlaveTemplate generally generates slaves having one label and each job only runs on slaves of a specific label. The AMI required by each job is the same, however. As a result, if one job has finished all of its work and another job is backlogged, then there may be an idle slave with label A having AMI ami-1, and still be a need for another slave with label B having AMI ami-1. If the system reaches this state, then the EC2 plugin doesn't provision more slaves, thinking that the need for more slaves of label B is really just a request for another slave of ami-1, which then can be satisfied by the existing idle slave of label A (this behavior is accompanied by messages in the logs saying "true - Node has capacity - can use it"). Then the job that only runs on slaves of label B doesn't have a new server on which to run, and remains backlogged. I've made a pull request at https://github.com/jenkinsci/ec2-plugin/pull/201 , which addresses
[JIRA] [core] (JENKINS-35425) Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet
Title: Message Title Oleg Nenashev commented on JENKINS-35425 Re: Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet Reassigning it to the core. I suspect there is a 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-35425) Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-35425 Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet Change By: Oleg Nenashev Component/s: core Component/s: _unsorted 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-35425) Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-35425 Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet Change By: Oleg Nenashev Assignee: Oleg Nenashev 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] [_unsorted] (JENKINS-35425) Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet
Title: Message Title Guy Pascarella commented on JENKINS-35425 Re: Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet Oleg Nenashev, will try that. just verified it's a problem in 2.7 also. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.7.jar!/hudson/model/Job/configure.jelly:59:58: hudson/maven/MavenModuleSet at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) 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 org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at
[JIRA] [coverity-plugin] (JENKINS-15143) deadlock - waiting on java.util.concurrent.Semaphore$NonfairSync@3b252642
Title: Message Title Ronny Schuetz edited a comment on JENKINS-15143 Re: deadlock - waiting on java.util.concurrent.Semaphore$NonfairSync@3b252642 This issue is still present with Jenkins 1.596.2 and Coverity Plugin 1.50 when Jenkins installs / updates for example a JDK.Thread-dump extract:"Executor #0 for PROJECT : executing PROJECT.trunk #1439" Id=92 Group=main WAITING on java.util.concurrent.Semaphore$NonfairSync@ff51826 at sun.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.Semaphore$NonfairSync@ff51826 at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) at java.util.concurrent.Semaphore.acquire(Semaphore.java:317) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:66) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:205) at hudson.model.JDK.forNode(JDK.java:130) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:351) at jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:78) at hudson.Launcher.decorateFor(Launcher.java:682) at hudson.model.Slave.createLauncher(Slave.java:362) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:141) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:205) at hudson.model.JDK.forNode(JDK.java:130) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:351) at jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:78) at hudson.Launcher.decorateFor(Launcher.java:682) at hudson.model.Slave.createLauncher(Slave.java:362) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:576) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:491) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)If this deadlock happens, the workaround for now is to manually kill the Jenkins (slave), disable the Coverity plugin and restart, re-run the job to install the JDK and finally enable the Coverity plugin and restart again ... Or install the JDK manually and configure it in Node Properties / Tools locations. Add Comment
[JIRA] [bitbucket-oauth-plugin] (JENKINS-35678) Unlimited number of exceptions when login.
Title: Message Title Ahmed AbouZaid created an issue Jenkins / JENKINS-35678 Unlimited number of exceptions when login. Issue Type: Bug Assignee: Unassigned Attachments: bitbucket-oauth-0.5-erros.txt Components: bitbucket-oauth-plugin Created: 2016/Jun/13 4:04 PM Environment: Jenkins: 2.7 Installation: apt Tomcat: No Proxy: Yes - Nginx Java: 8 oracle (1.8.0_91) Bitbucket OAuth: 0.5 System: Ubuntu 14.04.4 Prevent Cross Site Request Forgery exploits: On/Off (same result) Tested on multiple browsers. Labels: plugin Priority: Blocker Reporter: Ahmed AbouZaid Hello, After upgrade to Jenkins 2.7 Bitbucket OAuth 0.5 (and 0.4 too) started to through unlimited number of exceptions in log
[JIRA] [publish-over-ssh-plugin] (JENKINS-35231) Prime size must be multiple of 64 error after upgrading Publish-over-SSH from 1.13 to 1.14
Title: Message Title
Peter Marcoen updated an issue
Jenkins / JENKINS-35231
Prime size must be multiple of 64 error after upgrading Publish-over-SSH from 1.13 to 1.14
Change By:
Peter Marcoen
When upgrading Publish-over-SSH from v1.13 to v1.14, I all of a sudden get the following error when using "Send build artifacts over SSH":{quote}ERROR: Exception when publishing, exception message [Failed to connect session for config [my-server-name]. Message [Session.connect: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)]]{quote}I have configured this SSH server with user root, remote directory '/' and password authentication without a key.When I google this error I only get responses regarding the programming of SSH clients, no mention of a misconfiguration of some kind.
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] [build-timeout-plugin] (JENKINS-35677) build-timeout-plugin cannot be used with pipelines (workflows)
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-35677 build-timeout-plugin cannot be used with pipelines (workflows) Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: build-timeout-plugin Created: 2016/Jun/13 3:52 PM Priority: Major Reporter: Sorin Sbarnea It seems that the build-timeout plugin cannot be used in Jenkins pipelines and we would really want to be able to use it. While the pipelines do have the `timeout()` command this has a different behaviour which sets a fixed timeout, not one that can vary based on the existence or not of output on the build. Also it would be extremely useful to update the plugin homepage (wiki) in order to document its relationship with the timeout() from pipelines. Add Comment
[JIRA] [_unsorted] (JENKINS-35425) Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet
Title: Message Title Oleg Nenashev commented on JENKINS-35425 Re: Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet In any case Maven Project Plugin installation is the best available workaround 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] [amazon-ecs-plugin] (JENKINS-33196) Add g2.8xlarge to the list of instance types
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33196 Re: Add g2.8xlarge to the list of instance types Code changed in jenkins User: Nate Gallaher Path: pom.xml http://jenkins-ci.org/commit/aws-java-sdk-plugin/2a55e13b9c892f3028ff964b48612c544eb40c11 Log: Update aws-java-sdk to 1.10.50. In pursuit of closing: JENKINS-33196 - Add g2.8xlarge to the list of instance types JENKINS-32600 - Move to 1.10.49 version of AWS SDK 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] [aws-java-sdk-plugin] (JENKINS-32600) Move to 1.10.49 version of AWS SDK
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32600 Re: Move to 1.10.49 version of AWS SDK Code changed in jenkins User: Nate Gallaher Path: pom.xml http://jenkins-ci.org/commit/aws-java-sdk-plugin/2a55e13b9c892f3028ff964b48612c544eb40c11 Log: Update aws-java-sdk to 1.10.50. In pursuit of closing: JENKINS-33196 - Add g2.8xlarge to the list of instance types JENKINS-32600 - Move to 1.10.49 version of AWS SDK 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] [credentials-plugin] (JENKINS-28407) Create Credentials through CLI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28407 Re: Create Credentials through CLI Code changed in jenkins User: Stephen Connolly Path: src/test/java/com/cloudbees/plugins/credentials/cli/CLICommandsTest.java http://jenkins-ci.org/commit/credentials-plugin/2c01a29dc7b8fc736c5d2288fd284d54d2868b63 Log: JENKINS-28407 Add a test case for the create flow 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] [bitbucket-branch-source-plugin] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Nenad Miksa commented on JENKINS-33507 Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications We actually have solved this way: we created a webhook on BitBucket which every time there is a push to repository or pull request is created or updated, it calls this URL: http://jenkins.server/job/MyPipelineJob/build MyPipelineJob is multibranch pipeline job which only enumerates changes in pull requests and feature branches and triggers builds if necessary. However, we are missing Build status badges from BitBucket BuildStatus API. 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] [external-workspace-manager-plugin] (JENKINS-35281) Implement the exwsAllocate step for the downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35281 Re: Implement the exwsAllocate step for the downstream job Code changed in jenkins User: Alexandru Somai Path: pom.xml src/main/java/org/jenkinsci/plugins/ewm/actions/ExwsAllocateActionImpl.java src/main/java/org/jenkinsci/plugins/ewm/actions/ExwsAllocateActionWrapper.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/model/ExternalWorkspace.java src/main/resources/org/jenkinsci/plugins/ewm/Messages.properties src/main/resources/org/jenkinsci/plugins/ewm/actions/ExwsAllocateActionImpl/index.jelly src/main/resources/org/jenkinsci/plugins/ewm/actions/ExwsAllocateActionWrapper/index.jelly http://jenkins-ci.org/commit/external-workspace-manager-plugin/b7715b3178a48407701b992bf6f00d6c85a564ae Log: JENKINS-35281 Additional improvements. Error message enhancement. Remove unused dependencies 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] [_unsorted] (JENKINS-35425) Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet
Title: Message Title Guy Pascarella commented on JENKINS-35425 Re: Can't create job. NoClassDefFoundError: hudson/maven/MavenModuleSet I just experienced this also. Upgraded from Jenkins 2.7 to 2.8 on CentOS7 via yum. I had not tried to create a Freestyle project in 2.7 so have no idea if it worked then. I do have a lot of plugin churn since we are evaluating Jenkins and not using it in production. I do not have the error about a broken reverse proxy. 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] [credentials-plugin] (JENKINS-28407) Create Credentials through CLI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28407 Re: Create Credentials through CLI Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/cli/CreateCredentialsByXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/CreateCredentialsDomainByXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/DeleteCredentialsDomainCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/GetCredentialsDomainAsXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/ListCredentialsCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/ListCredentialsContextResolversCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/ListCredentialsProvidersCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/UpdateCredentialsByXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/UpdateCredentialsDomainByXmlCommand.java http://jenkins-ci.org/commit/credentials-plugin/396e9c3f66b4c469cb4218a5a346a706fec152cb Log: JENKINS-28407 Reformat code 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] [credentials-plugin] (JENKINS-28407) Create Credentials through CLI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28407 Re: Create Credentials through CLI Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/cli/CreateCredentialsByXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/CreateCredentialsDomainByXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/DeleteCredentialsCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/DeleteCredentialsDomainCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/GetCredentialsAsXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/GetCredentialsDomainAsXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/ListCredentialsCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/ListCredentialsContextResolversCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/ListCredentialsProvidersCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/UpdateCredentialsByXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/UpdateCredentialsDomainByXmlCommand.java src/main/resources/com/cloudbees/plugins/credentials/cli/Messages.properties http://jenkins-ci.org/commit/credentials-plugin/ac2e0700b55aea43df359676944ea83285e404c7 Log: JENKINS-28407 i18n all the things 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] [performance-signature-dynatrace-plugin] (JENKINS-35539) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Title: Message Title Raphael Pionke commented on JENKINS-35539 Re: Upgrade to Credentials 2.1.0+ API for populating credentials drop-down https://github.com/jenkinsci/performance-signature-dynatrace-plugin/pull/3 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] [credentials-plugin] (JENKINS-28407) Create Credentials through CLI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28407 Re: Create Credentials through CLI Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsStoreAction.java src/main/java/com/cloudbees/plugins/credentials/cli/BaseCredentialsCLICommand.java src/main/java/com/cloudbees/plugins/credentials/cli/CreateCredentialsByXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/CreateCredentialsDomainByXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/DeleteCredentialsCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/DeleteCredentialsDomainCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/GetCredentialsAsXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/GetCredentialsDomainAsXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/ListCredentialsCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/ListCredentialsContextResolversCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/ListCredentialsProvidersCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/UpdateCredentialsByXmlCommand.java src/main/java/com/cloudbees/plugins/credentials/cli/UpdateCredentialsDomainByXmlCommand.java http://jenkins-ci.org/commit/credentials-plugin/3497ffc9aa5bab9ae1fd43690ab55b22a2c45d31 Log: JENKINS-28407 Let's add the APIs CRUD for credentials (read retains secrets redacted) CRUD for credentials domains 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
[JIRA] [coverity-plugin] (JENKINS-15143) deadlock - waiting on java.util.concurrent.Semaphore$NonfairSync@3b252642
Title: Message Title Ronny Schuetz commented on JENKINS-15143 Re: deadlock - waiting on java.util.concurrent.Semaphore$NonfairSync@3b252642 Any update on this issue? 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.
