[JIRA] (JENKINS-53274) Remove AWS flavor plugins from essentials.yaml's spec.plugins
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53274 Remove AWS flavor plugins from essentials.yaml's spec.plugins Change By: Baptiste Mathus I think this was noticed first by [~jglick] a few days ago. Didn't take time to check this until today, we have to remove the AWS-based plugins for the list of always installed plugins so that it's only done when running the AWS flavor. !some aws plugins are installed even for docker cloud.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53286) Enable Sentry user capturing
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53286
Enable Sentry user capturing
Change By:
Baptiste Mathus
h3. User capturing is not enabled, hence makes it harder to automatically correlate messages from the same user in Sentry UIWhen working on JENKINS-53251, I see the "User" field on the top right always at 0 : !user count always 0 . png! h3. Expected behavior My understanding is that we should send Reading https://docs.sentry.io/learn/context/#capturing-the-user , I _think_ that we only have to change our code in two places in [sentry.js|https://github.com/jenkins-infra/evergreen/blob/fc4875a6d112f7bca2d1080e301125703de63285/services/src/libs/sentry.js#L47]. Instead of {code:js}Raven.captureMessage(data.log.message, { level: data.log.level.toLowerCase(), logger: data.log.name, extra: {uuid: data.uuid,source: data.log }});{code}We should use `id` field instead of `uuid`, i.e.:{code:js}Raven.captureMessage(data.log.message, { level: data.log.level.toLowerCase(), logger: data.log.name, extra: {id: data.uuid,source: data.log }});{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
[JIRA] (JENKINS-53286) Enable Sentry user capturing
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53286 Enable Sentry user capturing Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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-53274) Remove AWS flavor plugins from essentials.yaml's spec.plugins
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53274 Remove AWS flavor plugins from essentials.yaml's spec.plugins Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-28 08:46 Priority: Minor Reporter: Baptiste Mathus I think this was noticed first by Jesse Glick a few days ago. Didn't take time to check this until today, we have to remove the AWS-based plugins for the list of always installed plugins so that it's only done when running the AWS flavor. Add Comment
[JIRA] (JENKINS-53215) Secure defaults not being configured for Jenkins out of the box
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53215 Secure defaults not being configured for Jenkins out of the box Change By: Baptiste Mathus Attachment: the issue.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53215) Secure defaults not being configured for Jenkins out of the box
Title: Message Title Baptiste Mathus commented on JENKINS-53215 Re: Secure defaults not being configured for Jenkins out of the box Indeed, for the record, here's what can be seen on my own test instance 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-53281) Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53281 Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class Issue Type: Task Assignee: Nicolas De Loof Components: docker-plugin Created: 2018-08-28 10:41 Labels: evergreen-triggered Priority: Minor Reporter: Baptiste Mathus 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,
[JIRA] (JENKINS-53286) Enable Sentry user capturing
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53286 Enable Sentry user capturing Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-28 11:42 Priority: Minor Reporter: Baptiste Mathus User capturing is not enabled, hence makes it harder to automatically correlate messages from the same user in Sentry UI When working on JENKINS-53251, I see the "User" field on the top right always at 0. My understanding is that we should send https://docs.sentry.io/learn/context/#capturing-the-user Add Comment
[JIRA] (JENKINS-53273) Implement the git-based snapshot rollback system described in JEP 302
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53273 Implement the git-based snapshot rollback system described in JEP 302 Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-28 08:31 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus JEP 302 wasn't implemented back then because we were missing the client. It's now time to do it. Add Comment
[JIRA] (JENKINS-53273) Implement the git-based snapshot rollback system described in JEP 302
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53273 Implement the git-based snapshot rollback system described in JEP 302 Change By: Baptiste Mathus [ JEP 302 |https://github.com/jenkinsci/jep/tree/master/jep/302] wasn't implemented back then because we were missing the client. It's now time to do it. 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-53282) "Restarting VM as requested by admin" message should be just an INFO message
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53282 "Restarting VM as requested by admin" message should be just an INFO message Issue Type: Task Assignee: R. Tyler Croy Components: core Created: 2018-08-28 10:47 Labels: evergreen-triggered evergreen Priority: Minor Reporter: Baptiste Mathus Warninigs like JENKINS-53281 Add Comment
[JIRA] (JENKINS-53282) "Restarting VM as requested by admin" message should be just an INFO message
Title: Message Title Baptiste Mathus started work on JENKINS-53282 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53282) "Restarting VM as requested by admin" message should be just an INFO message
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53282 "Restarting VM as requested by admin" message should be just an INFO message Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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-53284) Changing default layout for workspace and builds should not be a warning for first time startup
Title: Message Title
Baptiste Mathus created an issue
Jenkins / JENKINS-53284
Changing default layout for workspace and builds should not be a warning for first time startup
Issue Type:
Task
Assignee:
Unassigned
Components:
core
Created:
2018-08-28 11:15
Labels:
evergreen evergreen-triggered
Priority:
Minor
Reporter:
Baptiste Mathus
Problem Currently, since JENKINS-50164, the message Changing workspaces directories from ${JENKINS_HOME}/workspace/${ITEM_FULL_NAME} to ... will be always issued as a WARNING. Expected It should only be a WARNING for non-fresh startups changes. For all first time uses (like for Jenkins Evergreen), it should be only logged as INFO.
Add Comment
[JIRA] (JENKINS-53274) Remove AWS flavor plugins from essentials.yaml's spec.plugins
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53274 Remove AWS flavor plugins from essentials.yaml's spec.plugins Change By: Baptiste Mathus I think this was noticed first by [~jglick] a few days ago. Didn't take time to check this until today, we have to remove the AWS-based plugins for the list of always installed plugins so that it's those are only done installed when running the AWS flavor. !some aws plugins are installed even for docker cloud.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53274) Remove AWS flavor plugins from essentials.yaml's spec.plugins
Title: Message Title Baptiste Mathus commented on JENKINS-53274 Re: Remove AWS flavor plugins from essentials.yaml's spec.plugins Mandie Smith I've assigned this to you because I'm working on something else just now, but probably can do it later this week if needed. If you cannot do this, just unassign yourself, no problem . Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53281) Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53281
Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class
Change By:
Baptiste Mathus
Jenkins is sending warnings like these:{noformat}Attempt to (de-)serialize anonymous class com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 in file:/evergreen/jenkins/var/plugins/docker-plugin/WEB-INF/lib/docker-plugin.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/{noformat}We should probably fix the Docker plugin as recommended in https://jenkins.io/redirect/serialization-of-anonymous-classes/
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-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53285
Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Change By:
Baptiste Mathus
h3. IssueWe get a bunch of WARNINGs back to Sentry backend for Evergreen.Typical message:{noformat}Created /evergreen/jenkins/var/plugins/authentication-tokens/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness// orCreated /evergreen/jenkins/var/plugins/conditional-buildstep/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness...{noformat}h3. ExpectedWe should probably make a pass to either update to last versions that might already be fixed, or propose patches around to have this cleaned up. h3. list of plugins suffering from this visible through Sentry * authentication-tokens* conditional-buildstep* icon-shim* javadoc* jsch* mapdb-api* maven-plugin* node-iterator-api* run-condition
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-53286) Enable Sentry user capturing
Title: Message Title Baptiste Mathus updated JENKINS-53286 Jenkins / JENKINS-53286 Enable Sentry user capturing Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53285 Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Issue Type: Epic Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-28 11:21 Labels: evergreen-triggered Priority: Minor Reporter: Baptiste Mathus Issue We get a bunch of WARNINGs back to Sentry backend for Evergreen. Typical message: Created /evergreen/jenkins/var/plugins/authentication-tokens/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness // or Created /evergreen/jenkins/var/plugins/conditional-buildstep/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness ... We should probably make a pass to either update to last versions that might already be fixed, or propose patches around to have this cleaned up.
[JIRA] (JENKINS-53282) "Restarting VM as requested by admin" message should be just an INFO message
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53282 "Restarting VM as requested by admin" message should be just an INFO message Change By: Baptiste Mathus Labels: evergreen evergreen-triggered sentry 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-53282) "Restarting VM as requested by admin" message should be just an INFO message
Title: Message Title Baptiste Mathus updated JENKINS-53282 Jenkins / JENKINS-53282 "Restarting VM as requested by admin" message should be just an INFO message Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53285 Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Change By: Baptiste Mathus Sprint: Evergreen - Milestone 1 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-53286) Enable Sentry user capturing
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53286 Enable Sentry user capturing Change By: Baptiste Mathus Attachment: user count always 0.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53289) Test that upgrading Evergreen through a new docker pull && docker run keeps things running
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53289 Test that upgrading Evergreen through a new docker pull && docker run keeps things running Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-28 14:46 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus At least currently, there are a few things we cannot update other than by updating the evergreen image. We do not have any tests for this right now, and we should since we rely on this use case to be able to update things like Node, or Nginx, etc. Add Comment
[JIRA] (JENKINS-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus commented on JENKINS-53285 Re: Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages I'm doing a quick pass to update at least things that are already fixed like this case of the maven-plugin (even if we filter its descriptors out, but well ). For things that will need code fixing, I think we'll plan differently and see how/when/if to do it. 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-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus commented on JENKINS-53285 Re: Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages OK, so I filed a PR to update to latest. I expect we should get much less warnings for this in the next days once it percolates through the fleet instances. The only one I could not update is run-condition, but this one is already also fixed in its master branch \o/. We just need a release out. But currently, nobody is listed to be allowed to https://github.com/batmat/repository-permissions-updater/blob/master/permissions/plugin-run-condition.yml though Dominik Bartholdi was maintaining it in the past IIUC. 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-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53304 Data loss when running on newly pulled version of the evergreen image Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 07:38 Labels: evergreen Priority: Blocker Reporter: Baptiste Mathus Issue Reproducer: run Evergreen using the current docs, mounting /evergreen/jenkins/home for data stop the container run a new one builds are lost, registration is redone Expected behavior Builds should not be lost The instance should be registering anew like it's a first startup Tentative cause This comes from mounting /evergreen/jenkins/home instead of /evergreen. Builds are under /evergreen/jenkins/var, keys (including uuid.json) are under /evergreen/keys.
[JIRA] (JENKINS-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus started work on JENKINS-53304 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53304 Data loss when running on newly pulled version of the evergreen image Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus commented on JENKINS-53304 Re: Data loss when running on newly pulled version of the evergreen image OK, better. Running from: /evergreen/jenkins/home/jenkins.war [INFO][2018-08-29 08:01:38] Logging initialized @1381ms to org.eclipse.jetty.util.log.JavaUtilLog (from org.eclipse.jetty.util.log.Log initialized) [INFO][2018-08-29 08:01:39] Beginning extraction from war file (from winstone.Logger logInternal) 2018-08-29 08:01:39,108 INFO success: evergreen-client entered RUNNING state, process has stayed up for > than 2 seconds (startsecs) [WARNING][2018-08-29 08:01:39] Empty contextPath (from org.eclipse.jetty.server.handler.ContextHandler setContextPath) [INFO][2018-08-29 08:01:39] jetty-9.4.z-SNAPSHOT; built: 2018-06-05T18:24:03.829Z; git: d5fc0523cfa96bfebfbda19606cad384d772f04c; jvm 1.8.0_171-b11 (from org.eclipse.jetty.server.Server doStart) info: Starting the evergreen-client.. info: Configuring the client to use the endpoint https://evergreen.jenkins.io/ info: Configuring the client for socket.io off https://evergreen.jenkins.io/ info: Registering listener for event: `update created` info: Registering listener for event: `status ping` info: Checking registration status.. info: We have keys and a UUID already 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-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53285 Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus commented on JENKINS-53285 Re: Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages OK, done yesterday through https://github.com/jenkins-infra/evergreen/pull/205/files. Do not see run-condition there BTW, possibly someone just removed it earlier. Spawning a brand new instance just now didn't get run-condition installed at least. But https://github.com/jenkins-infra/evergreen/pull/205/files didn't percolate yet to being consumed by the fleet. Once done, I'll have another look, I think we will just want to have another look at Sentry in a few days to see if/which messages for this still come in (if any). Going to mark this as resolved. 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-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus resolved as Fixed Jenkins / JENKINS-53285 Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Change By: Baptiste Mathus Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53306 Support plugin deletion from Essentials.yaml Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 08:20 Priority: Major Reporter: Baptiste Mathus Issue We currently support only adding plugins, by enriching essentials.yaml. We cannot remove plugins (or anything). With the recent rebrand, it would have come handy to be able to remove a given plugin. In that case, it was a simple rename. But there could more convoluted cases, with plugin split, a better one to achieve some feature, etc. Expected As Evergreen developers, we want to be able to instruct that a given (set of) plugin(s) be uninstalled to cover our various use cases Add Comment
[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus commented on JENKINS-53306 Re: Support plugin deletion from Essentials.yaml BTW, R. Tyler Croy what are you thoughts about that. Somehow as a followup to our discussioon yesterday, did you mean you think we should actually remove any plugin that is not explictly listed in essentials.yaml, or should we support adding some specific delete field or so? (I guess the former, but better check ) 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-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53304
Data loss when running on newly pulled version of the evergreen image
Change By:
Baptiste Mathus
h3. IssueReproducer:* run Evergreen using the current docs, mounting /evergreen/jenkins/home for data* stop the container* run a new one* builds are lost, registration is redoneh3. Expected behavior* Builds should not be lost* The instance should be registering anew like it's a first startuph3. Tentative causeThis comes from mounting /evergreen/jenkins/home instead of /evergreen. Builds are under {{/evergreen/jenkins/var}}, keys (including {{uuid.json}}) are under {{/evergreen/keys}}. Thanks for [~jglick] for seeing this first.
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-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53304
Data loss when running on newly pulled version of the evergreen image
Change By:
Baptiste Mathus
h3. IssueReproducer:* run Evergreen using the current docs, mounting /evergreen/jenkins/home for data* stop the container* run a new one* builds are lost, registration is redoneh3. Expected behavior* Builds should not be lost* The instance should be registering anew like it's a first startuph3. Tentative causeThis comes from mounting /evergreen/jenkins/home instead of /evergreen. Builds are under {{/evergreen/jenkins/var}}, keys (including {{uuid.json}}) are under {{/evergreen/keys}}.Thanks for to [~jglick] for seeing this first.
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-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus commented on JENKINS-53306 Re: Support plugin deletion from Essentials.yaml Another obvious case is for instance the maven-plugin: right now, for historical reasons, it is installed because pulled in by many plugins. But we filter out its descriptor, hence it's not even visible from the UI. So if some day we were able to break those transitive dependencies, it would be nice to be able to uninstall it seamlessly from instances running out there. 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-53307) Transform o.j.p.g.RemoteGitImpl$CommandInvocationHandler$1 into a non anonymous class
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53307 Transform o.j.p.g.RemoteGitImpl$CommandInvocationHandler$1 into a non anonymous class Issue Type: Task Assignee: Mark Waite Components: git-plugin Created: 2018-08-29 09:45 Labels: evergreen-triggered sentry Priority: Major Reporter: Baptiste Mathus Issue The Git plugin triggers the following warnings currently: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1 in file:/evergreen/jenkins/var/plugins/git-client/WEB-INF/lib/git-client.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Expected The anonymous class should be extracted to a full blown one so that this warning (and more importantly remoting works as fine as possible) goes away. Thanks!
[JIRA] (JENKINS-53309) Flavor should be pushed into Sentry
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53309 Flavor should be pushed into Sentry Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 09:52 Labels: evergreen sentry Priority: Minor Reporter: Baptiste Mathus I think it would be very helpful to have directly the flavor pushed with log entries into Sentry. For instance, it would help understand where a message is coming from and capturing context. If something is going wrong, like an EC2 plugin message for a docker-cloud flavor, we would understand it much quicker. (Technically: we do have that information in the DB, from the UUID, but it's not accessible to anyone and would require one more hop each time). Add Comment
[JIRA] (JENKINS-53307) Transform anonymous classes sent over remoting into non anonymous classes
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53307 Transform anonymous classes sent over remoting into non anonymous classes Change By: Baptiste Mathus Summary: Transform o.j.p.g.RemoteGitImpl$CommandInvocationHandler$1 anonymous classes sent over remoting into a non anonymous class classes 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-53307) Transform anonymous classes sent over remoting into non anonymous classes
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53307
Transform anonymous classes sent over remoting into non anonymous classes
Change By:
Baptiste Mathus
h3. IssueThe Git plugin triggers the following warnings currently:{noformat}Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1 in file:/evergreen/jenkins/var/plugins/git-client/WEB-INF/lib/git-client.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/{noformat} And{noformat}Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1 in file:/evergreen/jenkins/var/plugins/git-client/WEB-INF/lib/git-client.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/{noformat} h3. ExpectedThe anonymous class should be extracted to a full blown one so that this warning (and more importantly remoting works as fine as possible) goes away.Thanks!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52123) Adjust sse-gateway to the now configurable location for tasks logging
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52123 Adjust sse-gateway to the now configurable location for tasks logging Change By: Baptiste Mathus Priority: Critical Major 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-53164) Rebrand from Essentials to Evergreen the "essentials jenkins plugin"
Title: Message Title Baptiste Mathus commented on JENKINS-53164 Re: Rebrand from Essentials to Evergreen the "essentials jenkins plugin" Rename of text and artifactId done through https://github.com/jenkinsci/essentials-plugin/pull/13 JIRA component renamed using the IRC bot GitHub repo to be done through INFRA-1753 as the IRC bot requires one being an admin to rename a github repo Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53190) Initial admin password regenerated and reset on upgrades
Title: Message Title Baptiste Mathus updated JENKINS-53190 Jenkins / JENKINS-53190 Initial admin password regenerated and reset on upgrades Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53190) Initial admin password regenerated and reset on upgrades
Title: Message Title Baptiste Mathus commented on JENKINS-53190 Re: Initial admin password regenerated and reset on upgrades Issue being: we currently have no way to update this file automatically :'(, as goes for the client and many other things. I think I filed something for that in the past... Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53190) Initial admin password regenerated and reset on upgrades
Title: Message Title Baptiste Mathus commented on JENKINS-53190 Re: Initial admin password regenerated and reset on upgrades :facepalm: Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53190) Initial admin password regenerated and reset on upgrades
Title: Message Title Baptiste Mathus started work on JENKINS-53190 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53147
Rebrand from Essentials to Evergreen
Change By:
Baptiste Mathus
* {{Essentials Jenkins plugin}} => ** rename the plugin display name** change the artifactId (we generally do not do this, but I think in this case we should because it's 1) still early stage and 2) nobody is ever supposed to install this plugin manually anyway* Rename occurrences of Essentials to Evergreen in the pluginIn the evergreen repo itself, we should probably also rename Essentials to Evergreen as much as possible.{noformat}.../evergreen $ git grep -i essentials | wc -l 111{noformat}* Rename the {{essentials}} tag on jenkins.io** Also change some article related articles ? (wondering if we should do that on older blog entries: it feels partly wrong, like rewriting history. I'm inclined to only do the tag, not the content itself. The rebrand will get a dedicated new blog entry anyway).
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53147
Rebrand from Essentials to Evergreen
Change By:
Baptiste Mathus
* {{Essentials Jenkins plugin}} => ** rename the plugin display name** change the artifactId (we generally do not do this, but I think in this case we should because it's 1) still early stage and 2) nobody is ever supposed to install this plugin manually anyway* * Rename occurrences of Essentials to Evergreen in the pluginIn the evergreen repo itself, we should probably also rename Essentials to Evergreen as much as possible.{noformat}.../evergreen $ git grep -i essentials | wc -l 111{noformat} * Rename the {{essentials}} tag on jenkins.io** Also change some article? (wondering if we should do that on older blog entries: it feels partly wrong, like rewriting history. I'm inclined to only do the tag, not the content itself. The rebrand will get a dedicated new blog entry anyway).
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53251) Review Sentry issues
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53251 Review Sentry issues Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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-53251) Review Sentry issues
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53251 Review Sentry issues Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-27 13:39 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus There are many Sentry issues that have been automatically reported (yay Mandie Smith!), we need to review those and see how to fix those. Add Comment
[JIRA] (JENKINS-53251) Review Sentry issues
Title: Message Title Baptiste Mathus started work on JENKINS-53251 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53164) Rebrand from Essentials to Evergreen the "essentials jenkins plugin"
Title: Message Title Baptiste Mathus commented on JENKINS-53164 Re: Rebrand from Essentials to Evergreen the "essentials jenkins plugin" Good feedback on the PR to update evergreen about the cohabitation of the two artifactIds: we should tombstone the essentials artifact anyway to avoid issues we do not support yet removing things like plugins. @rtyler rightly says it might then be a good idea to do it now. => Tombstoning allows us to move forward right away by having the two plugins together. Then we can remove the essentials plugin from the disk later on by implementing deletions. 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-53251) Review Sentry issues
Title: Message Title Baptiste Mathus updated JENKINS-53251 Jenkins / JENKINS-53251 Review Sentry issues Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus commented on JENKINS-53306 Re: Support plugin deletion from Essentials.yaml Seems like Tyler actually filed JENKINS-53256 two days. Going to close this in favor of this older reported issue. 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-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title Baptiste Mathus commented on JENKINS-53318 Re: Version for a given plugin should be taken from environments first when overridden Jesse Glick is hinting that we might just want to forbid this. I'm inclined to agree: we could keep the JS code simple/simpler, and just forbid at the `essentials.yaml` level by fordidding to have different versions of a given plugin for "default" and all flavors involved. I think this would likely save some headaches and discrepancies in the future where different flavors would be actually running different versions of plugins for the same Update Level. 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-53306) Support plugin deletion from Essentials.yaml
Title: Message Title Baptiste Mathus closed an issue as Duplicate Jenkins / JENKINS-53306 Support plugin deletion from Essentials.yaml Change By: Baptiste Mathus Status: Open Closed Resolution: Duplicate 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-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53318
Version for a given plugin should be taken from environments first when overridden
Change By:
Baptiste Mathus
h3. IssueIn UL 33, it seems like the version for docker-commons that has been installed is the {{1.5}}.This version is the one defined in the main section under {{spec.plugins}}. But this version is overridden to {{1.9}} under the flavor-specific {{environments}} sectionto {{1.9}}.The {{.json}} available at https://evergreen.jenkins.io/ for 32a278882aee26f7075e2c219a76dcbacc7b7532 (I think this is the one for UL33) seems correct. So I _think_ the bug might be coming from the service side selection for a given plugin. This caused the update of my test instance, and it failed to restart, with the following in the logs:{noformat}[SEVERE][2018-08-29 10:08:59] Failed Loading plugin Docker plugin v1.1.5 (docker-plugin) (from jenkins.InitReactorRunner$1 onTaskFailed)java.io.IOException: Docker plugin v1.1.5 failed to load. - Docker Commons Plugin v1.5 is older than required. To fix, install v1.9 or later. - Token Macro Plugin v2.0 is older than required. To fix, install v2.3 or later.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:652)at hudson.PluginManager$2$1$1.run(PluginManager.java:517)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenkins$5.runTask(Jenkins.java:1066)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748){noformat}And here's the state on the browser side: !screenshot-1.png|thumbnail! h3. Expected behaviorWhen a plugin is overridden under the environment specific flavor part, the overridden version defined under the flavor should always be the selected one.
Add Comment
[JIRA] (JENKINS-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53318 Version for a given plugin should be taken from environments first when overridden Change By: Baptiste Mathus Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46684) Break transitive dependencies on maven-integration-plugin
Title: Message Title Baptiste Mathus closed an issue as Fixed Situation improved. I will likely now just file targeted JIRAs against plugins still pulling this plugin in, if any. \o/ Jenkins / JENKINS-46684 Break transitive dependencies on maven-integration-plugin Change By: Baptiste Mathus Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53317) Update level number should be displayed on the backend status page
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53317 Update level number should be displayed on the backend status page Change By: Baptiste Mathus Attachment: update levels list.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53317) Update level number should be displayed on the backend status page
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53317 Update level number should be displayed on the backend status page Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 12:37 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus Issue The page shown at https://evergreen.jenkins.io has been awesomely improved to show the existing UL. When looking both at the UI, and the logs from a given instance, it's currently a bit hard to correlate through. On a given instance, we see typically: debug: Currently at update level 33 (BTW, I think this should probably be at level info to be always shown, but that's another discussion). Expected The summary page should have another column showing the update level number
[JIRA] (JENKINS-53251) Review Sentry issues
Title: Message Title Baptiste Mathus commented on JENKINS-53251 Re: Review Sentry issues This will never be really finished, but I filed a bunch of issues and PRs around. Marked progressively everything as resolved. We will for sure see some issues coming back, but hopefully less and less. Or at least not the same . Currently, for the record, I've marked all issues as resolved. 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-53251) Review Sentry issues
Title: Message Title Baptiste Mathus updated JENKINS-53251 Jenkins / JENKINS-53251 Review Sentry issues Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53318 Version for a given plugin should be taken from environments first when overridden Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-29 12:46 Labels: evergreen Priority: Blocker Reporter: Baptiste Mathus Issue In UL 33, it seems like the version for docker-commons that has been installed is the 1.5. This version is the one defined in the main section under spec.plugins. But this version is overridden to 1.9 under the flavor-specific environments sectionto 1.9. The .json available at https://evergreen.jenkins.io/ for 32a278882aee26f7075e2c219a76dcbacc7b7532 (I think this is the one for UL33) seems correct. So I think the bug might be coming from the service side selection for a given plugin. Expected behavior When a plugin is overridden under the environment specific flavor part, the overridden version defined under the flavor should always be the selected one. Add Comment
[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen
Title: Message Title Baptiste Mathus updated JENKINS-53147 Jenkins / JENKINS-53147 Rebrand from Essentials to Evergreen Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus updated JENKINS-53304 Jenkins / JENKINS-53304 Data loss when running on newly pulled version of the evergreen image Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53317) Update level number should be displayed on the backend status page
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53317
Update level number should be displayed on the backend status page
Change By:
Baptiste Mathus
h3. IssueThe page shown at https://evergreen.jenkins.io has been awesomely improved to show the existing UL.When looking both at the UI, and the logs from a given instance, it's currently a bit hard to correlate through.On a given instance, we see typically:{noformat}debug: Currently at update level 33{noformat} (BTW But on the web browser , I think we cannot match this should probably be at level info immediately to be always shown, but that's another discussion) a given line: !update levels list . png|thumbnail!h3. ExpectedThe summary page should have another column showing the update level number , so that we can easily assess the UL a given instance is running in.
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-53281) Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class
Title: Message Title Baptiste Mathus commented on JENKINS-53281 Re: Convert com.nirima.jenkins.plugins.docker.DockerImagePullStrategy$2 to non anymous class Right, hadn't checked that DockerImagePullStrategy is actually an enum. So I just checked the other similar one JENKINS-53307 I had filed for the Git plugin, and there it seems like a fix would be needed. 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-53215) Secure defaults not being configured for Jenkins out of the box
Title: Message Title Baptiste Mathus commented on JENKINS-53215 Re: Secure defaults not being configured for Jenkins out of the box Associated PR is ready to review (and had a green build in CI). 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-53215) Secure defaults not being configured for Jenkins out of the box
Title: Message Title Baptiste Mathus updated JENKINS-53215 Jenkins / JENKINS-53215 Secure defaults not being configured for Jenkins out of the box Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title Baptiste Mathus commented on JENKINS-53318 Re: Version for a given plugin should be taken from environments first when overridden We just met with Mandie Smith and agreed on the following: she is going to do some checks and add tests in this feature area Because we can only reproduce it using the production deployed backend, it's very likely we should first upgrade the backend to latest before delving into this too much. I can see for instances commits like cc9ed7e60d441ecdea8737af8aac43a022ef92c1 or 21733e1228f9341b755d4727cc3ab08e52221352 or 7ac8b77de9a4f648916fc57dcaf6c48b02552831 that could well be fixes for just that. 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-53418) Provide a one-click button to use easily the CloudFormation template for AWS flavor
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53418 Provide a one-click button to use easily the CloudFormation template for AWS flavor Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-04 18:16 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus Currently, we have only a CloudFormation template that one must use the CLI for to use it. It would much more useful that we provide a button directly usable from GitHub that would take one to the AWS ui and provide the necessary parameters for the given template. Add Comment
[JIRA] (JENKINS-53418) Provide a one-click button to use easily the CloudFormation template for AWS flavor
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53418 Provide a one-click button to use easily the CloudFormation template for AWS flavor Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Baptiste Mathus commented on JENKINS-53285 Re: Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Dominik Bartholdi thanks a bunch! 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-53256) Backend should fill out `deletes` in the update level for plugins
Title: Message Title Baptiste Mathus updated JENKINS-53256 \o/ woot, thanks Mandie Smith! Jenkins / JENKINS-53256 Backend should fill out `deletes` in the update level for plugins Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53273) Implement the git-based snapshot rollback system described in JEP 302
Title: Message Title
Baptiste Mathus commented on JENKINS-53273
Re: Implement the git-based snapshot rollback system described in JEP 302
Started trying to find some library to manage a git repo. Until now, no luck:
https://www.npmjs.com/package/run-git-command => IIUC, uses ES6 import feature. Which fails in our build as it is.
http://www.nodegit.org/ seemed very nice, but cannot get it to work on my machine. And it's fun but their CI actually says the build is borked on Linux:
> nodegit@0.22.2 install /home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit
> node lifecycleScripts/preinstall && node lifecycleScripts/install
[nodegit] Running pre-install script
[nodegit] Configuring libssh2.
{ Error: Command failed: /home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/libssh2/configure --with-libssl-prefix=/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/openssl/openssl
/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/libssh2/missing: Unknown `--is-lightweight' option
Try `/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/libssh2/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
configure: error: No crypto library found!
Try --with-libssl-prefix=PATH
or --with-libgcrypt-prefix=PATH
or --with-wincng on Windows
at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
killed: false,
code: 1,
signal: null,
cmd: '/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/libssh2/configure --with-libssl-prefix=/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/openssl/openssl' }
/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/libssh2/missing: Unknown `--is-lightweight' option
Try `/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/libssh2/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
configure: error: No crypto library found!
Try --with-libssl-prefix=PATH
or --with-libgcrypt-prefix=PATH
or --with-wincng on Windows
[nodegit] ERROR - Could not finish preinstall
{ Error: Command failed: /home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/libssh2/configure --with-libssl-prefix=/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/openssl/openssl
/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/libssh2/missing: Unknown `--is-lightweight' option
Try `/home/tiste/dev/github/jenkins-infra/evergreen/distribution/client/node_modules/nodegit/vendor/libssh2/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
[JIRA] (JENKINS-53273) Implement the git-based snapshot rollback system described in JEP 302
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53273 Implement the git-based snapshot rollback system described in JEP 302 Change By: Baptiste Mathus Attachment: linux wut.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53445) JVM Version not shown for Java 10 on macOS
Title: Message Title Baptiste Mathus commented on JENKINS-53445 Re: JVM Version not shown for Java 10 on macOS Will try to triage/analyze this, though I'm not going to commit to anything before Jenkins World in San Francisco (i.e. ~22th of September) 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-53445) JVM Version not shown for Java 10 on macOS
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53445 JVM Version not shown for Java 10 on macOS Change By: Baptiste Mathus Assignee: sogabe Baptiste Mathus 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-53445) JVM Version not shown for Java 10 on macOS
Title: Message Title Baptiste Mathus commented on JENKINS-53445 Re: JVM Version not shown for Java 10 on macOS Yes, I am. I thought I had done that. Doing it. Thanks for the heads up. 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-53357) Error logs will fill up production disk indefinitely
Title: Message Title Baptiste Mathus updated JENKINS-53357 Jenkins / JENKINS-53357 Error logs will fill up production disk indefinitely Change By: Baptiste Mathus Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53357) Error logs will fill up production disk indefinitely
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53357 Error logs will fill up production disk indefinitely Change By: Baptiste Mathus Sprint: Evergreen - Milestone 1 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-53345) The evergreen UI constantly redirects to http:/// instead of http://:8080
Title: Message Title Baptiste Mathus updated JENKINS-53345 Jenkins / JENKINS-53345 The evergreen UI constantly redirects to http:/// instead of http://:8080 Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53494) Nginx redirection makes Evergreen instance unreachable
Title: Message Title Baptiste Mathus started work on JENKINS-53494 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53494) Nginx redirection makes Evergreen instance unreachable
Title: Message Title Baptiste Mathus commented on JENKINS-53494 Re: Nginx redirection makes Evergreen instance unreachable Reassigned to Tyler as discussed so I can focus back on JENKINS-53273. 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-53494) Nginx redirection makes Evergreen instance unreachable
Title: Message Title Baptiste Mathus assigned an issue to R. Tyler Croy Jenkins / JENKINS-53494 Nginx redirection makes Evergreen instance unreachable Change By: Baptiste Mathus Assignee: Baptiste Mathus R. Tyler Croy 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-53273) Implement the git-based snapshot rollback system described in JEP 302
Title: Message Title Baptiste Mathus stopped work on JENKINS-53273 Change By: Baptiste Mathus Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53494) Nginx redirection makes Evergreen instance unreachable
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53494 Nginx redirection makes Evergreen instance unreachable Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-10 14:27 Labels: evergreen Priority: Blocker Reporter: Baptiste Mathus Right now, on my public instance, if I run the latest image, opening http://:8080 redirects me to https:///blue/pipelines which makes Evergreen currently unusable. Add Comment
[JIRA] (JENKINS-53494) Nginx redirection makes Evergreen instance unreachable
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53494 Nginx redirection makes Evergreen instance unreachable Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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-53273) Implement the git-based snapshot rollback system described in JEP 302
Title: Message Title Baptiste Mathus started work on JENKINS-53273 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53345) The evergreen UI constantly redirects to http:/// instead of http://:8080
Title: Message Title Baptiste Mathus reopened an issue Either brought back by https://github.com/jenkins-infra/evergreen/pull/234, or was actually not fixed but hidden from testing because of JENKINS-53494 ? Jenkins / JENKINS-53345 The evergreen UI constantly redirects to http:/// instead of http://:8080 Change By: Baptiste Mathus Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53494) Nginx redirection makes Evergreen instance unreachable
Title: Message Title Baptiste Mathus updated JENKINS-53494 Merged earlier today, confirmed to resolve this issue. Jenkins / JENKINS-53494 Nginx redirection makes Evergreen instance unreachable Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53499) Improve tests to avoid race condition for updates during startup
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53499 Improve tests to avoid race condition for updates during startup Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-10 20:56 Labels: evergreen testing Priority: Major Reporter: Baptiste Mathus During shUnit2 tests, it can happen that there will be 3 or 4 Git commits related to the updates that happened. This is due to a race condition: when docker-compose starts everything, if the instance starts quickly enough to hit the backend before it received the curl call for pushing the ingest.json then there will be two updates: one from UL0 to UL1, with UL1 an actually first default and empty UL served by the backed one from UL1 to UL2, once the ingest.json with actual plugins and so on has been received. If the ingest.json is pushed before the instance first requests the backend, then the bump will be directly from UL0 to UL2. We need to work out a solution that avoids this source of test flakiness, or we will suffer from it for sure in the upcoming weeks.
[JIRA] (JENKINS-53503) More test coverage for Snapshotter.git()
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53503 More test coverage for Snapshotter.git() Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-11 05:12 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus Snapshotter.js is tested indirectly, we should test the core git() function more directly and this is the core and most critical part of this class. Add Comment
[JIRA] (JENKINS-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title Baptiste Mathus commented on JENKINS-53318 Re: Version for a given plugin should be taken from environments first when overridden OK, so 1) I confirm this one is really critical, I could not get a publicly running evergreen instance trying again just now. Not blocking anymore since I merged https://github.com/jenkins-infra/evergreen/commit/f7cb1f9fad38a4d36a9798dcd0960353b23604fa and it just got pushed as a new UL. 2) What actually concerns me even more right now is I realized no test is failing. So I do not understand why when running locally a docker-cloud flavor, docker-commons gets installed correctly as 1.9 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-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title Baptiste Mathus commented on JENKINS-53318 Re: Version for a given plugin should be taken from environments first when overridden Mandie Smith any idea of why the version could be chosen differently? The only thing I can thing about is the fact we have many UL on the official backend at https://evergreen.jenkins.io, when we have only one locally when testing. I do not know the backend service code enough for this part to form a hypothesis on what could lead to this. To clarify my previous comment: the new UL41 fixes this issue by working around it by forcing docker-commons all the time. So one will not be able to reproduce this issue using https://evergreen.jenkins.io. But because our tests are not failing for this case, this means we could well get back to this situation sooner than we hope (well, I do hope we get back to it soon so that we fix it now, and not when we have more users...). 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-53215) Secure defaults not being configured for Jenkins out of the box
Title: Message Title Baptiste Mathus started work on JENKINS-53215 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
