[JIRA] (JENKINS-38024) GithubLinkAnnotator NPE
Title: Message Title
Christopher Shannon created an issue
Jenkins / JENKINS-38024
GithubLinkAnnotator NPE
Issue Type:
Improvement
Assignee:
Kirill Merkushev
Components:
github-plugin
Created:
2016/Sep/07 12:23 PM
Environment:
Jenkins 2.72 GitHub Plugin 1.21.1 ClearCase UCM Plugin 1.7.0
Labels:
github clearcase-ucm npe
Priority:
Minor
Reporter:
Christopher Shannon
We are seeing a constant stream of error messages in our jenkins.err.log about the GithubLinkAnnotator failing to annotate a message. {{Sep 06, 2016 6:21:13 PM hudson.scm.ChangeLogSet$Entry getMsgAnnotated INFO: ChangeLogAnnotator com.coravy.hudson.plugins.github.GithubLinkAnnotator@7c6e03a4 failed to annotate message 'FOO00132383'; null}} I believe that the crux of the issue is that these change log sets are actually from the ClearCase Plugin, and not from GitHub projects at all. I see a null check in the annotate call, but apparently something else is tripping up this code. I realize that this will be hard for someone on the GitHub side to fix/verify since it requires ClearCase change sets. I'm not sure it can be deduced what extra null checks might be necessary, or if this issue could be bounced to the ClearCase UCM project to gather some additional information...
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title
Christopher Shannon created an issue
Jenkins / JENKINS-38062
"Create Delivery Pipeline version" errors
Issue Type:
Improvement
Assignee:
Patrik Boström
Components:
delivery-pipeline-plugin, matrix-project-plugin
Created:
2016/Sep/08 2:27 PM
Environment:
Jenkins 2.7.2 Delivery Pipeline Plugin 0.9.12 Matrix Project Plugin 1.7.1
Labels:
delivery matrix
Priority:
Major
Reporter:
Christopher Shannon
Steps to reproduce:
Create freestyle job and select the "Create Delivery Pipeline version" option (providing something like foo.$ {BUILD_NUMBER} in the Template field.
Create a matrix build, with one user-defined axis and one input string parameter.
Trigger the matrix build as a post-build step from the freestyle job, passing in the single parameter.
Although everything runs okay, jenkins.err.log will show several errors about skipping parameters. {{Sep 08, 2016 9:03:26 AM hudson.model.ParametersAction filter WARNING: Skipped parameter `INPUT` as it is undefined on `Sandbox/Matrix/Downstream/AXIS=64`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters`=true to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even tho
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title Christopher Shannon updated an issue Jenkins / JENKINS-38062 "Create Delivery Pipeline version" errors Change By: Christopher Shannon Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title Christopher Shannon commented on JENKINS-38062 Re: "Create Delivery Pipeline version" errors FYI - yes you can work around the error message for PIPELINE_VERSION, but what is strange is that we see parameter errors for every parameter that we're sending downstream as well. You have to do the blanket override to get work around this right now. -Dhudson.model.ParametersAction.keepUndefinedParameters=true Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35979) Newline in activity headline breaks build (our case 14765)
Title: Message Title Christopher Shannon commented on JENKINS-35979 Re: Newline in activity headline breaks build (our case 14765) Note that we just ran into a similar issue when "&&" was found in the activity headline as well. Basically, it looks to me like the fix is to make sure the headline is wrapped/escaped to be XML-safe. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38627) Add support for Job DSL
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-38627 Add support for Job DSL Issue Type: Improvement Assignee: huybrechts Components: template-project-plugin Created: 2016/Sep/30 1:51 PM Priority: Minor Reporter: Christopher Shannon It would be really nice if the template project plugin directly supported the Job DSL plugin, such that using build steps or publishers from another project showed up in those respective places under https://jenkinsci.github.io/job-dsl-plugin/. Add Comment
[JIRA] (JENKINS-38024) GithubLinkAnnotator NPE
Title: Message Title Christopher Shannon commented on JENKINS-38024 Re: GithubLinkAnnotator NPE I see on the GitHub plugin page that it will annotate all of the "Changes" pages with GitHub links: _The Github plugin decorates Jenkins "Changes" pages to create links to your Github commit and issue pages. It adds a sidebar link that links back to the Github project page. _ Has this been tested alongside Jenkins jobs that use other SCM solutions? Obviously my issue is with ClearCase, but I'm guessing that changesets from other SCMs could have the same issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38741) Job DSL execution is occassionally slow on large scale production servers
Title: Message Title Christopher Shannon commented on JENKINS-38741 Re: Job DSL execution is occassionally slow on large scale production servers I can confirm that running a job DSL script causes a significant load on the master. Our Jenkins instance was previously running on my laptop, and my PC would become almost unusable while a job DSL script was running. We have since moved to a real server and increased the max heap size that Jenkins can consume considerably, so it is no longer an issue for us. I'd be curious from the output of this thread "what" it is doing, but can at least confirm that there is a very noticeable load put on the master while a script is being processed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38747) Job DSL: strange behavior from "configure"
Title: Message Title
Christopher Shannon created an issue
Jenkins / JENKINS-38747
Job DSL: strange behavior from "configure"
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2016/Oct/05 6:22 PM
Environment:
Job DSL Plugin 1.48 Jenkins 2.7.4
Labels:
template dsl
Priority:
Minor
Reporter:
Christopher Shannon
I am using the "configure" command to directly modify the XML since the Template Plugin is not supported directly. This is simple groovy code that produces (in my opinion) a false ArrayIndexOutOfBoundsException:
job("Template Output Job") {
String[] templates = ["Template1", "Template2"]
for (int i = 0; i < templates.length; i++) {
configure {
it / "builders" << "hudson.plugins.templateproject.ProxyBuilder" {
"projectName"(templates[i]);
}
}
}
}
I can easily fix this by using a temporary variable:
job("Template Output Job") {
String[] templates = ["Template1", "Template2"]
for (int i = 0; i < templates.length; i++) {
String template = templates[i];
configure {
it / "builders" << "hudson.plugins.templa
[JIRA] (JENKINS-38747) Job DSL: strange behavior from "configure"
Title: Message Title Christopher Shannon commented on JENKINS-38747 Re: Job DSL: strange behavior from "configure" I appreciate the explanation, and can certainly update to use an iterator instead. The only thing I don't quite get is why my second code example works correctly. Based on your explanation, when the XML is finally generated, wouldn't I expect to see my second array element used twice? If both configure calls only capture the "template" variable but not the value, then shouldn't my XML have two calls to "Template 2"? This was changed from a bug report to a Groovy lesson... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38747) Job DSL: strange behavior from "configure"
Title: Message Title Christopher Shannon commented on JENKINS-38747 Re: Job DSL: strange behavior from "configure" Ah, makes perfect sense. Thanks for the explanation! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38741) Job DSL execution is occassionally slow on large scale production servers
Title: Message Title Christopher Shannon commented on JENKINS-38741 Re: Job DSL execution is occassionally slow on large scale production servers Waiting for locks could certainly explain variability in the latency of a Job DSL run, which I suppose is the crux of this original issue, but would not explain the high load that we see on the master node while the job is running... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38741) Job DSL execution is occassionally slow on large scale production servers
Title: Message Title Christopher Shannon commented on JENKINS-38741 Re: Job DSL execution is occassionally slow on large scale production servers I suppose that this is possible. I have looked at the output of the monitoring plugin and the spikes in CPU utilization don't necessarily correlate to drops in memory utilization, which I'd expect from a garbage collection... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15388) ClearCase UCM plugin does not support matrix builds - our case 7391
Title: Message Title Christopher Shannon commented on JENKINS-15388 Re: ClearCase UCM plugin does not support matrix builds - our case 7391 I would further comment that the ClearCase UCM plugin does not appear to work on matrix builds at all, regardless of promotion issue described by this bug's originator. Even when choosing the ANY promotion level, the per-configuration/child jobs attempt to create a CC stream with a comma in the name and fail miserably. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38741) Job DSL execution is occassionally slow on large scale production servers
Title: Message Title Christopher Shannon commented on JENKINS-38741 Re: Job DSL execution is occassionally slow on large scale production servers Martin Nonnenmacher: Super informative comment. I can confirm on our side that we do have the Job Config History plugin, many jobs, and likely many jobs without a retention policy in place. That probably goes a long way to explaining the server load we're seeing on our end. The that isn't clear, though, what do you mean by "many more jobs are updated than required"? Is Jenkins updating jobs that aren't generated by that particular run of the Job DSL? Or is it just the job history of those generated jobs that increases the load? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18486) When providing multiple jobs to run, support running them one after another and not all together
Title: Message Title Christopher Shannon commented on JENKINS-18486 Re: When providing multiple jobs to run, support running them one after another and not all together My use case involves one job triggering several other jobs that all specify "Build on the same node". I also have dependencies between these jobs, and the current behavior of randomly ordering those triggered jobs is not ideal. Note that building everything on the same node (with only one executor) precludes me from using the build step. In my opinion, these triggered builds should clearly be guaranteed to be queued up in the exact order that they are specified in the job configuration. If there are multiple executors available, certainly they can run in parallel. But everything would naturally run sequentially if the user specifies that everything runs on the same node. This seems like a very small change that could be made to solve this, and I'm really surprised that this wasn't already the default behavior. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30526) Summary Page for telling what template is used in which jobs or vice versa.
Title: Message Title Christopher Shannon commented on JENKINS-30526 Re: Summary Page for telling what template is used in which jobs or vice versa. We just identified this same issue, and I'm glad to see that a feature request was already filed. We are starting to encapsulate common functionality from our jobs into templates that everyone can reuse. The big problem with this approach is that there is no linkage between a particular template job and all of the users of that template. So, when I go to modify one of these common templates, I have no idea who will be impacted. We already maintain too many teams/users/jobs where a manual search would be impractical. Also, just a quick note that this could be shown on the template job itself (just like upstream/downstream jobs appear) or as a separate functionality similar to what the Plugin Usage Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Usage+Plugin+%28Community%29) provides. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18486) When providing multiple jobs to run, support running them one after another and not all together
Title: Message Title Christopher Shannon commented on JENKINS-18486 Re: When providing multiple jobs to run, support running them one after another and not all together Just a note for folks running into the same situation as me, I was able to workaround my issue by setting a "Quiet period" for my post-build parameterized jobs. So, I really want Job 1, Job 2, and Job 3 to be kicked off in that order. With default settings, and regardless of how they are ordered in the trigger step, they will be queued up in a seemingly random order by this plugin. If I put a quiet period of 5 seconds for Job 1, 10 seconds for Job 2, and 15 seconds for Job 3, however, then I can ensure that they execute in the order that I want. I can actually look at the build queue and see the jobs reorder themselves after their respective quiet periods end. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34605) Delivery Pipeline shows "null" for activity descriptions from CC-UCM
Title: Message Title Christopher Shannon updated an issue Jenkins / JENKINS-34605 Delivery Pipeline shows "null" for activity descriptions from CC-UCM Change By: Christopher Shannon Component/s: delivery-pipeline-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34605) Delivery Pipeline shows "null" for activity descriptions from CC-UCM
Title: Message Title Christopher Shannon commented on JENKINS-34605 Re: Delivery Pipeline shows "null" for activity descriptions from CC-UCM I removed the delivery-pipeline-plugin from the component list, as this looks to be an issue that can be resolved by the CC-UCM plugin on its own. It also looks like it could be a simple change, and very helpful to us if it was fixed... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37092) Fix for NPE in CCUCM Plugin
Title: Message Title
Christopher Shannon created an issue
Jenkins / JENKINS-37092
Fix for NPE in CCUCM Plugin
Issue Type:
Bug
Assignee:
Praqma Support
Components:
clearcase-ucm-plugin
Created:
2016/Aug/01 1:21 PM
Environment:
Jenkins 2.7.1 CCUCM 1.6.9
Labels:
clearcase-ucm
Priority:
Minor
Reporter:
Christopher Shannon
A null check needs to be wrapped around CheckoutTask.java:207. if (buildProject.equals("")) { buildProject = null; } Should be: if ((buildProject != null) && buildProject.equals("")) { buildProject = null; } I was able to cause this NPE by using Job DSL and not entering a value for buildProject (or including buildProject()). This caused config.xml to not have an entry for buildProject and caused this variable to be null at this point. I was able to get past this by specifying buildProject("") in my Job DSL script. It seems like the code should be made more robust here to handle this case better.
[JIRA] (JENKINS-37117) Pipeline support for CCUCM Plugin
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-37117 Pipeline support for CCUCM Plugin Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm-plugin Created: 2016/Aug/02 11:44 AM Labels: clearcase-ucm pipeline Priority: Minor Reporter: Christopher Shannon I don't see anything in the backlog that capture adding pipeline support to the ClearCase UCM Plugin. Hopefully this is already in the works, because as of right now this is keeping us from being able to use a pipeline for our jobs. Add Comment
[JIRA] (JENKINS-37119) Build Blocker Plugin needs a concept of a delay before checking the queue
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-37119 Build Blocker Plugin needs a concept of a delay before checking the queue Issue Type: Improvement Assignee: Unassigned Components: build-blocker-plugin Created: 2016/Aug/02 2:25 PM Labels: parameterized-trigger Priority: Minor Reporter: Christopher Shannon There is an issue with the Build Blocker Plugin and jobs chained together by the Parameterized Trigger Plugin, but is potentially easy to resolve... Issue: Three jobs configured to kick off the next one when it is finished. Job 1 -> Job 2 -> Job 3 I want to block Job 1 if Job 2 or Job 3 is queued or running. This will ensure that the above pipeline does not start again until a previous one finishes. A race condition currently exists which makes this impossible to implement: 1. Job 1 runs. 2. Job 1 finishes, Job 2 queued. 3. Job 2 runs. 4. Job 1 queues up, but is blocked. 5. Job 2 finishes, Job 3 queued. 6. Job 1 runs before Job 3. I do not know the code, but at the time that a blocking job finishes, it would be nice if the Build Blocker Plugin could delay its decision whether to run or not. This would allow Job 3 to get queued, and would stop Job 1 from running until the entire pipeline is finished.
[JIRA] (JENKINS-40198) allow scanning and retrieval of a pipeline job inside the pipeline
Title: Message Title Christopher Shannon commented on JENKINS-40198 Re: allow scanning and retrieval of a pipeline job inside the pipeline I'm really surprised this is not supported already. I'm running into the issue that our email notifications from the pipeline itself cannot include the build failure reasons, because all of the build failure analysis runs after the pipeline is done. This plugin provides the first level of triage for me, but I can't communicate that in our custom email notifications right now which is frustrating... 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-51105) JEP-200 compatibility for ClearCase UCM Plugin
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-51105 JEP-200 compatibility for ClearCase UCM Plugin Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm-plugin Created: 2018-05-03 12:57 Environment: Jenkins 2.107.1 ClearCase UCM Plugin 1.7.0 Labels: JEP-200 Priority: Critical Reporter: Christopher Shannon Many of these seen, but all seemingly related to net.praqma.clearcase.ucm.entities.Stream. SEVERE: Failed to save build record java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:1923) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) a
[JIRA] (JENKINS-51105) JEP-200 compatibility for ClearCase UCM Plugin
Title: Message Title Christopher Shannon commented on JENKINS-51105 Re: JEP-200 compatibility for ClearCase UCM Plugin I started down this path, but gave up after adding all of these (first three probably not related to this plugin). I could not keep rebooting my production server to keep expanding this list and gave up... -Dhudson.remoting.ClassFilter=java.io.PrintStream,java.util.Formatter,java.io.FileOutputStream,net.praqma.clearcase.ucm.entities.Stream,net.praqma.clearcase.PVob,net.praqma.clearcase.ucm.entities.Project,net.praqma.clearcase.ucm.entities.Baseline,net.praqma.clearcase.ucm.entities.Component,net.praqma.clearcase.ucm.entities.Activity,net.praqma.clearcase.ucm.entities.Changeset,net.praqma.clearcase.ucm.entities.Version,net.praqma.clearcase.Branch,net.praqma.clearcase.ucm.entities.UCMEntity Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-35979) Newline in activity headline breaks build
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-35979 Newline in activity headline breaks build Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm-plugin Created: 2016/Jun/15 7:33 PM Environment: Jenkins 2.6 ClearCase UCM Plugin 1.6.9 Labels: clearcase-ucm Priority: Minor Reporter: Christopher Shannon To reproduce, simply create an activity with a newline in the headline and trigger a build. When the plugin is comparing the new baseline to the previous one, an exception is thrown and the build fails: java.io.IOException: remote file operation failed: C:\jenkins\workspace\... at hudson.remoting.Channel@1aa6333a:: java.io.IOException: at hudson.FilePath.act(FilePath.java:1014) at hudson.FilePath.act(FilePath.java:996) at net.praqma.hudson.scm.CCUCMScm.initializeWorkspace(CCUCMScm.java:549) at net.praqma.hudson.scm.CCUCMScm.checkout(CCUCMScm.java:339) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.io.IOException: at net.praqma.hudson.remoting.CheckoutTask.invoke(CheckoutTask.java:125) at net.praqma.hudson.remoting.CheckoutTa
[JIRA] [clearcase-plugin] (JENKINS-25323) Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
Title: Message Title Christopher Shannon assigned an issue to Praqma Support Jenkins / JENKINS-25323 Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action Change By: Christopher Shannon Assignee: Ken Dang Praqma Support 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] [clearcase-plugin] (JENKINS-25323) Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
Title: Message Title Christopher Shannon commented on JENKINS-25323 Re: Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action Since this appears to be an issue with the ClearCase plugin, trying to get this assigned properly... 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] [clearcase-plugin] (JENKINS-25323) Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
Title: Message Title Christopher Shannon updated an issue Jenkins / JENKINS-25323 Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action Change By: Christopher Shannon Component/s: clearcase-plugin Component/s: coverity-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] [coverity-plugin] (JENKINS-31508) Coverity results not displayed if "Perform Coverity build, analysis and commit" is not selected
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-31508 Coverity results not displayed if "Perform Coverity build, analysis and commit" is not selected Issue Type: Bug Assignee: Ken Dang Components: coverity-plugin Created: 11/Nov/15 8:37 PM Environment: Coverity Plugin 1.6.0 Jenkins Labels: coverity plugins Priority: Blocker Reporter: Christopher Shannon There is a code block in IndioToolHandler, FresnoToolHandler, and PreFresnoToolHandler which fetches the defects for the snapshot ID just committed. This code block is conditional on invocationAssistance != null, even though invocationAssistance is not used in this code. The end result is that when the "Perform Coverity build, analysis and commit" checkbox is not selected, invocationAssistance will be null, and this code will not run. This means that the graphs are not populated and the link to the defects does not exist for the build. I noticed this because our Coverity server was just upgr
[JIRA] [coverity-plugin] (JENKINS-31541) Coverity plugin needs to obfuscate user passwords
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-31541 Coverity plugin needs to obfuscate user passwords Issue Type: Improvement Assignee: Ken Dang Components: coverity-plugin Created: 13/Nov/15 1:38 PM Labels: plugins coverity security Priority: Major Reporter: Christopher Shannon Currently the user's Coverity credentials are stored in the jenkins.plugins.coverity.CoverityPublisher.xml file in plain-text. This breaks many security requirements in our production environment. The password needs to be obfuscated/encrypted in some fashion. Add Comment
[JIRA] [clearcase-ucm-plugin] (JENKINS-33565) CCUCM Documentation Update
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-33565 CCUCM Documentation Update Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm-plugin Created: 15/Mar/16 6:11 PM Priority: Minor Reporter: Christopher Shannon The documentation for Child and Sibling mode clearly indicates that the baseline is only delivered to the target stream if the build is successful. When looking at the console output, though, it appears that the delivery happens first and then the build steps. It looks like if the build fails, the delivery is then reverted. This flow brings up several questions that I'm not able to find answers to. I'm sure that there are good reasons for why it happens this way, so please update the documentation to reflect this additional detail. Add Comment
[JIRA] [git-client-plugin] (JENKINS-34203) Webpage for Git Client Plugin is empty
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-34203 Webpage for Git Client Plugin is empty Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2016/Apr/13 2:26 PM Priority: Minor Reporter: Christopher Shannon The following page is empty and does not provide links to download the plugin. https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin Add Comment
[JIRA] [git-client-plugin] (JENKINS-34203) Webpage for Git Client Plugin is empty
Title: Message Title Christopher Shannon commented on JENKINS-34203 Re: Webpage for Git Client Plugin is empty I understand that it may not fit here, but I'm just an outside user and am letting you know that I cannot download the plugin right now. I would think that would be something important to the developers of the project... I have no idea where this issue should be filed instead. 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-34203) Webpage for Git Client Plugin is empty
Title: Message Title Christopher Shannon commented on JENKINS-34203 Re: Webpage for Git Client Plugin is empty And it's fixed - thanks so much for reporting this in the right place! 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] [cloudbees-folder-plugin] (JENKINS-34539) The global "system message" appears in every folder
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-34539 The global "system message" appears in every folder Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 2016/May/02 4:39 PM Environment: Jenkins 1.646 Folders Plugin 5.9 Labels: plugin plugins Priority: Minor Reporter: Christopher Shannon The global system message in Jenkins (Manage Jenkins -> Configure System -> System Message) clearly indicates that this message should only be shown on the "top page" (which is exactly what I want). In addition to the top page, though, I see the same exact message replicated in every folder. If there is a folder description, it gets appended to this system message.
[JIRA] [template-project-plugin] (JENKINS-34543) Failure email generated for ClearCase UCM job when changing node name
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-34543 Failure email generated for ClearCase UCM job when changing node name Issue Type: Bug Assignee: huybrechts Components: template-project-plugin Created: 2016/May/02 8:42 PM Environment: Jenkins 1.646 ClearCase UCM Plugin 1.6.9 Template Project Plugin 1.5.2 Labels: plugin plugins Priority: Minor Reporter: Christopher Shannon I believe that this issue is specific to the Template Project Plugin when the build steps result in "NOT_BUILT". I'm seeing some problems when changing node names on an existing ClearCase UCM job. Here are the steps to reproduce: Create a job which uses the ClearCase UCM Plugin for SCM. Set the job to Poll Self and Prom
[JIRA] [template-project-plugin] (JENKINS-34543) Failure email generated for ClearCase UCM job when changing node name
Title: Message Title
Christopher Shannon updated an issue
Jenkins / JENKINS-34543
Failure email generated for ClearCase UCM job when changing node name
Change By:
Christopher Shannon
I believe that this issue is specific to the Template Project Plugin when the build steps result in "NOT_BUILT".I'm seeing some problems when changing node names on an existing ClearCase UCM job. Here are the steps to reproduce:# Create a job which uses the ClearCase UCM Plugin for SCM.# Set the job to Poll Self and Promotion Level INITIAL.# Set the job to poll SCM at a certain rate.# Set the job to use publishers from another job.# In this other job, configure an email notification upon failure.# Map this job to a given node.# Run the job enough to process all INITIAL baselines on the given stream (such that the job doesn't have anything to do until a new baseline is created).# Change the name of the node.What happens is that the job will execute the next time it polls:{{Started on May 2, 2016 8:43:14 AMWorkspace is offline.Scheduling a new build to get a workspace. (nonexisting_workspace)Done. Took 1 msChanges found }}The job will then not build because there are no baselines available to process, but I get an email notification of a failed build.{{08:38:43 [CCUCM] * Promotion level: INITIAL08:38:43 08:38:45 ERROR: No valid baselines found08:38:45 [TemplateProject] Starting publishers from: 08:38:45 Sending e-mails to: 08:38:46 [TemplateProject] Successfully performed publishers from: 08:38:46 [CCUCM] Nothing to do!08:38:46 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:38:46 Notifying upstream projects of job completion08:38:46 Finished: NOT_BUILT }}When I do a similar flow, but without using the Template Project Plugin, the email notification publisher is completely suppressed:{{08:43:22 [CCUCM] * Promotion level: INITIAL08:43:22 08:43:25 ERROR: No valid baselines found08:43:25 [WARNINGS] Skipping publisher since build result is FAILURE08:43:25 [CCUCM] Nothing to do!08:43:25 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:43:25 Notifying upstream projects of job completion08:43:25 Finished: NOT_BUILT }}In this case, I really don't want the email notification of a failure, because it really isn't a failed build. Also, I'm sure that there is a simpler way to initiate a "NOT_BUILT" condition without using the ClearCase UCM Plugin, but i don't know what that is...
Add Comment
[JIRA] [template-project-plugin] (JENKINS-34543) Failure email generated for ClearCase UCM job when changing node name
Title: Message Title
Christopher Shannon updated an issue
Jenkins / JENKINS-34543
Failure email generated for ClearCase UCM job when changing node name
Change By:
Christopher Shannon
I believe that this issue is specific to the Template Project Plugin when the build steps result in "NOT_BUILT".I'm seeing some problems when changing node names on an existing ClearCase UCM job. Here are the steps to reproduce:# Create a job which uses the ClearCase UCM Plugin for SCM.# Set the job to Poll Self and Promotion Level INITIAL.# Set the job to poll SCM at a certain rate.# Set the job to use publishers from another job.# In this other job, configure an email notification upon failure.# Map this job to a given node.# Run the job enough to process all INITIAL baselines on the given stream (such that the job doesn't have anything to do until a new baseline is created).# Change the name of the node.What happens is that the job will execute the next time it polls:{{ Started on May 2, 2016 8:43:14 AMWorkspace is offline.Scheduling a new build to get a workspace. (nonexisting_workspace)Done. Took 1 msChanges found}}The job will then not build because there are no baselines available to process, but I get an email notification of a failed build.{{ 08:38:43 [CCUCM] * Promotion level: INITIAL08:38:43 08:38:45 ERROR: No valid baselines found08:38:45 [TemplateProject] Starting publishers from: 08:38:45 Sending e-mails to: 08:38:46 [TemplateProject] Successfully performed publishers from: 08:38:46 [CCUCM] Nothing to do!08:38:46 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:38:46 Notifying upstream projects of job completion08:38:46 Finished: NOT_BUILT}}When I do a similar flow, but without using the Template Project Plugin, the email notification publisher is completely suppressed:{{ 08:43:22 [CCUCM] * Promotion level: INITIAL08:43:22 08:43:25 ERROR: No valid baselines found08:43:25 [WARNINGS] Skipping publisher since build result is FAILURE08:43:25 [CCUCM] Nothing to do!08:43:25 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:43:25 Notifying upstream projects of job completion08:43:25 Finished: NOT_BUILT}}In this case, I really don't want the email notification of a failure, because it really isn't a failed build. Also, I'm sure that there is a simpler way to initiate a "NOT_BUILT" condition without using the ClearCase UCM Plugin, but i don't know what that is...
Add Comment
[JIRA] [template-project-plugin] (JENKINS-34543) Failure email generated for ClearCase UCM job when changing node name
Title: Message Title
Christopher Shannon updated an issue
Jenkins / JENKINS-34543
Failure email generated for ClearCase UCM job when changing node name
Change By:
Christopher Shannon
I believe that this issue is specific to the Template Project Plugin when the build steps result in "NOT_BUILT".I'm seeing some problems when changing node names on an existing ClearCase UCM job. Here are the steps to reproduce:# Create a job which uses the ClearCase UCM Plugin for SCM.# Set the job to Poll Self and Promotion Level INITIAL.# Set the job to poll SCM at a certain rate.# Set the job to use publishers from another job.# In this other job, configure an email notification upon failure.# Map this job to a given node.# Run the job enough to process all INITIAL baselines on the given stream (such that the job doesn't have anything to do until a new baseline is created).# Change the name of the node.What happens is that the job will execute the next time it polls: {{ Started on May 2, 2016 8:43:14 AMWorkspace is offline.Scheduling a new build to get a workspace. (nonexisting_workspace)Done. Took 1 msChanges found }} The job will then not build because there are no baselines available to process, but I get an email notification of a failed build. {{ 08:38:43 [CCUCM] * Promotion level: INITIAL08:38:43 08:38:45 ERROR: No valid baselines found08:38:45 [TemplateProject] Starting publishers from: 08:38:45 Sending e-mails to: 08:38:46 [TemplateProject] Successfully performed publishers from: 08:38:46 [CCUCM] Nothing to do!08:38:46 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:38:46 Notifying upstream projects of job completion08:38:46 Finished: NOT_BUILT }} When I do a similar flow, but without using the Template Project Plugin, the email notification publisher is completely suppressed: {{ 08:43:22 [CCUCM] * Promotion level: INITIAL08:43:22 08:43:25 ERROR: No valid baselines found08:43:25 [WARNINGS] Skipping publisher since build result is FAILURE08:43:25 [CCUCM] Nothing to do!08:43:25 Build step 'ClearCase UCM' changed build result to NOT_BUILT08:43:25 Notifying upstream projects of job completion08:43:25 Finished: NOT_BUILT }} In this case, I really don't want the email notification of a failure, because it really isn't a failed build. Also, I'm sure that there is a simpler way to initiate a "NOT_BUILT" condition without using the ClearCase UCM Plugin, but i don't know what that is...
Add Comment
[JIRA] [role-strategy-plugin] (JENKINS-34545) Assigning roles is case sensitive, and it shouldn't be
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-34545 Assigning roles is case sensitive, and it shouldn't be Issue Type: Bug Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2016/May/02 9:07 PM Environment: Jenkins 1.646 Role-based Authorization Strategy 2.2.0 Labels: plugin plugins security Priority: Minor Reporter: Christopher Shannon Steps to reproduce: Create a user in Jenkins own user database with upper-case letters. Assign a role to this user, but use lower-case letters. Note that going back into Assign Roles shows the icon indicating that this user is valid.
[JIRA] [robot-plugin] (JENKINS-22603) Add support Dashboard View
Title: Message Title Christopher Shannon commented on JENKINS-22603 Re: Add support Dashboard View I am looking for the same capability, and I don't believe that this is a lot of work. There must be some interface that is used because Robot Framework results already partially flow up to the Dashboard view as test results. Install Dashboard View plugin. In a Jenkins folder with a RF test, click the plus sign to create a new view. Select Dashboard View. Under the Jobs section, select the RF test. Click Add Dashboard Portlet to bottom of the view. Select Test Statistics Chart. Repeat for Test Statistics Grid and Test Trend Chart. Note that the Test Trend Chart looks great and shows an excellent trend chart. Also note that the other two portlets are empty/broken. It looks to me like RF is publishing test results in a way that the Dashboard can already partially consume. My hope would be that fixing the rest would be relatively easy. Final note - I have found that JUnit results flow to the Dashboard correctly, in case the code from there could be used as a reference. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [coverity-plugin] (JENKINS-25323) Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
Title: Message Title Christopher Shannon commented on JENKINS-25323 Re: Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action I have seen this same issue - not sure if it is an interaction between the Coverity and ClearCase 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] [coverity-plugin] (JENKINS-25323) Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
Title: Message Title
Christopher Shannon edited a comment on JENKINS-25323
Re: Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
I have seen this same issue - not sure if and it is appears to be an interaction between the Coverity and ClearCase plugins. The real problem seems to be this line in BuildUtils in the ClearCase plugin . {code:java}return builtOn . createLauncher(StreamTaskListener.NULL).isUnix();{code}This isRunningOnUnix method is called as the launcher is getting created (specifically when building the set of env variables). The call above tries to create a new launcher during this process which leads to the recursion loop / stack overflow.
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] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Christopher Shannon commented on JENKINS-48300 Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 In case it helps anyone else who stumbles across this thread, I just ran into this problem and was able to figure out why (which was not a durable-step, or Jenkins thing, but something I was doing wrong). I basically had three different stages in my pipeline using static code analysis tools. Each of these tools can be CPU intensive and by default are happy to consume as many cores as are available on the host. We also have multiple Jenkins executors for each of our nodes (e.g. 4 executors on a 4 core node). This problem presented itself when I put these three stages in a parallel block, and they all mapped to three executors on the same physical node. When they started analyzing the code, I'm sure that my system load was completely railed (i.e. 2 if not 3 processes each trying to peg every core to 100% CPU). It is no surprise that this error message would occur in this scenario. Sure, Jenkins could have been more patient, but it also pointed to a pipeline architecture problem on my end. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186889.1511985014000.10809.1580735761448%40Atlassian.JIRA.
[JIRA] [core] (JENKINS-5758) resolve variables in artifact filesets
Title: Message Title Christopher Shannon commented on JENKINS-5758 Re: resolve variables in artifact filesets I'm also running into this issue, especially when using ClearCase. Real-world example: CC plugin specifies a long view name, with a directory of the same name created under the workspace. Right now, the archive artifacts path needs to hard-code this directory name in order to find files. I then reorganize my projects using the CloudBees folder plugin, which changes my view names slightly, and all of my archive artifacts commands will fail if I don't change each of them individually. Is this feature request to include environment variables in the archive command really not being considered? 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.
