[JIRA] [core] (JENKINS-30039) Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked
Title: Message Title Magnus Jacobsson reopened an issue Happened again after upgrade to Jenkins ver. 1.626. Jenkins / JENKINS-30039 Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked Change By: Magnus Jacobsson Resolution: Cannot Reproduce Status: Resolved Reopened 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl commented on JENKINS-30200 Re: Nullpointer exception while connecting to a docker container provide full description of issue --> Upgrade Jenkins ver. 1.626 Docker plugin version: 0.12.1 Plugin started producing the mentioned error. check Manage Jenkins -> Manage Old Data for not updated configuraiton and provide this info --> "No old data was found." provide full list of installed plugins with versions, jenkins core version --> Please see PluginsInstalled Attachment. check and provide errors from system jenkins.log and errors from Manage Jenkins -> System Log --> Already added to the bug when reporting. provide Cloud section from $JENKINS_HOME/config.xml file --> the cloud section contains a lot of images. I am attaching partially in "clouds_section_config.xml". describe how your docker infrastructure looks like --> 2 docker servers, around 84 containers. The docker servers and Jenkins are all separate Virtual machines. --> The jobs are all sequential, running one container at a time. provide docker host/api version --> Tried two docker versions 1.6.1 and 1.8.1 provide steps for reproducing --> Just create a node with the mentioned configuration and jenkins and docker version as written before. Run a job. The run fails. any code or log example surround with right markdown https://help.github.com/articles/github-flavored-markdown/ --> configuration and logs already attached. 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Ashish Behl updated an issue Jenkins / JENKINS-30200 Nullpointer exception while connecting to a docker container Change By: Ashish Behl Attachment: PluginsInstalled Attachment: clouds_section_config.xml 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-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title Kanstantsin Shautsou commented on JENKINS-30223 Re: Migrator for Credential.java is failing As i see elasticbox plugin invented parts of ghprb-plugin and github-plugins. Github plugin need to be reviewed whether it can provide gh connection as fixed 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] [core] (JENKINS-28440) Allow to reject specific configurations via REST and CLI
Title: Message Title dogfood commented on JENKINS-28440 Re: Allow to reject specific configurations via REST and CLI Integrated in jenkins_main_trunk #4273 JENKINS-28440 Added @since for CriticalXStreamException. (Revision d6f9c5cdde8b80a40d3ce65f716099621c0ae9ce) JENKINS-28440 Uses CLICommandInvoker in tests. (Revision 0d54d89a367e5b3de3bde6fcc590ba6bedbfa82e) Result = SUCCESS devld : d6f9c5cdde8b80a40d3ce65f716099621c0ae9ce Files : core/src/main/java/jenkins/util/xstream/CriticalXStreamException.java devld : 0d54d89a367e5b3de3bde6fcc590ba6bedbfa82e Files : test/src/test/java/hudson/util/RobustReflectionConverterTest.java 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-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title Ignacio Fuertes commented on JENKINS-30223 Re: Migrator for Credential.java is failing We use to connect to the gihub and manage PR events to manage the lifecycle of pull requests 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] [rundeck-plugin] (JENKINS-29395) Jenkins doesn't trigger rundeck when failing
Title: Message Title andy gao commented on JENKINS-29395 Re: Jenkins doesn't trigger rundeck when failing Hi Marcin, Thanks for the replay. I have fixed problem by removing the "check status" in the code of the 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] [mail-watcher-plugin] (JENKINS-30220) NullPointerException when running groovy CLI without setting the offline cause
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30220 NullPointerException when running groovy CLI without setting the offline cause 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] [mail-watcher-plugin] (JENKINS-30220) NullPointerException when running groovy CLI without setting the offline cause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30220 Re: NullPointerException when running groovy CLI without setting the offline cause Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkinsci/plugins/mailwatcher/NodeStatusTest.java http://jenkins-ci.org/commit/mail-watcher-plugin/49b98e258d7ebe65d2073dbd88d67463ad451d78 Log: [FIXED JENKINS-30220] Add UnitTest: validate whether a particular computer when is offline it fails if the cause is null 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] [mail-watcher-plugin] (JENKINS-30220) NullPointerException when running groovy CLI without setting the offline cause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30220 Re: NullPointerException when running groovy CLI without setting the offline cause Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkinsci/plugins/mailwatcher/NodeStatusTest.java http://jenkins-ci.org/commit/mail-watcher-plugin/53ddf572cbafd2ff7e57bce2ced3b97008b0794b Log: Merge pull request #1 from v1v/nullcauseTestCase [FIXED JENKINS-30220] Add UnitTest: validate null Causes 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] [mail-watcher-plugin] (JENKINS-30220) NullPointerException when running groovy CLI without setting the offline cause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30220 Re: NullPointerException when running groovy CLI without setting the offline cause Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkinsci/plugins/mailwatcher/WatcherComputerListener.java http://jenkins-ci.org/commit/mail-watcher-plugin/2505935ae40b2cb06f6568319c8532a1b2718c89 Log: Avoid nullpointexception when cause is null since you can bypass validations as long as you use groovy api JENKINS-30220 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-30210) Allow Git checkout into absolute path
Title: Message Title Alexey Pakseykin commented on JENKINS-30210 Re: Allow Git checkout into absolute path Mark Waite, thank you for the suggested workaround! Just for documentation purposes: JENKINS-13576 explains how to access it for different job types. Although "Use custom workspace" feature is inconsistent, it will do the trick. I also want to note that in this case it is up to the individual job type plugin to control the location of the workspace. And on a separate note, there are cases (like deploying some configuration/script files on the system through Multi SCM + Git * N) when simply supporting absolute path by Git would be more straightforward than creating multiple jobs pointing to these absolute paths instead. It's not my case, but this may well be a candidate feature for future releases. 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-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title Kirill Merkushev commented on JENKINS-30223 Re: Migrator for Credential.java is failing is it ok if i send you pr with fix? 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] [multijob-plugin] (JENKINS-30226) MultiJob getting "stuck" after all child jobs complete
Title: Message Title Robert Schultheis created an issue Jenkins / JENKINS-30226 MultiJob getting "stuck" after all child jobs complete Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 31/Aug/15 3:10 PM Priority: Major Reporter: Robert Schultheis We have been experiencing an issue lately wherein our MultiJobs run, all the subjobs complete (and pass), and it gets "stuck". The multijob fails to complete, and it does not respond to manual halt requests. The only way to unstick it we've found is to restart jenkins. Reproduction I've setup a simplified generic example to reproduce it: One multijob named "parent_job" parent_job has one build phase build phase has 10 identical subjobs: subjob_1 - subjob_10 Each subjob merely runs this simple script: echo "start" sleep 3 echo "done"
[JIRA] [github-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title Ignacio Fuertes commented on JENKINS-30223 Re: Migrator for Credential.java is failing yes, it's ok 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] [versionnumber-plugin] (JENKINS-30224) NPE thrown when a job uses an automatically installed JDK
Title: Message Title
Yoann Dubreuil updated an issue
Jenkins / JENKINS-30224
NPE thrown when a job uses an automatically installed JDK
Change By:
Yoann Dubreuil
When a job is using an automatically installed JDK and when the JDK is not available yet on build node, this NPE is thrown:{code}ERROR: java.lang.NullPointerExceptionjava.lang.NullPointerException at hudson.Launcher$ProcStarter.stdout(Launcher.java:262) at hudson.tools.AbstractCommandInstaller.performInstallation(AbstractCommandInstaller.java:77) 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:355) at hudson.model.Run.getEnvironment(Run.java:2228) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:932) at org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.getPreviousBuildWithVersionNumber(VersionNumberBuilder.java:204) at org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.incBuild(VersionNumberBuilder.java:242) at org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.setUp(VersionNumberBuilder.java:497) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381){code}Plugin is calling {{build.getEnvironment(null)}} [here|https://github.com/jenkinsci/versionnumber-plugin/blob/master/src/main/java/org/jvnet/hudson/tools/versionnumber/VersionNumberBuilder.java#L204] which is not . Passing {{null }} doesn't seem to be legal.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [versionnumber-plugin] (JENKINS-30224) NPE thrown when a job uses an automatically installed JDK
Title: Message Title
Yoann Dubreuil updated an issue
Jenkins / JENKINS-30224
NPE thrown when a job uses an automatically installed JDK
Change By:
Yoann Dubreuil
When a job is using an automatically installed JDK and when the JDK is not available yet on build node, this NPE is thrown:{code}ERROR: java.lang.NullPointerExceptionjava.lang.NullPointerException at hudson.Launcher$ProcStarter.stdout(Launcher.java:262) at hudson.tools.AbstractCommandInstaller.performInstallation(AbstractCommandInstaller.java:77) 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:355) at hudson.model.Run.getEnvironment(Run.java:2228) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:932) at org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.getPreviousBuildWithVersionNumber(VersionNumberBuilder.java:204) at org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.incBuild(VersionNumberBuilder.java:242) at org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.setUp(VersionNumberBuilder.java:497) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381){code}Plugin is calling {{build.getEnvironment(null)}} [here|https://github.com/jenkinsci/versionnumber-plugin/blob/master/src/main/java/org/jvnet/hudson/tools/versionnumber/VersionNumberBuilder.java#L204]. Passing {{null }} doesn't seem to be legal.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [vsphere-cloud-plugin] (JENKINS-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave
Title: Message Title Kevin Smith updated an issue Jenkins / JENKINS-30203 When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution Change By: Kevin Smith Summary: Jobs When there are more jobs assigned to a cloud slave (once provisioned) but than the cloud will only be able to computer can handle a sub-set of those job. The , then the cloud should be able to provision a new slave (s) to handle the remaining jobs needing execution 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] [sonargraph-plugin] (JENKINS-29187) Specified Sonargraph system file is not used and generated report is not processed
Title: Message Title Andreas Hoyer assigned an issue to Andreas Hoyer Jenkins / JENKINS-29187 Specified Sonargraph system file is not used and generated report is not processed Change By: Andreas Hoyer Assignee: Ingmar Kellner Andreas Hoyer 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] [sonargraph-plugin] (JENKINS-29187) Specified Sonargraph system file is not used and generated report is not processed
Title: Message Title Andreas Hoyer started work on JENKINS-29187 Change By: Andreas Hoyer 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] [job-dsl-plugin] (JENKINS-29972) Unable to use custom SCM plugin Extension Point
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-29972 Unable to use custom SCM plugin Extension Point Change By: Daniel Spilker Attachment: job-dsl.hpi 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-29972) Unable to use custom SCM plugin Extension Point
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-29972 Unable to use custom SCM plugin Extension Point Change By: Daniel Spilker Attachment: job-dsl.hpi 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-29972) Unable to use custom SCM plugin Extension Point
Title: Message Title Daniel Spilker commented on JENKINS-29972 Re: Unable to use custom SCM plugin Extension Point I attached a new HPI file. Can you test again? 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-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title Kirill Merkushev commented on JENKINS-30223 Re: Migrator for Credential.java is failing will restore removed class and create fix in a few hours 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-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title Ignacio Fuertes commented on JENKINS-30223 Re: Migrator for Credential.java is failing Sounds great! 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] [workflow-plugin] (JENKINS-30206) Multibranch plugin does not pass parameters as expected
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30206 Re: Multibranch plugin does not pass parameters as expected Code changed in jenkins User: Jesse Glick Path: multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowParameterDefinitionBranchPropertyTest.java http://jenkins-ci.org/commit/workflow-plugin/b19985d062703304ba317a8f82743187469a4f27 Log: JENKINS-30206 WorkflowParameterDefinitionBranchProperty working fine from a test at least. 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] [workflow-plugin] (JENKINS-30206) Multibranch plugin does not pass parameters as expected
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30206 Re: Multibranch plugin does not pass parameters as expected Code changed in jenkins User: Jesse Glick Path: multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowParameterDefinitionBranchPropertyTest.java http://jenkins-ci.org/commit/workflow-plugin/2c148f146a8f8cf5c4bde9bf70978d6cc3983e8c Log: Merge pull request #199 from jglick/multibranch-param- JENKINS-30206 JENKINS-30206 Testing WorkflowParameterDefinitionBranchProperty more Compare: https://github.com/jenkinsci/workflow-plugin/compare/cc3469c132f0...2c148f146a8f 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.
Ваш электронный идентификатор выиграл $ 1,000,000.00 USD от объединенной премии национального
-- 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-collector-plugin] (JENKINS-30125) Add Workflow compatibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30125 Re: Add Workflow compatibility Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_collector/AnalysisCollectorPluginArea.java http://jenkins-ci.org/commit/acceptance-test-harness/afe63af83f2de2d76e598a564c541427b15edb3a Log: Merge pull request #37 from amuniz/JENKINS-30125 JENKINS-30125 Fix properties IDs on Analysis Collector Plugin Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/2b43bc002cd0...afe63af83f2d 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-plugin] (JENKINS-27378) Build when a change is pushed to GitHub so follow Use SCM from another project
Title: Message Title Jay Rutten commented on JENKINS-27378 Re: Build when a change is pushed to GitHub so follow Use SCM from another project Just FYI, this has decreased in importance for us as we have greatly simplified our jobs and removed this dependency. 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] [logging-plugin] (JENKINS-30227) login error
Title: Message Title raju kethi created an issue Jenkins / JENKINS-30227 login error Issue Type: Bug Assignee: Praqma Support Components: logging-plugin, security Created: 31/Aug/15 5:00 PM Labels: configuration Priority: Critical Reporter: raju kethi HTTP ERROR 404 Problem accessing /j_acegi_security_check. Reason: Not Found Powered by Jetty:// Add Comment
[JIRA] [youtrack-plugin] (JENKINS-30216) YouTrack plugin doesn't perform actions on issues
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30216 Re: YouTrack plugin doesn't perform actions on issues Code changed in jenkins User: Konstantin Gribov Path: src/main/java/org/jenkinsci/plugins/youtrack/YoutrackIssueUpdater.java http://jenkins-ci.org/commit/youtrack-plugin/6e4c241c42c0ec4ffc12be1c336b351f9f730add Log: Make ChangeLogSet.Entry iterator copy Fixes #JENKINS-30216 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-plugin] (JENKINS-21906) NumberFormatException occurs when accessing the JSON api
Title: Message Title Kirill Geizerov reopened an issue Git plugin: 2.4.0 Jnk: 1.609 Python api fails on function get_last_build() with status 500 Or when I try to send request http://localhost/job/playout_release-0.9.4/67/api/python?depth=1 I keep getting: Stack trace java.io.IOException: Failed to write timestamp at org.kohsuke.stapler.export.Property.writeTo(Property.java:122) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:172) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeTo(Model.java:164) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doPython(Api.java:222) at sun.reflect.GeneratedMethodAccessor217.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at
[JIRA] [git-plugin] (JENKINS-21906) NumberFormatException occurs when accessing the JSON api
Title: Message Title
Kirill Geizerov edited a comment on JENKINS-21906
Re: NumberFormatException occurs when accessing the JSON api
Git plugin: 2.4.0Jnk: 1.609Python api fails on function get_last_build() with status 500Or when I try to send request {noformat}http://localhost/job/ playout_release-0.9.4 job_name /67/api/python?depth=1{noformat}I keep getting:*Stack trace*{code:java}java.io.IOException: Failed to write timestamp at org.kohsuke.stapler.export.Property.writeTo(Property.java:122) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:172) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeTo(Model.java:164) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doPython(Api.java:222) at sun.reflect.GeneratedMethodAccessor217.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Title: Message Title Dennis Schulte commented on JENKINS-21750 Re: Promoted Builds Plugin Steve Jansen That would be ok for me. Who is going to decide that? In this case I need to release the job-dsl-promotions-plugin separately, right? 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] [p4-plugin] (JENKINS-25242) p4-plugin: Doesn't do concurrent builds
Title: Message Title Paul Allen commented on JENKINS-25242 Re: p4-plugin: Doesn't do concurrent builds Hi David, how did you change the '@' separator to '-'? In Perforce the '@' token is reserved for change list or label specifiers e.g. //some/path/...@12345 or //some/path/...@label Glad to hear that concurrent builds works with '-'. I might have to add some automatic remapping of the '@' or at least find out how the Perforce plugin gets around 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] [xcode-plugin] (JENKINS-30228) [xcode-plugin] Custom xcodebuild arguments should be textarea to make use easier
Title: Message Title Timothy Rundle created an issue Jenkins / JENKINS-30228 [xcode-plugin] Custom xcodebuild arguments should be textarea to make use easier Issue Type: Improvement Assignee: Unassigned Components: xcode-plugin Created: 31/Aug/15 6:08 PM Priority: Minor Reporter: Timothy Rundle Currently the "Custom xcodebuild arguments" field is a single line text box. After adding a couple arguments this get difficult to manage. If the field was switched to a textarea the usability would be greatly improved. The underlying code would not be impacted as the field value is already parsed using QuotedStringTokenizer, which supports new lines Add Comment
[JIRA] [core] (JENKINS-30229) Dashboard Padding CSS issues with 1.626
Title: Message Title Kyle Martinez created an issue Jenkins / JENKINS-30229 Dashboard Padding CSS issues with 1.626 Issue Type: Bug Assignee: Unassigned Attachments: image1.png, image2.png Components: core Created: 31/Aug/15 6:47 PM Environment: Jenkins version 1.626 Priority: Minor Reporter: Kyle Martinez After upgrading jenkins to 1.626 there are dramatic padding issues with the tabBarContainer div. Add Comment
[JIRA] [vsphere-cloud-plugin] (JENKINS-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave
Title: Message Title Kevin Smith commented on JENKINS-30203 Re: When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution So, it seems, that given enough time and getting the slave to return false with canTake when the slave has accepted x number of jobs it is designed to handle, that the provisioning task will execute. Working Scenario: Job 1 set to run 10 minutes is requested to be built. Jenkins provisions Slave 1 Slave 1 comes on-line Slave 1's slave.jar (channel) connects Slave 1 accepts and runs Job 1 Job 2 set to run 1 minute is requested to be built. Jenkins sets Job 2 to be blocked on slave 1. X number of iterations where Jenkins asks Slave 1 if it canTake Job 2 (which I am now responding CauseOfBlockage.BecauseNodeIsOffline(this) for all BuildableItem(s) which the slave isn't looking to take) and slave 1 returns with a blockage message. JOB 1 IS STILL RUNNING Jenkins provisions Slave 2 Slave 2 comes online Slave 2's slave.jar (channel) connects Slave 2 accepts and runs Job 2 Job 2 finishes Slave 2 unprovisions Job 1 finishes Slave 1 unprovisions. So what I am looking for is a way to tell jenkins that the slave isn't going to accept that job in the near future (or at all) so that the provisioning can happen quicker. 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-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave
Title: Message Title Kevin Smith updated an issue Jenkins / JENKINS-30203 When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution Change By: Kevin Smith Issue Type: Bug New Feature Priority: Major Trivial SEE COMMENTS (Looking for a CauseOfBlockage that will cause Jenkins to automatically ask the cloud for a new machine or another slave to accept a job because the currently assigned slave will not be available for that job.) I am enhancing the vsphere-cloud-plugin to work with slave templates so that the vSphereCloud can provision new slaves. In my first release I am going to have a newly provisioned slave run the jobs until the limited run limit is reached (right now 1 job execution) then it will be unprovisioned. When only working with 1 job this works perfectly. When I introduce a 2nd job then the newly provisioned slave is created, job 1 of 2 is executed, the slave is unprovisioned, another slave is provisioned, job 2 of 2 is executed, and the slave is unprovisioned. What I am expecting to see here is when (and yes I would have to implement a method that would control this which I can't find or doesn't exist) job 2 comes in and 1) the computer (or slave) tells jenkins it cannot handle the job (I tried canTake and reported all types of CauseOfBlockage) and 2) the cloud tells jenkins it can provision. I am wondering what I can do here. I would like the availability to notify jenkins that a slave/computer can handle a newly launched job request (even amongst the jobs already waiting to be ran) Add Comment
[JIRA] [workflow-plugin] (JENKINS-30206) Multibranch plugin does not pass parameters as expected
Title: Message Title Branton Horsley commented on JENKINS-30206 Re: Multibranch plugin does not pass parameters as expected I think I found the problem. It appears that when you modify the properties of the root project, a new config.xml does not get generated for existing branches but will be generated for new branches. The original bug reported appears to be caused by 1) create multibranch workflow 2) check in branch (let's say 'feature/2') and notify Jenkins 3) modify multibranch workflow to add a parameter to 'feature/*' 4) check in feature/2 again 5) feature/2's config.xml (workflow-root/branches/feature%2F1/config.xml) remains as it was in step 2 If you then were to check in a new branch feature/3 (also matching feature/*), the config.xml generated for feature/2 correctly inherits the parameter, but feature/1 still will not Going through the above example results in the following configs: main config.xml "jenkins.branch.NamedExceptionsBranchPropertyStrategy"> "java.util.Arrays$ArrayList"> "jenkins.branch.BranchProperty-array"> "sorted-set"> ---snip--- "workflow-multibranch@1.9-beta-2"> RUN_TESTS true test_parameter SHOULD_EXIST "java.util.Arrays$ArrayList"> "jenkins.branch.NamedExceptionsBranchPropertyStrategy$Named-array"> ---snip--- development,master "java.util.Arrays$ArrayList"> "jenkins.branch.BranchProperty-array"> "workflow-multibranch@1.9-beta-2"> RUN_TESTS true SECOND_PROP feature/* exception for feature/*: add RUN_TESTS and SECOND_PROP. prior to this (in step 2 above the above workflow), only RUN_TESTS was defined 'feature/2's config.xml created *before* multibranch config change but pushed to after the config change "workflow-job@1.10-beta-1"> "workflow-multibranch@1.9-beta-2"> "branch-api@0.2-beta-4"> "scm-api@0.2"> feature/workflow-test-2 "java.util.concurrent.CopyOnWriteArrayList"> "workflow-multibranch@1.9-beta-2"> RUN_TESTS true "../../org.jenkinsci.plugins.workflow.multibranch.BranchJobProperty/branch/properties/org.jenkinsci.plugins.workflow.multibranch.WorkflowParameterDefinitionBranchProperty/parameterDefinitions"/> "org.jenkinsci.plugins.workflow.multibranch.SCMBinder" plugin="workflow-multibranch@1.9-beta-2"/> only RUN_TESTS defined
[JIRA] [workflow-plugin] (JENKINS-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title Branton Horsley updated an issue Jenkins / JENKINS-30206 Multibranch plugin: Modified properties do not propagate to existing branches Change By: Branton Horsley Summary: Multibranch plugin does : Modified properties do not pass parameters as expected propagate to existing branches 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] [workflow-plugin] (JENKINS-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title
Branton Horsley updated an issue
Jenkins / JENKINS-30206
Multibranch plugin: Modified properties do not propagate to existing branches
Change By:
Branton Horsley
*EDIT*: see https://issues.jenkins-ci.org/browse/JENKINS-30206?focusedCommentId=235736=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-235736 h5. Steps to reproduce:1. Create a multi-branch workflow project2. Select a git repository as a branch source3. Set property strategy to "named branches get different properties"4. Add a parameter property (as the default or as an exception that matches the branch you're building. both seem to not work) of a string or boolean with a set default value5. Run a branch that attempts to use that property6. Property does not appear to be accessible from Jenkinsfileh5. ExampleSet parameter property of 'test_parameter' with a default value!Selection_384.png|thumbnail!Attempt to use the parameter{code}def param = test_parameternode("nodejs && swarm") { checkout scm println(param)...{code}this exception gets thrown when the script is being executed.{code}groovy.lang.MissingPropertyException: No such property: test_parameter for class: groovy.lang.Binding{code}I've tried accessing* boolean and string parameters* As properties of the 'env' object or directly (The current tutorial for the workflow-plugin suggests that parameters are exported as variables in the global scope)And I can't seem to get it to work in any instance
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message
[JIRA] [workflow-plugin] (JENKINS-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title Jesse Glick reopened an issue I see. Will try to reproduce when I get a chance. Jenkins / JENKINS-30206 Multibranch plugin: Modified properties do not propagate to existing branches Change By: Jesse Glick Resolution: Cannot Reproduce Status: Resolved Reopened 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] [workflow-plugin] (JENKINS-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30206 Multibranch plugin: Modified properties do not propagate to existing branches Change By: Jesse Glick Labels: 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] [embeddable-build-status-plugin] (JENKINS-29750) ClassCastException on a workflow job
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29750 ClassCastException on a workflow job Change By: Jesse Glick Summary: ClassCastException ona on a workflow job 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] [embeddable-build-status-plugin] (JENKINS-29750) ClassCastException ona workflow job
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29750 ClassCastException ona workflow job Change By: Jesse Glick 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] [embeddable-build-status-plugin] (JENKINS-29750) ClassCastException ona workflow job
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29750 ClassCastException ona workflow job 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] [timestamper-plugin] (JENKINS-30143) logs for individual workflow steps do not contain timestamps
Title: Message Title Jesse Glick commented on JENKINS-30143 Re: logs for individual workflow steps do not contain timestamps you will see timestamps for the echo step but not the SCM checkout For a script stored in SCM, the checkout happens before you run the wrap step. if you view the logs for the individual step then the output is shown without any timestamps Please check this again, it should be amending the log of the individual step, so long as it is within wrap. 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] [timestamper-plugin] (JENKINS-30142) timestamped logs not available in all workflow logs.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30142 timestamped logs not available in all workflow logs. Only possible with a custom Workflow step. SimpleBuildWrapper can only work inside node due to its assumption that the wrapper needs a workspace and associated APIs. Change By: Jesse Glick Issue Type: Improvement New Feature Component/s: workflow-plugin 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
[JIRA] [workflow-plugin] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Title: Message Title Jesse Glick resolved as Won't Fix unarchive has been deprecated in 1.10 in favor of stash/unstash, which internally use a .tar.gz file that ought to preserve file atttributes. Jenkins / JENKINS-26659 file permissions aren't protected after archive/unarchive Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix 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] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-26010 Workflow plugin not working with with Gerrit event Change By: SCM/JIRA link daemon Status: In Progress 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] [git-plugin] (JENKINS-27352) Git SCM polling is not triggered from a push notification with a parametrized branchspec
Title: Message Title pmv commented on JENKINS-27352 Re: Git SCM polling is not triggered from a push notification with a parametrized branchspec We updated to 1.609.2 on 08/25, so we've been running with it about a week. We still have git client 1.18.0 and git 2.4.0, and have not seen an increase in the number of triggered builds missing parameters (in fact, I don't think we've seen any since the upgrade). 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] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26010 Re: Workflow plugin not working with with Gerrit event Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/39a20897632ab295c8b394b9f7cb8f114a4f7b26 Log: [FIXED JENKINS-26010] Noting release. 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] [nodejs-plugin] (JENKINS-29980) Make NodeJS compatible with Workflow
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29980 Make NodeJS compatible with Workflow Change By: SCM/JIRA link daemon Status: In Progress 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] [nodejs-plugin] (JENKINS-29980) Make NodeJS compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29980 Re: Make NodeJS compatible with Workflow Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/401be6e31bc529040f0ae5706cc5a56b98eb53f0 Log: [FIXED JENKINS-29980] Noting fix. 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] [parameterized-trigger-plugin] (JENKINS-26050) Workflow integration for Parameterized Trigger
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26050 Re: Workflow integration for Parameterized Trigger Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/ad0ae293d06a22284930bf6bb4f7096b2f357771 Log: JENKINS-26050 Noting release. 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] [docker-workflow-plugin] (JENKINS-26178) Ability to run docker-exec etc. from a workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26178 Re: Ability to run docker-exec etc. from a workflow Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/6361ce7597b9579aa5725e614193b47d82fc7b90 Log: JENKINS-26178 docker-workflow plugin is where people would more likely go for this feature. 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] [mock-slave-plugin] (JENKINS-25090) Mock slaves should use a consistent remoteFS after restart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25090 Re: Mock slaves should use a consistent remoteFS after restart Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/44d46b1b8703e2d399a67f4b8414d93aff8c277b Log: JENKINS-25090 Noting release. 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-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title Kirill Merkushev commented on JENKINS-30223 Re: Migrator for Credential.java is failing https://github.com/jenkinsci/github-plugin/pull/79 https://github.com/jenkinsci/elasticbox-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] [github-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30223 Migrator for Credential.java is failing 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] [github-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30223 Re: Migrator for Credential.java is failing Code changed in jenkins User: Kirill Merkushev Path: src/main/java/com/cloudbees/jenkins/Credential.java src/main/java/com/cloudbees/jenkins/GitHubPushTrigger.java src/main/java/org/jenkinsci/plugins/github/config/GitHubServerConfig.java src/main/java/org/jenkinsci/plugins/github/deprecated/Credential.java src/main/java/org/jenkinsci/plugins/github/migration/Migrator.java src/test/java/org/jenkinsci/plugins/github/migration/MigratorTest.java http://jenkins-ci.org/commit/github-plugin/061d849cd41f079a205656afa4d3583fce821351 Log: [FIXES JENKINS-30223] return back com.cloudbees.jenkins.Credential as of it makes fail to boot jenkins after installation of plugin which depends on this class. Also remove migration to another package for this class and use it directly 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-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30223 Re: Migrator for Credential.java is failing Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/com/cloudbees/jenkins/Credential.java src/main/java/com/cloudbees/jenkins/GitHubPushTrigger.java src/main/java/org/jenkinsci/plugins/github/config/GitHubServerConfig.java src/main/java/org/jenkinsci/plugins/github/deprecated/Credential.java src/main/java/org/jenkinsci/plugins/github/migration/Migrator.java src/test/java/org/jenkinsci/plugins/github/migration/MigratorTest.java http://jenkins-ci.org/commit/github-plugin/36241308ca565289e93a4ed1ec706b7a25d6176b Log: Merge pull request #79 from lanwen/restore_creds [FIXES JENKINS-30223] return back com.cloudbees.jenkins.Credential Compare: https://github.com/jenkinsci/github-plugin/compare/a726907597da...36241308ca56 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] [multijob-plugin] (JENKINS-30230) URL rendering error with folder list views
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-30230 URL rendering error with folder list views Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2015-08-31 at 2.53.08 PM.png Components: multijob-plugin Created: 31/Aug/15 9:57 PM Priority: Major Reporter: Mark Austin Tested on 1.16... 1. Create a multi-job build in a list view 2. Create a job in a folder and set it as one of the phases of the multi-job build and save 3. Now when viewing the multi-job page, if you click on the reference to the job in the folder, the URL points to a non-existent page Notice that the job folder is being completely ignored. Add Comment
[JIRA] [multijob-plugin] (JENKINS-30230) URL rendering error with folder list views
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30230 URL rendering error with folder list views Change By: Jesse Glick Labels: folders 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] [multijob-plugin] (JENKINS-30230) URL rendering error with folder list views
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-30230 URL rendering error with folder list views Change By: Mark Austin Attachment: Screen Shot 2015-08-31 at 2.37.44 PM.png 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] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26186 Re: Last Build Trigger Column does not print author name Code changed in jenkins User: Baptiste Mathus Path: src/main/java/org/jenkinsci/plugins/buildtriggerbadge/LastBuildTriggerColumn.java src/main/resources/org/jenkinsci/plugins/buildtriggerbadge/LastBuildTriggerColumn/column.jelly src/main/resources/org/jenkinsci/plugins/buildtriggerbadge/LastBuildTriggerColumn/config.jelly http://jenkins-ci.org/commit/buildtriggerbadge-plugin/0d0fdb4b22b1bccafb262d82ef88a35fe6537200 Log: Merge pull request #15 from jenkinsci/trigger-column-configurable-display JENKINS-26186 Enable changing display format for Last Build Trigger Column Compare: https://github.com/jenkinsci/buildtriggerbadge-plugin/compare/40ac15121da4...0d0fdb4b22b1 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-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25977 Re: Make publishers of analysis-core a SimpleBuildStep Code changed in jenkins User: Antonio Muñiz Path: src/main/java/hudson/plugins/analysis/core/PluginDescriptor.java src/main/java/hudson/plugins/analysis/core/ReporterDescriptor.java src/main/resources/util/thresholds.jelly http://jenkins-ci.org/commit/analysis-core-plugin/0cd83845f41b03a47cc98edc844d6ca19311d357 Log: JENKINS-25977 Overriding newInstance in plugin descriptor is a bad practice (moreover, it does not work with Workflow snippet generator) 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-collector-plugin] (JENKINS-30125) Add Workflow compatibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30125 Re: Add Workflow compatibility Code changed in jenkins User: Antonio Muñiz Path: pom.xml src/test/java/hudson/plugins/analysis/collector/workflow/WorkflowCompatibilityTest.java src/test/resources/findbugs-native.xml http://jenkins-ci.org/commit/analysis-collector-plugin/d914ff770701b564c8c6df7503d3f79d6026fa75 Log: JENKINS-30125 Add workflow related tests 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-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25977 Re: Make publishers of analysis-core a SimpleBuildStep Code changed in jenkins User: Antonio Muñiz Path: src/main/java/hudson/plugins/analysis/core/PluginDescriptor.java http://jenkins-ci.org/commit/analysis-core-plugin/af6407e174db26f076bacf9433dd65447e5c9afe Log: JENKINS-25977 Mark JSON adapt method as deprecated 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] [dry-plugin] (JENKINS-30103) Make DRY Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30103 Re: Make DRY Plugin compatible with Workflow Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/plugins/dry/DryPublisher.java src/main/java/hudson/plugins/dry/DryReporterResult.java src/main/java/hudson/plugins/dry/DryResult.java src/main/java/hudson/plugins/dry/DryResultAction.java src/test/java/hudson/plugins/dry/DryWorkflowTest.java http://jenkins-ci.org/commit/dry-plugin/b62aa1033dd9f2a5221066b57faed3edcf5120d7 Log: JENKINS-30103 Deprecated methods have been removed. Asked by @uhafner 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] [dry-plugin] (JENKINS-30103) Make DRY Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30103 Re: Make DRY Plugin compatible with Workflow Code changed in jenkins User: Manuel Recena Path: pom.xml src/test/resources/hudson/plugins/dry/maven-project1.zip http://jenkins-ci.org/commit/dry-plugin/667bf236138f18847ec821a5644b1dea5829b527 Log: JENKINS-30103 The maven-project1.zip has been simplified to spend less time in the build process 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] [findbugs-plugin] (JENKINS-29601) Make Findbugs Plugin usable in Workflow jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29601 Re: Make Findbugs Plugin usable in Workflow jobs Code changed in jenkins User: Antonio Muñiz Path: plugin/pom.xml http://jenkins-ci.org/commit/findbugs-plugin/21ca1ce0c10a8d92f3dbab52d7999f479824088c Log: JENKINS-29601 Upgrade parent pom 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] [dry-plugin] (JENKINS-30103) Make DRY Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30103 Re: Make DRY Plugin compatible with Workflow Code changed in jenkins User: recena Path: .gitignore pom.xml http://jenkins-ci.org/commit/dry-plugin/1f4efa8b5e19f8fcf6402c0f5a9ef8a2fc7b66bd Log: JENKINS-30103 Removed unnecessary dependencies. Inherited from analysis-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] [dry-plugin] (JENKINS-30103) Make DRY Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30103 Re: Make DRY Plugin compatible with Workflow Code changed in jenkins User: recena Path: src/test/java/hudson/plugins/dry/DryWorkflowTest.java http://jenkins-ci.org/commit/dry-plugin/fa5a0c4bf1b78ff7ed35c8bfbcd1c6eda07d503f Log: JENKINS-30103 @jglick recommened to use ThisClass.class.getResourceAsStream(..) instead of getClass().getResourceAsStream(..) 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] [dry-plugin] (JENKINS-30103) Make DRY Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30103 Re: Make DRY Plugin compatible with Workflow Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/plugins/dry/DryPublisher.java src/main/java/hudson/plugins/dry/DryReporterResult.java src/test/java/hudson/plugins/dry/DryWorkflowTest.java http://jenkins-ci.org/commit/dry-plugin/0f8c4d35c5b2a87e6b3a0fbb7aedbef51c2211f5 Log: JENKINS-30103 @jglick's comments have been reviewed 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-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25977 Re: Make publishers of analysis-core a SimpleBuildStep Code changed in jenkins User: Antonio Muñiz Path: src/main/java/hudson/plugins/analysis/core/AbstractResultAction.java src/main/java/hudson/plugins/analysis/core/BuildHistory.java src/main/java/hudson/plugins/analysis/core/BuildResult.java src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java src/main/java/hudson/plugins/analysis/views/AbstractAnnotationsDetail.java src/main/java/hudson/plugins/analysis/views/AttributeDetail.java src/main/java/hudson/plugins/analysis/views/ConsoleDetail.java src/main/java/hudson/plugins/analysis/views/ErrorDetail.java src/main/java/hudson/plugins/analysis/views/FileDetail.java src/main/java/hudson/plugins/analysis/views/FixedWarningsDetail.java src/main/java/hudson/plugins/analysis/views/ModuleDetail.java src/main/java/hudson/plugins/analysis/views/NewWarningsDetail.java src/main/java/hudson/plugins/analysis/views/PackageDetail.java src/main/java/hudson/plugins/analysis/views/PrioritiesDetail.java src/main/java/hudson/plugins/analysis/views/SourceDetail.java src/main/java/hudson/plugins/analysis/views/TabDetail.java http://jenkins-ci.org/commit/analysis-core-plugin/6ba2b6520802373297ffcff443f0ff4c0feceefb Log: JENKINS-25977 Keep backward compatibility 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] [findbugs-plugin] (JENKINS-29601) Make Findbugs Plugin usable in Workflow jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29601 Re: Make Findbugs Plugin usable in Workflow jobs Code changed in jenkins User: Antonio Muñiz Path: plugin/pom.xml plugin/src/test/java/hudson/plugins/findbugs/workflow/WorkflowCompatibilityTest.java http://jenkins-ci.org/commit/findbugs-plugin/c45e9c05936cb775ee36a8b1dd063fe2e9978895 Log: JENKINS-29601 New functional tests 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-collector-plugin] (JENKINS-30125) Add Workflow compatibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30125 Re: Add Workflow compatibility Code changed in jenkins User: Antonio Muñiz Path: pom.xml src/main/java/hudson/plugins/analysis/collector/AnalysisPublisher.java src/main/java/hudson/plugins/analysis/collector/AnalysisResult.java src/main/java/hudson/plugins/analysis/collector/AnalysisResultAction.java http://jenkins-ci.org/commit/analysis-collector-plugin/be519ab023b6f69812da9bd0ea3fb6a1ab44e81c Log: JENKINS-30125 Initial interfacing changes 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] [dry-plugin] (JENKINS-30103) Make DRY Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30103 Re: Make DRY Plugin compatible with Workflow Code changed in jenkins User: recena Path: .gitignore pom.xml src/main/java/hudson/plugins/dry/DryPublisher.java src/main/java/hudson/plugins/dry/DryReporterResult.java src/main/java/hudson/plugins/dry/DryResult.java src/main/java/hudson/plugins/dry/DryResultAction.java src/test/java/hudson/plugins/dry/DryWorkflowTest.java http://jenkins-ci.org/commit/dry-plugin/d6d0924c9b66168291670959bcf8a69d4c3046f0 Log: JENKINS-30103 Initial source code modificatio ns 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-collector-plugin] (JENKINS-30125) Add Workflow compatibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30125 Re: Add Workflow compatibility Code changed in jenkins User: Antonio Muñiz Path: src/main/java/hudson/plugins/analysis/collector/AnalysisPublisher.java src/main/java/hudson/plugins/analysis/collector/AnalysisResult.java src/main/java/hudson/plugins/analysis/collector/AnalysisResultAction.java http://jenkins-ci.org/commit/analysis-collector-plugin/9ca75f8f3e7e33b15a5d717d590d600293d8e367 Log: JENKINS-30125 Remove deprecated signatures 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-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25977 Re: Make publishers of analysis-core a SimpleBuildStep Code changed in jenkins User: Antonio Muñiz Path: .gitignore pom.xml src/main/java/hudson/plugins/analysis/core/AbstractResultAction.java src/main/java/hudson/plugins/analysis/core/AnnotationsClassifier.java src/main/java/hudson/plugins/analysis/core/BuildHistory.java src/main/java/hudson/plugins/analysis/core/BuildResult.java src/main/java/hudson/plugins/analysis/core/FilesParser.java src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java src/main/java/hudson/plugins/analysis/core/HealthAwareRecorder.java src/main/java/hudson/plugins/analysis/core/HealthAwareReporter.java src/main/java/hudson/plugins/analysis/core/MavenResultAction.java src/main/java/hudson/plugins/analysis/core/PluginDescriptor.java src/main/java/hudson/plugins/analysis/core/ResultAction.java src/main/java/hudson/plugins/analysis/graph/CategoryBuildResultGraph.java src/main/java/hudson/plugins/analysis/util/FileFinder.java src/main/java/hudson/plugins/analysis/util/model/AbstractAnnotation.java src/main/java/hudson/plugins/analysis/util/model/FileAnnotation.java src/main/java/hudson/plugins/analysis/views/AbstractAnnotationsDetail.java src/main/java/hudson/plugins/analysis/views/AttributeDetail.java src/main/java/hudson/plugins/analysis/views/ConsoleDetail.java src/main/java/hudson/plugins/analysis/views/DetailFactory.java src/main/java/hudson/plugins/analysis/views/ErrorDetail.java src/main/java/hudson/plugins/analysis/views/FileDetail.java src/main/java/hudson/plugins/analysis/views/FixedWarningsDetail.java src/main/java/hudson/plugins/analysis/views/ModuleDetail.java src/main/java/hudson/plugins/analysis/views/NewWarningsDetail.java src/main/java/hudson/plugins/analysis/views/PackageDetail.java src/main/java/hudson/plugins/analysis/views/PrioritiesDetail.java src/main/java/hudson/plugins/analysis/views/PriorityDetailFactory.java src/main/java/hudson/plugins/analysis/views/SourceDetail.java src/main/java/hudson/plugins/analysis/views/TabDetail.java http://jenkins-ci.org/commit/analysis-core-plugin/fa14ef16af4e991d536f8716dfe81e834fb5b094 Log: JENKINS-25977 Initial changes for workflow compatibility Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [findbugs-plugin] (JENKINS-29601) Make Findbugs Plugin usable in Workflow jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29601 Re: Make Findbugs Plugin usable in Workflow jobs Code changed in jenkins User: Antonio Muñiz Path: plugin/src/main/java/hudson/plugins/findbugs/FindBugsPublisher.java http://jenkins-ci.org/commit/findbugs-plugin/299ce1fabfe018e77faa71b717f89f758aa50404 Log: JENKINS-29601 Adapt to upstream changes 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-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25977 Re: Make publishers of analysis-core a SimpleBuildStep Code changed in jenkins User: Antonio Muñiz Path: src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java http://jenkins-ci.org/commit/analysis-core-plugin/5ef6f26ab29cba4251a718289226e1d10b4fbabe Log: JENKINS-25977 Backward compatibility 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] [dry-plugin] (JENKINS-30103) Make DRY Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30103 Re: Make DRY Plugin compatible with Workflow Code changed in jenkins User: Manuel Recena Path: pom.xml src/test/java/hudson/plugins/dry/DryWorkflowTest.java src/test/resources/hudson/plugins/dry/maven-project1.zip src/test/resources/hudson/plugins/dry/parser/cpd/cpd-2warnings.xml http://jenkins-ci.org/commit/dry-plugin/0277ea79aacc1f31091efe5011d151191de25094 Log: JENKINS-30103 Tests have been reviewed 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] [checkstyle-plugin] (JENKINS-29648) Make Checkstyle Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29648 Re: Make Checkstyle Plugin compatible with Workflow Code changed in jenkins User: Manuel Recena Path: .gitignore pom.xml src/main/java/hudson/plugins/checkstyle/CheckStylePublisher.java src/main/java/hudson/plugins/checkstyle/CheckStyleReporterResult.java src/main/java/hudson/plugins/checkstyle/CheckStyleResult.java src/main/java/hudson/plugins/checkstyle/CheckStyleResultAction.java src/test/java/hudson/plugins/checkstyle/CheckstyleWorkflowTest.java http://jenkins-ci.org/commit/checkstyle-plugin/b2de9b3a03228a539022fae0f4b143f8125b6d24 Log: JENKINS-29648 Workflow compatible. Added new tests (workflow specific) 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] [warnings-plugin] (JENKINS-29959) Make Warnings Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29959 Re: Make Warnings Plugin compatible with Workflow Code changed in jenkins User: Manuel Recena Path: .gitignore pom.xml src/main/java/hudson/plugins/warnings/AggregatedWarningsResult.java src/main/java/hudson/plugins/warnings/AggregatedWarningsResultAction.java src/main/java/hudson/plugins/warnings/WarningsBuildHistory.java src/main/java/hudson/plugins/warnings/WarningsPublisher.java src/main/java/hudson/plugins/warnings/WarningsResult.java src/main/java/hudson/plugins/warnings/WarningsResultAction.java src/main/java/hudson/plugins/warnings/parser/ParserRegistry.java src/test/java/hudson/plugins/warnings/WarningsWorkflowTest.java http://jenkins-ci.org/commit/warnings-plugin/ee546a8f9de5dab58925e883c413d34659519696 Log: JENKINS-29959 Workflow compatible. Added new tests (workflow specific) 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] [dry-plugin] (JENKINS-30103) Make DRY Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30103 Re: Make DRY Plugin compatible with Workflow Code changed in jenkins User: recena Path: .gitignore pom.xml src/main/java/hudson/plugins/dry/DryPublisher.java src/main/java/hudson/plugins/dry/DryReporterResult.java src/main/java/hudson/plugins/dry/DryResult.java src/main/java/hudson/plugins/dry/DryResultAction.java src/test/java/hudson/plugins/dry/DryWorkflowTest.java src/test/resources/hudson/plugins/dry/parser/cpd/cpd-2warnings.xml http://jenkins-ci.org/commit/dry-plugin/b3a3fc1f2b8138429cf2ada0bd5438c3941b4b43 Log: JENKINS-30103 Tests have been reviewed 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-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25977 Re: Make publishers of analysis-core a SimpleBuildStep Code changed in jenkins User: Antonio Muñiz Path: src/main/java/hudson/plugins/analysis/core/AbstractHealthDescriptor.java src/main/java/hudson/plugins/analysis/graph/CategoryBuildResultGraph.java src/main/java/hudson/plugins/analysis/graph/GraphConfiguration.java src/main/java/hudson/plugins/analysis/graph/GraphConfigurationView.java src/main/resources/hudson/plugins/analysis/graph/GraphConfigurationView/index.jelly src/main/resources/hudson/plugins/analysis/graph/GraphConfigurationView/index.properties src/test/java/hudson/plugins/analysis/graph/GraphConfigurationTest.java http://jenkins-ci.org/commit/analysis-core-plugin/7a28211202aedfcfc4fa22473d635e96f8231a53 Log: Merge upstream branch 'master' into JENKINS-25977-workflow-compat Conflicts: src/main/java/hudson/plugins/analysis/graph/CategoryBuildResultGraph.java 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] [pmd-plugin] (JENKINS-29844) Make PMD Plugin compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29844 Re: Make PMD Plugin compatible with Workflow Code changed in jenkins User: recena Path: .gitignore pom.xml src/main/java/hudson/plugins/pmd/PmdPublisher.java src/main/java/hudson/plugins/pmd/PmdReporterResult.java src/main/java/hudson/plugins/pmd/PmdResult.java src/main/java/hudson/plugins/pmd/PmdResultAction.java src/test/java/hudson/plugins/pmd/PmdWorkflowTest.java http://jenkins-ci.org/commit/pmd-plugin/6a25c52a1348cfcad96acfabe5af4eb4c579d3ad Log: JENKINS-29844 Workflow compatible. Added new tests (workflow specific) 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] [findbugs-plugin] (JENKINS-29601) Make Findbugs Plugin usable in Workflow jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29601 Re: Make Findbugs Plugin usable in Workflow jobs Code changed in jenkins User: Antonio Muñiz Path: plugin/pom.xml plugin/src/main/java/hudson/plugins/findbugs/FindBugsDescriptor.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsDetailFactory.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsPublisher.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporterResult.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsResult.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsResultAction.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsTabDetail.java http://jenkins-ci.org/commit/findbugs-plugin/43582cd9d3b457e512798af77242d2fd8de67a74 Log: JENKINS-29601 Initial changes to make the plugin compatible with Workflow jobs 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] [tasks-plugin] (JENKINS-29704) Tasks Scanner Plugin workflow compatibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29704 Re: Tasks Scanner Plugin workflow compatibility Code changed in jenkins User: Antonio Muñiz Path: pom.xml src/main/java/hudson/plugins/tasks/TasksPublisher.java src/main/java/hudson/plugins/tasks/TasksReporterResult.java src/main/java/hudson/plugins/tasks/TasksResult.java src/main/java/hudson/plugins/tasks/TasksResultAction.java src/main/java/hudson/plugins/tasks/parser/WorkspaceScanner.java src/test/java/hudson/plugins/tasks/workflow/WorkflowCompatibilityTest.java http://jenkins-ci.org/commit/tasks-plugin/a709ab3c53f4f38e070f2ddbdf91c6b9cb505543 Log: JENKINS-29704 Adding workflow compatibility 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-oauth-plugin] (JENKINS-28319) GitHub OAuth client secret is stored in config as plain text
Title: Message Title
Sam Gleske commented on JENKINS-28319
Re: GitHub OAuth client secret is stored in config as plain text
It should be encrypted using hudson.util.Secret. Here's a Jenkins Script Console code snippet describing behavior of hudson.util.Secret.
import hudson.util.Secret
Secret secret = new Secret("hello")
String encrypted_text = secret.getEncryptedValue()
println "Plain text is: ${secret}"
println "Encrypted text is: ${encrypted_text}"
//create a new secret as if it was loaded from configuration XML
Secret new_secret = Secret.fromString(encrypted_text)
println "${new_secret} world"
Secret.fromString() is used by the credentials 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] [warnings-plugin] (JENKINS-26113) REST api needed to get individual warnings values, not combined ones
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-26113 REST api needed to get individual warnings values, not combined ones Change By: Ulli Hafner 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] [dry-plugin] (JENKINS-30103) Make DRY Plugin compatible with Workflow
Title: Message Title Manuel Jesús Recena Soto resolved as Fixed Jenkins / JENKINS-30103 Make DRY Plugin compatible with Workflow Change By: Manuel Jesús Recena Soto Status: In Progress 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] [nodejs-plugin] (JENKINS-30218) User Agent Containing JAVA doesn't download NodeJS package.
Title: Message Title Cristian Marquez Russo closed an issue as Not A Defect This is not a defect from Jenkins/NodeJS plugin side. This was a NodeJS.org issue. https://github.com/nodejs/node-v0.x-archive/issues/25912 Now is resolved. Workaround: add -Dhttp.agent='not java' to the JENKINS_ARGS var and restart jenkins Jenkins / JENKINS-30218 User Agent Containing JAVA doesn't download NodeJS package. Change By: Cristian Marquez Russo Status: Open Closed Assignee: Cristian Marquez Russo Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-21906) NumberFormatException occurs when accessing the JSON api
Title: Message Title Mark Waite resolved as Fixed Kirill Geizerov your report is not a NumberFormatException, so it should not be reported under this NumberFormatException bug. You've found JENKINS-29857 . You're running Java 6 and the code uses a Java 7 argument to SimpleDateFormat. Per the blog posting "Goodbye Java 6", the Jenkins project is moving towards dropping support for Java 6. You have several alternatives. You could: Switch your Java virtual machine from Java 6 to Java 7 or Java 8 Wait for the next release of the git plugin which includes a work around for the problem Test a [pre-release buildhttps://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/912/org.jenkins-ci.plugins$git/artifact/org.jenkins-ci.plugins/git/2.4.1-SNAPSHOT/git-2.4.1-SNAPSHOT.hpi|] of the git plugin which already contains the fix Since Oracle stopped shipping fixes for Java 6 a few years ago, and the Jenkins project already has plans to drop support for Java 6, you may want to upgrade to Java 8 whether or not you take any of the other alternatives. Jenkins / JENKINS-21906 NumberFormatException occurs when accessing the JSON api Change By: Mark Waite Status: Reopened Resolved Resolution: Fixed Add Comment
[JIRA] [core] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-30231 Build creates second workspace@2 for non-concurrent build configuration Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, matrix-project-plugin Created: 31/Aug/15 11:54 PM Environment: OS: Ubuntu 12.04 64-bit Jenkins: 1.609.1 (upgraded from 1.580.3) disk-usage plugin: 0.25 (upgraded from 0.24) Matrix Project Plugin: 1.6 (upgraded from 1.4.1) Priority: Minor Reporter: Rick Liu I didn't have this issue when I was using ver 1.580.3. After upgrading Jenkins ver 1.609.1 (together with other Jenkins plugins update), I started to see this issue. My jenkins job is using multi-config project type (aka Matrix project), and has 3 variants. I didn't set to be run concurrently, so the 3 variants will start the build one by one. In the previous version 1.580.3, it will reuse the same workspace folder for all of 3 variant builds. In the new version 1.609.1, when multiple jobs are triggerd, I can see sometimes the first variant build of the second job will start to create and use workspace@2 instead of re-using original worksapce. Note: I'm also using disk-usage plugin. At the end of build, it will trigger that plugin to calculate
[JIRA] [core] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Rick Liu commented on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration Per comment from Jesse Glick, I create this separate issue which has similar symptom. 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] [p4-plugin] (JENKINS-30232) p4-plugin creates p4 connection on both master and slave during checkout
Title: Message Title stuart rowe created an issue Jenkins / JENKINS-30232 p4-plugin creates p4 connection on both master and slave during checkout Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 31/Aug/15 11:55 PM Priority: Critical Reporter: stuart rowe During SCM checkout, the p4-plugin creates a p4 connection on both the master and the slave. The user specified credential should not be expected to work on both the master and the slave - only on the node where the associated job is intended to run. One example is a Jenkins master running on Linux and a Jenkins slave running on Windows. The job is configured to use a file based p4 tickets credential hosted on a windows network share. The Jenkins master would be unable to access that network share when specificed as \\path\to\network\share\p4tickets.txt. Add Comment
