[JIRA] (JENKINS-40188) Unable to use build step with boolean parameterized parameter
Title: Message Title aurelien leboulanger commented on JENKINS-40188 Re: Unable to use build step with boolean parameterized parameter booleanParam(name: 'SIMUL', value: env.SIMUL) not works: java.lang.ClassCastException: hudson.model.BooleanParameterValue.value expects boolean but received class java.lang.String Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40328) NeoLoad plugin causes long load times of unrelated job pages
Title: Message Title Roderich Schupp created an issue Jenkins / JENKINS-40328 NeoLoad plugin causes long load times of unrelated job pages Issue Type: Bug Assignee: Unassigned Components: neoload-jenkins Created: 2016/Dec/09 7:52 AM Environment: Jenkins 1.609.3 NeoLoad Plugin 2.0.1 Priority: Major Reporter: Roderich Schupp We have some jobs with a large number of artifacts (~4000 files in ~1200 directories per build). Displaying the job page for one of these jobs takes 30 seconds or more. These jobs do not use the NeoLoad plugin at all. Deinstalling the plugin makes the job page display in under 1 second. The reason is that the plugin's action are executed for every job, whether it uses the plugin or not. The action scans all artifacts of all builds of the job looking for the (one) NeoLoad results file (cf. findXMLResultsFile). The plugin should run the action only if the job actually uses the plugin. If that's not possible, I suggest an approach similar to what the JUnit plugin does: look for the test result file in post-build and persist that file with a fixed name (but not as an artifact).
[JIRA] (JENKINS-40314) [BlueOcean] Port mismatch between Jenkins and BlueOcean beta
Title: Message Title Gram Gram commented on JENKINS-40314 Re: [BlueOcean] Port mismatch between Jenkins and BlueOcean beta James Dumay as you pointed out, Manage Jenkins -> Jenkins Location -> Jenkins URL does not change, when HTTP_PORT was changed in /var/default/jenkins. I see I should manually change Jenkins URL when HTTP_PORT is changed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40327) "Build Now" does not work when using gitlab-plugin and webhooks
Title: Message Title Robin Björklin created an issue Jenkins / JENKINS-40327 "Build Now" does not work when using gitlab-plugin and webhooks Issue Type: Bug Assignee: Robin Müller Components: gitlab-plugin Created: 2016/Dec/09 7:17 AM Priority: Minor Reporter: Robin Björklin As stated in the subject "Build Now" does not work when using gitlab-plugin and webhooks when configured as described here: https://github.com/jenkinsci/gitlab-plugin Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-20994) Make "Just accept and fetch from a build workspace" more full featured
Title: Message Title Lakshmi Narasimhan Vaikuntam commented on JENKINS-20994 Re: Make "Just accept and fetch from a build workspace" more full featured Issue fixed in v 1.2.0.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20994) Make "Just accept and fetch from a build workspace" more full featured
Title: Message Title Lakshmi Narasimhan Vaikuntam resolved as Fixed Jenkins / JENKINS-20994 Make "Just accept and fetch from a build workspace" more full featured Change By: Lakshmi Narasimhan Vaikuntam 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-29130) RTC Polling broken when Proxy enabled
Title: Message Title Lakshmi Narasimhan Vaikuntam commented on JENKINS-29130 Re: RTC Polling broken when Proxy enabled David Jozis, Can you confirm whether you are using "Avoid using build toolkit on Master" option in the global or job configuration? If this option is not being used, then the issue is with build toolkit not honouring nonProxyHosts property. This has been fixed in build toolkit v 6.0.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-29130) RTC Polling broken when Proxy enabled
Title: Message Title Lakshmi Narasimhan Vaikuntam commented on JENKINS-29130 Re: RTC Polling broken when Proxy enabled This is an issue with build toolkit not honouring the nonProxyHosts property. See defect 366658. The issue has been fixed in build toolkit 6.0.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-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Lakshmi Narasimhan Vaikuntam commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure @suresh, Can you confirm whether you see this issue in the latest version of Team Concert 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-28847) Customize snapshot / baseline name
Title: Message Title Lakshmi Narasimhan Vaikuntam resolved as Fixed Fixed in 1.2.0.2 Jenkins / JENKINS-28847 Customize snapshot / baseline name Change By: Lakshmi Narasimhan Vaikuntam 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-28847) Customize snapshot / baseline name
Title: Message Title Lakshmi Narasimhan Vaikuntam commented on JENKINS-28847 Re: Customize snapshot / baseline name Support for customizing snapshot name has been added in 1.2.0.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-39178) RTC Plugin: Request Build Fails toolkit not found
Title: Message Title Lakshmi Narasimhan Vaikuntam resolved as Fixed Fixed in 1.1.9.9 Jenkins / JENKINS-39178 RTC Plugin: Request Build Fails toolkit not found Change By: Lakshmi Narasimhan Vaikuntam 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-25981) RTC plugin errors with parallel builds
Title: Message Title Lakshmi Narasimhan Vaikuntam commented on JENKINS-25981 Re: RTC plugin errors with parallel builds In 1.2.0.0, we have added support for building from a Stream. This will not have any load issues with parallel builds. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21964) Build definition and workspace name should accept parameters and/or environment variables.
Title: Message Title Lakshmi Narasimhan Vaikuntam resolved as Fixed Fixed in 1.2.0.1 Jenkins / JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. Change By: Lakshmi Narasimhan Vaikuntam 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,
[JIRA] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Title: Message Title Lakshmi Narasimhan Vaikuntam commented on JENKINS-21964 Re: Build definition and workspace name should accept parameters and/or environment variables. Support for parameters in Build definition, Repository Workspace, Stream names has been added in 1.2.0.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19387) Get a specific baseline or snapshot from JazzRTC
Title: Message Title Lakshmi Narasimhan Vaikuntam resolved as Fixed Fixed in 1.2.0.0 Jenkins / JENKINS-19387 Get a specific baseline or snapshot from JazzRTC Change By: Lakshmi Narasimhan Vaikuntam 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-19387) Get a specific baseline or snapshot from JazzRTC
Title: Message Title Lakshmi Narasimhan Vaikuntam commented on JENKINS-19387 Re: Get a specific baseline or snapshot from JazzRTC In 1.2.0.0, support has been added to load from a snapshot. You have to pass the snapshot name or UUID to the plugin configuration. See https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin#TeamConcertPlugin-JobConfiguration for more information on configuring the plugin to load from a snapshot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40304) Snippet generator does not generate valid code for ReverseBuildTrigger
Title: Message Title Bruce Merry commented on JENKINS-40304 Re: Snippet generator does not generate valid code for ReverseBuildTrigger I also had trouble getting it to show up when starting with a fresh Docker image. I fiddled around creating jobs until it worked, but I didn't keep a record of what I did and I'm not sure what the magic combination was. I recall creating a freestyle job and a (non-multibranch) pipeline job, and possibly the snippet generator showed the option on that pipeline job rather than the MBPL I was trying to set up. In production the option shows up when I use the snippet generator on a MBPL though. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-35867) Motion for status indicators changing status
Title: Message Title Brody Maclean commented on JENKINS-35867 Re: Motion for status indicators changing status In Progress, Success indicator and pipeline animations http://codepen.io/brody/pen/XNgYNW Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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 created an issue Jenkins / JENKINS-40326 Pipeline results (karaoke) doesn't reload when master is restarted Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/09 3:40 AM Priority: Minor Reporter: Michael Neale Run a long running pipeline Open pipeline results screen and follow along While running, restart the master Note that results screen never subsequently updates What should happen: Results screen should trigger a full reload (which may involve logging in) but then continue following along. tyler croy discovered this recently. Add Comment
[JIRA] (JENKINS-40323) No SCM selected when adding a shared library
Title: Message Title James Dumay commented on JENKINS-40323 Re: No SCM selected when adding a shared library What is "modern scm" vs "legacy 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-38491) Add new "waitingForInput" status to API for runs, dag and steps
Title: Message Title Michael Neale updated JENKINS-38491 Jenkins / JENKINS-38491 Add new "waitingForInput" status to API for runs, dag and steps Change By: Michael Neale 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-40325) Unable to create a VM with multiple networks
Title: Message Title Tim Soderstrom created an issue Jenkins / JENKINS-40325 Unable to create a VM with multiple networks Issue Type: Bug Assignee: Oliver Gondža Components: openstack-cloud-plugin Created: 2016/Dec/09 2:51 AM Priority: Major Reporter: Tim Soderstrom The current version of openstack-clouds plugin does not seem to allow for creating multiple networks on a slave. This is required because we have a private only network Jenkins would be SSHing from that differs from the "public" network which has the default gateway. Add Comment
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Zeus Minos commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens Seams to me that I am experiencing similar issue. Just for reference I am using the latest Jenkins 2.35 with all the latest Gitlab/Pipeline plugins. My Gitlab (Hosted on our own servers) version is 8.13.2. I have been using webhooks to start other non-pipeline Jenkins jobs and it works ok. I tried to do the same thing using a pipeline Jenkins job and GitLab will return "Hook executed successfully but returned HTTP 500" and nothing happens on the Jenkins side. My pipeline job just display a message on the console if the job gets triggered. This is the link used on my Gitlab webhook: http://MyJenkinsServer/gitlab/build_now/MyPipelineJob Any help is more than welcome Down below is my pipeline code. http://paste.ofcode.org/B9VFa5fHxEqbxKqxLEFAki Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40052) Office 365 Connector doesn't supply commiter name(s) for events started by SCM change
Title: Message Title Srivardhan Hebbar resolved as Fixed Released version 1.4 with support to show authors if the build is due to SCM change. Jenkins / JENKINS-40052 Office 365 Connector doesn't supply commiter name(s) for events started by SCM change Change By: Srivardhan Hebbar 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
[JIRA] (JENKINS-39580) Allow configuring which DisplayUrlProvider to use
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39580 Re: Allow configuring which DisplayUrlProvider to use Code changed in jenkins User: James William Dumay Path: src/main/java/org/jenkinsci/plugins/displayurlapi/ClassicDisplayURLProvider.java src/main/java/org/jenkinsci/plugins/displayurlapi/DisplayURLProvider.java src/main/java/org/jenkinsci/plugins/displayurlapi/actions/AbstractDisplayAction.java src/main/java/org/jenkinsci/plugins/displayurlapi/user/PreferredProviderUserProperty.java src/main/java/org/jenkinsci/plugins/displayurlapi/user/PreferredProviderUserPropertyDescriptor.java src/main/resources/org/jenkinsci/plugins/displayurlapi/Messages.properties src/main/resources/org/jenkinsci/plugins/displayurlapi/user/PreferredProviderUserProperty/config.jelly src/main/resources/org/jenkinsci/plugins/displayurlapi/user/PreferredProviderUserProperty/help-providerId.html src/test/java/org/jenkinsci/plugins/displayurlapi/actions/ActionRedirectExtendedTest.java http://jenkins-ci.org/commit/display-url-api-plugin/4f280c227750f37d6c8be8c5532c9701758c55ad Log: JENKINS-39580 Allow the user to configure a preferred provider (#5) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39580) Allow configuring which DisplayUrlProvider to use
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39580 Re: Allow configuring which DisplayUrlProvider to use Code changed in jenkins User: James Dumay Path: pom.xml src/main/java/org/jenkinsci/plugins/displayurlapi/ClassicDisplayURLProvider.java src/main/java/org/jenkinsci/plugins/displayurlapi/DisplayURLProvider.java src/main/java/org/jenkinsci/plugins/displayurlapi/actions/AbstractDisplayAction.java src/main/java/org/jenkinsci/plugins/displayurlapi/user/PreferredProviderUserProperty.java src/main/java/org/jenkinsci/plugins/displayurlapi/user/PreferredProviderUserPropertyDescriptor.java src/main/resources/org/jenkinsci/plugins/displayurlapi/user/PreferredProviderUserProperty/config.jelly src/test/java/org/jenkinsci/plugins/displayurlapi/actions/ActionRedirectExtendedTest.java http://jenkins-ci.org/commit/display-url-api-plugin/c3bd84e7773c8057374b49c16c3a6d97767f1c48 Log: JENKINS-39580 - Allow configuring which DisplayUrlProvider to use Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40207) Uninstalling alternative display url providers should keep issued URLs the same
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40207 Re: Uninstalling alternative display url providers should keep issued URLs the same Code changed in jenkins User: James William Dumay Path: pom.xml src/main/java/org/jenkinsci/plugins/displayurlapi/ClassicDisplayURLProvider.java src/main/java/org/jenkinsci/plugins/displayurlapi/DisplayURLProvider.java src/main/java/org/jenkinsci/plugins/displayurlapi/actions/AbstractDisplayAction.java src/main/java/org/jenkinsci/plugins/displayurlapi/actions/JobDisplayAction.java src/main/java/org/jenkinsci/plugins/displayurlapi/actions/RunDisplayAction.java src/test/java/org/jenkinsci/plugins/displayurlapi/DisplayURLProviderTest.java src/test/java/org/jenkinsci/plugins/displayurlapi/JenkinsRuleWithLocalPort.java src/test/java/org/jenkinsci/plugins/displayurlapi/actions/AbstractActionRedirectTest.java src/test/java/org/jenkinsci/plugins/displayurlapi/actions/ActionRedirectClassicTest.java src/test/java/org/jenkinsci/plugins/displayurlapi/actions/ActionRedirectExtendedTest.java http://jenkins-ci.org/commit/display-url-api-plugin/ffadcca1e3ecf114abc46eddfc1dcb1f5325b653 Log: JENKINS-40207 - Uninstalling alternative display url providers should keep issued URLs the same (#4) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40323) No SCM selected when adding a shared library
Title: Message Title Patrick Wolf commented on JENKINS-40323 Re: No SCM selected when adding a shared library Is this true for modern SCM, too? Should error on saving if they don't select something. I wouldn't want to choose a default for users. There's too much configuration needed to have a real default. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40324) Show links to certain artifacts while build is still running
Title: Message Title Brady Wied created an issue Jenkins / JENKINS-40324 Show links to certain artifacts while build is still running Issue Type: Improvement Assignee: Unassigned Components: workflow-aggregator-plugin Created: 2016/Dec/09 12:57 AM Priority: Minor Reporter: Brady Wied It might be useful to allow some artifacts that have been archived already to be visible from the build status page while a pipeline build is still in progress. The example I'm thinking of is the build generates a changelog HTML artifact and then is at an input step awaiting approval for deployment. The approver might wish to look at the changelog before they click the button. This is kind of similar to JENKINS-19154. Add Comment
[JIRA] (JENKINS-40323) No SCM selected when adding a shared library
Title: Message Title James Dumay commented on JENKINS-40323 Re: No SCM selected when adding a shared library Patrick Wolf we should revisit this and give it some design love. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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 Ivan Meredith started work on JENKINS-39907 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-40296) REGRESSION: Commit messages are not showing up in activities, branches and PR tables
Title: Message Title Ivan Meredith resolved as Fixed Jenkins / JENKINS-40296 REGRESSION: Commit messages are not showing up in activities, branches and PR tables Change By: Ivan Meredith 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-40224) Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Title: Message Title James Dumay commented on JENKINS-40224 Re: Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly @jeanfred sorry you ran into a problem. What was broken about the links we generated? Did the page 404, etc? We do have a configurable option in development for switching your links between Blue Ocean and Classic Jenkins. You can watch it on JENKINS-39580. You mentioned that being switched to Blue Ocean is inconvenient. Is there something missing from Blue Ocean today that makes it hard for you to switch away from Classic? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40323) No SCM selected when adding a shared library
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-40323 No SCM selected when adding a shared library Issue Type: Bug Assignee: CloudBees Inc. Attachments: Selection_018.png Components: pipeline Created: 2016/Dec/09 12:31 AM Environment: Jenkins 2.19.4, fresh Pipeline installation as of 2016-12-08 Priority: Minor Reporter: R. Tyler Croy When configuring a Shared Library, after selecting "Legacy SCM" or "Modern SCM" the SCM options are listed with a radio selection UI element. Unfortunately there is no item in that radio selection that is selected by default, meaning if the user doesn't notice nothing has been actually selected in the radio selection, might Save the configuration and be very confused with their Shared Libraries don't work. Add Comment
[JIRA] (JENKINS-40224) Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40224
Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Change By:
James Dumay
After installing BlueOcean beta, all links in the emails were changed to use BlueOcean URLs (which I find inconvenient, this should not be automatic in my opinion and I have been able to find a config option for this − happy to open a separate bug for this).For the emails indicating a failure, the links are broken. Here are some examples:* {{ https://jenkins.company.com/blue/organizations/jenkins/jobA/detail/jobA/42/--/ }}* {{ https://jenkins.acme.com/blue/organizations/jenkins/jobB/detail/jobB/773/--/ }}After uninstalling the BlueOcean plugins, the links are functional again:*{{ https://jenkins.acme.com/job/jobB/777/--/ }} which redirects properly to {{ https://jenkins.acme.com/job/jobB/777/ }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40224) Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40224
Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Change By:
James Dumay
After installing BlueOcean beta, all links in the emails were changed to use BlueOcean URLs (which I find inconvenient, this should not be automatic in my opinion and I have been able to find a config option for this − happy to open a separate bug for this).For the emails indicating a failure, the links are broken. Here are some examples:* {{ https://jenkins.company.com/blue/organizations/jenkins/jobA/detail/jobA/42/--/ }}* {{ https://jenkins.acme.com/blue/organizations/jenkins/jobB/detail/jobB/773/--/ }}After uninstalling the BlueOcean plugins, the links are functional again:* {{ https://jenkins.acme.com/job/jobB/777/--/ }} which redirects properly to {{ https://jenkins.acme.com/job/jobB/777/ }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40314) [BlueOcean] Port mismatch between Jenkins and BlueOcean beta
Title: Message Title
James Dumay edited a comment on JENKINS-40314
Re: [BlueOcean] Port mismatch between Jenkins and BlueOcean beta
[~gram7gram] when you changed the port in {{/var/default/jenkins}} did it change the URL in {{ Manage Jenkins -> Jenkins Location -> Jenkins URL }} ? I believe this is where we get the full URL.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-40314) [BlueOcean] Port mismatch between Jenkins and BlueOcean beta
Title: Message Title
James Dumay commented on JENKINS-40314
Re: [BlueOcean] Port mismatch between Jenkins and BlueOcean beta
Gram Gram when you changed the port in /var/default/jenkins did it change the URL in {{Manage Jenkins -> Jenkins Location -> Jenkins URL}}?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-40296) REGRESSION: Commit messages are not showing up in activities, branches and PR tables
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40296 Re: REGRESSION: Commit messages are not showing up in activities, branches and PR tables Code changed in jenkins User: Ivan Meredith Path: src/main/js/api/git.js src/test/js/multibranch/commitMessages.js src/test/resources/multibranch/commit_message/Jenkinsfile http://jenkins-ci.org/commit/blueocean-acceptance-test/7c10546856b7033fdfe8192aa92a2de7e189971d Log: JENKINS-40296 Tests to cover changeset messages (#85) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38670 Re: ability to enter build notes/parameters for a Manual step in the pipeline Code changed in jenkins User: Dan Alvizu Path: pom.xml src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/DownstreamProjectGridBuilder.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/ProjectForm.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildVariablesHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/FilteredVariablesHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/NullColumnHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/ParametersActionHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtension.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtensionDescriptor.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleColumnHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleRowHeader.java src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/AbstractNameValueHeader/projectCardTemplate.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildVariablesHeader/config.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/FilteredVariablesHeader/config.jelly src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/ProjectFormTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/FilteredVariablesHeaderTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/c12811d41bec5ab3e213158af9ccf002bce87c91 Log: Merge remote-tracking branch 'origin/master' into JENKINS-38670 Conflicts: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtension.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/d0d2352d9a71...c12811d41bec Add Comment
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Torben Knerr commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Sam Van Oort Jesse Glick thanks for the feedback! Good to hear that stage view is still maintained. Understood it needs a community PR. Would love to see it, but currently too short on time too :-/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40322) Re-run link offered but doesn't do anything
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-40322
Re-run link offered but doesn't do anything
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2016/Dec/08 11:13 PM
Environment:
ci.blueocean.io, hash {{b2cd597}}
Priority:
Minor
Reporter:
Andrew Bayer
A PR build of the editor failed and I was trying to get it to rebuild - I logged into ci.blueocean.io, and now there's a "Re-run" button, but when I click it...nothing happens. I have no idea why. =) I do have permission to launch a build (which I did outside of Blue Ocean, since I can't honestly tell how to just kick off a build manually through Blue Ocean in the first place).
Add Comment
[JIRA] (JENKINS-40304) Snippet generator does not generate valid code for ReverseBuildTrigger
Title: Message Title Daniel Beck commented on JENKINS-40304 Re: Snippet generator does not generate valid code for ReverseBuildTrigger I can't get the reverse build trigger to show up in the snippet generator for a MBPL, there's just periodically and periodically if not otherwise. Any idea why? Could you provide detailed steps to reproduce from scratch? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39355) API improvements based on real-world implementation and usage
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39355 Re: API improvements based on real-world implementation and usage Code changed in jenkins User: Stephen Connolly Path: README.md docs/basic-multi-branch.png docs/branch-sources.png docs/implementation.adoc docs/user.adoc pom.xml src/images/make-inkscape.sh src/images/organization-folder.svg src/main/java/jenkins/branch/BaseEmptyView.java src/main/java/jenkins/branch/Branch.java src/main/java/jenkins/branch/BranchCategoryFilter.java src/main/java/jenkins/branch/BranchEventCause.java src/main/java/jenkins/branch/BranchNameContributor.java src/main/java/jenkins/branch/BranchProjectFactory.java src/main/java/jenkins/branch/BranchProjectFactoryDescriptor.java src/main/java/jenkins/branch/BranchProperty.java src/main/java/jenkins/branch/BranchPropertyDescriptor.java src/main/java/jenkins/branch/BranchStatusColumn.java src/main/java/jenkins/branch/CustomOrganizationFolderDescriptor.java src/main/java/jenkins/branch/DescriptionColumn.java src/main/java/jenkins/branch/JobDecorator.java src/main/java/jenkins/branch/LocalizedViewsTabBar.java src/main/java/jenkins/branch/MetadataActionFolderIcon.java src/main/java/jenkins/branch/MultiBranchCategoryFilter.java src/main/java/jenkins/branch/MultiBranchProject.java src/main/java/jenkins/branch/MultiBranchProjectDescriptor.java src/main/java/jenkins/branch/MultiBranchProjectEmptyView.java src/main/java/jenkins/branch/MultiBranchProjectFactory.java src/main/java/jenkins/branch/MultiBranchProjectViewHolder.java src/main/java/jenkins/branch/NamedExceptionsBranchPropertyStrategy.java src/main/java/jenkins/branch/OrganizationFolder.java src/main/java/jenkins/branch/OrganizationFolderEmptyView.java src/main/java/jenkins/branch/OrganizationFolderViewHolder.java src/main/java/jenkins/branch/ParameterDefinitionBranchProperty.java src/main/java/jenkins/branch/RateLimitBranchProperty.java src/main/java/jenkins/branch/SimpleViewBranchFilter.java src/main/resources/jenkins/branch/BranchEventCause/description.jelly src/main/resources/jenkins/branch/BranchEventCause/description.properties src/main/resources/jenkins/branch/BranchIndexingCause/description.jelly src/main/resources/jenkins/branch/BranchStatusColumn/column.jelly src/main/resources/jenkins/branch/DescriptionColumn/column.jelly src/main/resources/jenkins/branch/DescriptionColumn/columnHeader.jelly src/main/resources/jenkins/branch/LocalizedViewsTabBar/viewTabs.jelly src/main/resources/jenkins/branch/Messages.properties src/main/resources/jenkins/branch/OrganizationFolder/newInstanceDetail.jelly src/main/webapp/images/16x16/organization-folder.png src/main/webapp/images/24x24/organization-folder.png src/main/webapp/images/32x32/organization-folder.png src/main/webapp/images/48x48/organization-folder.png src/test/java/integration/BrandingTest.java src/test/java/integration/CategorizationTest.java src/test/java/integration/EnvironmentTest.java src/test/java/integration/EventsTest.java src/test/java/integration/ScmApiTest.java src/test/java/integration/harness/BasicBranchProjectFactory.java src/test/java/integration/harness/BasicBranchProperty.java src/test/java/integration/harness/BasicDummyStepBranchProperty.java src/test/java/integration/harness/BasicMultiBranchProject.java src/test/java/integration/harness/BasicMultiBranchProjectFactory.java src/test/java/integration/harness/BasicSCMSourceCriteria.java src/test/java/jenkins/branch/BranchCategoryFilterTest.java src/test/java/jenkins/branch/BuildRetentionBranchPropertyTest.java src/test/java/jenkins/branch/CustomOrganizationFolderDescriptorTest.java src/test/java/jenkins/branch/LocalizedViewsTabBarTest.java
[JIRA] (JENKINS-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title Jesse Glick updated JENKINS-40281 Jenkins / JENKINS-40281 No Badge shown, Exception build.badgeActions depending on KeepBuildForever Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39977) Support for bitbucket-branch-source-plugin
Title: Message Title
Torben Knerr commented on JENKINS-39977
Re: Support for bitbucket-branch-source-plugin
Mike Kobit thanks taking this on! I was also confused as I was simply using the "Bitbucket Branch Source" in a standard "WorkflowMultiBranchProject". It was only later that I realized there is also the "Teams" configuration via the "OrganizationFolder". Here is how I configured it for a Multibranch Pipeline for now:
multibranchPipelineJob("somePipeline") {
configure {
it / sources / data / 'jenkins.branch.BranchSource' / source(class: 'com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource') {
credentialsId('bitbucketUserPasswordAPICredentialsForCheckingBranches')
checkoutCredentialsId('bitbucketCredentialsForCloningAndPulling')
repoOwner("KEY")
repository("my-repo")
includes('master release/* feature/*')
excludes()
bitbucketServerUrl('https://my.bitbucket.com')
sshPort('7999')
}
}
// check every minute for scm changes as well as new / deleted branches
triggers {
periodic(1)
}
}
Do you plan to add DSL support for this as well?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title Jesse Glick commented on JENKINS-40281 Re: No Badge shown, Exception build.badgeActions depending on KeepBuildForever From quick code inspection, I believe this was the only such case in Jenkins core. And, the associated keepLog functionality had zero test coverage. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14591) Add the ability to choose which parameters build will be displayed
Title: Message Title Dan Alvizu commented on JENKINS-14591 Re: Add the ability to choose which parameters build will be displayed Fixed in 1.5.6 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-34722) Unbounded searches with BuildUtil.getDownstreamBuild
Title: Message Title Dan Alvizu commented on JENKINS-34722 Re: Unbounded searches with BuildUtil.getDownstreamBuild Fixed in 1.5.6 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title Jesse Glick started work on JENKINS-40281 Change By: Jesse Glick 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-40240) Provide descriptors for build wrappers
Title: Message Title Andrew Bayer commented on JENKINS-40240 Re: Provide descriptors for build wrappers PR up at https://github.com/jenkinsci/blueocean-pipeline-editor-plugin/pull/6 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40240) Provide descriptors for build wrappers
Title: Message Title Andrew Bayer updated JENKINS-40240 Jenkins / JENKINS-40240 Provide descriptors for build wrappers Change By: Andrew Bayer 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-40240) Provide descriptors for build wrappers
Title: Message Title Andrew Bayer started work on JENKINS-40240 Change By: Andrew Bayer 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-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-40281 No Badge shown, Exception build.badgeActions depending on KeepBuildForever Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-40281
No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Change By:
Jesse Glick
After Update to Jenkins 2.34 and 2.35 we see several exceptions "WARNING: Caught exception evaluating: build.badgeActions" (see below) in the log file. We could easily reproduce this in a fresh new setup without additional installed plugins by:* Setup a new Build-Job and activate "Discard old builds".* Execute this job.* Navigate to the build and activate "Keep this build forever"* Access the job site.** => Exception in log file (see below)** => Lock icon "KeepBuild" not shown. In case of promotions the icons also not appear.After deactivating "Keep this build forever" the exception does not appear and promotion icons/stars appear again.Exception: Dec 07, 2016 1 {code : 18:43 PM none}… hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: build.badgeActions in /job/test/. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) … at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)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$JexlExpression.evaluate(ExpressionFactory2.java:74)at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at
[JIRA] (JENKINS-40085) Builds kept forever no longer have an icon
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-40085 Builds kept forever no longer have an icon Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40128) Plugin Manager API inconsistencies, produces empty XML/JSON/Python
Title: Message Title Daniel Beck resolved as Not A Defect I still believe the API to be broken. /pluginManager/api/xml?depth=1 shows you what exists (at depth 1), and why '?tree=name' cannot possibly work. /pluginManager/api/xml?tree=plugins[shortName] works like a charm for me. In the future, please ask for help in #jenkins or on the jenkinsci-users mailing list. This is an issue tracker, and not as actively read as these other channels. And I still believe the other endpoints should not return 404s. Not how the API works, or has ever worked. Not every view has an API, as API is tied to model objects, which is the same for all the 'tabs'. /job/foo/ws/api doesn't exist either, nor does /job/foo/configure/api. Jenkins / JENKINS-40128 Plugin Manager API inconsistencies, produces empty XML/JSON/Python Change By: Daniel Beck Status: Reopened Resolved Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-40296) REGRESSION: Commit messages are not showing up in activities, branches and PR tables
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40296 Re: REGRESSION: Commit messages are not showing up in activities, branches and PR tables Code changed in jenkins User: Ivan Meredith Path: src/main/js/api/git.js src/test/js/multibranch/commitMessages.js src/test/resources/multibranch/commit_message/Jenkinsfile http://jenkins-ci.org/commit/blueocean-acceptance-test/23cd6a49afbb6bab9ee44e5f8c6ae24eee7a63eb Log: JENKINS-40296 Tests to cover changeset messages Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-34654) support copy file from image
Title: Message Title Jesse Glick updated JENKINS-34654 Jenkins / JENKINS-34654 support copy file from image Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40321) Job notification settings not respected in multibranch pipeline
Title: Message Title James Emerton created an issue Jenkins / JENKINS-40321 Job notification settings not respected in multibranch pipeline Issue Type: Bug Assignee: Unassigned Components: hipchat-plugin Created: 2016/Dec/08 10:29 PM Environment: Jenkins 2.19.3 (no slave nodes) Hipchat Plugin 2.0.0 Windows 7 Priority: Major Reporter: James Emerton I have created a multibranch pipeline job and configured global HipChat notification settings to send a message on build failure. No messages are being sent when these jobs fail. I also tried to set the hipchat notification in the Jenkinsfile using HipChatJobProperty, which failed to work as well. properties([[ $class: 'HipChatJobProperty', notifyFailure: true, notifyBackToNormal: true, ]]) Using hipchatSend() does work, and appears to use the globally configured credentials and room values.
[JIRA] (JENKINS-30577) Performance issues when loading a large amount of views via getViews()
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30577 Performance issues when loading a large amount of views via getViews() Change By: SCM/JIRA link daemon 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-30577) Performance issues when loading a large amount of views via getViews()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30577 Re: Performance issues when loading a large amount of views via getViews() Code changed in jenkins User: Dan Alvizu Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java http://jenkins-ci.org/commit/build-pipeline-plugin/35e105fad810662edad3cf45042427339943758d Log: Merge pull request #88 from jpederzolli/master [FIXED JENKINS-30577] Performance fix when determining view permissions Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/1769711009d3...35e105fad810 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30577) Performance issues when loading a large amount of views via getViews()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30577 Re: Performance issues when loading a large amount of views via getViews() Code changed in jenkins User: John Pederzolli Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java http://jenkins-ci.org/commit/build-pipeline-plugin/e33ef9c0ee7fca2d0762149686ddedd35ab48cfe Log: JENKINS-30577 : performance enhancement when determining view permissions Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30577) Performance issues when loading a large amount of views via getViews()
Title: Message Title Dan Alvizu assigned an issue to Dan Alvizu Jenkins / JENKINS-30577 Performance issues when loading a large amount of views via getViews() Change By: Dan Alvizu Assignee: jpederzolli Dan Alvizu Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-38438) image.inside { ... } does not create full configured user account
Title: Message Title
Jesse Glick commented on JENKINS-38438
Re: image.inside { ... } does not create full configured user account
Seems related to JENKINS-39748?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-39977) Support for bitbucket-branch-source-plugin
Title: Message Title
Mike Kobit edited a comment on JENKINS-39977
Re: Support for bitbucket-branch-source-plugin
[~daspilker] - I've started trying to tackle this based on what I have seen in the UI and how some of the other code looks. I'm hoping to open a PR in the next couple days as I get some time to write it up.h3. Proposed DSLHow do you feel about this sort of DSL:{code:none}organizationFolderJob('orgFolder') { description('This contains branch source jobs for Bitbucket and GitHub') displayName('Organization Folder') branchAutoTriggerPattern('master|develop|feature/*') triggers {periodicIfNotOtherwiseTriggered(TWELVE_HOURS) } orphanedItemStrategy {discardOldItems { daysToKeep(1) numToKeep(10)} } organizations {bitbucket { repoOwner('KEY') scanCredentialsId('bitbucketScanCredentials') repositoryPattern('*') autoRegisterWebhooks() checkoutCredentialsId('bitbucketSshCheckoutCredentials') bitbucketServerUrl('https://bitbucket.corp.com') sshPort(7990)} }}{code}h3. Out-of-scope* Pipeline libraries configuration * (possibly) GitHub SCM Navigator configuration
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-39977) Support for bitbucket-branch-source-plugin
Title: Message Title
Mike Kobit commented on JENKINS-39977
Re: Support for bitbucket-branch-source-plugin
Daniel Spilker - I've started trying to tackle this based on what I have seen in the UI and how some of the other code looks. I'm hoping to open a PR in the next couple days as I get some time to write it up. Proposed DSL How do you feel about this sort of DSL:
organizationFolderJob('orgFolder') {
description('This contains branch source jobs for Bitbucket and GitHub')
displayName('Organization Folder')
branchAutoTriggerPattern('master|develop|feature/*')
triggers {
periodicIfNotOtherwiseTriggered(TWELVE_HOURS)
}
orphanedItemStrategy {
discardOldItems {
daysToKeep(1)
numToKeep(10)
}
}
organizations {
bitbucket {
repoOwner('KEY')
scanCredentialsId('bitbucketScanCredentials')
repositoryPattern('*')
autoRegisterWebhooks()
checkoutCredentialsId('bitbucketSshCheckoutCredentials')
bitbucketServerUrl('https://bitbucket.corp.com')
sshPort(7990)
}
}
}
Out-of-scope
Pipeline libraries configuration
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You
[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 *Scenario*Commit history looks like history looks like:* r2 - commit that breaks* r1 - commit that worksIf commit r1 finishes later than r2 then the dashboard shows a successful card instead of a failure.*Original* I'm using subversion and pipelinesI favourite a particular pipeline XI make a pipeline X-passing commit and then a failing pipeline X commitThe failing commit fails early in the pipeline i.e. unit testsThe earlier good commit continues through the pipeline and finishes successfully and at a time after the end of the failing commit's pipelineThe blue-ocean beta dashboard view shows me a green tick box rather than a red angry boxThis is not what I want, I want to know that my last commit broke the world. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed
[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 *Scenario*Commit history looks like:* r2 - commit that breaks* r1 - commit that worksIf commit r1 finishes later than r2 then the dashboard shows a successful card for r1 instead of a the lasted failure for r2 .*Original*I'm using subversion and pipelinesI favourite a particular pipeline XI make a pipeline X-passing commit and then a failing pipeline X commitThe failing commit fails early in the pipeline i.e. unit testsThe earlier good commit continues through the pipeline and finishes successfully and at a time after the end of the failing commit's pipelineThe blue-ocean beta dashboard view shows me a green tick box rather than a red angry boxThis is not what I want, I want to know that my last commit broke the world. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[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 *Scenario*Commit history looks like history looks like :* r2 - commit that breaks* r1 - commit that worksIf commit r1 finishes later than r2 then the dashboard shows a successful card instead of a failure.*Original*I'm using subversion and pipelinesI favourite a particular pipeline XI make a pipeline X-passing commit and then a failing pipeline X commitThe failing commit fails early in the pipeline i.e. unit testsThe earlier good commit continues through the pipeline and finishes successfully and at a time after the end of the failing commit's pipelineThe blue-ocean beta dashboard view shows me a green tick box rather than a red angry boxThis is not what I want, I want to know that my last commit broke the world. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-40068) Dashboard view masks later commit failure with earlier commit success
Title: Message Title James Dumay commented on JENKINS-40068 Re: Dashboard view masks later commit failure with earlier commit success matt lane 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-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Mark Waite commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Not resolved. The pull request is still open. You could build your own copy of the plugin which includes the master branch and the pull request. That would give you the fix and would provide an additional tester to declare if the change is working well for you. Proxy configuration changes are especially scary because they risk breaking users very badly. They are difficult to test due to the many different forms of proxying. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39748) Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39748 Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing Change By: Jesse Glick Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39748) Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39748 Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing Change By: Jesse Glick Issue Type: Bug New 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-39748) Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing
Title: Message Title Jesse Glick updated JENKINS-39748 Jenkins / JENKINS-39748 Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39748) Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing
Title: Message Title Jesse Glick started work on JENKINS-39748 Change By: Jesse Glick 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-39748) Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing
Title: Message Title Jesse Glick assigned an issue to James Hogarth Jenkins / JENKINS-39748 Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing Change By: Jesse Glick Assignee: James Hogarth Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40226) Dockerfile build failures do not trigger failure post section
Title: Message Title Andrew Bayer updated JENKINS-40226 Jenkins / JENKINS-40226 Dockerfile build failures do not trigger failure post section Change By: Andrew Bayer 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-40226) Dockerfile build failures do not trigger failure post section
Title: Message Title Andrew Bayer commented on JENKINS-40226 Re: Dockerfile build failures do not trigger failure post section PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/64 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40013) Unable to set and use global groovy functions
Title: Message Title Andrew Bayer commented on JENKINS-40013 Re: Unable to set and use global groovy functions Ah. Hrm. Let me see what I can figure out. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40188) Unable to use build step with boolean parameterized parameter
Title: Message Title Andrew Bayer commented on JENKINS-40188 Re: Unable to use build step with boolean parameterized parameter My first thought is to just try value: env.SIMUL - in relatively recent versions of the various Pipeline plugins, you can actually just use value: SIMUL, for that matter. Let me know if that helps? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Pratith Kanagaraj commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Was this resolved? Because I am still facing the 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-14591) Add the ability to choose which parameters build will be displayed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-14591 Re: Add the ability to choose which parameters build will be displayed Code changed in jenkins User: Dan Alvizu Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/DownstreamProjectGridBuilder.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/ProjectForm.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildVariablesHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/FilteredVariablesHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/NullColumnHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/ParametersActionHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtension.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtensionDescriptor.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleColumnHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleRowHeader.java src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/AbstractNameValueHeader/projectCardTemplate.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildVariablesHeader/config.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/FilteredVariablesHeader/config.jelly src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/ProjectFormTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/FilteredVariablesHeaderTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/1769711009d31b3400496c4d802329d12e281a8b Log: Merge pull request #106 from jenkinsci/JENKINS-14591 [FIXED JENKINS-14591] add build card to filter out parameters Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/2a279e70a8fd...1769711009d3 Add Comment
[JIRA] (JENKINS-39746) Allow running exec directly from a Container object
Title: Message Title Jesse Glick started work on JENKINS-39746 Change By: Jesse Glick 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-39746) Allow running exec directly from a Container object
Title: Message Title Jesse Glick updated JENKINS-39746 Jenkins / JENKINS-39746 Allow running exec directly from a Container object Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39746) Allow running exec directly from a Container object
Title: Message Title Jesse Glick assigned an issue to James Hogarth Jenkins / JENKINS-39746 Allow running exec directly from a Container object Change By: Jesse Glick Assignee: James Hogarth Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39372) Pipeline editor to use Pipeline-model-definition json model
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-39372 Pipeline editor to use Pipeline-model-definition json model Change By: Keith Zantow Assignee: Josh McDonald Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-33632) docker.inside broken with old client versions
Title: Message Title Jesse Glick resolved as Won't Fix Warning added with https://github.com/jenkinsci/docker-workflow-plugin/pull/80, thanks! Jenkins / JENKINS-33632 docker.inside broken with old client versions Change By: Jesse Glick Status: Reopened Resolved Resolution: Won't 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
[JIRA] (JENKINS-33632) docker.inside broken with old client versions
Title: Message Title Jesse Glick assigned an issue to Pierre Beitz Jenkins / JENKINS-33632 docker.inside broken with old client versions Change By: Jesse Glick Assignee: Jesse Glick Pierre Beitz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-33632) docker.inside broken with old client versions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33632 Re: docker.inside broken with old client versions Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java http://jenkins-ci.org/commit/docker-workflow-plugin/98d2af626cca98f05d358c11431c9f0b5600809b Log: Merge pull request #80 from PierreBtz/dev JENKINS-33632 Add a warning if the detected docker version is less than v1.8 Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/eb142f64eba3...98d2af626cca Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40320) No page found 'config.jelly' for class hudson.model.User
Title: Message Title Neil Hunt created an issue Jenkins / JENKINS-40320 No page found 'config.jelly' for class hudson.model.User Issue Type: Bug Assignee: Nicolas De Loof Attachments: jenkins user edit Oops.PNG Components: docker Created: 2016/Dec/08 9:36 PM Priority: Minor Reporter: Neil Hunt Getting this error when I hit the configure for a particular user https://JENKINS_URL/user/USER/configure javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/plugins/favorite/WEB-INF/lib/favorite.jar!/hudson/plugins/favorite/user/FavoriteUserProperty/config.jelly:4:66: No page found '/hudson/plugins/favorite/assets/css.jelly' for class hudson.model.User Running on Jenkins Docker using 2.35 (FROM jenkinsci/jenkins). Add Comment
[JIRA] (JENKINS-38835) 'make -C demo run' hard to do on OSX
Title: Message Title Jesse Glick assigned an issue to Carlos Sanchez Jenkins / JENKINS-38835 'make -C demo run' hard to do on OSX Change By: Jesse Glick Assignee: Richard Lee Carlos Sanchez Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-38835) 'make -C demo run' hard to do on OSX
Title: Message Title Jesse Glick updated JENKINS-38835 Jenkins / JENKINS-38835 'make -C demo run' hard to do on OSX Change By: Jesse Glick 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-38835) 'make -C demo run' hard to do on OSX
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38835 Re: 'make -C demo run' hard to do on OSX Code changed in jenkins User: Jesse Glick Path: demo/Dockerfile demo/Makefile demo/README.md http://jenkins-ci.org/commit/docker-workflow-plugin/80641e81402221ee53fe58bd2da14b81f47f96da Log: JENKINS-38835 Merged #83: demo fixups for OS X. Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/46432bbe36af...80641e814022 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40128) Plugin Manager API inconsistencies, produces empty XML/JSON/Python
Title: Message Title
Jeremy Loy updated an issue
Jenkins / JENKINS-40128
Plugin Manager API inconsistencies, produces empty XML/JSON/Python
Change By:
Jeremy Loy
Comment:
Daniel, how exactly do tree and depth parameters solve the issue? Perhaps I'm using it incorrectly./pluginManager/api/xml?tree=plugins[name]{0,1}This is the url I am using. It is still empty, although now of size one. I still believe the API to be broken. And I still believe the other endpoints should not return 404s.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-40128) Plugin Manager API inconsistencies, produces empty XML/JSON/Python
Title: Message Title
Jeremy Loy reopened an issue
Daniel, how exactly do tree and depth parameters solve the issue? Perhaps I'm using it incorrectly. /pluginManager/api/xml?tree=plugins[name] {0,1} This is the url I am using. It is still empty, although now of size one. I still believe the API to be broken. And I still believe the other endpoints should not return 404s. Again, perhaps I'm using it wrong. I will plainly admit that if so.
Jenkins / JENKINS-40128
Plugin Manager API inconsistencies, produces empty XML/JSON/Python
Change By:
Jeremy Loy
Resolution:
Not A Defect
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title Jesse Glick updated JENKINS-34276 Jenkins / JENKINS-34276 docker.inside within a withRegistry block seems to use image.id instead of image.imageName() Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14591) Add the ability to choose which parameters build will be displayed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-14591 Re: Add the ability to choose which parameters build will be displayed Code changed in jenkins User: Dan Alvizu Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/DownstreamProjectGridBuilder.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/ProjectForm.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildVariablesHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/FilteredVariablesHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/NullColumnHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/ParametersActionHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtension.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/PipelineHeaderExtensionDescriptor.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleColumnHeader.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/SimpleRowHeader.java src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/AbstractNameValueHeader/projectCardTemplate.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/BuildVariablesHeader/config.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/FilteredVariablesHeader/config.jelly src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/ProjectFormTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/extension/FilteredVariablesHeaderTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/d0221ecc8f3b8d84e2ac20d39e2595e23012f3a8 Log: [FIXED JENKINS-14591] add build card to filter out parameters Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-14591) Add the ability to choose which parameters build will be displayed
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-14591 Add the ability to choose which parameters build will be displayed Change By: SCM/JIRA link daemon 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.
