[JENKINS-43077] withEnv does not set some environment variables

Type: Bug
Resolution: Unresolved
Priority: Major
Component/s: docker-workflow-plugin
Labels:
None
Environment:
Jenkins 2.32.3
BlueOcean 1.0.0-rc1

Similar Issues:
Powered by SuggestiMate

Show

I don't believe this is a duplicate of ~~JENKINS-28317~~ but I haven't been able to figure out if I have that version of the plugin installed on my jenkins, because I'm not sure what plugin that applies to.

I had a `withEnv` section that looked like:

def flowContext(cl) {
    withEnv([
        'npm_config_cache=npm-cache',
        'npm_config_registry=http://npm.artifactory.mycompany.com/artifactory/api/npm/npm',
        'http_proxy=http://proxy.mycompany.com:8080',
        'https_proxy=http://proxy.mycompany.com:8080',
        'HTTP_PROXY=http://proxy.mycompany.com:8080',
        'HTTPS_PROXY=http://proxy.mycompany.com:8080',
        'PROXY_HOST=proxy.mycompany.com',
        'PROXY_PORT=8080',
        'no_proxy=.mycompany.com'
    ]) {
        credentialsContext(cl)
    }
}

def credentialsContext(cl) {
    withCredentials([
        usernamePassword(
            credentialsId: 'service-account-user-pass',
            passwordVariable: 'SVC_PASS',
            usernameVariable: 'SVC_USER'
        ),
        usernamePassword(
            credentialsId: 'github-auth-token',
            passwordVariable: 'GITHUB_TOKEN',
            usernameVariable: 'GITHUB_USERNAME'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-token',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_TOKEN'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-password',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_PASSWORD'
        ),
        string(credentialsId: 'slack-webhook', variable: 'SLACK_WEBHOOK_URL'),
        string(credentialsId: 'tracker-token', variable: 'TRACKER_TOKEN')

    ]) {
        cl()
    }
}

The credentials context is another function that exports a few credentials into the environment.
All of the credentials would be there, but not all of the environment variables.

This would be executed within a docker container like so:

    stage('Node Build') {
        docker.image(ciNode).inside() {
            //Do the node installs in parallel, because the npm install is the slowest part, and we can use lots of cpu
            parallel(
                "Root Npm Install/Build": {
                    flowContext {
                        sh('env')
                        sh('npm install')
                        sh('gulp')
                    }
                },
                "webapp/static Install/Build": {
                    flowContext {
                        echo "Due to bug: https://issues.jenkins-ci.org/browse/JENKINS-33510"
                        sh('cd src/main/webapp/static && npm install')
                        sh('cd src/main/webapp/static && grunt prod')
                    }
                },
                failFast: true
            )
        }
    }

The sh('env') command within the flowContext would never show the no_proxy environment variable. I eventually gave up on trying to get it set in the Jenkinsfile, and instead put it in the root container image.

David Kowis created issue - 2017-03-23 19:09

David Kowis made changes - 2017-03-23 19:15

Description

Original: I don't believe this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-28317 but I haven't been able to figure out if I have that version of the plugin installed on my jenkins, because I'm not sure what plugin that applies to.

I had a `withEnv` section that looked like:
{{
def flowContext(cl) {
    withEnv([
        'npm_config_cache=npm-cache',
        'npm_config_registry=http://npm.artifactory.mycompany.com/artifactory/api/npm/npm',
        'http_proxy=http://www-proxy.mycompany.com:8080',
        'https_proxy=http://www-proxy.homedepot.com:8080',
        'HTTP_PROXY=http://www-proxy.mycompany.com:8080',
        'HTTPS_PROXY=http://www-proxy.mycompany.com:8080',
        'PROXY_HOST=www-proxy.mycompany.com',
        'PROXY_PORT=8080',
        'no_proxy=.mycompany.com'
    ]) {
        credentialsContext(cl)
    }
}

def credentialsContext(cl) {
    withCredentials([
        usernamePassword(
            credentialsId: 'service-account-user-pass',
            passwordVariable: 'SVC_PASS',
            usernameVariable: 'SVC_USER'
        ),
        usernamePassword(
            credentialsId: 'github-auth-token',
            passwordVariable: 'GITHUB_TOKEN',
            usernameVariable: 'GITHUB_USERNAME'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-token',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_TOKEN'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-password',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_PASSWORD'
        ),
        string(credentialsId: 'slack-webhook', variable: 'SLACK_WEBHOOK_URL'),
        string(credentialsId: 'tracker-token', variable: 'TRACKER_TOKEN')

    ]) {
        cl()
    }
}

}}

