[JIRA] (JENKINS-61218) Stage view for previous builds should be displayed while the build is running
Title: Message Title Alex Taylor commented on JENKINS-61218 Re: Stage view for previous builds should be displayed while the build is running Alexander Samoylov to me having https://issues.jenkins-ci.org/browse/JENKINS-61217 solved means this one gets solved as well correct? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204772.1582631088000.17663.1587769740147%40Atlassian.JIRA.
[JIRA] (JENKINS-61217) Stage view for previous builds should not be removed if stages change
Title: Message Title Alex Taylor commented on JENKINS-61217 Re: Stage view for previous builds should not be removed if stages change Reclassified as a new feature because this is behaving as designed and will require a significant amount of work Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204771.1582628324000.17660.1587769680146%40Atlassian.JIRA.
[JIRA] (JENKINS-61217) Stage view for previous builds should not be removed if stages change
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-61217 Stage view for previous builds should not be removed if stages change Change By: Alex Taylor Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204771.1582628324000.17657.1587769620329%40Atlassian.JIRA.
[JIRA] (JENKINS-61669) Removing a template from the EC2 plugin while a job is still building causes a file leak
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-61669 Removing a template from the EC2 plugin while a job is still building causes a file leak Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-24 19:10 Priority: Major Reporter: Alex Taylor Issue: When a job is running on a template from EC2 and then you go and change or delete that template it causes a file leak of files `($INSTANCE_ID)/slave.log.*` which are the traditional log files open for agents but they are not cleaned up ever afterwards and as the agent is running it opens more and more of these file handles until eventually the whole instance crashes or the build is done (the files are not released at that point but they do not continue to increase) Steps to reproduce: 1. Create a EC2 cloud 2. Create a template within that cloud 3. Create a job which takes a long period of time and uses that template 4. Run that job 5. Delete the template 6. Observe the file handles continue to increase and you can find many file handles of the format above What I would normally expect: I think the file handles being opened is OK but they should not continue to re-open. Also they should be cleaned up when the job is done and the agent goes away I have not been able to reproduce locally with the code using hpi:run as of yet so I am not sure what is causing the leak
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title Alex Taylor commented on JENKINS-61591 Re: Using Stage view with mixed in/out of stage actions causes the build status to be wrong Devin Nusbaum Always been a problem with declarative and stage view as far back as I can tell. It does not replicate with scripted syntax in any way I have tried locally Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205288.1584636193000.12207.1585069740194%40Atlassian.JIRA.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title
Alex Taylor updated an issue
Jenkins / JENKINS-61591
Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Change By:
Alex Taylor
Issue:In declarative when you have a series of stages with one action outside of those stages that fails, it will cause the stage view status (the blue/red ball on the left side of the view) to show the incorrect status of the build.Steps to reproduce:Create a pipeline with this as the definition:{code:java}pipeline {agent any checkoutstages {stage('Build') { steps { echo "hello"}}stage('Test') { steps { echo "hello"}}stage('Deploy') { steps { echo "hello"}}}}{code}Run that code and look at the stage view to see that it appears the build was successful but it clearly failed on the build status screen on the left. Build 203 looks correct and build 204 is the one with the incorrect status indicator: !Screen Shot 2020-03-19 at 12.43.38 PM.png|thumbnail! Expected results:The stage view page correctly shows the build status being failed.The biggest issue with this is that if a build fails to checkout its Jenkinsfile it will do this same thing which causes a problem where the build looks successful when it actually wasn't
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-61591 Using Stage view with mixed in/out of stage actions causes the build status to be wrong Change By: Alex Taylor Attachment: Screen Shot 2020-03-19 at 12.43.38 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205288.1584636193000.9685.1584636300325%40Atlassian.JIRA.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-61591
Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2020-03-19 16:43
Priority:
Minor
Reporter:
Alex Taylor
Issue: In declarative when you have a series of stages with one action outside of those stages that fails, it will cause the stage view status (the blue/red ball on the left side of the view) to show the incorrect status of the build. Steps to reproduce: Create a pipeline with this as the definition:
pipeline {
agent any
checkout
stages {
stage('Build') {
steps {
echo "hello"
}
}
stage('Test') {
steps {
echo "hello"
}
}
stage('Deploy') {
steps {
echo "hello"
}
}
}
}
Run that code and look at the stage view to see that it appears the build was successful but it clearly failed on the build status screen on the left. Expected results: The stage view page correctly shows the build status being failed. The biggest issue with this is that if a build fails to checkout its Jenkinsfile it will do this same thing which causes a problem where the build looks successful when it actually wasn't
[JIRA] (JENKINS-61137) CloudBees flow plugin generates the wrong syntax with the syntax link
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-61137
CloudBees flow plugin generates the wrong syntax with the syntax link
Issue Type:
Bug
Assignee:
ElectricFlow ElectricCloud
Components:
electricflow-plugin
Created:
2020-02-19 01:05
Priority:
Major
Reporter:
Alex Taylor
Issue: When you use the pipeline syntax link to be able to build the proper step inside of a pipeline the syntax format looks like this:
cloudBeesFlowRunPipeline addParam: '{"pipeline":{"pipelineName":"$NAME","parameters":...', configuration: '$CONFIG', pipelineName: '$NAME', projectName: '$PROJECT'
but this syntax does not work inside of Jenkins and the syntax must be something more like this:
step([$class: 'ElectricFlowPipelinePublisher',
configuration: '$CONFIG',
projectName: '$PROJECT',
pipelineName: '$NAME',
addParam: '{"pipeline":{"pipelineName":"$NAME","parameters":...'
Getting the correct syntax added would be great
[JIRA] (JENKINS-61096) Blue Ocean UI never allows you to have more than about 10 tabs open at a time
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-61096
Blue Ocean UI never allows you to have more than about 10 tabs open at a time
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2020-02-14 14:00
Priority:
Minor
Reporter:
Alex Taylor
Issue: If you have around 10 tabs open inside of Blue Ocean to the same instance, the last few will never load the page and will persistently reload themselves making the entire UI unusable Steps to reproduce: 1. Open any Jenkins version with any Blue Ocean Version(tested the latest along with all the way back to 1.2.x versions) 2. Create a dummy pipeline job with `node() {echo "hello"} ` 3. Run said job 4. Open up the Blue Ocean UI on the pipeline job you created 5. Hold command/ctrl and click the `build number 1` link about 10 times 6. Observe that tab 10 never loads fully and eventually reloads all the pages because it becomes unresponsive Observations: I think there is either some kind of resource deadlock when opening that many tabs or such a bad bottleneck that it blocks the continuous loading nature of the Blue Ocean plugin so that it starts getting 404 errors and needs to reload itself. This issue never shows up in any threads from Jenkins (no new threads are even created) and the browser indicates a whole bunch of failing modules but nothing consistent enough to say "this is the cause" Resolution: To me this looks core to the way Blue Ocean was designed and has existed ever since the inception of it. It is worse now because it terminates the pages faster but it was still present in early versions.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Alex Taylor assigned an issue to Alex Taylor Jenkins / JENKINS-57430 Getting issue when using github Change By: Alex Taylor Assignee: Liam Newman Alex Taylor 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.199242.1557751552000.7896.1574885880819%40Atlassian.JIRA.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Alex Taylor updated JENKINS-57430 Jenkins / JENKINS-57430 Getting issue when using github Change By: Alex Taylor Status: In Progress Review 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.199242.1557751552000.7903.1574885881000%40Atlassian.JIRA.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Alex Taylor commented on JENKINS-57430 Re: Getting issue when using github This should be fixed by https://github.com/github-api/github-api/pull/622 for at least the CHECK_RUN event so it will stop this particular bug. There are many other unchecked events though that need to be added. That is a whole other problem 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.199242.1557751552000.7892.1574885880712%40Atlassian.JIRA.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Alex Taylor started work on JENKINS-57430 Change By: Alex Taylor Status: Open In Progress 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.199242.1557751552000.7901.1574885880948%40Atlassian.JIRA.
[JIRA] (JENKINS-59466) Nested Views are incompatible with Config as Code
Title: Message Title Alex Taylor commented on JENKINS-59466 Re: Nested Views are incompatible with Config as Code After testing out the PR, I have found that Nested views just pretty much doesnt work with Config as code. This stops if from breaking but the views dont actually work which means either nested views needs to ensure that it is following Config as Code practices or CasC needs to change so that this plugin works with it. I am assuming the former is going to be easiest. Technically, this defect is "done" but the plugin still doesnt work with CasC 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.202064.1569007172000.4994.1574344082831%40Atlassian.JIRA.
[JIRA] (JENKINS-59466) Nested Views are incompatible with Config as Code
Title: Message Title Alex Taylor commented on JENKINS-59466 Re: Nested Views are incompatible with Config as Code So I created this PR which does fix the error but I am not confident that this is the best fix since it would set the owner of all your nested views to the SYSTEM user or Jenkins user. That may be bad practice and make things break... 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.202064.1569007172000.5295.1569443400185%40Atlassian.JIRA.
[JIRA] (JENKINS-59466) Nested Views are incompatible with Config as Code
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-59466 Nested Views are incompatible with Config as Code Issue Type: Improvement Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin, nested-view-plugin Created: 2019-09-20 19:19 Priority: Minor Reporter: Alex Taylor Issue: When trying to import a yaml with config as code, if that yml code has nested views then it will fail due to a Null pointer Steps to reproduce: 1. Create a view with nested views 2. Export that config as code yaml 3. Import the yaml and observe the null pointer The error: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1095) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.reflect.InvocationTargetException at 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 hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) ... 8 more Caused by: java.lang.NullPointerException at hudson.plugins.nested_view.NestedView.save(NestedView.java:258) at hudson.BulkChange.commit(BulkChange.java:98) at
[JIRA] (JENKINS-57707) Env variables are empty after upgrade
Title: Message Title Alex Taylor commented on JENKINS-57707 Re: Env variables are empty after upgrade Roman80 Please try updating to 2.2.1 because there were some fixes on backslashed items in windows: https://github.com/jenkinsci/envinject-plugin/releases 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.199646.1558983656000.6094.1567542060172%40Atlassian.JIRA.
[JIRA] (JENKINS-58865) Electric flow plugin does not return the json details of a REST call
Title: Message Title Alex Taylor commented on JENKINS-58865 Re: Electric flow plugin does not return the json details of a REST call This could be done one of 3 ways: 1. The Electric flow REST API function could be changed into a `Step` rather than implementing a `SimpleBuildStep` since the Simple build step does not allow for return values. This would mean writing a custom step which will send out the API call and then return the response from the Electric Flow server into a groovy variable 2. This REST API could be converted into a block-scoped Step (or SimpleBuildWrapper) and then the response could be captured inside of an Environment variable which is able to be used later inside of the pipeline. 3. https://issues.jenkins-ci.org/browse/JENKINS-29144 could be fixed and a SimpleBuildStep could be used to create the same environment variable in #2 For 1 this would look like: def returnOut = step([$class: 'ElectricFlowGenericRestApi', configuration: 'CBFConfiguration', urlPath : '/projects', httpMethod : 'POST', body : '', parameters : [ [$class: 'Pair', key: 'projectName', value: 'EC-TEST-Jenkins-1.00.00.01' ], [$class: 'Pair', key: 'description', value: 'Native Jenkins Test Project' ] ] ]) and that returnOut would be a groovy variable and able to be used anywhere else For 2 and 3 there would be a general ENV variable called something like `REST_API_OUPUT` which is set on the return and then that can be used in the pipeline with `$env.REST_API_OUTPUT` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58865) Electric flow plugin does not return the json details of a REST call
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-58865 Electric flow plugin does not return the json details of a REST call Issue Type: Improvement Assignee: ElectricFlow ElectricCloud Components: electricflow-plugin Created: 2019-08-08 18:25 Priority: Minor Reporter: Alex Taylor Issue: I am trying to do a REST API call to create a electricflow job execution. When I run that REST call it will respond with a json of the ID for that execution and I want to parse that ID into a groovy variable Steps to resolve: From what I am seeing the `perform` method here: https://github.com/jenkinsci/electricflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/electricflow/ElectricFlowGenericRestApi.java#L68 does not return a value into a groovy variable. In my opinion it should be like `ReturnStdOut` on a shell step inside of a pipeline rather than just printing into the logs. This would allow other REST calls to check on the status the build using the ID which is returned Add Comment
[JIRA] (JENKINS-58817) Pipeline: Groovy kills remote calls after 5 minutes
Title: Message Title Alex Taylor commented on JENKINS-58817 Re: Pipeline: Groovy kills remote calls after 5 minutes https://github.com/jenkinsci/workflow-cps-plugin/pull/313 for the 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201129.1565026708000.8961.1565109540116%40Atlassian.JIRA.
[JIRA] (JENKINS-58817) Pipeline: Groovy kills remote calls after 5 minutes
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-58817 Pipeline: Groovy kills remote calls after 5 minutes Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-08-05 17:38 Priority: Minor Reporter: Alex Taylor Issue: I was trying to make a remote call on a Jenkins instance using a groovy script and it was failing after 5 minutes if there was not a response. Steps taken to identify the issue: 1. The Stacktrace from the interrupted exception: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.Channel.call(Channel.java:956) at sun.reflect.GeneratedMethodAccessor344.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:47) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:158) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:156) at
[JIRA] (JENKINS-43587) Pipeline fails to resume after master restart/plugin upgrade
Title: Message Title Alex Taylor commented on JENKINS-43587 Re: Pipeline fails to resume after master restart/plugin upgrade Mircea-Andrei Albu I think this may be a different issue since this is a much later version you are updating Jenkins to. I would open a new JIRA with the Jenkins logs included since there may be an error there about why the build did not resume 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.180909.1492112497000.4647.1558127400537%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
Alex Taylor edited a comment on JENKINS-34610
Re: Windows AMI in endless loop
We were able to get the windows agent to run by setting the "Allow remote server management through WinRM" IP settings to "*". Screenshot attached.We also had to run the below commands. !Screenshot 2019-05-09 11.58.27.png|thumbnail! {code:java} winrm quickconfig winrm set winrm/config/service/Auth @{Basic="true"} winrm set winrm/config/service @{AllowUnencrypted="true"} winrm set winrm/config/winrs @{MaxMemoryPerShellMB="10240"} {code} Should this exist on the wiki page [~francisu]? I was thinking there is not much "official troubleshooting" for windows EC2 connections and it seems lots of people are having troubles. !Screenshot 2019-05-09 11.58.27.png|thumbnail!
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.170238.1462391043000.1431.1557753362081%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
Alex Taylor commented on JENKINS-34610
Re: Windows AMI in endless loop
We were able to get the windows agent to run by setting the "Allow remote server management through WinRM" IP settings to "*". Screenshot attached. We also had to run the below commands. winrm quickconfig winrm set winrm/config/service/Auth @ {Basic="true"} winrm set winrm/config/service @ {AllowUnencrypted="true"} winrm set winrm/config/winrs @ {MaxMemoryPerShellMB="10240"} Should this exist on the wiki page Francis Upton? I was thinking there is not much "official troubleshooting" for windows EC2 connections and it seems lots of people are having troubles.
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.170238.1462391043000.1422.1557753361938%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-34610 Windows AMI in endless loop Change By: Alex Taylor Attachment: Screenshot 2019-05-09 11.58.27.png 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.170238.1462391043000.1394.1557753300439%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56992) When a pod dies in kubernetes, we should be able to dump out the pod logs somewhere
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-56992 When a pod dies in kubernetes, we should be able to dump out the pod logs somewhere Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-04-12 15:07 Priority: Major Reporter: Alex Taylor Issue: I have a pipeline which is massively parallel and spins up a series of kubernetes pods to do a build process with a few containers on each. Occasionally(about 1 of every 5-10) the kubernetes pod will disconnect with an error message Could not connect to $CONTAINER to send interrupt signal to process This becomes very difficult to troubleshoot a solution for since there is not any additional details Resoution: It would be very helpful here to get logs or more details about the failure by potentially dumping the failed pod logs somewhere. This would be very helpful to have inside of the Kubernetes plugin since the pod no longer exists after the build is done and getting the previous logs is difficult if it is not caught instantly
[JIRA] (JENKINS-38552) Multibranch pipeline (re)creation intelligence
Title: Message Title Alex Taylor commented on JENKINS-38552 Re: Multibranch pipeline (re)creation intelligence chirs damour If that is the case then this feature will not work as a workaround. The webhook triggering still happens normally there is just not an initial build which normally happens automatically without the intervention of a webhook 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-38552) Multibranch pipeline (re)creation intelligence
Title: Message Title Alex Taylor commented on JENKINS-38552 Re: Multibranch pipeline (re)creation intelligence chirs damour Yeah that would work since this configuration item will ignore that first default build which happens and therefore should not trigger the multibranch twice. I wold worry it would not work since there does not seem to be an actual cause for the other ticket but it would at least stop the first 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-56250) Ansible Tower Plugin not injecting Environment Variables for later use
Title: Message Title
Alex Taylor updated an issue
Jenkins / JENKINS-56250
Ansible Tower Plugin not injecting Environment Variables for later use
Change By:
Alex Taylor
Issue:When creating a ENV variable within the Ansible Tower plugin API calls on a pipeline, that ENV variable is not usable inside of subsequent steps for Jenkins.Steps to reproduce:1. Create a Pipeline job with an Ansible Tower step2. Inside of that step call an ansible script which uses the suggested line:{code:java} - name: Set a Jenkins variable debug:msg: "JENKINS_EXPORT VAR_NAME=value"{code}3. Try to echo that `VAR_NAME` using an `echo ${env.VAR_NAME} in a new stage4. Observe the variable comes back as "null"I even tried to expand the scope of the variable name using a `withEnv(['VAR_NAME=""']) {` at the beginning but that still does not workExpected Result:I would expect to see a ENV variable later in the pipeline but maybe the scope of that variable is only for within the ansible script?
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-56250) Ansible Tower Plugin not injecting Environment Variables for later use
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-56250
Ansible Tower Plugin not injecting Environment Variables for later use
Issue Type:
Bug
Assignee:
John Westcott
Components:
ansible-tower-plugin
Created:
2019-02-22 16:40
Priority:
Major
Reporter:
Alex Taylor
Issue: When creating a ENV variable within the Ansible Tower plugin API calls on a pipeline, that ENV variable is not usable inside of subsequent steps for Jenkins. Steps to reproduce: 1. Create a job with an Ansible Tower step 2. Inside of that step call an ansible script which uses the suggested line:
- name: Set a Jenkins variable
debug:
msg: "JENKINS_EXPORT VAR_NAME=value"
3. Try to echo that `VAR_NAME` using an `echo ${env.VAR_NAME} in a new stage 4. Observe the variable comes back as "null" I even tried to expand the scope of the variable name using a `withEnv(['VAR_NAME=""']) {` at the beginning but that still does not work Expected Result: I would expect to see a ENV variable later in the pipeline but maybe the scope of that variable is only for within the ansible script?
[JIRA] (JENKINS-48161) Deadlock caused by synchronized methods in EC2Cloud
Title: Message Title Alex Taylor commented on JENKINS-48161 Re: Deadlock caused by synchronized methods in EC2Cloud Andrea Vavassori This very much looks like JENKINS-53858 which was resolved in 1.42. Could I get you to compare that JIRA with your current one and see if it is the same thing? 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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Alex Taylor commented on JENKINS-53146 Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step Anyone have time to review my PR and give the "all good"? Once I can get someone else who says this works then I will work on getting a new release 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-52960) When running a job in distributed node, logs reports errors related to creation of csv files in workspace
Title: Message Title Alex Taylor commented on JENKINS-52960 Re: When running a job in distributed node, logs reports errors related to creation of csv files in workspace This issue was resolved with an update past 5.5.1 on at least one instance so thanks! 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-19892) TOOL_HOME doesn't work in PATH
Title: Message Title Alex Taylor updated JENKINS-19892 Jenkins / JENKINS-19892 TOOL_HOME doesn't work in PATH Change By: Alex Taylor Status: In Progress Review 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-19892) TOOL_HOME doesn't work in PATH
Title: Message Title Alex Taylor commented on JENKINS-19892 Re: TOOL_HOME doesn't work in PATH This should be fixed with the update in https://issues.jenkins-ci.org/browse/JENKINS-53146 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-19892) TOOL_HOME doesn't work in PATH
Title: Message Title Alex Taylor started work on JENKINS-19892 Change By: Alex Taylor Status: Open In Progress 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-19892) TOOL_HOME doesn't work in PATH
Title: Message Title Alex Taylor assigned an issue to Alex Taylor Jenkins / JENKINS-19892 TOOL_HOME doesn't work in PATH Change By: Alex Taylor Assignee: Alex Taylor 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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Alex Taylor started work on JENKINS-53146 Change By: Alex Taylor Status: Open In Progress 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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Alex Taylor commented on JENKINS-53146 Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step I am pretty sure I fixed this issue with the new PR. If anyone has time to test it out for themselves locally that would be great 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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Alex Taylor updated JENKINS-53146 Jenkins / JENKINS-53146 TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step Change By: Alex Taylor Status: In Progress Review 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-55355) HTML no longer is parsed in Build Pipeline view after core security update
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-55355 HTML no longer is parsed in Build Pipeline view after core security update Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 2018-12-28 20:21 Environment: Jenkins 2.46 and newer Latest Build Pipeline plugin Priority: Major Reporter: Alex Taylor Issue: When trying to create HTML within a build pipeline view(through either parameters or descriptions etc.) the HTML is no longer parsed by the markup formatter Steps to reproduce: Create a new OSS jenkins instance at least version 2.46 Install the build pipeline view plugin Create 2 jobs(upstream and downstream) Add a parameter to one of those jobs which has HTML(I used a string parameter) Create a new build pipeline view to start with the upstream job make sure you are displaying the parameters and variables within the view Observed behavior: The HTML code is not parsed correctly and it treats it as a literal string Expected behavior: The HTML code is parsed by the markup formatter and it appears as parsed HTML You can see with version 2.45 of Jenkins that the issue is not present and the HTML is parsed which means this security update is the cause. Additionally no where else within the instance is unable to parse this HTML code but on that
[JIRA] (JENKINS-55192) Being able to add a custom log file would be a really great feature
Title: Message Title Alex Taylor commented on JENKINS-55192 Re: Being able to add a custom log file would be a really great feature Ted That post action would not work on an audit trail log since that is kept on the master in an arbitrary location like /var/log by default which means your solution would be splunk forwarder? That is external to Jenkins correct? I was just hoping for a way to forward on master log files to splunk via the plugin but maybe the plugin does not work that way. Let me know if that was not how the plugin was intended to be used or if that does not make sense as a feature 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-55192) Being able to add a custom log file would be a really great feature
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-55192 Being able to add a custom log file would be a really great feature Change By: Alex Taylor Summary: Being able to add a custom log file would be a really cool great feature 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-55192) Being able to add a custom log file would be a really cool feature
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-55192 Being able to add a custom log file would be a really cool feature Issue Type: New Feature Assignee: Ted Components: splunk-devops-plugin Created: 2018-12-13 21:22 Priority: Minor Reporter: Alex Taylor Issue: I have a custom log file like an Audit trail log or something similar which I would like to do Splunk Analysis on but I have no way to get that there with the splunk plugin(that I am aware of). Request: I would love the ability to specify an arbitrary log file which would get pushed to Splunk so that analysis could be done on the log file. Being able to have a "custom log file" in that dropdown and then adding the location in an additional field would be a great new feature. Add Comment
[JIRA] (JENKINS-55127) Parallel Input stages are not individually selectable in Blue Ocean
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-55127
Parallel Input stages are not individually selectable in Blue Ocean
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-12-11 18:22
Environment:
Jenkins LTS 2.138.x.x BO plugins 1.8.2
Priority:
Minor
Reporter:
Alex Taylor
Issue: I have a pipeline script with parallel steps and each one has its own input that needs to be approved. Those inputs are not individually approvable when selecting their node icons which means I need to approve them all in order from top to bottom for all the stages to move forward Steps to reproduce: Create a new job with the following script
pipeline {
agent none
stages{
stage('Parallel Steps') {
parallel {
stage('BranchA'){
stages{
stage('InputA'){
agent any
input {
message "Should we continue?"
ok "Yes, we should."
}
steps {
echo "Approved A"
}
}
stage('DeployA'){
agent any
steps {
echo "Deploying A"
}
}
}
}
stage('BranchB'){
stages{
stage('InputB'){
[JIRA] (JENKINS-55116) Branch missing BranchJobProperty is unable to fix itself in a Multibranch pipeline
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-55116 Branch missing BranchJobProperty is unable to fix itself in a Multibranch pipeline Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-12-10 22:10 Priority: Minor Reporter: Alex Taylor Issue: If a job somehow loses its BranchJobProperty in its config.xml via adjusting properties or something similar, it is unable to recover without massive manual intervention Steps to reproduce: 1. Create a multibranch job with at least one branch containing a Jenkinsfile 2. Do a branch indexing event on that multibranch job 3. Edit the config.xml to remove the BranchJobProperty 4. Restart Jenkins 5. Observe the branch will no longer show up in the multibranch project and it is unable to be corrected via a branch indexing event Steps to workaround: 1. Completely remove the config.xml on the filesystem 2. Restart Jenkins 3. Re-trigger an indexing event We should most likely handle issues like this more gracefully/automatically Add Comment
[JIRA] (JENKINS-54501) ClassCastException in SonarUtils getPersistentActions
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-54501 ClassCastException in SonarUtils getPersistentActions Issue Type: Bug Assignee: Sonar Team Attachments: build.xml Components: sonar Created: 2018-11-06 21:22 Priority: Minor Reporter: Alex Taylor Issue: When iterating over all the actions within a Jenkins job using this code I hit a ClassCastException because getActions() does not necessarily return a class that can be converted to Action. This happened in particular with hudson.model.ParametersDefinitionProperty when I had a parameter in my build process. This issue is easily reproducible with the attached build.xml Steps to Reproduce: 1. Open up the Sonar plugin code in IDE of your choice 2. Do a mvn hpi:run and create a freestyle job 3. Build said freestyle job 2 times 4. Stop the run and then modify build #2's build.xml file with the attached 5. Restart the hpi:run 6. Observe the class cast error in the logs and the build #2 not show in the UI Expected results: The build.xml would throw other errors(like the sonar not existing) but be able to parse the build.xml Other Notes: I would normally expect the return for getActions() to be actionable items but apparently since it is deprecated the process has changed for what that will return. Additionally the getAllActions() method can not be used since it calls the overwritten createFor() which ends up causing a stackoverflow. There needs to either be a better checking on the getActions or the getActions needs to be replaced and the createFor() method needs to be fixed
[JIRA] (JENKINS-39403) Path separators in nested variables are not being escaped correctly when parsing the property file
Title: Message Title Alex Taylor commented on JENKINS-39403 Re: Path separators in nested variables are not being escaped correctly when parsing the property file I tried a fix in https://github.com/jenkinsci/envinject-plugin/pull/133 so please try it out to see if you see any obvious errors 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-15445) DefaultBuilderDescriptorLister should not check buildstep class for @DataBoundConstructor
Title: Message Title Alex Taylor commented on JENKINS-15445 Re: DefaultBuilderDescriptorLister should not check buildstep class for @DataBoundConstructor Nicolas De Loof This PR does not seem to cause issues with the latest version of Jenkins anymore. Can we get it re-attempted or am I just missing something? 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-45927) CauseOfBlockage of items in Queue is extremely verbose
Title: Message Title
Alex Taylor commented on JENKINS-45927
Re: CauseOfBlockage of items in Queue is extremely verbose
OK there is a way to workaround this issue by installing the Simple Theme Plugin which is to add a Theme Element of `Extra CSS` under `Manage Jenkins> Configre System` which contains the following data:
.build-details {
max-height:100px !important;
overflow: auto !important;
width:100% !important;
}
#tt {
overflow:hidden;max-height:200px;
}
This will restrict any pop up box to a certain size and truncate the rest which stops the UI from being blocked by this popup
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-45927) CauseOfBlockage of items in Queue is extremely verbose
Title: Message Title Alex Taylor commented on JENKINS-45927 Re: CauseOfBlockage of items in Queue is extremely verbose Daniel Beck would it not make more sense to just count the number of agents which do not have the label and then return that number? Then you could find out the names(if needed) from the build console log itself rather than from the hover over in the build queue. 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-53960) Mac agents fail to connect on vSphere plugin
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53960 Mac agents fail to connect on vSphere plugin Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2018-10-09 12:51 Environment: 2.121.x Jenkins LTS Latest vSphere plugin Priority: Minor Reporter: Alex Taylor Issue: I am successfully able to spin up a new agent with vSphere cloud if that agent is either a Linux or Windows machine but if the agent is a Mac agent, it is unable to spin up and connect back to Jenkins It appears to make the wrong API calls from what I can observe but I am not super familiar with how vSphere manages the Mac VMs Add Comment
[JIRA] (JENKINS-53944) Findbugs pulls in a very old Xerces library version
Title: Message Title Alex Taylor commented on JENKINS-53944 Re: Findbugs pulls in a very old Xerces library version https://github.com/jenkinsci/findbugs-plugin/pull/16 to update 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-53944) Findbugs pulls in a very old Xerces library version
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53944 Findbugs pulls in a very old Xerces library version Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 2018-10-08 12:17 Priority: Minor Reporter: Alex Taylor Looking at the pom I can see that the findbugs plugin pulls in 2.9.1 of the xerces library. Is it possible to step this up to a newer version? This caused an issue in the pipeline maven plugin which was difficult to track down. Add Comment
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" @Cyrille Return of the script is: class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl (classLoader:AntClassLoader[/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/cglib-2.2.2.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/analysis-core.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-beanutils-1.8.3.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-digester3-3.2.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-lang3-3.4.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/joda-time-2.9.5.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xml-apis-1.4.01.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/java2html-5.0.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/asm-3.3.1.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar]) -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar class org.apache.xerces.parsers.XIncludeAwareParserConfiguration (classLoader:AntClassLoader[/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/cglib-2.2.2.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/analysis-core.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-beanutils-1.8.3.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-digester3-3.2.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-lang3-3.4.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/joda-time-2.9.5.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xml-apis-1.4.01.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/java2html-5.0.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/asm-3.3.1.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar]) -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar class org.apache.xerces.parsers.XML11Configuration (classLoader:AntClassLoader[/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/cglib-2.2.2.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/groovy-sandbox-1.10.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/commons-beanutils-1.8.3.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/commons-digester3-3.2.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/findbugs.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/library-2.0.4.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/asm-3.3.1.jar]) -> file:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/library-2.0.4.jar Let me know if that helps Add Comment
[JIRA] (JENKINS-53820) If no Server Authentication Token is defined, it will cause builds to fail
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53820 If no Server Authentication Token is defined, it will cause builds to fail Issue Type: Bug Assignee: Sonar Team Components: sonar Created: 2018-09-27 15:19 Environment: Sonar version 2.8.1 Priority: Major Reporter: Alex Taylor Issue: Under `Manage Jenkins > Configure system` if you leave the Server authentication token blank(which you theoretically can do because it says: SonarQube authentication token. Mandatory when anonymous access is disabled) it will cause builds which have sonar configured to fail in a very interesting way. The logs show a Null pointer with this stacktrace: 2018-09-27_08:09:48.63940 SEVERE: #2389 failed to build and we don't even have a listener 2018-09-27_08:09:48.63940 java.lang.NullPointerException 2018-09-27_08:09:48.63940 at hudson.plugins.sonar.SonarBuildWrapper.createLoggerDecorator(SonarBuildWrapper.java:149) 2018-09-27_08:09:48.63941 at jenkins.tasks.SimpleBuildWrapper.decorateLogger(SimpleBuildWrapper.java:192) 2018-09-27_08:09:48.63941 at hudson.model.Run.createBuildListener(Run.java:1827) 2018-09-27_08:09:48.63941 at hudson.model.Run.execute(Run.java:1708) 2018-09-27_08:09:48.63941 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) 2018-09-27_08:09:48.63942 at hudson.model.ResourceController.execute(ResourceController.java:97) 2018-09-27_08:09:48.63942 at hudson.model.Executor.run(Executor.java:429) But does not show a build
[JIRA] (JENKINS-53790) Kubernetes plugin shows failing templates to only admins
Title: Message Title
Alex Taylor commented on JENKINS-53790
Re: Kubernetes plugin shows failing templates to only admins
Right now the only workaround is to do some strange-ness within a pipeline where you create a pipeline and parallel the template along with a groovy script(In my case I included it within a global shared library). So here are the steps I used: 1. Create a system log called "Kubernetes Log" with the `org.csanchez.jenkins.plugins.kubernetes` logger set to ALL 2. Create a pipeline job with a parallel statement which runs the template and loops through the following script until the template spins up:
import java.util.logging.Level
import java.util.logging.Logger
import hudson.logging.LogRecorderManager
import hudson.logging.LogRecorder
import java.util.logging.LogRecord
import hudson.util.RingBufferLogHandler;
def AgentName= searchString
List records = new ArrayList();
//Grabs the log manager
LogRecorderManager mgr = Jenkins.instance.getLog();
//Grabs the records
mgr.logRecorders.each{
if (it.getValue().getName() == "KubernetesLog")
{
records = it.getValue().getLogRecords()
}
}
//Iterates over the record messages looking for the agent name
for (LogRecord r : records) {
if (r.getMessage().contains(AgentName)){
println(r.getMessage().toString())
}
}
//Clears the logger
mgr.logRecorders.each{
if (it.getValue().getName() == "KubernetesLog")
{
it.getValue().doClear()
}
}
This will show the messages relating to `searchString` which should be the name of your template.
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
[JIRA] (JENKINS-53790) Kubernetes plugin shows failing templates to only admins
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53790 Kubernetes plugin shows failing templates to only admins Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-09-26 13:22 Priority: Major Reporter: Alex Taylor Background: With the advent of CJE2/Core on modern platforms, we started leveraging the Kubernetes plugin to define agents using kubernetes templates. This is a great new feature but allows non admins to generate new templates even within their pipelines. But since these non admins do not have access to the Kubernetes back end or the logging within Jenkins, they do not see when or why one of these templates fails Issue: When a non-admin user creates a k8s template which is badly formed they are unable to see that the container/pod is failing because it is just "waiting on $LABEL" Steps to reproduce: Create a pipeline job Create a template in that job with a badly defined docker image name Watch the job fail to start because it can not find its label If you are not an admin you can not see why the container/pod is failing to start because you can not access the k8s logs or the `Manage Jenkins> System Log` area of Jenkins to create a custom logger and see the cause for failure Resolution: We need a way in the job or similar to see why the container is failing to start, perhaps just a return code from Kubernetes. Or we need to not allow them to define templates on a job level so that non-admins can not create templates at all.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title
Alex Taylor updated an issue
Jenkins / JENKINS-51404
processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Change By:
Alex Taylor
Comment:
[~cleclerc] The output was this:{code:java}class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar{code}Sorry for not giving this earlier!
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-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Cyrille Le Clerc The output was this: class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar Sorry for not giving this earlier! 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-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Alex Taylor assigned an issue to Mark Waite Jenkins / JENKINS-20427 Build Parameter variable in branch name causes polling to detect false changes in GIT Change By: Alex Taylor Assignee: Nicolas De Loof Mark Waite 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-53326) SCM checkout needs to be able to refresh the checkout details
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53326 SCM checkout needs to be able to refresh the checkout details Issue Type: Improvement Assignee: Unassigned Components: workflow-scm-step-plugin Created: 2018-08-29 15:52 Priority: Minor Reporter: Alex Taylor Issue: I have a job where I am doing a simple checkout in a pipeline where I then make a modification to the git repo and push the update. This ends up causing a new build to be launched from either a webhook or polling event but it is a known good push done within the build process. Resolution: If there was a way to push which commitID the repo is associated with by doing something like a SCMrefresh step in a pipeline, it would help a new build not be triggered. I could stage the git commit locally to the workspace, update the commitID the job is "building", and then do the push which would stop a new build from triggering. This is especially useful for things like releases which a new build being triggered does not really make sense since all that was pushed is a new version number. Add Comment
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Mark Waite Yeah I think the setsid is probably affecting me because I am running Jenkins from the terminal. But my question would be how do I go about adding setsid on a master? I could normally add it onto the prefix to the agent but if I am doing a checkout on master then how would I add it? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Devin Nusbaumsorry missed this. I used ssh with private key when I did my test. That is interesting about the setsid but I was not actually doing this checkout on an agent and was instead doing it on the master. Did you guys run it on the master as well? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Mark WaiteDevin Nusbaum This is MacOS and I see the same behavior as the customer who was running on windows >Are you using a passphrase which includes a character that is special to the shell Password was `testing` in my case I have not tried in Linux yet but I can certainly do it if you like. Could I attach a bundle of my instance where I reproduced so you can spin up a copy? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53134 Git checkout fails when using an SSH key with a passphrase Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-08-20 13:58 Environment: Jenkins core 2.121.2 and 2.107.x Git Plugin latest Git api latest Priority: Major Reporter: Alex Taylor Issue: A checkout from the master can not be performed when using a ssh key with a passphrase. It will hang on this step: > git fetch --tags --progress g...@github.com:alexanderrtaylor/support-kb-articles.git +refs/heads/*:refs/remotes/origin/* And eventually fail. Workaround: You can remove the passphrase and it will work normally Steps to reproduce: 1. Create a SSH key with a specific passphrase like `testing` and add it to Jenkins 2. Add ssh key to github 3. Create a job(freestyle or pipeline the behavior is the same) 4. Use the SSH key connect to the ssh location of the git url 5. Watch as the job fails. This works normally if I use a shell step to clone from the agent but the git plugin seems to be causing the issue
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Cyrille Le Clerc Did you get the chance to look at this further? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Alex Taylor commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis Thanks for the update Gabriel Stanek just wanted make sure I was understanding everyone's issue and how best I can fix it Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52943) Blue Ocean view does not show descriptions for shell steps with `returnStdout: true`
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-52943
Blue Ocean view does not show descriptions for shell steps with `returnStdout: true`
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-08-08 18:51
Environment:
Blue Ocean version 1.7.0
Priority:
Minor
Reporter:
Alex Taylor
Issue: When you have a shell step with either returnStdout or returnStatus being "true", the step does not show a preview like when those are not set to "true". Steps to Reproduce: Create a simple pipeline with the following definition:
node('master'){
sh 'echo "hello"'
sh returnStdout: true, script: 'echo "hello"'
sh returnStatus: true, script: 'echo "hello"'
}
And run the pipeline. Then look at it in Blue Ocean view and see that the first one has a description but the others do not.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Alex Taylor commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis I was looking into this issue and it appears that the Jacoco plugin fixed this issue for ENV variables with https://github.com/jenkinsci/jacoco-plugin/pull/74 but it does not actually parse the pom.xml for the `excludes`(or `includes` for that matter) configuration. Does that sound like the actual issue here rather than the Excludes not working at all? Did I miss anything here? I was going to work on getting this fixed with a PR hopefully within the next week Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Cyrille Le Clerc The response was: class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar So it does not seem too outdated(only 1 version back from what I can see). Should that be updated first? 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-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-51404 processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-05-17 17:00 Environment: Jenkins Core 2.107.x Maven-pipeline 3.5.6 Priority: Minor Reporter: Alex Taylor Issue: When running a maven process inside of a build an error popped up saying java.lang.IllegalAccessError: tried to access method org.apache.xerces.parsers.XML11Configuration.getFeature0(Ljava/lang/String;)Z from class org.apache.xerces.parsers.XIncludeAwareParserConfiguration at org.apache.xerces.parsers.XIncludeAwareParserConfiguration.getFeature(Unknown Source) at org.apache.xerces.parsers.AbstractDOMParser.reset(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:97) at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050) It seems to come from the code here:
[JIRA] (JENKINS-51146) Github Branch Source does not allow `#` character within branch names
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-51146 Github Branch Source does not allow `#` character within branch names Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-05-04 20:11 Environment: Jenkins core at least 2.73.x LTS Github Branch source 2.3.0 Priority: Minor Reporter: Alex Taylor Something happened within the update of Github branch source plugin 2.3.0 update when combined with the update to Jenkins core 2.73.x where when you have a branch with a # character in the name it will not be able to find the branch name. Steps to recreate: Create a shared library with a branch name "Branch#Test" Attach that shared library to a Jenkins instance as a global library using the github modern SCM Create a job which loads the branch by doing @Library(SharedLibrary@Branch#Test) observe the job fails with No version Branch#Test found for library GithubLibrary This issue only happens when you update the github branch source plugin to newer than 2.3.0 and have a current version of core(from my testing) which means something in the 2.3.0 release changed this behavior. Let me know if I can provide more information
[JIRA] (JENKINS-50995) Credentials scoped at a folder level return `Null` when used in a checkmarx build step
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50995 Credentials scoped at a folder level return `Null` when used in a checkmarx build step Issue Type: Bug Assignee: Sergey Kadaner Components: checkmarx-plugin Created: 2018-04-25 12:40 Priority: Major Reporter: Alex Taylor Issue: When you create a credential at a folder level and try to use it during a build with a checkmarx build step, the credential returns `null` value which fails to give access. Steps to reproduce: Create username/password combination which only exists at a folder level Create freestyle build with a checkmarx build step requiring authentication inside of that folder Choose that folder scoped username/password at the job level Run the build and check the checkmarx logs Observe that `Anonymous` is trying to get access rather than the username/password combination Workaround: You can scope the credentials at the global level and this will work 100% fine I did see another JIRA which was having the same issue and it was resolved with [this PR|https://github.com/jenkinsci/pipeline-aws-plugin/pull/16]. Maybe there is something helpful you can get there? It looks like the credentials plugin dependency was bumped to a newer version which is not included in checkmarx
[JIRA] (JENKINS-47933) If Credentials are defined at a folder level, the Maven Artifact ChoiceListProvider plugin does not use them
Title: Message Title Alex Taylor commented on JENKINS-47933 Re: If Credentials are defined at a folder level, the Maven Artifact ChoiceListProvider plugin does not use them Stephan Watermeyer I was looking at other plugins that has this issue and found this PR which seems to iterate correctly. Maybe it is the included credentials plugin in your POM or the actual call you are making? Unfortunately that is for a pipeline step rather than a freestyle one but it may help. Otherwise I am not seeing anyone else who made the change. Any ideas Jesse Glick? 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-35269) Job configuration UI Layout is broken
Title: Message Title Alex Taylor commented on JENKINS-35269 Re: Job configuration UI Layout is broken Manuel Recena Soto Any ideas on the future PRs for this issue? 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-50509) Docker Traceability plugin is affected by JEP-200
Title: Message Title Alex Taylor commented on JENKINS-50509 Re: Docker Traceability plugin is affected by JEP-200 Oleg Nenashev So then I should add a whitelist similar to https://github.com/jenkinsci/docker-plugin/pull/619/files and add the InspectContainerResponse to it? 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-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Alex Taylor reopened an issue See my last comment since I think it is still an issue Jenkins / JENKINS-20427 Build Parameter variable in branch name causes polling to detect false changes in GIT Change By: Alex Taylor Resolution: Fixed Status: Closed Reopened 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,
[JIRA] (JENKINS-50498) Invalid Object ID in remoting module related to Proxy methods
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50498 Invalid Object ID in remoting module related to Proxy methods Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2018-03-30 16:08 Environment: Remoting 3.14 Priority: Minor Reporter: Alex Taylor Exactly the same as https://issues.jenkins-ci.org/browse/JENKINS-23271 but with a slightly different stacktrace: 2018-03-27 13:08:51.899+ [id=4840845] SEVERE hudson.remoting.ExportTable#unexportByOid: Trying to unexport an object that's already unexported java.lang.Exception: Object appears to be deallocated at lease before Tue Mar 27 07:59:42 CDT 2018 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:474) Caused: java.util.concurrent.ExecutionException: Invalid object ID 19 iota=20 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:478) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:516) at hudson.remoting.Channel.unexport(Channel.java:756) at hudson.remoting.Channel.unexport(Channel.java:746) at hudson.remoting.ProxyOutputStream$Unexport$1.run(ProxyOutputStream.java:345) at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at
[JIRA] (JENKINS-50497) Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list
Title: Message Title Alex Taylor commented on JENKINS-50497 Re: Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list Added a permissions matrix which includes Job Promote permission but there is no other "promote" permissions other than artifact promote: Screen Shot 2018-03-30 at 12.02.06 PM.png Admin user button: Screen Shot 2018-03-30 at 12.03.04 PM.png Dev user no button: Screen Shot 2018-03-30 at 12.03.39 PM.png Sorry for not adding that earlier 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-50497) Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-50497 Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list Change By: Alex Taylor Attachment: Screen Shot 2018-03-30 at 12.03.39 PM.png Attachment: Screen Shot 2018-03-30 at 12.03.04 PM.png Attachment: Screen Shot 2018-03-30 at 12.02.06 PM.png 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-50497) Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50497 Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list Issue Type: Bug Assignee: Devin Nusbaum Components: promoted-builds-plugin Created: 2018-03-30 15:48 Environment: Jenkins Core 2.107.x Promoted builds 3.0 + 3.1 Priority: Major Reporter: Alex Taylor Issue: When a user has full job permissions(build, create, promote) on Jenkins but not Overall Admin access, they can not manually promote a job using the button. Steps to reproduce: Spawn up a new Jenkins instance with 2 users: Admin(full admin permissions), Developer(full job permissions and overall read) and the promoted builds plugin installed Create a new job with a manual promotion process having no "Approvers" list Build the Job Observe that Admin can promote the build but Developer does not have access to the button to promote Workaround: Adding the Developer user to the list of approvers makes the button show up Expected Behavior: I would expect the Developer user to also have access to the promotion process since they have job promote permission Let me know if I can clarify anything
[JIRA] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Alex Taylor commented on JENKINS-20427 Re: Build Parameter variable in branch name causes polling to detect false changes in GIT Mark Waite- I was finally able to reproduce this issue 100% if you have access to bitbucket. 1. Have Bitbucket repository with at least 10 branches 2. Create a freestyle job and configure it to use the git plugin but connect to a Bitbucket repository at `$BITBUCKET_URL/git/$PROJECT/$REPO.git` 3. Add a parameter called BRANCH and has the default value of ** 4. Use that parameter in the `Branches to build` section 5. Add a poll for changes of `* * * * *` so that it will build every minute 6. Add a shell step of something like "echo hello" 7. Run one build This will then launch a new build for every branch and then once that is done you will see it build every minute seeing changes. Let me know if that does not work for you because it has worked 2x for me so far. 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-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor closed an issue as Duplicate Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Change By: Alex Taylor Status: Open Closed Resolution: Duplicate 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-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Change By: Alex Taylor Issue Type: Bug New Feature 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-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Change By: Alex Taylor Attachment: image001.png 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-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Issue Type: Bug Assignee: Unassigned Attachments: image001.png Components: blueocean-plugin Created: 2018-03-26 13:43 Priority: Minor Reporter: Alex Taylor Problem: When a pipeline builds a downstream job, there is not an easy way inside of blue ocean to navigate to that job(you have to go to the console log of the build and then click the downstream build link) Idea: It would be great if we could have a link in the pipeline flow UI(see attached) where the build link would either be clickable or there would be a new sub arrow which would give the downstream build links. Add Comment
[JIRA] (JENKINS-50326) Parameters with the same name as ENV variables overwrite the existing ENV variables
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50326 Parameters with the same name as ENV variables overwrite the existing ENV variables Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-03-21 19:32 Priority: Trivial Reporter: Alex Taylor When you have an existing ENV variable and then have a build with a parameter of the same name(even if different case) it will overwrite the ENV variable. Reproduction case: Create a global ENV variable called "FOO" and set it to "BAR" Create a test job "TestJob" Add a string parameter called "foo" to the job create a shell step to echo out the value of $FOO Run the job with TEST as the value of foo Observe that the output of the shell step is "TEST" instead of "BAR" Resolution: Personally I think freestyle jobs should call out if you want an ENV or parameter much like pipeline scripts do with the $param.VARIABLE. This will avoid the confusion entirely. Add Comment
[JIRA] (JENKINS-50222) Maven Metadata plugin does not iterate over credentials in folders
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50222 Maven Metadata plugin does not iterate over credentials in folders Issue Type: Bug Assignee: Gesh Markov Components: maven-metadata-plugin Created: 2018-03-16 15:44 Priority: Major Reporter: Alex Taylor When using the Maven Metadata plugin, it does not pull credentials which are configured on folders and will only pull global credentials. An example resolved similar issue is https://issues.jenkins-ci.org/browse/JENKINS-34825 but that is on the P4 plugin Add Comment
[JIRA] (JENKINS-49893) Declarative directive snippet generator
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-49893 Declarative directive snippet generator Change By: Alex Taylor Attachment: Screen Shot 2018-03-15 at 4.59.02 PM.png 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-49893) Declarative directive snippet generator
Title: Message Title Alex Taylor commented on JENKINS-49893 Re: Declarative directive snippet generator Andrew Bayer One other suggestion towards this issue would be to not have required "generated code" but maybe have inline help for the basics of the generation much like the Parallel step inside of the current Snippet Generator 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-50200) Label accepts 2 groovy variables when using && but not || operator
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-50200
Label accepts 2 groovy variables when using && but not || operator
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-03-15 17:20
Priority:
Minor
Reporter:
Alex Taylor
When running a pipeline, the label expects a string with the option of an operator. Apparently the && operator with 2 groovy variables will evaluate correctly but not a || operator. So this pipeline runs correctly:
def groovyLabel1 = 'master'
def groovyLabel2 = 'TestAgent'
node(groovyLabel1 && groovyLabel2){
echo "hello"
}
But this code does not run correctly:
def groovyLabel1 = 'master'
def groovyLabel2 = 'TestAgent'
node(groovyLabel1 || groovyLabel2){
echo "hello"
}
because it fails with this error:
java.lang.ClassCastException: org.jenkinsci.plugins.workflow.support.steps.ExecutorStep.label expects class java.lang.String but received class java.lang.Boolean
I think that groovy is doing some funky parsing here and causing the error because what should be the only thing allowed would be something
[JIRA] (JENKINS-49701) Would like a new section of the Script security approval page to be "pending scripts from Disabled Jobs"
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-49701 Would like a new section of the Script security approval page to be "pending scripts from Disabled Jobs" Issue Type: New Feature Assignee: Andrew Bayer Components: script-security-plugin Created: 2018-02-22 17:15 Priority: Minor Reporter: Alex Taylor Request: Create a new section inside of the "In Process Script Approval" screen which shows pending approvals which are coming from disabled jobs Reasoning: There are some situations where you want to deny some scripts where developers are potentially doing bad things. But when Jenkins is restarted, those denied scripts come back to the "In Process Script Approval" screen which is annoying. It would be great to have a way to isolate those scripts which are not being fixed by developers. This could be accomplished by disabling their projects and then being able to sort their scripts so that new scripts waiting on approval are not lumped in with the bad ones on restart. Implementation: `ScriptApproval/index.jelly` could perhaps show a special UI for `PendingThing`s whose `context` has an `item` which is in fact a `disabled` `Job`. So this would mean creating a new UI box and putting scripts into it with the disabled job flag. Thoughts?
[JIRA] (JENKINS-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Alex Taylor commented on JENKINS-47321 Re: Quality Gates Sonarqube: projectKey Illegal character Ivana Sh Eleni Grozdani Dimitar Pop Dimitrov We had this issue on the wrong component(we thought it was the Sonar quality gates plugin). Would it be possible to take a look at https://github.com/jenkinsci/quality-gates-plugin/pull/57 and then potentially merge it? Seems like a quick win 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-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Alex Taylor reopened an issue Jenkins / JENKINS-47321 Quality Gates Sonarqube: projectKey Illegal character Change By: Alex Taylor Resolution: Won't Do Status: Closed Reopened Assignee: Rafael Ramos Ivana Sh 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-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-47321 Quality Gates Sonarqube: projectKey Illegal character Change By: Alex Taylor Component/s: quality-gates-plugin Component/s: sonar-quality-gates-plugin 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-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Alex Taylor commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Jesse Glick, so I have a decently reproducible case for a freestyle job as well where docker-commons needs to be updated(either with the CLI or with changing the .dockercfg file). It seems that with the 1.12 version of docker they changed the file which is needed to log you in from ~/.dockercfg to ~/.docker/config.json which means that it will not see your credentials. So if you have a Private repo in dockerhub it will not log you in properly. Environment: Jenkins 2.32.3(but I think jenkins version is irrelevant) Docker-commons: 1.6 Docker version 1.12 on the machine running the job Docker build and publish:1.3.2 Steps to reproduce: Have a freestyle job Have a private dockerhub repository Have a step which is building a docker container and pushing it to that private dockerhub repo Behavior: It fails with a unauthenticated error because the ~/.dockercfg file no longer works. The docker build and publish step leverages the docker commons plugin to log into private repos so this is a good case to see the failure. Expected Behavior It would upload the docker container to your repo Workaround: If you log into that dockerhub repo through the CLI in a shell step before the build and publish step, it will create a ~/.docker/config.json file which will retain your credentials until the end of the build. Then the build and publish will work normally So I suppose we could potentially create both files as a temporary fix until we move to the CLI? What are your thoughts guys? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-33527) Intermittent exception thrown when using plugin
Title: Message Title Alex Taylor commented on JENKINS-33527 Re: Intermittent exception thrown when using plugin Lev Mishin So I was unable to reproduce locally but I may not have the scale to reproduce consistently. I wanted to see if other people could test it out. Otherwise it is a pretty simple change so I very much doubt it will cause issues. 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-33527) Intermittent exception thrown when using plugin
Title: Message Title Alex Taylor commented on JENKINS-33527 Re: Intermittent exception thrown when using plugin Try out this PR to see if it solves the serializable issue 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.
