[JIRA] (JENKINS-54184) manager.removeSummaries() throws UnsupportedOperationException
Title: Message Title Tobias Peitzsch commented on JENKINS-54184 Re: manager.removeSummaries() throws UnsupportedOperationException Thx for the fix. Works like a charm. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Tobias Peitzsch commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification To be more concrete, the best practice "one branch, one job" will not work in large companies with separated teams for SW development and infrastructure development due to job maintenance (E.g. are the latest released script versions used by the SW development teams). Here the build script version must be specified centrally. Please think about more than 1000 different SW development projects / repositories with at least 10 branches (note: multibranch is not possible, legacy SCM) but only 4 different workflows. It is a hard job to change some global configurations for more 1 jobs (even with Jobs DSL). To reduce the amount of jobs I want to use one job per released pipeline script version for all related projects / repositories (or 1 jobs running in one Job). Unfortunately the milestone step cannot be used. Markus Maga: Unfortunately not. I haven't found a real solution for this issue :/. E.g. the Job creation via Jobs DSL introduce additional infrastructure to handle the build parameters (some of them can be changed by the users and would be overwritten by the Jobs DSL) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54184) manager.removeSummaries() throws UnsupportedOperationException
Title: Message Title
Tobias Peitzsch created an issue
Jenkins / JENKINS-54184
manager.removeSummaries() throws UnsupportedOperationException
Issue Type:
Bug
Assignee:
Stefan Wolf
Components:
groovy-postbuild-plugin
Created:
2018-10-22 12:30
Priority:
Minor
Reporter:
Tobias Peitzsch
pipeline script to reproduce:
manager.createSummary("star-gold.gif").appendText("abc")
manager. removeSummaries()
Jenkins: 2.121.2 Groovy Post Build PlugIn: 2.4.2 Stacktrace:
java.lang.UnsupportedOperationException
at java.util.Collections$UnmodifiableCollection.removeAll(Collections.java:1068)
at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder$BadgeManager.removeSummaries(GroovyPostbuildRecorder.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:47)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Tobias Peitzsch commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification Antonio Muñiz: I would like to understand why it is not desirable to have 2 projects built by the same job? In my opinion it is a limitation as additional maintenance needed (DRY principle is not fulfilled) higher dependency to Jenkins / more Jenkins centric view e.g. multi branch has limitations (e.g. try to handle Subversion and GIT in one job) For me, Jenkins is a infrastructure tool. I use it to define where data shall be processed but not how. Representation of the result is not done with Jenkins (could this be the main reason to have one job per project?) E.g. my generalized workflow build is triggered by external tool build pulls data depending on provided parameters build processes data build pushes result to other tools (e.g. dashboard, artifactory ...) So in case of double builds / same data shall be processed twice I would like to abort one build. Unfortunately, it is not possible with the current implementation of the milestone. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