The credentials context is another function that exports a few credentials into the environment.
All of the credentials would be there, but not all of the environment variables.

This would be executed within a docker container like so:

{{
    stage('pip-ci-node Build') {
        docker.image(ciNode).inside() {
            //Do the node installs in parallel, because the npm install is the slowest part, and we can use lots of cpu
            parallel(
                "Root Npm Install/Build": {
                    flowContext {
                        sh('env')
                        sh('npm install')
                        sh('gulp')
                    }
                },
                "webapp/static Install/Build": {
                    flowContext {
                        echo "Due to bug: https://issues.jenkins-ci.org/browse/JENKINS-33510"
                        sh('cd src/main/webapp/static && npm install')
                        sh('cd src/main/webapp/static && grunt prod')
                    }
                },
                failFast: true
            )
        }
    }
}}

The {{sh('env')}} command within the flowContext would never show the {{no_proxy}} environment variable. I eventually gave up on trying to get it set in the Jenkinsfile, and instead put it in the root container image.

New: I don't believe this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-28317 but I haven't been able to figure out if I have that version of the plugin installed on my jenkins, because I'm not sure what plugin that applies to.

I had a `withEnv` section that looked like:

{code:groovy}
def flowContext(cl) {
    withEnv([
        'npm_config_cache=npm-cache',
        'npm_config_registry=http://npm.artifactory.mycompany.com/artifactory/api/npm/npm',
        'http_proxy=http://proxy.mycompany.com:8080',
        'https_proxy=http://proxy.mycompany.com:8080',
        'HTTP_PROXY=http://proxy.mycompany.com:8080',
        'HTTPS_PROXY=http://proxy.mycompany.com:8080',
        'PROXY_HOST=proxy.mycompany.com',
        'PROXY_PORT=8080',
        'no_proxy=.mycompany.com'
    ]) {
        credentialsContext(cl)
    }
}

def credentialsContext(cl) {
    withCredentials([
        usernamePassword(
            credentialsId: 'service-account-user-pass',
            passwordVariable: 'SVC_PASS',
            usernameVariable: 'SVC_USER'
        ),
        usernamePassword(
            credentialsId: 'github-auth-token',
            passwordVariable: 'GITHUB_TOKEN',
            usernameVariable: 'GITHUB_USERNAME'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-token',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_TOKEN'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-password',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_PASSWORD'
        ),
        string(credentialsId: 'slack-webhook', variable: 'SLACK_WEBHOOK_URL'),
        string(credentialsId: 'tracker-token', variable: 'TRACKER_TOKEN')

    ]) {
        cl()
    }
}
{code}

The credentials context is another function that exports a few credentials into the environment.
All of the credentials would be there, but not all of the environment variables.

This would be executed within a docker container like so:

{code:groovy}
    stage('Node Build') {
        docker.image(ciNode).inside() {
            //Do the node installs in parallel, because the npm install is the slowest part, and we can use lots of cpu
            parallel(
                "Root Npm Install/Build": {
                    flowContext {
                        sh('env')
                        sh('npm install')
                        sh('gulp')
                    }
                },
                "webapp/static Install/Build": {
                    flowContext {
                        echo "Due to bug: https://issues.jenkins-ci.org/browse/JENKINS-33510"
                        sh('cd src/main/webapp/static && npm install')
                        sh('cd src/main/webapp/static && grunt prod')
                    }
                },
                failFast: true
            )
        }
    }

