[JIRA] (JENKINS-49820) 'Do not allow concurrent builds' in pipeline sometimes fails
Title: Message Title suryatej yaramada commented on JENKINS-49820 Re: 'Do not allow concurrent builds' in pipeline sometimes fails Hi even we are facing this issue , any solution for this bug will help us Thanks 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-51275) SEVERE: Error in provisioning; agent=KubernetesSlave
Title: Message Title
Sasa Hohol created an issue
Jenkins / JENKINS-51275
SEVERE: Error in provisioning; agent=KubernetesSlave
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
jenkins.log
Components:
kubernetes-plugin
Created:
2018-05-11 18:50
Priority:
Major
Reporter:
Sasa Hohol
May 11, 2018 1:05:59 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher logLastLines SEVERE: Error in provisioning; agent=KubernetesSlave name: incubator-providerreferenceseribcommonsuite2-api23-198-qd-w3h1m, template=PodTemplate{, name='incubator-providerreferenceseribcommonsuite2-api23-198-qd4zp', namespace='default', label='incubator-providerreferenceseribcommonsuite2-api23-198', volumes=[HostPathVolume [mountPath=/var/run/docker.sock, hostPath=/var/run/docker.sock]], containers=[ContainerTemplate{name='jnlp', image='10.36.135.35:5000/sberbank/android:latest', privileged=true, workingDir='/root/agent', resourceRequestCpu='1.5', resourceRequestMemory='3.5G', resourceLimitCpu='1.5', resourceLimitMemory='3.5G', envVars=[KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], ... KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar
[JIRA] (JENKINS-51275) SEVERE: Error in provisioning; agent=KubernetesSlave
Title: Message Title
Sasa Hohol updated an issue
Jenkins / JENKINS-51275
SEVERE: Error in provisioning; agent=KubernetesSlave
Change By:
Sasa Hohol
{code:java} May 11, 2018 1:05:59 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher logLastLinesSEVERE: Error in provisioning; agent=KubernetesSlave name: incubator-providerreferenceseribcommonsuite2-api23-198-qd-w3h1m, template=PodTemplate \ {, name='incubator-providerreferenceseribcommonsuite2-api23-198-qd4zp', namespace='default', label='incubator-providerreferenceseribcommonsuite2-api23-198', volumes=[HostPathVolume [mountPath=/var/run/docker.sock, hostPath=/var/run/docker.sock]], containers=[ContainerTemplate \ {name='jnlp', image='10.36.135.35:5000/sberbank/android:latest', privileged=true, workingDir='/root/agent', resourceRequestCpu='1.5', resourceRequestMemory='3.5G', resourceLimitCpu='1.5', resourceLimitMemory='3.5G', envVars=[KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], ... KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getMay 11, 2018 5:55:09 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch {code} {code:java}def androidEmulator(String name, Closure c) { final String podName = name.toLowerCase().trim() podTemplate(cloud: 'android', name: podName, label: podName, containers: [containerTemplate( name: 'jnlp', image: '10.36.135.35:5000/sberbank/android:latest', envVars: [envVar(key: 'HOME', value: '/root')], workingDir: '/root/agent', privileged: true, resourceRequestCpu: '1.5', resourceRequestMemory: '3.5G')], volumes: [hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock')]) { work(podName) { c() } }}{code}
[JIRA] (JENKINS-51275) SEVERE: Error in provisioning; agent=KubernetesSlave
Title: Message Title
Sasa Hohol updated an issue
Jenkins / JENKINS-51275
SEVERE: Error in provisioning; agent=KubernetesSlave
Change By:
Sasa Hohol
{code:java}May 11, 2018 1:05:59 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher logLastLines SEVERE: Error in provisioning; agent=KubernetesSlave name: incubator-providerreferenceseribcommonsuite2-api23-198-qd-w3h1m, template=PodTemplate{, name='incubator-providerreferenceseribcommonsuite2-api23-198-qd4zp', namespace='default', label='incubator-providerreferenceseribcommonsuite2-api23-198', volumes=[HostPathVolume [mountPath=/var/run/docker.sock, hostPath=/var/run/docker.sock]], containers=[ContainerTemplate{name='jnlp', image=' 10 1 . 36 1 . 135 1 . 35 1 :5000/ sberbank/ android:latest', privileged=true, workingDir='/root/agent', resourceRequestCpu='1.5', resourceRequestMemory='3.5G', resourceLimitCpu='1.5', resourceLimitMemory='3.5G', envVars=[KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME],...KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getValue()=/root, getKey()=HOME], KeyValueEnvVar [getMay 11, 2018 5:55:09 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch{code} {code:java}def androidEmulator(String name, Closure c) { final String podName = name.toLowerCase().trim() podTemplate(cloud: 'android', name: podName, label: podName, containers: [containerTemplate( name: 'jnlp', image: '1.1.1.1:5000/android:latest', envVars: [envVar(key: 'HOME', value: '/root')], workingDir: '/root/agent', privileged: true, resourceRequestCpu: '1.5', resourceRequestMemory: '3.5G')], volumes: [hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock')]) { work(podName) { c() } }}{code}
[JIRA] (JENKINS-51268) Passwords in forms are returned back to client
Title: Message Title Oleg Nenashev commented on JENKINS-51268 Re: Passwords in forms are returned back to client If an attacker has an access to the Jenkins HOME directory, he can just dump it and retrieve all information he wants from 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-51268) Passwords in forms are returned back to client
Title: Message Title Maxim Titov created an issue Jenkins / JENKINS-51268 Passwords in forms are returned back to client Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-11 17:02 Environment: Jenkins 2.107.2 Priority: Minor Reporter: Maxim Titov Passwords in forms are stored in base64 and returned back to client. In case the internal attacker has the access to Jenkins` home directory, the attacker will be able to decrypt the passwords without any additional efforts using the secret key located in the same directory. Is there any option to return empty form keeping password stored elsewhere or encrypt form password with some random key? Add Comment
[JIRA] (JENKINS-49392) Violations plugin freezes project settings screen
Title: Message Title Petr H commented on JENKINS-49392 Re: Violations plugin freezes project settings screen I encountered a very similar issue during the Jenkins startup after it's been updated from 2.107.2 to 2.107.3. Downgraded to 2.107.2 for now and will look into the possibility to remove the Violations plugin. During the startup jenkins.log ends up at: May 11, 2018 6:45:12 PM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins And one thread can be seen utilizing 100% CPU and doing the following: "Initializing plugin sonar" #34 daemon prio=5 os_prio=0 tid=0x7fc6e400e800 nid=0x4700 runnable [0x7fc7129cb000] java.lang.Thread.State: RUNNABLE at org.kxml2.io.KXmlParser.next(Unknown Source) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor$ParseMessages.toTag(FindBugsDescriptor.java:141) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor$ParseMessages.doIt(FindBugsDescriptor.java:123) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor$ParseMessages.execute(FindBugsDescriptor.java:115) at hudson.plugins.violations.parse.ParseXML.parse(ParseXML.java:44) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor.parseMessages(FindBugsDescriptor.java:102) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor.parseMessages(FindBugsDescriptor.java:93) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor.(FindBugsDescriptor.java:88) at hudson.plugins.violations.TypeDescriptor.(TypeDescriptor.java:95) at org.jenkinsci.plugins.jvcts.config.ViolationsToBitbucketServerConfigHelper.createNewConfig(ViolationsToBitbucketServerConfigHelper.java:38) at org.jenkinsci.plugins.jvcts.ViolationsToBitbucketServerDescriptor.(ViolationsToBitbucketServerDescriptor.java:31) at org.jenkinsci.plugins.jvcts.ViolationsToBitbucketServerRecorder.(ViolationsToBitbucketServerRecorder.java:23) at sun.misc.Unsafe.ensureClassInitialized(Native Method) at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43) at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:142) at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1088) at java.lang.reflect.Field.getFieldAccessor(Field.java:1069) at java.lang.reflect.Field.get(Field.java:393) at net.java.sezpoz.IndexItem.instance(IndexItem.java:185) at hudson.ExtensionFinder$GuiceFinder.instantiate(ExtensionFinder.java:353) at hudson.ExtensionFinder$GuiceFinder.access$700(ExtensionFinder.java:232) at hudson.ExtensionFinder$GuiceFinder$SezpozModule$1.get(ExtensionFinder.java:526) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:53) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:61) at
[JIRA] (JENKINS-51271) Refresh token is not invalidated
Title: Message Title Maxim Titov created an issue Jenkins / JENKINS-51271 Refresh token is not invalidated Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-11 17:32 Environment: Jenkins 2.107.2 Priority: Major Reporter: Maxim Titov The refresh token (ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE cookie) is not invalidated on the server side after user logout. A user could still use the token in tailored requests in case he has logged out from the application. If a potential malefactor can steal the refresh token, he will have the large window (around two weeks) of time for malicious activity. Additionally, it should be noted that the lifetime of the token is set to two weeks period that provides to the attacker a wide time range for malicious activities on behalf of the victim. Add Comment
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Code changed in jenkins User: Jesse Glick Path: pom.xml src/test/java/org/jenkinsci/plugins/docker/workflow/DockerDSLTest.java http://jenkins-ci.org/commit/docker-workflow-plugin/d56b6d232b56e8d59d6176697ae6a1b1ecd99455 Log: Merge pull request #137 from jglick/release-JENKINS-38018 JENKINS-38018 Preparing for release Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/cf80d9e2f628...d56b6d232b56 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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-51269) Do not return session id back to client
Title: Message Title Maxim Titov created an issue Jenkins / JENKINS-51269 Do not return session id back to client Issue Type: Bug Assignee: Unassigned Attachments: Screenshot_1.png Components: core Created: 2018-05-11 17:16 Environment: Jenkins 2.107.2 Priority: Minor Reporter: Maxim Titov Do not return JSESSIONID in response headers back to client. Could be used by attacker to steal active session in case it's protected by 'httpOnly' flag. GET https:///whoAmI/ Add Comment
[JIRA] (JENKINS-51270) Anti-CSRF token exposed & static
Title: Message Title Maxim Titov created an issue Jenkins / JENKINS-51270 Anti-CSRF token exposed & static Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-11 17:20 Environment: Jenkins 2.107.2 Priority: Minor Reporter: Maxim Titov In some cases the Jenkins-crumb-token, utilized as countermeasure against CSRF attacks, is sent via URI parameters. Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the “Referer” header when any off-site links are followed. Placing tokens into the URL increases the risk that they will be captured by an attacker. Also the anti-CSRF token is constant for each user and did not change from session to session. Thus, in case an attacker steals victim`s token, he will be able to perform CSRF attacks against him. Add Comment
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Jesse Glick commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Fix released in docker-workflow 1.16. Probably I should file separate issues for the other two plugins, but I am too lazy. 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-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Jacob Keller commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields Make sure that commits aren't rebuilt when they've already been covered by a build. Make sure that job start time isn't significantly worse. 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-51247) Move flattened POM into target directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51247 Re: Move flattened POM into target directory Code changed in jenkins User: Jesse Glick Path: .gitignore .mvn/extensions.xml pom.xml http://jenkins-ci.org/commit/artifact-manager-s3-plugin/ea314b978317326fdbc44ae3f8f0a51bda29b0c6 Log: Merge pull request #21 from jglick/flatten JENKINS-51247 Simplified use of flatten-maven-plugin Compare: https://github.com/jenkinsci/artifact-manager-s3-plugin/compare/8f3e10aba6c8...ea314b978317 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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-51046) Tool to incrementalify POM
Title: Message Title Jesse Glick updated JENKINS-51046 Jenkins / JENKINS-51046 Tool to incrementalify POM Change By: Jesse Glick 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-51276) Erroneous credential issue with upgrade from 2.2.8 to 2.2.9 version of Bitbucket Branch Source Plugin
Title: Message Title NetAppBlueDevil created an issue Jenkins / JENKINS-51276 Erroneous credential issue with upgrade from 2.2.8 to 2.2.9 version of Bitbucket Branch Source Plugin Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-05-11 19:41 Environment: Jenkins 2.120 Bitbucket Server 5.8.2 Priority: Blocker Reporter: NetAppBlueDevil When upgrading from 2.2.8 to 2.2.9 of this plugin, my configured pipeline no longer functioned. When I went in to look at the configuration, within the Bitbucket server portion, this message was displayed under the Repository Name field - "The selected credentials do not have permission to determine whether devts-bb does or does not exist." My credential is a username/password for a user with write access on the repository and up through the 2.2.8 version of this plugin has worked just fine for obtaining the code and updating the build status. Because of this issue, the pipeline no longer executes when Bitbucket changes happen in the repo.
[JIRA] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Benoit Sigoure commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields Thanks for the link, I've installed the plugin [version: 3.9.0-SNAPSHOT (private-69892a21-jenkins)] and disabled the daily job that runs the groovy script. Anything special I should look out for? The issue with the bloat is going to take time to manifest itself again as usually it requires thousands of build.xml files to accumulate. 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-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Mark Waite commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields The biggest concern (for me) is that you enable the extension and watch for regressions in other areas of the git plugin. Does change history still display as expected? Are builds triggered as expected? Are there places where you detect the absence of the build data? 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM Since I didn't see this problem in Blue Ocean 1.4.2 but I'm seeing it in 1.5.0 I went looking for changes in Blue Ocean that may have triggered this problem... I found PR #1667 by Vivek Pandey. It was to fix JENKINS-48820. I doubt it caused this problem, but maybe it made it worse? 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-41194) Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job.
Title: Message Title Simon Weber commented on JENKINS-41194 Re: Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job. Here's a potential fix to try out: https://github.com/jenkinsci/parameterized-trigger-plugin/compare/master...venmo:resolve_pipelines. ymmv; I mostly just copied the approach from https://issues.jenkins-ci.org/browse/JENKINS-38825. 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-51247) Move flattened POM into target directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51247 Re: Move flattened POM into target directory Code changed in jenkins User: Jesse Glick Path: .mvn/extensions.xml pom.xml http://jenkins-ci.org/commit/jenkins/51e0da8ed23d56eb85882937b9a96b7c4aa3c542 Log: JENKINS-51247 source:jar, not source:jar-no-fork 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-51247) Move flattened POM into target directory
Title: Message Title Jesse Glick updated JENKINS-51247 Jenkins / JENKINS-51247 Move flattened POM into target directory Change By: Jesse Glick 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-51247) Move flattened POM into target directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51247 Re: Move flattened POM into target directory Code changed in jenkins User: Jesse Glick Path: .gitignore .mvn/extensions.xml pom.xml http://jenkins-ci.org/commit/jenkins/41c2c49443b442e92e4ec76c001acdc213c4327d Log: Merge pull request #3431 from jglick/flatten JENKINS-51247 Simplified usage of flatten-maven-plugin Compare: https://github.com/jenkinsci/jenkins/compare/72f4a592d28d...41c2c49443b4 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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-51277) Possible bug around labels when using google-compute-engine-plugin
Title: Message Title
Howard Grimberg created an issue
Jenkins / JENKINS-51277
Possible bug around labels when using google-compute-engine-plugin
Issue Type:
Bug
Assignee:
Evan Brown
Components:
google-compute-engine-plugin
Created:
2018-05-11 21:47
Environment:
Jenkins 2.121 Google Compute Engine Plugin 1.0.4
Priority:
Major
Reporter:
Howard Grimberg
I setup the Google Compute Engine according the instructions and have the host(s) starting and provisioning correctly. However, none of my jobs get assigned to it. Upon further investigation, I discovered that none of the labels were attached to the compute engine host. I double checked the labels field in the configuration and verified that the correct things are there, the labels seem to not propagate when the host is created. I verified this by running the following in the script console on the master
import jenkins.model.Jenkins
Jenkins.instance.slaves.each { agent ->
println agent.name + ' ' + agent.labelString
}
to which I found the result
gce-cloud-preemptable-bp86gx
jenkins-slave-instance-group-pgb2 compute-engine docker linux
jenkins-slave-macstadium-207.254.40.72 macstadium ui-tests
jenkins-slave-macstadium-207.254.40.73 macstadium
Result:
