[JIRA] (JENKINS-54529) CAN NOT get build number with jenkins API
Title: Message Title Daniel Beck closed an issue as Cannot Reproduce Any differences in output can be explained by either of the following: Time differences. While something is waiting in the queue, it does not yet have a corresponding build, or build number. Only once it starts building this changes. Authentication. If you're not allowed to see the build, the API for its queue item will not be displayed. Jenkins / JENKINS-54529 CAN NOT get build number with jenkins API Change By: Daniel Beck Status: Open Closed Resolution: Cannot Reproduce 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-54513) Builds occupying executor but not running
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-54513 Builds occupying executor but not running Change By: Daniel Beck Component/s: pipeline Component/s: core 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-39838) CHANGE_ variables are missing
Title: Message Title Barathwaja S commented on JENKINS-39838 Re: CHANGE_ variables are missing Is there any progress on this? Need some of the above env. variables to be used in a project. Any ETA on this? Ref. https://issues.jenkins-ci.org/browse/JENKINS-40486 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-40486) Plugin does not adhere to documented global variables
Title: Message Title Barathwaja S commented on JENKINS-40486 Re: Plugin does not adhere to documented global variables Is there any progress on this? Need some of the above env. variables to be used in a project. Any ETA on this? 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-39838) CHANGE_ variables are missing
Title: Message Title Barathwaja S edited a comment on JENKINS-39838 Re: CHANGE_ variables are missing Is there any progress on this? Need some of the above env. variables to be used in a project. Any ETA on this? Ref. [ JENKINS-40486| https://issues.jenkins-ci.org/browse/JENKINS-40486 |JENKINS-40486 ] 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-54512) can not change workspace in k8s pipeline
Title: Message Title David Currie commented on JENKINS-54512 Re: can not change workspace in k8s pipeline Why not just change your GOPATH then? 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-54512) can not change workspace in k8s pipeline
Title: Message Title runze xia commented on JENKINS-54512 Re: can not change workspace in k8s pipeline Changing the GOPATH is working, but it would be better if you could change the working directory at will in the k8s agent. 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-54537) Scripted Pipeline does not work due to tags
Title: Message Title
Cédric SARRE created an issue
Jenkins / JENKINS-54537
Scripted Pipeline does not work due to tags
Issue Type:
Bug
Assignee:
Vincent Behar
Components:
rundeck-plugin
Created:
2018-11-08 09:30
Environment:
Jenkins V2.138 Rundeck V2.9.3-1 Rundeck-plugin V3.6.4
Labels:
pipeline regression
Priority:
Major
Reporter:
Cédric SARRE
Hello, There is bug in the constructor of RundeckNotifier. When we declare a scripted pipeline like below, we get this exception "Caused by: java.lang.ClassCastException: org.jenkinsci.plugins.rundeck.RundeckNotifier.tags expects class java.lang.String but received class java.util.ArrayList".
stage('Deploy Release') {
steps {
script {
step([$class: "RundeckNotifier",
includeRundeckLogs: true,
jobId: "1",
rundeckInstance: "rundeck",
shouldFailTheBuild: true,
shouldWaitForRundeckJob: true,
tailLog: true])
}
}
}
}
In RundeckNotifier class, the constructor annotated by "@DataBoundConstructor" contains a parameter called "tags". Jenkins Structs plugin get the name of fields that can be declared in the pipeline thanks to this constructor and after the plugin get the type of fields declared as attribute of class. Two
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Hey guys, this seems to be still a problem with latest LTS Jenkins, I have Jenkins on Windows with a slave. I have used starting parameter as -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=2 works well on master, however builds on Node is still creating %2F folder which is breaking all the MSBuild projects Folder on Master: Folder on Slaves: Jenkins Version: Jenkins ver. 2.138.2 Branch API version: 2.0.20 Is there some specific configuration for slaves? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Hey guys, this seems to be still a problem with latest LTS Jenkins, I have Jenkins on Windows with a slave. I have used starting parameter as -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=2 works well on master, however builds on Node is still creating %2F folder which is breaking all the MSBuild projects Folder on Master:!image-2018-11-08-11-41-20-416.png|width=798,height=163! Folder on Slaves:!image-2018-11-08-11-41-54-437.png|width=785,height=184! Jenkins Version: [Jenkins ver. 2.138.2|https://jenkins.io/]Branch API version: [ 2.0.20 |https://jenkins.liveoptics-uat.com/pluginManager/plugin/branch-api/thirdPartyLicenses] Is there some specific configuration for slaves? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar reopened an issue Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Uma Shankar Resolution: Fixed Status: Resolved Reopened 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-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Baptiste Mathus updated JENKINS-49196 Jenkins / JENKINS-49196 java.io.IOException: Premature EOF when shutdown CLI command is used Change By: Baptiste Mathus Status: Fixed but Unreleased Reopened 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-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Baptiste Mathus started work on JENKINS-49196 Change By: Baptiste Mathus Resolution: Fixed Status: Reopened 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-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Baptiste Mathus updated JENKINS-49196 Jenkins / JENKINS-49196 java.io.IOException: Premature EOF when shutdown CLI command is used Change By: Baptiste Mathus 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-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Baptiste Mathus updated JENKINS-49196 Merged towards 2.151 Jenkins / JENKINS-49196 java.io.IOException: Premature EOF when shutdown CLI command is used Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed 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-53094) Option to expand variables in yamlFile
Title: Message Title Oleg Gumbar commented on JENKINS-53094 Re: Option to expand variables in yamlFile Agreed. Plugin is quite useless for some advanced cases without this feature. My case is I use complex kilometer yaml templates with separate docker images for each commit for tests in parallel. I wouldn't like to include 5kb yaml in each parallel step, instead of this I would like to inject env vars I need in target yaml file for each parallel step. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar updated an issue Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Uma Shankar Attachment: image-2018-11-08-11-41-20-416.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar updated an issue Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Uma Shankar Attachment: image-2018-11-08-11-41-54-437.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-49196 java.io.IOException: Premature EOF when shutdown CLI command is used Change By: Baptiste Mathus Labels: lts-candidate 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-54540) Pods stuck in error state
Title: Message Title
Daniel Watrous created an issue
Jenkins / JENKINS-54540
Pods stuck in error state
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
build-job-console-output.txt, jnlp-container-log-error.txt, jnlp-container-log-healthy.txt
Components:
kubernetes-plugin
Created:
2018-11-08 12:10
Environment:
I am running Jenkins in kubernetes with the kubernetes plugin. Versions as follows ~ # kubectl version Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:00:59Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"} Jenkins ver. 2.138.2 from https://hub.docker.com/r/jenkins/jenkins/ [centos@k8s-master-0 ~]$ sudo docker version Client: Version: 17.03.2-ce API version: 1.27 Go version: go1.7.5 Git commit: f5ec1e2 Built: Tue Jun 27 02:21:36 2017 OS/Arch: linux/amd64 Server: Version: 17.03.2-ce API version: 1.27 (minimum version 1.12) Go version: go1.7.5 Git commit: f5ec1e2 Built: Tue Jun 27 02:21:36 2017 OS/Arch: linux/amd64 Experimental: false
Labels:
jenkins kuberenetes-plugin kuberentes jnlp-slave jnlp plugin
Priority:
Minor
Reporter:
Daniel Watrous
[JIRA] (JENKINS-22547) Git timeout setting does not work for checkout
Title: Message Title Yarden Bar commented on JENKINS-22547 Re: Git timeout setting does not work for checkout Hi, We encountered this timeout as well, but we suspect that the git config core.sparsecheckout with out explicit true argument causes this. Adding the CloneOption with timeout didn't help in our case. Is there a way to configure git config core.sparsecheckout true in the checkout step? I've read the documentation but coudn't figure out how to do so... Thank you, Yarden 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-54541) Unreserve doesn't set environment variable
Title: Message Title Steven Foster created an issue Jenkins / JENKINS-54541 Unreserve doesn't set environment variable Issue Type: Bug Assignee: Unassigned Components: lockable-resources-plugin Created: 2018-11-08 12:23 Environment: lockable-resources 2.3 Priority: Major Reporter: Steven Foster The manual reserve feature doesn't work well with the pipeline variable feature. When a user unreserves a resource and the plugin assigns the resource immediately to a queued build, the environment variable won't be correctly set. In LockableResourceManager.unreserve, there is a LockStepExecution.proceed call at the end with the variable left null. I have no idea how to retrieve a singular variable to use at this point in the code. Add Comment
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title
Michael Zeitz edited a comment on JENKINS-50867
Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
We ran into similar issue.{noformat}...Caused by: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at org.springframework.oxm.jaxb.Jaxb2Marshaller.loadSchema(Jaxb2Marshaller.java:554) at org.springframework.oxm.jaxb.Jaxb2Marshaller.afterPropertiesSet(Jaxb2Marshaller.java:458) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624) ... 91 moreCaused by: java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228) ... 96 mor{noformat}In use is/was Jenkins 2.138.2 with Maven Integration Plugin 3.1.2 (and others).We updated/changed the maven plugin org.mortbay.jetty:jetty-maven-plugin:8.1.15.v20140411 to the new plugin org.eclipse.jetty:jetty-maven-plugin:9.4.12.v20180830 and then the issue occured. (on unix slave)The above mentioned workaround "-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser" works for us. I have to *revoke* as I registered there were more differences.In the _older_ jetty plugin we had this in area defined: {noformat} ... org.xml.sax.driver com.sun.org.apache.xerces.internal.parsers.SAXParser...{noformat}which wasn't used any more because the groupId of the plugin changed. So, the problem we had is not related to jetty plugin change - it's more a configurational topic.I'l let my comment here - maybe the information about jetty plugin configuration possibility to fix the problem is helpful for someone.
Add Comment
[JIRA] (JENKINS-54524) Improper Encoding of Sync Status
Title: Message Title Tim Foster commented on JENKINS-54524 Re: Improper Encoding of Sync Status Turns out I did save a copy of the HTML in question: SCM Sync status : Tue Nov 06 04:07:06 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Tue Nov 06 04:07:14 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Tue Nov 06 04:08:34 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Tue Nov 06 04:08:42 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Wed Nov 07 20:28:19 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Wed Nov 07 20:28:26 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/br/To remove this message, please a href='' _onclick_='_javascript_:removeLog();'click here/a I needed to edit the DOM and replace all the > and < with > and <. 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-54524) Improper Encoding of Sync Status
Title: Message Title
Tim Foster edited a comment on JENKINS-54524
Re: Improper Encoding of Sync Status
Turns out I did save a copy of the HTML in question:{noformat}SCM Sync status : < br > Tue Nov 06 04:07:06 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Tue Nov 06 04:07:14 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Tue Nov 06 04:08:34 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Tue Nov 06 04:08:42 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Wed Nov 07 20:28:19 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/Wed Nov 07 20:28:26 GMT 2018 : Checkout /var/lib/jenkins/scm-sync-configuration/checkoutConfigurationbr/br/To remove this message, please a href='' _onclick_='_javascript_:removeLog();'click here/a{noformat}I needed to edit the DOM and replace all the> and< with > and <.
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-45038) Add "Recurse in subfolders" option to sectioned view plugin
Title: Message Title Vitalii Petkanych commented on JENKINS-45038 Re: Add "Recurse in subfolders" option to sectioned view plugin Any progress here? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22547) Git timeout setting does not work for checkout
Title: Message Title Mark Waite commented on JENKINS-22547 Re: Git timeout setting does not work for checkout Yarden Bar it is generally considered bad form to ask an unrelated question in a bug report. It clutters the bug reports and wastes the time of maintainers that are notified when the unrelated comment is added to the bug report. Please don't do that in the future. Use the mailing list or chat questions and answers so that more than a few people are notified and might be able to assist. The question interested me enough that I added it to my JENKINS-52746 test case. Refer to that example for details that will allow you to use a sparse checkout path definition in a declarative Pipeline checkout statement. If you are using declarative Pipeline, you may also need to `skipDefaultCheckout(true)` in the options section, otherwise the full repository checkout happens implicitly before the first step. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title
Michael Zeitz edited a comment on JENKINS-50867
Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
We ran into similar issue.{noformat}...Caused by: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at org.springframework.oxm.jaxb.Jaxb2Marshaller.loadSchema(Jaxb2Marshaller.java:554) at org.springframework.oxm.jaxb.Jaxb2Marshaller.afterPropertiesSet(Jaxb2Marshaller.java:458) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624) ... 91 moreCaused by: java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228) ... 96 mor{noformat}In use is/was Jenkins 2.138.2 with Maven Integration Plugin 3.1.2 (and others).We updated/changed the maven plugin org.mortbay.jetty:jetty-maven-plugin:8.1.15.v20140411 to the new plugin org.eclipse.jetty:jetty-maven-plugin:9.4.12.v20180830 and then the issue occured. (on unix slave)The above mentioned workaround "-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser" works for us. I have to *revoke* as I registered there were more differences.In the _older_ jetty plugin we had this in area defined:{noformat} ... org.xml.sax.driver com.sun.org.apache.xerces.internal.parsers.SAXParser...{noformat}which wasn't used any more because the groupId of the plugin changed. So, the problem we had is not related to jetty plugin change - it's more a configurational topic.I' l ll let my comment here - maybe the information about jetty plugin configuration possibility to fix the problem is helpful for someone.
Add Comment
[JIRA] (JENKINS-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-49196 java.io.IOException: Premature EOF when shutdown CLI command is used Change By: Baptiste Mathus Released As: (towards) 2.151 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-27177) There should be a command line mechanism to disable plugins
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-27177 There should be a command line mechanism to disable plugins Change By: Baptiste Mathus Released As: (towards) 2.151 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-53558) Apply top level failFast option to all parallel stages inside Jenkinsfile.
Title: Message Title Andrew Bayer commented on JENKINS-53558 Re: Apply top level failFast option to all parallel stages inside Jenkinsfile. I'd say the way to do this would be to have a top level-only option called something like parallelAlwaysFailsFast, and if it's set and there isn't an explicit failFast setting on a parallel block, we would make every parallel within the pipeline fail fast. 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-54536) Support T3 instance types
Title: Message Title Janos Feher started work on JENKINS-54536 Change By: Janos Feher 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-54536) Support T3 instance types
Title: Message Title Janos Feher created an issue Jenkins / JENKINS-54536 Support T3 instance types Issue Type: Improvement Assignee: Janos Feher Components: ec2-plugin Created: 2018-11-08 09:09 Labels: plugin Priority: Minor Reporter: Janos Feher There is a new T3 EC2 instance type class, which is not supported by the plugin. This ticket adds support for T3 Nano T3 Micro T3 Small T3 Medium T3 Large T3 XLarge T3 2XLarge A PR has been created, but requires to upload the AWS Java SDK version 1.11.445 on https://repo.azure.jenkins.io/incrementals/org/jenkins-ci/plugins/aws-java-sdk/ classes.
[JIRA] (JENKINS-54536) Support T3 instance types
Title: Message Title Janos Feher updated JENKINS-54536 Jenkins / JENKINS-54536 Support T3 instance types Change By: Janos Feher 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-54538) Ability to save unmasked credentials to file
Title: Message Title Tomasz Fijarczyk created an issue Jenkins / JENKINS-54538 Ability to save unmasked credentials to file Issue Type: Bug Assignee: Unassigned Components: credentials-binding-plugin Created: 2018-11-08 11:06 Environment: Jenkins 2.149 - Credential Binding 1.17 Priority: Major Reporter: Tomasz Fijarczyk It looks like saving password variable from withCredentials using writeFile doesn't mask the password. I consider this to be a security vulnerability. Add Comment
[JIRA] (JENKINS-54539) REST API to generate API tokens
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-54539 REST API to generate API tokens Issue Type: New Feature Assignee: Antonio Muñiz Components: core Created: 2018-11-08 11:07 Priority: Minor Reporter: Antonio Muñiz As part of the installation procedure, Jenkins X needs to be able to get the API token for the default (admin) Jenkins user. At the moment, this is only possible/easy via browser interaction by clicking on the "Add new token" button in /me/configure and so the Jenkins X installer has to resort to opening up a browser and attaching a driver to perform the interaction (which is not ideal for very obvious reasons). We need a programmatic way (ie, RESTish) to create-and-get a new API Token. Jenkins X (at the moment) just uses Jenkins' default security realm (basic auth). Add Comment
[JIRA] (JENKINS-54539) REST API to generate API tokens
Title: Message Title Antonio Muñiz started work on JENKINS-54539 Change By: Antonio Muñiz 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-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Thorsten Scherler commented on JENKINS-54261 Re: Submit ( go ) on Email Template Testing produces blank screen Please test https://github.com/jenkinsci/jenkins/pull/3725 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-54333) Projects are triggered twice by "build with parameters"
Title: Message Title Thorsten Scherler commented on JENKINS-54333 Re: Projects are triggered twice by "build with parameters" https://github.com/jenkinsci/jenkins/pull/3725 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-40667) Support of Rundeck usage in Pipeline script
Title: Message Title Cédric SARRE commented on JENKINS-40667 Re: Support of Rundeck usage in Pipeline script John Mohan Hello, I met the same issue on yesterday, and I loggued an issue (https://issues.jenkins-ci.org/browse/JENKINS-54537). 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-54539) REST API to generate API tokens
Title: Message Title Antonio Muñiz updated JENKINS-54539 Jenkins / JENKINS-54539 REST API to generate API tokens Change By: Antonio Muñiz 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-46779) Suppress blaming for shallow git clones
Title: Message Title Ulli Hafner updated JENKINS-46779 Fixed withcommit/1c9c0ff86 Jenkins / JENKINS-46779 Suppress blaming for shallow git clones Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed 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-40667) Support of Rundeck usage in Pipeline script
Title: Message Title Andy Airey commented on JENKINS-40667 Re: Support of Rundeck usage in Pipeline script This ticket should actually be in-progress as there remain to be no docs for it? But it actually works (pipeline support for the rundeck plugin). BTW I don't have such issues on my environment regarding the tags field. 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-54213) MAC OS linked clone
Title: Message Title pjdarton commented on JENKINS-54213 Re: MAC OS linked clone What we did to debug this sort of issue was to manually add a "permanent" slave node to Jenkins and to also start a vSphere VM of the same name, and then to work out how to get it and Jenkins to connect to each other. Once you've got a VM + slave-configuration combination that works, you then turn that VM into a vSphere template and copy the slave configuration into the Jenkins cloud template. In this case, because the SSH launcher configuration in a "permanent" slave configuration contains fields that the cloud template configuration does not, you're a bit more limited, so you'll have to limit the permanent slave's configurations you try to just those that the cloud template can provide. However, if you can identify what "verification strategy" the SSL launcher is defaulting to, and then make that work with a permanent VM, you should also be able to make it work with a cloud-provisioned VM too. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Michael Zeitz commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found We ran into similar issue. ... Caused by: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at org.springframework.oxm.jaxb.Jaxb2Marshaller.loadSchema(Jaxb2Marshaller.java:554) at org.springframework.oxm.jaxb.Jaxb2Marshaller.afterPropertiesSet(Jaxb2Marshaller.java:458) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624) ... 91 more Caused by: java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228) ... 96 mor In use is/was Jenkins 2.138.2 with Maven Integration Plugin 3.1.2 (and others). We updated/changed the maven plugin org.mortbay.jetty:jetty-maven-plugin:8.1.15.v20140411 to the new plugin org.eclipse.jetty:jetty-maven-plugin:9.4.12.v20180830 and then the issue occured. (on unix slave) The above mentioned workaround "-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser" works for us. Add Comment
[JIRA] (JENKINS-35708) EC2 Plugin: Ability to round robin EC2 availability zones
Title: Message Title Mikael Gaunin commented on JENKINS-35708 Re: EC2 Plugin: Ability to round robin EC2 availability zones Hi Francis Upton, I guess the status does not reflect the reality. If I'm not wrong, the fix has been delivered into the 1.41 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-46779) Suppress blaming for shallow git clones
Title: Message Title Ulli Hafner edited a comment on JENKINS-46779 Re: Suppress blaming for shallow git clones Fixed with[commit/1c9c0ff86|https://github.com/jenkinsci/warnings-ng-plugin/commit/1c9c0ff86ba480dd6831c63ad91653cf7639ce81] 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-53090) No links available for several plugins on top level of pipeline view
Title: Message Title Samuel Hildwein edited a comment on JENKINS-53090 Re: No links available for several plugins on top level of pipeline view Of course I only evaluated builds which failed after plotting.The problem is the missing link.As soon as one successful build was finished, the link is available again showing plot data of all builds including the failed ones.But again: this behaviour is the same for other plugins too (tasks-plugin, warnings-plugin,junit-plugin), so I am sure this is not a plot plugin problme problem but a problem of core/pipeline plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54544) Allow Pipeline to add Badges to BlueOcean
Title: Message Title Florian Wilhelm created an issue Jenkins / JENKINS-54544 Allow Pipeline to add Badges to BlueOcean Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2018-11-08 15:20 Priority: Minor Reporter: Florian Wilhelm I'm working at SAP in a team that builds a pipeline and want to inform our consumers when they use an insecure configuration for deployments. The badge plugin works quite nice for our purposes in the classical Jenkins UI (code for reference). We tried to find something similar for Blue Ocean, but there does not seem to be anything. Is there an existing solution for this, or could this be added to Blue Ocean? Add Comment
[JIRA] (JENKINS-54519) resolved
Title: Message Title Ebrahim Moshaya updated an issue Jenkins / JENKINS-54519 resolved Change By: Ebrahim Moshaya Summary: Onelogin Groups Parameter pass as one value instead of a List resolved Hi,We are using Onelogin as the IDP for Saml. When we login via Onelogin, the user is assigned the role/group as on string instead of a list of roles/groups the user belongs to. this has been resolved now 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-54143) Cannot create new users in 2.138.2
Title: Message Title Ryszard Perkowski commented on JENKINS-54143 Re: Cannot create new users in 2.138.2 I'm seeing the same on version 2.150 (updated recently from 2.146). Thanks for the workaround. Sorry for lack of logs, I checked those and there is nothing that would stand out as related. The form just does: POST https://jenkins-url/securityRealm/createAccountByAdmin and the response is HTTP 200 with the same form. 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-54143) Cannot create new users in 2.138.2
Title: Message Title Daniel Beck commented on JENKINS-54143 Re: Cannot create new users in 2.138.2 and the response is HTTP 200 with the same form. Is there a response body? 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-54542) allow the `agent` block to be ignored
Title: Message Title Jesse Glick commented on JENKINS-54542 Re: allow the `agent` block to be ignored I do not think you need any help from JFR. In your CasC, just write jenkins: labelString: jenkins-maven That should make the master node be treated as having that label. In general ignoring the agent block is not a good idea because it can have all sorts of configuration, like a Dockerfile reference or a pod specification. A build run in serverless mode is fundamentally different and you cannot assume that a single Jenkinsfile will work for both modes. 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-53090) No links available for several plugins on top level of pipeline view
Title: Message Title Samuel Hildwein updated an issue Jenkins / JENKINS-53090 No links available for several plugins on top level of pipeline view Change By: Samuel Hildwein Environment: Jenkins 2. 136 143 latest plugin versions 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-54488) Lightweight checkout workspace
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.9.4 Jenkins / JENKINS-54488 Lightweight checkout workspace Change By: Paul Allen Status: In Progress Closed Resolution: Fixed 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-54382) Lightweight Checkout failure to find jenkinsfile when jenkinsfile is in a subfolder
Title: Message Title Paul Allen updated JENKINS-54382 Released in 1.9.4 Jenkins / JENKINS-54382 Lightweight Checkout failure to find jenkinsfile when jenkinsfile is in a subfolder Change By: Paul Allen Status: Fixed but Unreleased Closed 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title fisnik hajredini commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. So initially there was an update to 2.28 which i tried and it didnt have this issue fixed. Afterwards i tried the newer build you offered and it also didnt work Pictures: The variant should've been in front each line. Version: 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-54542) allow the `agent` block to be ignored
Title: Message Title
James Strachan created an issue
Jenkins / JENKINS-54542
allow the `agent` block to be ignored
Issue Type:
Task
Assignee:
Oleg Nenashev
Components:
jenkinsfile-runner
Created:
2018-11-08 14:50
Priority:
Minor
Reporter:
James Strachan
When using Jenkins X we have build packs with Jenkisnfiles using `agent` labels for pod templates and kubernetes plugins like this: e.g. our build packs use Jenkinsfiles like this: https://github.com/jenkins-x/draft-packs/blob/2.1/packs/maven/Jenkinsfile#L2 vs with
agent {
label "jenkins-maven"
}
for serverless jenkins we had to create a branch in the build pack like this: https://github.com/jenkins-x/draft-packs/blob/prow/packs/maven/Jenkinsfile#L2 using
agent any
It would be awesome to have a CLI argument or environment variable that basically ignores the `agent` setting! Then we won't need to have a separate set of build packs for serverless
[JIRA] (JENKINS-54543) Jenkins job doesn't show commits from perforce
Title: Message Title Michal Kolas created an issue Jenkins / JENKINS-54543 Jenkins job doesn't show commits from perforce Issue Type: Bug Assignee: Unassigned Attachments: jobsLog.zip, plugins_list.txt Components: p4-plugin, scm-api-plugin Created: 2018-11-08 15:00 Environment: Master on Centos 7.5 Slave on win7 64bit Jenkins: 2.149 Java 8 perforce p4v/ntx64/2017.1 Priority: Major Reporter: Michal Kolas Job is configured as pipeline script from SCM (perforce) Job is called on windows slave agent. Jenkins job doesn't display information about existing commits/changes (which exists) - his changelog is empty. He doesn't display it on job page (at #job execution / date / NO CHANGES) and in log during execution of checkout scm. Although he downloads new version of changed file. What is interesting when you use "replay" button, it works properly - it always displays existing changes. What is more, when you call job using jenkins-cli in jenkins-cli log you can see commits, but in job log doesn't attachments: logs from both jobs (from build and replay botton) plugins list
[JIRA] (JENKINS-50880) Create a new option for running when condition before stage input
Title: Message Title Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-50880 Create a new option for running when condition before stage input Change By: Jose Blas Camacho Taboada Assignee: Andrew Bayer Jose Blas Camacho Taboada 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-48556) timestamps() randomly not recognized as a valid option
Title: Message Title Andrew Bayer updated JENKINS-48556 This'll be fixed in 1.3.3. Jenkins / JENKINS-48556 timestamps() randomly not recognized as a valid option Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed 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-43754) Global pipeline library & simple 'checkout scm' rebuilds each polling cycle
Title: Message Title Aaron Marasco commented on JENKINS-43754 Re: Global pipeline library & simple 'checkout scm' rebuilds each polling cycle My workaround is to add a checkbox that the user has to check to force the rebuild to actually happen. :-/ 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-53644) Is it possible to configure the color of the job (success or not) depending on the error number of one parser
Title: Message Title iostrym commented on JENKINS-53644 Re: Is it possible to configure the color of the job (success or not) depending on the error number of one parser Thanks a lot. I tried it and I successfully launch a second time your warning plugin. then I configure the second warning plugin using Quality Gate Thresholds and I have a problem because I can only set threshold for : Severity High / normal / low And it seems that it correspond only to WARNING_HIGH, WARNING_NORMAL, WARNING_LOW severity. And I don't succeed to make my job failing when I have at least one ERROR. Is it normal ? My parser only generates warning with severity : "Low" or "Error". Is it possible to use Quality Gate Thresholds on "Error" severity ? Because if I'm correct, Severity High is WARNING_HIGH and not Error. Am I correct ? 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-43754) Global pipeline library & simple 'checkout scm' rebuilds each polling cycle
Title: Message Title Aaron Marasco commented on JENKINS-43754 Re: Global pipeline library & simple 'checkout scm' rebuilds each polling cycle Another workaround would involve checking the new currentBuild.getBuildCauses() provided by JENKINS-41272. 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-54504) Performance issue with promoted builds and Git branch parameter
Title: Message Title Devin Nusbaum commented on JENKINS-54504 Re: Performance issue with promoted builds and Git branch parameter Josh Schreuder Glad to hear that helped! It's up to you whether you want to work on it. While I am not very familiar with the APIs involved, my guess is that getDefaultParameterValue is normally a very quick operation, so the usage in promoted-builds should be fine as-is for the majority of cases, so I would be ok with just closing this issue for now, and we can revisit it if it becomes a widespread issue in the future. 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-53090) No links available for several plugins on top level of pipeline view
Title: Message Title Samuel Hildwein commented on JENKINS-53090 Re: No links available for several plugins on top level of pipeline view Of course I only evaluated builds which failed after plotting. The problem is the missing link. As soon as one successful build was finished, the link is available again showing plot data of all builds including the failed ones. But again: this behaviour is the same for other plugins too (tasks-plugin, warnings-plugin,junit-plugin), so I am sure this is not a plot plugin problme but a problem of core/pipeline plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title fisnik hajredini updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: fisnik hajredini Attachment: image-2018-11-08-15-38-49-986.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title fisnik hajredini updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: fisnik hajredini Attachment: image-2018-11-08-15-39-26-889.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title fisnik hajredini updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: fisnik hajredini Attachment: image-2018-11-08-15-41-10-158.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49179) Add queue duration for how long stages are wait for a build node to become available
Title: Message Title Adam Brousseau commented on JENKINS-49179 Re: Add queue duration for how long stages are wait for a build node to become available Also would like to see this. As a workaround we have added a "Queue" stage around our node block (which basically wraps the entire build). The side effect is that it breaks the Blue Ocean view by only displaying the Queue stage for the build. The classic view still shows all the stages. 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-48525) Perforce plugin doesn't sync
Title: Message Title Matthew Dews commented on JENKINS-48525 Re: Perforce plugin doesn't sync Also ran into this issue recently. William's workaround works for us at the moment. According to our admin the Perforce server has parallel sync on unless a client requests otherwise. Windows 10 x86 (virtualized) Jenkins Service runs as a local user Job that that had failing p4 sync was run locally 1 macOS slave which we have observed no sync issues on P4 Plugin 1.9.3 Jenkins 2.138.2 java.runtime.version 1.8.0_144-b01 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-54546) Missing policy violations column
Title: Message Title Thanh Ha created an issue Jenkins / JENKINS-54546 Missing policy violations column Issue Type: Improvement Assignee: Justin Young Components: nexus-platform-plugin Created: 2018-11-08 18:08 Priority: Minor Reporter: Thanh Ha Since switching to the Nexus Platform plugin from the old CLM plugin. We noticed the policy violations column for views was not ported over to the new plugin. This was a very convenient view column for us as it let us quickly refer to reports for several of our projects via Jenkins views. Is there any plans to migrate that column over to the new plugin? Add Comment
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title Joerg Schwaerzler commented on JENKINS-53162 Re: Blueocean support for visualizing stages in parallel block in scripted pipeline leromarinvit: Doesn't work for me using BlueOcean 1.8.2. That is: The job's green but BlueOcean still won't show me any stages which have been defined inside a parallel branch. Which version of BlueOcean did you use? 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-43546) Facing problem when integrating Blue Ocean with Bitbucket
Title: Message Title Joshua Noble assigned an issue to Joshua Noble Jenkins / JENKINS-43546 Facing problem when integrating Blue Ocean with Bitbucket Change By: Joshua Noble Assignee: James Dumay Joshua Noble 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-50633) JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Title: Message Title Jesse Glick commented on JENKINS-50633 Re: JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting Robin Smith trying. https://github.com/jenkinsci/pipeline-utility-steps-plugin/pull/47 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-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick updated JENKINS-54133 Jenkins / JENKINS-54133 No ANSI coloring on slave agents in pipeline Change By: Jesse Glick Status: In Review 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-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick stopped work on JENKINS-54133 Change By: Jesse Glick Status: In Progress Open 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-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick updated JENKINS-54133 All associated PRs merged. Jenkins / JENKINS-54133 No ANSI coloring on slave agents in pipeline Change By: Jesse Glick Status: Open Fixed but Unreleased Resolution: Fixed 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-35432) Scheduled builds crash after running for more than 8 hours
Title: Message Title Mitch McLaughlin commented on JENKINS-35432 Re: Scheduled builds crash after running for more than 8 hours Kellie Jos - I have just seen this recreated as well using: Jenkins Version: 2.89.4.2 TFS Plugin Version: 5.133.0 Java Version: 1.8.0_181 Operating System: RedHat Linux 3.10.0-862.14.4.el7.x86_64 Is there any plan to address this? Or a potential workaround to allow for jobs to continue running? 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-50310) Support stop GCE instance instead of Termination
Title: Message Title Kai Jing commented on JENKINS-50310 Re: Support stop GCE instance instead of Termination Thanks very much for your prompt response. we move our jenkins and salves from AWS to GCE, and heavily to use this plugin. we wish this plugin is better than ec2 plugin as quick as possible. thanks very much for your harder work. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Jesse Glick Apologies for reopening this issue. Regarding proposed implementation in JENKINS-2111, are you suggesting to use branch-api 2.0.21 ? What does it have different than 2.0.20, would like to know before putting it on production Jenkins instance? Also, JENKINS-2111 looks more about cleanup than fixing multi branch workspace folder name. 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-46167) Writing variables in JSON using writeJson of Pipeline Utility
Title: Message Title Andy Scollard commented on JENKINS-46167 Re: Writing variables in JSON using writeJson of Pipeline Utility If you don't want to get approval to use "inspect()" as Jay suggested, "toString()" worked for me. 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-11752) ANSI color plugin adds garbage to log
Title: Message Title Jesse Glick updated JENKINS-11752 Jenkins / JENKINS-11752 ANSI color plugin adds garbage to log Change By: Jesse Glick Status: In Review 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-39536) Console coloring not working in blueocean
Title: Message Title Jesse Glick updated JENKINS-39536 Jenkins / JENKINS-39536 Console coloring not working in blueocean Change By: Jesse Glick Status: Open Fixed but Unreleased Resolution: Fixed 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-39536) Console coloring not working in blueocean
Title: Message Title Jesse Glick stopped work on JENKINS-39536 Change By: Jesse Glick Status: In Progress Open 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-39536) Console coloring not working in blueocean
Title: Message Title Jesse Glick updated JENKINS-39536 Jenkins / JENKINS-39536 Console coloring not working in blueocean Change By: Jesse Glick Status: In Review 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-11752) ANSI color plugin adds garbage to log
Title: Message Title Jesse Glick updated JENKINS-11752 Jenkins / JENKINS-11752 ANSI color plugin adds garbage to log Change By: Jesse Glick Status: Open Fixed but Unreleased Resolution: Fixed 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-11752) ANSI color plugin adds garbage to log
Title: Message Title Jesse Glick stopped work on JENKINS-11752 Change By: Jesse Glick Status: In Progress Open 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Jesse Glick commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Please attach the log and log-index files from the build directory ($JENKINS_HOME/jobs/*/builds/*/) and show a full-size screenshot including a point at which output switches from one branch to another, and note any browser console warnings or 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-54546) Missing policy violations column
Title: Message Title Justin Young commented on JENKINS-54546 Re: Missing policy violations column Using the jobs view for policy violations was determined an antipattern as that table is used to store Jenkins specific job details. Instead I would expect the job status (pass/failure) to provide a high level indication into which jobs should be investigated. While there are currently no plans on adding the column to the new plugin, I will watch this issue to see if our customers are willing to live with the antipattern given the visibility into violations. 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-54128) Deprecated calls to Run.getLogFile
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile Change By: Sam Van Oort Labels: jep-210-regression regression 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-54358) AWS flavor got broken by a wrong update
Title: Message Title Baptiste Mathus updated JENKINS-54358 Jenkins / JENKINS-54358 AWS flavor got broken by a wrong update Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed 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-54263) Fix/make sure the AWS flavor still works
Title: Message Title Baptiste Mathus updated JENKINS-54263 Jenkins / JENKINS-54263 Fix/make sure the AWS flavor still works Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed 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-50310) Support stop GCE instance instead of Termination
Title: Message Title Kai Jing commented on JENKINS-50310 Re: Support stop GCE instance instead of Termination Any update about this feature. It is important to our implementation too. It has been more than half year. Please priority this feature request. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick updated JENKINS-34564 Please do not reopen. If you encounter bugs, file them separately with complete steps to reproduce from scratch. Or just try my proposed implementation of JENKINS-2111, which reduces path lengths considerably. Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Jesse Glick Status: Reopened Fixed but Unreleased Resolution: Fixed 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-54268) Incrementalify Blue Ocean
Title: Message Title Baptiste Mathus updated JENKINS-54268 Yey Jenkins / JENKINS-54268 Incrementalify Blue Ocean Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed 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-54466) HPIs should be renamed JPIs after download
Title: Message Title Baptiste Mathus updated JENKINS-54466 Jenkins / JENKINS-54466 HPIs should be renamed JPIs after download Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed 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-43546) Facing problem when integrating Blue Ocean with Bitbucket
Title: Message Title Joshua Noble assigned an issue to James Dumay Jenkins / JENKINS-43546 Facing problem when integrating Blue Ocean with Bitbucket Change By: Joshua Noble Assignee: Joshua Noble James Dumay 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-53170) SCM Sync unmaintained
Title: Message Title Craig Tataryn commented on JENKINS-53170 Re: SCM Sync unmaintained Craig Rodrigues Here's why I feel this plugin is still important: I have a whole ecosystem of "legacy" jobs (i.e. non-pipeline). They use a wide range of plugins, and special parameter types that I've cultivated over the years. Here's what I typically see when I try to use the "Convert to Pipeline" feature: // Unable to convert a build step referring to "hudson.plugins.copyartifact.CopyArtifact". Please verify and convert manually if required. // Unable to convert a build step referring to "jenkins.plugins.publish__over__ssh.BapSshBuilderPlugin". Please verify and convert manually if required. // Unable to convert a build step referring to "jenkins.plugins.publish__over__ssh.BapSshBuilderPlugin". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jvnet.hudson.plugins.SSHBuilder". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jvnet.hudson.plugins.SSHBuilder". Please verify and convert manually if required. The Jenkins documentation is not very clear on what to do in this situation. To keep up the the Jones' what I typically do is create an "umbrella" Pipeline script that takes care of orchestration between my legacy jobs. I am perfectly content with leaving those legacy jobs as-is instead of trying to "fix" what ain't broken. The only modification I'll make to my legacy jobs is strip them of their responsibility for kicking off downstream jobs. I instead let my orchestrating pipeline script handle that. I'll bet if you ask around, you'll find that my situation isn't at all unique in the community. Ultimately, stripping out the bells and whistles of per-change commit messages, the plugin is really just asking git (in my case) to commit/push using a .gitignore similar to: # Ignore Everything * ### # Except these files... ### !.gitignore # Jenkins main config and job configs !config.xml # deployment keys for accessing bitbucket !sshkeys/* # plugin configs !hudson*.xml #Even if those files are in sub directories !*/ ### I think this plugin is still important, and it should live on in some fashion. It may have to drop some features, but at least it'll still give people a bit of security knowing that if they mistakenly messed up a job, they can easily go to SCM and lookup the previous version of their job in an effort to restore it.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. are you suggesting to use branch-api 2.0.21 ? When released. Or you can install a build from my PR today. What does it have different than 2.0.20 A completely different system for selecting and managing workspace paths. Best discussed in the other issue or PR. 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.
