[JIRA] (JENKINS-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title Marc Brugger reopened an issue I've tested it with plugin version 1.0.7 in openshift-jenkins-2-rhel7:v3.9.14-2 The Problem does still exist. The root URL is not set. [Pipeline] notifyBitbucket Cannot notify Stash! (Jenkins Root URL not configured) Jenkins / JENKINS-48079 jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup Change By: Marc Brugger 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" gro
[JIRA] (JENKINS-51023) package javax.persistence does not exist
Title: Message Title
Praveen Kumar commented on JENKINS-51023
Re: package javax.persistence does not exist
Hi Oleg , I downloaded new Java version: jdk1.8.0_171 and tried to do the same. Still had the same issue Please find the complete build log Started by user admin [EnvInject] - Loading node environment variables. Building in workspace /home/master/.jenkins/workspace/trade-application-build Updating [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Injecting as environment variables the properties content PY_HOME=${WORKSPACE}/Python27 [EnvInject] - Variables injected successfully. Parsing POMs Established TCP socket on 53914 [trade-application-build] $ /home/master/JENKINS/jdk1.8.0_171/bin/java -cp /home/master/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.12-alpha-1.jar:/home/master/.jenkins/apache-maven-3.1.1/boot/plexus-classworlds-2.5.1.jar:/home/master/.jenkins/apache-maven-3.1.1/conf/logging jenkins.maven3.agent.Maven31Main /home/master/.jenkins/apache-maven-3.1.1 /home/master/.jenkins/war/WEB-INF/lib/remoting-3.17.jar /home/master/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.12-alpha-1.jar /home/master/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.12-alpha-1.jar 53914 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /home/master/.jenkins/workspace/trade-application-build/trade-application-build/pom.xml clean package -Dmaven.test.skip=true -e [INFO] Error stacktraces are turned on. [INFO] Scanning for projects...[WARNING] [WARNING] Some problems were encountered while building the effective model for com.eurexrepo.ntp:audit-app:bundle:002.730.000[WARNING] 'version' contains an _expression_ but should be a constant. @ com.eurexrepo.ntp:trade-parent:${f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/trade-parent/pom.xml, line 11, column 11[WARNING] [WARNING] Some problems were encountered while building the effective model for com.eurexrepo.ntp:ntp-domain:bundle:002.730.000[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.springframework:spring-aop:jar -> duplicate declaration of version ${org.springframework.version} @ com.eurexrepo.ntp:ntp-domain:${f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/ntp-domain/pom.xml, line 55, column 15[WARNING] 'version' contains an _expression_ but should be a constant. @ com.eurexrepo.ntp:trade-parent:${f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/trade-parent/pom.xml, line 11, column 11[WARNING] [WARNING] Some problems were encountered while building the effective model for com.eurexrepo.ntp:perfmon-client:bundle:002.730.000[WARNING] 'version' contains an _expression_ but should be a constant. @ com.eurexrepo.ntp:trade-parent:${f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/trade-parent/pom.xml, line 11, column 11[WARNING] [WARNING] Some problems were encountered while building the effective model for com.eurexrepo.ntp:trade-web:war:002.730.000[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-war-plugin @ com.eurexrepo.ntp:trade-web:${f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/trade-web/pom.xml, line 445, column 12[WARNING] 'version' contains an _expression_ but should be a constant. @ com.eurexrepo.ntp:trade-parent:${f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/trade-parent/pom.xml, line 11, column 11[WARNING] 'build.plugi
[JIRA] (JENKINS-51023) package javax.persistence does not exist
Title: Message Title Praveen Kumar commented on JENKINS-51023 Re: package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[17,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[18,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[19,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[20,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[21,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[22,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[23,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[27,2] cannot find symbol [ERROR] symbol: class Entity [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[28,2] cannot find symbol [ERROR] symbol: class Table [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfigurationId.java:[2,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfigurationId.java:[3,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfigurationId.java:[5,31] package org.apache.commons.lang does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfigurationId.java:[17,2] cannot find symbol [ERROR] symbol: class Embeddable [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/rdom/User.java:[14,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/rdom/User.java:[15,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/rdom/User.java:[16,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/rdom/User.java:[17,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/rdom/User.java:[18,25] package javax.persistence does not exist [JENKINS] Archiving /home/master/.jenkins/workspace/trade-application-build/ntp-domain/pom.xml to com.eurexrepo.nt
[JIRA] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Oliver Lockwood updated an issue
Jenkins / JENKINS-51035
Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Change By:
Oliver Lockwood
Issue Type:
Improvement Bug
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-51023) package javax.persistence does not exist
Title: Message Title Praveen Kumar assigned an issue to Oleg Nenashev Jenkins / JENKINS-51023 package javax.persistence does not exist Change By: Praveen Kumar Assignee: Oleg Nenashev 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-20736) Git plugin does not update origin if URL changes
Title: Message Title Sergey Egorov commented on JENKINS-20736 Re: Git plugin does not update origin if URL changes Had similar. Seems workarround is to delete all builds in such job :S 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-50969) core site build is broken, needed for core taglibs reference
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50969 Re: core site build is broken, needed for core taglibs reference Code changed in jenkins User: Baptiste Mathus Path: pom.xml http://jenkins-ci.org/commit/pom/78460d863800ba4145ad64ecf5a983405460869d Log: JENKINS-50969 Bump to latest maven-site-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-50969) core site build is broken, needed for core taglibs reference
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50969 Re: core site build is broken, needed for core taglibs reference Code changed in jenkins User: Baptiste Mathus Path: pom.xml http://jenkins-ci.org/commit/pom/6610a525bbfc657e0a06f402ed59083edaecaacc Log: Merge pull request #21 from batmat/JENKINS-50969 JENKINS-50969 Bump to latest maven-site-plugin Compare: https://github.com/jenkinsci/pom/compare/c2041fe2418a...6610a525bbfc 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-50843) Cannot call closure element of map as method in sandbox
Title: Message Title Rudolf-Walter Kiss-Szakacs updated JENKINS-50843 Jenkins / JENKINS-50843 Cannot call closure element of map as method in sandbox Change By: Rudolf-Walter Kiss-Szakacs Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51023) package javax.persistence does not exist
Title: Message Title Oleg Nenashev resolved as Not A Defect I reviewed javax.persistence documentation, and I confirm that NO classes of "javax.persistence" are included into standard JDK 8 packages. Whatever you do in your Maven project, you need to add proper Maven dependencies in order to build it with Java 8. Several examples of packages offering javax.persistence API: https://mvnrepository.com/artifact/javax.persistence I am closing it as "Not a defect" according to the in investigation results Jenkins / JENKINS-51023 package javax.persistence does not exist Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Oliver Lockwood commented on JENKINS-51035
Re: Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Apologies, I meant to raise this as a bug originally. I have now fixed that field. Note that we have found it is possible to work around this issue by testing if the directory already exists or not, and only creating if it doesn't, e.g. import jenkins.model.Jenkins if (!Jenkins.instance.getItem('dir')) ... but this is clearly unsatisfactory in the longer term.
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-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Oliver Lockwood updated an issue
Jenkins / JENKINS-51035
Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Change By:
Oliver Lockwood
This is a regression observed between Jenkins LTS 2.89.4 and LTS 2.107.2.The version of the Job DSL plugin (1.69) is unchanged.To reproduce: # Run the following Job DSL to create a folder and some sample views within that folder. {{}} {noformat}folder('/dir') { displayName('dir') } buildMonitorView('/dir/Test BMV') { jobs { regex('.*') } } listView('/dir/Test LV') { jobs { regex(".*") } }{noformat} {{}} # Run the following Job DSL script on its own. {{}} {noformat}folder('/dir') { displayName('dir')}{noformat} {{}} Before the upgrade to Jenkins 2.107.2, this worked fine. Following the upgrade, step 2 destroys the views that were created in step 1.
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
[JIRA] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Oliver Lockwood updated an issue
Jenkins / JENKINS-51035
Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Change By:
Oliver Lockwood
This is a regression observed between Jenkins LTS 2.89.4 and LTS 2.107.2.The version of the Job DSL plugin (1.69) is unchanged.To reproduce: # Run the following Job DSL to create a folder and some sample views within that folder.{{ }}{noformat} folder('/dir') \ { }} {{ displayName('dir') }} {{ } }} {{ buildMonitorView('/dir/Test BMV') \ { }} {{ jobs \ { regex('.*') } }} {{ } }} {{ listView('/dir/Test LV') \ { }} {{ jobs \ { regex(".*") } } {noformat }{{}} } # Run the following Job DSL script on its own.{{ }}{noformat} folder('/dir') \ { }} {{ displayName('dir') } {noformat }{{}} } Before the upgrade to Jenkins 2.107.2, this worked fine. Following the upgrade, step 2 destroys the views that were created in step 1.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
[JIRA] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Oliver Lockwood updated an issue
Jenkins / JENKINS-51035
Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Change By:
Oliver Lockwood
This is a regression observed between Jenkins LTS 2.89.4 and LTS 2.107.2.The version of the Job DSL plugin (1.69) is unchanged.To reproduce: # *1.* Run the following Job DSL to create a folder and some sample views within that folder. {noformat}folder('/dir') { displayName('dir') } buildMonitorView('/dir/Test BMV') { jobs { regex('.*') } } listView('/dir/Test LV') { jobs { regex(".*") } }{noformat} # *2.* Run the following Job DSL script on its own. {noformat}folder('/dir') { displayName('dir')}{noformat} Before the upgrade to Jenkins 2.107.2, this worked fine. Following the upgrade, step 2 destroys the views that were created in step 1.
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 Iss
[JIRA] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Oliver Lockwood updated an issue
Jenkins / JENKINS-51035
Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Change By:
Oliver Lockwood
This is a regression observed between Jenkins LTS 2.89.4 and LTS 2.107.2.The version of the Job DSL plugin (1.69) is unchanged.To reproduce:*1.* Run the following Job DSL to create a folder and some sample views within that folder.{noformat}folder('/dir') { displayName('dir') } buildMonitorView('/dir/Test BMV') { jobs { regex('.*') } } listView('/dir/Test LV') { jobs { regex(".*") } }{noformat}*2.* Run the following Job DSL script on its own.{noformat}folder('/dir') { displayName('dir')}{noformat} Before the upgrade to Jenkins 2.107.2, this worked fine. Following the upgrade, step 2 destroys the views that were created in step 1.
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
[JIRA] (JENKINS-50495) Rundeck configuration is removed on plugin update
Title: Message Title Lionel FÉLICITÉ assigned an issue to Vincent Behar Jenkins / JENKINS-50495 Rundeck configuration is removed on plugin update Change By: Lionel FÉLICITÉ Assignee: Lionel FÉLICITÉ Vincent Behar 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-51007) bitbake slows down 20% when started through jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-51007 Re: bitbake slows down 20% when started through jenkins How is you build implemented? Is it Pipeline or Freestyle Project? My assumption would be that it is mostly related to STDOUT/STDERR streaming, and in such case using Durable Task implementations (like Pipeline steps) could be more efficient. E.g. see https://jenkins.io/blog/2018/02/22/cheetah/ (CC Sam Van Oort) 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-50940) Introduce a way to have build data only during Evergreen testing
Title: Message Title Baptiste Mathus commented on JENKINS-50940 Re: Introduce a way to have build data only during Evergreen testing "bit less than trivial": just had another quick look when testing manually a build, so yes: confirmed. The fact we have no executor on the master makes triggering a job non that trivial, since it then requires tackling for instance JENKINS-49866 so that we do have an agent to run a freestyle job on (FreeStyle, because pipeline would mean we need to install the plugin at startup, which is currently not done yet, and will be done through the update/upgrade lifecycle, which R. Tyler Croy was working on the design on with JEP-307). 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-51023) package javax.persistence does not exist
Title: Message Title
Praveen Kumar updated an issue
Jenkins / JENKINS-51023
package javax.persistence does not exist
Change By:
Praveen Kumar
Comment:
Hi Oleg ,I downloaded new Java version: jdk1.8.0_171 and tried to do the same. Still had the same issuePlease find the complete build log Started by user [admin|http://10.29.60.146:9090/user/admin][EnvInject] - Loading node environment variables.Building in workspace /home/master/.jenkins/workspace/trade-application-buildUpdating [EnvInject] - Executing scripts and injecting environment variables after the SCM step.[EnvInject] - Injecting as environment variables the properties content PY_HOME=$\{WORKSPACE}/Python27[EnvInject] - Variables injected successfully.Parsing POMsEstablished TCP socket on 53914[trade-application-build] $ /home/master/JENKINS/jdk1.8.0_171/bin/java -cp /home/master/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.12-alpha-1.jar:/home/master/.jenkins/apache-maven-3.1.1/boot/plexus-classworlds-2.5.1.jar:/home/master/.jenkins/apache-maven-3.1.1/conf/logging jenkins.maven3.agent.Maven31Main /home/master/.jenkins/apache-maven-3.1.1 /home/master/.jenkins/war/WEB-INF/lib/remoting-3.17.jar /home/master/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.12-alpha-1.jar /home/master/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.12-alpha-1.jar 53914<===[JENKINS REMOTING CAPACITY]===>channel startedExecuting Maven: -B -f /home/master/.jenkins/workspace/trade-application-build/trade-application-build/pom.xml clean package -Dmaven.test.skip=true -e[INFO] Error stacktraces are turned on.[INFO] Scanning for projects...[WARNING] [WARNING] Some problems were encountered while building the effective model for com.eurexrepo.ntp:audit-app:bundle:002.730.000[WARNING] 'version' contains an _expression_ but should be a constant. @ com.eurexrepo.ntp:trade-parent:$\{f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/trade-parent/pom.xml, line 11, column 11[WARNING] [WARNING] Some problems were encountered while building the effective model for com.eurexrepo.ntp:ntp-domain:bundle:002.730.000[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.springframework:spring-aop:jar -> duplicate declaration of version $\{org.springframework.version} @ com.eurexrepo.ntp:ntp-domain:$\{f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/ntp-domain/pom.xml, line 55, column 15[WARNING] 'version' contains an _expression_ but should be a constant. @ com.eurexrepo.ntp:trade-parent:$\{f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/trade-parent/pom.xml, line 11, column 11[WARNING] [WARNING] Some problems were encountered while building the effective model for com.eurexrepo.ntp:perfmon-client:bundle:002.730.000[WARNING] 'version' contains an _expression_ but should be a constant. @ com.eurexrepo.ntp:trade-parent:$\{f7.software.version}, /home/master/.jenkins/workspace/trade-application-build/trade-parent/pom.xml, line 11, column 11[WARNING] [WARNING] Some problems were encountered while building the effective model for com.eurexrepo.ntp:trade-web:war:002.730.000[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be
[JIRA] (JENKINS-51023) package javax.persistence does not exist
Title: Message Title Praveen Kumar closed an issue as Not A Defect Jenkins / JENKINS-51023 package javax.persistence does not exist Change By: Praveen Kumar Status: Resolved Closed Assignee: Oleg Nenashev Praveen Kumar 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-51023) package javax.persistence does not exist
Title: Message Title Praveen Kumar updated an issue Jenkins / JENKINS-51023 package javax.persistence does not exist Change By: Praveen Kumar Comment: [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[17,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[18,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[19,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[20,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[21,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[22,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[23,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[27,2] cannot find symbol [ERROR] symbol: class Entity [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfiguration.java:[28,2] cannot find symbol [ERROR] symbol: class Table [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfigurationId.java:[2,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfigurationId.java:[3,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfigurationId.java:[5,31] package org.apache.commons.lang does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/tdom/TradeSlipConfigurationId.java:[17,2] cannot find symbol [ERROR] symbol: class Embeddable [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/rdom/User.java:[14,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/rdom/User.java:[15,25] package javax.persistence does not exist [ERROR] /home/master/.jenkins/workspace/trade-application-build/ntp-domain/src/main/java/com/eurexrepo/ntp/domain/rdom/User.java:[16,25] package javax.persistence does not exist [ERROR] /h
[JIRA] (JENKINS-29326) Workflow sidebar has duplicated Git Build Data links
Title: Message Title Max M commented on JENKINS-29326 Re: Workflow sidebar has duplicated Git Build Data links May I ask why is this Priority: Minor? Can this be escalated? There are like dozens of duplicates of this issue (see e.g. JENKINS-38204 – the SVN lineage of dupes), and it looks like it's getting "fixed", then broken, then fixed again, then broken again... Is this an architectural problem in Jenkins? Can anybody fix this one-and-for-all? 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-51007) bitbake slows down 20% when started through jenkins
Title: Message Title Thomas Witt commented on JENKINS-51007 Re: bitbake slows down 20% when started through jenkins Freestyle project I am not sure how much Java interferes with IO in the background, but the timings stay the same even when I redirect my output to /dev/null inside build.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-38204) SVN plugin show all checkouts twice in pipeline project
Title: Message Title Max M commented on JENKINS-38204 Re: SVN plugin show all checkouts twice in pipeline project Looks like this is not specific to SVN. JENKINS-29326, by the looks of it, is the very same [bunch of duplicate] issue(s), but reported with Git. 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-29326) Workflow sidebar has duplicated Git Build Data links
Title: Message Title Max M edited a comment on JENKINS-29326 Re: Workflow sidebar has duplicated Git Build Data links May I ask why is this *Priority: Minor*?Can this be escalated?There are like +dozens+ of duplicates of this issue (see e.g. JENKINS-38204 -- – the SVN lineage of dupes), and it looks like it's getting "fixed", then broken, then fixed again, then broken again... Is this an architectural problem in Jenkins?Can anybody fix this one once -and-for-all? 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-49776) Multiple duplicate "Label This Build" links in workflow sidebar for Pipeline project with P4
Title: Message Title Max M commented on JENKINS-49776 Re: Multiple duplicate "Label This Build" links in workflow sidebar for Pipeline project with P4 The same story, but with Git: JENKINS-29326 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-50868) Cannot checkout code via SHH when using blue ocean
Title: Message Title Zack Snyder commented on JENKINS-50868 Re: Cannot checkout code via SHH when using blue ocean When using checkout via SSH, I have to provide an username with key. Other option will work. However, I think the other credential option should not be available anyway. So in fact you can close it, or maybe see this as feature request to fix this. 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-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Zack Snyder commented on JENKINS-50638 Re: windows agent via SSH - Slave JVM has terminated. Exit code Ivan Fernandez Calvo Any update? Or are you now at the end of you knowledge? A tricky problem. 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-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title Gabe Montero commented on JENKINS-48079 Re: jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup Did you explicitly configure it from the Jenkins console. That is the "fix" 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-50761) Integration Test for Multiple Tools and Aggregation
Title: Message Title Anna-Maria Sophie Hardi commented on JENKINS-50761 Re: Integration Test for Multiple Tools and Aggregation Bitte wie besprochen mögliche weitere Testszenarien mitteilen. Danke. 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-48556) timestamps() randomly not recognized as a valid option
Title: Message Title Kyle Leinen commented on JENKINS-48556 Re: timestamps() randomly not recognized as a valid option We just saw this on over 15 brand new pipeline builds (new repos in Github with Jenkinsfiles) on a server that was just updated to latest LTS with latest plugins. It only showed up on the first build, subsequent rebuilds worked as expected. 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-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title Rafi Greenberg commented on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user +1 please 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-50475) Scope import / Maven BOM dependencies
Title: Message Title Maxime Michel commented on JENKINS-50475 Re: Scope import / Maven BOM dependencies Thanks for giving it a shot & sorry it took time to respond. The reason why you want to trigger downstream builds in case of changes of snapshot BOM is scenarios where you add/remove dependencies or change dependency version in the snapshot BOM, correct? Yes. If a BOM change doesn't trigger downstream builds, then a library version introducing problems might be merged and go unnoticed for some time. Making them harder to pinpoint when they're caught. If the BOM pulls a snapshot dependency and if the snapshot dependency gets redeployed, then withMaven would detect it and trigger the downstream job, correct? There are no SNAPSHOT dependencies in our BOM, they're all 3rd party dependencies (think commons-lang3 for instance). They don't appear as dependencies in any of our downstream jobs' Maven dashboards. Our feature request is that a SNAPSHOT BOM build should trigger another of our build that imports the BOM (with a scope `import`). We'll dedicate some time to try to take your branch further ASAP. 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
[JIRA] (JENKINS-50695) Evaluate impact on IDEA workflows
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50695 Evaluate impact on IDEA workflows Change By: Baptiste Mathus Labels: essentials essentials-triggered 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-50695) Evaluate impact on IDEA workflows
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50695 Evaluate impact on IDEA workflows Change By: Baptiste Mathus Sprint: Essentials - Milestone 2 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-50985) Deploy backend services to evergreen.jenkins.io
Title: Message Title R. Tyler Croy commented on JENKINS-50985 Re: Deploy backend services to evergreen.jenkins.io As part of this work, be sure to smash our migrations down into one 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-50849) Define the versions manifest schema
Title: Message Title R. Tyler Croy updated JENKINS-50849 Jenkins / JENKINS-50849 Define the versions manifest schema Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50721) Ensure that the Evergreen backend is using a configured secret for JWT
Title: Message Title R. Tyler Croy started work on JENKINS-50721 Change By: R. Tyler Croy Status: Open In Progress 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-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline
Title: Message Title Bastian Brodbeck commented on JENKINS-48897 Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline Hi, I have the same issue. While the initial setup with username/password through blue ocean works for detecting branches it does not work when actually running a build. I am not able to add proper credentials with ssh key as described above. And builds won't even start with username/password credentials on my private BitBucket Cloud repositories. using GIT_ASKPASS to set credentials > /usr/bin/git fetch --no-tags --progress https://bitbucket.org/me/my-fancy-fake-repo.git +refs/heads/master:refs/remotes/origin/master ERROR: Timeout after 10 minutes ERROR: Error fetching remote repo 'origin' if i set it up a generic git then i can add an ssh key and the build runs fine. But i won't be able to "discover Pull Requests from origin". 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-50764) JIRA steps plugin requires In-process script approval
Title: Message Title Raul Bejaran commented on JENKINS-50764 Re: JIRA steps plugin requires In-process script approval Hello Naresh Rayapati, Sorry but I don't have much time to do the doc change myself. I guess it takes some time to do it the right way (read, undestand then follow workflow and conventions). If there is already an open ticket for adding this on the default whitelist, then I guess it would be OK to just wait for it, hoping it will come soon. Thanks for the plugin Naresh. Cheers. 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-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title Marc Brugger commented on JENKINS-48079 Re: jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup What should I do to 'configure it from the jenkins console'? The fix commit is quite hard to read, since the whole file changed. https://github.com/jenkinsci/openshift-sync-plugin/compare/e1e2e2d05350...d3b43c767085 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-21670) Option to anonymize customer labels
Title: Message Title Matt Sicker assigned an issue to Matt Sicker Jenkins / JENKINS-21670 Option to anonymize customer labels Change By: Matt Sicker Assignee: Rebecca Ysteboe Matt Sicker 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-47345) environment and withEnv not set some environment variables like http_proxy, https_proxy and no_proxy
Title: Message Title
Vitali Rydvan updated an issue
Jenkins / JENKINS-47345
environment and withEnv not set some environment variables like http_proxy, https_proxy and no_proxy
Change By:
Vitali Rydvan
I setted-up in a jenkins pipeline some environment variables and tested to access them in a pipeline step: environment \{ ... http_proxy = 'http://xxx:xxx' ... TOTO='titi' } ... stages \{ stage('xxx') \{ when \{ anyOf \{ branch "$\{env.STABLE_BRANCH}"; branch "$\{env.DEV_BRANCH}" } } steps \{ sh 'env' sh 'env | grep TOTO' sh 'env | grep http_proxy' } } } [...S3MX7KBEQ] Running shell script+ env+ grep TOTOTOTO=titi[Pipeline] sh[...S3MX7KBEQ] Running shell script+ env+ grep http_proxy[Pipeline] }[Pipeline] // stage[Pipeline] } TOTO var is well found but never http_proxy. I've tested to write http_proxy in uppercase too but same behavior. I've tested to setted http_proxy in withEnv but same behavior. Thanks.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this mes
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Jenn Briden updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Jenn Briden Sprint: Pipeline - April 2018 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-50721) Ensure that the Evergreen backend is using a configured secret for JWT
Title: Message Title R. Tyler Croy updated JENKINS-50721 Jenkins / JENKINS-50721 Ensure that the Evergreen backend is using a configured secret for JWT Change By: R. Tyler Croy Status: In Progress Review 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-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title Jenn Briden updated an issue Jenkins / JENKINS-49686 NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Change By: Jenn Briden Sprint: Pipeline - April 2018 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-48491) NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve
Title: Message Title Jenn Briden commented on JENKINS-48491 Re: NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve Sam Van Oort, was this fixed as part of https://github.com/jenkinsci/workflow-cps-plugin/pull/216? 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-50951) evergreen-client should store its current update level
Title: Message Title R. Tyler Croy started work on JENKINS-50951 Change By: R. Tyler Croy Status: Open In Progress 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-50534) git-plugin quality audit for essentials
Title: Message Title Raul Arabaolaza assigned an issue to Raul Arabaolaza Jenkins / JENKINS-50534 git-plugin quality audit for essentials Change By: Raul Arabaolaza Assignee: Isa Vilacides Raul Arabaolaza 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-38381) Optimize log handling in Pipeline and Durable Task
Title: Message Title Jenn Briden updated an issue Jenkins / JENKINS-38381 Optimize log handling in Pipeline and Durable Task Change By: Jenn Briden Labels: blocked cloudbees-internal-pipeline performance project-cheetah 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-50730) NoClassDefFound errors in Cloud Slaves
Title: Message Title Luke Hopkins commented on JENKINS-50730 Re: NoClassDefFound errors in Cloud Slaves We are having similar issues. On slave we see INFO: Connected Apr 27, 2018 3:58:55 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated Apr 27, 2018 3:59:05 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller java.lang.NoClassDefFoundError: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller at jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1.onReconnect(JnlpSlaveRestarterInstaller.java:97) at hudson.remoting.EngineListenerSplitter.onReconnect(EngineListenerSplitter.java:49) at hudson.remoting.Engine.innerRun(Engine.java:662) at hudson.remoting.Engine.run(Engine.java:469) Caused by: java.lang.ClassNotFoundException: jenkins.slaves.restarter.JnlpSlaveRestarterInstaller at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:171) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) We also see in the logs of the job these errors. java.io.IOException: remote file operation failed Cannot contact minion-srzt-svc-template-master-qgsj1-kj8cr: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException Add Comment
[JIRA] (JENKINS-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title Sam Van Oort commented on JENKINS-49686 Re: NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead bentoi Appreciate the update – I think I've got a handle on all of the related issues here and test coverage for it. Just working through a few remaining challenges and then review + human testing. 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-43568) readProperties java.exe locks properties file
Title: Message Title Daniel Baum commented on JENKINS-43568 Re: readProperties java.exe locks properties file I am experiencing this issue with readMavenPom locking pom.xml files. I recursively find all pom.xml files in a project to get information out of them. When I run a build for a second time it finds pom.xml files within the maven target folder and then causes the 'mvn clean install' command to fail since maven cannot completely delete the target folder because the readMavenPom function has locked those extra pom files. 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-40689) Java 10 compatibility
Title: Message Title Jason Juang commented on JENKINS-40689 Re: Java 10 compatibility I just wanted to add that I ran into the same problem when upgrading our jenkins server to Ubuntu 18.04. Antony Gelberg's solution `sudo update-alternatives --config java` solves it for me. For those who are interested, here is what happens after executing the command ``` There are 2 choices for the alternative java (providing /usr/bin/java). Selection Path Priority Status 0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 auto mode 1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 manual mode 2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode ``` After I switched back to java 8, and then `sudo service jenkins start` jenkins comes back to life again. 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-50972) broken link to jira in top level readme.md
Title: Message Title Ben Sherman updated an issue Jenkins / JENKINS-50972 broken link to jira in top level readme.md Change By: Ben Sherman [https://github.com/jenkinsci/amazon-ecs-plugin/] has a broken link to this wiki. Fixed in [ https://github.com/jenkinsci/amazon-ecs-plugin/pull/60 ] 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-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title
Gabe Montero edited a comment on JENKINS-48079
Re: jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Sorry, I got this bug confused with another one.I refreshed my memory with this and [https://bugzilla.redhat.com/show_bug.cgi?id=1510908]Yeah, there was no explicit intention to set the value in the jenkins.model.JenkinsLocationConfiguration.xml file from this pluginWe did not want to override an settings the user might have made to that file via Jenkins configuration.or the jenkins service in OpenShift. I'll also not not3 what jenkins.Model.Jenkins.getRootUrl() does: public @Nullable String getRootUrl() \{ String url = ""> if(url!=null) \{ return Util.ensureEndsWith(url,"/"); } StaplerRequest req = Stapler.getCurrentRequest(); if(req!=null) return getRootUrlFromRequest(); return null; }And what the corresponding panel code does:f.section(title:_("Jenkins Location")) \{ f.entry(title:_("Jenkins URL"), field:"url") \{ f.textbox(default: Functions.inferHudsonURL(request)) } f.entry(title:_("System Admin e-mail address"), field:"adminAddress") \{ f.textbox() }}So they take the request URI to infer an initial setting. That is why you still see a value when you bring up that panel from our OpenShift Jenkins Image for example.As to changing from the Jenkins console (which is does store the changed version in that file)From "Manage Jenkins" -> "Configure System", you look for the "Jenkins Location" heading and the "Jenkins URL" field Then, the relevant piece of code is [https://github.com/openshift/jenkins-sync-plugin/blob/master/src/main/java/io/fabric8/jenkins/openshiftsync/OpenShiftUtils.java#L448-L462] If the root url from jenkins is set, per that jenkins.model.Jenkins code, we'll get the value from the xml file first. It will use that before trying to discern from the service. You are free to open an RFE (not bug) to make such behavior configurable. thanks
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title
Gabe Montero commented on JENKINS-48079
Re: jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Sorry, I got this bug confused with another one. I refreshed my memory with this and https://bugzilla.redhat.com/show_bug.cgi?id=1510908 Yeah, there was no explicit intention to set the value in the jenkins.model.JenkinsLocationConfiguration.xml file from this plugin We did not want to override an settings the user might have made to that file via Jenkins configuration. or the jenkins service in OpenShift. I'll also not what jenkins.Model.Jenkins.getRootUrl() does: public @Nullable String getRootUrl() { String url = ""> if(url!=null) { return Util.ensureEndsWith(url,"/"); } StaplerRequest req = Stapler.getCurrentRequest(); if(req!=null) return getRootUrlFromRequest(); return null; } And what the corresponding panel code does: f.section(title:_("Jenkins Location")) { f.entry(title:_("Jenkins URL"), field:"url") { f.textbox(default: Functions.inferHudsonURL(request)) } f.entry(title:_("System Admin e-mail address"), field:"adminAddress") { f.textbox() } } So they take the request URI to infer an initial setting. That is why you still see a value when you bring up that panel from our OpenShift Jenkins Image for example. As to changing from the Jenkins console (which is does store the changed version in that file) From "Manage Jenkins" -> "Configure System", you look for the "Jenkins Location" heading and the "Jenkins URL" field Then, the relevant piece of code is https://github.com/openshift/jenkins-sync-plugin/blob/master/src/main/java/io/fabric8/jenkins/openshiftsync/OpenShiftUtils.java#L448-L462 If the root url from jenkins is set, per that jenkins.model.Jenkins code, we'll get the value from the xml file first. It will use that before trying to discern from the service. You are free to open an RFE (not bug) to make such behavior configurable. thanks
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48079) jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup
Title: Message Title Gabe Montero resolved as Won't Fix Jenkins / JENKINS-48079 jenkins.model.JenkinsLocationConfiguration.xml is not set upon startup Change By: Gabe Montero Status: Reopened Resolved Resolution: Won't Fix 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-51033) Use incrementals from workflow-api PR 67 and downstream
Title: Message Title Jesse Glick commented on JENKINS-51033 Re: Use incrementals from workflow-api PR 67 and downstream Blocked on review from Oleg Nenashev. 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-51036) -Dignore.dirt flag
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-51036 -Dignore.dirt flag Issue Type: Improvement Assignee: Jesse Glick Components: plugin-pom Created: 2018-04-27 17:50 Priority: Minor Reporter: Jesse Glick git-changelist-maven-extension should accept a -Dignore.dirt flag to make the Git status check nonfatal. This would be useful for testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51037) Add ConcurrentSkipListSet to class whitelist
Title: Message Title Matt Sicker started work on JENKINS-51037 Change By: Matt Sicker Status: Open In Progress 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-51037) Add ConcurrentSkipListSet to class whitelist
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-51037 Add ConcurrentSkipListSet to class whitelist Issue Type: Bug Assignee: Matt Sicker Components: core Created: 2018-04-27 18:26 Labels: JEP-200 Priority: Minor Reporter: Matt Sicker While its related class ConcurrentSkipListMap is already whitelisted, the Set version of the class should also be added to the whitelist. Add Comment
[JIRA] (JENKINS-50164) 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50164 Re: 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running Code changed in jenkins User: Baptiste Mathus Path: content/doc/book/architecting-for-scale.adoc http://jenkins-ci.org/commit/jenkins.io/2da6c1addc4830acf28435bf691896dee0612b31 Log: JENKINS-50164 Document builds location configuration NOT documentation the workspaces location customization on purpose: people should generally not have workspaces on `master` anyway since this would mean builds are run there. 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-50164) 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50164 Re: 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running Code changed in jenkins User: R. Tyler Croy Path: content/doc/book/architecting-for-scale.adoc http://jenkins-ci.org/commit/jenkins.io/0338ee06238749f9f0cf4cc1a234308cce43d75c Log: Merge pull request #1510 from batmat/JENKINS-50164 JENKINS-50164 Document builds location configuration Compare: https://github.com/jenkins-infra/jenkins.io/compare/0010f35371cc...0338ee062387 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-51037) Add ConcurrentSkipListSet to class whitelist
Title: Message Title Matt Sicker updated JENKINS-51037 Jenkins / JENKINS-51037 Add ConcurrentSkipListSet to class whitelist Change By: Matt Sicker Status: In Progress Review 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-51037) Add ConcurrentSkipListSet to class whitelist
Title: Message Title Matt Sicker updated JENKINS-51037 Unneeded, using readResolve and writeReplace to use a HashSet instead. Jenkins / JENKINS-51037 Add ConcurrentSkipListSet to class whitelist Change By: Matt Sicker Status: In Review Closed Resolution: Won't Fix 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://gr
[JIRA] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Aaron Marasco commented on JENKINS-51035
Re: Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
I think importing of previous jobs might be broken - I'm having major problems with environment variables and am about to file a bug for 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-51038) Re-defining existing job loses environment variables
Title: Message Title
Aaron Marasco created an issue
Jenkins / JENKINS-51038
Re-defining existing job loses environment variables
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-04-27 19:32
Environment:
EnvInject 2.1.5 Job DSL 1.69 Jenkins 2.107.2
Priority:
Major
Reporter:
Aaron Marasco
If I define a pipeline job with environment variables in it, on the second (and subsequent) runs, the environment disappears.
def my_job = pipelineJob("/${ROOT}/${BRANCH_FOLDER}/${pf}/${test}")
my_job.with {
description "${test} on ${pf} (${BRANCH_FOLDER})".replaceAll('_', ' ')
displayName test.replaceAll('_', ' ')
definition {
cps {
script(readFileFromWorkspace('jenkins/runtime/groovy/Jenkinsfile_example_job_to_run.groovy'))
sandbox()
}
}
environmentVariables {
envs(
Upstream_Job_Name: JOB_NAME,
Upstream_Job_Build: BUILD_NUMBER,
GIT_BRANCH: BRANCH_FOLDER,
PLATFORM: pf,
COMPONENT_TO_TEST: test,
)
keepBuildVariables(true)
}
quietPeriod 1 // 1 second
} // my_job
// Launch it!
queue(my_job) // should be able to be a string too
Delete the job
Run the job
Save off target job's config.xml on server
[JIRA] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Aaron Marasco edited a comment on JENKINS-51035
Re: Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
I think importing of previous jobs might be broken - I'm having major problems with environment variables and am about to file a bug for it. JENKINS-50138
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-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Aaron Marasco edited a comment on JENKINS-51035
Re: Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
I think importing of previous jobs might be broken - I'm having major problems with environment variables JENKINS- 50138 51038
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-50716) Include scm/tag in flattened POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50716 Re: Include scm/tag in flattened POM Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/pom/3dd6e2d377daec76f58e50f47827760e8d390d13 Log: JENKINS-50716 Flatten scm/tag. 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-50692) Allow incrementals deployment from core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50692 Re: Allow incrementals deployment from core Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/pom/fa64385172027a6265d40efcecd71c42dbfb87c6 Log: JENKINS-50692 Incrementals profiles. 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-50689) Document opt-in process
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50689 Re: Document opt-in process Code changed in jenkins User: Jesse Glick Path: README.md incrementals.md pom.xml http://jenkins-ci.org/commit/plugin-pom/5b2f11d9b029beb632eab5b66426a839ffeccf00 Log: Again splitting up consume-incrementals from produce-incrementals profiles, and JENKINS-50689 formally documenting their usage. 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-50716) Include scm/tag in flattened POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50716 Re: Include scm/tag in flattened POM Code changed in jenkins User: Jesse Glick Path: incrementals.md http://jenkins-ci.org/commit/plugin-pom/c86bfaebc5179fdb42d4e7b71d87591f95466cbe Log: JENKINS-50716 Documentation for flattening of scm/tag. 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-50716) Include scm/tag in flattened POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50716 Re: Include scm/tag in flattened POM Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/plugin-pom/3a7175bace6072f1075a9ded068e46985f282c7e Log: JENKINS-50716 Flatten scm/tag. 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-51033) Use incrementals from workflow-api PR 67 and downstream
Title: Message Title Jesse Glick commented on JENKINS-51033 Re: Use incrementals from workflow-api PR 67 and downstream Unblocked. 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-42090) Include Link to claimed testCase in claim mail
Title: Message Title Arnaud TAMAILLON resolved as Fixed fixed in next version Jenkins / JENKINS-42090 Include Link to claimed testCase in claim mail Change By: Arnaud TAMAILLON Status: Open Resolved Assignee: Christian Bremer florian gouze Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Go
[JIRA] (JENKINS-51033) Use incrementals from workflow-api PR 67 and downstream
Title: Message Title Jesse Glick started work on JENKINS-51033 Change By: Jesse Glick Status: Open In Progress 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-51039) http proxy are ignored by git operations for loading pipeline libraries
Title: Message Title Holger Partsch created an issue Jenkins / JENKINS-51039 http proxy are ignored by git operations for loading pipeline libraries Issue Type: Bug Assignee: Mark Waite Components: git-plugin, pipeline Created: 2018-04-27 20:51 Environment: lts 2.107.2 with current plugins Labels: jenkins pipeline Priority: Critical Reporter: Holger Partsch Our Jenkins sits behind a firewall, so we have to configure a proxy to access external resources, also git repositories. After upgrading from 2.89.4 to above LTS I noticed that pipeline jobs were hanging because they failed to fetch the Jenkinsfile from a git repo. It turned out that proxy settings were not used. I managed to work around that by disabling "Lightweight Checkout". After that the pipeline failed to load libraries, again because of missing proxy settings. All the problematic repositories could be cloned by "plain" git checkout steps, so my proxy setting are in fact correct, they are just not applied. many thanks, Holger
[JIRA] (JENKINS-51039) http proxy are ignored by git operations for loading pipeline libraries
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-51039 http proxy are ignored by git operations for loading pipeline libraries Change By: Mark Waite Assignee: Mark Waite 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-51039) http proxy are ignored by git operations for loading pipeline libraries
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-51039 http proxy are ignored by git operations for loading pipeline libraries Change By: Mark Waite Component/s: git-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-51029) Option to ignore SSL certificate errors
Title: Message Title Markus Winter commented on JENKINS-51029 Re: Option to ignore SSL certificate errors Instead of ignoring ssl certificates one could also extend the plugin to take a specific certificate that is stored in Jenkins as a certificate credential. This avoids the risk of man in the middle attacks. 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-51033) Use incrementals from workflow-api PR 67 and downstream
Title: Message Title Jenn Briden updated an issue Jenkins / JENKINS-51033 Use incrementals from workflow-api PR 67 and downstream Change By: Jenn Briden Sprint: Pipeline - April 2018 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Sam Van Oort commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Tom Ghyselinck Thanks! That does help, quite a bit. I think I know what's happened here: so, one of the recent changes added a lazy-load feature for the FlowExecution which slightly reduces the work associated with iterating through Pipeline builds (many plugins just iterate to look at the Build result/status or similar build record data). But in several case that lazy-load isn't being invoked when it should be. This should be addressed by https://github.com/jenkinsci/workflow-job-plugin/pull/96 once I can get the full set of fixes validated (it's linked to a second set of fixes in workflow-cps 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Sam Van Oort started work on JENKINS-50888 Change By: Sam Van Oort Status: Open In Progress 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-50888 NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Change By: Sam Van Oort Assignee: Sam Van Oort 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Sam Van Oort commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Now the fun bit: why does it work when you show it in Stage View? Well Stage View requires flow graph data (records of steps run) for visualization, so it explicitly fetches the execution, which triggers lazy load. If lazy-load wasn't invoked, the FlowExecution is uninitialized – the heads are still not deserialized from disk, so that field is null, and thus if you try to modify a field of the build and save it, the run will fail to persist to disk. 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-51033) Use incrementals from workflow-api PR 67 and downstream
Title: Message Title Jesse Glick updated JENKINS-51033 Jenkins / JENKINS-51033 Use incrementals from workflow-api PR 67 and downstream Change By: Jesse Glick Status: In Progress Review 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-51033) Use incrementals from workflow-api PR 67 and downstream
Title: Message Title Jesse Glick updated JENKINS-51033 Jenkins / JENKINS-51033 Use incrementals from workflow-api PR 67 and downstream Change By: Jesse Glick Status: In Review Resolved Resolution: Done 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-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Jesse Glick commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ AFAICT this has been misdiagnosed. The errors are indeed coming from XStream, but not as part of persisted settings like you might think. Rather, the stack traces here and in the duplicate all come from CredentialsProvider.getOrCreateFingerprintOf, which uses XStream merely to get a hash to identify credentials. Thus, changing the serial format from one plugin release to another just means that existing fingerprints will no longer match—as if anyone cares. RemotableGoogleCredentials is explicitly documented as an ephemeral object to be passed over Remoting. Therefore, there is no compatibility concern about its serial form—we can pick anything. 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-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Jesse Glick commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ Filed a simpler revision: PR 17. 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-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-50216 Google Auth Plugin is incompatible with Jenkins 2.102+ Change By: Jesse Glick Assignee: Oleg Nenashev 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-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Jesse Glick commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ I suspect that the compatibility impact on even the unimportant fingerprint issue is zero: from what I can tell, the fingerprints were hashing based on an expiration timestamp which is different every time the credentials are used, so it would never have matched to begin with. Since the problematic class is supposed to be ephemeral and apparently for Remoting only, this indicates a design flaw in the plugin. Perhaps it needed to implement CredentialsSnapshotTaker rather than rolling its own GoogleRobotCredentials.forRemote. 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-48551) Cannot select CIFS publish in project configuration
Title: Message Title Matthew Klepeis commented on JENKINS-48551 Re: Cannot select CIFS publish in project configuration Alex Earl yes this is resolved by the .10 release. When I add a new "Send to Windows Share" element to a job now though I think the Pattern Separator is missing its default value. I added 6 new elements and 5 of them failed. After 30 minutes I realized that property was missing, after adding it everything worked no prob. Thanks again for your help! 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.
