[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title Henry Borchers commented on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script It started working on our end when we upgraded the version of Docker to the latest. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.3905.1572304500149%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title Henry Borchers commented on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script I'm taking a research day, so I'm working from home and haven't tried anything on the Windows server at work. Anyways, I tried to get a Windows Docker container working in Jenkins on my home Windows 10 machine and it worked. I'm thinking the server at work must have a configuration incorrectly set. I just wish I could figure out what the heck the problem is. I'm not even sure where to look. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.18588.1571861880210%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title
Henry Borchers commented on JENKINS-59893
Re: bat calls hang in Windows Docker container in declarative pipeline script
a b Host OS:, Windows Server 2019 Docker images tried:
mcr.microsoft.com/windows/servercore:ltsc2019
mcr.microsoft.com/powershell:preview
One of my own based off of mcr.microsoft.com/dotnet/framework/sdk:3.5
Same experience on every one. Currently my test pipeline looks like. this
pipeline {
agent any
stages {
stage('hello world') {
parallel {
// this one doesn't work
stage('Hello world on Windows') {
agent {
docker {
label 'Windows&&Docker&&aws'
image 'mcr.microsoft.com/windows/servercore:ltsc2019'
}
}
options {
timeout(1) // in case the pipeline hangs
}
steps {
// hangs here
powershell 'powershell "cmd /c echo test inside"'
}
}
// This one works just fine
stage('Hello world on Linux') {
agent {
docker {
label 'linux&&docker&&aws'
image 'alpine:latest'
}
}
options {
timeout(1) // in case the pipeline hangs
}
steps {
sh 'echo "hello world"'
}
}
}
}
}
}
Add Comment
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title Henry Borchers edited a comment on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script I'm also have having this problem. However for me, it's also hanging on powershell as well . Edit: typo Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.13417.1571771340180%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title Henry Borchers commented on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script I'm also have this problem. However for me, it's also hanging on powershell. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202638.1571768371000.13412.1571770020111%40Atlassian.JIRA.
[JIRA] (JENKINS-57968) Set the source root for Warnings-ng plugin
Title: Message Title Henry Borchers updated an issue Jenkins / JENKINS-57968 Set the source root for Warnings-ng plugin Change By: Henry Borchers Summary: set Set the source root for Warnings-ng plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199952.1560274992000.25369.1560275580283%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57968) set the source root for Warnings-ng plugin
Title: Message Title Henry Borchers updated an issue Jenkins / JENKINS-57968 set the source root for Warnings-ng plugin Change By: Henry Borchers Summary: set the source rootfor Warnings-ng plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199952.1560274992000.25367.1560275580261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57968) set the source root
Title: Message Title Henry Borchers created an issue Jenkins / JENKINS-57968 set the source root Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-06-11 17:43 Priority: Minor Reporter: Henry Borchers My pipelines generate my builds out of source which has provide me with a problem with any warning messages that use relative paths for the file names. warnings-ng is able to parse the warning messages beautifully but it's unable to link it back to the scm directory or source root. For reference, my jenkins workspace looks a little like this... / /scm/ /scm/.git/ /build/ /reports/ /dist/ /logs/ What I would love is to use is something like this is my pipeline recordIssues( tools: [myPy(name: 'MyPy', pattern: 'logs/mypy.log')], sourcePath: "scm" ) I love this plugin. it's saved me from so much trouble
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Well then you may be trying to apply a wrong tool for the job. Try some commercial offers maybe. I understand your be frustrated but comments like this are not very helpful. I guess my point is - declarative style just sucks. From my experience it works only for small and simple projects despite how hard it's being advertised an opposite. I couldn't disagree more. It's super easy to read and understand. It has a clean syntax. It's well thought out. It's expandable with scripts if need be. It's so easy to to look through the blue ocean to see why something has failed. It's freaking brilliant!!! The declarative pipeline is the main reason that I use Jenkins and why I advocate for it wherever I go. Did I mention it's brilliant? The biggest issue is that it is so easy to use, that I just want to use it more and more until I get smacked in the face with "Method code too large!. It's a little bit like the use of electricity over the last century. Most electronic devices have become more efficient throughout the decades and use less electricity as their designs have improved. However, we keep finding new uses for electricity at a faster rate than we can make them more efficient. We end up needing more and more power plants as a result, not fewer. I feel the same way with Jenkins and especially the declarative pipeline. I've been getting the lines in my steps into fewer and fewer lines. I make shared-libraries for my common code and "helper script functions" outside of the pipeline block. However, I keep finding more and more ways to find problems in my code early with careful placement of "sequential and parallel stages" and "when and post" blocks. I end up with lots of stages with one or two lines in the steps block. Then all of a sudden, I run into "Method code too large!"... And then I become a sad developer... Add Comment
[JIRA] (JENKINS-56383) Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade
Title: Message Title Henry Borchers commented on JENKINS-56383 Re: Blue Ocean pipeline UI stopped rendering correctly after plugin upgrade Same issue here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Jesse Glick, a few post ago you mentioned something about creating a different execution engine that wouldn't have this issue. Anything you can point me to so that I can follow the progress or, at least, is anything interesting that you can tease to keep me hopeful that the future looks bright? I have been putting any "steps block" that is more than 1 line into into helper functions but I'm still running into issues. I'm sorry if I come off as nagging. I just really love Jenkins. The declarative pipeline has been my one of favorite tools which I used for everything I build, Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Sam Van Oort, it's been a few months since you teased us about something on your roadmap that would alleviate this issue. Any chance you could provide a little more info or at least tease us enough to wet our appetite? I'm running against the limit way too often these days. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I'm running into this more and more. I've put what makes sense into shared libraries and squeeze more and more into ugly "helper functions" outside of the pipeline but it's getting really hard. I really hope there is a better solution coming soon because I'm pretty sure that my coworkers are working with HR to have a talk with me about how much swearing I've been doing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56106) Install Python automatically Global Tools
Title: Message Title Henry Borchers created an issue Jenkins / JENKINS-56106 Install Python automatically Global Tools Issue Type: New Feature Assignee: Jan Niklas Hasse Components: python-plugin Created: 2019-02-12 18:34 Priority: Minor Reporter: Henry Borchers I love not having to worry about deploying of CMake to a build node when it needs it. Declaring the tool in my pipeline build will simply returns the path to the installed executable if installed and if not, Jenkins installs it for me. I really wish I could do that same with Python instead of having to manually install multiple versions on different workstations and configuring the tools location on each node. Is there any way that using Python in Jenkins could be made this simple? Add Comment
[JIRA] (JENKINS-55156) Warnings NG beta6's recordIssues command doesn't close the file handles
Title: Message Title Henry Borchers created an issue Jenkins / JENKINS-55156 Warnings NG beta6's recordIssues command doesn't close the file handles Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2018-12-12 16:52 Environment: Jenkins ver. 2.150.1 Priority: Major Reporter: Henry Borchers Just upgraded from beta4 to beta6 on a Windows 2016 server. When upgraded, I started running into an issue where the log files I used with recordIssues wouldn't close the file handles and couldn't be deleted unless I restart or force it with ProcessExplorer. Even after the pipeline is completed. I'm using this line in my post section recordIssues enabledForFailure: true, tools: [[tool: myPy(pattern: 'logs/mypy.log')]] Add Comment
[JIRA] (JENKINS-51367) Add support of optional report names
Title: Message Title Henry Borchers commented on JENKINS-51367 Re: Add support of optional report names Is this still in the works? I would really like to customize my coverage report names. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Henry Borchers commented on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Henry Borchers, complexity of your pipeline is completely irrelevant.
Couldn't agree more
Just to draw a parallel, the fact that you're creating complex Enterprise product does not justify you to put all it's code in a single file, or even in a single method, does it?
It's not a complex Enterprise product. Quite the opposite. I don't have much support so I have to automate as much DevOps stuff myself. Because I have very little resources and stakeholders that require a lot, I'm making the most of the resources I can get my hands on.
Parts of your pipeline has to be a reusable functions in the shared library, so your actual jenkins file should consist only simple statements, something like
doThis()
if (itsTrue()) {
doThat()
}
That applies only for scripted pipelines, of course. Accordingly to https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines it sounds like declarative pipelines even more limited than I thought, so I'm happy I don't use 'em.
I'm happy that you're happy that you don't use declarative pipelines. However, I do. The only limit I've run has been line length.
Just a quick searching in google reveal there is actually an open source project doing something good enough to demonstrate what I mean: https://github.com/fabric8io/fabric8-pipeline-library https://github.com/fabric8io/fabric8-jenkinsfile-library
Yes. I already use shared libraries for somethings already. I just don't use need it very often. The only reason my pipelines are so long is because of the declarative style.
stage("Run Doctest Tests"){
when {
equals expected: true, actual: params.TEST_DOCTEST
}
steps{
bat "pipenv run sphinx-build -b doctest docs\\source build\\docs -d build\\docs\\doctrees -v"
}
post{
always {
dir(reports){
archiveArtifacts artifacts: "doctest.txt"
}
}
}
}
It's more verbose but I find it highly readable and very easy to maintain. Shared libraries are nice for helpers but they can be a pain for maintain so I keep the
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Dmytro Kryvenko, My pipeline is long because it contains more than just unit testing. It's a complete DevOps pipeline with optional stages depending on the situation. I have sequential stages, parallel stages and most of these have a post section that cleans up or depends on the success or failure of the stage. It's very declarative and pretty easy to reason with so there really shouldn't be a reason to refactored the code. Jenkins has become very very powerful tool with the Pipeline DSL with a lot of very useful features. It's a shame when I when I can't use a feature because my pipeline contains too many lines already. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Henry Borchers assigned an issue to Olivier Lamy Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Henry Borchers Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Henry Borchers commented on JENKINS-53311 Re: [Blue Ocean] Sequential stages appear to be completed but are still executing sorry, i accidentally clicked assign to me. didn't mean to and I'm not sure how to revert to the original setting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Henry Borchers assigned an issue to Unassigned Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Henry Borchers Assignee: Henry Borchers Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Henry Borchers assigned an issue to Henry Borchers Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Henry Borchers Assignee: Olivier Lamy Henry Borchers Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Henry Borchers commented on JENKINS-36776 Re: Support Windows Server Containers I'm super excited to see a pull request that's has passed all the required check. I'm wondering what's holding it back from being merged. Using Windows containers as Jenkins Agents would be very very useful to me for testing in isolation and caching of dependencies and tools. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I'm starting to run into this issue myself when my pipeline reaches about 800 lines. I've been creating helper function outside of the "pipeline" brackets and that's helping but I find myself still running into this issue more than I'd like. I can't help it. Having all the new nice features makes me write longer more useful pipelines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51117) Having CMake versions 3.11 in Global Tool Configuration cause errors in updating plugins
Title: Message Title Henry Borchers closed an issue as Fixed Jenkins / JENKINS-51117 Having CMake versions 3.11 in Global Tool Configuration cause errors in updating plugins Change By: Henry Borchers Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51117) Having CMake versions 3.11 in Global Tool Configuration cause errors in updating plugins
Title: Message Title Henry Borchers created an issue Jenkins / JENKINS-51117 Having CMake versions 3.11 in Global Tool Configuration cause errors in updating plugins Issue Type: Bug Assignee: Martin Weber Components: cmakebuilder-plugin Created: 2018-05-03 21:37 Priority: Minor Reporter: Henry Borchers If you manually add cmake-3.11.1 to the CMake installations in the Global Tool Configuration, any time you check updates in the Plugins Manager menu, the resulting page is "None of the tool installer metadata passed the signature check" Add Comment
[JIRA] (JENKINS-34454) Add support for Docker-Toolbox/Windows
Title: Message Title Henry Borchers commented on JENKINS-34454 Re: Add support for Docker-Toolbox/Windows I'm guessing it's going to be a long time before we see Windows support since it doesn't look like anybody is working on this and it seems like it's low priority. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34454) Add support for Docker-Toolbox/Windows
Title: Message Title Henry Borchers commented on JENKINS-34454 Re: Add support for Docker-Toolbox/Windows Just curious. Any luck on making any progress on this or is this a feature that I won't see for any time in the foreseeable future? I just want to adjust my hype expectations appropriately. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Henry Borchers commented on JENKINS-36776 Re: Support Windows Server Containers It's been a while since any comments were posted here. Is anybody working on this? Docker on Windows would make my life so much easier. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