{code}

The {{sh('env')}} command within the flowContext would never show the {{no_proxy}} environment variable. I eventually gave up on trying to get it set in the Jenkinsfile, and instead put it in the root container image.

David Kowis made changes - 2017-03-23 19:15

Description

Original: I don't believe this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-28317 but I haven't been able to figure out if I have that version of the plugin installed on my jenkins, because I'm not sure what plugin that applies to.

I had a `withEnv` section that looked like:

{code:groovy}
def flowContext(cl) {
    withEnv([
        'npm_config_cache=npm-cache',
        'npm_config_registry=http://npm.artifactory.mycompany.com/artifactory/api/npm/npm',
        'http_proxy=http://proxy.mycompany.com:8080',
        'https_proxy=http://proxy.mycompany.com:8080',
        'HTTP_PROXY=http://proxy.mycompany.com:8080',
        'HTTPS_PROXY=http://proxy.mycompany.com:8080',
        'PROXY_HOST=proxy.mycompany.com',
        'PROXY_PORT=8080',
        'no_proxy=.mycompany.com'
    ]) {
        credentialsContext(cl)
    }
}

def credentialsContext(cl) {
    withCredentials([
        usernamePassword(
            credentialsId: 'service-account-user-pass',
            passwordVariable: 'SVC_PASS',
            usernameVariable: 'SVC_USER'
        ),
        usernamePassword(
            credentialsId: 'github-auth-token',
            passwordVariable: 'GITHUB_TOKEN',
            usernameVariable: 'GITHUB_USERNAME'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-token',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_TOKEN'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-password',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_PASSWORD'
        ),
        string(credentialsId: 'slack-webhook', variable: 'SLACK_WEBHOOK_URL'),
        string(credentialsId: 'tracker-token', variable: 'TRACKER_TOKEN')

    ]) {
        cl()
    }
}
{code}

The credentials context is another function that exports a few credentials into the environment.
All of the credentials would be there, but not all of the environment variables.

This would be executed within a docker container like so:

{code:groovy}
    stage('Node Build') {
        docker.image(ciNode).inside() {
            //Do the node installs in parallel, because the npm install is the slowest part, and we can use lots of cpu
            parallel(
                "Root Npm Install/Build": {
                    flowContext {
                        sh('env')
                        sh('npm install')
                        sh('gulp')
                    }
                },
                "webapp/static Install/Build": {
                    flowContext {
                        echo "Due to bug: https://issues.jenkins-ci.org/browse/JENKINS-33510"
                        sh('cd src/main/webapp/static && npm install')
                        sh('cd src/main/webapp/static && grunt prod')
                    }
                },
                failFast: true
            )
        }
    }

{code}

The {{sh('env')}} command within the flowContext would never show the {{no_proxy}} environment variable. I eventually gave up on trying to get it set in the Jenkinsfile, and instead put it in the root container image.

New: I don't believe this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-28317 but I haven't been able to figure out if I have that version of the plugin installed on my jenkins, because I'm not sure what plugin that applies to.

I had a `withEnv` section that looked like:

{code:none}
def flowContext(cl) {
    withEnv([
        'npm_config_cache=npm-cache',
        'npm_config_registry=http://npm.artifactory.mycompany.com/artifactory/api/npm/npm',
        'http_proxy=http://proxy.mycompany.com:8080',
        'https_proxy=http://proxy.mycompany.com:8080',
        'HTTP_PROXY=http://proxy.mycompany.com:8080',
        'HTTPS_PROXY=http://proxy.mycompany.com:8080',
        'PROXY_HOST=proxy.mycompany.com',
        'PROXY_PORT=8080',
        'no_proxy=.mycompany.com'
    ]) {
        credentialsContext(cl)
    }
}

