[JIRA] (JENKINS-40973) Failed to prepare configFileProvider step
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-40973
Re: Failed to prepare configFileProvider step
[~mramanathan] in that case, please provide more information about your environment. Can you reproduce the same issue with a clean/new jenkins installation? and please attache the support information generated by this plugin https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin to this issue. you should also include the complete {{config.xml}} of the job having this 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-40973) Failed to prepare configFileProvider step
Title: Message Title Dominik Bartholdi commented on JENKINS-40973 Re: Failed to prepare configFileProvider step Ramanathan M in that case, please provide more information about your environment. Can you reproduce the same issue with a clean/new jenkins installation? and please attache the support information generated by this plugin https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin to this 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-40973) Failed to prepare configFileProvider step
Title: Message Title Dominik Bartholdi reopened an issue Jenkins / JENKINS-40973 Failed to prepare configFileProvider step Change By: Dominik Bartholdi Resolution: Fixed Status: Resolved Reopened 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-41244) NoSuchMethodError when using with Git 3.0.0 or 3.0.1
Title: Message Title
Stephen Connolly updated an issue
Jenkins / JENKINS-41244
NoSuchMethodError when using with Git 3.0.0 or 3.0.1
Change By:
Stephen Connolly
The fix for JENKINS-39837 requires either:* Git 2.6.x versions >= 2.6.2 < 3.0.0 ; or* Git 3.0.x versions >= 3.0.2Thus the minimum Git version is 2.6.2This can still let a user have Git 3.0.0 and not get an automatic upgrade.In such situations the user will see{code } SEVERE: Executor threw an exceptionjava.lang.NoSuchMethodError: hudson.plugins.git.GitSCM.setBrowser(Lhudson/plugins/git/browser/GitRepositoryBrowser;)V at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.build(GitHubSCMSource.java:818) at jenkins.scm.api.SCMSource.build(SCMSource.java:778) at jenkins.branch.MultiBranchProject.newBranch(MultiBranchProject.java:400){code}We should be defensive and just alert the user to the problem rather than blow up
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are
[JIRA] (JENKINS-41244) NoSuchMethodError when using with Git 3.0.0 or 3.0.1
Title: Message Title Stephen Connolly started work on JENKINS-41244 Change By: Stephen Connolly Status: Open In Progress 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-41244) NoSuchMethodError when using with Git 3.0.0 or 3.0.1
Title: Message Title Stephen Connolly updated JENKINS-41244 Jenkins / JENKINS-41244 NoSuchMethodError when using with Git 3.0.0 or 3.0.1 Change By: Stephen Connolly 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-41221) Maven build with pom.xml in subfolder fails
Title: Message Title Harm Doedens updated an issue Jenkins / JENKINS-41221 Maven build with pom.xml in subfolder fails Change By: Harm Doedens 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-41207) NullPointerException in Github branch source plugin after upgrading
Title: Message Title Alexandre Aubert commented on JENKINS-41207 Re: NullPointerException in Github branch source plugin after upgrading Hi, I can see that this issue has been solved but i don't see any update available, even on experimental update center. Could you advise on what i should to fix the pb on my jenkins instance ? Thanks 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-41221) Maven build with pom.xml in subfolder fails
Title: Message Title Harm Doedens commented on JENKINS-41221 Re: Maven build with pom.xml in subfolder fails I have removed the symbolic link and replaced with a normal folder, now the build of a maven project from a subfolder works fine. However, this is still an issue as disk space on /var is limited but on /opt it is virtually unlimited. 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-41244) NoSuchMethodError when using with Git 3.0.0 or 3.0.1
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-41244 NoSuchMethodError when using with Git 3.0.0 or 3.0.1 Change By: Stephen Connolly 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-41244) NoSuchMethodError when using with Git 3.0.0 or 3.0.1
Title: Message Title
Stephen Connolly created an issue
Jenkins / JENKINS-41244
NoSuchMethodError when using with Git 3.0.0 or 3.0.1
Issue Type:
New Feature
Assignee:
Stephen Connolly
Components:
github-branch-source-plugin
Created:
2017/Jan/20 7:25 AM
Priority:
Minor
Reporter:
Stephen Connolly
The fix for JENKINS-39837 requires either:
Git 2.6.x versions >= 2.6.2 ; or
Git 3.0.x versions >= 3.0.2
Thus the minimum Git version is 2.6.2 This can still let a user have Git 3.0.0 and not get an automatic upgrade. In such situations the user will see {code SEVERE: Executor threw an exception java.lang.NoSuchMethodError: hudson.plugins.git.GitSCM.setBrowser(Lhudson/plugins/git/browser/GitRepositoryBrowser;)V at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.build(GitHubSCMSource.java:818) at jenkins.scm.api.SCMSource.build(SCMSource.java:778) at jenkins.branch.MultiBranchProject.newBranch(MultiBranchProject.java:400)
We should be defensive and just alert the user to the problem rather than blow up
[JIRA] (JENKINS-41221) Maven build with pom.xml in subfolder fails
Title: Message Title
Harm Doedens updated an issue
Jenkins / JENKINS-41221
Maven build with pom.xml in subfolder fails
Change By:
Harm Doedens
I have created two jobs of the maven jobtype. One has a quite common folder structure wheren the pom.xml is in the root of the project. The other one has many folders and each folder contains a pom. Mind you: it is not a modular maven project, every folder contains a stand-alone-ish project.When I build the job where the pom.xml is in the root of the workspace it works well.When I build the job where the pom is in a subdirectory I configure the _Root POM_ option as */pom.xml* *edit:* The _jobs_ folder is a symbolic link to another volume (/var/lib/jenkins/jobs to /opt/jenkins_jobs) This jenkins build gives me an error with the following output:{code}[workspace] $ /bin/sh -xe /tmp/hudson7796811335066889247.sh+ mvn --versionApache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)Maven home: /usr/local/apache-mavenJava version: 1.8.0_112, vendor: Oracle CorporationJava home: /usr/java/jdk1.8.0_112/jreDefault locale: en_US, platform encoding: UTF-8OS name: "linux", version: "4.1.12-61.1.25.el7uek.x86_64", arch: "amd64", family: "unix"Parsing POMsFATAL: nulljava.lang.StackOverflowError at java.lang.Exception.(Exception.java:102) at java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.(InvocationTargetException.java:72) at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50) at com.sun.proxy.$Proxy108.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50) at com.sun.proxy.$Proxy108.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498)...and so on at com.sun.proxy.$Proxy108.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source)Started calculate disk usage of buildFinished Calculation of disk usage of build in 0 secondsStarted calculate disk usage of workspaceFinished Calculation of disk usage of workspace in 0 secondsFinished: FAILURE{code}
[JIRA] (JENKINS-41221) Maven build with pom.xml in subfolder fails
Title: Message Title Harm Doedens updated an issue Jenkins / JENKINS-41221 Maven build with pom.xml in subfolder fails Change By: Harm Doedens Priority: Major Minor 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-39345) Use js-modules to coordinate async loading of i18n translation bundles as part of dependant JavaScript bundle
Title: Message Title Tom FENNELLY commented on JENKINS-39345 Re: Use js-modules to coordinate async loading of i18n translation bundles as part of dependant _javascript_ bundle I think we should bring this forward It was puzzling me how making the "Quick Language Switcher" work could have been higher priority than getting BO itself to switch language properly. So yes, bringing this forward seems consistent to me Tom - how "destructive" will these changes be? hard to say? Hmmm ... atm I don't think it will be destructive. I would expect/hope the component _javascript_ code to not change at all. The plugins might have to "declare" their i18n bundles e.g. in the same yaml file as they declare Extension Points. We (the build) could auto-detect the default bundle, which atm is all any of the core BO plugins are using afaik. The bigger changes would be in js-modules and js-builder, building in generic hooks (so we can potentially do this for other "stuff" e.g. Keith Zantow did some work for extension decorators that would be able to use something like this too) to allow us hook into the bundle loading process i.e. to allow us inject resource loading "functions" that return a Promise that needs to be fullfilled along with the normal _javascript_ loading stuff before the bundle can start executing. After that, we wire the above into blue ocean's plugin for js-builder and get it to inject resource loading for i18n resources. That resource loading would load i18next with the resource bundle it's told to load (declared by the plugin - detected by js-builder plugin etc) and would only resolve its promise once that's done, blocking the dependant/owner _javascript_ bundle from executing. I'm sure there'll be kinks that need working out, but that's the general idea. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-41159) Disappearing parallels in karoke
Title: Message Title Vivek Pandey commented on JENKINS-41159 Re: Disappearing parallels in karoke Thorsten Scherler Sorry to have wasted your time investigating it, should have looked closely at union functionality of partial execution of pipeline with projected ones. PTAL PR https://github.com/jenkinsci/blueocean-plugin/pull/737. 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-41159) Disappearing parallels in karoke
Title: Message Title Vivek Pandey updated JENKINS-41159 Jenkins / JENKINS-41159 Disappearing parallels in karoke Change By: Vivek Pandey 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-41243) Randomly missing TagAction(SYNTHETIC_STAGE)
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-41243 Randomly missing TagAction(SYNTHETIC_STAGE) Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Jan/20 7:01 AM Environment: 0.8.1 version Priority: Major Reporter: Vivek Pandey While running this pipeline: https://github.com/i386/app-store-demo and polling FlowNodes from current heads, "Declarative: Checkout SCM" stage has missing SYNTHETIC_STAGE TagAction. BlueOcean hides any stage that has SYNTHETIC_STAGE TagAction present, due to this issue synthetic stage such as "Declarative: Checkout SCM" starts appearing in the node graph. Add Comment
[JIRA] (JENKINS-41091) git-parameter:0.7.1 breaks the multi-line parameters in rebuild
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41091 Re: git-parameter:0.7.1 breaks the multi-line parameters in rebuild Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterRebuild.java http://jenkins-ci.org/commit/git-parameter-plugin/9463ef418317007e55008f4a7daec20ab23744e1 Log: Merge pull request #42 from jenkinsci/bugfix/JENKINS-41091 JENKINS-41091: git-parameter:0.7.1 breaks the multi-line parameters i… Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/4af44534c70b...9463ef418317 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-41241) Jenkins Failes to startup, Without updatating any plugin (WebAppMain.java:248)
Title: Message Title Veeresh r resolved as Fixed The issue get resolves when you delete all the plugins from Jenkins Installation folder Follow these steps (Windows installation) 1. Go to Jenkins installation folder in "C:\Program files\Jenkins\Plugins" copy all the files in some other drive for future reference. 2. Stop Jenkins server : Go to Control Panel\All Control Panel Items\Administrative Tools\Services search for Jenkins and stop it 3. Delete all the files in the "C:\Program files\Jenkins\Plugins" folder 4. Restart the Jenkins your good to go but all the plugins will have to be reinstalled 5. Refer the "Plugins " folder which you have copied in some other destination and install the plugins Jenkins / JENKINS-41241 Jenkins Failes to startup, Without updatating any plugin (WebAppMain.java:248) Change By: Veeresh r Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41241) Jenkins Failes to startup, Without updatating any plugin (WebAppMain.java:248)
Title: Message Title Veeresh r commented on JENKINS-41241 Re: Jenkins Failes to startup, Without updatating any plugin (WebAppMain.java:248) Resolved the Issue by deleting all plugins in Jenkins Installation folder and restart the Jenkins, It will restart but again you have to install all the plugins for your jobs frustrating but there is no option for any doubts please comment thanks. 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-41240) naginator-plugin allows some build parameters to be changed via request parameters
Title: Message Title Cuong Tran updated an issue Jenkins / JENKINS-41240 naginator-plugin allows some build parameters to be changed via request parameters Change By: Cuong Tran Summary: naginator-plugin allows some build parameters to be changed via request parameters 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-39345) Use js-modules to coordinate async loading of i18n translation bundles as part of dependant JavaScript bundle
Title: Message Title James Dumay commented on JENKINS-39345 Re: Use js-modules to coordinate async loading of i18n translation bundles as part of dependant _javascript_ bundle ... and is there any way for us to try it before committing to master? 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-39345) Use js-modules to coordinate async loading of i18n translation bundles as part of dependant JavaScript bundle
Title: Message Title Michael Neale commented on JENKINS-39345 Re: Use js-modules to coordinate async loading of i18n translation bundles as part of dependant _javascript_ bundle I think we should bring this forward, Tom FENNELLY is right, this one will bite (cliff is seeing it with creation flow). Tom - how "destructive" will these changes be? hard to say? 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-41242) Blue Ocean views should include core version in footer
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-41242 Blue Ocean views should include core version in footer Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/20 4:56 AM Priority: Minor Reporter: R. Tyler Croy Right now it's just: Built at 19th January 2017 04:32 PM · (no branch) · c7e4db9 It would be much more useful for users and admins alike if the footer included the version of core present. Add Comment
[JIRA] (JENKINS-41205) Stage graph unsuitable for large, complex pipelines
Title: Message Title James Dumay commented on JENKINS-41205 Re: Stage graph unsuitable for large, complex pipelines Ian Leitch actually would you be up for a Google Hangout in the next few weeks? We can discuss this in greater detail. Would love to see some of the Pipelines you have built and how they show up in Blue Ocean. 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-41205) Stage graph unsuitable for large, complex pipelines
Title: Message Title James Dumay commented on JENKINS-41205 Re: Stage graph unsuitable for large, complex pipelines Ian Leitch yeah I think that design is totally out for the reason you provided and because two steps can appear on the screen it makes the running behaviour really complex. 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-41241) Jenkins Failes to startup, Without updatating any plugin (WebAppMain.java:248)
Title: Message Title Veeresh r updated an issue Jenkins / JENKINS-41241 Jenkins Failes to startup, Without updatating any plugin (WebAppMain.java:248) Change By: Veeresh r Summary: Jenkins Failed Failes to start startup, Without updatating any plugin (WebAppMain.java:248) 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-41205) Stage graph unsuitable for large, complex pipelines
Title: Message Title Ian Leitch commented on JENKINS-41205 Re: Stage graph unsuitable for large, complex pipelines The sketch you provided: https://issues.jenkins-ci.org/secure/attachment/34100/blueocean.sketch%202016-09-28%2015-03-57.png would not be ideal as it only alters the steps table, not the graph. If we applied this approach to our pipeline, the graph would only display a single "Test" stage, with all of the meaningful stages being shown in the list below. This would make the graph linear, and somewhat redundant. 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-41205) Stage graph unsuitable for large, complex pipelines
Title: Message Title James Dumay commented on JENKINS-41205 Re: Stage graph unsuitable for large, complex pipelines Ian Leitch we are not even clear how things should be rendered because users ideas of how that should look are so diverse I think there are some things we can do here to make the existing graph more acceptable in your case. We will also be looking at how to solve the nesting problem this year but I can't give a good ETA on it yet. 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-41205) Stage graph unsuitable for large, complex pipelines
Title: Message Title Ian Leitch commented on JENKINS-41205 Re: Stage graph unsuitable for large, complex pipelines James Dumay It's not clear in JENKINS-38442 how the graph would be rendered. Nested stages would solve the issue for me provided they do alter the graph, however ideally both nested stages and parallel stages would provide the most flexibility. 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-41241) Jenkins Failed to start Without updatating any plugin (WebAppMain.java:248)
Title: Message Title Veeresh r updated an issue Jenkins / JENKINS-41241 Jenkins Failed to start Without updatating any plugin (WebAppMain.java:248) Change By: Veeresh r Summary: Jenkins waont Failed to start Without updatating any plugin (WebAppMain.java:248) 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-41241) Jenkins Failed to start Without updatating any plugin (WebAppMain.java:248)
Title: Message Title Veeresh r assigned an issue to Veeresh r Jenkins / JENKINS-41241 Jenkins Failed to start Without updatating any plugin (WebAppMain.java:248) Change By: Veeresh r Assignee: Oleg Nenashev Veeresh r 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-41241) Jenkins waont start Without updatating (WebAppMain.java:248)
Title: Message Title Veeresh r created an issue Jenkins / JENKINS-41241 Jenkins waont start Without updatating (WebAppMain.java:248) Issue Type: Bug Assignee: Oleg Nenashev Attachments: Capture100.PNG Components: _unsorted Created: 2017/Jan/20 4:34 AM Environment: Jenkins Version :version='1.0' Editable E-mail, Git hub plugin, Assembla plugin, Arteffect Deployer plug in and many more i cant get access to Jenkins UI i am getting above error Operating system :Wnidows 10 Web browser : Crome, Firefox, Internet explorer java version "1.8.0_121" Labels: jenkins Priority: Major Reporter: Veeresh r Error hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:248) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:47) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1062) at jenkins.model.Jenkins.(Jenkins.java:905) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:231) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at
[JIRA] (JENKINS-40740) Blue ocean branches page crashes when branch does not have a last run date
Title: Message Title Brody Maclean commented on JENKINS-40740 Re: Blue ocean branches page crashes when branch does not have a last run date Ivan Meredith Is this the same as https://issues.jenkins-ci.org/browse/JENKINS-41238 ? 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-33762) Per-folder tool installations
Title: Message Title Owen Wood commented on JENKINS-33762 Re: Per-folder tool installations Seems like a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-40275 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-40973) Failed to prepare configFileProvider step
Title: Message Title Ramanathan M commented on JENKINS-40973 Re: Failed to prepare configFileProvider step Tried verbatim code snippet from your response and failed at the same step with the exact error as reported in the issue description. 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-41238) Empty state for when a branch has no run data on branch and pr tab
Title: Message Title Brody Maclean commented on JENKINS-41238 Re: Empty state for when a branch has no run data on branch and pr tab Ivan Meredith pretty simple solution but you can definitely notice 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-41238) Empty state for when a branch has no run data on branch and pr tab
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41238 Empty state for when a branch has no run data on branch and pr tab Change By: Brody Maclean Attachment: screenshot-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-41240) naginator-plugin allows some parameters to be changed via request parameters
Title: Message Title Cuong Tran created an issue Jenkins / JENKINS-41240 naginator-plugin allows some parameters to be changed via request parameters Issue Type: Improvement Assignee: Nicolas De Loof Components: naginator-plugin Created: 2017/Jan/20 3:06 AM Priority: Minor Reporter: Cuong Tran I would like to add the option to overwrite some of the build parameters if they are passed via query parameters. I'm willing to submit a PR for the change but I would like know if this change is welcomed. My use case is I manage a large Jenkins farm and have an integration server that allows me to retry a large number of failed builds. I have a need to change the priority assigned to the retried builds. Thanks. Add Comment
[JIRA] (JENKINS-41104) Cannot get source branch in PR build in Bitbucket team project
Title: Message Title Gregory Kman edited a comment on JENKINS-41104 Re: Cannot get source branch in PR build in Bitbucket team project I don't know that I would consider this a feature request. This seems more like a bug to me. The I would imagine that the 'BRANCH_NAME=PR-4' should actually be what the source branch is in Git. 'BRANCH_NAME' is equivalent to 'SOURCE_NAME' and 'CHANGE_TARGET' to be equivalent to `TARGET_NAME`Am I mistaken? And if so could someone explain what 'BRANCH_NAME' and 'CHANGE_TARGET' are supposed to mean? 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-41104) Cannot get source branch in PR build in Bitbucket team project
Title: Message Title Gregory Kman edited a comment on JENKINS-41104 Re: Cannot get source branch in PR build in Bitbucket team project I don't know that I would consider this a feature request. This seems more like a bug to me. The would imagine that the 'BRANCH_NAME=PR-4' should actually be what the source branch is in Git. 'BRANCH_NAME' is equivalent to 'SOURCE_NAME' and 'CHANGE_TARGET' to be equivalent to `TARGET_NAME`Am I mistaken? And if so could someone explain what 'BRANCH_NAME' and 'CHANGE_TARGET' are supposed to mean? 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-41104) Cannot get source branch in PR build in Bitbucket team project
Title: Message Title Gregory Kman commented on JENKINS-41104 Re: Cannot get source branch in PR build in Bitbucket team project I don't know that I would consider this a feature request. This seems more like a bug to me. The would imagine that the `BRANCH_NAME=PR-4` should actually be what the source branch is in Git. `BRANCH_NAME` is equivalent to `SOURCE_NAME` and `CHANGE_TARGET` to be equivalent to `TARGET_NAME` Am I mistaken? And if so could someone explain what `BRANCH_NAME` and `CHANGE_TARGET` are supposed to mean? 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-41104) Cannot get source branch in PR build in Bitbucket team project
Title: Message Title Gregory Kman edited a comment on JENKINS-41104 Re: Cannot get source branch in PR build in Bitbucket team project I don't know that I would consider this a feature request. This seems more like a bug to me. The would imagine that the ` ' BRANCH_NAME=PR-4 ` ' should actually be what the source branch is in Git. ` ' BRANCH_NAME ` ' is equivalent to ` ' SOURCE_NAME ` ' and ` ' CHANGE_TARGET ` ' to be equivalent to `TARGET_NAME`Am I mistaken? And if so could someone explain what ` ' BRANCH_NAME ` ' and ` ' CHANGE_TARGET ` ' are supposed to mean? 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-41205) Stage graph unsuitable for large, complex pipelines
Title: Message Title James Dumay commented on JENKINS-41205 Re: Stage graph unsuitable for large, complex pipelines Thanks Ian Leitch! For that second point would you be interested in something like JENKINS-38442 ? 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-41155) User can see the current running and queued jobs from blue ocean UI
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41155 User can see the current running and queued jobs from blue ocean UI Change By: James Dumay Sprint: post-release 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-41205) Stage graph unsuitable for large, complex pipelines
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41205 Stage graph unsuitable for large, complex pipelines Change By: James Dumay Sprint: post-release 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-41146) SCM Trigger configuration being overwritten by SYSTEM user in Pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41146 SCM Trigger configuration being overwritten by SYSTEM user in Pipeline Change By: James Dumay Component/s: blueocean-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-41142) SQLPlus Runner build status is wrong.
Title: Message Title Fernando Boaglio resolved as Fixed Jenkins / JENKINS-41142 SQLPlus Runner build status is wrong. Change By: Fernando Boaglio 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-39640) SQLPlus Script Runner Plugin - Unable to execute scripts
Title: Message Title Fernando Boaglio commented on JENKINS-39640 Re: SQLPlus Script Runner Plugin - Unable to execute scripts Have you tried to enable the auto detect ORACLE_HOME option ? 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-41238) Empty state for when a branch has no run data on branch and pr tab
Title: Message Title Ivan Meredith closed an issue as Won't Do Jenkins / JENKINS-41238 Empty state for when a branch has no run data on branch and pr tab Change By: Ivan Meredith Status: Open Closed Resolution: Won't Do 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-31597) SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level
Title: Message Title Fernando Boaglio closed an issue as Fixed Jenkins / JENKINS-31597 SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level Change By: Fernando Boaglio Status: Resolved Closed 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-32286) SQLPlus Script Runner 1.0.1 - "file script" will not run + other issues...
Title: Message Title Fernando Boaglio closed an issue as Fixed Jenkins / JENKINS-32286 SQLPlus Script Runner 1.0.1 - "file script" will not run + other issues... Change By: Fernando Boaglio Status: Resolved Closed 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-32105) SQLPlus Script Runner Plugin: Global ORACLE_HOME cannot save after Jenkins 1.640.
Title: Message Title Fernando Boaglio closed an issue as Fixed Jenkins / JENKINS-32105 SQLPlus Script Runner Plugin: Global ORACLE_HOME cannot save after Jenkins 1.640. Change By: Fernando Boaglio Status: Resolved Closed 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-40131) "Re-run" button text needs to be translated
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40131 "Re-run" button text needs to be translated Change By: James Dumay Sprint: frank, panthalassa iapetus 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-39864) Page title should include build number
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39864 Page title should include build number Change By: James Dumay Sprint: tasman, frank, panthalassa iapetus 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-39705) Remove Show More button instead of disabling it
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39705 Remove Show More button instead of disabling it Change By: James Dumay Priority: Trivial Minor 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-39705) Remove Show More button instead of disabling it
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39705 Remove Show More button instead of disabling it Change By: James Dumay Sprint: arctic, frank , iapetus 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-36083) Error handling
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36083 Error handling Change By: James Dumay Sprint: 1.0-m10, 1.0-b05/b-06, iapetus panthalassa 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-41159) Disappearing parallels in karoke
Title: Message Title James Dumay commented on JENKINS-41159 Re: Disappearing parallels in karoke Good job on tracking these down Thorsten Scherler and Vivek Pandey! 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-41159) Disappearing parallels in karoke
Title: Message Title Vivek Pandey commented on JENKINS-41159 Re: Disappearing parallels in karoke Thorsten Scherler Looks like a bug in how union/merge of current and last successful pipeline parallels are merged. I am going to work on a fix. 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-41159) Disappearing parallels in karoke
Title: Message Title Vivek Pandey assigned an issue to Vivek Pandey Jenkins / JENKINS-41159 Disappearing parallels in karoke Change By: Vivek Pandey Assignee: Thorsten Scherler Vivek Pandey 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-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title James Dumay commented on JENKINS-39464 Re: Pipeline with parallel and no stages does not get visualised correctly This fix will be released in 1.0.0-b19 next week. 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-41239) Declarative: error during always block skips execution of remaining steps
Title: Message Title
Liam Newman created an issue
Jenkins / JENKINS-41239
Declarative: error during always block skips execution of remaining steps
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Jan/20 1:48 AM
Priority:
Major
Reporter:
Liam Newman
Here's a trivial example of a general problem:
pipeline {
agent any
stages {
stage ("Example") {
steps {
// Install dependencies
sh 'npm install'
echo 'Execute build that creates artifacts'
echo 'Execute step that fails to create the expected junit test file'
}
}
}
post {
always {
junit 'reports/**'
echo 'This step and everything after it won't run.'
archive '**'
echo "send email to people with final build status"
}
}
}
I have an always block, but I can't actually guarantee that all steps in that always block will all always attempt to run. In Scripted Pipeline I could wrap each of these in a try-catch, but I can't do that in Declarative. I can reorder these steps to put the ones that I know won't fail earlier, but what about the email step? I want that to be last, so it gets the proper build status in the email. Andrew Bayer suggested a catchError block. But depending on which step fails, that doesn't get the right behavior either. I want each step in the always to run exactly once no matter the build status. If the second step fails the catchError can't tell which one failed and not to run the first step again. Logically what I would expect to work:
[JIRA] (JENKINS-41133) Github Pull Requests showing up under Branches
Title: Message Title James Dumay commented on JENKINS-41133 Re: Github Pull Requests showing up under Branches Stewart Bryson Camilo Ribeiro you have been effected by a bad SCM API upgrade that was rolled back from the update center. At the moment it isn't possible to cleanly rollback. We will be rolling out fixes in Blue Ocean when the SCM API has been fixed as part of JENKINS-40299. I am really sorry for any inconvenience caused and rest assured we have a team of our best people working on it right now. 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-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title Vivek Pandey updated JENKINS-39464 Jenkins / JENKINS-39464 Pipeline with parallel and no stages does not get visualised correctly Change By: Vivek Pandey Status: In Review 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-41238) Empty state for when a branch has no run data on branch and pr tab
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-41238 Empty state for when a branch has no run data on branch and pr tab Issue Type: Bug Assignee: Brody Maclean Attachments: Screen Shot 2017-01-20 at 2.11.22 PM.png Components: blueocean-plugin Created: 2017/Jan/20 1:34 AM Priority: Critical Reporter: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41237) Error result for when creation fails
Title: Message Title Cliff Meyers commented on JENKINS-41237 Re: Error result for when creation fails Also I'm not sure about trying again. I mean we could let them try again in case the initial REST API call fails - we are not handling that scenario now except for a naming conflict - but once the project is saved, they'd have to rename it again if they wanted to "try again" - just FYI. 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-41237) Error result for when creation fails
Title: Message Title Cliff Meyers commented on JENKINS-41237 Re: Error result for when creation fails The two pieces of data that we'll have are simply that an error occurred, and the contents of the log. So unless we can parse the file in some way (unlikely?) I think we're sorta just stuck with showing the log. Unless Michael Neale you have some fancy ideas? 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-41237) Error result for when creation fails
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41237 Error result for when creation fails Change By: Michael Neale Sprint: tethys 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-41237) Error result for when creation fails
Title: Message Title Michael Neale assigned an issue to Brody Maclean Jenkins / JENKINS-41237 Error result for when creation fails Change By: Michael Neale Assignee: Brody Maclean 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-41237) Error result for when creation fails
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41237 Error result for when creation fails Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/20 1:29 AM Priority: Minor Reporter: Michael Neale When the pipeline creation process finishes, it may end up in a state that is a failure. This may result in a short message to the user (in which case they may try again) or the ability to expand to a longer more verbose log view for the user to see what went wrong. need some designs of what this could look like (after the creation UI is dismissed) Add Comment
[JIRA] (JENKINS-39793) When there are no repositories in the Org folder we need to show an empty state to help them create a pipeline
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-39793 When there are no repositories in the Org folder we need to show an empty state to help them create a pipeline Change By: Brody Maclean Assignee: Brody Maclean 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-41236) SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"
Title: Message Title
Andrew Bayer edited a comment on JENKINS-41236
Re: SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"
So...I would consider this very much a bug in the Sauce plugin rather than Declarative. If you look at https://github.com/jenkinsci/sauce-ondemand-plugin/blob/master/src/main/java/com/saucelabs/jenkins/pipeline/SauceConnectStep.java#L49-L55, you can see that the {{sauceconnect}} step in fact has four required parameters - if any of them should actually be optional, they shouldn't be in the {{@DataBoundConstructor}}, and they should instead have their own {{@DataBoundSetter}}. And I should mention that I'm actually not sure how this works outside Declarative! =)
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-41236) SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"
Title: Message Title Andrew Bayer assigned an issue to Gavin Mogan Jenkins / JENKINS-41236 SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath" Change By: Andrew Bayer Assignee: Andrew Bayer Gavin Mogan 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-41236) SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-41236 SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath" Change By: Andrew Bayer Component/s: pipeline-model-definition-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-41236) SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"
Title: Message Title Andrew Bayer commented on JENKINS-41236 Re: SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath" So...I would consider this very much a bug in the Sauce plugin rather than Declarative. If you look at https://github.com/jenkinsci/sauce-ondemand-plugin/blob/master/src/main/java/com/saucelabs/jenkins/pipeline/SauceConnectStep.java#L49-L55, you can see that the sauceconnect step in fact has four required parameters - if any of them should actually be optional, they shouldn't be in the @DataBoundConstructor, and they should instead have their own @DataBoundSetter. 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-39793) When there are no repositories in the Org folder we need to show an empty state to help them create a pipeline
Title: Message Title Brody Maclean commented on JENKINS-39793 Re: When there are no repositories in the Org folder we need to show an empty state to help them create a pipeline Zeplin https://zpl.io/AOIaW 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-39793) When there are no repositories in the Org folder we need to show an empty state to help them create a pipeline
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-39793 When there are no repositories in the Org folder we need to show an empty state to help them create a pipeline Change By: Brody Maclean Attachment: screenshot-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-41236) SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"
Title: Message Title
Liam Newman created an issue
Jenkins / JENKINS-41236
SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin, sauce-ondemand-plugin
Created:
2017/Jan/20 12:57 AM
Priority:
Major
Reporter:
Liam Newman
The following code fails on the sauceconnect step unless the script block is uncommented: https://raw.githubusercontent.com/bitwiseman/JS-Nightwatch.js/issue/declarative/sauceConnectPath/Jenkinsfile
pipeline {
agent any
stages {
stage ("Build") {
steps {
// Install dependencies
sh 'npm install'
}
}
stage ("Test") {
steps {
// script {
// Add sauce credentials
sauce('f0a6b8ad-ce30-4cba-bf9a-95afbc470a8a') {
// Start sauce connect
sauceconnect(options: '', useGeneratedTunnelIdentifier: false, verboseLogging: false) {
}
}
// }
}
}
}
}
The error is:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 16: Missing required parameter: "sauceConnectPath" @ line 16, column 25.
sauceconnect(options: '', useGeneratedTunnelIdentifier: false, verboseLogging: false) {
^
1 error
at
[JIRA] (JENKINS-39793) When there are no repositories in the Org folder we need to show an empty state to help them create a pipeline
Title: Message Title Brody Maclean started work on JENKINS-39793 Change By: Brody Maclean Status: Open In Progress 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-37590) RuntimeException Error if you attempt to save a parameterized build with no parameters
Title: Message Title Andrew Bayer commented on JENKINS-37590 Re: RuntimeException Error if you attempt to save a parameterized build with no parameters New PR up at https://github.com/jenkinsci/jenkins/pull/2723 since the previous one was dealing with a scenario that actually no longer exists. 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-41132) Should be able to click anywhere in pipeline row
Title: Message Title James Dumay commented on JENKINS-41132 Re: Should be able to click anywhere in pipeline row Thanks Christopher Orr 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-41139) Refactor Creation UI code into "blueocean-git-pipeline" and "blueocean-github-pipeline" modules
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-41139 Refactor Creation UI code into "blueocean-git-pipeline" and "blueocean-github-pipeline" modules Change By: Cliff Meyers * Migrate Git-specific code to "blueocean-git-pipeline"* Migrate Github-specific code to "blueocean-github-pipeline"* Validate that CSS still loads correctly for each SCM provider: potential issue with how SandboxComponent is loading/rendering the extension. Maybe need similar logic as in ExtensionPoint class* Move Flow API's and Credentials code to "blueocean-core-js" 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-41050) Do checkout scm always outside of container
Title: Message Title Michael Neale edited a comment on JENKINS-41050 Re: Do checkout scm always outside of container OK have thought about this and talked with Andrew. I somewhat can appreciate philosphically what Bobby says, however I think this should proceed. The reason is that the pull of "use any docker container" is far stronger than the push back of "well you need your scm on your agent". Some docker plugins have solved this by using a "side car" container with the tools, and maybe someday there will be support for those (as opposed to docker pipeline, which it uses now). So I think this should def. go ahead. So - +1 for me. The risk of not doing this is people will use bad, unmaintained images just to get the scm they need (which is what has happened in the past). They already have to have the jenkins agent running (and jvm). Bind mounting is the price of entry with docker pipeline right now, so this is how it needs to 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-41050) Do checkout scm always outside of container
Title: Message Title Michael Neale edited a comment on JENKINS-41050 Re: Do checkout scm always outside of container One suggestion by James was that this could be "smart" and attempt checkout scm in on agent host , and fail over to checkout scm inside a container if possible. Give the best chance to find the tool without the user telling. This absolutely nuts idea may work, and could be a good enhancement. Or be terrible. Often the best ideas are both. 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-41050) Do checkout scm always outside of container
Title: Message Title Michael Neale commented on JENKINS-41050 Re: Do checkout scm always outside of container One suggestion by James was that this could be "smart" and attempt checkout scm in agent, and fail over to checkout scm inside a container if possible. Give the best chance to find the tool without the user telling. This absolutely nuts idea may work, and could be a good enhancement. Or be terrible. Often the best ideas are both. 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-41235) Ansible plugin does not escape single quotes in extra vars
Title: Message Title Dave Wittman created an issue Jenkins / JENKINS-41235 Ansible plugin does not escape single quotes in extra vars Issue Type: Bug Assignee: Jean-Christophe Sirot Components: ansible-plugin Created: 2017/Jan/20 12:28 AM Priority: Minor Reporter: Dave Wittman Ansible Plugin 0.6.2 Single quotes in the value of an extra var are not properly escaped, causing the command to fail. This only happens if the variable has a space in the value as well, as that is when the plugin wraps the variable in single quotes instead of double quotes. ERROR! failed at splitting arguments, either an unbalanced jinja2 block or quotes: my_variable='this ain't right ' Add Comment
[JIRA] (JENKINS-41050) Do checkout scm always outside of container
Title: Message Title Michael Neale commented on JENKINS-41050 Re: Do checkout scm always outside of container OK have thought about this and talked with Andrew. I somewhat can appreciate philosphically what Bobby says, however I think this should proceed. The reason is that the pull of "use any docker container" is far stronger than the push back of "well you need your scm on your agent". Some docker plugins have solved this by using a "side car" container with the tools, and maybe someday there will be support for those (as opposed to docker pipeline, which it uses now). So I think this should def. go ahead. So - +1 for me. The risk of not doing this is people will use bad, unmaintained images just to get the scm they need (which is what has happened in the past). They already have to have the jenkins agent running (and jvm). 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-40670) Input status indicator is off
Title: Message Title Ivan Meredith started work on JENKINS-40670 Change By: Ivan Meredith Status: Open In Progress 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-38982) User would like to have a fast smart search to find jobs from the dashboard
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38982 User would like to have a fast smart search to find jobs from the dashboard Change By: James Dumay Sprint: atlantic, frank, christmas, post- release candidate, christmas 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-41162) Input descriptions can contain html tags - allow or prevent
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41162 Input descriptions can contain html tags - allow or prevent Change By: James Dumay 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-39345) Use js-modules to coordinate async loading of i18n translation bundles as part of dependant JavaScript bundle
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39345 Use js-modules to coordinate async loading of i18n translation bundles as part of dependant _javascript_ bundle Change By: James Dumay Sprint: indian, arctic, tasman, panthalassa pannonian 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-40860) Go to the end of the expanded log
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40860 Go to the end of the expanded log Change By: James Dumay Sprint: iapetus pannonian 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-40860) Go to the end of the expanded log
Title: Message Title James Dumay assigned an issue to Thorsten Scherler Jenkins / JENKINS-40860 Go to the end of the expanded log Change By: James Dumay Assignee: Tom FENNELLY Thorsten Scherler 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-40068) Dashboard view masks later commit failure with earlier commit success
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40068 Dashboard view masks later commit failure with earlier commit success Change By: James Dumay Sprint: pannonian iapetus 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-40605) Time reported is not correct
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40605 Time reported is not correct Change By: James Dumay Sprint: pannonian iapetus 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-40326) Pipeline results (karaoke) doesn't reload when master is restarted
Title: Message Title Michael Neale assigned an issue to Tom FENNELLY Jenkins / JENKINS-40326 Pipeline results (karaoke) doesn't reload when master is restarted Change By: Michael Neale Assignee: Michael Neale Tom FENNELLY 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-40617) Handling unsupported inputs
Title: Message Title James Dumay assigned an issue to Thorsten Scherler Jenkins / JENKINS-40617 Handling unsupported inputs Change By: James Dumay Assignee: Tom FENNELLY Thorsten Scherler 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-40617) Handling unsupported inputs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40617 Handling unsupported inputs Change By: James Dumay Sprint: frank, tethys panthalassa 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-40728) Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem
Title: Message Title Bryson Gibbons commented on JENKINS-40728 Re: Invalid class cast in Disk Usage Plugin when ItemGroup is not a TopLevelItem I have a new stack trace, after again upgrading to Config File Provider Plugin version 2.15.5 (previously upgraded to Config File provider version 2.15.1, which is now flagged as "DO NOT INSTALL" due to issues with Managed scripts/configs). This time the promotion fails quickly rather than endlessly running, and the exception now appears in the UI as follows: FATAL: can not determine current context/parent for: MyJob/promotion of type class hudson.plugins.promoted_builds.JobPropertyImpl java.lang.IllegalArgumentException: can not determine current context/parent for: MyJob/promotion of type class hudson.plugins.promoted_builds.JobPropertyImpl at org.jenkinsci.plugins.configfiles.ConfigFiles.getByIdOrNull(ConfigFiles.java:114) at org.jenkinsci.plugins.configfiles.ConfigFiles.getByIdOrNull(ConfigFiles.java:140) at org.jenkinsci.plugins.configfiles.ConfigFiles.getByIdOrNull(ConfigFiles.java:164) at org.jenkinsci.plugins.managedscripts.PowerShellBuildStep.getContents(PowerShellBuildStep.java:126) at hudson.tasks.CommandInterpreter.createScriptFile(CommandInterpreter.java:161) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:93) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:65) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:405) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:347) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1729) at hudson.model.Run.run(Run.java:1688) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:286) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
