[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Andrew Widdersheim commented on JENKINS-59552 Re: Detached plugins installed are those with security warnings Go for it. I'm busy too. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202183.1569511656000.6228.1569517920155%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Created https://issues.jenkins-ci.org/browse/JENKINS-59552. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.6148.1569511740229%40Atlassian.JIRA.
[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Andrew Widdersheim created an issue Jenkins / JENKINS-59552 Detached plugins installed are those with security warnings Issue Type: Bug Assignee: Carlos Sanchez Components: docker Created: 2019-09-26 15:27 Priority: Critical Reporter: Andrew Widdersheim When running Jenkins with the official Docker container, some plugins will pull in detached plugins that have security vulnerabilities and also have newer versions available that could be used instead. To replicate, you can install https://plugins.jenkins.io/purge-build-queue-plugin# for example. This will pull in a vulnerable version of https://plugins.jenkins.io/pam-auth: jenkins_1 | INFO: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/pam-auth.jpi jenkins_1 | WARNING: Created /var/jenkins_home/plugins/pam-auth/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness jenkins_1 | INFO: Took 0ms for Loading plugin PAM Authentication plugin v1.1 (pam-auth) by pool-6-thread-4 jenkins_1 | INFO: Took 0ms for Initializing plugin pam-auth by pool-6-thread-1 According to Jesse Glick, this is a bug and not intended behavior. This might be scoped to just running with Docker but it's the only place I'm able to test and replicate.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Daniel Beck any update on this? Was an issue ever made that I can track? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4391.1569346980350%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Thanks Daniel Beck. Did you need me to make a ticket or did you already? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.5107.1568724120400%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Er, I'm sorry. The https://plugins.jenkins.io/pam-auth plugin is the one with the security issue. jenkins_1 | INFO: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/pam-auth.jpi jenkins_1 | WARNING: Created /var/jenkins_home/plugins/pam-auth/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness jenkins_1 | INFO: Took 0ms for Loading plugin PAM Authentication plugin v1.1 (pam-auth) by pool-6-thread-4 jenkins_1 | INFO: Took 0ms for Initializing plugin pam-auth by pool-6-thread-1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3406.1568402940436%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Some logs: jenkins_1 | INFO: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/ldap.jpi jenkins_1 | WARNING: Created /var/jenkins_home/plugins/ldap/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness jenkins_1 | INFO: Took 0ms for Loading plugin LDAP Plugin v1.11 (ldap) by pool-6-thread-24 jenkins_1 | INFO: Took 0ms for Initializing plugin ldap by pool-6-thread-18 The latest version is 1.20 according to my UI. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3398.1568402580305%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Jesse Glick I am not seeing the detached plugins being updated. At last when using the Docker container. I'm able to replicate with the https://plugins.jenkins.io/purge-build-queue-plugin# which pulls in LDAP 1.0 for example. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3312.1568397300249%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data > Apart from that, what's the point of separating functionality into plugins, when the same functionality is injected (in an outdated version) anyway? My understanding is the functionality isn't included anymore in core Jenkins so when those things got peeled out, in order to keep things from breaking, core will pull in these "implied" dependencies to keep other plugins working that may have used them. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3061.1568377861414%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data This feels a little bit untenable if I'm understanding everything correctly, at least for those using the Docker images. Like I'll be playing whack-a-mole either by adding these implied dependencies to my list of installed plugins so they get updated (because of security issues) or by disabling them because they aren't actually used but are pulling in ancient versions with tons of security warnings. It also heavily relies on plugin maintainers to be constantly updating the version of Jenkins their plugin relies on to not be continually pulling in implied deps of old Jenkins core versions. For example, the simple https://plugins.jenkins.io/purge-build-queue-plugin# is referencing a really old Jenkins core version so it's pulling in a ton of implied deps, most of which are really old and some with security vulnerabilities. Whats the best way to handle this other than having that plugin updated to reference a new Jenkins version so less implied deps are pulled in? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.2751.1568374620235%40Atlassian.JIRA.
[JIRA] (JENKINS-58254) Skip initial branch build ignores all other build strategies
Title: Message Title Andrew Widdersheim commented on JENKINS-58254 Re: Skip initial branch build ignores all other build strategies As I understand this more, all of the strategies are OR'ed together so this is working as expected. I would need to use the Any or All strategies to achieve something similar to what I was expecting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200318.1561721912000.12197.1561848840047%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58254) Skip initial branch build ignores all other build strategies
Title: Message Title Andrew Widdersheim commented on JENKINS-58254 Re: Skip initial branch build ignores all other build strategies Félix Belzunce Arcos, you introduced this feature. Maybe you could take a look and confirm what I'm seeing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200318.1561721912000.11631.1561722180127%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58254) Skip initial branch build ignores all other build strategies
Title: Message Title Andrew Widdersheim created an issue Jenkins / JENKINS-58254 Skip initial branch build ignores all other build strategies Issue Type: Bug Assignee: Unassigned Components: basic-branch-build-strategies-plugin Created: 2019-06-28 11:38 Priority: Minor Reporter: Andrew Widdersheim When I enable the "Skip initial build on first branch indexing" build option, all other build strategies I have are ignored. For example, if I have a build strategy to do named branches with an exact name of master as well as the skip option on and push to a branch foo, that branch will get built. It is not until after I remove the skip option that the named branch strategy begins to work again. I am seeing this on version 1.3.2 of this plugin. Add Comment
[JIRA] (JENKINS-44679) need to support script inside options
Title: Message Title
Andrew Widdersheim edited a comment on JENKINS-44679
Re: need to support script inside options
I have a similar need here but a bit more complex than the original reporter. I see that this issue is closed but hopefully we can re-examine the use case. I can also make a new issue.In my case I'd much rather omit {{buildDiscarder()}}. Also the original solution doesn't really work with things like {{disableConcurrentBuilds()}}. For example, it is not possible AFAIK to do something like: {code:java} pipeline \ {options {disableConcurrentBuilds(env.FOO ? true : false)}} {code} Either way I'd much prefer to do something like this:{code:java}pipeline { options {script {if (env.FOO) { buildDiscarder logRotator(daysToKeepStr: '30')disableConcurrentBuilds()} }} }{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182543.1496663658000.8255.1561468200797%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44679) need to support script inside options
Title: Message Title
Andrew Widdersheim commented on JENKINS-44679
Re: need to support script inside options
I have a similar need here but a bit more complex than the original reporter. I see that this issue is closed but hopefully we can re-examine the use case. I can also make a new issue. In my case I'd much rather omit buildDiscarder(). Also the original solution doesn't really work with things like disableConcurrentBuilds(). For example, it is not possible AFAIK to do something like: pipeline { options { disableConcurrentBuilds(env.FOO ? true : false) } } Either way I'd much prefer to do something like this:
pipeline {
options {
script {
if (env.FOO) {
buildDiscarder logRotator(daysToKeepStr: '30')
disableConcurrentBuilds()
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182543.1496663658000.8252.1561467960286%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working Liam Newman Thanks for coming up with a fix. On paper, it looks good but wont' be able to test for a few days unfortunately. Do you need me to before going forward with release? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199501.1558451822000.10362.1558626660120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working Liam Newman great. Thanks! Let me know if I can help with anything. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199501.1558451822000.9458.1558548600116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I'm not sure Only rebuild merge pull requests when source branch has changed is desired and doesn't really accomplish the same thing as Ignore rebuilding merge branches when only the target branch. Feels like either your change needs to adhere to what the base class says it should do by not taking target into account or the logic in this plugin changes in a way that is compatible with all SCMs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199501.1558451822000.9117.1558538820368%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I followed a rabbit hole to this: https://github.com/jenkinsci/github-branch-source-plugin/pull/218 I am wondering if it is related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199501.1558451822000.8951.1558534980397%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I downgraded to 1.1.1 of this plugin and still see the same issue. Also, it appears that the merability message isn't always consistently displayed and may be a red herring. Checking pull request #149 ‘Jenkinsfile’ found Met criteria Changes detected: PR-149 (831936ab764be06ae376045e698f855f77e339da+3f65ffafeddbc4ce48a4abf27ec1dd3c0188ec60 (678431339386505e9e029c095b1d5e83c6cd) → 831936ab764be06ae376045e698f855f77e339da+326d0409c9ecc5675988c4c1d7cbf688d2cf2055 (8ab2d59a2fc7f6432b7863951976756ca6911781)) Scheduled build for branch: PR-149 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199501.1558451822000.8138.1558471740159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I saw that as well though I'm not familiar with internals of how this all fits together. I have no doubt that this issue could be caused by some other plugin but at the end of the day it's this plugins job to prevent the build from happening which brought me here. Also, I'm not entirely able to play with downgrading packages on our production Jenkins currently. Are you able to replicate at all? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199501.1558451822000.8101.1558467900099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I will also sometimes see PRs getting checked twice. Getting remote pull requests... Checking pull request #4597 Could not determine the mergability of pull request 4597. Retrying 4 more times... ‘Jenkinsfile’ found Met criteria Changes detected: PR-4597 (1d496879cc394a321a189f94d34c9bb8eb52166a+5cf22230284e0ddfffcf260c1bb53c04c4a2597a (f3ce4c9e279465bc0182f71ca3d85bf9e5f02f76) → 1d496879cc394a321a189f94d34c9bb8eb52166a+b177caaafd1be37b8f97fe5f2d557ec1a9a78478 (1d2d5ffb99d3496a07edb2714961af1b01581b36)) Scheduled build for branch: PR-4597 Checking pull request #4597 ‘Jenkinsfile’ found Met criteria No changes detected: PR-4597 (still at 1d496879cc394a321a189f94d34c9bb8eb52166a+b177caaafd1be37b8f97fe5f2d557ec1a9a78478 (1d2d5ffb99d3496a07edb2714961af1b01581b36)) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199501.1558451822000.8081.1558464720001%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim commented on JENKINS-57583 Re: Ignore target branch no longer working I will also sometimes see PRs getting checked twice. Getting remote pull requests... Checking pull request #4597 Could not determine the mergability of pull request 4597. Retrying 4 more times... ‘Jenkinsfile’ found Met criteria Changes detected: PR-4597 (1d496879cc394a321a189f94d34c9bb8eb52166a+5cf22230284e0ddfffcf260c1bb53c04c4a2597a (f3ce4c9e279465bc0182f71ca3d85bf9e5f02f76) → 1d496879cc394a321a189f94d34c9bb8eb52166a+b177caaafd1be37b8f97fe5f2d557ec1a9a78478 (1d2d5ffb99d3496a07edb2714961af1b01581b36)) Scheduled build for branch: PR-4597 Checking pull request #4597 ‘Jenkinsfile’ found Met criteria No changes detected: PR-4597 (still at 1d496879cc394a321a189f94d34c9bb8eb52166a+b177caaafd1be37b8f97fe5f2d557ec1a9a78478 (1d2d5ffb99d3496a07edb2714961af1b01581b36)) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199501.1558451822000.8080.1558464660043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57583) Ignore target branch no longer working
Title: Message Title Andrew Widdersheim created an issue Jenkins / JENKINS-57583 Ignore target branch no longer working Issue Type: Bug Assignee: Unassigned Components: basic-branch-build-strategies-plugin Created: 2019-05-21 15:17 Priority: Major Reporter: Andrew Widdersheim I have Ignore rebuilding merge branches when only the target branch changed option enabled but it does not seem to work when doing a repository scan. Checking pull request #126 Could not determine the mergability of pull request 126. Retrying 4 more times... ‘Jenkinsfile’ found Met criteria Changes detected: PR-126 (d4c1e76f93b3bd14801516c1492ba086104c9f40+f0f67d5327479b7265b99bcbbcc9dfba41ac9d74 (84faa76b0eb2e77205ecd1d76aad5db154d0043a) → d4c1e76f93b3bd14801516c1492ba086104c9f40+a5b83e33ac3c7e8f950da549835e9ff6b630ec19 (b5dcd562b082ef2d32f265da138488cabe1ab39f)) Scheduled build for branch: PR-126 Checking pull request #125 Could not determine the mergability of pull request 125. Retrying 4 more times... ‘Jenkinsfile’ found Met criteria Changes detected: PR-125 (c58b5220b377015968b931d94e1687275b46c930+f0f67d5327479b7265b99bcbbcc9dfba41ac9d74 (d6aeb08d075198bd6cde73945584bdd77aa3dca0) → c58b5220b377015968b931d94e1687275b46c930+a5b83e33ac3c7e8f950da549835e9ff6b630ec19 (5377880b32efd962cf9efc0f9ef223f891a09a19)) Scheduled build for branch: PR-125 I only ever see the Could not determine the mergability of pull request 125. Retrying 4 more times... line after a change has been merged to the target of some PRs and I rescan. When rescanning without any changes it's fine.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Andrew Widdersheim commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub I wonder if it has anything to do with the cache just being recently turned on again by default here: https://github.com/jenkinsci/github-branch-source-plugin/commit/1b3a370d78a4f8b431a55bc79ee795f1d8cece88 The time when people started reporting this issue and when that changed happened in early October seem to line up. https://wiki.jenkins.io/display/JENKINS/GitHub+Branch+Source+Plugin The cache can be disabled by setting -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0. My guess is that will serve as a decent work around seeing as the cache wasn't on prior and shouldn't have any adverse affects AFAIK. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54566) Failed to execute command Pipe.Flush
Title: Message Title
Andrew Widdersheim updated an issue
Jenkins / JENKINS-54566
Failed to execute command Pipe.Flush
Change By:
Andrew Widdersheim
Seeing this in my logs but for the most part everything seems to be working fine. I am sort of unclear on whether my Jenkins master is compatible with this agent version so that may be the problem. {noformat} Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: This command is created here Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: Failed to execute command Pipe.Flush(-1) (channel Jenkins Agent (i-03788ba5fec517424)) java.util.concurrent.ExecutionException: Invalid object ID -1 iota=263 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:478) at hudson.remoting.ExportTable.get(ExportTable.java:397) at hudson.remoting.Channel.getExportedObject(Channel.java:780) at hudson.remoting.ProxyOutputStream$Flush.execute(ProxyOutputStream.java:307) at hudson.remoting.Channel$1.handle(Channel.java:565) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:87) Caused by: java.lang.Exception: Object appears to be deallocated at lease before Sat Nov 10 15:38:16 UTC 2018 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:474) ... 5 more Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: This command is created here{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54566) Failed to execute command Pipe.Flush
Title: Message Title Andrew Widdersheim created an issue Jenkins / JENKINS-54566 Failed to execute command Pipe.Flush Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2018-11-10 17:00 Environment: Running Jenkins in Docker on version 2.138.2. Running the Jenkins Slave Docker container using remoting version 3.27 Priority: Minor Reporter: Andrew Widdersheim Seeing this in my logs but for the most part everything seems to be working fine. I am sort of unclear on whether my Jenkins master is compatible with this agent version so that may be the problem. Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: This command is created here Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: Failed to execute command Pipe.Flush(-1) (channel Jenkins Agent (i-03788ba5fec517424)) java.util.concurrent.ExecutionException: Invalid object ID -1 iota=263 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:478) at hudson.remoting.ExportTable.get(ExportTable.java:397) at hudson.remoting.Channel.getExportedObject(Channel.java:780) at hudson.remoting.ProxyOutputStream$Flush.execute(ProxyOutputStream.java:307) at hudson.remoting.Channel$1.handle(Channel.java:565) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:87) Caused by: java.lang.Exception: Object appears to be deallocated at lease before Sat Nov 10 15:38:16 UTC 2018 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:474) ... 5 more Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: This command is
[JIRA] (JENKINS-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title Andrew Widdersheim commented on JENKINS-49558 Re: Run stages in separate Docker containers when top level agent declared Andrew Bayer sure, makes sense. Looks good to me! Though not sure it helps with comment-328884 at all. That said, you mentioned that issue is related to something else. 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-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title Andrew Widdersheim commented on JENKINS-49558 Re: Run stages in separate Docker containers when top level agent declared Pretty similar issue JENKINS-46831. 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-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title
Andrew Widdersheim commented on JENKINS-49558
Re: Run stages in separate Docker containers when top level agent declared
Another annoying scenario I just noticed is you are not trying to execute a stage in lightweight executor as to not tie up anything. For example:
pipeline {
agent {
docker {
image 'python3.6'
}
}
stages {
stage('Foo') {
steps {
sh 'echo foo'
}
}
stage('Verify') {
agent none
steps {
input(
message: "Should we update production?"
)
}
}
}
}
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-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title Andrew Widdersheim commented on JENKINS-49558 Re: Run stages in separate Docker containers when top level agent declared Just to add to this some, it is possible to have each stage run in it's own container instance but requires setting agent on every stage which can become very verbose and not DRY. 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-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title
Andrew Widdersheim created an issue
Jenkins / JENKINS-49558
Run stages in separate Docker containers when top level agent declared
Issue Type:
New Feature
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-02-14 17:48
Priority:
Minor
Reporter:
Andrew Widdersheim
When specifying either docker or dockerfile as the top level agent this will run the entire pipeline and all of it's stages in the same container instance created at the beginning.
pipeline {
agent {
docker {
image 'python3.6'
}
}
/* These stages all run in the same python3.6 container
* created at the beginning of the pipeline.
*/
stages {
stage('Stage 1') {
steps {
sh 'echo foo'
}
}
stage('Stage 2') {
steps {
sh 'echo bar'
}
}
}
}
It would be nice if there were some setting to run each stage in it's own container instance.
pipeline {
agent {
docker {
image 'python3.6'
runPerStage true
}
}
/* These stages all create their own python3.6 container
* created at the beginning of each stage.
*/
stages {
stage('Stage 1') {
steps {
sh 'echo foo'
}
}
stage('Stage 2') {
steps {
sh 'echo bar'
}
}
}
}