def credentialsContext(cl) {
    withCredentials([
        usernamePassword(
            credentialsId: 'service-account-user-pass',
            passwordVariable: 'SVC_PASS',
            usernameVariable: 'SVC_USER'
        ),
        usernamePassword(
            credentialsId: 'github-auth-token',
            passwordVariable: 'GITHUB_TOKEN',
            usernameVariable: 'GITHUB_USERNAME'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-token',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_TOKEN'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-password',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_PASSWORD'
        ),
        string(credentialsId: 'slack-webhook', variable: 'SLACK_WEBHOOK_URL'),
        string(credentialsId: 'tracker-token', variable: 'TRACKER_TOKEN')

    ]) {
        cl()
    }
}
{code}

The credentials context is another function that exports a few credentials into the environment.
All of the credentials would be there, but not all of the environment variables.

This would be executed within a docker container like so:

{code:none}
    stage('Node Build') {
        docker.image(ciNode).inside() {
            //Do the node installs in parallel, because the npm install is the slowest part, and we can use lots of cpu
            parallel(
                "Root Npm Install/Build": {
                    flowContext {
                        sh('env')
                        sh('npm install')
                        sh('gulp')
                    }
                },
                "webapp/static Install/Build": {
                    flowContext {
                        echo "Due to bug: https://issues.jenkins-ci.org/browse/JENKINS-33510"
                        sh('cd src/main/webapp/static && npm install')
                        sh('cd src/main/webapp/static && grunt prod')
                    }
                },
                failFast: true
            )
        }
    }

{code}

The {{sh('env')}} command within the flowContext would never show the {{no_proxy}} environment variable. I eventually gave up on trying to get it set in the Jenkinsfile, and instead put it in the root container image.

Andrew Bayer made changes - 2017-03-24 01:28

Component/s		New: workflow-basic-steps-plugin [ 21712 ]
Component/s	Original: pipeline [ 21692 ]

Jesse Glick made changes - 2017-05-30 23:20

Description

Original: I don't believe this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-28317 but I haven't been able to figure out if I have that version of the plugin installed on my jenkins, because I'm not sure what plugin that applies to.

I had a `withEnv` section that looked like:

{code:none}
def flowContext(cl) {
    withEnv([
        'npm_config_cache=npm-cache',
        'npm_config_registry=http://npm.artifactory.mycompany.com/artifactory/api/npm/npm',
        'http_proxy=http://proxy.mycompany.com:8080',
        'https_proxy=http://proxy.mycompany.com:8080',
        'HTTP_PROXY=http://proxy.mycompany.com:8080',
        'HTTPS_PROXY=http://proxy.mycompany.com:8080',
        'PROXY_HOST=proxy.mycompany.com',
        'PROXY_PORT=8080',
        'no_proxy=.mycompany.com'
    ]) {
        credentialsContext(cl)
    }
}

def credentialsContext(cl) {
    withCredentials([
        usernamePassword(
            credentialsId: 'service-account-user-pass',
            passwordVariable: 'SVC_PASS',
            usernameVariable: 'SVC_USER'
        ),
        usernamePassword(
            credentialsId: 'github-auth-token',
            passwordVariable: 'GITHUB_TOKEN',
            usernameVariable: 'GITHUB_USERNAME'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-token',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_TOKEN'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-password',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_PASSWORD'
        ),
        string(credentialsId: 'slack-webhook', variable: 'SLACK_WEBHOOK_URL'),
        string(credentialsId: 'tracker-token', variable: 'TRACKER_TOKEN')

    ]) {
        cl()
    }
}
{code}

The credentials context is another function that exports a few credentials into the environment.
All of the credentials would be there, but not all of the environment variables.

This would be executed within a docker container like so:

