[JIRA] (JENKINS-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.
Title: Message Title
Nick Sonneveld updated an issue
Jenkins / JENKINS-39092
Pipeline branches SCM polling properties for multibranch has broken behaviour.
Change By:
Nick Sonneveld
We're attempting to configure a pipeline multibranch folder such that 'default' is always built but feature branches are only built daily. We did this by suppressing automatic SCM triggering for all branches except 'default', then configuring a separate pollSCM in the jenkinsfile for each branch. However we're seeing issues where feature branches that have changes are not built for days while sometimes a branch will be triggered many times for the same changeset.Multiple jobs for the same changeset are triggered. The first by "Branch indexing" and the later ones by "Started by an SCM change". The logs show "Dependent changes detected"No other polling is configured. Removing the pipelineTriggers/pollSCM property seems to stop repeat builds (but won't give you daily builds) Our Jenkinsfile starts with this:{noformat}def alwaysBuild = (env.BRANCH_NAME == "default" || env.BRANCH_NAME ==~ /CompanyName-.*/);properties([overrideIndexTriggers(alwaysBuild), pipelineTriggers([pollSCM('@daily')])]);{noformat}Multibranch folder is configured with properties overrides:- "named branches get different properties" exceptions: "default": no properties "us*,d*,ts*": Suppess automatic SCM triggering.And every commit will notify jenkins via {noformat}curl -v http://jenkins:8080/mercurial/notifyCommit?url="">{noformat}
Add Comment
This message was
[JIRA] (JENKINS-38443) Pollscm trigger runs the job twice for the same commit
Title: Message Title Nick Sonneveld commented on JENKINS-38443 Re: Pollscm trigger runs the job twice for the same commit Linking to related JENKINS-39092 . The difference is that no polling interval is set, only change notifications 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-30183) Openstack Cloud Plugin does not wait until the user data script completes
Title: Message Title Joshua Harlow commented on JENKINS-30183 Re: Openstack Cloud Plugin does not wait until the user data script completes Ya, that idea is similar to what I'm doing at godaddy as well. Its not ideal, but basically using a shell script to add the user (and making sure adding the user last) will at least ensure jenkins can't login until the rest of the user script is finished... Best I've seen so far (though IMHO far from the best it could be). 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-39092) Pipeline branches SCM polling properties for multibranch has broken behaviour.
Title: Message Title
Nick Sonneveld created an issue
Jenkins / JENKINS-39092
Pipeline branches SCM polling properties for multibranch has broken behaviour.
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
build 125 Screen Shot 2016-10-19 at 4.11.14 PM.png, build 126 Screen Shot 2016-10-19 at 4.11.28 PM.png, job config - Screen Shot 2016-10-19 at 4.09.04 PM.png, multibranch config Screen Shot 2016-10-19 at 4.10.24 PM.png, multiple builds - Screen Shot 2016-10-19 at 4.10.53 PM.png
Components:
mercurial-plugin, pipeline, workflow-multibranch-plugin
Created:
2016/Oct/19 5:28 AM
Environment:
Jenkins 2.26
Priority:
Critical
Reporter:
Nick Sonneveld
We're attempting to configure a pipeline multibranch folder such that 'default' is always built but feature branches are only built daily. However we're seeing issues where feature branches that have changes are not built for days while sometimes a branch will be triggered many times for the same changeset. Multiple jobs for the same changeset are triggered. The first by "Branch indexing" and the later ones by "Started by an SCM change". The logs show "Dependent changes detected" No other polling is configured. Our Jenkinsfile starts with this:
def alwaysBuild = (env.BRANCH_NAME == "default" || env.BRANCH_NAME ==~ /CompanyName-.*/);
properties([overrideIndexTriggers(alwaysBuild), pipelineTriggers([pollSCM('@daily')])]);
[JIRA] (JENKINS-39091) Jira plugin fails to log in to Jira site after dependency updates
Title: Message Title Tomas Zaleniakas created an issue Jenkins / JENKINS-39091 Jira plugin fails to log in to Jira site after dependency updates Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2016/Oct/19 5:05 AM Environment: Jenkins 2.25 Latest compiled Jira plugin Priority: Critical Reporter: Tomas Zaleniakas This commit broke the log in mechanizm https://github.com/jenkinsci/jira-plugin/commit/ea4deb1fabe92cb89736d432cef6d8b36e3b19db Revert dependency or update usage on plugin. Add Comment
[JIRA] (JENKINS-37229) CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone
Title: Message Title Mark Waite commented on JENKINS-37229 Re: CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone Sean Flanigan, you're correct that it is more a bug than a feature, though it appears to be a bug in command line git 1.8.3.1. That version of command line git does not seem to have full support for shallow clone. 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-37229) CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37229 CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone Change By: Mark Waite 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-37229) CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone
Title: Message Title Sean Flanigan commented on JENKINS-37229 Re: CLI Git 1.8.3.1 (RHEL 7) reports "git fetch-pack: expected shallow list" on pipeline job shallow clone Mark Waite Should this be marked as a bug rather than an improvement? What would you say is the expected (or enhanced) behaviour? 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-39085) namespaces don't seem to be created
Title: Message Title Jae Gangemi commented on JENKINS-39085 Re: namespaces don't seem to be created could that be documented somewhere? 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-39084) PROD: cbwf-controller component is causing Jenkins's CPU to spike
Title: Message Title Sam Van Oort commented on JENKINS-39084 Re: PROD: cbwf-controller component is causing Jenkins's CPU to spike David Chou Which would suggest that user lookup is still proving to be a bottleneck in your setup (haven't seen that happen before with the UserDetails cache on though). That's tied to your security realm – setting hudson.model.User.SECURITY_243_FULL_DEFENSE=false may also resolve the issue (and would suggest the details cache needs more work). Unfortunately there's not really anything to be done about this from the stage view end of things, aside from using one of the overrides in your Jenkins config file to make it permanent: the problematic API is deeply embedded in Jenkins core, and the override I put in here simply avoids invoking it. No rabbits to pull out from my hat this time, I'm afraid. 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-39079) Record timestamps for pipeline jobs without filling the log file with console notes
Title: Message Title Steven G Brown updated an issue Jenkins / JENKINS-39079 Record timestamps for pipeline jobs without filling the log file with console notes Change By: Steven G Brown Summary: Timestamper plugin inserts encoded TimeStampNote when using in Record timestamps for pipeline job jobs without filling the log file with console notes 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-39079) Timestamper plugin inserts encoded TimeStampNote when using in pipeline job
Title: Message Title Steven G Brown assigned an issue to Unassigned The comment could be clearer. What it means is, pipeline jobs do not extend AbstractBuild and so they rely on console notes to work. I'd love to have the pipeline builds working without filling the log file with console notes, but no-one has implemented that yet. But the system property is checked as a boolean and since TimeStampNote.getSystemProperty() always returns a string its always true. No, it looks up the system property with that name. Have a look at the Javadoc for Boolean.getBoolean(String). Jenkins / JENKINS-39079 Timestamper plugin inserts encoded TimeStampNote when using in pipeline job Change By: Steven G Brown Issue Type: Bug New Feature Assignee: Steven G Brown Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39085) namespaces don't seem to be created
Title: Message Title Carlos Sanchez closed an issue as Not A Defect You are supposed to create it Jenkins / JENKINS-39085 namespaces don't seem to be created Change By: Carlos Sanchez Status: Open Closed Resolution: Not A Defect 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-39090) Upgrade from Credentials 2.1.6 to Credentials 2.1.7 prevents logins
Title: Message Title Cody Konior updated an issue Jenkins / JENKINS-39090 Upgrade from Credentials 2.1.6 to Credentials 2.1.7 prevents logins Change By: Cody Konior I've been using Credentials plugin 1. 2. 1. 6 with project-based AD security.Today after upgrading to Credentials plugin 1. 2. 1. 7 I was unable to login. I restarted Jenkins, I would get the login screen, but after entering credentials nothing would happen.I restarted a few times before rolling back by removing the credentials.jpi and restoring the .bak. After restarting Jenkins logins were working again. 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-39090) Upgrade from Credentials 2.1.6 to Credentials 2.1.7 prevents logins
Title: Message Title Cody Konior created an issue Jenkins / JENKINS-39090 Upgrade from Credentials 2.1.6 to Credentials 2.1.7 prevents logins Issue Type: Bug Assignee: Stephen Connolly Components: credentials-plugin Created: 2016/Oct/19 2:22 AM Environment: Jenkins 2.26, JRE 1.8.0_101-b13 x64, Windows Server 2012 R2, Priority: Major Reporter: Cody Konior I've been using Credentials plugin 1.2.6 with project-based AD security. Today after upgrading to Credentials plugin 1.2.7 I was unable to login. I restarted Jenkins, I would get the login screen, but after entering credentials nothing would happen. I restarted a few times before rolling back by removing the credentials.jpi and restoring the .bak. After restarting Jenkins logins were working again. Add Comment
[JIRA] (JENKINS-38789) Provide pipeline example that enables timestamper if is available
Title: Message Title Steven G Brown updated an issue Jenkins / JENKINS-38789 Provide pipeline example that enables timestamper if is available Change By: Steven G Brown Component/s: pipeline 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-38374) Cannot change user.timezone value
Title: Message Title Tadashi Aikawa commented on JENKINS-38374 Re: Cannot change user.timezone value I met this problem too. (Jenkins ver. 2.26) 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-33761) Ability to disable "resume" build.
Title: Message Title Charlie Groves commented on JENKINS-33761 Re: Ability to disable "resume" build. If true, that is a bug in the EC2 plugin. It is supposed to keep the agent connected for the entire duration of the build. Maybe the build finished before Jenkins came back? It doesn't really change that we'd prefer not to resume these builds. Pipeline does not restart any build steps when Jenkins is restarted. It simply lets the existing process continue running and displaying output (or it might have ended on its own during the Jenkins restart). Oh, it was my understanding that it'd continue to the next step after that? Does it only complete the current step and stop? 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-39017) archiveArtifacts produces an empty/erroneous log for Blue Ocean
Title: Message Title Michael Neale commented on JENKINS-39017 Re: archiveArtifacts produces an empty/erroneous log for Blue Ocean tyler croy got it - so the end result is ok IF there was a log. And in progress would be ok IF there was a log - fair to say? If so, I think we have enough to go on here. 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-39017) archiveArtifacts produces an empty/erroneous log for Blue Ocean
Title: Message Title Michael Neale assigned an issue to Michael Neale Jenkins / JENKINS-39017 archiveArtifacts produces an empty/erroneous log for Blue Ocean Change By: Michael Neale Assignee: Michael Neale 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-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Torben Knerr commented on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version It's 2016 and there is still no way to install a plugin at a specific version (inlcuding it's dependencies) from the commandline? 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-39089) ansicolor plugin 0.4.2 is not working with Jenkins ver. 1.651.2
Title: Message Title Sammi SINGH created an issue Jenkins / JENKINS-39089 ansicolor plugin 0.4.2 is not working with Jenkins ver. 1.651.2 Issue Type: Bug Assignee: Unassigned Components: ansicolor-plugin Created: 2016/Oct/18 11:33 PM Priority: Minor Reporter: Sammi SINGH AnsiColor plugin 0.4.2 is not working with Jenkins ver. 1.651.2 I'm using basic shell commands and looks like ANSi Color is not working. I have checked it under Build Environment and restarted Jenkins after the ANSI Color plugin installation. Add Comment
[JIRA] (JENKINS-39081) Cannot get property 'fullName' on null object
Title: Message Title Nick Sonneveld commented on JENKINS-39081 Re: Cannot get property 'fullName' on null object Duplicates JENKINS-38721 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-39087) Add ability to mark a multibranch pipeline as a favourite - NOT a branch
Title: Message Title Michael Neale commented on JENKINS-39087 Re: Add ability to mark a multibranch pipeline as a favourite - NOT a branch James Dumay we should think on this more. Having a favourite as a shortcut is not unreasonable, and may solve the related issue of what to do when there is no default branch... 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-39087) Add ability to mark a multibranch pipeline as a favourite - NOT a branch
Title: Message Title Michael Neale assigned an issue to James Dumay Jenkins / JENKINS-39087 Add ability to mark a multibranch pipeline as a favourite - NOT a branch Change By: Michael Neale Assignee: James Dumay 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-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch
Title: Message Title Michael Neale commented on JENKINS-38601 Re: Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch Perhaps a better solution is JENKINS-39087. If there is no master branch, you fav the MB folder and show no branch details (essentially just a shortcut, as requested) 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-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Michael Neale commented on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 Thanks Tom - you are a wizard. This will be in beta-10 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-39088) Improve OutOfMemory diagnostics in Jenkins Support Core
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-39088 Improve OutOfMemory diagnostics in Jenkins Support Core Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 2016/Oct/18 11:06 PM Priority: Minor Reporter: Oleg Nenashev Currently Jenkins can recover from OutOfMemory errors in particular cases, but there are known issues like channel hanging. They issue may stay unnoticed till it disappears from logs. In such case Jenkins admins may have no clue if it was a cause of connection hanging. Proposals: Record last OOM events in support bundles (if they happen after the restart) Add an administrative monitor with a warning (Jenkins restart is recommended in general) It may likely require patches in the Jenkins core Add Comment
[JIRA] (JENKINS-39087) Add ability to mark a multibranch pipeline as a favourite - NOT a branch
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39087 Add ability to mark a multibranch pipeline as a favourite - NOT a branch Change By: Michael Neale Summary: Add ability to mark a multibranch pipeline as a favourite - NOT a branch 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-39087) Add ability to mark a multibranch pipeline as a favourite
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-39087 Add ability to mark a multibranch pipeline as a favourite Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2016/Oct/18 10:59 PM Priority: Minor Reporter: Christopher Orr I have a multibranch pipeline that contains only GitHub Pull Requests — no branches. I would like to be able to mark the whole pipeline folder as a favourite — I'm not interested in any one particular branch (PR), as these are pretty much ephemeral. i.e. it's probably just a shortcut to the pipeline folder, but since it's one of my most-used pipeline folders, I'd like to have it at the top of my dashboard. Add Comment
[JIRA] (JENKINS-34637) pipeline DSL: timeout() does not work if withEnv() is enclosed
Title: Message Title Jesse Glick updated JENKINS-34637 Jenkins / JENKINS-34637 pipeline DSL: timeout() does not work if withEnv() is enclosed Change By: Jesse Glick Status: In Progress Review 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-39015) Support hudson.model.UnprotectedRootAction
Title: Message Title Denys Digtiar commented on JENKINS-39015 Re: Support hudson.model.UnprotectedRootAction Thank you Oliver Gondža! The workaround worked for me. 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-39086) Scan Credentials dropdown is always empty
Title: Message Title Greg Parsons updated an issue Jenkins / JENKINS-39086 Scan Credentials dropdown is always empty Change By: Greg Parsons Hi there,I am finding that no matter what I do. I do not have any credentials to select from the dropdown:!Screenshot 2016-10-18 14.32.04.png|thumbnail! !Screenshot 2016-10-18 14.31.48.png|thumbnail! !Screenshot 2016-10-18 14.31.15.png|thumbnail! I have added the credentials to the Github plugin in the Jenkins General Config and under the Github Pull Request Builder.Attached is the versions of all of the Github Plugins I am using:!Screenshot 2016-10-18 14 15 . 31 25 . 15 48 .png|thumbnail! Using Jenkins 2.26.Am I doing something wrong?This is not resolved by disabling CSRF Crumbs, and I am using NGINX, already looked over JENKINS-12875. 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
[JIRA] (JENKINS-39084) PROD: cbwf-controller component is causing Jenkins's CPU to spike
Title: Message Title David Chau commented on JENKINS-39084 Re: PROD: cbwf-controller component is causing Jenkins's CPU to spike The work around fixes the error but we are in Jenkins Version 2.7.4 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-39086) Scan Credentials dropdown is always empty
Title: Message Title Greg Parsons created an issue Jenkins / JENKINS-39086 Scan Credentials dropdown is always empty Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2016-10-18 14.31.15.png, Screenshot 2016-10-18 14.31.48.png, Screenshot 2016-10-18 14.32.04.png, Screenshot 2016-10-18 15.25.48.png Components: github-branch-source-plugin Created: 2016/Oct/18 10:34 PM Priority: Minor Reporter: Greg Parsons Hi there, I am finding that no matter what I do. I do not have any credentials to select from the dropdown: I have added the credentials to the Github plugin in the Jenkins General Config and under the Github Pull Request Builder. Attached is the versions of all of the Github Plugins I am using: Using Jenkins 2.26. Am I doing something wrong? This is not resolved by disabling CSRF Crumbs, and I am using NGINX, already looked over JENKINS-12875. Add Comment
[JIRA] (JENKINS-39084) PROD: cbwf-controller component is causing Jenkins's CPU to spike
Title: Message Title
David Chau updated an issue
Jenkins / JENKINS-39084
PROD: cbwf-controller component is causing Jenkins's CPU to spike
Change By:
David Chau
Within the Jenkin Pipeline View, any build that contains {code:_javascript_}cbwf-controller{code}, is causing a HTTP GET request to https://example.com/job/project/job/BRANCH_NAME/3/wfapi/changesets?_=1476824899808.Each branch of a project on initial load will make a request to that endpoint. That will then cause the Jenkins process spike because it is trying to fulfill all of the requests.An example of the element which has that controller is {code:_javascript_}{code} Build #10 will cause a GET request while build #9 wouldn't
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,
[JIRA] (JENKINS-39084) PROD: cbwf-controller component is causing Jenkins's CPU to spike
Title: Message Title Sam Van Oort commented on JENKINS-39084 Re: PROD: cbwf-controller component is causing Jenkins's CPU to spike David Chau The cause is a Jenkins core change to fix SECURITY-243, which makes user lookup extremely expensive – this is now fixed, please see JENKINS-35493 and upgrade to Jenkins 2.7.3 or later. There's a workaround for people not yet able to update, and documented on the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin#PipelineStageViewPlugin-ConfigurableProperties%3A Set property com.cloudbees.workflow.rest.external.ChangeSetExt.resolveCommitAuthors to "false" to disable user lookup for changesets. This can be set at runtime to test the impact and should make your problem go away nearly immediately. 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-23309) Upstream changes are not displayed for Folder contained jobs
Title: Message Title Rob Petti resolved as Fixed Jenkins / JENKINS-23309 Upstream changes are not displayed for Folder contained jobs Change By: Rob Petti Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39084) PROD: cbwf-controller component is causing Jenkins's CPU to spike
Title: Message Title Sam Van Oort resolved as Fixed Closing as duplicate of existing issue with documented workaround and sustainable fix. Jenkins / JENKINS-39084 PROD: cbwf-controller component is causing Jenkins's CPU to spike Change By: Sam Van Oort Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-39084) PROD: cbwf-controller component is causing Jenkins's CPU to spike
Title: Message Title David Chau updated an issue Jenkins / JENKINS-39084 PROD: cbwf-controller component is causing Jenkins's CPU to spike Change By: David Chau Attachment: Screen Shot 2016-10-18 at 3.12.54 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39084) PROD: cbwf-controller component is causing Jenkins's CPU to spike
Title: Message Title
David Chau updated an issue
Jenkins / JENKINS-39084
PROD: cbwf-controller component is causing Jenkins's CPU to spike
Change By:
David Chau
Within the Jenkin Pipeline View, any build that contains ` {code:_javascript_} cbwf-controller ` {code} , is causing a HTTP GET request to https://example.com/job/project/job/BRANCH_NAME/3/wfapi/changesets?_=1476824899808.Each branch of a project on initial load will make a request to that endpoint. That will then cause the Jenkins process spike because it is trying to fulfill all of the requests.An example of the element which has that controller is {code:_javascript_}{code}
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-39084) PROD: cbwf-controller component is causing Jenkins's CPU to spike
Title: Message Title
David Chau updated an issue
Jenkins / JENKINS-39084
PROD: cbwf-controller component is causing Jenkins's CPU to spike
Change By:
David Chau
Within the Jenkin Pipeline View, any build that contains `cbwf-controller`, is causing a HTTP GET request to https://example.com/job/project/job/BRANCH_NAME/3/wfapi/changesets?_=1476824899808.Each branch of a project on initial load will make a request to that endpoint. That will then cause the Jenkins process spike because it is trying to fulfill all of the requests. An example of the element which has that controller is {code:_javascript_}{code}
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-30183) Openstack Cloud Plugin does not wait until the user data script completes
Title: Message Title Andrew Grimberg commented on JENKINS-30183 Re: Openstack Cloud Plugin does not wait until the user data script completes Donald Morton Here's how we do it in our various environments. We pass a user-data script that does what is explained in the README in the following location. https://github.com/zephyrproject-rtos/ci-management/tree/master/jenkins-scripts I'll note we do this for several different Jenkins systems that we support < /td> 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-39027) Blue Ocean does not start on Chrome/Firefox
Title: Message Title Michael Neale closed an issue as Fixed Jenkins / JENKINS-39027 Blue Ocean does not start on Chrome/Firefox Change By: Michael Neale Status: Resolved Closed Assignee: Michael Neale 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-39085) namespaces don't seem to be created
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-39085 namespaces don't seem to be created Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Oct/18 10:16 PM Priority: Minor Reporter: Jae Gangemi the plugin does not create the namespace i specify in the configuration. when i go to the kubes dashboard, it does not appear in the dropdown and it does not appear when i run the associated kubectl command. the documentation doesn't say anything about this, so i'm not sure if this is an actual bug or if it's my responsibility to create the namespaces in the cluster upfront. Add Comment
[JIRA] (JENKINS-39027) Blue Ocean does not start on Chrome/Firefox
Title: Message Title Michael Neale commented on JENKINS-39027 Re: Blue Ocean does not start on Chrome/Firefox @Michael Štědrý it's perfectly fine. Having a ticket is better than not, as if others see this, JIRA will suggest it and it will help gather evidence there is some install or upgrade race condition going on (or whatever it is...). It should work first time so it is worth opening this ticket. If you see this again with a fresh install some day, do re-open this or a new ticket! I will close this off. 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-39027) Blue Ocean does not start on Chrome/Firefox
Title: Message Title Michael Neale resolved as Fixed A reinstall solved this (not entirely sure why... so slightly suspicious.) Jenkins / JENKINS-39027 Blue Ocean does not start on Chrome/Firefox Change By: Michael Neale Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-39084) PROD: cbwf-controller component is causing Jenkins's CPU to spike
Title: Message Title David Chau created an issue Jenkins / JENKINS-39084 PROD: cbwf-controller component is causing Jenkins's CPU to spike Issue Type: Bug Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Oct/18 10:14 PM Environment: Chrome Priority: Major Reporter: David Chau Within the Jenkin Pipeline View, any build that contains `cbwf-controller`, is causing a HTTP GET request to https://example.com/job/project/job/BRANCH_NAME/3/wfapi/changesets?_=1476824899808. Each branch of a project on initial load will make a request to that endpoint. That will then cause the Jenkins process spike because it is trying to fulfill all of the requests. Add Comment
[JIRA] (JENKINS-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch
Title: Message Title Michael Neale commented on JENKINS-38601 Re: Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch Christopher Orr oh interesting. That is a case I didn't think of - when you filter. Would it bug you if you went to fav a pipeline and it told you to pick a branch? As in your case, it won't know that "develop" if the default branch even if all the stars aligned and there was a default branch (as that isn't the default branch necessarily, its just how filtered). I think simplest thing we can do is for MB that don't have master branch - we ask user to pick which branch if they try (or remove the star icon). Blue ocean has no concept of fav'ing a folder (the fact that a MB pipeline is actually a folder is a leaky implementation detail), as fav's apply to branches that do work only. There may be other strategies... Cliff Meyers we should talk about this some time. 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-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38601
Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch
Change By:
Michael Neale
Summary: if there is no master branch, if you try to favourite a MB pipeline (vs a specific branch) it does incorrect things. It should work out what the default branch is (or ask user) or at least tell them to pick a branch... (latter is easiest). +Steps:+# Click "New Item" and Create "Multibranch Pipeline" without branch "master".# Open Dashboard Jenkins. Check "Favorite" button for Multibranch Pipeline.# Open Jenkins Blue Ocean.*Actual Result:* New line for this job has been created in "Favorites" (grey colour). "Run" button hasn't worked.# Open Dashboard Jenkins -> this Multibranch Pipeline. Check "Favorite" button for any branch.*E.R. = A.R.:* No error. Favorites Job have displayed correctly in Jenkins Blue Ocean.# Disable "Favorite" for this job. # Open Jenkins Blue Ocean.# Click "Favorite" button for Multibranch Pipeline.*Expected Result:* Favorite label has been added. New line for this job has been created in "Favorites".*Actual Result:* Failed to load resource: the server responded with a status of 400 (Bad Request){noformat}{"message" : "no master branch to favorite","code" : 400,"errors" : [ ]}{noformat}# Disable "Favorite" for this job. *Expected Result:* Favorite label has been deleted.*Actual Result:* TypeError: undefined is not an object (evaluating 'favoriteToRemove._links')
Add Comment
This message was
[JIRA] (JENKINS-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38601 Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch Change By: Michael Neale Summary: Cannot mark Multibranch Pipeline as Favorite in Blue Ocean when no master branch 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-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38601 Cannot mark Multibranch Pipeline as Favorite in Blue Ocean Change By: Michael Neale Sprint: indian 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-38956) can't add clover publisher
Title: Message Title Toby Collett commented on JENKINS-38956 Re: can't add clover publisher I am also seeing this with Jenkins 2.19.1, clover plugin 4.7.0 (Upgraded recently from 4.5.0) javax.servlet.ServletException: java.lang.IllegalArgumentException: Unable to convert to class hudson.plugins.clover.targets.CoverageTarget at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at
[JIRA] (JENKINS-26148) Incorrect implementation of RetryStepExecution.stop
Title: Message Title Jesse Glick commented on JENKINS-26148 Re: Incorrect implementation of RetryStepExecution.stop Similarly, there is no apparent reason for ParallelStepExecution.bodies to exist except to pass on failures in stop. 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-39072) timeout step should include more logging/diagnostics information
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39072 timeout step should include more logging/diagnostics information Change By: Jesse Glick Labels: diagnostics robustness 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-39072) timeout step should include more logging/diagnostics information
Title: Message Title Jesse Glick commented on JENKINS-39072 Re: timeout step should include more logging/diagnostics information As part of JENKINS-34637 I am adding a message to the log, but something in getStatus is also in order. And I suppose if canceling the body does not work for whatever reason, it should set a (say) 1m timer and then declare itself dead so the rest of the build will abort. Independently, it might be appropriate for DurableTaskStep.Execution.stop to forcibly end after a (say) 10s grace period. 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-39072) timeout step should include more logging/diagnostics information
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39072 timeout step should include more logging/diagnostics information Change By: Jesse Glick Priority: Minor Major 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-39083) Record the "default branch" of the Bitbucket repository
Title: Message Title James Dumay created an issue Jenkins / JENKINS-39083 Record the "default branch" of the Bitbucket repository Issue Type: Task Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Oct/18 9:29 PM Priority: Major Reporter: James Dumay In order to solve JENKINS-38601 we need to know what branch other than master the "default branch" has been set to on Bitbucket. Setting it as a property on the multi-branch job would do. Not sure what value this is in the v2 API but heres the v1 for reference. https://confluence.atlassian.com/bitbucket/repository-resource-1-0-296095202.html#repositoryResource1.0-GETtherepository'smainbranch Add Comment
[JIRA] (JENKINS-39072) timeout step should include more logging/diagnostics information
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39072 timeout step should include more logging/diagnostics information Change By: Jesse Glick Component/s: workflow-basic-steps-plugin Component/s: pipeline 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-34637) pipeline DSL: timeout() does not work if withEnv() is enclosed
Title: Message Title Jesse Glick commented on JENKINS-34637 Re: pipeline DSL: timeout() does not work if withEnv() is enclosed Yes the bug is not in timeout or withEnv, it is more general. I am working on it. 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-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Jae Gangemi commented on JENKINS-39077 Re: unable to provision pods using 0.9 snapshot also - the scripts directory is in /home/jenkins and the Dockerfile sets that as the WORKDIR right before it sets that script as the entry point 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-39082) Record the "default branch" of the Github repository
Title: Message Title James Dumay created an issue Jenkins / JENKINS-39082 Record the "default branch" of the Github repository Issue Type: Task Assignee: Unassigned Components: github-branch-source-plugin Created: 2016/Oct/18 9:23 PM Priority: Major Reporter: James Dumay In order to solve JENKINS-38601 we need to know what branch other than master the "default branch" has been set to on Github. Setting it as a property on the multi-branch job would do. It is available from the default_branch field on https://developer.github.com/v3/repos/#get Add Comment
[JIRA] (JENKINS-39081) Cannot get property 'fullName' on null object
Title: Message Title Maciej Piechotka created an issue Jenkins / JENKINS-39081 Cannot get property 'fullName' on null object Issue Type: Bug Assignee: Unassigned Components: workflow-job-plugin Created: 2016/Oct/18 9:21 PM Priority: Minor Reporter: Maciej Piechotka When opening specific build: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/plugins/workflow-job/WEB-INF/lib/workflow-job.jar!/org/jenkinsci/plugins/workflow/job/WorkflowRun/index.jelly:63:93: org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.19.1.jar!/lib/hudson/summary.jelly:105:31: Cannot get property 'fullName' on null object at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) Add Comment
[JIRA] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Tommy Tynjä commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin There has been some more progress on this functionality. The following issues are still to be addressed: [ ] Build failure should not mark all tasks as failed (mimic DPP behaviour) when task nodes are configured (currently works if no tasks are defined) [ ] Progress bar timing [ ] Verify that commit messages are shown [ ] Increase test coverage 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-39077) unable to provision pods using 0.9 snapshot
Title: Message Title
Jae Gangemi commented on JENKINS-39077
Re: unable to provision pods using 0.9 snapshot
Events:
FirstSeenLastSeenCountFromSubobjectPathTypeReasonMessage
--------
6m6m1{default-scheduler }NormalScheduledSuccessfully assigned java8-mvn-slave-28081e60dd37c to ip-172-22-1-147.ec2.internal
6m6m1{kubelet ip-172-22-1-147.ec2.internal}spec.containers{java8-mvn-slave}NormalPullingpulling image "registry.battery-park.conductor.com/jenkins-slave-maven-debian"
6m6m1{kubelet ip-172-22-1-147.ec2.internal}spec.containers{java8-mvn-slave}NormalPulledSuccessfully pulled image "registry.battery-park.conductor.com/jenkins-slave-maven-debian"
6m6m1{kubelet ip-172-22-1-147.ec2.internal}spec.containers{java8-mvn-slave}NormalCreatedCreated container with docker id 451bce1c3290; Security:[seccomp=unconfined]
6m6m1{kubelet ip-172-22-1-147.ec2.internal}spec.containers{java8-mvn-slave}WarningFailedFailed to start container with docker id 451bce1c3290 with error: Error response from daemon: Container command 'scripts/jenkins-slave.sh' not found or does not exist.
6m6m1{kubelet ip-172-22-1-147.ec2.internal}WarningFailedSyncError syncing pod, skipping: failed to "StartContainer" for "java8-mvn-slave" with RunContainerError: "runContainer: Error response from daemon: Container command 'scripts/jenkins-slave.sh' not found or does not exist."
i don't understand the Container command 'scripts/jenkins-slave.sh' not found or does not exist. error. this container runs fine in the 0.8 version of the plugin and nothing has changed there.
Add Comment
[JIRA] (JENKINS-39066) hudson.util.ArgumentListBuilder quoting incorrectly in procStarter
Title: Message Title Daniel Beck commented on JENKINS-39066 Re: hudson.util.ArgumentListBuilder quoting incorrectly in procStarter Well, you could copy its implementation to a utility function, all the fields/getters it acts on are public/have public getters. https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/FilePath.java#L350...L364 Less than ideal, clearly, but should work. 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-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Jae Gangemi commented on JENKINS-39077 Re: unable to provision pods using 0.9 snapshot the Unrecognized input header: 50 is all i have been able to get in terms of logs. i am going to try upgrading my version of docker to see if it yields any changes. i'll report back whatever extra logs come out of this. 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-34637) pipeline DSL: timeout() does not work if withEnv() is enclosed
Title: Message Title
Domingo K edited a comment on JENKINS-34637
Re: pipeline DSL: timeout() does not work if withEnv() is enclosed
[~jglick] - Would this only affect `withEnv` code paths or have other consequences?I'm seeing a similar issue Confirmed with code below where the timeout is never being triggered for another example without "withEnv" . I am debating opening a different issue, just don't have enough data yet. {code:java}def disableClusterRoutingAllocation(node){timeout(time: 10, unit: "SECONDS"){waitUntil{try {sh "curl -XPUT -sS http://$node/_cluster/settings -d '{ \"transient\" : { \"cluster.routing.allocation.enable\" : \"none\" } }' | grep \"acknowledged\":true"return true} catch(exception){return false}}}}{code}
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-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Carlos Sanchez commented on JENKINS-39077 Re: unable to provision pods using 0.9 snapshot increase logging for org/csanchez/jenkins/plugins/kubernetes and if still nothing there see https://github.com/jenkinsci/kubernetes-plugin#debugging 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-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Carlos Sanchez commented on JENKINS-39077 Re: unable to provision pods using 0.9 snapshot you would need to provide the logs, the result of kubectl get pods, if there are any slaves there their logs,... 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-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-39077 unable to provision pods using 0.9 snapshot Change By: Carlos Sanchez Issue Type: New Feature 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-39080) Plugin fools itself with script output
Title: Message Title Igor Pashev commented on JENKINS-39080 Re: Plugin fools itself with script output I can probably take this over in a while 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-39080) Plugin fools itself with script output
Title: Message Title Igor Pashev created an issue Jenkins / JENKINS-39080 Plugin fools itself with script output Issue Type: Bug Assignee: Gregory Boissinot Attachments: fool itself.png Components: scripttrigger-plugin Created: 2016/Oct/18 8:43 PM Priority: Minor Reporter: Igor Pashev This plugin parses script output for foo. Unfortunately it prints script content and can spot that fragment in script, not in the script output. Add Comment
[JIRA] (JENKINS-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean
Title: Message Title Christopher Orr commented on JENKINS-38601 Re: Cannot mark Multibranch Pipeline as Favorite in Blue Ocean I'm having the same problem with multibranch pipelines, for example in a folder where the default branch is develop (and that's the only branch I have listed in "Include branches"). In some other multibranch pipelines, I'm not building any branches at all — only pull requests. I can't favourite those folders either. 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-34637) pipeline DSL: timeout() does not work if withEnv() is enclosed
Title: Message Title
Domingo K commented on JENKINS-34637
Re: pipeline DSL: timeout() does not work if withEnv() is enclosed
Jesse Glick - Would this only affect `withEnv` code paths or have other consequences? I'm seeing a similar issue with code below where the timeout is never being triggered. I am debating opening a different issue, just don't have enough data yet.
def disableClusterRoutingAllocation(node){
timeout(time: 10, unit: "SECONDS"){
waitUntil{
try {
sh "curl -XPUT -sS http://$node/_cluster/settings -d '{ \"transient\" : { \"cluster.routing.allocation.enable\" : \"none\" } }' | grep \"acknowledged\":true"
return true
} catch(exception){
return false
}
}
}
}
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-39079) Timestamper plugin inserts encoded TimeStampNote when using in pipeline job
Title: Message Title
jared welch created an issue
Jenkins / JENKINS-39079
Timestamper plugin inserts encoded TimeStampNote when using in pipeline job
Issue Type:
Bug
Assignee:
Steven G Brown
Components:
timestamper-plugin
Created:
2016/Oct/18 8:29 PM
Environment:
Jenkins 2.7.4 Timestamp plugin 1.8.7
Priority:
Minor
Reporter:
jared welch
Although the source documentation indicates otherwise, it appears that the encoded timestamps are always being inserted directly into the console log files leading to difficulty parsing files from disk.
/**
* Time-stamp console note.
*
* These are inserted into the log file when:
*
* The build does not extend {@link AbstractBuild}, e.g. a pipeline job.
* Running the Timestamper plugin prior to version 1.4.
* The system property is set: ({@link #getSystemProperty()}). The is
* intended to support scripts that were written prior to Timestamper 1.4 to
* parse the log files. New scripts should query the {@code /timestamps} URL
* instead (see {@link TimestampsAction}).
*
*
* Otherwise, the time-stamps are stored in a separate file, which allows a more
* compact format to be used and avoids filling the log files with encoded
* console notes.
*
* @author Steven G. Brown
*/
Seem to indicate that a pipeline job using recent versions of the plugin should not have this issue. But the system property is checked as a boolean and since TimeStampNonte.getSystemProperty() always returns a string its always true.
[JIRA] (JENKINS-39078) Config UI in job broken / unusable
Title: Message Title wujek srujek updated an issue Jenkins / JENKINS-39078 Config UI in job broken / unusable Change By: wujek srujek Environment: Jenkins 2.19.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39078) Config UI in job broken / unusable
Title: Message Title wujek srujek created an issue Jenkins / JENKINS-39078 Config UI in job broken / unusable Issue Type: Bug Assignee: Nicolas De Loof Components: docker-slaves-plugin Created: 2016/Oct/18 8:20 PM Priority: Blocker Reporter: wujek srujek The UI in job configuration is broken, the Docker configuration made available by this plugin is intermingled with other configuration. While it is possible to add 'side containers' (which is located under 'Post-build Actions'), I can't find the field to configure the main image/Dockerfile anywhere, which means I can't finish the configuration and hence not use this plugin at all. Add Comment
[JIRA] (JENKINS-39077) unable to provision pods using 0.9 snapshot
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-39077 unable to provision pods using 0.9 snapshot Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Oct/18 7:58 PM Priority: Minor Reporter: Jae Gangemi i'm compiling the project from source so i can try out the tty functionality and i am unable to provision any pods/slaves now. is what's on master not in a usable state? the jenkins logs don't give much information and the error i see in kubernetes is this: Unrecognized input header: 50 Add Comment
[JIRA] (JENKINS-26148) Incorrect implementation of RetryStepExecution.stop
Title: Message Title Jesse Glick commented on JENKINS-26148 Re: Incorrect implementation of RetryStepExecution.stop Seems that the bogus overrides of stop are useful as a workaround for JENKINS-34637: CpsBodyExecution.getCurrentExecutions disobeys its contract (it returns just the first step running, not the innermost steps), and cancel suffers from the same problem. When that is fixed, I think it would be best for StepExecution.stop to have a default implementation—getContext().onFailure(cause)—and for most of the overrides to be deleted, leaving only those which actually do something before, after, or between body invocations. 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-34637) pipeline DSL: timeout() does not work if withEnv() is enclosed
Title: Message Title Jesse Glick commented on JENKINS-34637 Re: pipeline DSL: timeout() does not work if withEnv() is enclosed Indeed the problem is in CpsBodyExecution, not timeout. 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-34637) pipeline DSL: timeout() does not work if withEnv() is enclosed
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34637 pipeline DSL: timeout() does not work if withEnv() is enclosed Change By: Jesse Glick Component/s: workflow-cps-plugin Priority: Major Critical 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-39076) Stack Overflow when trying to save system configuration
Title: Message Title Brenden Conte created an issue Jenkins / JENKINS-39076 Stack Overflow when trying to save system configuration Issue Type: Bug Assignee: Unassigned Attachments: plugin list.txt, stack overflow.txt Components: core Created: 2016/Oct/18 7:12 PM Environment: Windows server 2012 x64 Jenkins 2.19.1 Priority: Major Reporter: Brenden Conte When attempting to save the system configuration, I get a stack overflow as noted below. I attempted to remove all plugins I was not using to try to see if the issue was related to a plugin, but was unsuccessful. Plugin list is at the bottom. Reverting back to 2.7.4 resolves the issue, which makes me believe this to be a Jenkins core issue. Summary stack: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.StackOverflowError at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mike Kobit edited a comment on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Still Git is still waiting on https://github.com/jenkinsci/git-plugin/pull/437, really looking forward to not having to use Chrome Editor tools to use this feature . ! 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-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Mike Kobit commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Still waiting on https://github.com/jenkinsci/git-plugin/pull/437, really looking forward to not having to use Chrome Editor tools to use this feature. 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-39066) hudson.util.ArgumentListBuilder quoting incorrectly in procStarter
Title: Message Title Joseph Petersen commented on JENKINS-39066 Re: hudson.util.ArgumentListBuilder quoting incorrectly in procStarter Wouldn't that be wonderful if FilePath.isUnix was public? 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-39066) hudson.util.ArgumentListBuilder quoting incorrectly in procStarter
Title: Message Title Joseph Petersen edited a comment on JENKINS-39066 Re: hudson.util.ArgumentListBuilder quoting incorrectly in procStarter Wouldn't that be wonderful if FilePath.isUnix was public? ;) 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-38972) fileExists doesn't take variables
Title: Message Title Rachel Moreno resolved as Not A Defect Jenkins / JENKINS-38972 fileExists doesn't take variables Change By: Rachel Moreno Status: In Progress Resolved Resolution: Not A Defect 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-38972) fileExists doesn't take variables
Title: Message Title
Rachel Moreno commented on JENKINS-38972
Re: fileExists doesn't take variables
And the section:
} else {
error: '${controlFile} still missing. Will now fail the job.'
}
It should be:
} else {
error("${controlFile} still missing. Will now fail the job.")
}
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-38972) fileExists doesn't take variables
Title: Message Title Rachel Moreno updated an issue Jenkins / JENKINS-38972 fileExists doesn't take variables Change By: Rachel Moreno Component/s: workflow-basic-steps-plugin Component/s: workflow-aggregator-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-38972) fileExists doesn't take variables
Title: Message Title
Rachel Moreno commented on JENKINS-38972
Re: fileExists doesn't take variables
Hi angel vera, Of course, it's the first thing I did: Output:
[Pipeline] {
[Pipeline] fileExists
[Pipeline] echo
/home/rachel/examples/file.txt exists.
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
The only problem I found in your code was the use of single quotes in echo strings.
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-38972) fileExists doesn't take variables
Title: Message Title Rachel Moreno updated an issue Jenkins / JENKINS-38972 fileExists doesn't take variables Change By: Rachel Moreno Attachment: 38972-step-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38972) fileExists doesn't take variables
Title: Message Title Rachel Moreno updated an issue Jenkins / JENKINS-38972 fileExists doesn't take variables Change By: Rachel Moreno Attachment: 38972-step-2.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38972) fileExists doesn't take variables
Title: Message Title Rachel Moreno updated an issue Jenkins / JENKINS-38972 fileExists doesn't take variables Change By: Rachel Moreno Attachment: 38972-step-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38972) fileExists doesn't take variables
Title: Message Title Rachel Moreno updated an issue Jenkins / JENKINS-38972 fileExists doesn't take variables Change By: Rachel Moreno Attachment: 38972-step-2.png Attachment: 38972-step-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38972) fileExists doesn't take variables
Title: Message Title Rachel Moreno updated an issue Jenkins / JENKINS-38972 fileExists doesn't take variables Change By: Rachel Moreno Attachment: JENKINS-38972-step-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38972) fileExists doesn't take variables
Title: Message Title Rachel Moreno updated an issue Jenkins / JENKINS-38972 fileExists doesn't take variables Change By: Rachel Moreno Attachment: JENKINS-38972-step-2.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38972) fileExists doesn't take variables
Title: Message Title Rachel Moreno updated an issue Jenkins / JENKINS-38972 fileExists doesn't take variables Change By: Rachel Moreno Attachment: JENKINS-38972-step-2.png Attachment: JENKINS-38972-step-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39075) how does "Include Test Summary" works?
Title: Message Title pooja shah created an issue Jenkins / JENKINS-39075 how does "Include Test Summary" works? Issue Type: Bug Assignee: Kurt Madel Attachments: .DS_Store Components: slack-plugin Created: 2016/Oct/18 6:27 PM Priority: Minor Reporter: pooja shah I'm having python nosetests running in jenkins job. in job, have ticked, Include Test Summary" but it shows "No Tests found" (please refer the screenshot) What is the pre condition required to actually fill the "Test Summary"? or is it not working anymore? Add Comment
[JIRA] (JENKINS-25653) TimeoutStepTest.killingParallel() in aggregator failing on MacOS
Title: Message Title Jesse Glick resolved as Cannot Reproduce Too old, closing. Jenkins / JENKINS-25653 TimeoutStepTest.killingParallel() in aggregator failing on MacOS Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce 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
