[JIRA] (JENKINS-39897) auto-register of webhook silently fails for BB cloud
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-39897 auto-register of webhook silently fails for BB cloud Issue Type: Improvement Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Nov/21 8:24 AM Priority: Minor Reporter: Dominik Bartholdi "auto-register webhooks" for BB cloud requires admin permission, thats clear - but it took my a long time until I realized that my user was not having the required permissions. Even tough I checked the box "Auto-register webhook", I had no evidence that there was any attempt of really do so. No error, no message. It would be good if the user would get some sort of a hint that this operation did not work as expected. Add Comment
[JIRA] (JENKINS-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title squalou jenkins updated an issue Jenkins / JENKINS-39615 Global Pipeline Libraries triggers the 'poll SCM' of jobs Change By: squalou jenkins 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-39891) Add i18n backend into a plugin and distribute with Blue Ocean
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39891
Add i18n backend into a plugin and distribute with Blue Ocean
Change By:
James Dumay
*Context** We think that having two very different i18n behaviors across 2.7.x and the latest LTS is going to be a source of quality risk* We want all supported versions to use i18n in the same way*In scope** Move i18n into a plugin and distribute with blue ocean* Resource bundles should be cached appropriately** {{/_i18n/resource/blueocean-dashboard/1.0.0/jenkins.plugins.blueocean.dashboard.Messages/en}}** {{/_i18n/resource/$PLUGIN_NAME/$PLUGIN_VERSION/$BUNDLE_NAME/$LANG}}** Any non-snapshot version should be cached for 365 days** Any snapshot version should not be cached* Update blueocean i18n so that it loads via the new endpoint above* Remove any english fall backs from the jsx as now all versions of Blue Ocean can load i18n bundles
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because yo
[JIRA] (JENKINS-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title squalou jenkins commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs I allow myself to increase criticality. Why ? because in my infrastructure I have dozens of jenkins master with plenty of jobs in each. Our target is to share a common lib, and this feature is really welcome. Matter is : each commit to the lib leads to hundreds of jobs triggered. So for now we stopped the deployment of this feature. There is no easy workaround in our case. (again : if I could get rid of poll-scm I would, but I can'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, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39898) allow exclusion of branches
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-39898 allow exclusion of branches Issue Type: New Feature Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin, workflow-multibranch-plugin Created: 2016/Nov/21 8:56 AM Priority: Major Reporter: Dominik Bartholdi It should be possible to exclude some branches from being a job created at all. e.g. we only merge to the master branch while we do a release, but there should never be a build triggered from the master branch itself. As a result we don't like the master branch to appear in the list of jobs at all. I think an additional regex to define the branches to be included would be a perfect solution. While there is an option in the "Bitbucket Team/Project" type to exclude jobs from automatically build (via "Automatic branch project triggering" of the "Branch API plugin"). This has not the same effect, a job is still created and a user could potentially trigger it in the UI. Add Comment
[JIRA] (JENKINS-35414) Folders don't show up in dashboard view after upgrade
Title: Message Title
Bruno Bieri commented on JENKINS-35414
Re: Folders don't show up in dashboard view after upgrade
I guess one of the following fixes is causing the folders to disappear:
[Ensure that $ {jobs} is really a Collection |https://github.com/evandy0/dashboard-view-plugin/commit/18ef5137e8aba0d50e0fc256171ddf06ecf106af ] * [[FIXED JENKINS-21578] Ensure that ${jobs} is really a Collection|https://github.com/jenkinsci/dashboard-view-plugin/commit/baa8c5043072c6cc7a3cf44f002d55befd86f1c5]
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-35414) Folders don't show up in dashboard view after upgrade
Title: Message Title
Bruno Bieri edited a comment on JENKINS-35414
Re: Folders don't show up in dashboard view after upgrade
I guess one of the following fixes is causing the folders to disappear: * [Ensure that ${jobs} is really a Collection |https://github.com/evandy0/dashboard-view-plugin/commit/18ef5137e8aba0d50e0fc256171ddf06ecf106af ] * [[FIXED JENKINS-21578] Ensure that ${jobs} is really a Collection|https://github.com/jenkinsci/dashboard-view-plugin/commit/baa8c5043072c6cc7a3cf44f002d55befd86f1c5]
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-35414) Folders don't show up in dashboard view after upgrade
Title: Message Title
Bruno Bieri edited a comment on JENKINS-35414
Re: Folders don't show up in dashboard view after upgrade
I guess one of the following fixes is causing the folders to disappear:Ensure that ${jobs} is really a Collection[|https://github.com/evandy0/dashboard-view-plugin/commit/18ef5137e8aba0d50e0fc256171ddf06ecf106af][ [ FIXED JENKINS-21578] Ensure that ${jobs} is really a Collection [ |https://github.com/jenkinsci/dashboard-view-plugin/commit/baa8c5043072c6cc7a3cf44f002d55befd86f1c5]
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-35414) Folders don't show up in dashboard view after upgrade
Title: Message Title
Bruno Bieri edited a comment on JENKINS-35414
Re: Folders don't show up in dashboard view after upgrade
I guess one of the following fixes is causing the folders to disappear: [ Ensure that ${jobs} is really a Collection [ |https://github.com/evandy0/dashboard-view-plugin/commit/18ef5137e8aba0d50e0fc256171ddf06ecf106af][[FIXED JENKINS-21578] Ensure that ${jobs} is really a Collection|https://github.com/jenkinsci/dashboard-view-plugin/commit/baa8c5043072c6cc7a3cf44f002d55befd86f1c5]
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-35414) Folders don't show up in dashboard view after upgrade
Title: Message Title
Bruno Bieri edited a comment on JENKINS-35414
Re: Folders don't show up in dashboard view after upgrade
I experience the same issue.After investigations I guess one of the following fixes is causing the folders to disappear:Ensure that ${jobs} is really a Collection[|https://github.com/evandy0/dashboard-view-plugin/commit/18ef5137e8aba0d50e0fc256171ddf06ecf106af][FIXED JENKINS-21578] Ensure that ${jobs} is really a Collection[|https://github.com/jenkinsci/dashboard-view-plugin/commit/baa8c5043072c6cc7a3cf44f002d55befd86f1c5]
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-39900) abcd
Title: Message Title sree nivas created an issue Jenkins / JENKINS-39900 abcd Issue Type: Bug Assignee: sree nivas Components: absint-astree-plugin Created: 2016/Nov/21 9:06 AM Environment: php Labels: pipeline Priority: Blocker Reporter: sree nivas test Add Comment
[JIRA] (JENKINS-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title
squalou jenkins created an issue
Jenkins / JENKINS-39899
workflow-lib : declaring several Libraries causes them to overlap
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline, workflow-cps-global-lib-plugin
Created:
2016/Nov/21 9:06 AM
Environment:
RHEL 7.3 for master jenkins LTS 2.19.3
Priority:
Major
Reporter:
squalou jenkins
Workflow lib is great, but still suffers some issues. Several libraries can be defined in Jenkins configuration. This is great. What I plan is :
a global 'core' lib for those boilerplate high level methods everyone need (not many methods, used by lots of people, shared among several jenkins instances)
a 'per jenkins instance' lib, see it as a 'per team' lib for any 'team-specific usecases', if they exist
Mater is : apparently now the lib checkout MUST put 'vars' directory at the root of /jobs/jobId@libs So, for instance, my libs are on a git repo, I tried to 'checkout in a specific subdirectory' : it doesn't work So, ok, I leave it in default place ... but then I have to make a 'wipe and force clone' checkout. in the pipeline I would write this :
@Library ('lib-one')
import method1
// at this moment, the checkout is done, methods1 becomes available in classpath etc... great
@Livrary('lib-two')
import method2
//at this moment : lib-two is checked out, lib-one is in the way ... that's where the 'wip
[JIRA] (JENKINS-35414) Folders don't show up in dashboard view after upgrade
Title: Message Title
Bruno Bieri edited a comment on JENKINS-35414
Re: Folders don't show up in dashboard view after upgrade
I experience the same issue.After investigations I guess one of the following fixes is causing the folders to disappear:Ensure that ${jobs} is really a Collection[|https://github.com/evandy0/dashboard-view-plugin/commit/18ef5137e8aba0d50e0fc256171ddf06ecf106af][FIXED JENKINS-21578] Ensure that ${jobs} is really a Collection[|https://github.com/jenkinsci/dashboard-view-plugin/commit/baa8c5043072c6cc7a3cf44f002d55befd86f1c5] *Workaround*As a temporary workaround you could check the checkbox `Recurse in subfolders` on your view and you would be able to select jobs within your `Folder` project. It also works if you use Regex for your view.
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-39900) abcd
Title: Message Title sree nivas started work on JENKINS-39900 Change By: sree nivas 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-39900) abcd
Title: Message Title sree nivas updated JENKINS-39900 Jenkins / JENKINS-39900 abcd Change By: sree nivas 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-39900) abcd
Title: Message Title sree nivas updated JENKINS-39900 Jenkins / JENKINS-39900 abcd Change By: sree nivas Status: In Review 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-39900) abcd
Title: Message Title sree nivas updated JENKINS-39900 Jenkins / JENKINS-39900 abcd Change By: sree nivas 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-39900) abcd
Title: Message Title sree nivas started work on JENKINS-39900 Change By: sree nivas 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-39900) abcd
Title: Message Title sree nivas stopped work on JENKINS-39900 Change By: sree nivas Status: In Progress Open 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-39900) abcd
Title: Message Title sree nivas updated JENKINS-39900 Jenkins / JENKINS-39900 abcd Change By: sree nivas Status: Resolved In 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-39900) abcd
Title: Message Title sree nivas resolved as Fixed Jenkins / JENKINS-39900 abcd Change By: sree nivas 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-39900) abcd
Title: Message Title sree nivas stopped work on JENKINS-39900 Change By: sree nivas Resolution: Fixed Status: In Progress Open 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-38882) Avoid browser cache busting after Jenkins restart
Title: Message Title James Dumay commented on JENKINS-38882 Re: Avoid browser cache busting after Jenkins restart We should have a mini-design doc here and have members of the team collaborate 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-39572) Jira trigger plugin too many opened files
Title: Message Title Kristo Moorits commented on JENKINS-39572 Re: Jira trigger plugin too many opened files Yes, we're using JQL Filter 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-39849) Lots of failed requests for i18n bundles in the console
Title: Message Title Thorsten Scherler updated JENKINS-39849 Jenkins / JENKINS-39849 Lots of failed requests for i18n bundles in the console Change By: Thorsten Scherler 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-39901) Add pipeline support
Title: Message Title I G created an issue Jenkins / JENKINS-39901 Add pipeline support Issue Type: New Feature Assignee: Unassigned Components: icescrum-plugin Created: 2016/Nov/21 9:18 AM Priority: Minor Reporter: I G Plugin should give the ability to send message to IceScrum inside a Pipeline script. See this first Q&A for more details. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39902) Add User search filter to restrict login username used
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-39902 Add User search filter to restrict login username used Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2016/Nov/21 9:19 AM Priority: Minor Reporter: Félix Belzunce Arcos People can currently login as 'foo@bar' or 'bar\foo' or just 'foo', but from Jenkins point of view the user on each of those possibilities is a different user. It could be nice to have a Dropdown menu in which AD admins could indeed restrict the way users can login as from Jenkins point of view 'foo@bar' != 'bar\foo' != 'foo' Add Comment
[JIRA] (JENKINS-26700) Download build artifacts as zip generates a corrupted file
Title: Message Title chris_mh3 commented on JENKINS-26700 Re: Download build artifacts as zip generates a corrupted file I would be very surprised if this would fix Srinivasan Venkataraman's and my problem. In my case it's not with zip files at all. Should I open a new issue for 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-39903) Use credential plugin to obfuscate passwords
Title: Message Title I G created an issue Jenkins / JENKINS-39903 Use credential plugin to obfuscate passwords Issue Type: Improvement Assignee: Unassigned Components: icescrum-plugin Created: 2016/Nov/21 9:24 AM Priority: Major Reporter: I G IceScrum settings in the job's configuration page are in clear text in the page source. "setting-name">Password"setting-main">"icescrum.password" type="password" class="setting-input " value="CLEARTEXTPASSWORD" /> Using the credential plugin should avoid this. Add Comment
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Oleg Nenashev commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious If the test run marks the build unstable instead of Failed, it should be also visible. In https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/master/113/pipeline I get an unstable state, but all Pipeline steps are being shown as green. It complicates the analysis if you have multiple test result publishing steps 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-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious Oleg Nenashev if there are any failed tests we will show this summary 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-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39892
When the run fails with tests or another analysis then it should be more obvious
Change By:
James Dumay
*Problem*{quote}When I upload a PR to GitHub and Jenkins responds with something bad and I click on details; In the traditional UI I get to the build page where I with a quick glance can most of the time directly see what is wrong, wether it's a test case that has failed or a checkstyle or findbugs violation etc.With BO I first get a blank page that load a bunch of stuff, compared to the traditional UI it takes forever, and during that load time I would have already found the culprit. And then I get a page that from my perspective shows me nothing except for a yellow color indicating an unstable build, but I sort of already knew that. And then I need to click around to find out what is wrong. While in the traditional build page I only need to click something to find out the details of why a particular thing is wrong.{quote}*Possible solution** When we detect that tests that have failed (or another analysis ) that is the cause of a failed run) the failure the log is not expanded and the "Issues detected" panel appears at the top of the screen.* Developer can click on the summary information in the issues detect and jump into analysis
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Oleg Nenashev commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious James Dumay But from what I see in Summary I won't be able to determine which test reporting step caused the failure. If I do the test parallelization across multiple machines, it will be complicated. 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-5703) Exception leaves zombie processes for slaves started by command on master
Title: Message Title Matthias Gehre commented on JENKINS-5703 Re: Exception leaves zombie processes for slaves started by command on master This is still happening. I see multiple [defunct] processes accumulating under "java -jar slave.jar". Im using remoting version 3.1. I'm not exactly sure what leads to the [defunct] processes, but the they should be collected by the slave jar anyways. Is there any information I can provide? I'm able to do more investigations if I know which to make. 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-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious Oleg Nenashev we can't do that until JENKINS-27395 is 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-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay edited a comment on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious [~oleg_nenashev] we can't do that until JENKINS-27395 is fixed. ping [~svanoort] [~hrmpw] 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-39904) No email sent when build a submodule
Title: Message Title arnaud dovi created an issue Jenkins / JENKINS-39904 No email sent when build a submodule Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2016/Nov/21 9:58 AM Environment: Jenkins 2.33, Linux CentOS 7 Priority: Minor Reporter: arnaud dovi Hello, We use email-ext-plugin on all the Jenkins main Jobs we have defined properly as below http://igor.sdr/jenkins/job/ However, when a Jenkins Jobs is a parent multi module project, it works fine for the parent project, but any sub modules we are accessing with such url http://igor.sdr/jenkins/job On the configuration page of the submodule we are not presented the email-ext-plugin configuration settings, and despite the settings present in the config.xml file of the submodule job, the email send does not trigger Can you extend the use of this plugin to submodules please ? My team keeps asking me for this Add Comment
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title Arnaud Héritier commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs Also it may be useful to ease the access to a build/job workspaces. Having to navigate in pipeline steps to find workspaces isn't user friendly. Maybe we could: 1) have a workspace icon (and link) nearby the console icon where relevant on steps view. 2) have a "Workspaces" link on the pipeline job page that opens a "pop up layer" (just as logs does) listing all the workspace links used in the last pipeline build, just as the workspace link of a "standard job" shows the content of the workspace of the last job link. 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-39176) Project-based security configuration doesn't work for folders and subfolders
Title: Message Title Roman Stepanchuk commented on JENKINS-39176 Re: Project-based security configuration doesn't work for folders and subfolders If I have installed plugins: Folders Plugin 5.13 Role-based Authorization Strategy 2.3.2 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-39176) Project-based security configuration doesn't work for folders and subfolders
Title: Message Title Roman Stepanchuk edited a comment on JENKINS-39176 Re: Project-based security configuration doesn't work for folders and subfolders If I have installed plugins: Folders Plugin 5.13 Role-based Authorization Strategy 2.3.2 When I try configure some Folder in Jenkins, "Enable project-based security" option is missing. 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-39905) Wrong Path for BitbucketWeb Source Files
Title: Message Title Christoph Forster created an issue Jenkins / JENKINS-39905 Wrong Path for BitbucketWeb Source Files Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Nov/21 10:15 AM Priority: Minor Reporter: Christoph Forster Using Git Plugin 3.0.0 the following Link is generated for Source-File-Changes using BitbucketWeb: https://myhostedbitbucket/projects/myProject/repos/myRepo/history/package/of/java/class.java Link leads to 404 - correct would be https://myhostedbitbucket/projects/myProject/repos/myRepo/browse/package/of/java/class.java "history" was dedected hardcoded in https://github.com/jenkinsci/git-plugin/blob/e3b32afe0697ec2825fb86b82417f311874cecc5/src/main/java/hudson/plugins/git/browser/BitbucketWeb.java#L70 Add Comment
[JIRA] (JENKINS-39176) Project-based security configuration doesn't work for folders and subfolders
Title: Message Title Roman Stepanchuk updated an issue Jenkins / JENKINS-39176 Project-based security configuration doesn't work for folders and subfolders Change By: Roman Stepanchuk Attachment: Screen Shot 2016-11-21 at 12.14.16.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-39176) Project-based security configuration doesn't work for folders and subfolders
Title: Message Title Roman Stepanchuk edited a comment on JENKINS-39176 Re: Project-based security configuration doesn't work for folders and subfolders If I have installed plugins: Folders Plugin 5.13 Role-based Authorization Strategy 2.3.2When I try configure some Folder in Jenkins, "Enable project-based security" option is missing. You can find mentioned option on screenshot !Screen Shot 2016-11-21 at 12.14.16.png|thumbnail! 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-39906) Fix PCT against core >= 2.16
Title: Message Title Andres Rodriguez created an issue Jenkins / JENKINS-39906 Fix PCT against core >= 2.16 Issue Type: Bug Assignee: Andres Rodriguez Components: credentials-binding-plugin Created: 2016/Nov/21 10:21 AM Environment: Jenkins 2.19.3 Credentials Binding 1.10 Priority: Minor Reporter: Andres Rodriguez The changes in JENKINS-21486 causes errors when running the tests against Jenkins >= 2.16 Add Comment
[JIRA] (JENKINS-39906) Fix PCT against core >= 2.16
Title: Message Title Andres Rodriguez started work on JENKINS-39906 Change By: Andres Rodriguez 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-39176) Project-based security configuration doesn't work for folders and subfolders
Title: Message Title Roman Stepanchuk edited a comment on JENKINS-39176 Re: Project-based security configuration doesn't work for folders and subfolders If I have installed plugins: Folders Plugin 5.13 Role-based Authorization Strategy 2.3.2When I try configure some Folder in Jenkins, "Enable project-based security" option is missing. You can find mentioned option on screenshot !Screen Shot 2016-11-21 at 12.14.16.png|thumbnail!I haven't specific plugin configuration, but sure I can provide all configuration, if you help me.Please clarify where is I can find configuration of 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-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title rsandell commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious I would also like to see what analysis/tools that failed, and some of the tests that failed. In certain systems there are known flaky tests, so if one of those are in the quick summary then you could just rerun from the summary page instead of having to go into details and you saved yourself a click or two more. 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Leo Gallucci commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage This missing feature might be one of main reasons why Jenkins is on HOLD in one of the most popular tech radars: https://www.thoughtworks.com/radar/tools 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Leo Gallucci take a look at Blue Ocean - we're building an entirely new user experience for CD pipelines, including a visual editor for 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-33185 Visualize parallel steps within a Pipeline Stage Change By: James Dumay Attachment: successful-pipeline.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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage [~elgalu] take a look at [Blue Ocean|https://jenkins.io/projects/blueocean/] - we're building an entirely new user experience for CD pipelines, including a [visual editor for Pipeline|https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/].Here's a preview that includes parallel visualisation: !successful-pipeline.png |thumbnail ! 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage [~elgalu] take a look at [Blue Ocean|https://jenkins.io/projects/blueocean/] - we're building an entirely new user experience for CD pipelines, including a [visual editor for Pipeline|https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/]. Here's a preview that includes parallel visualisation: !successful-pipeline.png|thumbnail! 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage [~elgalu] take a look at [Blue Ocean|https://jenkins.io/projects/blueocean/] - we're building an entirely new user experience for CD pipelines, including a [visual editor for Pipeline|https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/].Here's a preview screenshot that includes parallel visualisation: !successful-pipeline.png|thumbnail! 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage [~elgalu] take a look at [Blue Ocean|https://jenkins.io/projects/blueocean/] - we're building an entirely new user experience for CD pipelines, including a [visual editor for Pipeline|https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/].Here's a preview that includes parallel visualisation: !successful-pipeline.png |thumbnail ! 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Sorin Sbarnea commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Leo Gallucci Please remember that ThoughtWorks has its own CI/CD solutions so I would count their tech radar a biased one. Still, I have to confess that I partially support your view, I would love to be able to migrate OpenStack build jobs to pipelines but I doubt it would be possible in the next 1-2 years, and that's because they are not mature enough and because there were some design decisions regarding not supporting old jobs, making progressive transitions hardly possible. Shortly, future is bright for small companies with simple workflows as they would be able to benefit from Jenkins pipelines. Others are kinda screwed as I don't see any migration scenario working at this moment. 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-39906) Fix PCT against core >= 2.16
Title: Message Title rsandell assigned an issue to rsandell Jenkins / JENKINS-39906 Fix PCT against core >= 2.16 Change By: rsandell Assignee: Andres Rodriguez rsandell 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-39906) Fix PCT against core >= 2.16
Title: Message Title Andres Rodriguez assigned an issue to Andres Rodriguez Jenkins / JENKINS-39906 Fix PCT against core >= 2.16 Change By: Andres Rodriguez Assignee: rsandell Andres Rodriguez 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-39461) "Poll SCM" triggers don't generate valid Groovy in snippet generator
Title: Message Title rsandell commented on JENKINS-39461 Re: "Poll SCM" triggers don't generate valid Groovy in snippet generator I noticed this as well today with all the most recent plugin updates installed 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-38631) NullPointerException when packaging IPA (XCode plugin 1.4.11 & Jenkins 2.23)
Title: Message Title D A reopened an issue Why should one resave all configurations on upgrade? And if there is no other solution is there such instruction upon upgrade? Jenkins / JENKINS-38631 NullPointerException when packaging IPA (XCode plugin 1.4.11 & Jenkins 2.23) Change By: D A Resolution: Cannot Reproduce Status: Closed 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 jenkinsc
[JIRA] (JENKINS-39906) Fix PCT against core >= 2.16
Title: Message Title Andres Rodriguez updated JENKINS-39906 Jenkins / JENKINS-39906 Fix PCT against core >= 2.16 Change By: Andres Rodriguez 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-39907) Github pull requests gets unproper statuses url link
Title: Message Title Javier Delgado created an issue Jenkins / JENKINS-39907 Github pull requests gets unproper statuses url link Issue Type: Bug Assignee: Ivan Meredith Components: blueocean-display-url-plugin Created: 2016/Nov/21 10:47 AM Environment: ci.jenkins.io Priority: Critical Reporter: Javier Delgado As seen on https://github.com/jenkinsci/git-plugin/pull/212, the PR status links to https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgit-plugin/detail/PR-212/21/pipeline, returning a 404 error code. The real (even seemingly wrong) url is https://ci.jenkins.io/blue/organizations/jenkins%20/Plugins%2Fgit-plugin/detail/PR-212/21/pipeline/ Note the extra space (%20) after the organization name, causing the 404 Add Comment
[JIRA] (JENKINS-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title
squalou jenkins updated an issue
Jenkins / JENKINS-39899
workflow-lib : declaring several Libraries causes them to overlap
Change By:
squalou jenkins
Workflow lib is great, but still suffers some issues.Several libraries can be defined in Jenkins configuration. This is great. What I plan is :- a global 'core' lib for those boilerplate high level methods everyone need (not many methods, used by lots of people, shared among several jenkins instances)- a 'per jenkins instance' lib, see it as a 'per team' lib for any 'team-specific usecases', if they existMater is : apparently now the lib checkout MUST put 'vars' directory at the root of /jobs/jobId@libsSo, for instance, my libs are on a git repo, I tried to 'checkout in a specific subdirectory' : it doesn't workSo, ok, I leave it in default place ... but then I have to make a 'wipe and force clone' checkout. in the pipeline I would write this :{code:java}@Library ('lib-one')import method1// at this moment, the checkout is done, methods1 becomes available in classpath etc... great@ Livrary Library ('lib-two')import method2//at this moment : lib-two is checked out, lib-one is in the way ... that's where the 'wipe' option is handy, it removes lib-one from disk, even if it's still in memory //without the 'wipe' option, note that there will be a failure here {code}As a result there are several issues :- performance issues : useless git clone performed at each build- hard to setup (I lost hours finding this 'wipe clean chekcout' method- lack of readability : for a post-mortem analysis, lib sources that were used are no more available- rely on repo availability : this is specific to my situation where we have several SCM, the libs are on a 'less critical' one ... and if it's not available then all jobs fail. If I didn't need to wipe lib-one to get lib-two ... next run would simply use the current cached libs.What could work :- either have several @libs dirs, but it's probably not that easy- or correctly follow the 'checkout in subdir' to look for 'vars' etc...
Add Comment
[JIRA] (JENKINS-14054) The "Root POM" field value in the Build section of a Maven job configuration is not being read in.
Title: Message Title Michael Paesold commented on JENKINS-14054 Re: The "Root POM" field value in the Build section of a Maven job configuration is not being read in. No, I can't reproduce either. Earliest tested version is LTS 1.609.3. That and all later versions are good. I propose to resolve this issue. Any objections? 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-26700) Download build artifacts as zip generates a corrupted file
Title: Message Title Fritz Elfert commented on JENKINS-26700 Re: Download build artifacts as zip generates a corrupted file Well thats a little confusing. After all, the title specifically names zip artifacts. So: yes, I'd suggest a separate issue if it is not about zipped artifacts. Of course thats MY personal opinion only. 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-24581) tasks status icon not visible at overview of single task
Title: Message Title Michael Paesold commented on JENKINS-24581 Re: tasks status icon not visible at overview of single task I would like to get the fix merged. I am willing to update the merge request. Anyone of the original participants still interested in this 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-39774) API: export getAllItems() to be accessed from the RestAPI
Title: Message Title Victor Martinez commented on JENKINS-39774 Re: API: export getAllItems() to be accessed from the RestAPI Hi Daniel, I've got a few instances with some matrix project, no maven project I'm afraid, what do you want me to test? Besides of that, Is there any reason why it's not exported? 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-33265) I am not able to see Build envirment at my job configuaration page
Title: Message Title Victor Martinez assigned an issue to Unassigned Jenkins / JENKINS-33265 I am not able to see Build envirment at my job configuaration page Change By: Victor Martinez Assignee: Victor Martinez 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-33265) I am not able to see Build envirment at my job configuaration page
Title: Message Title Victor Martinez commented on JENKINS-33265 Re: I am not able to see Build envirment at my job configuaration page I guess this issue is about the RVM plugin or a similar one rather than the Jenkins Lint plugin. Cheers 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-33265) I am not able to see Build envirment at my job configuaration page
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-33265 I am not able to see Build envirment at my job configuaration page Change By: Victor Martinez Component/s: rvm-plugin Component/s: jenkinslint-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-34562) Parameterized Build option not providing advanced button in build page
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-34562 Parameterized Build option not providing advanced button in build page Change By: Victor Martinez Component/s: other Component/s: jenkinslint-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-34562) Parameterized Build option not providing advanced button in build page
Title: Message Title Victor Martinez commented on JENKINS-34562 Re: Parameterized Build option not providing advanced button in build page Please fill this ticket with the right component. Cheers 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-33265) I am not able to see Build envirment at my job configuaration page
Title: Message Title stanley shen commented on JENKINS-33265 Re: I am not able to see Build envirment at my job configuaration page I am still trying to figure out what exactly the cause for my case, will update here if I got more information or proof. 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-39908) Update Documentation to match Pattern
Title: Message Title Stephan Watermeyer created an issue Jenkins / JENKINS-39908 Update Documentation to match Pattern Issue Type: Task Assignee: Stephan Watermeyer Components: maven-artifact-choicelistprovider-plugin Created: 2016/Nov/21 11:18 AM Priority: Minor Reporter: Stephan Watermeyer Test Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39908) Update Documentation to match Pattern
Title: Message Title Stephan Watermeyer closed an issue as Fixed Jenkins / JENKINS-39908 Update Documentation to match Pattern Change By: Stephan Watermeyer 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-39908) Update Documentation to match Pattern
Title: Message Title Stephan Watermeyer resolved as Fixed Documentation Updated Jenkins / JENKINS-39908 Update Documentation to match Pattern Change By: Stephan Watermeyer Status: In Progress 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-39908) Update Documentation to match Pattern
Title: Message Title Stephan Watermeyer started work on JENKINS-39908 Change By: Stephan Watermeyer 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-39909) Incomplete downloads of artifacts
Title: Message Title chris_mh3 created an issue Jenkins / JENKINS-39909 Incomplete downloads of artifacts Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Nov/21 11:52 AM Environment: Jenkins 2.19.3 Windows Server 2008 R2 jdk1.8.0_66 (and jdk1.7.0_51) Priority: Major Reporter: chris_mh3 When downloading artifacts from jenkins (lastSuccessfulBuild/artifact) the download terminates with incomplete files quite frequently. This only seems to happen with files > 60MB for me. The corresponding exception in the error.log seems to be: Nov 17, 2016 10:28:16 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: request.getSession() in /job//artifact/.jar. Reason: java.lang.IllegalStateException: Response is committed java.lang.IllegalStateException: Response is committed at org.eclipse.jetty.server.Request.getSession(Request.java:1400) at org.eclipse.jetty.server.Request.getSession(Request.java:1378) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:279) at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExp
[JIRA] (JENKINS-26700) Download build artifacts as zip generates a corrupted file
Title: Message Title chris_mh3 edited a comment on JENKINS-26700 Re: Download build artifacts as zip generates a corrupted file I would be very surprised if this would fix Srinivasan Venkataraman's and my problem. In my case it's not with zip files at all.Should I open a new issue for this? JENKINS-39909 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-24581) tasks status icon not visible at overview of single task
Title: Message Title podskalsky commented on JENKINS-24581 Re: tasks status icon not visible at overview of single task At the moment we don't use that feature. But If you will merge it, I can check if the new version of the plugin is working 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-39879) Add pipeline documentation
Title: Message Title Johnny Willemsen closed an issue as Fixed Closing, after installing the plugin there is documentation installed Jenkins / JENKINS-39879 Add pipeline documentation Change By: Johnny Willemsen Status: Open Closed 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/
[JIRA] (JENKINS-39896) AWS EC2 Build Slave Always offline (even though it is ready to Rock).
Title: Message Title Michael de Silva commented on JENKINS-39896 Re: AWS EC2 Build Slave Always offline (even though it is ready to Rock). I've managed to get over the slave connectivity issue partially, closing for now https://gist.github.com/bsodmike/b8deb3804e135a0f5b34adfb8a61deef 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-39896) AWS EC2 Build Slave Always offline (even though it is ready to Rock).
Title: Message Title Michael de Silva closed an issue as Postponed My solution so far https://gist.github.com/bsodmike/b8deb3804e135a0f5b34adfb8a61deef Jenkins / JENKINS-39896 AWS EC2 Build Slave Always offline (even though it is ready to Rock). Change By: Michael de Silva Status: Open Closed Resolution: Postponed 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...@go
[JIRA] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin"" was unexpected at this time.' error
Title: Message Title Sravya Pudota commented on JENKINS-11992 Re: Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin"" was unexpected at this time.' error Any updates or any temporary fixes? 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-39910) Docker Pipeline gails when using Pipelinescript from SCM
Title: Message Title
Shaun Adams created an issue
Jenkins / JENKINS-39910
Docker Pipeline gails when using Pipelinescript from SCM
Issue Type:
Bug
Assignee:
magnayn
Components:
docker-plugin, pipeline
Created:
2016/Nov/21 12:59 PM
Environment:
Jenkins ver. 2.7.4 NAME="Red Hat Enterprise Linux Server" VERSION="7.2 (Maipo)"
Priority:
Minor
Reporter:
Shaun Adams
Using the same syntax, Docker builds fail when using Pipeline Script from SCM. The syntax that works on Pipeline Script but fails when copying from SCM is
stage ("Build Docker image"){
def image = docker.build('sam/base-image:'+BUILD_NUMBER, '.')
}
The error is
java.io.IOException: Cannot retrieve .Id from 'docker inspect sam/base-image:3' at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:190) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:115) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at j
[JIRA] (JENKINS-39910) Docker Pipeline fails when using Pipelinescript from SCM
Title: Message Title Shaun Adams updated an issue Jenkins / JENKINS-39910 Docker Pipeline fails when using Pipelinescript from SCM Change By: Shaun Adams Summary: Docker Pipeline gails fails when using Pipelinescript from SCM 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-37462) Polling breaks with multiple slaves with own workspace
Title: Message Title Hugues Moreau commented on JENKINS-37462 Re: Polling breaks with multiple slaves with own workspace Hi Paul, very quickly: it seems to work with "checkout" and the filter you suggested. I wil have to factorize all that blob of awful configuration in a user-function in our groovy library, but I think that will do, many thanks. (still happy to test stuff for you if needed) 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Leo Gallucci updated an issue Jenkins / JENKINS-33185 Visualize parallel steps within a Pipeline Stage Change By: Leo Gallucci Attachment: blue-ocean-parallel-generated-view.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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
Leo Gallucci commented on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
Yes Sorin Sbarnea I also thought about them being biased, I assisted their tech radar presentation and the topic came, the presenter assured they are not biased and they make a big effort to be objective and explained all the reasons behind it. James Dumay Blue Ocean looked promising, I installed it. Why a visual editor? shouldn't the view be generated out of the Jenkinsfile? I thought we want pipeline as code. So I tried to write `parallel` Jenkinsfiles and the generated view looks weird, both examples: Left example
node() {
stage('Build') {
println 'I prepare the build for the parallel steps'
}
parallel (
"chrome" : { println 'running tests in chrome' },
"firefox" : { println 'running tests in firefox' },
"edge" : { println 'running tests in edge' }
)
}
Right example
node() {
stage('Build') {
println 'I prepare the build for the parallel steps'
}
parallel (
"chrome" : { stage('chrome') { println 'running tests in chrome' } },
"firefox" : { stage('firefox') { println 'running tests in firefox' } },
"edge" : { stage('edge') { println 'running tests in edge' } }
)
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39911) Extremely slow Build with Parameters page loads with underscores in parameter description field
Title: Message Title Robert Beddow created an issue Jenkins / JENKINS-39911 Extremely slow Build with Parameters page loads with underscores in parameter description field Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Nov/21 1:13 PM Priority: Minor Reporter: Robert Beddow Hi, I have a jenkins setup with all sorts of parameterised jobs, but I had this one job, which is quite small, i.e. just a handful of fields, which took forever to load the "Build with Parameters" page. Most of my pages load in less than 1000ms. This page took > 500,000ms. Conveniently this particular job was copied from another job and only a few small modifications made. Yet the original loaded in around 1000ms, while the modified one loaded in 500,000ms. One of the modifications was to the description field of one of the parameters. The new one referenced a name that included a number of underscores. If I removed that name, the page load time reduced back to 1000ms. Replacing the underscores with other characters ( "/", ".", "x", etc.) also resulted in a 1000ms page load time. I found that once I had 4 or 5 underscores in the description field I started to notice an increase in page load time. The very slow load time was associated with 21 underscores in the description field. I also placed the names with all those underscores in other parameter description fields and it had the same slowing effect. It doesn't appear to cause a problem in the General description field though. The workaround for me has obviously been to remove those names with underscores from the description field. It's only a description after all.
[JIRA] (JENKINS-39911) Build with Parameters page loads extremely slowly with underscores in parameter description field
Title: Message Title Robert Beddow updated an issue Jenkins / JENKINS-39911 Build with Parameters page loads extremely slowly with underscores in parameter description field Change By: Robert Beddow Summary: Extremely slow Build with Parameters page loads extremely slowly with underscores in parameter description field 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-39912) P4-Plugin > SSL issue, Server Connection Error.
Title: Message Title Mark Pender created an issue Jenkins / JENKINS-39912 P4-Plugin > SSL issue, Server Connection Error. Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Nov/21 1:14 PM Environment: Jenkins : 2.25 P4-plugin : 1.4.9 Jenkins Master Java version: openjdk version "1.8.0_102" Jenkins Slave Java version : openjdk version "1.8.0_111" Priority: Major Reporter: Mark Pender Using Jenkins Master with multiple slaves which have a base version of JDK installed, using the p4-plugin version listed above to pass perforce credentials. The test functionality for Perforce does not appear to work but I only get a 'Server Connection Error' when testing. I am also using the java us_policy in $JAVA/security... etc Is there any dependency I am missing ? Can I also ask that more verbose logging be included in the plugin Add Comment
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Diego Molina updated an issue Jenkins / JENKINS-33185 Visualize parallel steps within a Pipeline Stage Change By: Diego Molina 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Diego Molina updated an issue Jenkins / JENKINS-33185 Visualize parallel steps within a Pipeline Stage Change By: Diego Molina 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-37462) Polling breaks with multiple slaves with own workspace
Title: Message Title Paul Allen commented on JENKINS-37462 Re: Polling breaks with multiple slaves with own workspace Thanks, that is good news. If you want to try the snapshot, the build 459 link in the earlier post will give you the HPI file (p4-1.4.10-SNAPSHOT.hpi); download it and install the snapshot in Jenkins by using: Jenkins > Manage Jenkins > Manage Plugins > Advanced (tab) > Upload File > (choose the downloaded HPI) > Upload. You may need to restart Jenkins to take effect. You can remove it by going to Manage Plugins and downgrading, and restart as required. 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-39913) Pipeline viewed in classic dashboard does not render logs dropdown when clicked on Logs button for a stage
Title: Message Title Jim Klimov created an issue Jenkins / JENKINS-39913 Pipeline viewed in classic dashboard does not render logs dropdown when clicked on Logs button for a stage Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2016/Nov/21 1:18 PM Priority: Minor Reporter: Jim Klimov Jenkins 2.32 and Pipeline plugin (installed late last week) runs my Multiple Pipeline job and displays the stages in classic view dashboard, and when I hover on a running or finished step, a popup appears with the Logs button. From Youtube presentations I know there should appear a list on top side of browser window with links to steps' sub-logs and timings, but in practice my browser window just grays out and becomes unclickable (invisible modal window?) Refreshing or pressing ESC (sometimes more than once) brings back the usable browser, but no logs are seen. The original console log is viewable, in all its multimegabyte entirety. Add Comment
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
malcolm crum commented on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
Can you try this instead:
node() {
stage('Build') {
println 'I prepare the build for the parallel steps'
}
stage('Test') {
parallel (
"chrome" : { println 'running tests in chrome' },
"firefox" : { println 'running tests in firefox' },
"edge" : { println 'running tests in edge' }
)
}
}
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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Leo Gallucci updated an issue Jenkins / JENKINS-33185 Visualize parallel steps within a Pipeline Stage Change By: Leo Gallucci Attachment: blue-ocean-parallel-WORKS.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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Diego Molina commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I guess it is better to read a bit how it works before Leo Gallucci 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Leo Gallucci commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Yay! thanks malcolm crum (my bad) 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-38533) Pull Requests checkout the wrong commit
Title: Message Title Carsten Kuhl commented on JENKINS-38533 Re: Pull Requests checkout the wrong commit Hello Alexander Gerock, thanks for your input, but I think you talked about another plug-in. 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.