{code:none}
    stage('Node Build') {
        docker.image(ciNode).inside() {
            //Do the node installs in parallel, because the npm install is the slowest part, and we can use lots of cpu
            parallel(
                "Root Npm Install/Build": {
                    flowContext {
                        sh('env')
                        sh('npm install')
                        sh('gulp')
                    }
                },
                "webapp/static Install/Build": {
                    flowContext {
                        echo "Due to bug: https://issues.jenkins-ci.org/browse/JENKINS-33510"
                        sh('cd src/main/webapp/static && npm install')
                        sh('cd src/main/webapp/static && grunt prod')
                    }
                },
                failFast: true
            )
        }
    }

{code}

The {{sh('env')}} command within the flowContext would never show the {{no_proxy}} environment variable. I eventually gave up on trying to get it set in the Jenkinsfile, and instead put it in the root container image.

New: I don't believe this is a duplicate of ~~JENKINS-28317~~ but I haven't been able to figure out if I have that version of the plugin installed on my jenkins, because I'm not sure what plugin that applies to.

I had a `withEnv` section that looked like:
{code:none}
def flowContext(cl) {
    withEnv([
        'npm_config_cache=npm-cache',
        'npm_config_registry=http://npm.artifactory.mycompany.com/artifactory/api/npm/npm',
        'http_proxy=http://proxy.mycompany.com:8080',
        'https_proxy=http://proxy.mycompany.com:8080',
        'HTTP_PROXY=http://proxy.mycompany.com:8080',
        'HTTPS_PROXY=http://proxy.mycompany.com:8080',
        'PROXY_HOST=proxy.mycompany.com',
        'PROXY_PORT=8080',
        'no_proxy=.mycompany.com'
    ]) {
        credentialsContext(cl)
    }
}

def credentialsContext(cl) {
    withCredentials([
        usernamePassword(
            credentialsId: 'service-account-user-pass',
            passwordVariable: 'SVC_PASS',
            usernameVariable: 'SVC_USER'
        ),
        usernamePassword(
            credentialsId: 'github-auth-token',
            passwordVariable: 'GITHUB_TOKEN',
            usernameVariable: 'GITHUB_USERNAME'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-token',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_TOKEN'
        ),
        usernamePassword(
            credentialsId: 'service-account-maven-artifactory-password',
            passwordVariable: 'ARTIFACTORY_USER',
            usernameVariable: 'ARTIFACTORY_PASSWORD'
        ),
        string(credentialsId: 'slack-webhook', variable: 'SLACK_WEBHOOK_URL'),
        string(credentialsId: 'tracker-token', variable: 'TRACKER_TOKEN')

    ]) {
        cl()
    }
}
{code}
The credentials context is another function that exports a few credentials into the environment.
All of the credentials would be there, but not all of the environment variables.

This would be executed within a docker container like so:
{code:none}
    stage('Node Build') {
        docker.image(ciNode).inside() {
            //Do the node installs in parallel, because the npm install is the slowest part, and we can use lots of cpu
            parallel(
                "Root Npm Install/Build": {
                    flowContext {
                        sh('env')
                        sh('npm install')
                        sh('gulp')
                    }
                },
                "webapp/static Install/Build": {
                    flowContext {
                        echo "Due to bug: https://issues.jenkins-ci.org/browse/JENKINS-33510"
                        sh('cd src/main/webapp/static && npm install')
                        sh('cd src/main/webapp/static && grunt prod')
                    }
                },
                failFast: true
            )
        }
    }

{code}
The {{sh('env')}} command within the flowContext would never show the {{no_proxy}} environment variable. I eventually gave up on trying to get it set in the Jenkinsfile, and instead put it in the root container image.

Jesse Glick added a comment - 2017-06-30 16:54

Sounds like a bug but I have no idea offhand where. Would need to narrow it down into a minimal, self-contained reproduction case. (Is withCredentials necessary? Image.inside?)

Jesse Glick added a comment - 2017-06-30 16:54 Sounds like a bug but I have no idea offhand where. Would need to narrow it down into a minimal, self-contained reproduction case. (Is withCredentials necessary? Image.inside ?)

