[JIRA] [gerrit-trigger-plugin] (JENKINS-33933) Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Title: Message Title
Björn Pedersen created an issue
Jenkins / JENKINS-33933
Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Issue Type:
Bug
Assignee:
rsandell
Components:
gerrit-trigger-plugin
Created:
2016/Mar/31 12:41 PM
Environment:
jenkins 1.655/ jenkins 2.0-alpha/beta gerrit-trigger-plugin 2.18.3+, also with f1a6a39 applied
Priority:
Critical
Reporter:
Björn Pedersen
In my test install I can not trigger jobs anymore: I always get a null-pointer exception in BuildChooser (see log below).
{{Manually triggered by user pedersen for Gerrit: https:///review/3200 [lockable-resources] acquired lock on [Test1] [EnvInject] - Loading node environment variables. Baue auf Master in Arbeitsbereich /usr/local/jenkins/jobs/ResiSingleCounterMulti/workspace > /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url ssh://:29418/ # timeout=10 Fetching upstream changes from ssh://:29418/ > /usr/local/bin/git --version # timeout=10 using GIT_SSH to set credentials > /usr/local/bin/git fetch --tags --progress ssh://:29418/ refs/changes/00/3200/2 > /usr/local/bin/git rev-parse efa17ba464d2392714029effc904c9fb8612e255^
[JIRA] [core] (JENKINS-33924) Show me which version of Jetty is bundled in Winstone-Jetty in /about
Title: Message Title Félix Belzunce Arcos commented on JENKINS-33924 Re: Show me which version of Jetty is bundled in Winstone-Jetty in /about I tried to fix it using https://github.com/jenkinsci/jenkins/blob/master/licenseCompleter.groovy - but it looks like it only works for direct dependencies. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33924) Show me which version of Jetty is bundled in Winstone-Jetty in /about
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-33924 Show me which version of Jetty is bundled in Winstone-Jetty in /about Change By: Félix Belzunce Arcos Currently the container running Jenkins Jetty is not exposed bundled in /about.It winstone so it should be exposed there. in /about Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [description-setter-plugin] (JENKINS-30195) Option for appending an unique descriptions only
Title: Message Title Pavel Janoušek commented on JENKINS-30195 Re: Option for appending an unique descriptions only Help messages fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33597) White Screen of Death (in the web UI) when updating to Jenkins 1.653
Title: Message Title Brian Wilson resolved as Fixed Confirmed this has been resolved in the 1.655 release. I tested this on a Linux RHEL5 platform which had previously shown the WSoD issue. With the upgrade to 1.655, the system returned and displayed the UI properly after a restart from the UI URL line. I tried two restarts just to make sure this continued to work and observed no UI issues. Jenkins / JENKINS-33597 White Screen of Death (in the web UI) when updating to Jenkins 1.653 Change By: Brian Wilson Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33597) White Screen of Death (in the web UI) when updating to Jenkins 1.653
Title: Message Title Brian Wilson edited a comment on JENKINS-33597 Re: White Screen of Death (in the web UI) when updating to Jenkins 1.653 Confirmed. The WSoD did not occur on our test Linux platform for when we installed 1.655 release and did a restart on the URL line . Thank you! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-organization-folder-plugin] (JENKINS-33797) Github Organization folder creation causes exception with space in job name
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-33797 Github Organization folder creation causes exception with space in job name Change By: Manuel Jesús Recena Soto Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-organization-folder-plugin] (JENKINS-33797) Github Organization folder creation causes exception with space in job name
Title: Message Title Manuel Jesús Recena Soto resolved as Fixed Jenkins / JENKINS-33797 Github Organization folder creation causes exception with space in job name Change By: Manuel Jesús Recena Soto Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33597) White Screen of Death (in the web UI) when updating to Jenkins 1.653
Title: Message Title Brian Wilson commented on JENKINS-33597 Re: White Screen of Death (in the web UI) when updating to Jenkins 1.653 Confirmed. The WSoD did not occur on our test Linux platform for 1.655 release. Thank you! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-33932) Plugin does no blocking when job is generated with job DSL groovy script
Title: Message Title nif y created an issue Jenkins / JENKINS-33932 Plugin does no blocking when job is generated with job DSL groovy script Issue Type: Bug Assignee: Unassigned Attachments: BuildExecutorStatus.PNG, example2_config.PNG, main.groovy Components: build-blocker-plugin Created: 2016/Mar/31 11:51 AM Environment: Windows 7 64 bit Jenkins ver. 1.655 Build Blocker Plugin 1.7.3 Job DSL 1.44 Priority: Major Reporter: nif y To reproduce the error, use the attached main.groovy script in a seed job with the Job DSL process to generate two jobs (example1, example2). Both jobs could be started on a windows environment and produce a 10 sec. sleep. example2 is configured to be blocked when example1 is running. But both jobs can run in parallel as one can see in the attached BuildExecutorStatus.PNG The config.xml of example2 has a entry for the plugin: ... true example1 GLOBAL DISABLED ...
[JIRA] [core] (JENKINS-33924) Show me which version of Jetty is bundled in Winstone-Jetty in /about
Title: Message Title Félix Belzunce Arcos commented on JENKINS-33924 Re: Show me which version of Jetty is bundled in Winstone-Jetty in /about issue title was rebuilt. Jetty is bundled in winstone so it should be exposed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33931) exceptions on pluginManager with no plugins
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-33931
exceptions on pluginManager with no plugins
Change By:
James Nord
start jenkins2.0 on a clean installclose the wizzard so no plugins are installed.loginrestartlogin againgo to plugin manangerclick on Available tab wait for the page to start loading click con Installed tabWatch the exceptions spew in the logs...{noformat}Mar 31, 2016 12:41:50 PM org.eclipse.jetty.util.log.JavaUtilLog warnWARNING: /pluginManager/availablejava.io.IOException: failed to deflate: error=-5 avail_out=198at com.jcraft.jzlib.DeflaterOutputStream.deflate(DeflaterOutputStream.java:140)at com.jcraft.jzlib.DeflaterOutputStream.finish(DeflaterOutputStream.java:111)at com.jcraft.jzlib.DeflaterOutputStream.close(DeflaterOutputStream.java:117)at org.kohsuke.stapler.compression.FilterServletOutputStream.close(FilterServletOutputStream.java:36)at org.kohsuke.stapler.compression.CompressionServletResponse.close(CompressionServletResponse.java:67)at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:63)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:553)at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)at org.eclipse.jetty.server.Server.handle(Server.java:499)at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)Mar 31, 2016 12:41:51 PM org.eclipse.jetty.util.log.JavaUtilLog warnWARNING: /pluginManager/availablejava.io.IOException: failed to deflate: error=-5 avail_out=198at
[JIRA] [core] (JENKINS-33924) Show me which version of Jetty is bundled in Winstone-Jetty in /about
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-33924 Show me which version of Jetty is bundled in Winstone-Jetty in /about Change By: Félix Belzunce Arcos Summary: Expose container Show me which version of Jetty is running Jenkins bundled in Winstone-Jetty in /about Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33931) exceptions on pluginManager with no plugins
Title: Message Title James Nord created an issue Jenkins / JENKINS-33931 exceptions on pluginManager with no plugins Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Mar/31 11:46 AM Environment: 2.0-beta-1 windows x64 java8 Labels: 2.0 2.0-beta Priority: Minor Reporter: James Nord start jenkins2.0 on a clean install close the wizzard so no plugins are installed. login restart login again go to plugin mananger click on Available tab click con Installed tab Watch the exceptions spew in the logs... Mar 31, 2016 12:41:50 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: /pluginManager/available java.io.IOException: failed to deflate: error=-5 avail_out=198 at com.jcraft.jzlib.DeflaterOutputStream.deflate(DeflaterOutputStream.java:140) at
[JIRA] [core] (JENKINS-33930) new tabbed job config page broken accessibility
Title: Message Title James Nord created an issue Jenkins / JENKINS-33930 new tabbed job config page broken accessibility Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Mar/31 11:40 AM Labels: ui 2.0 2.0-beta Priority: Critical Reporter: James Nord you can no longer use the keyboard to navigate on the restyled "FreeStyle" job configuration page. There is no way to change the tabs which would confuse a user (they are not tabs - but look like tabs? - when an item gets focus via a tab key the "tab" thing should change highlight as it does if you just scroll The tabbing order of the items and help is completely out of whack. The red X on a build step never seems to receive focus, Add
[JIRA] [amazon-ecs-plugin] (JENKINS-33928) Communication to AWS API should support HTTP proxies
Title: Message Title Jan Röhrich commented on JENKINS-33928 Re: Communication to AWS API should support HTTP proxies I created a pull request for this: https://github.com/jenkinsci/amazon-ecs-plugin/pull/18 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33929) newJob "New Item name" textbox gets focus on IE
Title: Message Title James Nord created an issue Jenkins / JENKINS-33929 newJob "New Item name" textbox gets focus on IE Issue Type: Bug Assignee: Unassigned Attachments: Untitled.png Components: core Created: 2016/Mar/31 11:31 AM Labels: 2.0 2.0-beta ui Priority: Minor Reporter: James Nord In IE (11.162) when you go to the newJob page the "new item name" textbox gets focus. This is handy but by giving it focus it removes the "New Item name..." text so you are clueless as to what you are supposed to do here. On chrome, Edge and Firefox the text only disappears when you start typing not when you get focus.
[JIRA] [maven-plugin] (JENKINS-28629) Fix Apache Maven 3.3 support
Title: Message Title Tomer Cohen commented on JENKINS-28629 Re: Fix Apache Maven 3.3 support I opened pull requests that should fix at least the toolchains problem (as this is what is essentially blocking me from upgrading Jenkins to Maven 3.3) maven-interceptors: https://github.com/jenkinsci/maven-interceptors/pull/9 maven-plugin: https://github.com/jenkinsci/maven-plugin/pull/63 I tested it on my setup and it seems to work as intended. Would appreciate if someone can take a look. Thanks a bunch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [amazon-ecs-plugin] (JENKINS-33928) Communication to AWS API should support HTTP proxies
Title: Message Title Jan Röhrich created an issue Jenkins / JENKINS-33928 Communication to AWS API should support HTTP proxies Issue Type: New Feature Assignee: Nicolas De Loof Components: amazon-ecs-plugin Created: 2016/Mar/31 11:27 AM Priority: Minor Reporter: Jan Röhrich The connection to AWS' API doesn't support proxies at the moment. Support for using the HTTP proxy configured under the plugins extras page should be integrated to allow Jenkins servers behind a firewall to use AWS resources. Add Comment
[JIRA] [core] (JENKINS-33927) newJob page borders not aligned.
Title: Message Title James Nord created an issue Jenkins / JENKINS-33927 newJob page borders not aligned. Issue Type: Bug Assignee: Unassigned Attachments: Untitled.png Components: core Created: 2016/Mar/31 11:24 AM Environment: windows 10 x64 chrome Labels: 2.0 2.0-beta ui Priority: Minor Reporter: James Nord the newJob Page borders are not aligned on some screensizes Seems like someone is dividing and rounding up and other dividing and rounding down. if you resize the windows the border flips between being in line and not being inline. pushing pixels
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33110) Log details are not shown
Title: Message Title Daniel Beck commented on JENKINS-33110 Re: Log details are not shown Sam Van Oort Are you still working on this? If not: Patrick Wolf WDYT? Looks like a pretty popular issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33924) Expose container which is running Jenkins in /about
Title: Message Title Daniel Beck commented on JENKINS-33924 Re: Expose container which is running Jenkins in /about Why? So far, that only shows license information? What makes you think configuration details belong there? It doesn't show the Java version either. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33925) Test framework for Jenkinsfile
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-33925
Test framework for Jenkinsfile
Change By:
Jesse Glick
It would be desirable to have a standard mechanism for testing Pipeline scripts without running them on a production server. There are two competing suggestions:h3. Mock frameworkInspired by Job DSL ([example|https://github.com/sheehan/job-dsl-gradle-example/blob/e240056da6691bf0a2fdc99e5aab33bc49e42b2f/src/test/groovy/com/dslexample/GrailsCiJobBuilderSpec.groovy#L34-L49]).We could set up a {{GroovyShell}} in which step functions and global variables were predefined as mocks (in a fashion similar to Powermock, but easier in Groovy given its dynamic nature), and stub out the expected return value / exception for each, with some standard predefinitions such as for {{currentBuild}}.Ideally the shell would be CPS-transformed, with the program state serialized and then reloaded between every continuation (though this might involve a lot of code duplication with {{workflow-cps}}).Should be easy to pass it through the Groovy sandbox (if requested), though the live {{Whitelist.all}} from Jenkins would be unavailable, so we would be limited to known static whitelists, the {{@Whitelisted}} annotation, and perhaps some custom additions.Quick and flexible, but low fidelity to real behavior.h3. {{JenkinsRule}}-styleUse an embedded Jenkins server, as per {{JenkinsRule}} in {{jenkins-test-harness}}, and actually create a {{WorkflowJob}} with the specified definition. Can use for example {{mock-slave}} to create nodes.Need to have a "dry-run" flag so that attempts to do things like deploy artifacts or send email do not really take action. This could perhaps be a general API in Jenkins core, as it would be useful also for test instances (shadows of production servers), {{acceptance-test-harness}}, etc.Slower to run (seconds per test case rather than milliseconds), and trickier to set up, but much more realistic coverage. The tests for Pipeline (and Pipeline steps) themselves use this technique.
Add Comment
[JIRA] [workflow-plugin] (JENKINS-33925) Test framework for Jenkinsfile
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-33925 Test framework for Jenkinsfile Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Mar/31 11:16 AM Labels: testing Priority: Major Reporter: Jesse Glick It would be desirable to have a standard mechanism for testing Pipeline scripts without running them on a production server. There are two competing suggestions: Mock framework Inspired by Job DSL (example). We could set up a GroovyShell in which step functions and global variables were predefined as mocks (in a fashion similar to Powermock, but easier in Groovy given its dynamic nature), and stub out the expected return value / exception for each, with some standard predefinitions such as for currentBuild. Ideally the shell would be CPS-transformed, with the program state serialized and then reloaded between every continuation (though this might involve a lot of code duplication with workflow-cps). Should be easy to pass it through the Groovy sandbox (if requested), though the live Whitelist.all from Jenkins would be unavailable, so we would be limited to known static whitelists, the @Whitelisted
[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly
Title: Message Title James Nord created an issue Jenkins / JENKINS-33926 Jenkins no longer appears to shutdown correctly Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Mar/31 11:16 AM Environment: Windows 10 x64 java version "1.8.0_71" 2.0-beta-1 Labels: 2.0-beta regression 2.0 Priority: Minor Reporter: James Nord Start Jenkins with java -jar jenkins-2.0-beta-1.jar on windows In the console hit ctrl+c expected behaviour Jenkins does a graceful shutdown and this is appropriately logged actual behaviour it appears as though Jenkins is brutally terminated and does not do a graceful shutdown. There are no logs to indicate a graceful termination In 1.x I see the following logs Mar 31, 2016 12:02:39 PM winstone.Logger logInternal
[JIRA] [core] (JENKINS-33888) Jenkins 2.0 - create first admin - 'skip' button confusing
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-33888 Jenkins 2.0 - create first admin - 'skip' button confusing Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33924) Expose container which is running Jenkins in /about
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-33924 Expose container which is running Jenkins in /about Issue Type: Bug Assignee: Félix Belzunce Arcos Components: core Created: 2016/Mar/31 11:08 AM Priority: Minor Reporter: Félix Belzunce Arcos Currently the container running Jenkins is not exposed in /about. It should be exposed there. Add Comment This message was sent
[JIRA] [branch-api-plugin] (JENKINS-33808) Prove that richer Create Item API works by implementing for GH Org folders.
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-33808 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-33923) Credentials listbox is always empty
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-33923 Credentials listbox is always empty Change By: Antonio Muñiz Summary: Credentials listobox listbox is always empty Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-33923) Credentials listobox is always empty
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-33923 Credentials listobox is always empty Issue Type: Bug Assignee: Unassigned Components: ssh-agent-plugin Created: 2016/Mar/31 10:27 AM Environment: Jenkins 1.642.3 SSH Agent 1.10 Priority: Critical Reporter: Antonio Muñiz Credentials listbox is always empty, even after defining a new credential using the inline add button. Checked for both Freestyle and Pipeline snippet generator. Add Comment
[JIRA] [instant-messaging-plugin] (JENKINS-33922) Pipeline support for IRC Notifier
Title: Message Title Matthias Viehweger updated an issue Jenkins / JENKINS-33922 Pipeline support for IRC Notifier Change By: Matthias Viehweger Summary: Please add Pipeline support for jenkins pipeline plugin to ircbot IRC Notifier Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-33922) Please add support for jenkins pipeline plugin to ircbot
Title: Message Title Matthias Viehweger created an issue Jenkins / JENKINS-33922 Please add support for jenkins pipeline plugin to ircbot Issue Type: Improvement Assignee: kutzi Components: instant-messaging-plugin, ircbot-plugin, workflow-plugin Created: 2016/Mar/31 9:56 AM Priority: Major Reporter: Matthias Viehweger I an unsure where the extension needs to be made. I hope it is enough to add support between pipeline and instant-messaging. Since we are heavily IRC-driven, support for IRC notifications of build results is very important in adopting the pipeline for all jobs. Add Comment
[JIRA] [android-lint-plugin] (JENKINS-33075) Android lint plugin fails to run and hangs indefinitely on a Workflow script
Title: Message Title Luca Vitucci edited a comment on JENKINS-33075 Re: Android lint plugin fails to run and hangs indefinitely on a Workflow script Correct me if I'm wrong but I think this might be related to JENKINS-33311Version of LintPublisher that supports Pipeline is not yet released, even if source code is there. In this case you might try building the plugin using *mvn install* from sources. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33467 Re: CauseAction.causes can become huge Code changed in jenkins User: Robert Sandell Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/f1a6a398ba1cf1f1f1ce1fb48e84a437ec3fb3bb Log: Merge pull request #278 from jenkinsci/ JENKINS-33467 Don't crash because JENKINS-33467 has changed expected behaviour Compare: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/b7ab5892c183...f1a6a398ba1c Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter-plugin] (JENKINS-33921) Extended choice parameter not using defaults on timed builds
Title: Message Title Dave Taddei created an issue Jenkins / JENKINS-33921 Extended choice parameter not using defaults on timed builds Issue Type: Bug Assignee: vimil Components: extended-choice-parameter-plugin Created: 2016/Mar/31 9:18 AM Environment: Jenkins 1.655 Priority: Blocker Reporter: Dave Taddei The extended choice parameter plugin (versions 0.59, 0.61) are not populating variables with default values on timed builds. But they do populate parameter variables for on demand builds. Reverting back to 0.56 works around this issue. The expected behaviour is that when the timer goes off the build is initiated with the default parameter values. Add Comment
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Geoffroy Jabouley commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy What was at the beginning a simple patch supposed to fix a regression introduced in march 2015 (it's been a year now!) still cannot be mainlined because someone has decided instead to include it in a much wider story/task of implementing JNLP3 support. Why not keeping the scope of this fix simple? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-lint-plugin] (JENKINS-33075) Android lint plugin fails to run and hangs indefinitely on a Workflow script
Title: Message Title Luca Vitucci commented on JENKINS-33075 Re: Android lint plugin fails to run and hangs indefinitely on a Workflow script Correct me if I'm wrong but I think this might be related to JENKINS-33311 Version of LintPublisher that supports Pipeline is not yet released, even if source code is there. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Matt Clark commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Mark Waite I've put together a pull request for a change that makes sure the http_proxy and https_proxy values aren't already set before setting them from within git client (like if they are set at the node level). So no work for you to do there. Unfortunately the test framework is doing my head in (my fault I am sure). Any pointers on how to implement some unit tests or at least could you let me know what is a recent one that I should look at first to get my head around them. I was looking at PushTest and PushSimpleTest, being the most recently worked on, are they the best to be starting with? I couldn't see anything specifically around the environmental variables... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-cifs-plugin] (JENKINS-16739) Can't strip "**/"
Title: Message Title Giacomo Boccardo commented on JENKINS-16739 Re: Can't strip "**/" If it's not an issue, what's the proper way to handle it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: Manuel Recena Path: .gitignore src/main/java/hudson/model/ExternalJob.java src/main/resources/hudson/model/ExternalJob/newJobDetail.jelly src/main/resources/hudson/model/ExternalJob/newJobDetail.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_da.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_de.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_es.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_fr.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_it.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_ja.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_ko.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_nb_NO.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_nl.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_pl.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_pt_BR.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_ru.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_sv_SE.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_tr.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_zh_CN.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_zh_TW.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_da.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_es.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_fr.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_it.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_ko.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_nb_NO.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_pl.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_pt_BR.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_ru.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_sv_SE.properties src/main/webapp/images/48x48/externaljob.png http://jenkins-ci.org/commit/external-monitor-job-plugin/d1c101136c0f87926b5e97c90dd2623e988ddbb1 Log: Merge pull request #9 from recena/ JENKINS-31162 Support for Item categorization in Jenkins 2 Compare: https://github.com/jenkinsci/external-monitor-job-plugin/compare/c1725b597003...d1c101136c0f Add Comment
[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: recena Path: .gitignore src/main/java/hudson/model/ExternalJob.java src/main/resources/hudson/model/ExternalJob/newJobDetail.jelly src/main/resources/hudson/model/ExternalJob/newJobDetail.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_da.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_de.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_es.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_fr.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_it.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_ja.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_ko.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_nb_NO.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_nl.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_pl.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_pt_BR.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_ru.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_sv_SE.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_tr.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_zh_CN.properties src/main/resources/hudson/model/ExternalJob/newJobDetail_zh_TW.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_da.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_es.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_fr.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_it.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_ko.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_nb_NO.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_pl.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_pt_BR.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_ru.properties src/main/resources/org/jenkinsci/plugins/externalmonitorjob/Messages_sv_SE.properties src/main/webapp/images/48x48/externaljob.png http://jenkins-ci.org/commit/external-monitor-job-plugin/295c7ef4678f1d6c592405bf87f1c8cc43d53521 Log: JENKINS-31162 Support for Item categorization in Jenkins 2 Add Comment
[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: recena Path: src/main/java/hudson/model/ExternalJob.java http://jenkins-ci.org/commit/external-monitor-job-plugin/501279b707d314e0b8e6d3908b27c07e63daa830 Log: JENKINS-31162 Using Jenkins.RESOURCE_PATH for getIconFilePathPattern() Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: recena Path: src/main/java/hudson/model/ExternalJob.java http://jenkins-ci.org/commit/external-monitor-job-plugin/273a4108efa86b4cf5523274bfc15418eeea6a7c Log: JENKINS-31162 No forced the usage of Jenkins.RESOURCE_PATH Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: recena Path: src/main/resources/hudson/model/ExternalJob/newJobDetail.jelly http://jenkins-ci.org/commit/external-monitor-job-plugin/58573c893ee4115ec0e04c3d402e1191d23be34e Log: JENKINS-31162 Prevent inappropriate escaping Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-33730) ATH needs to be made to work with 2.0
Title: Message Title Oliver Gondža commented on JENKINS-33730 Re: ATH needs to be made to work with 2.0 Tom FENNELLY, working on tools config page extraction support ... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33573) Getting Started and Job configuration views should not use two different loading animations
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-33573 Getting Started and Job configuration views should not use two different loading animations Change By: Daniel Beck Labels: 2.0 2.0-planned Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33535) It would be nice to show the Jenkins version during the initial setup wizard
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-33535 It would be nice to show the Jenkins version during the initial setup wizard Change By: Daniel Beck Labels: 2.0 2.0-planned Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33805) Integrate upgrade wizard step 0 and InstallUtil/InstallState
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-33805 Integrate upgrade wizard step 0 and InstallUtil/InstallState Change By: Daniel Beck Labels: 2.0 2.0-beta 2.0-planned Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33805) Integrate upgrade wizard step 0 and InstallUtil/InstallState
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-33805 Integrate upgrade wizard step 0 and InstallUtil/InstallState Maybe just rename the files used by wizard step 0 so it's clear where they are from? Change By: Daniel Beck Labels: 2.0 2.0-beta 2.0-planned Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33813) 2.0 Setup wizard: No valid crumb was included in the request
Title: Message Title Daniel Beck commented on JENKINS-33813 Re: 2.0 Setup wizard: No valid crumb was included in the request Keith Zantow The merged commit fixes this, right? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jgiven-plugin] (JENKINS-33920) Jenkins standard output overwritten by JGiven
Title: Message Title Niko Wittenbeck updated an issue Jenkins / JENKINS-33920 Jenkins standard output overwritten by JGiven Change By: Niko Wittenbeck Summary: Jenkins Standard Output standard output overwritten by JGiven Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jgiven-plugin] (JENKINS-33920) Jenkins Standard Output overwritten by JGiven
Title: Message Title Niko Wittenbeck created an issue Jenkins / JENKINS-33920 Jenkins Standard Output overwritten by JGiven Issue Type: Bug Assignee: wolfs Components: jgiven-plugin Created: 2016/Mar/31 7:32 AM Priority: Minor Reporter: Niko Wittenbeck The regular Jenkins standard output is completely overwritten with the JGiven results. It would be great if the standard output could be preserved and the JGiven results are either prepended or appended. Add Comment
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-28289 JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Change By: Oliver Gondža Labels: 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected 1.651.1-rejected lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Change By: Oliver Gondža Labels: 1.651.1-rejected jnlp lts-candidate remoting security Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Oliver Gondža commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Fixing this on master caused JENKINS-33886, not backporting this into LTS. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
Title: Message Title Oliver Gondža commented on JENKINS-26580 Re: For JNLP slaves the master-slave communication should be encrypted Fixing this on master caused JENKINS-33886, not backporting this into LTS. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-28289 JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Change By: Oliver Gondža Labels: 1.625.3-rejected 1.642.2-rejected 1.642.3-rejected 1.651.1- fixed rejected Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Change By: Oliver Gondža Labels: 1.651.1- fixed rejected jnlp remoting security Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-33919) Add option to choose path delimiter
Title: Message Title Maciej Wolniewicz created an issue Jenkins / JENKINS-33919 Add option to choose path delimiter Issue Type: New Feature Assignee: Oleg Nenashev Components: throttle-concurrent-builds-plugin Created: 2016/Mar/31 6:51 AM Environment: Jenkins 1.596.2 Throttle Concurrent Builds Plug-in 1.8.4 Priority: Major Reporter: Maciej Wolniewicz Hi, Is it possible to add an option to plugin to change current path delimiter from "@" to other sign? Currently when job is using Throttle Concurrent Builds plugin following naming convention is used to create new workspace: .../workspace/@ We have tools which are executing svn commands on each workspace and we are getting errors as svn commands interprets @ sign as revision number: svn --non-interactive info ../worskpace/job_name@2 Failed to resolve revision ../worskpace/job_name@2: (Not a valid URL)
[JIRA] [workflow-plugin] (JENKINS-33837) Pipelines: Blocking also for subsequent downstream jobs
Title: Message Title
Michael Hüttermann updated an issue
Jenkins / JENKINS-33837
Pipelines: Blocking also for subsequent downstream jobs
Change By:
Michael Hüttermann
Given a pipeline script, I configure to execute a build step to build a (existing) job:{code}build job: 'Project-Build-Job1_Kickoff', wait: true{code}The job is triggered successfully, and the pipeline waits for its completion. But, the called build job has a post-build action defined of kind "trigger parameterized build on other project". The pipeline does not wait for the downstream build, only for the first one in the chain which is referenced by name in the pipeline script. It is expected that the existing functionality is used and embedded "as is", thus pipeline waits for completion of complete downstream chain.Update: this works as a sequence of build jobs linked with Post Build Actions. Triggering the first one via Pipeline, the downstreamed ones are triggered as well, but the Pipeline does not block until completion. This is critical because this prevents migration.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33837) Pipelines: Blocking also for subsequent downstream jobs
Title: Message Title Michael Hüttermann updated an issue Jenkins / JENKINS-33837 Pipelines: Blocking also for subsequent downstream jobs Change By: Michael Hüttermann Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
