[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-27739 Changes to slave environment variables are ignored by master Change By: Daniel Beck Assignee: DanielBeck 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-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
Title: Message Title Jesse Glick resolved as Fixed Fixed in 1.8. Jenkins / JENKINS-26900 Hide flyweight master executor when ≥1 heavyweight executors running as subtasks Change By: Jesse Glick Status: InProgress 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] [workflow-plugin] (JENKINS-28604) Parallel step will create 2nd executor on single-executor slaves
Title: Message Title A C commented on JENKINS-28604 Re: Parallel step will create 2nd executor on single-executor slaves Workflow 1.7 has made this problem worse. Now whenever a slave fails a long running process, Workflow tries to run all the queued parallel builds at once when the node is freed, and generates a new workspace for each one - so I end up with 6 workspaces on a slave machine that only has 1 executor. This is sometimes, but not always correlated with Workflow hanging on a batchfile step that failed. From the outside, this partly looks like a race condition in node assignment for parallel steps. 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] [durable-task-plugin] (JENKINS-25727) Occasional exit status -1 with long latencies
Title: Message Title A C commented on JENKINS-25727 Re: Occasional exit status -1 with long latencies OK. WF 1.7 seems to have made this problem worse, tracking a possibly related symptom in JENKINS-28604. 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-6097) Update Center could upgrade plugins to latest-release-for-my-Hudson
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-6097 Update Center could upgrade plugins to latest-release-for-my-Hudson 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] [walldisplay-plugin] (JENKINS-26036) Wall Display folder support
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26036 Wall Display folder support 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] [walldisplay-plugin] (JENKINS-26036) Wall Display folder support
Title: Message Title Jesse Glick resolved as Fixed If the fix is in fact merged, then this should be Resolved/Fixed. Jenkins / JENKINS-26036 Wall Display folder support Change By: Jesse Glick Status: InProgress 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] [workflow-plugin] (JENKINS-28604) Parallel step will create 2nd executor on single-executor slaves
Title: Message Title Jesse Glick commented on JENKINS-28604 Re: Parallel step will create 2nd executor on single-executor slaves Sounds like a core bug. Any steps to reproduce? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-26178) Ability to run docker-exec etc. from a workflow
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26178 Ability to run docker-exec etc. from a workflow Change By: Jesse Glick Component/s: docker-workflow-plugin Component/s: docker-build-step-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] [docker-workflow-plugin] (JENKINS-26178) Ability to run docker-exec etc. from a workflow
Title: Message Title Jesse Glick resolved as Fixed The CloudBees Docker Workflow plugin offers this feature. Jenkins / JENKINS-26178 Ability to run docker-exec etc. from a workflow Change By: Jesse Glick Status: Open Resolved Assignee: vjuranek JesseGlick 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] [docker-traceability-plugin] (JENKINS-28693) docker-java dependency should be shaded
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28693 docker-java dependency should be shaded Change By: Oleg Nenashev Reasons Issues :*docker-javadoesnotguaranteethebackwardcompatibilityacrossversions(there'rebinarycompatibilityviolationsinthelatestreleases)*sharingofincompatiblelibasapluginisnotsafe,sowewanttosetuptheshadingoftheentiredocker-javalib *ifweleavethepluginasis,there'smaybeaconflictwithotherpluginsusingdocker-javaSolution:*Shadethedocker-javalibraryinthepluginI'mawarethatthisissueisablockerfor1.0release.Needsomehelptoelaborateit. 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-28191) Job configuration screen stuck on LOADING due to a JavaScript TypeError
Title: Message Title Daniel Beck resolved as Incomplete No response to comment asking for additional information in a month, so resolving as Incomplete. Jenkins / JENKINS-28191 Job configuration screen stuck on LOADING due to a _javascript_ TypeError Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete 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] [email-ext-plugin] (JENKINS-28729) Exception raised during template rendering: getAffectedFiles() is not implemented
Title: Message Title Santosh Akuthota created an issue Jenkins / JENKINS-28729 Exception raised during template rendering: getAffectedFiles() is not implemented Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin, tfs-plugin Created: 03/Jun/15 7:46 PM Environment: Jenkins ver. 1.598, Windows Server, TFS 2013 Priority: Minor Reporter: Santosh Akuthota The Email is having issues and throws exception when a build is triggered by SCM poll. We are using TFS as our version tool. Please find the below email content for reference. Exception raised during template rendering: getAffectedFiles() is not implemented by this SCM java.lang.UnsupportedOperationException: getAffectedFiles() is not implemented by this SCM at hudson.scm.ChangeLogSet$Entry.getAffectedFiles(ChangeLogSet.java:242) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at groovy.lang.MetaClassImpl$GetBeanMethodMetaProperty.getProperty(MetaClassImpl.java:3500) at
[JIRA] [tfs-plugin] (JENKINS-28729) Exception raised during template rendering: getAffectedFiles() is not implemented
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-28729 Exception raised during template rendering: getAffectedFiles() is not implemented Change By: Alex Earl Component/s: email-ext-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] [tfs-plugin] (JENKINS-28729) Exception raised during template rendering: getAffectedFiles() is not implemented
Title: Message Title Alex Earl commented on JENKINS-28729 Re: Exception raised during template rendering: getAffectedFiles() is not implemented This is not a bug in the email-ext plugin, the template requires that the SCM implements that based on what template you are using. You could edit your template to remove the call to getAffectedFiles(). 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] [tfs-plugin] (JENKINS-28729) Exception raised during template rendering: getAffectedFiles() is not implemented
Title: Message Title Alex Earl assigned an issue to redsolo Jenkins / JENKINS-28729 Exception raised during template rendering: getAffectedFiles() is not implemented Change By: Alex Earl Assignee: AlexEarl redsolo 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] [cvs-plugin] (JENKINS-27717) CVS/Workflow integration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27717 Re: CVS/Workflow integration Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/1f919e4a60824804cba6508d7470df7f6fdd03bd Log: JENKINS-27717 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] [durable-task-plugin] (JENKINS-25727) Occasional exit status -1 with long latencies
Title: Message Title Jesse Glick resolved as Fixed A C I am not sure what bug you are seeing but it sounds different than this one. Better to file separately. Note that 1.7 included a fix in a related area. Jenkins / JENKINS-25727 Occasional exit status -1 with long latencies Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-27739 Changes to slave environment variables are ignored by master Change By: Daniel Beck Labels: envinronment-variables lts-candidate slaves Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-plugin] (JENKINS-28730) GitLab plugin archived versions not available at GitLab http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/
Title: Message Title Andr Pereira assigned an issue to Unassigned Jenkins / JENKINS-28730 GitLab plugin archived versions not available at GitLab http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/ Change By: Andr Pereira Assignee: DanielBrooks 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] [active-choices-plugin] (JENKINS-28732) Add support to the script security plug-in to Active Choices
Title: Message Title Bruno P. Kinoshita commented on JENKINS-28732 Re: Add support to the script security plug-in to Active Choices Some background information: https://groups.google.com/forum/#!searchin/jenkinsci-dev/jesse$20bruno$20security$20groovy/jenkinsci-dev/17--9NhoFJA/odGXD-UOQ18J Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-plugin] (JENKINS-28730) GitLab plugin archived versions not available at GitLab http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/
Title: Message Title Andr Pereira created an issue Jenkins / JENKINS-28730 GitLab plugin archived versions not available at GitLab http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/ Issue Type: Bug Assignee: Daniel Brooks Components: gitlab-plugin Created: 03/Jun/15 10:44 PM Priority: Minor Reporter: Andr Pereira It seems GitLab plugin archived versions are not available at updates.jenkins title. Unfortunatelly jenkins official docker image do not work properly since plugin installation requires this. Can you tell why is not there? Can be fixed? Add Comment
[JIRA] [workflow-plugin] (JENKINS-28604) Parallel step will create 2nd executor on single-executor slaves
Title: Message Title
A C commented on JENKINS-28604
Re: Parallel step will create 2nd executor on single-executor slaves
I don't have the time right now to write a full test case, but here's a cut-down version of the idiom I am trying to use, hopefully helpful:
1 restricted master executor with no labels, 2 restricted slaves with labels and 1 executor each (restricted = only run jobs with matching labels)
try { parallel { node( 'slave' ) { batch step that fails }
repeat node( 'slave' ) several times } } catch( Exception e ) { node( 'slave' ) { another batch step that fails }
}
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-28604) Parallel step will create 2nd executor on single-executor slaves
Title: Message Title
A C edited a comment on JENKINS-28604
Re: Parallel step will create 2nd executor on single-executor slaves
Idon'thavethetimerightnowtowriteafulltestcase,buthere'sacut-downversionoftheidiomIamtryingtouse,hopefullyhelpful:-1restrictedmasterexecutorwithnolabels,2restrictedslaveswithlabelsand1executoreach(restricted=onlyrunjobswithmatchinglabels)try{parallel{node('slave'){batchstepthatfails}repeatnode('slave')severaltimes}}catch(Exceptione){node('slave'){anotherbatchstepthatfails} throwe }
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-28731) Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state
Title: Message Title Matt Taylor created an issue Jenkins / JENKINS-28731 Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state Issue Type: Bug Assignee: Unassigned Components: core Created: 03/Jun/15 11:50 PM Environment: Jenkins 1.616 Windows 8.1 64bit VirtualBox 4.3.28 Labels: jenkins windows build job gui virtualbox Priority: Major Reporter: Matt Taylor == Symptom == Whenever I try and start a VM from the Execute Windows Batch Command inside a freestyle Jenkins job, my VM immediately crashes. == Details == Trying to execute a batch script inside a Jenkins job that starts a Virtual Machine via a batch script will immediately crash and go to the aborted state. However, the same exact batch script can be ran by the host machine with the same variable and parameters perfectly fine manually. Also another workaround is to have
[JIRA] [active-choices-plugin] (JENKINS-28732) Add support to the script security plug-in to Active Choices
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-28732 Add support to the script security plug-in to Active Choices Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 04/Jun/15 12:08 AM Priority: Minor Reporter: Bruno P. Kinoshita We can use the existing Script Security Plug-in to let users be able to secure their scripts. Add Comment This message was sent by Atlassian JIRA
[JIRA] [support-core-plugin] (JENKINS-28703) add the pinned status of a plugin to the support bundle
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28703 Re: add the pinned status of a plugin to the support bundle Code changed in jenkins User: christ66 Path: src/main/java/com/cloudbees/jenkins/support/impl/AboutJenkins.java http://jenkins-ci.org/commit/support-core-plugin/766dce94fbc6de4afa8215ed631328d48546c1f0 Log: JENKINS-28703 Add pinned status for plugins. 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] [support-core-plugin] (JENKINS-28703) add the pinned status of a plugin to the support bundle
Title: Message Title Steven Christou resolved as Fixed Jenkins / JENKINS-28703 add the pinned status of a plugin to the support bundle Change By: Steven Christou 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] [support-core-plugin] (JENKINS-28703) add the pinned status of a plugin to the support bundle
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28703 Re: add the pinned status of a plugin to the support bundle Code changed in jenkins User: Steven Christou Path: src/main/java/com/cloudbees/jenkins/support/impl/AboutJenkins.java http://jenkins-ci.org/commit/support-core-plugin/a8001e90328b14d7c7a9bdebe22a934c69400a1f Log: Merge pull request #34 from christ66/ JENKINS-28703 JENKINS-28703 Add pinned status for plugins. Compare: https://github.com/jenkinsci/support-core-plugin/compare/0a69bdb3b7df...a8001e90328b 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] [tap-plugin] (JENKINS-28508) Broken link on Tap Results
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Fixed in 1.23 Jenkins / JENKINS-28508 Broken link on Tap Results Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-plugin] (JENKINS-28730) GitLab plugin archived versions not available at: http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/
Title: Message Title Andr Pereira updated an issue Jenkins / JENKINS-28730 GitLab plugin archived versions not available at: http://updates.jenkins-ci.org/download/plugins/gitlab-plugin/ Change By: Andr Pereira Summary: GitLabpluginarchivedversionsnotavailableat GitLab : http://updates.jenkins-ci.org/download/plugins/gitlab-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] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier started work on JENKINS-28311 Change By: William Gautier Status: Open InProgress 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] [cloudfoundry-plugin] (JENKINS-28602) Error: Default domain calculated from api domain
Title: Message Title William Gautier resolved as Fixed Fixed in https://github.com/jenkinsci/cloudfoundry/commit/9f2693ee5953baf6c2f0f30f4bb99119c8ed06a9 Will be in v1.4, with the service creation feature. Jenkins / JENKINS-28602 Error: Default domain calculated from api domain Change By: William Gautier Status: InProgress 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] [join-plugin] (JENKINS-28709) Join Plugin ignores dependencies wrapped with flexible-publish
Title: Message Title ikedam assigned an issue to mdonohue It is just because join plugin fails to find out dependencies wrapped with flexible-publish. You can also see project D is displayed in the project status page when you configure a project with Join Trigger without Build other projects. To be exact, JoinTrigger#getAllDownstream fails to find out them: https://github.com/jenkinsci/join-plugin/blob/join-1.15/src/main/java/join/JoinTrigger.java#L216 This results not only project D is displayed but also project D is always triggered just after project A is finished. That means, join doesn't work at all. Jenkins / JENKINS-28709 Join Plugin ignores dependencies wrapped with flexible-publish Change By: ikedam Summary: WrongDownstreamprojectwhere JoinPlugin isused ignoresdependencieswrappedwithflexible-publish Component/s: flexible-publish-plugin Assignee: ikedam mdonohue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [join-plugin] (JENKINS-28709) Join Plugin ignores dependencies wrapped with flexible-publish
Title: Message Title ikedam commented on JENKINS-28709 Re: Join Plugin ignores dependencies wrapped with flexible-publish Promoted Builds Plugin might be an alternate solution for you. 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-28707) Jenkins is trying to queue an already running job
Title: Message Title Jet Rey Maza commented on JENKINS-28707 Re: Jenkins is trying to queue an already running job thanks Daniel but in our situation right now polling is more relevant? (as far as I know) To give you an idea In our project, For every bug fix or new feature we are going to create a new git branch to isolate code changes And for every branch we are going to create a new Jenkins job to build that particular branch Therefore setting up a git hook for every job is tedious rather than having a job generator with preset values Thank you 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] [active-choices-plugin] (JENKINS-28732) Add support to the script security plug-in to Active Choices
Title: Message Title Bruno P. Kinoshita commented on JENKINS-28732 Re: Add support to the script security plug-in to Active Choices Complete example being used as basis: https://github.com/jenkinsci/groovy-postbuild-plugin/pull/11/files 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-traceability-plugin] (JENKINS-28658) Support creation of named container fingerprints
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28658 Re: Support creation of named container fingerprints Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityReportListenerImpl.java http://jenkins-ci.org/commit/docker-traceability-plugin/889ff6f61af71c7acf7b4f172f4d62933082695d Log: [FIXED JENKINS-28658] - Create named container fingerprints The plugin will use container name if it is available. Otherwise it will fall-back to the container ID. 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-traceability-plugin] (JENKINS-28658) Support creation of named container fingerprints
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28658 Support creation of named container fingerprints Change By: SCM/JIRA link daemon Status: Reopened 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] [docker-traceability-plugin] (JENKINS-28658) Support creation of named container fingerprints
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28658 Re: Support creation of named container fingerprints Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityReportListenerImpl.java http://jenkins-ci.org/commit/docker-traceability-plugin/7e6499493c14a1f6a3249c489228cf1237c28575 Log: Merge pull request #12 from oleg-nenashev/ JENKINS-28658 -named-container-FPs [FIXED JENKINS-28658] - Create named container fingerprints Compare: https://github.com/jenkinsci/docker-traceability-plugin/compare/94d22ad7e208...7e6499493c14 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] [email-ext-plugin] (JENKINS-28711) Error while serving recipientListRecipientsCheck
Title: Message Title James Howe created an issue Jenkins / JENKINS-28711 Error while serving recipientListRecipientsCheck Issue Type: Bug Assignee: Alex Earl Attachments: stacktrace.txt Components: email-ext-plugin Created: 03/Jun/15 10:49 AM Environment: Jenkins 1.611, email-ext 2.40.4 Priority: Minor Reporter: James Howe Unknown if this is causing any actual issues. See attached stacktrace. Add Comment
[JIRA] [docker-build-publish-plugin] (JENKINS-28675) Create Docker image fingerprints after the build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28675 Re: Create Docker image fingerprints after the build Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java src/main/java/com/cloudbees/dockerpublish/DockerCLIHelper.java src/main/resources/com/cloudbees/dockerpublish/DockerBuilder/config.jelly src/main/resources/com/cloudbees/dockerpublish/DockerBuilder/help-createFingerprint.html src/test/java/com/cloudbees/dockerpublish/DockerCLIHelperTest.java src/test/resources/dockerInspectImage_response.json http://jenkins-ci.org/commit/docker-build-publish-plugin/570ab9b547f0f82cc49fa555c2bfe63b8ca79283 Log: Merge pull request #22 from oleg-nenashev/JENKINS-28675 JENKINS-28675 - Create fingerprints when creating new images Compare: https://github.com/jenkinsci/docker-build-publish-plugin/compare/899be05ae916...570ab9b547f0 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-build-publish-plugin] (JENKINS-28675) Create Docker image fingerprints after the build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28675 Re: Create Docker image fingerprints after the build Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java src/main/java/com/cloudbees/dockerpublish/DockerCLIHelper.java http://jenkins-ci.org/commit/docker-build-publish-plugin/30a0bc09c2a917cbe11cfb86562d4d2dfe055686 Log: JENKINS-28675 - Refactor docker-build-publish STDOUT/STDERR handling Return STDERR in Result New method, which allows to manage logging of STDOUT/STDERR outputs Annotations 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-build-publish-plugin] (JENKINS-28675) Create Docker image fingerprints after the build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28675 Re: Create Docker image fingerprints after the build Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java src/main/java/com/cloudbees/dockerpublish/DockerCLIHelper.java src/main/resources/com/cloudbees/dockerpublish/DockerBuilder/config.jelly src/main/resources/com/cloudbees/dockerpublish/DockerBuilder/help-createFingerprint.html src/test/java/com/cloudbees/dockerpublish/DockerCLIHelperTest.java src/test/resources/dockerInspectImage_response.json http://jenkins-ci.org/commit/docker-build-publish-plugin/defbeabb366cd7633d197db1b9c64e55dd81cf7f Log: JENKINS-28675 - Create fingerprints when creating new images This is a draft implementation of the on-demand creation of Docker fingerprints from docker-build-publich plugin. The current version has a limited usability due to the lack of the info in fingerprints. We assume that something like Docker Traceability Plugin will add more info later. 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-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title Daniel Beck commented on JENKINS-28698 Re: Update Jenkins to 1.616 results in a 1.615 version It would be helpful to know what gets logged in this situation. 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-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title Kevin Phillips commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs In my latest case the view was a Sectioned View type, with maybe 10 sub-sections of type List View. Each list view subsection has a regular _expression_ for the job filter, and there are few if any jobs that are checked off individually. I suspect I can reproduce the problem on other view types as well. If I get some time today to try that out I'll let you know the results. 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-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title Guy Rooms edited a comment on JENKINS-28698 Re: Update Jenkins to 1.616 results in a 1.615 version Iencounteredsimilarbehavior,althoughcontextwasdifferent:Ididanupdateto1.615(from1.5xx)intomcat,anditfailedtostartjenkins.So,I gradually startedfrom1.600andgraduallymovedtonewerversion-startingfrom1.600=success-*didsomehot-deploystonewerversion,atacertainpointoftimeIalsoexperiencedjenkinstopublishthepreviousversion*.-soIrestartedtomcat,(+removedthejenkinssubdirinapache-dir/webappfolder)-..andfoundjenkinswasnotstartinganymoreenv:OS:CentOSrelease6.5(Final)Java:java-1.6.0-openjdk-1.6.0.0.x86_64/jreWebserver:apache-tomcat-7.0.42jenkins:1.600(andfollowing...) 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-28698) Update Jenkins to 1.616 results in a 1.615 version
Title: Message Title Guy Rooms commented on JENKINS-28698 Re: Update Jenkins to 1.616 results in a 1.615 version I encountered similar behavior, although context was different: I did an update to 1.615 (from 1.5xx) in tomcat, and it failed to start jenkins. So, I gradually started from 1.600 and gradually moved to newer version starting from 1.600 = success did some hot-deploys to newer version, at a certain point of time I also experienced jenkins to publish the previous version. so I restarted tomcat, (+ removed the jenkins subdir in apache-dir/webapp folder) .. and found jenkins was not starting anymore env: OS: CentOS release 6.5 (Final) Java: java-1.6.0-openjdk-1.6.0.0.x86_64/jre Webserver: apache-tomcat-7.0.42 jenkins: 1.600 (and following...) 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-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title Kevin Phillips commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs I decided to just take some time right away to do some further tests and I can't seem to reproduce the problem on other view types. I have tried the following: nested views list views categorized jobs view build pipeline view my view status view dashboard view Also, for some of our views of type Sectioned View with a smaller number of sub-sections on them, the error doesn't appear to occur. The combination of a view of type Sectioned View with a large number of sub-sections of type List View seems to be the problematic case. Also, our build farm has a large number of jobs on it (1200 atm). If the Sectioned View were submitting information about each of these jobs for each of the list sub-views that could explain why the error only happens in this one use case. Either way, the hack mentioned above for overriding the maxFormContentSize property for Jetty seems to prevent the problem, at least for us. This at least unblocks us for the time being. Still, it would be good to try and get a fix for this if possible. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-28601) Order of job table reverse
Title: Message Title Lars W commented on JENKINS-28601 Re: Order of job table reverse The InitialSortDir of the job table (and some other tables) should be changed to up. But I don't know where to do it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28706) Hide Docker Traceability Root Action by default
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28706 Re: Hide Docker Traceability Root Action by default Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootAction.java src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.properties src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/help-showRootAction.html src/test/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginTest.java src/test/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootActionTest.java http://jenkins-ci.org/commit/docker-traceability-plugin/0cd64a191f786400d340208398cab6ff45119f5d Log: [FIXED JENKINS-28706] - Hide Docker Traceability Root Action by default 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-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: README.md src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.java src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityReportListenerImpl.java src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.properties src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/help-createImageFingerprints.html src/test/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginTest.java src/test/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootActionTest.java http://jenkins-ci.org/commit/docker-traceability-plugin/e66fbf451b02ecd02b2fa4cb006018e0df60d74a Log: [FIXED JENKINS-28656] - On-demand creation of image fingerprints This change allows to configure Docker Traceability plugin to accept all submissions and create container/image fingerprints on-demand. This functionality is useful even if we don't support the fingerprints cleanup prevention now. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java http://jenkins-ci.org/commit/docker-traceability-plugin/23093513a0dec5b0eacec0dbf03e77e50d224be2 Log: JENKINS-28656 - Add Javadoc and fix mis-behavior on null name 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-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28656 Re: Docker Traceability should support the creation of image fingerprints on-demand Code changed in jenkins User: Oleg Nenashev Path: README.md src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin.java src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityHelper.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityReportListenerImpl.java src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPlugin/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.properties src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/help-createImageFingerprints.html src/test/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginTest.java src/test/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootActionTest.java http://jenkins-ci.org/commit/docker-traceability-plugin/48c703147f35403aef5a68fd9e40035ced3db793 Log: Merge pull request #11 from oleg-nenashev/ JENKINS-28656 -on-demand-image-fingerprints [FIXED JENKINS-28656] - On-demand creation of image fingerprints Compare: https://github.com/jenkinsci/docker-traceability-plugin/compare/7e6499493c14...48c703147f35 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
[JIRA] [docker-traceability-plugin] (JENKINS-28706) Hide Docker Traceability Root Action by default
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28706 Hide Docker Traceability Root Action by default 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] [docker-traceability-plugin] (JENKINS-28706) Hide Docker Traceability Root Action by default
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28706 Re: Hide Docker Traceability Root Action by default Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration.java src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootAction.java src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/config.properties src/main/resources/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginConfiguration/help-showRootAction.html src/test/java/org/jenkinsci/plugins/docker/traceability/DockerTraceabilityPluginTest.java src/test/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootActionTest.java http://jenkins-ci.org/commit/docker-traceability-plugin/7bb2459480d81b5fbb00f05038ef088764a4fcb5 Log: Merge pull request #13 from oleg-nenashev/ JENKINS-28706 -hide-root-action [FIXED JENKINS-28706] - Hide Docker Traceability Root Action by default Compare: https://github.com/jenkinsci/docker-traceability-plugin/compare/48c703147f35...7bb2459480d8 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-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28656 Docker Traceability should support the creation of image fingerprints on-demand Change By: SCM/JIRA link daemon Status: Reopened 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] [ownership-plugin] (JENKINS-28712) Do not show empty boxes when ownership is not set
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-28712 Do not show empty boxes when ownership is not set Issue Type: Bug Assignee: Oleg Nenashev Components: ownership-plugin Created: 03/Jun/15 11:38 AM Priority: Minor Reporter: Oliver Gondža It just clutters the page without presenting any information. This can be reproduced by setting Assign job creators as owners and creating jobs as anonymous. It also appears on runs with default configuration, though I am not 100% sure under what condition that happens. Add Comment
[JIRA] [dry-plugin] (JENKINS-28669) Dry-plugin crashing with GC exception
Title: Message Title Debashis Prusty commented on JENKINS-28669 Re: Dry-plugin crashing with GC exception The cpd file is 38MB. Below is the complete dump. INFO: Code_Duplicity #1 main build action completed: SUCCESS Exception in thread Ping thread for channel hudson.remoting.Channel@6f4dbda2:tools Exception in thread Channel reader thread: vagrant_buildserver Exception in thread Ping thread for channel hudson.remoting.Channel@1d1c75d:vagrant_buildserver Exception in thread Thread-5 Exception in thread Ping thread for channel hudson.remoting.Channel@16e7ae76:vagrant_tibi Exception in thread Ping thread for channel hudson.remoting.Channel@5d6577bf:InV_CI java.lang.OutOfMemoryError: GC overhead limit exceeded at java.lang.AbstractStringBuilder.init(AbstractStringBuilder.java:68) at java.lang.StringBuffer.init(StringBuffer.java:116) java.lang.OutOfMemoryError: GC overhead limit exceeded java.lang.OutOfMemoryError: GC overhead limit exceeded at java.util.Arrays.copyOf(Arrays.java:3332) at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:137) at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:121) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:421) at java.lang.StringBuilder.append(StringBuilder.java:136) at com.trilead.ssh2.transport.TransportConnection.receiveMessage(TransportConnection.java:278) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:693) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:489) at java.lang.Thread.run(Thread.java:745) Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread Ping thread for channel hudson.remoting.Channel@5d6577bf:InV_CI java.lang.OutOfMemoryError: GC overhead limit exceeded java.lang.OutOfMemoryError: GC overhead limit exceeded at java.io.ObjectOutputStream$BlockDataOutputStream.init(ObjectOutputStream.java:1754) at java.io.ObjectOutputStream.init(ObjectOutputStream.java:242) at hudson.remoting.MultiClassLoaderSerializer$Output.init(MultiClassLoaderSerializer.java:38) at hudson.remoting.UserRequest._serialize(UserRequest.java:154) at hudson.remoting.UserRequest.serialize(UserRequest.java:167) at hudson.remoting.UserRequest.init(UserRequest.java:63) at hudson.remoting.Channel.callAsync(Channel.java:779) at hudson.remoting.PingThread.ping(PingThread.java:104) at hudson.remoting.PingThread.run(PingThread.java:85) java.lang.OutOfMemoryError: GC overhead limit exceeded May 27, 2015 6:52:34 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: java.lang.OutOfMemoryError: GC overhead limit exceeded May 27, 2015 6:47:59 PM hudson.triggers.Trigger$Cron doRun Add Comment
[JIRA] [ownership-plugin] (JENKINS-28713) Improper permission checks in the plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28713 Improper permission checks in the plugin Issue Type: Bug Assignee: Oleg Nenashev Components: ownership-plugin Created: 03/Jun/15 11:55 AM Labels: security Priority: Major Reporter: Oleg Nenashev The plugin's API methods use hasPermission() instead of checkPermission() in several places, so the exception is not being thrown. Add Comment
[JIRA] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title Oleg Nenashev reopened an issue Pushed the branch to a wrong repo Jenkins / JENKINS-28656 Docker Traceability should support the creation of image fingerprints on-demand Change By: Oleg Nenashev Resolution: Fixed 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] [core] (JENKINS-21301) Jenkins stops responding to HTTP requests outside builds
Title: Message Title Daniel Beck resolved as Incomplete No response to comments asking for additional information in several months, so resolving as obsolete. If this happens again, please file a new issue after reading https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Jenkins / JENKINS-21301 Jenkins stops responding to HTTP requests outside builds Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete 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] [flexible-publish-plugin] (JENKINS-28709) Wrong Downstream project where Join Plugin is used
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-28709 Wrong Downstream project where Join Plugin is used Change By: Raphael CHAUMIER Hi,Iwanttochecksomeenvvariablebeforetriggering2downstreamprojectswhicharejointaftertheirbuildto1otherproject.SoIdeclaredmyconditionsthenadda'builddownstreamproject'actionwithmytwoprojectsplusa'JoinTrigger'actiontojointheprojectstoanotherprojectoncetheyhavebuiltsuccessfully.WhenIhavealookofmymainproject dashboard IseeIttriggerallofthe3projectsasdownstreamwhereasItshouldtriggeronlythefirsttwoones 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-28593) Make gerrit comments configurable
Title: Message Title rsandell edited a comment on JENKINS-28593 Re: Make gerrit comments configurable Howtoselectafiletobeincludedinthecomment. !unsuccessfulmessagefile.png|thumbnail! 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-28593) Make gerrit comments configurable
Title: Message Title rsandell updated an issue Jenkins / JENKINS-28593 Make gerrit comments configurable How to select a file to be included in the comment. Change By: rsandell Attachment: unsuccessfulmessagefile.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] [ownership-plugin] (JENKINS-28712) Do not show empty boxes when ownership is not set
Title: Message Title Oleg Nenashev commented on JENKINS-28712 Re: Do not show empty boxes when ownership is not set Thanks for the issue - I'll check it. I don't expect that anonymous is allowed to create jobs on Jenkins instances requiring ownership plugin, but it would good to cover this case Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mantis-plugin] (JENKINS-28381) My mantis plugin does not show me any project and category
Title: Message Title rake kniven commented on JENKINS-28381 Re: My mantis plugin does not show me any project and category Any ideas? We are using mantis and jenkins a lot and would appreciate any help. 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-23152) builds getting lost due to GerritTrigger
Title: Message Title rsandell commented on JENKINS-23152 Re: builds getting lost due to GerritTrigger And what happens if you upgrade to = 2.13 where efforts have been made to fix this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28643) timestamps in the UI are not correct
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28643 Re: timestamps in the UI are not correct Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootAction.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerInspectImageFacet.java src/main/resources/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootAction/_api.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/lib/eventTime.groovy http://jenkins-ci.org/commit/docker-traceability-plugin/9aba193094966aa063f48b1da90ac16487ce1d3c Log: [FIXED JENKINS-28643] - Event times are being logged in seconds Seems I've read a wrong doc on docker APIs. All modern ones return times in seconds. 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-traceability-plugin] (JENKINS-28643) timestamps in the UI are not correct
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28643 timestamps in the UI are not correct Change By: SCM/JIRA link daemon Status: InProgress 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] [docker-traceability-plugin] (JENKINS-28643) timestamps in the UI are not correct
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28643 Re: timestamps in the UI are not correct Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootAction.java src/main/java/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerInspectImageFacet.java src/main/resources/org/jenkinsci/plugins/docker/traceability/core/DockerTraceabilityRootAction/_api.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/fingerprint/DockerInspectImageFacet/main.jelly src/main/resources/org/jenkinsci/plugins/docker/traceability/lib/eventTime.groovy http://jenkins-ci.org/commit/docker-traceability-plugin/f3e23ec04eaacbd1deeaca7b9290a24c7aefd9c9 Log: Merge pull request #10 from oleg-nenashev/ JENKINS-28643 [FIXED JENKINS-28643] - Event times are being logged in seconds Compare: https://github.com/jenkinsci/docker-traceability-plugin/compare/7bb2459480d8...f3e23ec04eaa 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] [mantis-plugin] (JENKINS-28381) My mantis plugin does not show me any project and category
Title: Message Title rake kniven commented on JENKINS-28381 Re: My mantis plugin does not show me any project and category Spent some more time and have it working again. What I did: Removed mantis plugin 0.26 Restarted jenkins Installed mantis plugin 0.25 (hpi file from archive) Restarted jenkins Entered mantis user credentials again Restarted jenkins Configured job and now project and category Combobox has entries again. I am happy so far. Bad side: I will not upgrade to 0.26 and further releases due to named problems. I am willing to support plugin devs in testing. Just let me know. 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
[JIRA] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title Daniel Beck commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs Was there some specific information you'd like me to provide that hasn't already been stated above? Is this a view with a very large number of items selected via checkbox? 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-28707) Jenkins is trying to queue an already running job
Title: Message Title Daniel Beck commented on JENKINS-28707 Re: Jenkins is trying to queue an already running job Your polling interval is so short that it's likely the first build has not yet recorded revision information in Jenkins when Jenkins polls and schedules the second build. Increase the polling interval until after the build overview page of the first build shows revision information for that (still running) build. 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-28707) Jenkins is trying to queue an already running job
Title: Message Title Jet Rey Maza updated an issue Jenkins / JENKINS-28707 Jenkins is trying to queue an already running job Change By: Jet Rey Maza Icreatedajob(i.e.*JOB-A*)usingajobgeneratorjob(letsayMY-JOB-GENERATOR)Thisjob(JOB-A)willsimplybuildourproject:)Thisjob(JOB-A)willbetriggeredbypolling(everyminute)alocalgitrepository(whichisasharedfolderinourlocalnetwork)(!)AnywayJenkinsissittingonanothercomputer(aserver)Aftercreatingthejob(JOB-A),Jenkinswillstartpolling(y)Afterthefirstpoll,Jenkinswillfindoutthattheworkspaceforthisjob(JOB-A)isempty,thereforeheisgoingtoclonetherepositoryHowever,*whilethefirstbuildisrunning*,Jenkinswilltrytoscheduleanotherbuildforthisjob(JOB-A)(i)ResultingtotwoconsecutivebuildswhichisunnecessaryandcausingadditionalloadtoourJenkinsserver(!)Alsothishappensonlyduringtheinitialbuild(!)Ialsofoundaquitesimilarissueherehttps://issues.jenkins-ci.org/browse/JENKINS-23415however*unresolved*:((on)IalreadytriedtoadjustthequietperiodofJenkinsfrom(5to0)to(0to10) (on)Ialreadytriedcreatingajobmanually(notusingthejobgeneratorjob)butthisissueisstillhappening Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth-plugin] (JENKINS-23844) Matrix based security should apply to case insensitive user name.
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-23844 Matrix based security should apply to case insensitive user name. There is a fairly easy workaround for this issue: Have your users log in using the user name case used in the permissions config. Use e.g. Simple Theme Plugin to add a note to the login page. For any higher priority, please explain the reasoning. I really want it fixed is not a good reason Change By: Daniel Beck Priority: Blocker Minor 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] [ownership-plugin] (JENKINS-28713) Improper permission checks in the plugin
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28713 Improper permission checks in the plugin 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] [ownership-plugin] (JENKINS-28713) Improper permission checks in the plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28713 Re: Improper permission checks in the plugin Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction.java http://jenkins-ci.org/commit/ownership-plugin/9d670510f53227e1be347f0887dae2ad2dc571c0 Log: [FIXED JENKINS-28713] - Proper security checks in API methods The plugin's API methods use hasPermission() instead of checkPermission() in several places, so the exception is not being thrown. 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] [ownership-plugin] (JENKINS-28713) Improper permission checks in the plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28713 Re: Improper permission checks in the plugin Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction.java http://jenkins-ci.org/commit/ownership-plugin/b2a3f863023ef45d66376129d79f430609545c9f Log: Merge pull request #39 from oleg-nenashev/ JENKINS-28713 [FIXED JENKINS-28713] - Proper security checks in API methods Compare: https://github.com/jenkinsci/ownership-plugin/compare/82dc6b31a3b7...b2a3f863023e 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] [ownership-plugin] (JENKINS-28714) Optianally do not display run ownership
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-28714 Optianally do not display run ownership Issue Type: Improvement Assignee: Oleg Nenashev Components: ownership-plugin Created: 03/Jun/15 12:01 PM Priority: Minor Reporter: Oliver Gondža Introduce global configuration option not to present that information. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-client-plugin] (JENKINS-28707) Jenkins is trying to queue an already running job
Title: Message Title Jet Rey Maza resolved as Fixed I owe you once sir Jenkins / JENKINS-28707 Jenkins is trying to queue an already running job Change By: Jet Rey Maza Status: Open Resolved Assignee: JetReyMaza DanielBeck 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-client-plugin] (JENKINS-28707) Jenkins is trying to queue an already running job
Title: Message Title Jet Rey Maza commented on JENKINS-28707 Re: Jenkins is trying to queue an already running job Thank you Daniel I will try that and send you a feedback later 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] [nunit-plugin] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title Flaviu S updated an issue Jenkins / JENKINS-27906 Fail to read NUnit3 output xml Change By: Flaviu S Attachment: nunit3_TestResult.xml Attachment: nunit2_TestResult.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] [git-client-plugin] (JENKINS-28707) Jenkins is trying to queue an already running job
Title: Message Title Daniel Beck commented on JENKINS-28707 Re: Jenkins is trying to queue an already running job You're welcome! FWIW polling is an inefficient way to do this anyway. See e.g. http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ Of course this probably won't work with your shared folder. 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] [sauce-ondemand-plugin] (JENKINS-28651) Sauce Connect doesn't work using v4 but it works fine with v3
Title: Message Title Ross Rowe commented on JENKINS-28651 Re: Sauce Connect doesn't work using v4 but it works fine with v3 It looks like Sauce Connect is failing to start because of the 'Error opening sc_my-tun2.log: No such file or directory' error. The default location for the Sauce Connect log file is /tmp, and my guess is that Sauce Connect v4 can't write to this directory due to the permissions of the user which launched Jenkins. Can you try supply a different value for the log location for Sauce Connect? You can do this by including --logfile /path/to/sc.log in the Sauce Connect Options field within the Jenkins job configuration (under Sauce Connect Advanced Options) where /path/to is a location on the Jenkins server which the user has write access to. 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-tag-message-plugin] (JENKINS-28705) Plugin expose the actual tag name as enviroment variable
Title: Message Title Thomas Blitz created an issue Jenkins / JENKINS-28705 Plugin expose the actual tag name as enviroment variable Issue Type: New Feature Assignee: Thomas Blitz Components: git-tag-message-plugin Created: 03/Jun/15 6:06 AM Labels: plugin, feature git-tag git-tag-message Priority: Minor Reporter: Thomas Blitz The plugin should expose the actual tagname as an enviroment variable. The change is already made and a pull request has been issued on github. see the URL in this feature request. This feature is simply waiting for a github pull request merge. Add Comment
[JIRA] [logstash-plugin] (JENKINS-28040) Allow logstash plugin to feed a syslog server
Title: Message Title Cyrille Le Clerc commented on JENKINS-28040 Re: Allow logstash plugin to feed a syslog server @rgerard I feel that it's good to offer this feature in the logstash plugin waiting for the audit trail plugin to offer something equivalent. Most of the syslog logic is located in the syslog-java-client dependency, the quantity of code duplication between the 2 plugins (logstash-plugin and audit-trail-plugin) is limited. 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-28695) job-dsl allocatePorts does not work
Title: Message Title Andreas Holzner commented on JENKINS-28695 Re: job-dsl allocatePorts does not work The logs did no show anything so I did not make the connection to the FAQ item. Restarting helped, 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] [job-dsl-plugin] (JENKINS-28695) job-dsl allocatePorts does not work
Title: Message Title Andreas Holzner closed an issue as Not A Defect Jenkins / JENKINS-28695 job-dsl allocatePorts does not work Change By: Andreas Holzner Status: Open Closed Resolution: NotADefect 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-28278) Environment variables stuck on windows slave
Title: Message Title Daniel Beck commented on JENKINS-28278 Re: Environment variables stuck on windows slave Which Jenkins versions are affected by this? Which are the last known good versions? 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] [flexible-publish-plugin] (JENKINS-28709) Wrong Downstream project where Join Plugin is used
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-28709 Wrong Downstream project where Join Plugin is used Change By: Raphael CHAUMIER Hi,Iwanttochecksomeenvvariablebeforetriggering2downstreamprojectswhicharejointaftertheirbuildto1otherproject.SoIdeclaredmyconditionsthenadda'builddownstreamproject'actionwithmytwoprojectsplusa'JoinTrigger'actiontojointheprojectstoanotherprojectoncethey build havebuilt successfully.WhenIhavealookofmymainprojectIseeIttriggerallofthe3projectsasdownstreamwhereasItshouldtriggeronlythefirsttwoones 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] [flexible-publish-plugin] (JENKINS-28709) Wrong Downstream project where Join Plugin is used
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-28709 Wrong Downstream project where Join Plugin is used Change By: Raphael CHAUMIER Hi,Iwanttochecksomeenvvariablebeforetriggering2downstreamprojectswhicharejointaftertheirbuildto1otherproject.SoIdeclaredmyconditionsthenadda'builddownstreamproject'actionwithmytwoprojectsplusa'JoinTrigger'actiontojointheprojectstoanotherprojectoncetheyhavebuiltsuccessfully.WhenIhavealookofmymainprojectdashboardIsee Ittrigger ittriggers allofthe3projectsasdownstreamwhereasItshouldtriggeronlythefirsttwoones 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] [flexible-publish-plugin] (JENKINS-28709) Wrong Downstream project where Join Plugin is used
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-28709 Wrong Downstream project where Join Plugin is used Change By: Raphael CHAUMIER Component/s: join-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] [radiatorview-plugin] (JENKINS-28674) Timing mismatch between radiator and individual jenkin job
Title: Message Title Daniel Beck assigned an issue to Unassigned Jenkins / JENKINS-28674 Timing mismatch between radiator and individual jenkin job Change By: Daniel Beck Assignee: R.TylerCroy 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] [delivery-pipeline-plugin] (JENKINS-28708) Add abort button
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-28708 Add abort button Issue Type: New Feature Assignee: Patrik Bostrm Components: delivery-pipeline-plugin Created: 03/Jun/15 8:33 AM Priority: Minor Reporter: Marcin Zajączkowski I like very much the addition of a retry button for a job in a pipeline view. It would be useful to have also an abort button to be able to stop selected job. Add Comment This message was sent
[JIRA] [git-client-plugin] (JENKINS-28707) Jenkins is trying to queue an already running job
Title: Message Title Jet Rey Maza commented on JENKINS-28707 Re: Jenkins is trying to queue an already running job This issue is solved after adjusting my polling interval from (1 minute to 5 minutes) Thanks to @danielbeck 1 more concern is that this workaround may introduce a little bit of delay on our automation 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] [matrix-project-plugin] (JENKINS-28681) mercurial-plugin doesn't work if matrix-project-plugin plugin is disabled
Title: Message Title Daniel Beck resolved as Not A Defect Matrix Project Plugin is a non-optional dependency of Mercurial Plugin as you can see in the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Mercurial+Plugin So this behavior is to be expected. Jenkins / JENKINS-28681 mercurial-plugin doesn't work if matrix-project-plugin plugin is disabled Change By: Daniel Beck Status: Open Resolved Resolution: NotADefect 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] [pollscm-plugin] (JENKINS-28710) Poll source from tfs to jenkins slave showing no change
Title: Message Title Ajit Nair created an issue Jenkins / JENKINS-28710 Poll source from tfs to jenkins slave showing no change Issue Type: Bug Assignee: Vincent Latombe Attachments: Config.png Components: pollscm-plugin, tfs-plugin Created: 03/Jun/15 9:27 AM Environment: OS - Windows 7, Google Crome, Jenkins 1.596.2, TFS 2012, msbuild plugin 1.24, mstest plugin 0.18, ncover plugin 0.3, tfs plugin 3.2.0 Labels: jenkins slave tfs pollscm Priority: Blocker Reporter: Ajit Nair I am trying to perform CI through Jenkins on .NET projects using TFS as source control. I have created Master Slave connection with Jenkins. Master is my machine and Slave is different VM. When I am trying to create the build it is failing because it is not
[JIRA] [docker-traceability-plugin] (JENKINS-28706) Hide Docker Traceability Root Action by default
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28706 Hide Docker Traceability Root Action by default Issue Type: Improvement Assignee: Oleg Nenashev Components: docker-traceability-plugin Created: 03/Jun/15 6:14 AM Priority: Minor Reporter: Oleg Nenashev The root action is not very helpful in the current version. It makes sense to hide it by default in order to prevent the sidepanel pollution. Add Comment This message was
[JIRA] [fitnesse-plugin] (JENKINS-27938) Unable to expand collapsed SLIM tables
Title: Message Title Antoine Aumjaud assigned an issue to Antoine Aumjaud Jenkins / JENKINS-27938 Unable to expand collapsed SLIM tables Change By: Antoine Aumjaud Assignee: AntoineAumjaud 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.