Aurélie Vache added a comment - 2017-10-09 09:02

Seems we have the same issue for http_proxy, https_proxy and no_proxy env var setted in environement or withEnv.

is it possible to have some news about this issue?

Thanks.

Aurélie Vache added a comment - 2017-10-09 09:02 Seems we have the same issue for http_proxy, https_proxy and no_proxy env var setted in environement or withEnv. is it possible to have some news about this issue? Thanks.

Aaron D. Marasco added a comment - 2017-10-27 12:30

I'm hitting this as well, and hopefully can show it here:

properties properties: [ // This is ugly https://stackoverflow.com/a/35471196
  parameters([
    string(defaultValue: '', description: 'RPM Release tag (e.g. "beta"). Usually left blank.', name: 'RPM_Release'),
  ]),
]
// ... later ...:
        // Start the actual build
        // Workaround for JENKINS-43077 (as is any RR to get cleaned up later)
        def RR=""
        if (params.RPM_Release.trim())
          RR="export RPM_RELEASE=${params.RPM_Release.trim()};"
        prereq_image.inside("--volumes-from tools_arm_cs:ro --name ${env.BUILD_TAG}-C${OS}") {
          withEnv(["RPM_RELEASE=${params.RPM_Release.trim()}"]) {
            sh """
              ${RR}
              make -C releng driver
              cd releng; make cdk # cdk-all
              """
          } // env
        } // inside() container

If I comment out that "RR" line, make isn't getting RPM_RELEASE set properly.

If it matters, this is all within a closure that is going into a map for parallel and lives within a timestamps block.

Aaron D. Marasco added a comment - 2017-10-27 12:30 I'm hitting this as well, and hopefully can show it here: properties properties: [ // This is ugly https://stackoverflow.com/a/35471196 parameters([ string(defaultValue: '', description: ' RPM Release tag (e.g. "beta" ). Usually left blank. ', name: ' RPM_Release'), ]), ] // ... later ...: // Start the actual build // Workaround for JENKINS-43077 (as is any RR to get cleaned up later) def RR="" if (params.RPM_Release.trim()) RR= "export RPM_RELEASE=${params.RPM_Release.trim()};" prereq_image.inside( "--volumes-from tools_arm_cs:ro --name ${env.BUILD_TAG}-C${OS}" ) { withEnv([ "RPM_RELEASE=${params.RPM_Release.trim()}" ]) { sh """ ${RR} make -C releng driver cd releng; make cdk # cdk-all """ } // env } // inside() container If I comment out that " RR " line, make isn't getting RPM_RELEASE set properly. If it matters, this is all within a closure that is going into a map for parallel and lives within a timestamps block.

Jesse Glick added a comment - 2017-10-27 15:10

Probably a duplicate.

Jesse Glick added a comment - 2017-10-27 15:10 Probably a duplicate.

Jesse Glick made changes - 2017-10-27 15:10

Component/s		New: docker-workflow-plugin [ 20625 ]
Component/s	Original: workflow-basic-steps-plugin [ 21712 ]

Assignee:: Unassigned

Reporter:: David Kowis

Votes:: 6 Vote for this issue

Watchers:: 12 Start watching this issue

Created:: 2017-03-23 19:09

Updated:: 2023-10-15 19:31

Jenkins

Details

Description

Attachments

Activity

Collapse comment: Jesse Glick added a comment - 2017-06-30 16:54

Expand comment: Jesse Glick added a comment - 2017-06-30 16:54

Collapse comment: Aurélie Vache added a comment - 2017-10-09 09:02

Expand comment: Aurélie Vache added a comment - 2017-10-09 09:02

Collapse comment: Aaron D. Marasco added a comment - 2017-10-27 12:30

Expand comment: Aaron D. Marasco added a comment - 2017-10-27 12:30

Collapse comment: Jesse Glick added a comment - 2017-10-27 15:10

Expand comment: Jesse Glick added a comment - 2017-10-27 15:10

People

Dates